As with simple control points, you can copy kitControl components to any folder or component needed in the station. (This varies from proxy points—see “Location of proxy points” in the Drivers Guide). This includes under any device’s Points extension (container), or any subfolder underneath.
There are two competing “best practice” philosophies about locating your control logic.
-
Philosophy A, where you should only have proxy points under a device’s Points container. You can add extensions (control, history, and alarm), as needed, to proxy points. However, other components (kitControl components, simple control points, schedules) are located under a central folder not under the station’s Driver architecture—but instead in subfolders under a main “Logic” folder (by convention) created in the root of the station’s Config container.
This method requires many “internal” links between proxy points and kitControl components. It often makes following control logic harder, because you don’t see most links except as “knobs.” In addition, it makes applications much less portable (you can’t copy it all by selecting a single device container, as you might otherwise using philosophy B).
-
Philosophy B, where you add any needed kitControl components, simple control points, and schedules under each device’s Points container (either directly, or in subfolders). This allows you to create more “local” links between the device’s proxy points and other components.
The original intention of philosophy A was to establish a logic “convention” that allows universal support of different application types. However, philosophy B offers more “portability” of each application, allowing easy replication and reuse at a “device level.” In general, use of philosophy B is more common—locate kitControl components where they are needed.