Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.stsci.edu/ops/stories/13.text Дата изменения: Wed Jul 14 15:17:57 1999 Дата индексирования: Sun Apr 10 14:27:34 2016 Кодировка: Поисковые слова: http astrokuban.info astrokuban

Here's how we did proposal implementation before PRESTO!

Procedure for Proposal PMDB Flight Readiness Review (PFRR)
and Preliminary (test) Scheduling in SPSS
28-JUN-1990

OVERVIEW:

Following approval of a given proposal by the User Support Branch
(USB), that proposal will be Transform'ed by Science Planning Branch
(SPB) personnel. Following initial Transformation, the proposal will
go through an implementation review period prior to long range
planning by SPB and PMDB flight readiness review and preliminary test
scheduling by SPSS. This initial review will be performed by the
Transformation Working Group (TWG).

The TWG is made up of persons from USB, SPB, and SPSS. The SPSS
contingency will primarily be people who are scheduled on the BACKUP
shift, although others will be utilized as flight operations permit.
The TWG will review the Transformation results and will work together
to resolve warning and error messages reported by the Transformation
software in the initial and iterative runs, and resolve related
proposal implementation questions which may involve scheduling (SPSS)
as well as proposer level (USB) issues. Among the specific issues they
will address are:

1) identify whether or not Transformation produced the desired results
in order to satisfy the proposal requirements,

2) if not, determine what the problem is

3) 1 & 2 above then relate to ensuring that the proposal's structural
requirements are met in order for SPB to begin realiable long range
planning,

4) resolve problems related to actual scheduling conflicts or problems
identified by SPSS.

5) "Baseline" (or configure) the levels file,

6) Release to SPB for Long Range Planning (LRP) and to SPSS for
PMDB Flight Readiness Review (PFRR) and test scheduling.

Transformation runs and reviews will be iterated during the TWG review
period until the TWG feels that the resulting proposal structures and
content are satisfactory to the best of their ability at that stage.
During "normal" operations (GO cycles), the review period for
individual proposals in Cycle B, for example, will start near the
beginning of the actual observing time for Cycle A. The individual
proposals will become available from USB as they are approved. Each
proposal will be in the TWG review for up to 4(?)weeks.

PMDB Flight Readiness Review and Preliminary Scheduling Activities:

During this period of time, which will last ~8-12 weeks, SPSS BACKUP
shift personnel (and others as available) will be responsible for the
following activities:

1) transfer of the baselined proposal assignment file (.AF)

2) a final review of the proposal structure

3) review of the proposal against a list of outstanding Transformation
OPR's to identify any which may affect this proposal;

4) assigned actions to the appropriate group and follow 10 step
procedure for solving OPR problems.

5) Following successful resolution of all OPR (and other) problems
identified for a proposal, SPSS will begin PMDB proposal processing
and preliminary test scheduling activities. Any problems encountered
during these activities which affect the proposal implementation will
be handled as in step 4 and brought before the TWG and the OPS
Division management where appropriate with options for resolution.

SPB/SPSS Procedures:

Following approval for release of a proposal by the TWG, SPB will
generate a Proposal Delivery Notice (PDN) which will contain the
proposal id(s) and any relevant comments about them. This will be sent
via E-MAIL to the SPSSOA on STOSC. The SPSSOA account MAIL will be
checked by the SPSSOA at the beginning of each shift