<span style=" font-size:10pt;font-family:sans-serif">Dear all,</span>
<br><span style=" font-size:10pt;font-family:sans-serif">
please find below a set
of links to an early Christmas present. These consist of;</span>
<br>
<ol>
<li value=1><span style=" font-size:10pt;font-family:sans-serif">Final
(?) updates to Service Management Common Data Entities Magenta book. Hopefully,
subject to Erik having a final sanity check, this can now be sent to Tom
for entry into the publications queue.</span>
<li value=2><span style=" font-size:10pt;font-family:sans-serif">Final
(?) updates to the Abstract Event Definition Magenta Book. Hopefully, subject
to Erik having a final sanity check, this can now be sent to Tom for entry
into the publications queue.</span>
<li value=3><span style=" font-size:10pt;font-family:sans-serif">Final
(?) updates to the Communications Planning Info Blue Book. Hopefully, subject
to Erik having a final sanity check, this can now be sent to Tom for entry
into the publications queue.</span>
<li value=4><span style=" font-size:10pt;font-family:sans-serif">Draft
of the changes needed to the Simple Schedule Blue Book required for Technical
Corrigendum 1.</span>
<li value=5><span style=" font-size:10pt;font-family:sans-serif">Draft
of Technical Corrigendum 1 for the Simple Schedule Blue Book.</span>
<li value=6><span style=" font-size:10pt;font-family:sans-serif">Zip file
containing updated schemas consistent with the above.</span>
<li value=7><span style=" font-size:10pt;font-family:sans-serif">Zip file
containing updated UML Model consistent with the above</span>
<li value=8></ol><span style=" font-size:10pt;font-family:sans-serif">For
those of you not familiar with what a Technical Corrigendum is in the context
of CCSDS (as I was until a few days ago) and are wondering what the difference
between 4 and 5 on the above list are the answer is as follows. A technical
Corrigendum contains a list of changes that have to be made to the original
recommendation, it is not an updated version of the document itself. For
me the easiest way to sort out what changes were required was to update
the original recommendation (resulting in 4 in the above list) and then
go through this and put the changes into a new document (resulting in 5
in the above list). Anyway the documents etc</span>
<ol>
<li value=1></ol><span style=" font-size:10pt;font-family:sans-serif">Common
Data Entities Magenta Book:</span><span style=" font-size:10pt;color:blue;font-family:sans-serif">
ht</span><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Magenta/Service%20Management%20Common%20Data%20Entities/Final%20Version/Post%20CESG%20Poll/902x12m0_CESG_Approval-PostPIDs-CRH-20201217.doc?Web=1"><span style=" font-size:10pt;color:blue;font-family:sans-serif">tps://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Magenta/Service%20Management%20Common%20Data%20Entities/Final%20Version/Post%20CESG%20Poll/902x12m0_CESG_Approval-PostPIDs-CRH-20201217.doc?Web=1</span></a>
<br><span style=" font-size:10pt;font-family:sans-serif">Abstract Event
Definition Magenta Book </span><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Magenta/Abstract%20Event%20Definition/Final%20Version/Post%20CESG%20Poll/902x13m0_CESG_Approval-PostPIDs-CRH-20201217.doc?Web=1"><span style=" font-size:10pt;color:blue;font-family:sans-serif">
https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Magenta/Abstract%20Event%20Definition/Final%20Version/Post%20CESG%20Poll/902x13m0_CESG_Approval-PostPIDs-CRH-20201217.doc?Web=1</span></a>
<br><span style=" font-size:10pt;font-family:sans-serif">Communications
Planning Information Formats Blue Book
</span><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Blue/Communication%20Planning%20Information%20Formats/Red%20Book/Drafts/902x2r1_02-For%20AD%20Review-CRH-20201217.doc?Web=1"><span style=" font-size:10pt;color:blue;font-family:sans-serif">https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Blue/Communication%20Planning%20Information%20Formats/Red%20Book/Drafts/902x2r1_02-For%20AD%20Review-CRH-20201217.doc?Web=1</span></a><span style=" font-size:10pt;font-family:sans-serif"><br>
Draft of changes to the Simple Schedule for Technical Corrigendum 1
</span><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Blue/Simple%20Schedule/Technical%20Corrigendum/902x1b1TC1-%20Simple%20Schedule%20Format%20Specification-CRH-20201217.doc?Web=1"><span style=" font-size:10pt;color:blue;font-family:sans-serif">https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Blue/Simple%20Schedule/Technical%20Corrigendum/902x1b1TC1-%20Simple%20Schedule%20Format%20Specification-CRH-20201217.doc?Web=1</span></a>
<br><span style=" font-size:10pt;font-family:sans-serif">Draft of Technical
Corrigendum 1 for the Simple Schedule Blue Book. </span><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Blue/Simple%20Schedule/Technical%20Corrigendum/902x1b1TC1-%20Simple%20Schedule%20Format%20Specification%20-%20Technical%20Corrigendum-CRH-20201217.doc?Web=1"><span style=" font-size:10pt;color:blue;font-family:sans-serif">https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Blue/Simple%20Schedule/Technical%20Corrigendum/902x1b1TC1-%20Simple%20Schedule%20Format%20Specification%20-%20Technical%20Corrigendum-CRH-20201217.doc?Web=1</span></a>
<br><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Schemas/902Schema%2020201217%20Snapshot.zip"><span style=" font-size:10pt;font-family:sans-serif">Zip
file containing updated schemas consistent with the above</span><span style=" font-size:10pt;color:blue;font-family:sans-serif">
https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/Schemas/902Schema%2020201217%20Snapshot.zip</span></a>
<br><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/UML%20Model/902UmlModel%2020201217%20Snapshot.zip"><span style=" font-size:10pt;font-family:sans-serif">Zip
file containing updated UML Model consistent with the above</span><span style=" font-size:10pt;color:blue;font-family:sans-serif">
https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Book%20Production/UML%20Model/902UmlModel%2020201217%20Snapshot.zip</span></a>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Well the year
is drawing to a close and its been the weirdest year I've lived through.
I hope that you and yours have got through the pandemic safely so far and
I'd just like to wish everybody good health for the coming year. Hopefully
we'll be able to meet physically again next year, although I don't think
it will be in Huntsville, but possibly in Toulouse. I'm look forward to
meeting you all again</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Merry Christmas
& A Happy (and healthy) new Year.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Cheers for now,</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Colin</span>
<br><span style=" font-size:10pt;font-family:sans-serif"><br>
<br>
---------------------------------------------------------------------------------------------------------<br>
Dr. Colin R. Haddow,<br>
HSO-GI, European Space Agency,<br>
European Space Operations Centre,<br>
Robert-Bosch-Str 5,<br>
64293 Darmstadt,<br>
Germany.<br>
<br>
Phone; +49 6151 90 2896<br>
Fax; +49 6151 90 3010<br>
E-Mail; colin.haddow@esa.int<br>
---------------------------------------------------------------------------------------------------------<br>
</span><PRE>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or
protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received
this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect
personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).
</PRE>