<font size=2 face="sans-serif">A note on Emergency Support Services for
comments.</font>
<br>
<br>
<br>
<br>
<br><font size=2 face="sans-serif">Below are notes from IOAG on Emergency
Cross Support.</font>
<br>
<br><font size=2 face="sans-serif">Cheers</font>
<br><font size=2 face="sans-serif">Ian.</font>
<br>
<br><font size=1 color=#800080 face="sans-serif">----- Forwarded by Andreas
Rudolph/esoc/ESA on 14/07/2014 17:48 -----</font>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Michael Schmidt/esoc/ESA</font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">martin.pilgram@dlr.de,
rolf.kozlowski@dlr.de, iwata.takanori@jaxa.jp, philip.e.liebrecht@nasa.gov,
rfc@rniikp.ru, peter.allan@stfc.ac.uk, siahn@kari.re.kr, pierre.jean@asc-csa.gc.ca,
ken.lord@asc-csa.gc.ca, ganyong2000@hotmail.com, fabio.damico@asi.it, nprao@isro.gov.in,
li.lj@263.net.cn, heshanbao@cast.cn, stephanie.wan@nasa.gov, </font>
<br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">Erik Soerensen/esoc/ESA@ESA,
Peter.Willburger@dlr.de, shigeta.tsutomu@jaxa.jp, wallace.s.tai@jpl.nasa.gov,
jon.z.walker@nasa.gov, jean-marc.soula@cnes.fr, gary.a.morse@nasa.gov,
danielle.l.gibbs@nasa.gov, madeline.j.butler@nasa.gov</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">14/07/2014 15:34</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">IOAG Emergency
Cross Support - Output of WG</font>
<br>
<hr noshade>
<br>
<br><font size=2 face="sans-serif">Dear All,</font>
<br>
<br><font size=2 face="sans-serif">I received a first output from the Emergency
Cross-Support WG, which was established after our Rome meeting. Please
find attached an initial report that will be further elaborated. However,
since it raises a couple of interesting questions to the IOAG community,
which includes also organisations that are not represented in the WG, I
want to forward this information. There are a couple of issues that need
to be addressed during our next meeting / telecon. I don't want to open
a second discussion chain at this stage in addition to the one within the
WG. However, I would like to give those agencies that are not involved
in the WG the opportunity to provide inputs that can be addressed in the
WG. </font>
<br>
<ul>
<li><font size=2 face="sans-serif">Context of Emergency Support</font></ul><font size=2 face="sans-serif">The
WG will define the context and scope of emergency cross-support. This should
be verified and confirmed by the IOAG.</font>
<br>
<ul>
<li><font size=2 face="sans-serif">Providing Emergency Under a Cross-Support
Agreement</font></ul><font size=2 face="sans-serif">There are various bilateral
agreements that comprise the cross-support emergency support. However,
even in those cases the results of the WG are useful in order to standardise
the cooperation.</font>
<br>
<ul>
<li><font size=2 face="sans-serif">Providing Emergency Support With No
Cross-Support Agreement</font></ul><font size=2 face="sans-serif">As mentioned
in the report the IOAG can help to establish multi-lateral guidelines that
can help to support each in time of spacecraft emergency.</font>
<br><font size=2 face="sans-serif">It might even be possible to define
a charta that regulates the emergency cross-support between IOAG member
agencies to be used when no cross-support agreements exist. However, this
is an aspect that requires further discussion.</font>
<br>
<ul>
<li><font size=2 face="sans-serif">Legal and Liability Issues</font></ul><font size=2 face="sans-serif">Some
points to be considered are addressed in the report.</font>
<br>
<ul>
<li><font size=2 face="sans-serif">Response Time</font></ul><font size=2 face="sans-serif">I
believe that the response time is an issue. We have to discuss whether
we want to take commitments on the quality of the service.</font>
<br><font size=2 face="sans-serif">Apart from the initial response time
we might also have to discuss the duration of the services that will be
provided.</font>
<br>
<ul>
<li><font size=2 face="sans-serif">Support Priority</font></ul><font size=2 face="sans-serif">I
believe that the IOAG guidelines should clearly specify what the limitations
are.</font>
<br>
<ul>
<li><font size=2 face="sans-serif">Services Provided</font></ul><font size=2 face="sans-serif">I
believe that the idea of defining the "Operational Services"
together with some basic processes and procedures is good.</font>
<br>
<ul>
<li><font size=2 face="sans-serif">Safeguarding Emergency Support Capabilities</font></ul><font size=2 face="sans-serif">I
don't think that special functions are required as I believe that no special
resources are needed and the standard resources are anyhow maintained and
put under configuration control.</font>
<br>
<ul>
<li><font size=2 face="sans-serif">Charge For Support</font></ul><font size=2 face="sans-serif">My
first reaction would be that the initial support to rescue a satellite
is free of charge. However, this might dependent on the duration the support
is required and the bilateral agreements. I believe that this is more an
issue of bilateral agreements than an issue of the IOAG.</font>
<ul>
<li></ul><font size=2 face="sans-serif">I am looking forward to discuss
these aspects with you in our next telecon and face-to-face meeting.</font>
<br>
<br><font size=2 face="sans-serif">If you have any question or require
further information please contact either Erik Soerensen, who is the co-chair
of the WG, or myself.</font>
<br>
<br><font size=2 face="sans-serif">Kind Regards</font>
<br>
<br><font size=2 face="sans-serif">Michael</font>
<br>
<br>
<br><PRE>This message and any attachments are intended for the use of the addressee or addressees only.
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its
content is not permitted.
If you received this message in error, please notify the sender and delete it from your system.
Emails can be altered and their integrity cannot be guaranteed by the sender.
Please consider the environment before printing this email.
</PRE>