---------------------------------------------------------------------
To:       All Instrument Teams
From:     SOHO Science Operations Coordinators
Subject:  Commanding from MEDOC
Last Updated:  12 May 1999, from original version: 11 December 1996

 
What follows is a Standard Operating Procedure (SOP) to be followed
developed by the SOCs, FOT, and Project Scientists. All requests to command 
from MEDOC will be decided on a case-by-case basis. This SOP is to ensure 
that precautions are taken due to the remote nature of MEDOC commanding.


                          Standard Operating Procedure
                               MEDOC COMMANDING


1) MEDOC contacts the EOF SOC to request a commanding session at least
   1 - 2 days prior so that both the FOT and other instrument teams
   have been consulted prior to MEDOC commanding. 
 
   In the MEDOC communication (either by e-mail or phone), ALL of the
   following items should be specified:

   * Reason -- science observations, or debugging instrument problems

               Also want to know:
               	a)  Will red or yellow limits be flagged ?
		b)  Have the commands been sent before in NRT ?
                c)  Will any of the commands result in heat
		    dissipation that will affect other instruments ?
		d)  Any expected power increase beyond ICD values ?
		e)  Any expected outgassing effects ?
	        f)  Any micro vibration effects ?
        
    * Priority -- Is dedicated NRT or priority commanding needed ?

    * Contingency Plans 

       a) If something goes wrong with the instrument, what procedures should
          the FOT perform ? 
       b) Also, if something happens to the phone lines or network connections at
          any point during the commanding session -- what should be done 
          (routine limit monitoring or switching the instrument off) ?             


2) Remote commanding will only occur on the LONG DSN contact for a given day. 
   If the remote commanding is agreed upon by the FOT and other instrument teams,
   EOF SOC will notifiy MEDOC.  EOF SOC and MEDOC will confirm:

      * The time (UT) to start commanding from MEDOC.  This will make certain
        that the EOF office is staffed with a SOC and the FOT is staffed with an 
        Observatory Engineer (OE).   It is also suggested that a system/network
        administrator for both EOF and MEDOC be "on-call" or otherwise reachable
        during this time.

      * A phone number at MEDOC which will be dedicated to talk to the EOF.  
        Someone at MEDOC will need to be by this phone at all times during MEDOC
        commanding in the case of an unexpected event.  MEDOC should also supply
        one backup phone number in case.


3) At the agreed commanding time, MEDOC calls the EOF at the following phone
   number:  301-286-3797.  All communication will go through this "dedicated MEDOC phone"
   rather than the usual EOF/SOC phone number (301-286-8985) which can get 
   tied-up with phone calls (however the 301-286-8985 will serve as a backup phone). 

   EOF SOC will confirm that MEDOC is aware of the NRT schedule and any "unusual"
   activities by other teams.  Then will enable MEDOC for commanding.

   EOF SOC will inform MEDOC immediately of any long unscheduled pauses or
   commanding/telemetry problems.

   MEDOC will inform the EOF when they are finished commanding.


4) In the event a problem with the dedicated line or other network problem
   occurs, the following method will be used to investigate the problem:

    *) A phone call is initiated to confirm both sides see the 
       dedicated line is down.
  
    *) MEDOC will inform the EOF as to the commanding instrument's status
       at that moment.  (Is the instrument in a safe or unsafe position ?) 
      
       If the instrument is in danger, the instrument team will confirm
       safing procedures and the EOF SOC will immediately notify the FOT. 

    *) If the instrument is not in any danger, checks of the network status
       and dedicated line will be made.  However, it could take a some time
       before it is operational.  ECS and MEDOC system administrators will
       be in contact to handle the problem.


5) In the event of a "MEDOC Campaign" where instrument planning/commanding
   is being done from MEDOC, it may happen that an instrument team 
   will see a problem with their instrument at hours when a SOC and
   Observatory Engineer are not on duty.  The situation will be treated 
   just like any other remote commanding request, the instrument team
   should:

      - Decide if a TSTOL or delayed command file is the preferred
        method to safe their instrument.
      - Call the FOT and request either a TSTOL procedure be run or
        a delayed command file be uplinked.
      - Follow up with a FAX (301-286-0218) and e-mail 
        (ecs@soc.nascom.nasa.gov) to report what happened.
        This report will be incorporated into an Operations Change
        Directive (OCD) and associated anomaly reports.