1

SMOV Proposal ProcessInitial Submission through Flight

George Chapman

Merle Reinhart

Tony Roman

February 21, 2001

2

Overview

• Proposal Implementation Team (PIT)

• The PIT Process

• PIT Schedule

• The Proposal – Phase 2 Tips

• Beyond the PIT

3

Proposal Implementation Team (PIT)

• A group of experts that meet to develop and implement proposals fast, safely and efficiently

• Compressed timeline for SMOV benefits from a focused group

• Try to accomplish via one or two meetings per proposal (more if necessary)

4

The PIT Process • Proposal Submission

– best attempt at converting Activity Summary into a proposal

– no later than deadline (earlier is better)

• Proposal Processing

• PIT meeting #1– proposal reviewed in detail– modifications identified – special implementation needs identified

5

The PIT Process (cont’d)

• Modifications & Resubmission– no later than deadline (earlier is better)

• Proposal Processing• PIT meeting #2 (if needed)

– verify expected modifications– final review of proposal and ancillary products– approval to process to flight ready state

• If necessary, PIT meeting #3

6

The PIT Schedule

SubmissionDeadline PIT Meeting #1

ResubmissionDeadline PIT Meeting #2

10+working

days5 Working Days

5 Working Days

7

The Proposal – Phase 2 Tips• Use Web version of proposal for any changes

– http://www.stsci.edu/public/propinfo.html

• Good, Detailed Descriptions• Include Related Activity Summary Ids• Include prerequisite Proposal Ids• Default for SMOV is SCHED 100%• Absolute Time constraints should be used only for

visits with alternate targets• SMOV3B is to be tagged as Cycle 10

8

The Proposal – Phase 2 tips (cont’d)Contingency Planning

• Each Phase 2 should allow for a launch shift of at least plus or minus 1 month

• Use the ON HOLD special requirement on conditional visits

9

The Proposal – Phase 2 Tips (cont’d)Expedited Data Flow

• If data is needed in a timeline fashion for analysis, then this needs to be explicitly mentioned in the visit comments.– Data to the PI within 12 hours of visit completion.

– Data to the PI within 20 hours of visit completion.

– Data to the PI within 32 hours of visit completion.

• These numbers assume ~8 hours of processing after the data is downlinked from the spacecraft until the data is available to the PI.

10

The Expedited DataflowSSR

PACOR-IN

PACOR-OUT

OPUS-OUT

PI

PACOR-OUT

OPUS-OUT OPUS-OUT

STARVIEW

PACOR-OUT

RealTime<<1 hr.

Quicklook<2 hrs.

Production<~4 hrs.

<1 hr. <1 hr. <1 hr.

<~1 hr.

<1 hr.

OPUS-IN OPUS-IN OPUS-IN

DADS-IN

<1 hr. ~1 hr. ~3 hrs.

FTP FTP FTP

Spacecraft

PACOR

OPUS

DADS

PACOR-IN

ScienceRealTime

Science Dump <1hr. to <~12 hrs.

CCS-IN

CCS-OUT

Engineering Dump<1 hr. to <~12 hrs.

~2-4 hrs.

SE

OPUS-IN

24 -48 hrs.

Extraction fromWarehouse

CCS

11

Beyond the PIT

• Process proposal through flight ready • Schedule first 4-weeks of SMOV and provide

products for review before launch– First 4-weeks flight ready by launch minus eight weeks

– Representative calendars are built assuming a nominal launch date and without normal science visits (SMOV only)

– Provides feedback into the overall SMOV Timeline

– Provides necessary input for the LRP

12

Beyond the PIT (cont’d)

• After launch, the SMOV and Operational databases are merged and the LRP rebuilt

• Visits are set flight ready during week T-5

• Appropriate flight calendar requirements are defined during week T-4

• Flight calendar building begins at week T-3

• Execution