Subclause 9.2 defines a generic pattern to expose and configure components. It defines the following principles:

• A configurable Object shall contain a folder called SupportedTypes that references the list of Types available for configuring components using Organizes References. Sub-folders can be used for further structuring of the set. The names of these sub-folders are vendor specific.
• The configured instances shall be components of the configurable Object.

Figure 54 illustrates these principles.

Figure 54 – Configurable component pattern

In some cases the SupportedTypes folder on the instance may be different to the one on the Type and may contain only a subset. It may be for example that only one instance of each Type can be configured. In this case the list of supported Types will shrink with each configured component.

This ObjectType implements the configurable component pattern and is used when an Object or an instance declaration needs nothing but configuration capability. Figure 55 illustrates the ConfigurableObjectType. It is formally defined in Table 105. Concrete examples are in Clauses 9.3 and 9.4.

Figure 55 – ConfigurableObjectType

Table 105 – ConfigurableObjectType definition

Attribute	Value
BrowseName	ConfigurableObjectType
IsAbstract	False
References	NodeClass	BrowseName	DataType	TypeDefinition	Other
Subtype of the BaseObjectType defined in OPC 10000-5
0:HasComponent	Object	SupportedTypes		0:FolderType	M
0:HasComponent	Object	<ObjectIdentifier>		0:BaseObjectType	OP
Conformance Units
DI Information Model

The SupportedTypes folder is used to maintain the set of (subtypes of) BaseObjectTypes that can be instantiated in this configurable Object (the course of action to instantiate components is outside the scope of this specification).

The configured instances shall be components of the ConfigurableObject.