USE OF BEST PRACTICES DURING OPERATIONS DEVELOPMENT FOR AIM

1
USE OF BEST PRACTICES DURING OPERATIONS
DEVELOPMENT FOR AIM

• David C. Welch
• Honeywell Technology Solutions Incorporated
• University of Colorado
• Laboratory for Atmospheric and Space Physics
• Boulder, Colorado
• SpaceOps 2004
• 17-21 May 2004
• Montreal, Canada

2
Presentation Overview

• AIM Background
• SORCE Heritage
• AIAA SOSTC Best Practices
• Operations Concept Document
• Requirements Development
• Automation
• IT Support
• Conclusions

3
AIM Background

• Orbital LEOStar-2 Platform
• SOFIE Instrument - SDL
• CIPS/CDE Instruments - LASP
• Ground Stations at Poker Flat, Alaska Svalbard,
  Norway
• 2.0 Mbps down, 2.0 kbps up
• Space Network use for LEOP
• 4 kbps return, 2.0 kbps forward
• 4.0 Gbits onboard storage
• 50 hours before data overwrite
• Mission Operations Center at LASP
• Science Ops Centers at LASP and GATS

AIM will resolve why Polar Mesospheric Clouds
form and why they vary.
4
SORCE Heritage

• Orbital LEOStar-2 Platform
• Instruments - LASP
• SolSTice (A/B)
• TIM
• SIM (A/B)
• XPS
• Ground Stations at Wallops Island, Virginia and
  Santiago, Chile
• Also - Hartebeesthoek, S. Africa for LEOP
• 1.5 Mbps down, 2.0 kbps up
• Space Network use for LEOP and contingencies
• 4 kbps return, 2.0 kbps forward
• 1.0 Gbits onboard storage
• 27 hours before data overwrite
• MOC/SOC at LASP

SORCE is part of NASAs Earth Observing System
and provides 2 of 24 key variables required by
the EOS science program 1) total solar
irradiance with an absolute accuracy of 100 parts
per million and a relative accuracy of less than
10 ppm per year 2) solar spectral irradiance in
wavelengths from the near-infrared to the
extreme ultraviolet.
5
Use of SORCE Lessons Learned

• AIM development profile is modeled after SORCE
• So far, 44 Lessons Learned from SORCE have been
  provided
• Additional Staffing during Observatory IT (2 Ops
  TCs)
• Dedicated TDRS Planner for Launch and Early Orbit
  Phase
• External Control of RFICD Slowed Down Progress
  (Started Earlier)
• Schedule Accountability on Items with
  Interdependencies
• On-board Data Storage Capacity (36 hrs min/48
  preferred -gt 50 hrs)
• Number of Spacecraft Engineers Available at MOC
  for Launch
• S/C Instrument Packet Decommutated Differently
  (Standardized)
• Incomplete Listing of Important Telemetry Points
  to Monitor/Trend
• Lessons Learned Incorporated into Operations
  Concept Document so they are not lost or forgotten

6
Use of LASP Best Practices

• Best Practices from all of LASPs Operational
  Missions applied
• SME
• Student Training Model
• STRV-1A/1B
• Analysis of COTS Automation Tools
• SNOE
• LASP MOC Automations Prototype
• Student Involvement
• QuikSCAT
• MOC Automation
• Configuration Management
• Multi-mission Operations
• ICESat
• Interactive Science Planning with remote SOC
• SORCE
• Many similarities to AIM

7
AIAA SOSTC Best Practices

• Search for Best Practices began in Fall 1999,
  with result being that not very many available to
  the general community
• Forum for development of set of Best Practices to
  be shared was initiated at the SOSTC Annual
  Workshop on Reducing Space Mission Costs in April
  2000
• Modeled after NASA GSFCs Satellite Operations
  Risk Assessment Team research into SOHO
  operations problem
• Lessons Learned Applied

http//www.aiaa.org/tc/sos/Ops_Best_Practices.PDF
8
Operations Concept Document

• Based on GSFC Work done in 1995
• Past experiences on other Small Explorer missions
  factored in
• SAMPEX
• FAST
• SWAS
• WIRE
• TRACE
• Integrated into the Requirements Generation
  Process
• Concept has been utilized on many proposals, but
  AIM is first full utilization as a means of
  capturing and explaining requirements
• Operations Concept is a Living Document which
  will become the baseline for Mission Readiness
  Testing as well as the development of Flight
  Operations Procedures and Handbooks

9
Operations Development System Engineering

• Requirements
• Mission Requirements levied on Ground System
  derived from OCD Outline
• Level 3 Ground Requirements derived directly from
  OCD
• Network Requirements Document will be derived
  from OCD, SORCE Detailed Mission Requirements,
  and Lessons Learned from SORCE Mission Readiness
  Testing
• Schedules and Milestones
• Work Breakdown Structure and Schedule for
  Operations Support and Development created
• Schedule Milestones aid in managing development
  and support and in detecting problems earlier
• Interdependencies List created at the Project
  Level to track items which are generated by one
  group, but needed by another to maintain schedule

10
Automation

• Based on QuikSCAT ICESat single mission
  implementations
• OASIS-CC
• Real-time Monitoring
• Alarm Paging
• TQSM Handshaking and Data Transfer
• TQSM
• Real-time System Monitoring
• Post-pass Data Transfer Monitoring
• Alarm Paging
• Alarm Management
• TQSM tool enhancements being added for
  multi-mission use
• AIM utilization being worked into multi-mission
  implementation
• Automated passes not used for SORCE, but will be
  for AIM

11
IT Support

• Participation from operations personnel during
  entire Integration and Test Phase
• Operations has appointed an IT Manager
• 2 Operators at Orbital (includes DB maintenance
  proc development)
• Engineering Model/Flight Software Development
• Bus IT
• Observatory IT
• Launch Site Preparations and Launch support
• Early Orbit support at MOC
• Operations Support for LASP Instrument IT
• Command and Telemetry Database Development
• Functional Procedure Development
• Functional Testing Support
• Database and procedure development support to SDL
• Use of OASIS-CC, OASIS-PS MOC Analysis Tools
  throughout IT

12
Conclusions

• Experience from many past successful missions is
  factoring into the development of the AIM Mission
  Operations
• Use of these practices have enabled operations to
  be involved in the Mission System design from the
  outset
• Operations Involvement in the Early Design Phase
  of AIM has provided large cost savings and should
  provide for improved operational capabilities
• Involvement of operations in IT and use of the
  Ops Concept Document, as well as implementation
  of many other Best Practices, will greatly
  benefit the AIM Project