# Presentation: 376489

## Life Cycle:Mission Responsibilities

**SEEDS: Strategic Evolution of ESE Data Systems**

**U.S. Department of the Interior**
**U.S. Geological Survey**

**Contractor for the USGS**
**at the EROS Data Center**

**Life Cycle:****Mission Responsibilities**
- Jon ChristophersonRaytheon at the USGS EROS Data Center18 June 2002

## Premise

- Routine Operations data is not the only data to archive
- Supporting data is also important
- Engineering design data
- Pre-launch data
- OIVP data
- On-Orbit Calibration data over mission life

## Why?

- Supporting data helps put Operational Data in context
- Satellite/Instrument design
- Vital for monitoring satellite/instrument performance
- And therefore is _*vital*_ to ensuring the Quality of the Operational Data Archive and _*should be maintained*_

## Engineering and Build Data

- Industry standard practice is to control and keep all designs, drawings, build history, test data
- Engineering data vital to pre-flight and OIVP
- Remains critical throughout mission
- But less visible and (hopefully) used less often
- Only to a small group, not majority of users

## Engineering & Build Data (cont.)

- Typically maintained by instrument/satellite manufacturer and/or NASA, but.....
- Given to engineering and launch teams, who go away
- Private companies sometimes go out of business
- Some material is poorly described – difficult to understand or use later

## Engineering & Build Data (cont.)

- Commercial/Gov’t Partnerships add new concerns
- Designs may be proprietary – who gets access?
- Lengthy contractual relationships req’d
- International Partnerships
- Country A built satellite, Country B gets data – who gets support data?
- ITAR concerns

## Pre-Launch and OIV Test Data

- Gathered during Pre-launch and OIV testing
- Often not in standard formats, contents
- Gathered from incomplete systems, engineering H/W
- Processed with non-standard software
- Difficult to archive alongside operational data
- Not valuable without good Content Description
- Instrument condition, test environment, other special characteristics

## Examples and Life Stories

- Landsat 7
- Heritage Design
- Engineering data generated in 1970s, 1980s still used today for routine operations
- Santa Barbara Remote Sensing (SBRS) and Lockheed-Martin (LMMS) under contract for engineering support
- Pre-launch and OIV data still used in analyses for calibration of recent data

## Examples and Life Stories (cont.)

- Landsats 4 & 5
- Landsat 4 launched 1982, decommissioned in 2001
- Landsat 5 launched in 1984 – still operating!
- Instrument aging, engineering documentation has been invaluable in maintaining operations
- Pre-launch and OIV test data still exists but is poorly documented
- Afraid to throw it away!

## A Case in Point!

**A Case in Point!**

## Recommended Best Practices

- Engage Operations & Archive in the earliest stages of instrument/satellite design and build
- Helps to keep Operations/Archiving in mind of builders
- Note: Science is often involved in design/build but not Ops/Archive is not!
- One complete set of Engineering Drawings and As-Built records to be archived for life of mission
- Formatting, access concerns
- Future computing likely to make task easier

## Recommended Best Practices (cont.)

- Test Data:
- Pertinent test data shall be fully described and archived
- “Pertinent” defined as potentially useful for understanding instrument/satellite performance or anomalies
- “Fully Described” includes describing inst/sat configuration, test environment, data formatting
- Engineering to assist in establishing these criteria
- Special tools/techniques req’d to analyze data these must be described also

## Recommended Best Practices (cont.)

- Pre-Launch Cal/Val data to be archived
- Must be fully described and annotated
- “Primitive” data may be kept with engineering data
- Relatively few users
- Operational Cal/Val data to be archived
- Metadata describing conditions and nature of cal/val data, analyses, applications also archived
- Somewhat larger number of users