Search

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

200 result(s) for Device

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

3.1.8 Device

Device As defined in OPC 10000-100 . Note 1 to entry: For this document a Device also executes one or more OPC UA Applications. Note 2 to entry: a generic ... computer or mobile device may be a Device if it has a DeviceIdentity Certificate
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

3.1.3 device

device independent physical entity capable of performing one or more specified functions in a particular context and delimited by its interfaces Note 1 to entry: See IEC 61499-1. Note ... valve controllers, drives, motor controllers, PLCs, and communication gateways. Note 3 to entry: A Device can be a system (topology) of other Devices , components, or parts
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

3.1.5 Device

Device independent physical entity capable of performing one or more specified functions in a particular context and delimited by its interfaces Note 1 to entry: See IEC 61499-1. Note ... valve controllers, drives, motor controllers, PLCs, and communication gateways. Note 3 to entry: A Device can be a system (topology) of other Devices , components, or parts
OPC-30142 – OPC UA for PROFINET Remote IO

3.2.2 Device

Device A Device is a stand-alone unit exchanging cyclic data with a Controller . Devices are usually configured by the Controller and may also generate acyclic data like alarms ... diagnostic information. A Device may consist of several modules and Submodules . Remote IO (RIO) RIO Channel RIO Input Channel
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

3.2.11 Device

Device A Device is a separate addressable unit exchanging IO Data with a Controller . Devices are usually configured by the Controller and may also generate acyclic data like Alarms ... diagnostic information. A Device may consist of several modules and Submodules . The IO Data , the Parameters, the Alarms, and the Data Objects of a Device are described in the GSDML
OPC-30200 – OPC UA for Commercial Kitchen Equipment

3.2.2 Device

Device item of technical equipment, equipped with a communication interface and software that enables the exchange of data in accordance with this definition
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.2 URIs

ApplicationUris identify an OPC UA 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 ... subjectAltName (see OPC 10000-6 ); 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
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services

7.5 Application Setup

Devices can be authenticated when they are added to the network. Once a Device is authenticated the Device is trusted and can use the push or PullManagement without additional administrator ... Certificates in the TrustList . A vendor specific process for setup is required if a device restricts the Clients allowed to connect securely. See Annex G for more specific instructions
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services

7.10.13 ResetToServerDefaults

application configuration to its default settings. If the application is running on a Device that supports OPC 10000-21 , the Device is placed in a state where the Onboarding process ... restart. If the Device does not support OPC 10000-21 , the Server repeats the Application Setup process described in Annex G . If the application is a Server , after this Method
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

3.1.1 Application

Application a program that runs on a Device and communicates with other Applications on the network. Note 1 to entry: Each Application has an identifier that is unique within
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

3.1.2 ApplicationUri

ApplicationUri a globally unique identifier for an OPC UA Application running on a particular Device . Note 3 to entry: The Application Instance Certificate has the ApplicationUri in the subjectAltName field
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

3.1.3 Composite

globally unique identifier. Note 2 to entry: A Composite may act as a single Device when connected to a network. Note 3 to entry: A Composite may appear as multiple
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

3.1.9 Device Configuration Application (DCA)

Device Configuration Application (DCA) a Client or Server installed on a Device used to configure other applications installed on the same Device . Note 1 to entry: a DCA which
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

3.1.10 DeviceIdentity Certificate

DeviceIdentity Certificate a Certificate issued to a Device that identifies the Device . Note 1 to entry: All DeviceIdentity Certificates have the ProductInstanceUri as a subjectAltName . Note 2 to entry
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-21 – OPC Unified Architecture - Part 21: Device Onboarding

3.1.19 Ticket

Ticket a document that identifies a Device or Composite and has a DigitalSignature
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

4.1 Device Lifecycle

Device Lifecycle The Onboarding model is designed to allow the configuration of a Device to be managed over the complete lifecycle of the Device from manufacture to decommissioning. The entire ... they are given access to a sensitive network. The complete life cycle of a Device is shown in Figure 1 . Figure 1 - The Lifecycle of a Device The actors
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

4.2.1 Secure Elements

cryptographic secrets that protect them against authorized access and disclosure. The mechanisms defined for Device authentication depend on PrivateKeys that are stored in SecureElements . PrivateKeys stored on Devices without SecureElements
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

4.2.2 Firmware and Applications

Firmware and Applications Every Device has multiple layers of hardware and software that are installed and managed at different stages in the lifecycle by different actors. The layers are shown ... Figure 2 . Figure 2 - Device Hardware and Software Layers A Device has firmware that is generally not changed during normal operation. Firmware updates may be provided by the Manufacturer
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

4.2.3 Transfer of Physical Control

Transfer of 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 ... organization. When a transfer of physical control occurs, the supplier ships the equipment (a Device or Composite ) and an electronic Ticket (see 6 ) that describes the equipment. The receiver
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

4.2.4 Trust on First Use (TOFU)

allow Devices to authenticate the network it is connected to. This implies that a Device connected to a network will allow itself to be configured via any network that ... same as a factory reset which typically deletes all software installed on the Device . The reset mechanism should require proof of physical possession of the Device to ensure it cannot
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

4.2.5 SoftwareUpdateManager

system component that provides updates to firmware or software running on a Device . The SoftwareUpdateManager may implement the standard model defined in OPC 10000-100 , however, it often will
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

4.2.6 Roles and Privileges

possible. SoftwareUpdateAdmin The Role grants rights to set the software status for a Device . SecurityAdmin The Role grants the right to changes the security configuration of a Registrar ... listed in Table 4 . Table 4 - Privileges for Onboarding Name Description DeviceSelfAdmin The Device has rights to modify its own registration. DCA The Client is a DCA that has rights
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

4.3.2 Onboarding

Onboarding Onboarding is the process where a Device or Composite is connected to the network managed by an organization. When this happens the authenticity of the Device is verified ... interactions with a Registrar running on the network. Every Device has a Device Configuration Application (DCA) which interacts with the Registrar using the interactions described in PullManagement ( 7.2 ) or PushManagement
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

4.3.3 Application Setup

