340 likes | 780 Views
GOES-R Ground Segment Project NSOF Lunchtime Seminar Tracy Zeiler Assistant Ground Segment Project Manager 17 September 2009. Agenda. Welcome Program Overview Ground Segment Project Functional & Performance Requirements Questions. 2. GOES-R Program Office. Weather sentinel Hurricanes
E N D
GOES-R Ground Segment ProjectNSOF Lunchtime SeminarTracy ZeilerAssistant Ground Segment Project Manager17 September 2009
Agenda Welcome Program Overview Ground Segment Project Functional & Performance Requirements Questions 2
Weather sentinel Hurricanes Severe storms Flash floods Input to weather models, forecasts and warnings Fire and smoke products for air quality monitoring and forecasting and fire fighting Sea surface temperature monitoring for fisheries and climate Winds for aviation Solar imagery for communication satellites, utility companies, and astronaut safety Environmental data collection–buoys, rain gauges… Search and Rescue GOES data shared within the western hemisphere GOES Satellite Mission
GOES-R Objectives Continuity of the Geostationary Environmental Data Observational Mission Modernization and Upgrade Measurement Technology for Temporal and Spatial Improvement Continuation of data and products for: Protection of Life and Property Alerting the Public through Watches/Warnings Preserving and Expanding the Economy Dissemination of Data 5
GOES-R Program GOES-R acquisitions are through an integrated NOAA/NASA program office, led by NOAA, located at Goddard Space Flight Center Roles and responsibilities identified in a NOAA/NASA Memorandum of Understanding (MOU) NASA responsibilities include procurement, management, and execution of the Flight Project, including: Instruments Spacecraft Launch Services NOAA responsibilities include procurement, management, and execution of the Ground Segment Project, including: Mission Management Product Distribution Product Generation Enterprise Management Three sites: NSOF, WCDAS, and RBU
GOES-R Program (Continued) Program System Engineering and Integration (SE&I) is a NASA-led function within the program office with significant NOAA participation Mission Assurance function is a NASA-led function for Program and Projects NOAA is responsible for operation of the deployed system 7
GOES-R Program Status Key program documents signed Level 1 Requirements Documents – June 10, 2007 NOAA/NASA Memorandum of Understanding - June 15, 2007 Spacecraft acquisition July 22. 2009 – Lockheed-Martin Denver, Colorado Ground acquisition May 27, 2009 – Harris Corporation Melbourne, Florida GOES-R Launch Readiness Date September 2015 Information Spacecraft: NNG07193033J, NNG08193033R / http://prod.nais.nasa.gov/cgi-bin/eps/bizops.cgi?gr=D&pin=51 Ground: DG133E-08-RP-0068 http://www.fedbizopps.gov 8
Program Management Structure DOC NOAA Program Management Council NOAA NESDIS AA: Mary Kicza Program Scientist (NOAA) Lead: Steven Goodman GOES-R Program Office System Program Director (SPD): Greg Mandt (NOAA) Deputy SPD: Hal Bloom (NOAA) (reports Mar 3) Assistant SPD: Mark Brumfield (NASA) GSFC Center Management Council STAR Program Systems Engineering Lead: Barbara Pfarr (NASA) Deputy: Bill Mazur (NOAA) Program Control Lead: Stephen Schaeffer (NOAA) Program Mission Assurance Lead: Roman Kilgore (NASA) Contracts Lead: David Runner (NOAA) Kelly Mabe (NOAA) Ground Segment Project Project Manager: Vanessa Griffin (NOAA) Deputy: Robin Pfister (NASA) Assistant: Tracy Zeiler Flight Project Project Manager: Michael Donnelly (NASA) Deputy: Tim Walsh (NOAA) 9
Ground Segment Project Support Contractors The GSP operates as a truly “Badgeless Team.”
GOES-R Acquisition Background • Architecture Studies • 12 Architecture Study contracts awarded November 2003 to evaluate end-to-end architecture approaches • Program Definition and Risk Reduction (PDRR) • September 2005 – April 2007 • 3 firm-fixed-price contracts • Define an end-to-end system architecture • Create detailed concept designs and cost estimates • Conduct system and subsystem level trade studies to identify and mitigate program risk • Prepare and plan for instrument transition to a space segment contractor during the A&O phase
GOES-R Acquisition Background (Continued) • Harris Contract • “Ground Segment Contractor / GS ‘Core’ Contractor” • Awarded May 27, 2009 • $750M • 10 year Period of Performance • Award Fee • Develops, Integrates, Delivers, Installs, and Tests the “Core” Ground Segment (EM, MM, PG, PD) across three Government Sites (NSOF / WCDAS / RBU) in multiple “Releases.” • Maintains, Sustains, and Technology Refreshes the Ground Segment through 2019.
GOES East GOES West Archive and Access (CLASS*; ESPC*) Notional Functional Overview GOES-R Ground Segment Facilities GOES-R Re-broadcast (GRB) GOES-R Ground Segment Functional Elements Mission Management NOAA Satellite Operations Facility (NSOF) Remote Backup (RBU) NOAA Wallops Ground Station (WCDAS) Product Generation Product Distribution User Community -- Enterprise Management -- *CLASS: Comprehensive Large Array-data Stewardship System *ESPC: Environmental Satellite Processing Center 17
Requirements SummaryGround Segment Maintain Health and Safety of the Flight Systems Key Performance Parameters (Priority Products): Provide GRB and Cloud and Moisture Imagery, to users within latency that meets the refresh rate Meet product allocated latencies as identified in the GS F&PS Appendix A (baseline), and Appendix D (increased Mode 4 refresh rates) (Option #1) Overall system availability of 0.99989 (TBR) for KPP products and 0.997 (TBR) for non-KPP products Maximum Time to Restore Service of 4.75 min for MM, KPP PG and PD Maximum Time to Restore Service of 120 min for non-KPP PG and PD 18 18
Requirements SummaryGround Segment (Continued) GS capability to fail over by function without failing over an entire site Failover to RBU within 4.75 min RBU contains Product Generation of KPP products Continuity of legacy capabilities Distribute products to users Provide relay for other NOAA services IT security requirements 19 19 19
Requirements SummaryGround Segment (Continued) Utilization rates Memory utilization less than 50% (TBR) CPU utilization less than 70% (TBR) Development environment for all GS elements (software/databases) I&T environment for operationally-equivalent I&T conditions for all GS elements Modular, Scalable, Extensible, Expandable, and Open Support “Plug and Play” algorithm implementations and other future upgrades Use of existing assets NOAA Satellite Operations Facility (NSOF), Wallops Command and Data Acquisition Station (WCDAS) Permanent data archive provided by the NOAA National Data Centers using the Comprehensive Large Array-data Stewardship System (CLASS) RF Antennas (GFE … both existing, new, and upgraded) NOAA telecommunication assets, including inter-site WANs 20 20
Requirements SummaryGround Segment (Continued) Operational approach consistent with existing operational processes and procedures, and staff Staffing level equal to or less than today’s level Use of standards, including: Consultative Committee for Space Data Systems (CCSDS) standards International Standards Organization (ISO) and Federal Geographic Data Committee (FGDC) metadata standards Use of common end-product format standards to ease user transition NetCDF4 (all) McIDAS (terrestrial) FITS (space) 21
Space-Ground communications TLM & CMD Unique Payload Services (HRIT/EMWIN*, DCS, SARSAT) GOES Rebroadcast (GRB) Generate Spacecraft Commands, and Process Spacecraft Telemetry 5-day local storage of raw data for anomaly resolution Life-of-the-mission storage of engineering telemetry and event messages Generate and manage command loads 7 days in advance Process raw (instrument) data to Level 0 Perform mission scheduling and planning Perform Orbit & Attitude determination and maneuver planning Requirements SummaryMission Management 22
Conduct Product Monitoring (L1b) Routine instrument calibration support Image Navigation and Registration (INR) monitoring Telemetry data archive, engineering analysis system, and remote access to telemetry Integrate Flight Software (FSW) Development Environment Spacecraft and Instrument Simulators Antennas and front-end RF equipment Requirements SummaryMission Management (Continued) 23 23
Process Level 0 data to calibrated and navigated products (Level 1b) Assemble GRB data set Assemble Emulated GVAR (eGVAR) data sets Receive ancillary data files Process Level 1b data to Level 2/2+ Product Sets 1 and 2 (baseline), and Product Sets 3 and 4 (Option #2) Send Level 1b, Level 2/2+ products and associated data to PD Provide a portable simulation capability for GRB data to test user ingest and data handling systems (GRB Simulator) Maintain calibration database for the life-of-the-mission Monitor Product quality for Level 2/2+ Requirements SummaryProduct Generation 24
Distribute GRB to the MM for Rebroadcast Distribute data and products (L1b, L2/2+) to operational users Translate products into appropriate formats Provide a GOES-R User Access Point for products (“GAS”) Deliver to 7-day store for User Access (“GAS”) Distribute selected data, products (L0, L1b, L2/L2+), ancillary data, algorithms, and associated metadata to CLASS for long-term archive Distribute emulated GOES Variable Format (eGVAR) to GOES-N ground segment for RF transmission through GOES-N series satellites Requirements SummaryProduct Distribution 25
Monitor and Report status on the entire GS All GS components (hardware and software) Networks Communication links and antenna operations Infrastructure Receive status from GS Elements Provide real time textual and graphical display of system performance and status Monitor and maintain statistics on network status, system resources, utilization, etc. Requirements SummaryEnterprise Management 26
Identify anomalous conditions, correlate failures, initiate diagnostic process Monitor and report primary and backup site functions, and the interfaces to external systems Provide event status, tracking, and investigation Monitor and report enterprise IT security Control segment elements via Ground Directives from any site E.g., Antenna System Requirements SummaryEnterprise Management (Continued) 27 27
Deliverables Three Releases have been established to support various program review, test, and preparation activities. Release MM (GRD – 28 months) includes Mission Management command and telemetry capabilities, installed and tested at the NSOF site. Release 1 (GRD – 14 months) includes Mission Management, Enterprise Management, Product Generation for Product Set 1, and Product Distribution capabilities, installed, integrated, and tested across the three operational sites. Release 2 (GRD – 8 months) includes all the capabilities of Release 1, plus Product Set 2. 29 29
Government Furnished Property (GFP) Summary • Facilities at NSOF, WCDAS, and RBU • Antennas (NSOF) • Inter-site communications circuits • Algorithms • Test Data • Simulators • T&C Database • Flight Software Development Environment • Documentation, e.g., • Spacecraft T&C Handbook • Instrument Calibration Databooks • Security • Common Anomaly Tracking System (CATS) Database
Transition to Operations Support for GOES-R GS transition to operations Operations and support documentation Handbooks Manuals Procedures Training for operators and maintenance personnel Input to Government user support activities Operations support including GOES-S Pre-launch and Launch activities Support Post GOES-R Launch Testing September 2015 – June 2016 31
Transition to Operations(Continued) Ensure Severity I and II DRs are closed prior to acceptance Sustainment support Hardware Software Logistics A GS Acceptance Review will review Ground Segment readiness for final acceptance by the Government July 2016 32 32
Summary GOES-R Ground Segment is critical to the success of the GOES-R Program and the achievement of NOAA environmental monitoring objectives. Additionally, GOES-R will be the subject of considerable review both within the administration and in Congress. A strong working relationship between the GSP and the Operating Units (OSO & OSDPD) is critical to GOES-R success. 34