<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Verdana","sans-serif";
color:#1F497D;
font-weight:normal;
font-style:normal;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Verdana","sans-serif";
color:#1F497D;
font-weight:normal;
font-style:normal;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:745998151;
mso-list-template-ids:-1077111300;}
@list l0:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple style='word-wrap: break-word;
-webkit-nbsp-mode: space;-webkit-line-break: after-white-space'>
<div class=WordSection1>
<p class=MsoNormal><span style='color:#1F497D'>Hello Gert,<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>I hope this e-mail finds you
doing well. Unfortunately I have been extremely preoccupied with other
matters and so have not really had time (not to mention budget) for the
Exomars architecture effort. <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>With regard to point 7, I think
that Peter's inclusion of the service management component is okay from the
overall architecture point of view as this is indeed something that has to
occur. I have no objections to assuming that the management port for the
managed components is implicitly -- perhaps some sort of stereotype could be to
indicate this for the managed components. I realize that all of this may be
somewhat academic at this point as you perhaps may not have any further budget
to produce any further updates the document. Which brings me to the main
point of writing which is to see if there is an update of the document that is
to be made available such that it should be scheduled for some sort of
discussion/review at the fall CCSDS meetings beginning in approximately 6
weeks. Any information as to the updated document would be most
appreciated.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Best regards,<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>-Erik<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Villemos, Gert
[mailto:gert.villemos@logica.com] <br>
<b>Sent:</b> Tuesday, July 19, 2011 12:47 AM<br>
<b>To:</b> Shames, Peter M (313B); Barkley, Erik J (317H); Colin.Haddow@esa.int<br>
<b>Cc:</b> Nestor Peccia; Mario Merri; CCSDS RASG<br>
<b>Subject:</b> RE: ExoMars Architecture update?<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana","sans-serif";
color:#1F497D'>One comment more regarding point 7;<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana","sans-serif";
color:#1F497D'>In principles all services should have a 'Service Management'
service as well, allowing the agreement, configuration, scheduling, etc of the
specific service. I think the 'Cross Support Functional Model' as defined in
RASIG and in the CSTS-RM contains the concept that all functions have service
ports and management ports.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana","sans-serif";
color:#1F497D'>Question is whether we want to model the management port
explicitly every time, or whether we say that a (set of) services has an
associated 'management service', but doesn’t show it to keep the diagram
simple?<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana","sans-serif";
color:#1F497D'>Cheers,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana","sans-serif";
color:#1F497D'>Gert.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Shames, Peter M
(313B) [mailto:peter.m.shames@jpl.nasa.gov] <br>
<b>Sent:</b> Mittwoch, 22. Juni 2011 23:30<br>
<b>To:</b> Villemos, Gert; Barkley, Erik J (317H); Colin.Haddow@esa.int<br>
<b>Cc:</b> Nestor Peccia; Mario Merri; CCSDS RASG<br>
<b>Subject:</b> Re: ExoMars Architecture update?<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><span lang=DE><o:p> </o:p></span></p>
<div>
<p class=MsoNormal><span lang=DE style='font-size:8.5pt;color:black'>Guys,<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=DE style='font-size:8.5pt;color:black'><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=DE style='font-size:8.5pt;color:black'>Here are
some hacks at the model. I am sure that I did no lasting damage, but
hopefully the tweaks to the Exomars diagram will help clarify some things.
I found the following confusing things, but it may just be how I am
reading your intent:<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=DE style='font-size:8.5pt;color:black'><o:p> </o:p></span></p>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
lang=DE style='font-size:8.5pt;color:black'><span style='mso-list:Ignore'>1.<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span lang=DE style='font-size:8.5pt;color:black'>A
"Space Link" is normally thought of as an RF physical thing.
As such it is not a function, but you may wish to model it as a first class
entity. It will not have ports such as SLE RAF, and F-CLTU, if anything
it would have only an RF port and attributes such as frequency, modulation, and
pointing.<o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
lang=DE style='font-size:8.5pt;color:black'><span style='mso-list:Ignore'>2.<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span lang=DE style='font-size:8.5pt;color:black'>Ditto
for the "Proximity Link", which is how "space to space
links" are usually described<o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
lang=DE style='font-size:8.5pt;color:black'><span style='mso-list:Ignore'>3.<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span lang=DE style='font-size:8.5pt;color:black'>I
do not think we need to go into all of the details of how RF links are created,
just to model them at a high enough level to show how they participate in
communications.<o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
lang=DE style='font-size:8.5pt;color:black'><span style='mso-list:Ignore'>4.<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span lang=DE style='font-size:8.5pt;color:black'>I
added Space Link Production component (and Proximity too) since we need to
separate the service production from the service provisioning, which is what
SLE actually connects to.<o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
lang=DE style='font-size:8.5pt;color:black'><span style='mso-list:Ignore'>5.<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span lang=DE style='font-size:8.5pt;color:black'>You
seem to have SLE bits and pieces scattered all over the place. The only place
they really belong is between the elements in the OMOC that produce and
aggregate frames and the element in the service provide that accepts them.<o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
lang=DE style='font-size:8.5pt;color:black'><span style='mso-list:Ignore'>6.<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span lang=DE style='font-size:8.5pt;color:black'>I
added a Spacecraft Tracking element that would produce tracking and radiometric
data, which what the Flight Dynamics functions needs to get its job done.<o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
lang=DE style='font-size:8.5pt;color:black'><span style='mso-list:Ignore'>7.<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span lang=DE style='font-size:8.5pt;color:black'>I
added a Space Link Management (or Planning) function in the OMOC, which is what
would connect to the Service Management function in the service provider, using
the CCSDS Service Management protocol. I showed it connected to SLE as
shorthand, since the diagram was getting rather cluttered.<o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
lang=DE style='font-size:8.5pt;color:black'><span style='mso-list:Ignore'>8.<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span lang=DE style='font-size:8.5pt;color:black'>The
DSN, EDL & Rover, OMOC are listed as Organizational Elements in the
Functional View. But these are also given "ports", which seems
somewhat strange to me. I think of organizational elements as being in
the Enterprise view. If they show up in the Functional View at all it is
for purposes of showing ownership. If you called these things Facilities
I would have less of a problem, or you could call them Service and Service User
Elements.<o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
lang=DE style='font-size:8.5pt;color:black'><span style='mso-list:Ignore'>9.<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span lang=DE style='font-size:8.5pt;color:black'>Everything
under "Ports" is called a Service of some type. I would think
that Service Elements have Ports, which I think is backwards from how you have
it now. But maybe I misunderstand how you are using this.<o:p></o:p></span></p>
<div>
<p class=MsoNormal><span lang=DE style='font-size:8.5pt;color:black'>I am sure
that there is more, but it escapes me right now.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=DE style='font-size:8.5pt;color:black'><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=DE style='font-size:8.5pt;color:black'>Peter<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=DE style='font-size:8.5pt;color:black'><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=DE style='font-size:8.5pt;color:black'><o:p> </o:p></span></p>
</div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span lang=DE style='color:black'>From: </span></b><span
lang=DE style='color:black'>Gert Villemos <<a
href="mailto:gert.villemos@logica.com">gert.villemos@logica.com</a>><br>
<b>Date: </b>Tue, 21 Jun 2011 00:46:33 -0700<br>
<b>To: </b>Erik Barkley <<a href="mailto:Erik.J.Barkley@jpl.nasa.gov">Erik.J.Barkley@jpl.nasa.gov</a>>,
"<a href="mailto:Colin.Haddow@esa.int">Colin.Haddow@esa.int</a>" <<a
href="mailto:Colin.Haddow@esa.int">Colin.Haddow@esa.int</a>>, Peter Shames
<<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>><br>
<b>Cc: </b>Nestor Peccia <<a href="mailto:Nestor.Peccia@esa.int">Nestor.Peccia@esa.int</a>>,
Mario Merri <<a href="mailto:Mario.Merri@esa.int">Mario.Merri@esa.int</a>>,
CCSDS RASG <<a href="mailto:CSS-RASG@mailman.ccsds.org">CSS-RASG@mailman.ccsds.org</a>><br>
<b>Subject: </b>RE: ExoMars Architecture update?<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=DE style='font-size:8.5pt;color:black'><o:p> </o:p></span></p>
</div>
<blockquote style='border:none;border-left:solid #B5C4DF 3.0pt;padding:0in 0in 0in 3.0pt;
margin-left:3.0pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'
id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<div>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana","sans-serif";
color:#1F497D'>Hi Eric,</span><span lang=DE style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana","sans-serif";
color:#1F497D'> </span><span lang=DE style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana","sans-serif";
color:#1F497D'>Peter send some very interesting documentation on methodology
(thanks Peter), but I did not receive any suggestions to update / addition of
functional elements from anyone. We would very much welcome this input.</span><span
lang=DE style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana","sans-serif";
color:#1F497D'> </span><span lang=DE style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana","sans-serif";
color:#1F497D'>I will update the recommendation with the comments raised at the
meeting that I can correct without input. I will be away next week, so it will
be the 8<sup>th</sup> of July, not the 20<sup>th</sup> of June as planned.</span><span
lang=DE style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana","sans-serif";
color:#1F497D'> </span><span lang=DE style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana","sans-serif";
color:#1F497D'>Regards,</span><span lang=DE style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana","sans-serif";
color:#1F497D'>Gert.</span><span lang=DE style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana","sans-serif";
color:#1F497D'> </span><span lang=DE style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana","sans-serif";
color:#1F497D'> </span><span lang=DE style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana","sans-serif";
color:#1F497D'> </span><span lang=DE style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana","sans-serif";
color:#1F497D'> </span><span lang=DE style='color:black'><o:p></o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black'> Barkley, Erik J (317H) [<a
href="mailto:erik.j.barkley@jpl.nasa.gov">mailto:erik.j.barkley@jpl.nasa.gov</a>]
<br>
<b>Sent:</b> Montag, 20. Juni 2011 21:53<br>
<b>To:</b> <a href="mailto:Colin.Haddow@esa.int">Colin.Haddow@esa.int</a>;
Villemos, Gert; Shames, Peter M (313B)<br>
<b>Cc:</b> <a href="mailto:'Nestor.Peccia@esa.int">'Nestor.Peccia@esa.int</a>';
Mario Merri; CCSDS RASG<br>
<b>Subject:</b> ExoMars Architecture update?</span><span lang=DE
style='color:black'><o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><span lang=DE style='color:black'> <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:black'>My notes from the Berlin meetings
indicate that Gert was to receive inputs with regard to the function
definitions by 10 June. In particular, Peter had an action item to provide
additional functional inputs by 10 June. I will admit that my e-mail goes by
rather fast sometimes but to the best of my knowledge I don't believe anybody
supplied any inputs? There was then supposed to be an update with regard
to the ExoMars architecture document so that a teleconference could be held on
17 June. The general idea was then to produce the updated document by 30 June.
So far I don't think we are doing so good on this. Does anyone have any updates
with regard to their function definition inputs and/or updates to the ExoMars
architecture document? I suspect we need to do a bit of a rescheduling
here. Status updates would be much appreciated. Thank you.</span><span
lang=DE style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span style='color:black'> </span><span lang=DE
style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span style='color:black'>Best regards,</span><span lang=DE
style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span style='color:black'> </span><span lang=DE
style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span style='color:black'>-Erik</span><span lang=DE
style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=DE style='font-size:8.5pt;color:black'><br
clear=all>
Think green - keep it on the screen. This e-mail and any attachment is for
authorised use by the intended recipient(s) only. It may contain proprietary
material, confidential information and/or be subject to legal privilege. It
should not be copied, disclosed to, retained or used by, any other party. If
you are not an intended recipient then please promptly delete this e-mail and
any attachment and all copies and inform the sender. Thank you. <o:p></o:p></span></p>
</div>
</div>
</blockquote>
<p class=MsoNormal><span lang=DE style='font-size:12.0pt;font-family:"Times New Roman","serif"'><br
clear=all>
Think green - keep it on the screen. This e-mail and any attachment is for
authorised use by the intended recipient(s) only. It may contain proprietary
material, confidential information and/or be subject to legal privilege. It
should not be copied, disclosed to, retained or used by, any other party. If
you are not an intended recipient then please promptly delete this e-mail and
any attachment and all copies and inform the sender. Thank you. <o:p></o:p></span></p>
</div>
</body>
</html>