...............................
Date: Mon, 22 Feb 1999 13:03:54
Who: cjl
Subject:  Schedule this week - PLEASE READ
Original file: /home/tab/ja.t
...............................
From listmaster Mon Feb 22 13:03 PST 1999
From: cjl
Subject: Schedule this week - PLEASE READ
To: wire
Date: Mon, 22 Feb 1999 13:03:54 -0800 (PST)

WIRE's - this may update a few times - please watch for a read any updates
immediately.

Carol



LAST WEEK BEFORE LAUNCH - SOC GOALS AND SCHEDULE:

1.  L-1 week delivery to GSFC of EJECT.  TODAY.

    We do not need to re-deliver NOSLEW, GYROCAL, CONSTR, EJECT again
    for different launch dates this week as the files we made yesterday
    cover the first several days

2.  L-1 week completion of REGOTL for March 1 launch.  By end of Tuesday.

3.  Ongoing through week:  Additional deliveries of IOCSCI and REGOTL for
    later launch days.

    We must have valid planfiles and timelines, fully checked, for
    March 2,3,4 at least, on the following schedule:

        Monday - March 2 launch
        Tuesday  March 3
        Weds     March 4
        Thurs    March 5
        Fri      March 6

    If your planfile must change to accomodate each date, then you must deliver
    it by about noon on the appropriate day.

    The Mon-Weds deliveries are essential because we cannot know ahead of
    March 1 whether 2,3,4 will be needed.  We can revisit the need for
    the March 5,6 dates on Weds.

    PLEASE send mail to WIRE when you deliver a new planfile so other planners
    are aware of it.  (Tim is drafting a proper plan delivery procedure)

4.  Ongoing:  Everyone should identify what cross-training they ought to
    have to support their backup tasks.   Do what they can to acquire this
    training.


Daily Schedule:
--------------

5.  Monday: Review SO bugs and decide priorities and schedule.  Also
    draw up robust SO development,test,delivery procedure
    (Tim, Carol, Dave, David, Yi).

    Current version of SO code to Ops TODAY.

5.  Tuesday: meet with Catena and Casasanta and review a daily schedule;
    review interfaces.

6.  Tuesday:  Final pre-launch delivery of all cal files from TERRY.

7.  Wednesday: Meeting to discuss contingency planning for non-nominal
    orbit.  (1) How to re-tile the entire sky quickly with a safe plan (non-
    optimal science, no AI tile, no bright source avoidance, acceptable;
    science efficiency takes second priority to mission safety); (2)
    How to add science efficiency back in: first order plan.  Lead: NICK.

8:  Weds: Copy prelaunch 'wire' database to 'wire_test'
    and put launch-ready access priveleges on critical tables <- WEN
    (This needs proper oversight by CCB)

    Reconfigure disk, esp. DBMS disk. <- STEVE,NIAN

9.  Weds: Carol, Dave, Tim and Perry to produce short SOC Operations procedures
    guidelines document.

10. Thursday: Wrap up new DA development. Delivery to dev. Testing.

11. Thursday: Nick, Sumita, Virginia to create wall chart showing mission
    time/orbit number translations.   Large chart to which mission events
    can be posted.

12. Friday: Testing. and Bug fixes for DA. Delivery to int and ops (and dev
    if there were changes). Create RTB.