Application Instance Certificate and a TrustList to one or more Applications running on a Device that will allow the Applications to communicate with other OPC UA Applications running ... request or accept Certificates on behalf of any Application running on the Device . If the DCA is a Client it can connect to CertificateManager and request the additional Certificates
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

4.3.4 Configuration

Configuration Configuration occurs when the Applications running on the Device are installed, modified, backed up or restored. Configuration is also the mode that allows a new Device to be dropped ... replacement for an existing Device that is no longer functioning. Some Devices may allow individual Applications to be configured while other Applications continue in Operation state described
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

4.3.5 Operation

Operation Operation occurs when one or more Applications on a Device are running normally performing whatever task it was deployed to do. In this stage it is possible to update
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

4.3.6 Decommissioning

Decommissioning Decommissioning is the final state for the Device where it is reset to an initial state to ensure that all sensitive data is deleted. Any permissions granted ... Device on the OwnerOperator network are revoked. The DeviceIdentity Certificates and their associated PrivateKeys are not affected by a reset. A Device that was Decommissioned by mistake can be Onboarded
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

5.1 Device Identity

Device Identity Every Device shall have an "Initial Device Identifier" (IDevID) Certificate (see 802.1AR ) that is used to prove the origin of the Device . This identity shall ... 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
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

externally visible Devices . A Machine is a common example of a Composite . A Device which is visible on an external network may have an LDevID Certificate (see 802.1AR ) created ... CompositeBuilder that can be used to prove the Device belongs to the Composite . The CompositeInstanceUri is an identifier for the Composite assigned by the CompositeBuilder . All Devices in the same
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

6.1 Tickets

Tickets The Device lifecycle shown in Figure 1 implies information needs to flow between businesses when there is a transfer of physical control over a Device (see 4.2.3 ). How this ... format of a document that contains information that needs to be provided with a Device . A Ticket is the term used for a document that describes one or more Devices
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

6.2 Ticket Distribution

When transferring Devices, the sender provides a DeviceIdentityTicket (see 8.2.1 ) for each Device. When transferring Composites, the sender provides a CompositeIdentityTicket (see 8.2.4 ) for each Composite and a DeviceIdentityTicket ... each externally visible Device in the 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
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

6.3 Authentication

their DeviceIdentity Certificates and finds the corresponding DeviceIdentityTicket . If a match was found the Device is accepted and can be provisioned for use on the network ... complete description of this process. There are two modes of operation that a Device can use depending on whether it is a Client or a Server . Clients use PullManagement which
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

6.4 Acquiring and Validating Tickets

Acquiring and Validating Tickets Device authentication depends on a process for creating, distributing and validating Tickets which contain information needed to determine if any given Device is allowed ... file is delivered to an RegistrarAdmin that uploads it to Registrar . When a new Device is detected on the network the matching Ticket is found which confirms that the Device
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

7.1 Overview

trust. The steps to determine trust are: Read all DeviceIdentity Certificates from the Device ; Locate a Ticket that has a ProductInstanceUri that matches one or more DeviceIdentity Certificates ; Validate ... Validate DeviceIdentity Certificate that matches the Ticket ; Establish a secure connection to the Device using the selected DeviceIdentity Certificate. Issue a DCA Application Instance Certificate to the Device that indicates
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

7.2 Pull Management

Management Clients may use pull management which is illustrated in Figure 4 . Figure 4 - Device Authentication using Pull Management See 7 for a complete description of the Device authentication process ... sequence begins when the Device discovers the location of the Registrar via mDNS (see OPC 10000-12 ), the SetRegistrarEndpoints Method is called ( Servers only) or the Endpoints are provided
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

7.3 Push Management

Push Management Servers may use PushManagement which is illustrated in Figure 6 . Figure 6 - Device Authentication using Push Management See 7 for a complete description of the authentication process. Each ... SecureChannel and calls RequestTickets . The Registrar needs to validate the Tickets returned by the Device which requires access to the Certificate that created one of the Signatures and the ability
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

7.4.1 Overview

Overview There are different standards for Device Authentication which do not meet the complete set of requirements described in this specification. However, an OwnerOperator may have reasons ... complete solution that manages the entire life cycle of the Certificates installed on the Device . In these cases, the onboarding mechanisms described in this specification are not used
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

7.4.2.2 Integration with the Registrar

handoff from the FDO protocol to the mechanisms defined in this document. Figure 9 - Device Authentication with the FDO Protocol Specifically, the FDO Owner supplies the FDO device with ... FSIM (fdo.csr) that creates a new LDevID that can be installed on the FDO Device as part of the onboarding process described in 7.4.2.1 . This LDevID shall contain the information
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

8.1 Signed Ticket Encoding

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.2 BaseTicketType

manufacturerName 0:String The name of the Manufacturer for the Device . modelName 0:String The model name assigned by the Manufacturer . Not specified if no model name was assigned ... same as the current version of software installed on the Device . Not specified if no software revision was assigned or known. serialNumber 0:String The serial number assigned
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 ... BaseTicketType DataType defined in 8.2.1 . productInstanceUri 0:UriString The ProductInstanceUri for the Device . Its representation in the AddressSpace is defined in Table 10 . Table 10 - DeviceIdentityTicketType Definition Attribute Value BrowseName
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
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

9.2.2 DeviceRegistrarType

Administration 2:DeviceRegistrarAdminType Optional Conformance Units Onboarding Registrar PullManagement The ProvideIdentities Method allows a Device to request that it be authenticated so it can have access to the network ... UpdateSoftwareStatus Method is used by the SoftwareUpdateManager to tell the Registrar that the Device has up to date software. The RegisterDeviceEndpoint Method allows an administration Client to provide the location
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

9.2.3 ProvideIdentities

ProvideIdentities The ProvideIdentities Method allows a Device to request that it be authenticated so it can have access to the network. It is called by a Device using PullManagement ... ManagerDescription softwareUpdateManager ); Argument Description identities The DER encoded DeviceIdentity Certificates issued to the Device . The first Certificates shall be the IDevID Certificates. issuers The DER encoded Certificates needed to verify
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

9.2.4 UpdateSoftwareStatus

