Search

94 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-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/