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

• A configurable Objectshall contain a folder called SupportedTypesthat references the list of Typesavailable 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 54illustrates these principles.

Figure 54– Configurable component pattern

In some cases the SupportedTypesfolder on the instance may be different to the one on the Typeand may contain only a subset. It may be for example that only one instance of each Typecan be configured. In this case the list of supported Typeswill shrink with each configured component.

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

Figure 55– ConfigurableObjectType

Table 89– ConfigurableObjectType definition

Attribute	Value
BrowseName	ConfigurableObjectType
IsAbstract	False
References	NodeClass	BrowseName	DataType	TypeDefinition	ModellingRule
Subtype of the BaseObjectTypedefined in OPC 10000-5
HasComponent	Object	SupportedTypes		FolderType	Mandatory
HasComponent	Object	<ObjectIdentifier>		BaseObjectType	OptionalPlaceholder
Conformance Units
DI Information Model

The SupportedTypesfolder is used to maintain the set of (subtypes of) BaseObjectTypesthat 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.