International EOS

1. NPOESS community refers to Direct Readout systems as Field Terminals While Field Terminals make up a segment of NPOESS we will be developing only software. Prior to release of RFP for NPOESS the Integrated Program Office and DOC and DoD agreed that NPOESS should provide only software and the respective agencies would build there own terminals to meet their unique environmental requirements. NPOESS community refers to Direct Readout systems as Field Terminals While Field Terminals make up a segment of NPOESS we will be developing only software. Prior to release of RFP for NPOESS the Integrated Program Office and DOC and DoD agreed that NPOESS should provide only software and the respective agencies would build there own terminals to meet their unique environmental requirements.

2. Direct Readout Lab Roadmap to NPP and Beyond Evolution of satellites , signal processing, technologies developed and available to Users and Vendors Looking for technologies needed by Users for NPOESS era Evolution of satellites , signal processing, technologies developed and available to Users and Vendors Looking for technologies needed by Users for NPOESS era

3. Data Volume Evolution Note increase of data rates and storage growth that will be needed in future Highlight data latency improvement Data access for military with EOS, NPP and NPOESS Note increase of data rates and storage growth that will be needed in future Highlight data latency improvement Data access for military with EOS, NPP and NPOESS

4. RF Communications Subsystem Overview

5. Overview Spacecraft Iso-view

6. HRD RF Downlink Characteristics ..

7. HRD RF Downlink CharacteristicsCoding/Randomization

8. HRD EIRP vs. Nadir Angle

9. HRD Downlink Spectral Mask

10. HRD Long-Term Orbit-Averaged Availability

11. LRD RF Downlink Characteristics ..

12. LRD RF Downlink CharacteristicsCoding/Randomization

13. LRD EIRP vs. Nadir Angle

14. LRD Downlink Spectral Mask

15. LRD Long-Term Orbit-Averaged Availability

16. NPOESS / NPP Sensor Manifest Reminder of payload manifest VIIRS largest contributor of data @ 10.5Mbps with Rice Lossless compression at 1.8:1 Sensors produce raw data for EDR production. Reminder of payload manifest VIIRS largest contributor of data @ 10.5Mbps with Rice Lossless compression at 1.8:1 Sensors produce raw data for EDR production.

17. LRD Data Content Balances Performance and Provides Flexibility 2 points on this chart � 1) shows each sensor configuration by spacecraft Nodal crossing time 2) Programmable LRD Link means that we can change data in link by APID, for example we could have more imagery over land and more sounding data over oceans � configurations will be determined by procedures to be defined during next few years well before launch.2 points on this chart � 1) shows each sensor configuration by spacecraft Nodal crossing time 2) Programmable LRD Link means that we can change data in link by APID, for example we could have more imagery over land and more sounding data over oceans � configurations will be determined by procedures to be defined during next few years well before launch.

18. Field Terminal Ancillary Data Approach Dynamic ancillary data contained within LRD and HRD downlinks to meet specified performance levels Data for six pressure levels from the NWP forecast model Temperature Humidity Surface pressure Standard pressure levels Wind speed, wind direction Precipitable water For SESS EDR production Effective sunspot number and global geomagnetic Kp NPOESS mission support data server, accessible via internet Read ChartRead Chart

19. Ancillary Data DownlinkGraphical Representations Explain uplink and downlink conops � 2 orbit wide swaths of ancillary dataExplain uplink and downlink conops � 2 orbit wide swaths of ancillary data

21. NPOESS High Rate Data (HRD)Environmental Data Records (EDRs) Greyed out EDRs not in HRDGreyed out EDRs not in HRD

22. NPOESS Low Rate Data (LRD)Environmental Data Records (EDRs) Greyed out EDRs not in LRD 8 High Priority EDRs listed (P) Predecessor EDR needed to produce some of 8 High Priority EDRs � you get them for free Bandwidth allows other EDRs to be provided as well Greyed out EDRs not in LRD 8 High Priority EDRs listed (P) Predecessor EDR needed to produce some of 8 High Priority EDRs � you get them for free Bandwidth allows other EDRs to be provided as well

23. Field Terminal Data Flow Read chartRead chart

24. Direct Readout Interfaces

25. Field Terminal Data Processor Element Software Design Open Systems Group standards compliance at interfaces minimizes configurations Programmable LRD downlink favors 8 Priority EDRs Onboard VIIRS data compression rates by APID for LRD Flexible ancillary data approach Dynamic ancillary data via satellite downlink NPOESS Mission Support Data Server via Internet access Read Chart Programmability could be used to change data packets for different EDR production in regional areas e.g., Antarctica JPEG-2000 base lining 6:1 Introduce ancillary data concept � will describe design later.Read Chart Programmability could be used to change data packets for different EDR production in regional areas e.g., Antarctica JPEG-2000 base lining 6:1 Introduce ancillary data concept � will describe design later.

