Effectors

Action Models partition common logical effector settings into sets of attributes. Individual effectors may be separately enabled or disabled by Monitoring and Control components. However, when jointly enabled, all effectors must be consistent (i.e., all must be performing and/or displaying the same action.)

Design Steps

Construct per-device Effector components, that perform actions in accord with these attributes in either of two ways:

Advice.

User interfaces or instruments that display Action model attributes in a manner useful to pilots.

Transduction.

Devices that transform action representations into direct manipulation of mechanical components.

Structure effector Update protocols with respect to Connected action models in a manner guaranteeing Consistency across multiple devices that must reflect the same actions.

Mechanical effectors may fail or change state in unpredictable ways. Also, pilots may be able to intervene and override mechanical controls at any time. Most effector devices possess feedback capabilities to deal with such events. Thus, nearly every effector component contains special kinds of Sensors and even stripped-down Models to represent internal state, serving as data sources to Monitors and other ACS components, normally resulting in interactions with high-priority pilot displays, Action Functions, alternative Guidance Modes, and effectors to deal with failure. Support these feedback and status operations in the same fashion as Sensors.