(1) Date & Time of delivery
10th July 2009 13:00 BST

(2) ICC individual to be contacted where problems arise with the delivery
    (1) Sarah Leeks (RAL)
    (2) Michael Pohlen (UofC)
    (3) Sunil Sidher (RAL)

    Note: always copy spire@rl.ac.uk

    Also note, that we list people who you can be contacted about the 
    delivery here as usual, however really the person to contact depends
    on who is on duty that day which can be seen in
    http://www.herschel.be/twiki/pub/Spire/CopPV/The_Masterplan.pdf under
    scheduling, although emailing in response to this email (to the SPIRE
    operations and all the SPIRE people) should always get your message to
    the relevant people.

(3) Time range for which the data being delivered is applicable
OD 60

(4) Delivery information - names of all files contained in the tar file
SPIRE_MC_pv26_FULL_14_0_CUS.def
SPIRE_MC_pv26_FULL_14_0_CUS_CAL.xml
SPIRE_SSF_OD0060_2_0.ssf
SPIRE_POS_OD0060_2_0.pos
SPIRE_ICP_OD0060_2_0.icp
SPIRE_AOR_OD0060_2_0.aor
Command scripts: SPIRE_CUS_THCP.py
SPIRE_Duration.txt
SPIRE_Readme_OD0060_2_0.txt

(5) CUS Script amd Calibration files ICC internal configuration control 
issues
(a) Name of ICC mission configuration from which files were exported 
(for reference purposes only)
pvPhase_mconfig_26
(b) Name of the CVS Tag related to this delivery (if relevant)


(c) Name of the ICC Database containing this delivery (for reference 
purposes only)
mps_phs_1
(d) HCSS version used when working with these files
Version 396/1.0.3

(6) AOR Files issues
(a) HSpot, PHS and MPS versions used
HSpot v4.2,  PHS over 396 Build #566
(b) Number of AORs delivered in the .aor file
51
(c) Overall Time Estimation calculated by HSpot
9h31m32s

(7) Spacecraft Database issues
(a) ICC MIB version applicable to these cus & calibration files
SPIRE 3.0.B2 PR
(b) HPSDB version (if known) that contains this MIB
HPSDB_R_TM_HERSCH_FM1_M_903062241
(c) OBSM software version on the instrument applicable to this MIB
the one currently loaded on S/C

(8) Go-ahead of the ICC CCB (if applicable)
Okay given by Sarah Leeks

(9) SxRs applicable to the updates of the scripts delivered in this release
SpireSpr:1612 and SpireSpr:1613

(10) Additional notes e.g. special installation instructions, HIFI 
Sequencer code version to be used at HSC,
messages for missioning planning (like change default avoidance setup) etc
       (a) default avoidance setup used
       (b) Solar System Objects scheduled on this OD:
There is one moving target - Uranus.
The default avoidance setup is used.
Note Uranus is far away (in the other DTCP) and it is with SAA>100.
It has been agreed with HIFI and PACS to observe Uranus.
We have ~11,000  TC COUNTs.
We have put in a dummy observation at the very start of the day. This should be removed by the HSC mission planners as it was just to get the S/C to where HIFI leaves it - i.e. Uranus.
We slew to PACS dark sky region near the end of our day as we agreed to pay for the slew time.
We agreed with PACS and HIFI as to the time slots that we use.
We made sure that our cooler recycle and our first observations after HIFI have finished start at the same time as they do in the HSC OD60 as originally planned.
Our final observation finishes 22 seconds earlier than previously.
(11) CusCmdscript output file (see Note below)
(a) Name of CusCmdScript
SPIRE_CUS_THCP.py
(b) Expected durations when this is run
see SPIRE_Duration.txt