Mark Kowaleski,

1
ICESat Ground System (IGS)Kick-Off
MeetingTechnical Management Implementation
PlansMarch 11, 1999

• Mark Kowaleski,
• ICESat Operations Manager
• 301-286-7816
• mark.kowaleski_at_gsfc.nasa.gov

2
Agenda Purpose

• AGENDA
• ICESat Mission Overview
• IMIT Team IMIT Monthly Meetings
• Short-Term Activities
• Documentation Flow
• Schedules Schedule Drivers
• Baseline Architecture Major Interfaces
• Top-Level Trades in process
• Wrap-up

• PURPOSE
• Get everyone up to speed regarding everything
  that is presently known about the status of the
  ICESat Ground System.
• Document our operating processes (surprise - ISO
  9001).
• Identify short term work to be done.
• Identify overall project activities, drivers,
  etc.
• Give everyone involved a chance to meet everyone
  else.
• Share Information

3
ICESat Mission Profile

• Mission
• July 1, 2001 launch date (depends on rocket)
• 600 km orbit _at_ 94 degree inclination.
• 3 to 5 years to EOL.
• Science - Measure ice sheet height, cloud
  structure, topography.
• Spacecraft - Ball Aerospace RS2000 bus
  derivative.
• Instrument - Geoscience Laser Altimer System
  (GLAS) by Code 924.
• Launch Vehicle - Athena or Delta - TBD.

• SOMO provides
• EPGS operations
• EDOS operations
• Ebnet/NISN operations

• ESDIS provides
• EDOS development
• DAACs
• TBD (this discussion)
• Mission Operations Center
• Flight Operations Team
• Flight Dynamics

• Science Provides
• SCF
• ISIPS
• ISF
• IOT

4
ICESat Information Resources

• ICESAT PROJECT - http//icesat.gsfc.nasa.gov/
• GLAS
• http//glas.gsfc.nasa.gov/
• http//glas.wff.nasa.gov/
• EOSDIS - http//spsosun.gsfc.nasa.gov/New_EOSDIS.h
  tml
• Ball - http//www.ball.com/aerospace/batchp.html
• Science Team - http//ltpwww.gsfc.nasa.gov/eib/gla
  s_sci_team.html

5
IGS Key Points of Contact (the I-TEAM)

• Highly integrated team from many organizations.
• Direct working interface with OM for
  coordination, direction, clarification, problem
  resolution, status reporting.

6
IGS Team Member Responsibilities

• Help identify Requirements and Deliverables.
• Provide Cost Estimates for their respective IGS
  element.
• Provide Element Schedule.
• Attend Working Groups Regular Meetings for
  Mission Planning support.
• Prepare and present Design Status at various
  project reviews.
• Provide ICDs, Systems, Documents, Operational
  Agreements, etc.
• Provide Monthly Status Reporting to IGS
  Operations Manager.

7
IGS Implementation Team (IGSIT) Communications
Project Managers
Science
Instrument
Systems
Spacecraft
Matrixed Support
IGS MIT
8
IMIT Meetings Schedule Purpose

• Meeting Guidelines
• Week 1
• Lasts 1 hour maximum (guaranteed).
• 100 PM each accounting Thursday.
• Week 2 -Working Week
• Week 3
• Lasts as long as necessary.
• 830 AM start time TBD.
• At YOUR location.
• Week 4 - Status Reports due

9
ICESat Project System Engineering Meeting
Schedules
10
Monthly Status Reporting Flow Format

• Contents
• Accomplishments This Month
• Planned Activities Next Month
• Schedule Status
• Implementation Status
• Mission Operations Status
• Top 10 Issues
• Concerns

• Standard Reporting Templates to be provided that
  MUST be used.

11
IGS Short-Term Major Activities

• 1. Establish the IGS Implementation Team, regular
  meetings, Working Groups, etc.
• 2. Finalize the IGS requirements and establish a
  baseline - MORD.
• 3. Develop an integrated end-end IGS
  implementation schedule.
