<font size=2 face="sans-serif">Dear Erik, dear CMC members,</font>
<br>
<br><font size=2 face="sans-serif">concerning the nominations for CSS DAD,
ESA proposes Colin Haddow for this position</font>
<br><font size=2 face="sans-serif"> </font>
<br><font size=2 face="sans-serif"><u>Find below a resume of Colin Haddow</u></font>
<br>
<br><font size=2 face="sans-serif">Colin has been a member of the CCSDS
Service Management Working Group for the last 10 years and deputy
Working Group Chair for the last 4 years. He is the lead author on 4 of
the recommendations being prepared by the working group;</font>
<br>
<br><font size=2 face="sans-serif">1. Simple Schedule Format Specification
</font>
<br><font size=2 face="sans-serif">2. Service Management Utilization Request
Formats</font>
<br><font size=2 face="sans-serif">3. Planning Data Formats</font>
<br><font size=2 face="sans-serif">4. Terrestrial Generic File Transfer.</font>
<br>
<br><font size=2 face="sans-serif">He has a good working knowledge of the
space link extensions, having been involved with the design and implementation
of the telemetry and telecommand subsystems on a number of mission control
systems. In addition he led the design and implementation of the ESA Network
Interface System (NIS) that is used by ESA to establish links between mission
control systems and ground stations. The NIS implements the SLE RCF, RAF,
ROCF, FSP and FCLTU services.</font>
<br>
<br><font size=2 face="sans-serif">Operational experience in supporting
missions, especially the telemetry and commanding subsystems, have provided
him with a good familiarity with the operational aspects of TTC both internal
to ESA and in the context of cross support. He has also been involved with,
and in some cases has led, the standardisation of internal ESA interfaces,
between the mission control systems, flight dynamics and the ESA Tracking
network (ESTRACK). This has given him considerable insight into the scheduling
and coordination aspects of the ESTRACK.</font>
<br>
<br><font size=2 face="sans-serif">His ongoing involvement in the Service
Management Working group have demonstrated his interpersonal skills with
respect to the coordination of international projects and development efforts.</font>
<br>
<br><font size=2 face="sans-serif">I hope I have provided enough background
about Colin, who is well known in CCSDS and I am willing to further information
if needed.</font>
<br>
<br><font size=2 face="sans-serif">Regards</font>
<br><font size=2 face="sans-serif">Juan Miró</font>
<br><font size=2 face="sans-serif">ESA delegate to CMC</font>
<br>
<br><font size=2 face="sans-serif">Juan Miro<br>
Head Ground Systems Engineering Department</font>
<br><font size=2 face="sans-serif">European Space Operations Centre<br>
European Space Agency</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">"Barkley, Erik
J (3970)" <erik.j.barkley@jpl.nasa.gov></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">"CCSDS Management
Council (CMC@mailman.ccsds.org) (CMC@mailman.ccsds.org)" <CMC@mailman.ccsds.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">"Margherita.di.Giulio@esa.int"
<Margherita.di.Giulio@esa.int>, "CESG -- CCSDS-Engineering Steering
Group \(cesg@mailman.ccsds.org\) \(cesg@mailman.ccsds.org\)" <cesg@mailman.ccsds.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">02/12/2017 00:36</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">[CMC] Invitation
for nominees for CSS Area, Deputy Area Director</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">"CMC"
<cmc-bounces@mailman.ccsds.org></font>
<br>
<hr noshade>
<br>
<br>
<br><font size=2 face="Calibri">CMC Colleagues,</font>
<br><font size=2 face="Calibri">As you are probably aware, the current
Cross Support Services Area Deputy Area Director (CSS DAD), Margherita
DiGiulio will be the CESG Chair, effective January 1, 2018. As such, there
is now a need for a new CSS DAD. This email is to invite the CMC to nominate
candidates for this position.</font>
<br><font size=2 face="Calibri">In addition, to the general CCSDS qualifications,
which are listed below, here is my emphasis on the ideal qualifications
for the CSS Area DAD:</font>
<br><font size=2 face="Calibri">a) Significant familiarity
with agency TTC (Tracking, Telemetry and Command) operations and systems,
especially as applied in an interagency cross support setting</font>
<br><font size=2 face="Calibri">b) A working knowledge
of space link extension (SLE) standards and their implementation; familiarity
with the Cross Support Transfer Services framework is desirable but not
required</font>
<br><font size=2 face="Calibri">c) A good understanding
of how the agencies TTC services are managed and coordinated, especially
in an interagency cross support context</font>
<br><font size=2 face="Calibri">d) Established interpersonal
skills for coordination of international projects and development efforts</font>
<br><font size=2 face="Calibri">Note that the CCSDS procedures manual states
that an AD and DAD cannot be from the same agency. Therefore, this
request does not apply to NASA. </font>
<br><font size=2 face="Calibri">General qualifications, as stated in the
procedures manual are “...A candidate for selection as CESG chair, Area
Director, or their deputies must have demonstrated the ability to function
independently of his/her own agency’s agenda and to be able to fairly
lead the development of international consensus..”</font>
<br><font size=2 face="Calibri">A more formal statement about the role
of the DAD, extracted from the current CCSDS Procedure manual and listed
below. It may be helpful to review this.</font>
<br><font size=2 face="Calibri">Given that this is recent development and
that it is desirable to have a new deputy for the CSS Area established
well in advance of the spring 2018 meetings, I respectfully request identification
of nominees by January 12, 2018. A brief indication of the candidate’s
qualifications is much appreciated.</font>
<br><font size=2 face="Calibri">Best regards,</font>
<br><font size=1 face="Georgia">Erik Barkley</font>
<br><font size=1 face="Georgia">Cross Support Services Area Director</font>
<br><font size=1 face="Georgia">Consultative Committee for Space Data Systems</font>
<br><a href=http://www.ccsds.org/><font size=1 color=#0082bf face="Georgia"><u>www.ccsds.org</u></font></a>
<br><font size=1 face="Georgia"> </font>
<br><font size=1 face="Georgia">+1 818.393.4972</font>
<br><font size=1 face="Georgia"> </font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">From CCSDS A02.1-Y-4, April 2014:</font>
<br><font size=2 face="Calibri"><u>For refence, The DAD role</u>: </font><font size=2 face="Calibri">“…The
DAD is responsible for performing the functions of the AD in the AD’s
absence. DADs may assist ADs in performance of functions, and DADs are
expected to participate in the CESG consensus process…”</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri"><u>For reference, the role of the AD for
which the DAD is the deputy</u>:</font>
<br><font size=2 face="Calibri">“…An Area Director is responsible for
the work done in his or her WGs, BOFs, and SIGs and is</font>
<br><font size=2 face="Calibri">specifically responsible for the following:</font>
<br><font size=2 face="Calibri">a) being a member of the CESG as the single
representative of the CCSDS technical</font>
<br><font size=2 face="Calibri">Area;</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">b) screening all proposals to form new
WGs that are brought forward by BOFs to make</font>
<br><font size=2 face="Calibri">sure that they are supported by required
documentation and their technical focus is</font>
<br><font size=2 face="Calibri">vectored toward the goals and objectives
of CCSDS;</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">c) making recommendations to the CESG concerning
approval for the chartering and</font>
<br><font size=2 face="Calibri">formation of WGs;</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">d) ensuring that CCSDS documents are properly
categorized and that they embody the</font>
<br><font size=2 face="Calibri">content and quality expected of documents
of their type;</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">e) making recommendations to the CESG for
the progression of WG documents as they</font>
<br><font size=2 face="Calibri">approach key decision gates along the various
document tracks;</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">f) demonstrating and certifying that formal
review procedures have been properly</font>
<br><font size=2 face="Calibri">followed prior to recommending the advancement
of a document;</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">g) communicating the dates of CESG meetings
to the WG, BOF, and SIG chairs so that</font>
<br><font size=2 face="Calibri">they may schedule the completion of their
work prior to this time;</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">h) notifying the WG, BOF, and SIG chairs
as to how and when their work is to be</font>
<br><font size=2 face="Calibri">presented to the AD for review;</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">i) deciding if Area meetings are to be
held, and if so, setting the date, location, and</font>
<br><font size=2 face="Calibri">agenda for each Area meeting (it is strongly
recommended that periodic face-to-face</font>
<br><font size=2 face="Calibri">co-located meetings of the WGs, BOFs, and
SIGs in a particular Area should be held</font>
<br><font size=2 face="Calibri">to maximize opportunities for cross-pollination
of ideas);</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">j) chairing Area meetings, ensuring that
every WG, BOF, or SIG presents its work in a</font>
<br><font size=2 face="Calibri">satisfactory manner and that Area decisions
are made through a process of consensus;</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">k) ensuring that all Area work follows
the set of architectural principles agreed to by the</font>
<br><font size=2 face="Calibri">CESG and is properly synchronized with
work in other areas and with the smooth</font>
<br><font size=2 face="Calibri">evolution of the large installed base of
CCSDS-compatible mission-support</font>
<br><font size=2 face="Calibri">infrastructure;</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">l) working with the WG, BOF, and SIG chairs
to prepare detailed reports of overall</font>
<br><font size=2 face="Calibri">status, progress and problems for presentation
at CESG meetings (as necessary, the</font>
<br><font size=2 face="Calibri">AD may request specific WG, BOF, or SIG
chairs to attend CMC meetings to discuss</font>
<br><font size=2 face="Calibri">difficult issues);</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">m) verifying that all Normative Track documents
are subject to the proper process of</font>
<br><font size=2 face="Calibri">formal agency review by the WG chair; </font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">n) maintaining the Area master-tracking
list of relevant specifications as they progress</font>
<br><font size=2 face="Calibri">through the standardization tracks;</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">o) making recommendations to the CESG to
reconvene a WG to refresh a standard that</font>
<br><font size=2 face="Calibri">has been finalized and deployed into operational
use, and for which the WG is no</font>
<br><font size=2 face="Calibri">longer active;</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">p) making sure that technical cross-pollination
occurs among the various WGs by</font>
<br><font size=2 face="Calibri">seeking frequent opportunities to hold
Area meetings; and</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">q) seeking opportunities to advertise and
promulgate the work of the Area by alerting</font>
<br><font size=2 face="Calibri">WG, BOF, and SIG chairs to opportunities
to publish results or participate in relevant</font>
<br><font size=2 face="Calibri">conferences...”</font><tt><font size=2>_______________________________________________<br>
CMC mailing list<br>
CMC@mailman.ccsds.org<br>
</font></tt><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cmc"><tt><font size=2>https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cmc</font></tt></a><tt><font size=2><br>
</font></tt>
<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>