<font size=4 color=red face="sans-serif"><b><u>R E M I N D E R</u></b></font>
<br>
<br><font size=4 color=red face="sans-serif"><b><u>Thanks to all WG Chairs
who have updated the schedule. </u></b></font>
<br>
<br><font size=4 color=red face="sans-serif"><b><u>Secretariat has run
yesterday the "workflow" that checks the projects </u></b></font>
<br>
<br><font size=4 color=red face="sans-serif"><b><u>We have still 15 Projects
behind schedule</u></b></font>
<br>
<br><font size=2 face="sans-serif">Dear ADs/DADs/ WG Chairs</font>
<br>
<br><font size=2 face="sans-serif">Considering that</font>
<ol>
<li value=1><font size=2 face="sans-serif"> During the next joint
CESG / CMC meeting in Rome on the 25th October 2016 one of the main topics
will be the CCSDS Work Plan and its long term strategy</font>
<li value=2><font size=2 face="sans-serif">Several approved Projects are
constantly being adjusted wrt its real schedule (and as consequence using
part of the precious Agency Resources for the next years that can be used
for new Projects)</font>
<li value=3><font size=2 face="sans-serif">some draft Projects will be
started in the next 6 months (if Agencies are keen to commit its resources
on the same Project. This depends on the Agency' priorities for the Draft
projects)</font>
<li value=4><font size=2 face="sans-serif">we have currently (3rd October
2016) 36 Projects out of 91 "behind schedule"</font></ol>
<br><font size=2 face="sans-serif">I would like to ask ADs/DADs/ WG Chairs
to bring the following Projects on schedule</font>
<br>
<br><font size=2 color=#008000 face="sans-serif">Note 1: I apologize, but
I have only mentioned the AD or the WG Chair. Sorry deputies</font>
<br><font size=2 color=#008000 face="sans-serif">Note 2: <b>It takes only
5' to update a Project. </b></font>
<br><font size=2 color=#008000 face="sans-serif">Note 3: </font>
<br><font size=2 color=#008000 face="sans-serif">Please, when updating
the schedule, consider real dates. Just one example: When a WG delivers
a document to the AD for Agency review or for Publication, it takes normally
between 3 to 5 months until the review or Publication is achieved</font>
<br>
<br><font size=2 face="sans-serif"><b>====================================</b></font>
<br><font size=3 face="sans-serif"><b><u>SEA Area</u></b><u>
</u></font><font size=3 color=red face="sans-serif"><b><u>3
Projects behind schedule</u></b></font><font size=3 face="sans-serif"><u>
</u></font><font size=3 color=blue face="sans-serif"><b><u>P.
Shames</u></b></font>
<br><font size=2 face="sans-serif"><b>1.01 System Architecture Working
Group</b></font><font size=2 color=red face="sans-serif"><b>
3 Projects behind schedule</b></font><font size=2 face="sans-serif">
</font><font size=2 color=blue face="sans-serif"><b>P.
Shames</b></font>
<br><font size=2 color=red face="sans-serif">CCSDS Global Spacecraft Identifier
Field: Code Assignment Control Procedures (Issue 7) Magenta 320.0 </font>
<br><font size=2 color=red face="sans-serif">Reference Architecture for
Space Data Systems (Issue 2) Magenta 311.0</font>
<br><font size=2 color=red face="sans-serif">Registry Management Policy
Yellow 313.1</font><font size=2 face="sans-serif"> </font>
<br><font size=2 face="sans-serif">=========================================</font>
<br><font size=3 face="sans-serif"><b><u>MOIMS Area</u></b><u>
</u></font><font size=3 color=red face="sans-serif"><b><u>3
Projects behind schedule</u></b></font><font size=3 face="sans-serif"><u>
</u></font><font size=3 color=blue face="sans-serif"><b><u>M.
Merri</u></b></font>
<br><font size=2 face="sans-serif"><b>2.04 Spacecraft Monitoring and Control
Working Group</b> </font><font size=2 color=red face="sans-serif"><b>6
Projects behind schedule</b></font><font size=2 face="sans-serif">
</font><font size=2 color=blue face="sans-serif"><b>D.
Smith</b></font>
<br><font size=2 color=red face="sans-serif">Mission Operations - Message
Abstraction Layer Binding to ZeroMQ Transport and CNES Binary Encoding
Blue 524.4 </font>
<br><font size=2 face="sans-serif"><b>2.06 Telerobotics Working Group</b>
</font><font size=2 color=red face="sans-serif"><b>2
Projects behind schedule</b></font><font size=2 face="sans-serif">
</font><font size=2 color=blue face="sans-serif"><b>N.N.
(M. Merri) </b></font>
<br><font size=2 color=red face="sans-serif">Telerobotic Operations Green
540.0 </font>
<br><font size=2 color=red face="sans-serif">Telerobotic Standard (Blue
Book) Blue 541.0</font>
<br><font size=2 face="sans-serif">=========================================</font>
<br><font size=3 face="sans-serif"><b><u>SOIS Area</u></b><u>
</u></font><font size=3 color=red face="sans-serif"><b><u>8
Projects behind schedule</u></b></font><font size=3 face="sans-serif"><b><u>
</u></b></font><font size=3 color=blue face="sans-serif"><b><u>R.
Barton</u></b></font>
<br><font size=2 face="sans-serif"><b>4.01 Subnetwork Services Working
Group</b> </font><font size=2 color=red face="sans-serif"><b>3
Projects behind schedule</b></font><font size=2 face="sans-serif"><b>
</b></font><font size=2 color=blue face="sans-serif"><b>G.
Rakow</b></font><font size=2 face="sans-serif"> </font>
<br><font size=2 color=red face="sans-serif">SOIS Subnetwork Device Discovery
Service 5 Year Book Review Magenta 854.0 </font>
<br><font size=2 color=red face="sans-serif">SOIS Subnetwork Services -
Subnetwork Deterministic Service Magenta 856.0</font>
<br><font size=2 color=red face="sans-serif">SOIS Subnetwork Synchronization
Service 5 Year Book Review Magenta 853.0</font><font size=2 face="sans-serif">
</font>
<br><font size=2 face="sans-serif"><b>4.02 Application Support Services
Working Group</b> </font><font size=2 color=red face="sans-serif"><b>3
Projects behind schedule</b></font><font size=2 face="sans-serif"><b>
</b></font><font size=2 color=blue face="sans-serif"><b>J.
Wilmot</b></font>
<br><font size=2 color=red face="sans-serif">Electronic Data Sheets and
Common Dictionary of Terms - Overview and Rationale Green 870.1</font>
<br><font size=2 color=red face="sans-serif">Specification for Dictionary
of Terms for Electronic Data Sheets for Onboard Components Magenta 876.1</font>
<br><font size=2 color=red face="sans-serif">XML Specification for Electronic
Data Sheets for Onboard Devices and Software Components Blue 876.0 </font>
<br><font size=2 face="sans-serif"><b>4.03 Onboard Wireless Working Group
</b></font><font size=2 color=red face="sans-serif"><b>2
Projects behind schedule</b></font><font size=2 face="sans-serif"><b>
</b></font><font size=2 color=blue face="sans-serif"><b>K.
Gifford</b></font>
<br><font size=2 color=red face="sans-serif">RFID Tag Encoding Specification
Blue 881.1</font>
<br><font size=2 color=red face="sans-serif">Wireless Network Communications
Overview for Space Mission Operations, Issue 3 Green 880.0</font>
<br><font size=2 face="sans-serif">========================================</font>
<br><font size=3 face="sans-serif"><b><u>SLS Area</u></b><u>
</u></font><font size=3 color=red face="sans-serif"><b><u>1
Project behind schedule</u></b></font><font size=3 face="sans-serif"><b><u>
</u></b></font><font size=3 color=blue face="sans-serif"><b><u>G.
Calzolari</u></b></font>
<br><font size=2 face="sans-serif"><b>5.09 Space Data Link Security WG</b>
</font><font size=2 color=red face="sans-serif"><b>1
Project behind schedule</b></font><font size=2 face="sans-serif"><b>
</b></font><font size=2 color=blue face="sans-serif"><b>G.
Moury</b></font>
<br><font size=2 color=red face="sans-serif">Space Data Link Security (SDLS)
protocol : extended procedures Blue 355.1 </font>
<br><font size=2 face="sans-serif">========================================</font>
<br>
<br><font size=2 face="sans-serif">ciao</font>
<br><font size=2 face="sans-serif">nestoir</font><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>