E13

1
E-1-3

• NPOESS Program and Spacecraft

2
Nunn-McCurdy Impacts to A-DCS on NPOESS

• NPOESS is dual-funded by NOAA and DOD
• Nunn-McCurdy law (applies to DOD) required
  re-certification of NPOESS program to Congress
• This took place June 6th, 2006
• Recertified program differs in some respects from
  prior program
• - NPOESS returning to the original concept of
  two orbit planes
• - Two (sequential) satellites for each plane
• - NPOESS no longer populating the 2130
  ascending (930 descending) orbit
• - 2130 orbit did not include A-DCS, so no
  A-DCS impact due to fewer orbit planes
• - New launch dates (see below)

3
Nunn-McCurdy Impacts to A-DCS on NPOESS (cont.)

• Initial order for two satellites,
• - option for additional two to be exercised in
  2010
• Planned launch dates C1 2013
• C2 2016
• C3 2018
• C4 2020
• Spacecraft need dates for A-DCS instrument
  approximately 15 months prior to launch
• Actual spacecraft need dates for A-DCS will be
  developed during NGST replan
• Program runs through 2026

4
NPOESS Contacts June 2006

• IPO Payload Hal Bloom hal.bloom_at_noaa.gov
• Jim Morris James.W.Morris_at_noaa.gov
• IPO A-DCS Mike Cummings
• Michael.Cummings_at_noaa.gov
• NGST A-DCS Massih Hamidi massih.hamidi_at_ngc.com
• NGST SI Tim Gresham tim.gresham_at_ngc.com
• ______
• Massih Hamidi replaced Greg Barber in this
  capacity
• SISystems Integration (responsible for
  ground interface control documents)
• Tim Gresham replaced Alexa Davis in this
  capacity

5
Ground Interfaces

• A-DCS data and telemetry interface via NESDIS,
  not directly from NGST/NPOESS
• mission data, raw and converted housekeeping
  telemetry
• For other, direct, interfaces between CNES or CLS
  and NPOESS, NGST would like to utilize a
  web-based system
• command requests, mission notices, ephemeris

6
Ground Interfaces (cont.)

• Raw and engineering unit housekeeping telemetry
  to NESDIS  "wrapped" in HDF5.  NESDIS
  responsible for forwarding that data in a
  mutually agreeable format, time frame, etc. 
• Same as 1 for the A-DCS "mission data
• NGST will provide an emergency telephone contact
  number to the control center
• Normal interactions to be through External Web
  Server, to which you will have access
• Command requests need to be entered into that Web
  Server, from a single authorized source

7
Ground Interfaces (cont.)

• 6) Peripheral information, comes from the
  External Web Server
• - examples ephemeris, predicted ephemeris for
  orbit-adjustment maneuver, command history
  during pass, notice of events which could (or
  did) affect the ability of A-DCS to provide
  useful data, etc.
• 7) Events which also resulted in turning off
  A-DCS (such as red out-of-limit condition, or a
  general Spacecraft Safe Mode) would ALSO be
  communicated to you "directly" , meaning phone,
  FAX, email, or whatever means is found mutually
  satisfactory.
• 8) Some degree of telemetry analysis available
  via requests to the Web Server.
• 9) NGST plans to send you ALL mission notices,
  not just the ones that apply to you, and you
  would need to decide if they apply to you or not. 

8
Ground Interface Schedule

• 17 May - NGST Deliver Accommodation Presentation
  to A-DCS (complete)
• 24 May - NGST Deliver preliminary ground ICD to
  A-DCS (complete)
• 9 June - A-DCS provide comments on Accommodation
  Presentation to NGST
• 16 June - NGST incorporate appropriate
  presentation comments into ICDs, Deliver updated
  ICD to A-DCS
• 27 June - A-DCS provide comments on ICDs to NGST
• Week of 10 July - ICD Stakeholder Review -
  discuss any unresolved issues
• 27 July - NGST Complete ICD comment adjudication
  and update ICDs for NGST Engineering Review Board
  process
• 18 August - Begin NGST ERB Process
• 29 September - Complete NGST ERB Process