Point-level composite
The following image shows a proxy NumericPoint representing a space temperature value that has two extensions:
an alarm extension (OutOfRangeAlarmExt)
a history extension (NumericInterval)
Figure 1. Property sheet of proxy point with two extensions 
In this example, when another system-related BooleanWritable (representing the system fan) has a false (Off) status, it is desired that this temperature point be:
disabled from alarming, and
disabled from continued history collection
To achieve these disable functions, you must link the controlling source fan out to a slot of each extension (visible in point’s wire sheet view, but not in the parent wire sheet for the point itself). Furthermore, other kitControl objects needed. Without making a composite, the necessary objects and links may appear.
Notice that when looking at the proxy NumericPoint in the wire sheet of its parent folder, it is not apparent that this point has linked extensions.
By making a composite of the NumericPoint (acting as the container for both the extensions plus the additional kitControl objects) you can simplify reuse and clarify available links. The following image shows the now-composited NumericWritable linked to the controlling BooleanWritable, and the wire sheet view of the NumericWritable that contains the needed kitControl objects.
In this example, the exposed input slots in the composite were renamed from In to almInhib and histStop respectively, to clarify what each does. When looking at the Composite Editor for this example NumericPoint, it appears as given below.