UpdateSoftwareStatus The UpdateSoftwareStatus Method allows a Client to provide the firmware status for a Device on the network. The Client may be the SoftwareUpdateManager (see 4.2.5 ) or other administrative application ... Boolean status, [in] 0:String softwareRevision ); Argument Description productInstanceUri The unique identifier for the Device . status The status of the software. If TRUE the firmware is up to date, otherwise
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

9.2.5 RegisterDeviceEndpoint

RegisterDeviceEndpoint The RegisterDeviceEndpoint Method allows a Client to provide the location of a Device on the network that needs to be authenticated. The Client may be an engineering tool ... information that cannot be discovered automatically. Once the Registrar knows the location of a Device it schedules a task that uses PushManagement to complete the onboarding process. This Method shall
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

9.2.10 DeviceRegistrarAdminType

Devices and Composites that it is expecting to install on the network. Any Device which matches one of these Tickets will be accepted automatically. The UnregisterTickets Method allows an administration ... administration Client to manage the Certificates for authorities that sign Tickets . If a Device provides a Ticket, it is accepted automatically if and only if the signing Certificate
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

9.2.11 RegisterTickets

Devices and Composites that it is expecting to install on the network. Any Device which can be correlated with one of these Tickets will be accepted automatically. This Method validates
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

9.2.13 DeviceRegistrationAuditEventType

This abstract Event is a base type for events raised when a change affecting Device registration occurs. This Event and its subtypes are security related and Servers shall only report ... defined in OPC 10000-5 . The ProductInstanceUri Property specifies the identity for the Device that was affected by the change
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

9.2.14 DeviceIdentityAcceptedAuditEventType

Composite Property is the signed Ticket (see 8.1 ) for the Composite that contains the Device
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

9.2.15 DeviceSoftwareUpdatedAuditEventType

DeviceSoftwareUpdatedAuditEventType This abstract Event is raised when the Registrar receives the Device software status has changed. This Event and it subtypes are security related and Servers shall only report them ... defined in OPC 10000-5 . The Status Property is the TRUE if the Device firmware is up to date. The SoftwareRevision Property is the version of the firmware that
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

9.3.1 Overview

also allows the location of the Registrars to be manually provided if the Device needs to use PullManagement and no multicast discovery capabilities are available. Figure 11 - Device Address Space ... organized by the Resources Object (see OPC 10000-22 ) used to provision the Device the Server is running on. It is an instance of the ProvisionableDeviceType ObjectType which defines Methods
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

9.3.2 ProvisionableDevice

ProvisionableDeviceType. It is the well-known Resource which is used to authenticate a Device using PushManagement . It is a target of an Organizes Reference from the Resources Object defined
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

9.3.3 ProvisionableDeviceType

RequestTickets Method allows the Registrar to request the list of Tickets stored on the Device . The SetRegistrarEndpoints Method allows a configuration Client to provide the location of one or more ... Registrars which the Device can use to authenticate itself via PullManagement . The :<ApplicationName> Objects defines an API which represents the configuration of an Client or Server running
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

9.3.4 RequestTickets

RequestTickets Method allows a Client to request the list of Tickets stored on the Device . It is called by a Client using PushManagement to authenticate a Device. The Registrar follows ... RequestTickets ( [out] 0:EncodedTicket [] tickets ); Argument Description tickets The signed Tickets stored on the Device . Method Result Codes (defined in Call Service) Result Code Description Table 34 specifies the AddressSpace
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

9.3.5 SetRegistrarEndpoints

allows a Client to provide the location of one or more Registrars which the Device can use to authenticate itself via PullManagement . The Client may be an engineering tool ... Signature SetRegistrarEndpoints ( [in] 0:ApplicationDescription [] registrars ); Argument Description registrars The Servers which allow a Device to be authenticated via PullManagement . Method Result Codes (defined in Call Service) Result Code Description
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts

3.1.14 OfflineEngineering

planned (typically without the hardware available), which gets deployed to the physical Controller , device , or Compute during the commissioning phase at a plant
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts

5.1 Motivation

they support the same infrastructure, they cannot coexist in the same network. Also, device information is structured using different syntax and semantics, making data analysis a labour-intensive and time
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.3.2 FxAssetType definition

information that is defined as an Interface . Being defined as an Interface allows other device models to include what is required for OPC UA FX Asset modelling without having ... software component, the software/firmware of a hardware component, or the software/firmware of the Device ." " DeviceRevision provides the overall revision level of a hardware component or the Device
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

6.4.1 Overview

