Profiles and ConformanceUnits – OPC UA for Weihenstephan Standards

10 Profiles and ConformanceUnits

10.1 Conformance Units

This chapter defines the corresponding Conformance Units for the OPC UA Information Model for OPC UA for Weihenstephan Standards.

Table 28 – Conformance Units for OPC UA for Weihenstephan Standards

Category	Title	Description
Server	Weihenstephan WS Machine	Supports the base functionality defined in OPC UA for Weihenstephan Standards Information Model. This includes all mandatory properties, the Object Identification and at least one of the optional FunctionalGroups.
Server	Weihenstephan Writable WS DataPoints	Supports write access to all variables of the WS DataPoints, which are defined as writing according to the Weihenstephan Standards.
Server	Weihenstephan WSBaseObjectType	The server supports the WS BaseObjectType.
Server	Weihenstephan WSBaseStateMachineType	The server supports the BaseStateMachine. This include the list of AvailableStates and AvailableTransitions. It also includes all mandatory states and the mandatory sub-statemachines. The methods which are defined in PackML (See OPC 30050) do not have to be offered.
Server	Weihenstephan WSAnalogUnitType	The server supports the WSAnalogUnitType.
Server	Weihenstephan Engineering Units	For each data point of the instance WSAnalogUnitType an engineering unit is defined. If an engineering unit is not defined in UNECE Recommendations N° 20, the values in the EUInformation DataType must be filled in. See OPC 10000-8.
Server	Weihenstephan Corresponding WS TagNumbers	If the WSTagNumber is used in one of the following datatypes it must be ensured that the value is empty or belongs to the corresponding WS DataPoint: WSBaseObjectType, WSBaseStateMachineType and WSAnalogUnitType. Initial values like 0 are invalid values, MaxUInt16 (65535) might be a valid value.
Server	Weihenstephan WSAlarmType	Supports the base WSAlarm type, and the mandatory component of the type.
Server	Weihenstephan WSAlarmCode	The WSAlarmCode is of type Integer and is exchanged between server and client. The mapping of the WSAlarmCode to the corresponding error message is done on the client side. The mapping table is exchanged outside the Weihenstephan Standards. Ensure that a WSAlarmCode is mapped to the correct error message on both server and client side.
Client	Weihenstephan WSAlarmCode	The WSAlarmCode is of type Integer and is exchanged between server and client. The mapping of the WSAlarmCode to the corresponding error message is done on the client side. The mapping table is exchanged outside the Weihenstephan Standards. Ensure that a WSAlarmCode is mapped to the correct error message on both server and client side.
Server	Weihenstephan WSAlarmMessage	The optional component WSAlarmMessage sends the error message directly to the client as localizedText. The descriptions of the alarm message from WSAlarmMessage and the mapped message from WSAlarmCode are identical.
Client	Weihenstephan WSAlarmMessage	The optional component WSAlarmMessage sends the error message directly to the client as localizedText. The descriptions of the alarm message from WSAlarmMessage and the mapped message from WSAlarmCode are identical.
Server	Weihenstephan WSWarningType	Supports the WSWarning type, and the mandatory component of the type.
Server	Weihenstephan WSWarningCode	The WSWarningCode is of type Integer and is exchanged between server and client. The mapping of the WSWarningCode to the corresponding warning message is done on the client side. The mapping table is exchanged outside the Weihenstephan Standards. Ensure that a WSWarningCode is mapped to the correct warning message on both server and client side.
Client	Weihenstephan WSWarningCode	The WSWarningCode is of type Integer and is exchanged between server and client. The mapping of the WSWarningCode to the corresponding warning message is done on the client side. The mapping table is exchanged outside the Weihenstephan Standards. Ensure that a WSWarningCode is mapped to the correct warning message on both server and client side.
Server	Weihenstephan WSWarningMessage	The optional component WSWarningMessage sends the warning message directly to the client as localizedText. The descriptions of the warning message from WSWarningMessage and the mapped message from WSWarningCode are identical.
Client	Weihenstephan WSWarningMessage	The optional component WSWarningMessage sends the warning message directly to the client as localizedText. The descriptions of the warning message from WSWarningMessage and the mapped message from WSWarningCode are identical.
Server	Weihenstephan WSExecuteStateMachineType	The server supports the ExecuteStateMachine. This include the list of AvailableStates and AvailableTransitions. It also includes all mandatory states. The certification will include a list of all states and transitions supported by the StateMachine. This include the mandatory Sub-statemachines. All methods defined in the 4: PackMLExecuteStateMachineType (See OPC 30050) are not needed in this companien specification.
Server	Weihenstephan WSHeldStateMachineType	The server supports the HeldStateMachine. This include the list of AvailableStates and AvailableTransitions. It also includes all mandatory states. The certification will include a list of all states and transitions supported by the StateMachine
Server	Weihenstephan WSSuspendedStateMachineType	The server supports the SuspendedStateMachine. This include the list of AvailableStates and AvailableTransitions. It also includes all mandatory states. The certification will include a list of all states and transitions supported by the StateMachine.

