Subject: Product Outage/Anomaly: Update #9: SNPP Data Delay Rev This is a multi-part message in MIME format. --------------030306090403080403030704 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit ********Update*****#9*****SVL rev 20364 (AOS 17:20Z) was recovered and is being processed nominally. All recoverable SMD data is on the ground and recorded at SVL. DMR remains down. Engineers were unable to flow any recovered SMD data from the previous rev. SMD data from SVL rev 20356 (AOS 03:49Z) and approximately one third of SVL 20357 (AOS 05:30Z) has been positioned and should be able to be flowed and processed by IDPS during the upcoming back orbit.***** *Update*****#8* SVL rev 20363 (AOS 15:37Z) was recovered and is being processed nominally. SMD data missed from SVL rev 20360 (AOS 10:31Z) was recovered and recorded nominally at SVL. DMR remains down. Engineers have manually flowed data from SVL rev 20355 and it has been received at IDPS and is being processed.**** **Update #7 **SVL rev 20362 (AOS 13:54Z) was recovered and is being processed nominally. The remainder of SVL 20357 (AOS 05:30Z) and SVL 20358 (AOS 07:10Z) were recovered and recorded nominally at SVL. DMR remains down. Engineers are still having difficulties manually flowing SMD data that has been recovered and recorded at SVL and continue to troubleshoot. SVL rev 20360 (AOS 10:31Z) should be recovered on the upcoming SVL rev 20363 (AOS 15:37Z). ** Update #6:******Stored mission data (SMD) SVL contact 20360 AOS 1031Z was not recovered due to SMD Pre-processor not being configured. The previous problem with corrupted TLE files has been corrected. SMD data from SVL rev 20355 (AOS 02:09Z) was recovered nominally on the previous support but has not been ingested and processed due to Data Management Recovery (DMR) failure. Engineers are working to manually flow the data from SVL for recovery and processing. SVL rev 20361 AOS 12:12Z was recovered and is being processed nominally. SVL rev 20356 (AOS 03:49Z) and approximately one third of SVL rev 20357 (AOS 05:30Z) was recovered and recorded nominally at SVL. DMR remains down. Engineers will manually flow the data from SVL to NESDIS for processing as soon as possible.** *Update #5: *TLE issue has been corrected and SNPP is now receiving valid telemetry from Svalbard. SNPP Data from Svalbard rev 20359 has been received. Data from Svalbard revs 20355, 20356, 20357 and 20358 are expected to be recovered approximately one rev at a time starting with rev 20355 on this current rev. Full data recovery is expected to take an additional 5 hours.* Update #4: *All SNPP products from SVL rev 20355, 20356, 20357 and 20358 have not been received. Ongoing communication issues with Ground system and S/C are currently being troubleshooted by Engineering. Telemetry was successfully received from S/C via TDRSS support at 0735Z and it appears there are no issue with the S/C itself. Initial troubleshooting indicates issue with TLE. Updates will be provided accordingly. At this time the length of outage for missing data is TBD. * Correction: Update #3:*All SNPP products from SVL revs 20355, 20356, 20357 and 20358 have not been received. Ongoing communication issues with Ground system and S/C are currently being troubleshooted by Engineering. No causes have yet to be discovered. Updates will be provided accordingly. At this time the length of outage is TBD.** * Update #3: *All SNPP products from SVL revs 20355,20356 and 20357 have not been received. Ongoing communication issues with Ground system and S/C are currently being troubleshooted by Engineering. No causes have yet to be discovered. Updates will be provided accordingly. At this time the length of outage is TBD.* Correction: Subject:*Update #2: SNPP Data Delay Rev20355: Issued: October 02, 2015 0636Z * Update #2:* **All SNPP products from SVL revs 20355,20356 and 20357 have not been received. Ongoing communication issues with Ground system and S/C are currently being troubleshooted by Engineering. No causes have yet to be discovered. Updates will be provided accordingly. At this time the length of outage is TBD. * Update #1: *All SNPP products from Svalbard revs 20355 and 20356 will be delayed. Svalbard did not receivevalid telemetry from S/C on two consecutive revs. Engineering is troubleshooting. Cause may be related to scheduling and/or TLE update. Contingent upon valid telemetry from rev 20357, SNPP data will be recovered for missing revs as time allows. The length of time has been extended to 4 hours.* Topic: *SNPP data delay all products. *Date/Time**Issued:***October 02, 2015 1815Z * * *Product(s) or Data Impacted:*All SNPP data products. ** *Date/Time of Initial Impact:*October 02, 2015 0215Z** *Date/Time of Expected End:*October 02, 2015 0500Z** *Length of Outage:*3 Hours* * *Details/Specifics of Change:*No telemetry or data was received at Svalbard during contact 20355. Reasons are unknown, however the data should be recovered on the next support 20356.** **Contact Information for Further Information:* *ESPC Operations at ESPCOperations@noaa.gov and 301-817-3880 ** **Web Site(s) for applicable information:N/A This message was sent byESPC.Notification@noaa.gov . You have been sent this and other notifications because you have opted in to receive it. If for any reason, you wish to unsubscribe, please contact ESPC Help Desk at ESPCOperations@noaa.gov or (301) 817-3880 . Please note: it may take up to two business days to process your unsubscribe request. --------------030306090403080403030704 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Update #9 SVL rev 20364 (AOS 17:20Z) was recovered and is being processed nominally. All recoverable SMD data is on the ground and recorded at SVL.  DMR remains down.
Engineers were unable to flow any recovered SMD data from the previous rev.  SMD  data from SVL rev 20356 (AOS 03:49Z) and approximately one third of SVL 20357 (AOS 05:30Z) has been positioned and should be able to be flowed and processed by IDPS during the upcoming back orbit.

