Table 20 shows the ResponseSPDUDataType Structure. The Prefix “Out” is interpreted from the SafetyProvider’s point of view and is used in a consistent manner to the parameters of the Method ReadSafetyData (see 6.2.2.3).

Table 20 – ResponseSPDUDataType structure

Name	Type	Description
ResponseSPDUDataType	structure
OutFlags	OutFlagsType	See corresponding Method argument in Table 7.
OutSPDU_ID_1	UInt32	See corresponding Method argument in Table 7.
OutSPDU_ID_2	UInt32	See corresponding Method argument in Table 7.
OutSPDU_ID_3	UInt32	See corresponding Method argument in Table 7.
OutSafetyConsumerID	UInt32	See corresponding Method argument in Table 7.
OutMonitoringNumber	UInt32	See corresponding Method argument in Table 7.
OutCRC	UInt32	See corresponding Method argument in Table 7.

[RQ6.7] To define the concrete DataType for the ResponseSPDU (which specifies the concrete DataTypes for SafetyData and NonSafetyData, respectively), proceed as follows: (1) Derive a concrete DataType from the abstract ResponseSPDUDataType. (2) In doing so, add the following fields to the Structure in the given order: (a) First, field OutSafetyData with the concrete Structure DataType for the SafetyData (see 7.2.1.5). (b) Second, field NonSafetyData with the concrete Structure DataType for the NonSafetyData (or a placeholder DataType, see requirement RQ6.8).

[RQ6.8] To avoid possible problems with empty Structures, the dummy Structure NonSafetyDataPlaceholder shall be used as DataType for OutNonSafetyData when no NonSafetyData is used. The DataType Node defining this Structure has a fixed NodeID and contains a single Boolean.

The representation in the AddressSpace of the ResponseSPDUDataType is defined in Table  21.

Table  21 – ResponseSPDUDataType definition

Attributes	Value
BrowseName	ResponseSPDUDataType
IsAbstract	True
References	NodeClass	BrowseName	DataType	TypeDefinition	ModellingRule
Subtype of Structure defined in OPC 10000-3
Conformance units
SafetyPDUs