The Control OSID manages control systems. A system is
f Devices whose
Controllers are the control points.
Input mechanisms to
Device represents some piece of
visible equipment in a system. Example
are joysticks, yokes, and control panels.
Controller is an
manages a specific responder in a system such as a
model railroad gate, an airplane rudder, or the volume of
a stereo. The management of a
includes on/off, variable amount values, or a set of
Controller is a black box. The
Control OSID does not describe or manage system responders
or how a Controller performs its tasks.
Input is an
Device and a
Controller. A yoke may have several
Input for push-pull that
Controller for the elevator,
Input for turning that commands the
Controller for the ailerons, and another
Input that commands the
for enabling and disabling auto-pilot.
Setting captures fixed setting values
for a sound system volume may have a variable
Setting for LOUD and another
Setting for SOFT.
Settings are the basic building blocks for
Scen e is a set of
Setting is a value for a
apply values across a bunch of
Executing a movie theater
Scene may set the
Controllers to dim values, close the
curtains, and set the sound system vilume.
used to perform actions in response to a value or state
change in a
have two parts. One part of the
is the event listening criteria (fan turned on,
light changed brightness). The second part of a
Trigger is the execution that is to be performed
when the event criteria is true. The
may encapsulate more complex event criteria.
Trigger is when the motion
Controller is turned "on," the
Trigger executes a
Scene that turns on the porch light.
Triggers may execute
Settings directly. This is the
simpler approach but does not allow for other rules or
conditionals not expressable by a set of critera.
Triggers may also execute
Actions and ActionGroups
ActionGroups are a set of
OsidRules to be executed. Built-in rules execute
OsidRules may reference other actions or
behaviors not directly described in the
Settings, Scenes, and Actions
Setting is a single state or value
for a specific
Controller used to build
Scenes but may also be directly executed by
Scenes are a set of
used to set the state or values of multiple
Controllers simultaneously and provide reusability
of clusters of
ActionGroups may be used with
Triggers to achieve the same effect as a
Setting. The difference between a set of
Actions and a
Setting are the
presence of rules in the
rules may determine which
Actions within an
ActionGroup apply at tha time within a
context. As such, each evaluation across an
ActionGroup may result in different sets of
whose complete set of
known up front and may be thought of as a multicast group.
Triggers , and
ActionGroups may be organized into
The Control OSID includes a Control Rules OSID for
managing rules amd a Control Batch OSID for managing
ActionGroups in bulk.