Update #8 SVL rev 20363 (AOS 15:37Z) was recovered and is being processed nominally.  SMD data missed from SVL rev 20360 (AOS 10:31Z) was recovered and recorded nominally at SVL. DMR remains down. Engineers have manually flowed data from SVL rev 20355 and it has been received at IDPS and is being  processed.

Update #7  SVL rev 20362 (AOS 13:54Z)  was recovered and is being processed nominally. The remainder of SVL 20357 (AOS 05:30Z) and SVL 20358 (AOS 07:10Z) were recovered and recorded nominally at SVL.  DMR remains down. Engineers are still having difficulties manually flowing SMD data that has been recovered and recorded at SVL and continue to troubleshoot.  SVL rev 20360  (AOS 10:31Z) should be recovered on the upcoming SVL rev 20363 (< style="">AOS 15:37Z).
Update #6: Stored mission data (SMD) SVL contact 20360 AOS 1031Z was not recovered due to SMD  Pre-processor not being configured. The previous problem with corrupted
 TLE files has been corrected. SMD data from SVL rev 20355 (AOS 02:09Z) was recovered nominally on the previous  support but has not been ingested and processed due to Data Management  Recovery (DMR) failure. Engineers are working to manually flow the data from SVL for recovery and processing.

SVL rev 20361 AOS 12:12Z was recovered and is being processed nominally. SVL rev 20356 (AOS 03:49Z) and approximately one third of SVL rev 20357 (AOS 05:30Z) was recovered and recorded nominally at SVL. DMR remains down. Engineers will manually flow the data from SVL to NESDIS for processing as soon as possible.

Update #5:  TLE issue has been corrected and SNPP is now receiving valid telemetry from Svalbard. SNPP Data from Svalbard rev 20359 has been received. Data from Svalbard revs 20355, 20356, 20357 and 20358 are expected to be recovered approximately one rev at a time starting with rev 20355 on this current rev. Full data recovery is expected to take an additional 5 hours.

Update #4:  All SNPP products from SVL rev 20355, 20356, 20357 and 20358 have not been received. Ongoing communication issues with Ground system and S/C are currently being troubleshooted by Engineering.  Telemetry was successfully received from S/C via TDRSS support at 0735Z and it appears there are no issue with the S/C itself. Initial troubleshooting indicates issue with TLE. Updates will be provided accordingly. At this time the length of outage for missing data is TBD.

Correction: Update #3: All SNPP products from SVL revs 20355, 20356, 20357 and 20358 have not been received.  Ongoing communication issues with Ground system and S/C are currently being troubleshooted by Engineering.  No causes have yet to be discovered.  Updates will be provided accordingly. At this time the length of outage is TBD.

Update #3:  All SNPP products from SVL revs 20355,20356 and 20357 have not been received.  Ongoing communication issues with Ground system and S/C are currently being troubleshooted by Engineering.  No causes have yet to be discovered.  Updates will be provided accordingly. At this time the length of outage is TBD.

Correction: Subject: Update #2: SNPP Data Delay Rev20355: Issued: October 02, 2015 0636Z

Update #2: All SNPP products from SVL revs 20355,20356 and 20357 have not been received.  Ongoing communication issues with Ground system and S/C are currently being troubleshooted by Engineering.  No causes have yet to be discovered.  Updates will be provided accordingly. At this time the length of outage is TBD.

Update #1: All SNPP products from Svalbard revs 20355 and 20356 will be delayed. Svalbard did not receive valid telemetry from S/C on two consecutive revs.  Engineering is troubleshooting.  Cause may be related to scheduling and/or TLE update.  Contingent upon valid telemetry from rev 20357, SNPP data will be recovered for missing revs as  time allows. The length of time has been extended to 4 hours.

Topic:  SNPP data delay all products.

Date/Time Issued:  October 02, 2015  1815Z

Product(s) or Data Impacted: All SNPP data products. 

Date/Time of Initial Impact:  October 02, 2015 0215Z

Date/Time of Expected End:   October 02, 2015 0500Z

Length of Outage:  3 Hours

Details/Specifics of Change:   No telemetry or data was received at Svalbard during contact 20355. Reasons are unknown, however the data should be recovered on the next support 20356.

Contact Information for Further Information: ESPC Operations at ESPCOperations@noaa.gov and 301-817-3880

Web Site(s) for applicable information: N/A

This message was sent byESPC.Notification@noaa.gov. You have been sent this and other notifications because you have opted in to receive it.  If for any reason, you wish to unsubscribe, please contact ESPC Help Desk at ESPCOperations@noaa.gov or (301) 817-3880. Please note: it may take up to two business days to process your unsubscribe request. 

--------------030306090403080403030704--