Operational data management and monitoring :

1. Operational data management and monitoring : CCM and SCS OD Monitored by the IMS SW, Heater Refuse transition if consecutive errors detection

2. DPS error detection : • IMS errors management • EC32, EC21, DPS_EC21_Sum • DPS_ELT21_Status • ELT entries in Report format IMS Complementary status OD DPS I/F Checks • DMC errors management : • ELT entries • EC32/EC21 counters IIS I/F Checks Image MAS I/F Checks Interferograms - Spectra Processing - Algorithms checks

3. DPS error Management (FOM §1.2.2.2.7 & §1.2.2.7) :

4. IMS Management of DPS medium B and minor errors : Algorithm errors are not handled by the IMS SW, and therefore will never leads to a mode transition Some I/F errors detected at DPS level and reported to the IMS are monitored by the IMS SW (cf PFM/FM2/FM3 models parameters document §3.4) When an anomaly is detected, an ELT entry is performed in the Report format, and this will increase the Anomaly Counter (ENA0011) If there are consecutive occurrences of these anomalies, an automatic transition to Heater/Refuse will be executed (see Functional monitoring #35, DPS_ELT21_Status parameter #168)

5. AR 6614 This case corresponds to the Algorithms error detection (NZPD detection failed on very cool atmosphere views). There is no corrective action triggers by the IMS SW. The ELT were decoded by TEC checks and confirms the origin of the anomaly. Patch is already available to cope with that NZPD determination algorithm AR 6667 This case correspond to an I/F errors detected by the DPS and reported to the IMS. This created an Report format entry with an ELT logging. The error “Err_ODNV_CSQ” was identified and confirmed by TEC checks. This was a single error detection, and therefore this error did not lead to an on-board corrective action. For the future SIOV operation, IASI Team proposes to be called only in case there is a refuse mode transition for these types of anomalies.