Each day the EIS planner should send an e-mail to the CDS planner account giving details of the EIS plan. As well as a general description of the EIS plan, the message should also contain the EIS plan summary file. This gives the exact details of which EIS studies are being run each day.
For all but the period 11-24 UT on Monday, the EIS chief observer (CO) will create the observation plan before the CDS planner. This means that it is straightforward for the CDS planner to respond to the EIS plan and ensure that observations are coordinated, as long as pointing and timing information is passed to the CDS planner.
Note, however, that there is an opportunity for the Hinode pointing to be changed prior to the upload of the EIS plan, for which the CDS planner will not be able to respond. These changes are usual minor, though, and should not affect the coordinated observations.
If CDS and EIS are both part of a JOP, HOP or campaign, then pointing coordinates and study information will be passed to the planner through e-mail or the CDS planning notes, and planning will occur as normal.
Otherwise, if EIS is taking its own observations or if CDS isn't part of the Hinode campaign, then CDS planner should choose pointings and studies that best match the EIS plan as contained in the EIS plan summary file.
EIS runs a study called SYNOP002 once a week that obtains complete EIS spectra over a 128"x184" field of view over a 3.5 hour period. Usually this is run at some point during the EIS weekend plan (11 UT Saturday to 11 UT Monday). It is a high priority for CDS to support this observation. Based on the contents of the EIS plan summary file produced on Friday, the CDS planner should run the following pair of studies during this 3.5 hour observation: