Ability to fall-back on abstract alternative to a faulty function input

• API for declaring function inputs and outputs as “universal” values that can be replaced by other values
  • Ability to mark values as faulty/disabled or recovered
  • Ability to mark entire components as faulty/disabled or recovered
  • !! (MG, 2) Ability to define an accuracy for values, in engineering units (units need testing)
• Components capable of finding a sensor reading to be "faulty" – probably should demonstrate this three ways:
  • An example sensor component that determines its sensor is bad, for a very obvious reason
  • –HS (BK, 2) An example sensor component that determines its sensor is bad, for a non-obvious reason
  • –MM (BK, 30) CBIT (Built In Test) that determines sensors are bad, via heuristics, comparison with other readings, or other means.
• Components capable of providing an alternate sensor reading.
  • An example derivation component that estimates a the value based on other readings
• Algorithm within the state table to provide the "best" value when an abstract value is requested.
• Logging capability to indicate which is “best” value.