====== Alarms in OMG Specifications ======
It is important that we have a common set and definition of alarm level/severities throughout the Space Domain Task Force specifications. This page tracks information about the related information in each specification.

  * [[https://www.astrouxds.com/platforms/astro-for-r2c2/|Astro UXDS Guidance for R2C2]]
  * [[https://issues.omg.org/issues/?jql=labels%20%3D%20alarm-alignment|All Alignment Issues]]

[[https://www.astrouxds.com/patterns/status-system/#status-colors|AstroUX Status Colors]] - now updated to mention all XTCE alarm levels!

Migrating to four alarm levels (Normal, Warning, Distress, Critical) was approved by the Space DTF on 4/26/2024.

====== C2MS ======
  * Table 8-9: Log message SEVERITY of 0=Debug, 1=Nominal, 2=Medium, 3=High, 4=Critical
    * Change to Standby/DEBUG, Normal/INFO, Warning/WARN, Distress/ERROR, Critical/FATAL [[https://issues.omg.org/browse/C2MS11-222|C2MS11-222]]
  * Table 8-11: RED/YEL/NORM
    * Deprecate RED/YEL/NORM. Add: NORMAL,WARNING,DISTRESS,CRITICAL [[https://issues.omg.org/browse/C2MS11-222|C2MS11-222]]
  * Table 8-26: RESPONSE-STATUS enum 1=Ack, 2=Working/keep alive, 3=Successful completion, 4=Failed completion, 5=Invalid Request, 6=Final Response
  * Table 8-53: DEVICE.n.STATUS enum 0=Debug, 1=Normal/Green, 2=Yellow, 3=Orange, 4=Red
    * Rename to 0=Standby, 1=Normal, 2=Warning, 3=Distress, 4=Critical [[https://issues.omg.org/browse/C2MS11-222|C2MS11-222]]
  * Table 8-58: COMPONENT-STATUS enum 0=Debug, 1=Normal/Green, 2=Yellow, 3=Orange, 4=Red
    * Rename to 0=Standby, 1=Normal, 2=Warning, 3=Distress, 4=Critical [[https://issues.omg.org/browse/C2MS11-222|C2MS11-222]]
  * Table 8-84: MNEMONIC.n.STATUS enum 1=Valid, 2=Valid/No data, 3=Invalid 
  * Table 8-104: Attributes: RED-HIGH, RED-LOW, YELLOW-HIGH, YELLOW-LOW
    * Deprecate the individual items above.  Add new MNEMONIC.n.SAMPLE.STATUS with enum of: 0=Unavailable, 1=Normal, 2=Warning, 3=Distress, 4=Critical [[https://issues.omg.org/browse/C2MS11-222|C2MS11-222]]
    * And SAMPLE..QUALITY 0=Good, 1=Questionable
  * Table 8-109: Attributes: RED-HIGH, RED-LOW, YELLOW-HIGH, YELLOW-LOW
    * Deprecate the individual items above.  Add new MNEMONIC.n.SAMPLE.STATUS with enum of: 0=Unavailable, 1=Normal, 2=Warning, 3=Distress, 4=Critical [[https://issues.omg.org/browse/C2MS11-222|C2MS11-222]]
    * And SAMPLE..QUALITY 0=Good, 1=Questionable
  * Table 8-126: Attributes: RED-HIGH, RED-LOW, YELLOW-HIGH, YELLOW-LOW
    * Deprecate the individual items above.  Add new MNEMONIC.n.SAMPLE.STATUS with enum of: 0=Unavailable, 1=Normal, 2=Warning, 3=Distress, 4=Critical [[https://issues.omg.org/browse/C2MS11-222|C2MS11-222]]
    * And SAMPLE..QUALITY 0=Good, 1=Questionable
  * Table 8-136: XTCE-STATUS enum Astro defines colors for: 2=Invalid, 9=Complete, 10=Failed
  * Table 8-141: CMD-ECHO-RESULT: NOTC=Not compared, GOOD=Good compare, MISC=Miscompare, TOUT=Timed out waiting for echo, UEX=Unexpected echo received
  * Table 8-160: PRIORITY enum 1=Nominal, 2=Medium, 3=High
    * Change to 1=Low [[https://issues.omg.org/browse/C2MS11-222|C2MS11-222]]
  * Table 8-171: DATA-QUALITY: RAW, VALIDATED, DEGRADED

====== CSRM ======
Alarms are not defined in this specification

====== GEMS ======
Alarms are not defined in this specification

====== SOLM ======
Based on review, there is no common mechanism in the SOLM specification for alarm/limit levels being defined.

Alarms are not defined in this specification (no mention of alarm, warning, yellow, etc.)
Limits are mentioned in <Parameter>_<Attribute> / Restriction of SOLM Python mapping, page 59

====== XTCE ======
  * Alarm levels of: normal, watch, warning, distress, critical, and severe
    * In XTCE 1.3: Deprecate watch and severe [[https://issues.omg.org/browse/XTCE13-142|XTCE13-142]]
  * Significance levels of: normal, vital, critical, forbidden, user1, user2
  * None is similar to "in limits" or "normal"

====== XUSP ======
  * Alarm levels of: normal, warning, and severe (XUSP 1.0 CSV)
    * For XUSP 1.1: Add distress as new option [[https://issues.omg.org/browse/XUSP11-41|XUSP11-41]]
    * For XUSP 1.1: Add support for critical [[https://issues.omg.org/browse/XUSP11-44|XUSP11-44]]
    * For XUSP 1.1: Deprecate severe [[https://issues.omg.org/browse/XUSP11-45|XUSP11-45]]
  * Significance levels of: none, critical, severe (XUSP 1.0 PDF)
    * None is not a type in XTCE, nor is severe.
    * For XUSP 1.1/XTCE 1.2: Change to normal, critical, forbidden [[https://issues.omg.org/browse/XUSP11-43|XUSP11-43]]

====== Future Considerations =======
The following scenarios are typically marked differently by a C2 system though have no representation within AstroUX at this time.

  * How to represent stale?  Magenta hourglass?
  * Unreasonable (outside valid range)? ??
  * Invalid (decoding error)? ??