The OPC UA FX Information Model defines well-known instances (see Table 252 and Table 253) that are used to group OPC UA FX Object instances. OPC UA FX Object instances may also exist in other Folders or in other groupings. Figure 64 provides an overview of these instances.

Figure 64 – FxRoot overview/example

The following instance shall exist in all Servers that expose an OPC UA FX Information Model. It is formally defined in Table 252.

Table 252 – FxRoot definition

Attribute	Value
BrowseName	2:FxRoot
References	NodeClass	BrowseName	DataType	TypeDefinition
Organized by the Objects Folder defined in OPC UA Part 5
HasTypeDefinition	ObjectType	0:FolderType
ConformanceUnits
UAFX FxRoot

The FxRoot is the standard entry point for all instances related to OPC UA FX. It may contain multiple AutomationComponents that include Assets and FunctionalEntities. It may also contain, at most, one ConnectionManager.

NOTE   AutomationComponents are part of the Server, i.e. the Server exposes the AutomationComponents as instances. In the world of a physical Controller, there would only be one instance of an AutomationComponent. In the world of digital twins, there might very well be multiple instances that represent each of the digitalised AutomationComponents – all running on one Server.

The following instance shall exist in all Servers that expose a ConnectionManager. It is formally defined in Table 253

Table 253 – ConnectionManager definition

Attribute	Value
BrowseName	4:ConnectionManager
References	NodeClass	BrowseName	DataType	TypeDefinition
Organized by the FxRoot defined in 12.2
HasTypeDefinition	ObjectType	4:ConnectionManagerType
ConformanceUnits
UAFX ConnectionManager Base

The ConnectionManager is the well-known object that represents a ConnectionManager. A Server that supports a ConnectionManager will always have only one instance of this Node.