The FunctionalEntityCapabilitiesType extends the FolderType defined in OPC 10000-5. It shall be restricted to hold only Variables that reflect the capabilities of the FunctionalEntity.

The FunctionalEntityCapabilitiesType is formally defined in Table 58.

Table 58 – FunctionalEntityCapabilitiesType definition

Attribute	Value
BrowseName	3:FunctionalEntityCapabilitiesType
IsAbstract	False
References	NodeClass	BrowseName	DataType	TypeDefinition	Other
Subtype of the 0:FolderType defined in OPC 10000-5
3:HasCapability	Variable	3:<Capability>	0:BaseDataType	0:BaseDataVariableType	OP
3:HasCapability	Variable	3:FeedbackSignalRequired	0:Boolean	0:BaseDataVariableType	O
ConformanceUnits
UAFX FunctionalEntity Base

<Capability> - is a placeholder to indicate that additional capabilities may be added by this document or by a companion specification at any time. These capabilities shall include a description.

If the optional FeedbackSignalRequired is present and set to TRUE, the FunctionalEntity requires a feedback signal for all Connections. A feedback signal is represented by the reception of either data or a heartbeat. The following connection types (see 5.5.1) support feedback: bidirectional, unidirectional with heartbeat, unidirectional (if configured as Subscriber), and autonomous subscriber. If FeedbackSignalRequired is missing or set to FALSE, the connection types unidirectional (if configured as Publisher) and autonomous publisher are also supported.