More complex IA-stations incorporating several End Station Components and Bridge Components within one device can also be found in industrial automation (e.g., a Controller with multiple modules
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

1 Scope

This specification describes three models which build upon each other as follows: The (base) Device Model is intended to provide a unified view of devices and their hardware and software ... parts irrespective of the underlying device protocols. The Device Communication Model adds Network and Connection information elements so that communication topologies can be created. The Device Integration Host Model finally
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

3.1.1 Block

function block (see IEC 62769 ) or to the resource parameters of the Device itself
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

3.1.4 Connection Point

Connection Point logical representation of the interface between a Device and a Network
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

3.1.8 Fieldbus

Note 2 to entry: Designates the communication bus used by a Device
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

3.1.9 Parameter

Parameter variable of the Device that can be used for configuration, monitoring or control purposes Note 1 to entry: In the information model it is synonymous
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

3.2 Abbreviated terms

Abbreviated terms ADI Analyser Device Integration ASiC-E Associated Signature Container Extended (ZIP with signature, see ASiC-E ) BMP Bitmap (image format) CAdES CMS Advanced Electronic Signatures (see CAdES ... Cryptographic Message Syntax CP Communication Processor (hardware module) CPU Central Processing Unit (of a Device ) DA Data Access DI Device Integration (the short name for this specification) ERP Enterprise Resource
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

4.1 General

General Figure 1 depicts the main ObjectTypes of the base device model and their relationship. The drawing is not intended to be complete. For the sake of simplicity only ... relations were captured to give a rough idea of the overall structure. Figure 1 - Device model overview The boxes in this drawing show the ObjectTypes used in this specification
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

4.5.2 VendorNameplate Interface

software component, the software/firmware of a hardware component, or the software/firmware of the Device . SemanticVersionString (a sub-type of String defined in OPC 10000-5 ) can be used when using ... Versioning format. DeviceRevision provides the overall revision level of a hardware component or the Device . As an example, this Property can be used in ERP systems together with the ProductCode
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

4.5.4 DeviceHealth Interface

Properties and Alarms that are commonly used to expose the health status of a Device . It is illustrated in Figure 7 and formally defined in Table 21 . Figure 7 - DeviceHealth ... NAMUR Recommendation NE107 . Clients can read or monitor this Variable to determine the device condition. The DeviceHealthEnumeration DataType is an enumeration that defines the device condition. Its values are defined
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

4.5.5 OperationCounter Interface

UInteger 0:PropertyType O Conformance Units DI OperationCounter Interface PowerOnDuration is the duration the Device has been powered. The main purpose is to determine the time in which degradation ... Device occurred. The details, when the time is counted, is implementation-specific. Companion specifications can define specific rules. Typically, when the Device has supply voltage and the main
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

4.6 ComponentType

does not mandate any Properties . This makes it usable for representation of a Device or parts of a Device . Parts include both mechanical and software parts. The ComponentType applies
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

4.7 DeviceType

DeviceType This ObjectType can be used to define the structure of a Device . Figure 10 shows the DeviceType . It is formally defined in Table 35 . Figure 10 - DeviceType Table
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

4.8 SoftwareType

SoftwareType This ObjectType can be used for software modules of a Device or a part of a Device . SoftwareType is a concrete subtype of ComponentType and can be used directly
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

4.9 DeviceSet entry point

locatable by following Hierarchical References from the root instance. An example is the Modular Device defined in 9.4 and also illustrated in Figure 12 . Examples: UA Server represents a monolithic ... modular Device : DeviceSet only contains one instance UA Server represents a host system that has access to a number of Devices that it manages: DeviceSet contains several instances that
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

5.1 General

communication topology. The types for this model are illustrated in Figure 16 . Figure 16 - Device communication model overview A ProtocolType ObjectType represents a specific communication protocol (e.g., FieldBus ) implemented ... Examples are shown in Figure 18 . The ConnectionPointType represents the logical interface of a Device to a Network . A Network is the logical representation of wired and wireless technologies. Figure
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

5.2 ProtocolType

used to specify a specific communication (e.g., FieldBus ) protocol that is supported by a Device (respectively by its ConnectionPoint ) or Network . The BrowseName of each instance of a ProtocolType shall
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

5.4 ConnectionPoint

ConnectionPoint This ObjectType represents the logical interface of a Device to a Network . A specific subtype shall be defined for each protocol. Figure 20 shows the ConnectionPointType including some specific ... types. Figure 20 - Example of ConnectionPointType hierarchy A Device can have more than one such interface to the same or to different Networks . Different interfaces usually exist for different protocols
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

5.5 ConnectsTo and ConnectsToParent ReferenceTypes

their ConnectionPoint , respectively). Browsing a Network returns the connected Devices ; browsing from a Device , one can follow the ConnectsTo Reference from the Device's ConnectionPoint to the Network . The ConnectsToParent ... ReferenceType is a concrete ReferenceType used to define the parent (i.e. the communication Device ) of a Network . It is a subtype of the ConnectsTo ReferenceType . The two ReferenceTypes are illustrated
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

6.1 General

General A Device Integration Host is a Server that manages integration of multiple Devices in an automation system and provides Clients with access to information about Devices regardless of where ... information is stored, for example, in the Device itself or in a data store. The Device communication is internal to the host and can be based on field-specific protocols
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

6.2 DeviceTopology Object

DeviceTopology Object The Device Topology reflects the communication topology of the Devices . It includes Devices and the Networks. The entry point DeviceTopology is the starting point within the AddressSpace ... level Networks that provide access to all instances that constitute the Device Topology ((sub-)networks, devices and communication elements). The DeviceTopology node is formally defined in Table 51 . Table
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

6.3.1 General

General Management of the Device Topology is a configuration task, i.e., the elements in the topology ( Devices , Networks , and Connection Points ) are usually configured "offline ... them. This is illustrated in Figure 27 . Figure 27 - Online component for access to Device data If Online/Offline is supported, the main (leading) instance represents the offline information. Its HasTypeDefinition
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

6.3.2 IsOnline ReferenceType

IsOnline ReferenceType is a concrete ReferenceType used to bind the offline representation of a Device to the online representation. The source and target Node of References of this type shall ... instance of the same subtype of a ComponentType . Each Device shall be the source of at most one Reference of type IsOnline . The IsOnline ReferenceType is illustrated in Figure
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

6.4.1 Definition

transfer of information ( Parameters ) between offline nodes and the physical device is supported through OPC UA Methods . These Methods are built on device specific knowledge and functionality. The transfer ... Server . However, whenever possible after a failure, the Server should bring the Device back into a functional state. The Client has to retry by calling the transfer Method again
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

6.4.2 TransferServices Type

Type The TransferServicesType provides the Methods to transfer data to and from the online Device . Figure 29 shows the TransferServicesType definition. It is formally defined in Table 53 . Figure
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

6.4.3 TransferServices Object

Methods and shall have the BrowseName Transfer . HasComponent is used to reference from a Device to its "TransferServices" Object . The TransferServiceType and each instance can share the same
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

6.4.4 TransferToDevice Method

TransferToDevice Method TransferToDevice initiates the transfer of offline configured data ( Parameters ) to the physical device. This Method has no input arguments. Which Parameters are transferred is based on Server -internal ... affected by the transfer. That way the cache will be re-populated from the Device next time they are requested. The signature of this Method is specified below. Table
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

6.4.5 TransferFromDevice Method

TransferFromDevice Method TransferFromDevice initiates the transfer of values from the physical device to corresponding Parameters in the offline representation of the Device . This Method has no input arguments. Which Parameters ... InitTransferStatus Specifies if the transfer has been initiated. 0 - OK -1 - E_NotLocked - the Device is not locked by the calling Client -2 - E_NotOnline - the Device is not online
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

6.4.6 FetchTransferResultData Method

data. Result data will be deleted with each new transfer request for the same Device . FetchTransferResultData is used to request the execution status and a set of result data ... transfer operation was aborted; no results exist. -3 - DeviceError: An error in the device or the communication to the Device occurred. "diagnostics" can contain device- or protocol-specific
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

7.3 LockingServices Object

referenced using HasComponent or HasAddIn from the lock-owner Object (for example, a Device ). The LockingServicesType and each instance can share the same Methods . All Properties are distinct
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.1 Overview

update model defined in this clause is used to manage the software of a Device . This can include the installation of new software, the update of existing software, the update ... update. The specific steps to perform the actual installation are only known by the device. They are not exposed by this Information Model . The use cases that were considered
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.3.11 AddIn model

instance the fixed BrowseName "SoftwareUpdate" shall be used. This model gives any device, hardware- or software-component the opportunity to support SoftwareUpdate . With this mechanism it is also ... expose parts as additional software components with their own update AddIn . To identify the device / component that is the target for the software update, the IVendorNameplateType Interface is used
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.7.5 Solution packages

Packages as a single file (e.g., a complete machine with several devices or one device with several updateable components). Only a specific combination of Software Packages shall be installed (could ... Solution Package ). A combination of several Software Packages shall be installed to a device as a single file. The device is then responsible for distribution / installation of the subpackages
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

9.3 Block Devices

Block Devices A Block -oriented Device can be composed using the modelling elements defined in this specification. A Block -oriented Device includes a configurable set of Blocks . Figure 58 shows ... general structure of Block -oriented Devices . Figure 58 - Block-oriented Device structure example An Object called Blocks is used as a container for the actual BlockType instances
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

9.4 Modular Devices

Modular Devices A Modular Device is represented by a (subtype of) ComponentType that is composed of a top- Device and a set of subdevices (modules). The top- Device often ... depends on the used subdevices. The supported subdevices can be restricted by the Modular Device . Figure 59 shows the general structure of Modular Devices . Figure 59 - Modular Device structure example
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

12.2 Handling of OPC UA namespaces

defined in the local Server . This can include types and instances used in a Device represented by the Server . This namespace shall have namespace index 1. Mandatory http://opcfoundation.org/UA/DI/
OPC-30000 – OPC UA for Programmable Logic Controllers based on IEC61131-3

4.2.3.4 Introduction to OPC UA Devices

model is intended to provide a unified view of Devices irrespective of the underlying Device protocols. Controllers are physical or logical Devices and the Devices model is therefore used ... communication infrastructure in an OPC UA Address Space . The main use cases are Device configuration and diagnostic, but it allows a general and standardized way for any kind of application
OPC-30081 – OPC UA for Process Automation Devices - PA-DIM™

7.2 PADIMType

ISignal PA-DIM SignalSet PA-DIM SubDevices PA-DIM DeviceRevision PA-DIM Device Condition Set PA-DIM IGeneralDeviceConditionSet Interface PA-DIM IGeneralDeviceConditionSet DeviceComponentConditions The DefaultInstanceBrowseName Property - defined ... DeviceRevision). DeviceRevision provides the overall revision level of a hardware component or the Device . As an example, this Property can be used in ERP systems together with the ProductCode Property
OPC-30110 – OPC UA for POWERLINK - POWERLINK: OPC Unified Architecture