10.2 Profiles

10.2.1 Profile list

Table 29 lists all Profiles defined in this document and defines their URIs.

Table 29 – Profile URIs forOPC UA for Weihenstephan Standards

Profile	URI
Weihenstephan Base Functionality Server Profile	http://opcfoundation.org/UA-Profile/Weihenstephan/Server/BaseFunctionality
Weihenstephan Base Functionality Client Profile	http://opcfoundation.org/UA-Profile/Weihenstephan/Client/BaseFunctionality
Weihenstephan Base Functionality Server Facet	http://opcfoundation.org/UA-Profile/Weihenstephan/Server/BaseFunctionalityFacet
Weihenstephan Base Functionality Client Facet	http://opcfoundation.org/UA-Profile/Weihenstephan/Client/BaseFunctionalityFacet

10.2.2 Server Facets

10.2.2.1 Overview

The following sections specify the Facets available for Servers that implement the OPC UA for Weihenstephan Standards companion specification. Each section defines and describes a Facet or Profile.

10.2.2.2 Weihenstephan Base Functionality Server Profile

Table 30 Table defines a profile that all OPC servers should support in order to meet the minimum requirements of the Weihenstephan Standards according to the present companion specification.

Table 30 – Weihenstephan Base Functionality Server Profile

Group	Conformance Unit / Profile Title	Mandatory / Optional
Profile	0:Embedded 2017 UA Server Profile http://opcfoundation.org/UA-Profile/Server/EmbeddedUA2017
Profile	0:Data Access Server Facet http://opcfoundation.org/UA-Profile/Server/DataAccess
Profile	Weihenstephan Base Functionality Server Facet

10.2.2.3 Weihenstephan Base Functionality Server Facet

Table 31 defines a Facet that all OPC servers should support in order to meet the minimum requirements of the Weihenstephan Standards according to the present companion specification.

10.2.3 Client Facets

10.2.3.1 Overview

The following sections specify the Facets available for Clients that implement the OPC UA for Weihenstephan Standards companion specification. Each section defines and describes a Facet or Profile.

10.2.3.2 Weihenstephan Base Functionality Client Profile

Table 30 defines a profile that all OPC client should support in order to meet the minimum requirements of the Weihenstephan Standards according to the present companion specification.

Table 32 – Weihenstephan Base Functionality Client Profile

Group	Conformance Unit / Profile Title	Mandatory / Optional
Profile	0:Core 2017 Client Facet http://opcfoundation.org/UA-Profile/Client/Core2017
Profile	0:AddressSpace Lookup Client Facet http://opcfoundation.org/UA-Profile/Client/AddressSpaceLookup
Profile	0:DataAccess Client Facet http://opcfoundation.org/UA-Profile/Client/DataAccess
Data Access	0:Data Access Client AnalogUnitType	M
Profile	0:DataChange Subscriber Client Facet http://opcfoundation.org/UA-Profile/Client/DataChangeSubscriber
Profile	Weihenstephan Base Functionality Client Facet

10.2.3.3 Weihenstephan Base Functionality Client Facet

Table 31 defines a Facet that all OPC servers should support in order to meet the minimum requirements of the Weihenstephan Standards according to the present companion specification.