26. FTS EDR Performance HRD EDR performance 99% of performance attributes meet or exceed performance thresholds Latency requirements achievable with current COTS multiple CPU workstations Designed to recognize missing channels and ancillary data Lossless RICE compression on VIIRS LRD EDR performance 0.8 km resolution imagery and programmable downlink Produces 8 high priority EDRs at or near LRD objective levels Produces 15 lower priority EDRs and required predecessor EDRs Designed to recognize missing channels and ancillary data Lossless and Lossy JPEG2000 compression on selected APIDs Read chart Read chart

27. FTS Latency Analysis for Stress-case FTS Latency Requirement: max latency is ? 15 minutes. SYS013235 & SYS013230 - Field Terminal software, when installed on NPOESS-specified HRD field terminal hardware, shall produce the Imagery EDR in less than or equal to 2 minutes and all other EDRs as specified in Appendix E in less than or equal to 15 minutes after receipt of data from the FT Signal Processing Subsystem. A large number of factors impact FTS processing. Terrain - Land or ocean Day versus Night sensor characteristics Weather - Cloudy, Partial Cloudy, Clear Satellite Orbits & FTS emplacement (Latitudes) FTS Hardware: CPUs (3 GHz NPP era) Story is what is driving processing power needed to meet requirements Story is what is driving processing power needed to meet requirements

28. FTS Simulation (e.g. 45N/00):1 day 15 Passes with 3 NPOESS S/C

29. Overlapping S/C contacts don�t occur due to spacecraft orbital phasing. Smallest gap of 10.2 minutes has minimal impact to FTS latency. Above 60N there is a large increase in contacts and EDRs. Back-to-back S/C Contacts

30. Orbital Position Defines Dynamic Scene Content in Sensor Data

31. Land/Ocean, Day/Night, and Clear/Cloudy Data Land has process loads comparable to ocean. Day data is 4x night data processing. Day-only algorithms are: ACO/OCC Vegetation Index Surface Types Aerosols (large load) Surface Albedo (large load) Clear Data is most stressing  Clear-only algorithms are: ACO/OCC Vegetation Index Land/Ice Surface & Sea Surface Temp Surface Types Aerosols (large load) Surface Albedo (large load) CMIS/CrIS AVT/MP (large load) Used Land, Day and 100% Clear data Read ChartRead Chart

32. FTS Latency StatusAll EDRs & Imagery EDR Comparison of 2.6 GHz and 5.0 GHz HRD Results

33. NPOESS Field Terminal Segment Schedule Note that I�ve added the Field Terminal Tech Spec (FTTS) and the Decryption Spec (FTDS) to the ICD CDR version, this is within scope and will result in a better product. I haven�t changed FTS FAT 2.2 and 2.3, the whole NPOESS build schedule 2.1, 2.2, and 2.3 is in flux. I�ve based the NPP Launch on the best estimate that we have at the moment, that of a 16-18 month slip, I took the 18, if you want we can change to the 16 month point. Maureen has a number of options for how to progress that she is going to be briefing at the F2F, but one of her main assumptions is an 18 month slip in NPP launch and NPP Ground Readiness at the Launch -8 point. All three of her options have Launch -6 but her assumption was Launch -8. I put NPP HRD demo at NLT May 2009, but I believe that we can beat that by several months. The way the schedule stacks now, we should be able to complete 2.1 well before launch, so should only have to check out, and fix problems to prepare for the demo. I�d like to take the conservative road for right now and then beat the schedule by 6-9 months. Note that I�ve added the Field Terminal Tech Spec (FTTS) and the Decryption Spec (FTDS) to the ICD CDR version, this is within scope and will result in a better product. I haven�t changed FTS FAT 2.2 and 2.3, the whole NPOESS build schedule 2.1, 2.2, and 2.3 is in flux. I�ve based the NPP Launch on the best estimate that we have at the moment, that of a 16-18 month slip, I took the 18, if you want we can change to the 16 month point. Maureen has a number of options for how to progress that she is going to be briefing at the F2F, but one of her main assumptions is an 18 month slip in NPP launch and NPP Ground Readiness at the Launch -8 point. All three of her options have Launch -6 but her assumption was Launch -8. I put NPP HRD demo at NLT May 2009, but I believe that we can beat that by several months. The way the schedule stacks now, we should be able to complete 2.1 well before launch, so should only have to check out, and fix problems to prepare for the demo. I�d like to take the conservative road for right now and then beat the schedule by 6-9 months.

34. NPOESS Direct Readout Mission Points of Contact Direct Readout Mission POCs: John Overton: (301) 713-4747 Bill Munley: (301) 713-4782 Joe Mulligan: (301) 713-4803 John van de Wouw: (310) 812-0800 NPOESS websites Http://www.npoess.noaa.Gov Http://npoesslib.ipo.noaa.Gov/ (electronic bulletin board) Read ChartRead Chart