Background 1 of 2

1. 1

2. 2 Background1 of 2 Currently, NOAA�s ability to dump POES satellite GAC/LAC data exists only at Fairbanks and Wallops (CDAs) We encounter 2-3 blind orbits/day on each satellite with the CDAs The number of satellites currently being operated can compound the data latency issues CDAs experience delays in transferring some satellite data due to limitations on the DOMSAT transfer bandwidth Improvements are pending in this area. We wanted the ability to minimize/eliminate data latency

3. 3 Background 2 of 2 Primary satellites (NOAA-17, 18) have anomalies that require instrument data from the secondary satellites for product development: N16 HIRS vs. N18 HIRS N15 AMSU vs. N17 AMSU Overall constellation continuity N15, N16, N17 gyro 3 issues N15 antenna issues N15, N16, N17 tape recorder issue EUMETSAT�s Svalbard ground station (SVL) is handling the blind orbits for NOAA-18 Approached by IPO � who offered the Svalbard ground station for POES use Conducted a feasibility study and developed a proof of concept in the Spring 2006 Users have a clear interest in getting the data from NOAA-17�s blind orbit 2-3 orbits earlier

4. 4 Objectives for Using NPOESS Svalbard (NSV) for POES Decrease/Eliminate Data latency Eliminates blind orbits which minimizes the delays in data recovery Provide continuous coverage when there are outages (planned and unplanned) at the CDA stations Develop an economical solution(s) Utilize existing resources

5. 5 Proposed Enhancements for OSO to Address Data Latency on the POES program Usage of NPOESS Svalbard (NSV) Antenna for GAC dumps only No commanding Increased bandwidth of the DOMSAT link to SOCC

6. 6 Planned Usage of NSV1 of 2 Usage for NOAA-17 and NOAA-15 GAC dumps NOAA-17 and 15 blind orbit GACS would be transferred, on average, 150 minutes sooner than is currently possible Currently 2-3 orbits of data are dumped when the satellite comes out the CDA blind Integrated using current IJPS resources and configuration Testing efforts benefited both IJPS and NSV

7. 7 DOMSAT Enhancements Upgrade the bandwidth from 1.33 Mbps to 2.66 Mbps Expected in Spring 2007 Substantially improves transfers between CDAs to SOCC but does not eliminate blind orbits

8. 8 Benefits of using NSV1 of 2 Retrieving blind orbit data from the NOAA-17, NOAA-15 satellites at NSV should never interfere with NOAA-18 blind orbit retrieval from IJPS Svalbard (SVL) due to orbit plane differentials. NOAA-18 blind orbits typically 0100-0500z NOAA-17 blind orbits typically 0930-1330z NOAA-15 blind orbits typically 0600-1000z Note: Should an operational overlap occur on IJPS resources (interfaces into SOCC), priority would be on NOAA-18 (IJPS spacecraft), N17, then N15 according to the POES Scheduling algorithms. These algorithms (POES Scheduling System) have already been modified to schedule resources at NSV on a non-interference basis with IJPS SVL.

9. 9 Benefits of Using NSV2 of 2 Timeliness of data recovery would approach 100% Currently, data latency (data processed less than 3 hours from observation) for orbital GACs on the operational Satellites can never be better than ~83% (average 2.5 blind orbits IPO antenna at Svalbard is NOAA controlled property

10. 10 NSV Dataflow

11. 11 Proposed Concept of Operations Data recorded as normal POES would have priority over Coriolis once operational SOCC will not perform health and safety prior to NSV SOCC conveys spacecraft anomalies through NSV or TNOC Minimal support would be required by operational staff �Blind orbits� dumped scheduled at NSV through POES Scheduling System Data is transferred to SOCC after LOS as scheduled, no call needed Test indicate a throughput of ~15mins to receive data NOAA-18 contacts have priority on transfers resolved through POES Scheduling System During test period data would be dumped over the CDA only if noisy or not received at NSV. Must avoid repeated transfers to IPD Preserve an opportunity to playback data over CDAs on N-17 is managed through scheduling JORP under development

12. 12 Issues1 of 2 POES will have priority over Coriolis once operational until NPP launched� NPP will out prioritize at NSV POES when it launches this will affect the POES data flow because the IPO�s NSV antenna currently available (being paid for by NESDIS) allows for any of the KLMNN' satellites, using any of the operational HRPT downlink frequencies, whereas IJPS actually requires a special STX4 configuration with AIP data for every pass, i.e., operational reliability decreases and data latency increases. NPP's launch date has slipped to NET FY09, so overall impact and mitigation efforts can occur now. ��

13. 13 Issues 2 of 2 NSOF move prevents further end-to-end testing at this time Need to develop procedure(s) to prevent multi-transfers to products group of the same data Blind orbit data would no longer be transferred over the DOMSAT link. AFWA, Univ. of Wisc, Monterey, etc. would need to get data directly from IPD, i.e., the same process/path they will have to use when N18 starts dumping at IJPS SVL.

14. 14 Remaining Implementation Items and Dates Verify changes in the POES Scheduling system to incorporate NSV Generation and distribution of satellite recorder schedules Redumps at the CDA if needed Generation and distribution of integrated LEO-T schedule Demonstrate KSATs ability to use POES Scheduling System products Perform ETE: November- February with N-15 Perform ETE: January-March with NOAA-17, 15 Train Operational crew: December � March Regression test at NSOF: December

15. 15 Conclusion Testing and analysis to date have shown that NSV is a viable, inexpensive solution to resolving SOCC�s current data latency issues We are using existing NESDIS resources If no major issues encountered during ETE test then we should be operational in April 2007