5.1 Overview

subtypes of PowerlinkConnectionPointType are used to represent the POWERLINK Object Dictionary of a POWERLINK Device . The subtypes of ConnectionPointType are used to extend a Device (not limited to PowerlinkDeviceType ... more POWERLINK Object Dictionaries . The PowerlinkDeviceType is used to represent a typical POWERLINK Device and defines a standardised way to generate the mandatory Properties for a DeviceType (like SerialNumber, RevisionCounter
OPC-30110 – OPC UA for POWERLINK - POWERLINK: OPC Unified Architecture

6.1.1 General

General This OPC UA ObjectType represents a Device with one or more POWERLINK interfaces. Figure 15 shows an overview for the PowerlinkDeviceType with its Properties and related components
OPC-30110 – OPC UA for POWERLINK - POWERLINK: OPC Unified Architecture

6.1.2 PowerlinkDeviceType Definition

instance for the representation of POWERLINK Devices by a generic gateway. Usually a Device will only implement one of these choices, but it is also possible to implement multiple POWERLINK ... interfaces on one Device. The usage of the PowerlinkCnConnectionPointType and the PowerlinkMnConnectionPointType is not limited to the PowerlinkDeviceType . These ConnectionPoint -Types can be used by any other subtype of DeviceType
OPC-30110 – OPC UA for POWERLINK - POWERLINK: OPC Unified Architecture

6.1.5 Mapping for DeviceType (Types namespace)

DeviceType defined in OPC 10000-100, which mandates a list of Properties for the Device . Table 16 defines the values for these Properties based on the POWERLINK Objects ... POWERLINK interface, the selection of the interface as source for these objects is device specific. Table 16 - DeviceType Mapping DeviceType / OPC 10000-100 POWERLINK BrowseName DataType Description 1:SerialNumber String
OPC-30142 – OPC UA for PROFINET Remote IO

6.2 OPC UA for RIO Channel Model

needed to represent the IO's associated with the PN Submodules of the Device . The "ProcessValue" Variable in Figure 8 contains an analog Process Value . The VariableType used
OPC-30142 – OPC UA for PROFINET Remote IO

6.8.1.1 Condensed Status restricted to NE 107

Condensed Status restricted to NE 107 If the Device generates condensed status codes restricted to NE 107 (See [ PCD ] chapter 5.4.3.2), the status information delivered for one Process Value
OPC-30142 – OPC UA for PROFINET Remote IO

7.1.1.1 SetApplicationTag Method

server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure. If the SetApplicationTag Method
OPC-30142 – OPC UA for PROFINET Remote IO

7.1.3.1 SetSimulation Method

server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure
OPC-30142 – OPC UA for PROFINET Remote IO

7.1.3.2 SetSimulationValue Method

server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure
OPC-30142 – OPC UA for PROFINET Remote IO

7.1.5.1 SetSimulation Method

server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure
OPC-30142 – OPC UA for PROFINET Remote IO

7.1.5.2 SetSimulationValue Method

server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure
OPC-30142 – OPC UA for PROFINET Remote IO

7.2.1.1 SetApplicationTag Method

server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure. The Server might provide diagnosis
OPC-30142 – OPC UA for PROFINET Remote IO

7.2.2.2 SetMode Method

Server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure. If the Mode Variable
OPC-30142 – OPC UA for PROFINET Remote IO

7.2.2.3 SetManualProcessValue Method

Server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure. If the ManualProcessValue Variable
OPC-30142 – OPC UA for PROFINET Remote IO

7.2.2.4 SetSimulation Method

Server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure. If the SimulationEnabled Variable already
OPC-30142 – OPC UA for PROFINET Remote IO

7.2.2.5 SetSimulationValue Method

Server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure
OPC-30142 – OPC UA for PROFINET Remote IO

7.2.3.2 SetMode Method

Server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure. If the Mode Variable
OPC-30142 – OPC UA for PROFINET Remote IO

7.2.3.3 SetManualOutValue Method

Server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure. If the ManualOutValue Variable
OPC-30142 – OPC UA for PROFINET Remote IO

7.2.3.4 SetSimulation Method

Server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure. If the SimulationEnabled Variable already
OPC-30142 – OPC UA for PROFINET Remote IO

7.2.3.5 SetSimulationValue Method

Server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure
OPC-30142 – OPC UA for PROFINET Remote IO

7.2.4.2 SetMode Method

Server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure. If the Mode Variable
OPC-30142 – OPC UA for PROFINET Remote IO

7.2.4.3 SetManualProcessValue Method

Server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure. If the ManualProcessValue Variable
OPC-30142 – OPC UA for PROFINET Remote IO

7.2.4.4 SetSimulation Method

Server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure. If the SimulationEnabled Variable already
OPC-30142 – OPC UA for PROFINET Remote IO

7.2.4.5 SetSimulationValue Method

Server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure
OPC-30142 – OPC UA for PROFINET Remote IO

7.2.5.2 SetMode Method

Server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure. If the Mode Variable
OPC-30142 – OPC UA for PROFINET Remote IO

7.2.5.3 SetManualOutValue Method

Server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure. If the ManualOutValue Variable
OPC-30142 – OPC UA for PROFINET Remote IO

7.2.5.4 SetSimulation Method

Server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure. If the SimulationEnabled Variable already
OPC-30142 – OPC UA for PROFINET Remote IO

7.2.5.5 SetSimulationValue Method

Server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure
OPC-30142 – OPC UA for PROFINET Remote IO

9.2.3 RioPaAnalogProcessValueVariableType

meaningful. This may be the case if the Server is running directly on the Device . The Value of the QualifierValue Variable contains the status information as transmitted in the telegram
OPC-30142 – OPC UA for PROFINET Remote IO

9.2.4 RioFaAnalogProcessValueVariableType

meaningful. This may be the case if the Server is running directly on the Device . The Value of the QualifierValue Variable contains the qualifier bit. The optional Quality component
OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>

7.1.1 SetApplicationTag Method

server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure. The EncoderProfileVersion Variable contains
OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>

7.2.1 PresetControl Method

server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure. The PositionOffset Variable contains
OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>

7.2.2 Ref1LatchStart Method

server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure. The Ref1LatchActive Variable contains True
OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>

7.4.1 LatchStart Method

server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure. The LatchActive Variable contains True
OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>

7.5.1 DeleteLogbook Method

Server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure
OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>

7.5.2 GetFilteredLogbookEntries Method

Server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure
OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>

7.5.3 GetCurrentFaultSituation Method

Server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure
OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>

7.5.4 GetHistoricFaultSituation Method

Server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure
OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>

7.5.5 GetActiveDiagnosis Method

Server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure. The Server might provide
OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>

7.6.1 SetAxisConfig Method

Server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure. If the desired settings
OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>

7.7.1 SetControlConfig Method

Server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure. If the desired settings
OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>

7.8.1 SetSensorConfig Method

Server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure. If the desired settings
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

3.1 Overview

Generic Information Model. This functional Information Model is created using information found in GSDML Device description files, comprising elements of already existing IO Data and Parameter descriptions as well
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

3.2.3 Output Data

Output Data Data, which a Device cyclically receives from the Controller and which controls the Device application or the peripherals
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

3.2.4 Input Data

Input Data Data, which a Device cyclically sends to the Controller
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

3.2.8 Parameter

Parameter Initial setting written to a Device with a parameter record during its start-up phase
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

3.2.10 Data Object

ambient temperature, welding current, and the like) or Parameter which is yielded by a Device . The data value can either be read from a Submodule using the associated PROFINET record
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

3.2.14 Application Relation (AR)

established by the Controller during the start-up phase of the Device using the configuration data created by the engineering tool
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

3.2.15 NameOfStation

name of the communication interface determined by the configuration assigned to the Device by the Controller . One Device can have more than one communication interface
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

4.1 Introduction to PROFINET GSD Generic Model

Model . It can be used also to extend the Information Model of a profile Device by adding vendor specific Data Objects . The standardized way to describe a PROFINET Device ... This primary purpose was extended by enhancing the GSDML with additional information used for Device certification, and for the purpose of this specification elements describing Data Objects were added. This
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

5 Use cases

support the PROFINET Devices which do not have an OPC UA Server on the Device itself and a firmware upgrade for OPC UA support is not an option ("Brownfield
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

6.1 Information Model Creation

Server has access to by PROFINET means: The Server reads Vendor-ID and Device-ID from the Device. With Vendor-ID and Device-ID the Server finds the matching GSDML ... Server reads the "RealIdentificationData" to obtain the IO Data available on the Device . The Server reads the "ARData" record to obtain a list
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

6.2 Application Object

shall be as many GsdGenSubmoduleApplicationType Objects as there are PN Submodules found on the Device . The GsdGenSubmoduleApplicationType Object aggregates the representation of the elements found in the GSDML file
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

6.6 Parameters

Property contains the PROFINET record number used to read the parameter record from the Device . The "Configuration" folder Object references as many GsdGenParameterVariableType Variables as there are separate ... ParameterRecordDataItem" element to read the actual value of the parameter record from the Device . The Server shall then use the attributes of the "Ref" elements describing single
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

7.1.1 SetApplicationTag Method

server is not able to execute the function because an unexpected error occurred. The Device might be temporarily unavailable or unreachable due to network failure. The Lock Object ensures exclusive
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

11.1 Conformance Units

Table 50 - Conformance Units for PROFINET GSD Generic Model Category Title Description Server PNGSDGM Device Server shows the PROFINET Device structure (Module - Submodule - Channel ). Server PNGSDGM Parameter Server provides
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

C.1 RefMeta child elements

Double . The display value shall always be calculated as Value = (value read from Device * Gradient) + Offset. O <Meta> opc:DestinationDataType Name of the OPC UA base data type
OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives

4.1.1 Drive Model

object, the DO is used for the addressing of different axis within a Drive Device , by using the unique DO-ID or the assigned PROFINET module number. Figure 1 shows ... PROFIdrive device model, where the P-Device represents the PROFINET Device hosting the Drive Objects as representatives for a Drive Axis functionality. The Drive Unit is used for internal Device
OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives

4.1.5 Drive Communication Model

standard parameters and vendor specific parameters. This offers the possibility for an edge device to use the PROFIdrive profile as a standardized interface for the access to drive data ... Devices can be represented by an OPC UA Server in an edge or proxy Device (like a PLC cell Controller ) by using a generic mapping based on the PROFIdrive application
OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives

7.1 DriveAxisType

However, as a default, vendors might generate the ApplicationTag string out of the PROFINET device structure given by standard PROFINET configuration data as initial content of the Variable . The generic ... where the < NameOfStation > is the NameOfStation of the PROFINET Drive device and the <axis number> is the PROFINET device module number representing the related PROFIdrive axis
OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives

D.1 Relationship of asset model and functional model

asset information. The Powertrain:PtAssetMotor Object relates to an additional part of the modelled Device using the UAFX:ConnectedTo (see [ OPC 10000-81 ]) ReferenceType . Figure 29 - Connection of asset model
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

4.1.3.2 Device State Machines

Device State Machines The DeviceStateMachine provides a domain-specific view of the device's state. It reflects the condition of the Device itself
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

4.1.3.4 MachineryOperationMode

MachineryOperationMode The MachineryOperationMode indicates the type of Tasks being performed by the Device . It may not be known by the MachineryItem itself and might need to be provided
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

4.1.4 Program and result lifetime of a LADS Device

Program and result lifetime of a LADS Device The lifetime of a program, from uploading a program template to the creation of the result, including additional information about the ActiveProgramType ... Client application using the Start or StartProgram Method or internally by the Device itself based on internal/process reasons. Program Execution: The program execution progresses through various states defined
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

4.2.2 Basics of OPC UA

developers and users. OPC UA Clients can be any consumer of data, from another Device on the network to browser-based thin clients and ERP systems. The full scope
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

5.1.2 Function-based remote control

stop Functions . It includes the remote invocation of Methods to perform Functions on a Device . For example, to start or stop device-specific Functions , open and close covers, as well
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

5.1.3 Program-based remote control

enables a supervising system (e.g., LIMS) to manage and execute programs on a Device as part of a greater workflow. Furthermore, it covers the capability to retrieve the Program Templates ... Device , select a program to be executed, start a program run and monitor the program's progress. The combined program-management and result-management use-cases are the basis
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

5.1.4 Results management

Results management Description A Device performing a specific Function may generate results. These results are typically consumed by one or more applications which may not run on the Device itself ... generating Device exposes the results such that they can be retrieved by the application via OPC UA. The results data include the results themselves, but also metadata such as results
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

5.2.1 Device and fleet management

Device and fleet management Description Devices typically come with a set of properties that identify them for discovery, management, and maintenance purposes. This set of properties is commonly summarized using ... term "nameplate". The information available includes (but it is not limited to) device name, identifiers, serial number, manufacturer, hardware and software versions, and product URI. A nameplate
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

5.2.2 Condition monitoring and maintenance

Condition monitoring and maintenance Description The condition of a Device or a Component of a device is useful for understanding its health status and performance, as well as possible maintenance ... needed. For these reasons, the following information is envisioned to be represented for a Device or Component : Indicators of health status, Indicators of operating time and number of actions performed
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

5.2.3 Location

Location Description The location of a Device is of interest for multiple purposes. These include: Finding a Device position for asset management and service needs Enabling autonomous robots to navigate ... within a lab facility or across multiple lab facilities Sample location tracking (future). A Device location can include different information, including: Geographical Address Organizational Indoor coordinates GPS coordinates. Addressed
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

6 LADS Information Model Overview

have both References (to DeviceSet and Machines ), depending on the environment of the Device . Both References are needed if the LADSDeviceType is used in a production environment
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

7.1.1 LADSDeviceType ObjectType Definition

Units LADS LADSDeviceType Components is a generic set of identifiable sub-components of the Device as mandated by OPC 40001-1. Note: The BrowseName of Components does not follow ... harmonization with the Machinery Specification. FunctionalUnitSet contains the Functional Units of this Device . HierarchicalLocation pro vides the hierarchical location of the LADS Device . The structure within the string may expose
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

7.1.2.1 Overview

Overview The LADSDeviceStateMachineType state machine represents the Device 's current state. It is inspired by the AnalyserDeviceStateMachineType from the Analyzer Devices Specification. The LADSDeviceStateMachine is depicted in Figure 15 Figure ... Sleep StateType 0:HasComponent Object SleepToOperate TransitionType Conformance Units LADS LADSDeviceStateMachineType There are four Device states, as follows: Initialization : The Device is in its initializing sequence and cannot perform
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

7.1.2.2 GotoOperate

GotoOperate The GotoOperate Method is used to set the Device into an operating mode. The signature of this Method is specified below. Table 20 specifies its representation in the AddressSpace
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

7.1.2.3 GotoShutdown

GotoShutdown The GotoShutdown Method is used to shut down the Device . The signature of this Method is specified below. Table 21 specifies its representation in the AddressSpace . Signature GotoShutdown () Table
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

7.1.2.4 GotoSleep

GotoSleep The GotoSleep Method is used to set the Device to Sleep. The signature of this Method is specified below. Table 22 specifies its representation in the AddressSpace . Signature GotoSleep
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

7.1.3 LADSComponentType ObjectType Definition

Conformance Units LADS LADSComponentType Components is a generic set of identifiable subcomponents of the device as mandated by OPC 40001-1. Note: The BrowseName of Components does not follow ... harmonization with the Machinery Specification. Identification provides the properties to identify a device. Recommendations for Identification: • If the Component consists solely of software with no hardware, the SoftwareRevision should
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

7.1.7.1 Overview

Overview The FunctionalUnitStateMachineType represents the state of a FunctionalUnit in a LADS Device . It uses the same StateTypes and TransitionTypes as its parent but specifies the additional Start Method
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

7.1.7.3 StartProgram

Argument[1] 0:PropertyType M DeviceProgramRunId is the internal program identifier assigned by the Device to the program run to generate this result. It is used to identify a Result
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

7.1.10.1 Overview

MaintenanceTaskType shall be used to implement instances of maintenance tasks applicable at both the Device and Component levels. Maintenance tasks include activities such as periodic maintenance, cleaning, calibration, and validation ... Maintenance tasks for a Device shall be grouped under the Maintenance functional group present in the LADSDeviceType . The MaintenanceTaskType is formally defined in Table 51 . Note: All existing Properties
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

7.2.1.1 Overview

Units LADS ProgramManagerType ActiveProgram represents the ongoing operational state of a FunctionalUnit on a Device , providing user-friendly, sequential insight into the progress and context of the currently running program ... also being able to transport transparent metadata for the LADS server itself or possible device drivers. Note: Results must be created between the start (calling Start / StartProgram method
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

7.2.2 ResultType ObjectType Definition

result and the result itself. DeviceProgramRunId is the internal program identifier assigned by the Device to the program run generating this result. It is used to identify a Result object
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

7.2.4 ActiveProgramType ObjectType Definition

FunctionalUnit . It provides context and information about the currently active program on the Device . This allows users to follow the progress of a program run in a standardized fashion ... properties must be communicated through various StatusCodes , depending on the situation: • For a device that has not had a prior run and therefore cannot estimate the runtime, the StatusCode should
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

7.2.6 SupportedPropertyType Definition

Supported Property object is typically an argument name for a variable in the Device . Table 67 - SupportedPropertyType Definition Attribute Value BrowseName SupportedPropertyType IsAbstract False References Node Class BrowseName DataType TypeDefinition
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

7.3.10 MaintenanceSetType Definition

MaintenanceSetType Definition The MaintenanceSetType is a set containing all maintenance tasks for a Device or Component according to the recommendations in OPC UA 10000-110. It is formally defined
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

7.4.2 FunctionType ObjectType Definition

Function . IsEnabled indicates whether the Function can currently be executed on the Device . A Function may be disabled for several reasons including not licensed, missing hardware modules, or missing supplies
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

7.7.1 CoverFunctionType ObjectType Definition

CoverFunctionType is used to control the cover, door, or lid of a Laboratory Device . In addition to the FunctionType , the Operational FunctionalGroup was added for operational Parameters and Methods. Additionally ... CoverStateMachine was added to monitor/control the state of a Device . The CoverFunctionType is formally defined in Table 118 . Table 118 - CoverFunctionType Definition Attribute Value BrowseName CoverFunctionType IsAbstract False References Node
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

7.7.2.1 Overview

CoverStateMachineType is used to control the lid, door, or cover of a LADS Device. One Device may have any arbitrary number of lids, doors, covers and their corresponding CoverFunction ... that can be called in the Opened state to close the cover of the Device . Closed is the state of the LADS Device cover when it is closed. ClosedToError
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

7.7.2.2 Close

Method can be called in the Opened state to close the cover of the Device . The signature of this Method is specified below. Table 122 specifies its representation
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

7.7.2.3 Lock

Method can be called from the Closed state to lock the cover of the Device . The signature of this Method is specified below. Table 123 specifies its representation
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

7.7.2.4 Open

Method can be called from the Closed state to open the cover of the Device . The signature of this Method is specified below. Table 124 specifies its representation
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

7.7.2.5 Reset

Method can be called from the Error state to open the cover of the Device . The signature of this Method is specified below. Table 125 specifies the Arguments and AddressSpace
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

B.1 Building the MachineryItemStateMachine

Building the MachineryItemStateMachine The MachineryItemStateMachine is constructed based on the state of the Device (as represented by the LADSDeviceStateMachineType ), the states of the FunctionalUnits (as represented by the FunctionalUnitStateMachineType ... subsequent columns represent the states of the other state machines. Given that a device can have multiple functional units, their states are aggregated. The rules for this aggregation are also
OPC-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions

8.3 DeviceClass

DeviceClass The DeviceClass Property indicates in which domain or for what purpose a certain Device is used. The Property is optional in OPC UA DI. Here it is overridden
OPC-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions

8.3.2 DeviceManual

DeviceManual The DeviceManual Property allows specifying an address of the user manual for the Device . It may be a pathname in the file system or a URL (Web address
OPC-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions

8.3.6 DeviceRevision

DeviceRevision The DeviceRevision Property provides the overall revision level of the Device
OPC-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions

8.3.7 HardwareRevision

HardwareRevision The HardwareRevision Property provides the revision level of the hardware of the Device
OPC-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions

8.3.8 RevisionCounter

incremental counter indicating the number of times the static data within the Device has been modified
OPC-40400-1 – OPC UA for the Powertrain - Part 1: Asset Management

3.2 OPC UA for Powertrain terms

communication protocols like e.g. CAN, PROFIBUS, PROFINET, vendor specific communication bus) of a device. The communication interface may be an integrated part of a device (e.g. control module , output converter ... Component Constituent part of a device which cannot be physically divided into smaller parts without losing its particular function. IEC 60050-151 [151-11-21] Contactor Element intended to carry
OPC-40400-1 – OPC UA for the Powertrain - Part 1: Asset Management

4.2.2 Basics of OPC UA

developers and users. OPC UA Clients can be any consumer of data from another device on the network to browser based thin clients and ERP systems. The full scope