• 4. Develop cost estimates to explore the
  viability of alternate approaches as needed.
• 5. Determine IGS procurement items and
  acquisition funding flow for each element.
• 6. Establish a commitment from each IGS element
  to provide systems and services.
• 7. Develop an integrated IGS Test Plan.
• 8. Provide monthly status directly to 401.6 and
  423.

IGS
12
IGS Reviews Major Scheduled Activities

• Short Term
• IMIT Splinter Working Groups (monthly)
• Project Status Review (PSR) to 423/401.6
  (monthly).
• MOWG II, July, 1999. Others to be scheduled TBD.
• IGS Requirements Peer Review (informal),
  September, 1999.
• Mission Operations Review, planned December, 1999
  but TBD.
• Long Term
• Version 1 ISIPS release, December, 2000
• GLAS IT (assembly) starts February, 2000
• 1st S/C Basic CMD/TEL Compatibility Test
  (GSCT1), April, 2000
• IGS Test Readiness Review, June, 2000.
• Flight Operations Review, April, 2001.
• Launch Readiness Review, June, 2001.

13
ICESat Ground System Schedule Drivers
14
IGS Documentation Flow
15
Supporting Documentation Available to Date

• ICESat Mission Systems Requirements Document
  (MSRD) -Final.
• ICESat Mission Operations Requirements Document
  (MORD) -Draft.
• RF ICD -Near Final.
• Data ICD - Very rough Draft!
• Various Ball Spacecraft documents (TC Hnbk,
  Spacecraft Requirements document, etc.).
• GLAS Instrument Requirements Document - Final.
• Various Science Computing Facility Documents -
  Draft Final.
• GLAS Instrument Description Document - Draft

16
Schedule Development Needs the Following Elements

• Facilities Readiness
• Personnel (when available training)
• Procurement Items (any items needed)
• Documentation (ICDs, Manuals, Operational
  Agreements, Support Plans, Users Guides,
  MOU/MOA, etc.)
• Hardware Software Procurements
• Equipment Installation Check-out
• Software Coding, Installation, and Check-out
• Element Testing
• Ground System Test Readiness
• Simulation Rehearsal Support
• Reviews Status Reports
• DEPENDENCIES (predecessors) for element
  schedules.

17
IGS Master Schedule - Line Item Elements to be
Developed

• Major Reviews Documents
• EPGS WFF
• Ebnet NISN
• EDOS
• SCF ISIPS
• DAAC
• MOC FOT
• FDS
• ISF IOT
• IGS Testing, Simulations, Rehearsals
• LEO Support
• Calibration Validation Support
• Normal Operations

18
IGS Overview (as it stands today - the Baseline)
19
IGS Major Interfaces I2 Chart
20
Organizational Funding Considerations
21
Top-Level IGS Trades in Process

• Trade A Flight Dynamics System
• GSFC FD (GSFC develops and provides LEO support,
  then turns over to MOC/FOT for routine
  operations).
• Ball FD - Ball does it all.
• Trade B S-band RT, PB, and CMD Data Processing
• EPGS (via PTP/SAFS) processes RT PB S-band
  simultaneously
• EPGS processes CMDs from MOC.
• EPGS processes just RT telemetry and forwards
  to MOC.
• EDOS processes PB only and forwards to MOC.
• Trade C X-band Level Zero Data Processing
• EDOS does all X-band processing and strips out
  GPS raw data.
• EPGS does all X-band processing.
• SIPS Extention - all X-band processing.

Most likely decision.
22
Top-Level Trades Overview
23
Wrap-Up

• March Splinter Meetings will focus on the
  following
• Baseline IGS Element Leads.
• IGS Requirements Definition and MORD release.
• IGS Master Schedule Draft.
• Complete Cost Estimate process.
• Baseline IGS Architecture.
• Identify Elements Documentation.
• Status Reporting Templates.
• Continue MOC procurement.
• Next IMIT Meeting on 4/8/99.