[CMC] [EXTERNAL] Formal Request for Candidates - MOIMS Deputy Area Director
Townes, Stephen A (US 9000)
stephen.a.townes at jpl.nasa.gov
Thu Oct 1 21:08:42 UTC 2020
Dear CMC Members,
NASA is pleased to nominate Theresa Beech for the position of Deputy Area Director for the MOIMS Area. Theresa’s information and qualifications are attached.
Stephen A. Townes, PhD
Chief Technologist, Interplanetary Network Directorate
NASA/Jet Propulsion Laboratory
California Institute of Technology
mobile: +1 818-731-4614
desk: +1 818-354-7525
From: CMC <cmc-bounces at mailman.ccsds.org> on behalf of "Blackwood, Michael D via CMC" <cmc at mailman.ccsds.org>
Reply-To: "Blackwood, Michael D" <MBlackwood at asrcfederal.com>
Date: Tuesday, September 15, 2020 at 9:48 AM
To: "'cmc at mailman.ccsds.org'" <cmc at mailman.ccsds.org>
Cc: CCSDS Engineering Steering Group - CESG Exec <cesg at mailman.ccsds.org>
Subject: [EXTERNAL] [CMC] Formal Request for Candidates - MOIMS Deputy Area Director
Dear CMC Members,
As was announced by Margherita di Giulio earlier this year, Brigitte Behal will be stepping down from her position as Deputy Area Director of the MOIMS Area at the fall CCSDS Technical Meetings. There is now a need for a new MOIMS DAD. This email if a formal invitation for the CMC to nominate candidates for this position. Per CCSDS A02.1-Y-4, Organization and Processes for the Consultative Committee for Space Data Systems, Section 184.108.40.206, general qualifications of a DAD 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.
A candidate for selection as an AD (or deputy AD) must be recognized as leading technical expert in the field covered by that Area and must have extensive prior experience leading a specific standards development task within the CCSDS, such as having served as a WG chair or deputy chair.”
Please note that the CCSDS procedures manual states that an AD and DAD cannot be from the same agency. Therefore, candidates for this position may not represent ESA. A more formal statement about the role of the DAD, extracted from the Organization and Processes manual is listed below. It may be helpful to review this in considering candidates for this role.
Please submit you nominations for this position to the Secretariat by 13 October 2020. A brief summary of the candidates qualifications will be much appreciated.
W: 301-837-3901 | michael.blackwood at asrcfederal.com<mailto:michael.blackwood at asrcfederal.com>
7515 Mission Drive, Seabrook, MD 20706
ASRC Federal | Customer-Focused. Operationally Excellent.
CCSDS A02.1-Y-4, Organization and Processes for the Consultative Committee for Space Data Systems, April 2014
220.127.116.11.4 Deputy Area Director Responsibilities
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.
18.104.22.168.3 Area Director Responsibilities
An Area Director is responsible for the work done in his or her WGs, BOFs, and SIGs and is specifically responsible for the following:
a) being a member of the CESG as the single representative of the CCSDS technical Area;
b) screening all proposals to form new WGs that are brought forward by BOFs to make sure that they are supported by required documentation and their technical focus is vectored toward the goals and objectives of CCSDS;
c) making recommendations to the CESG concerning approval for the chartering and formation of WGs;
d) ensuring that CCSDS documents are properly categorized and that they embody the content and quality expected of documents of their type;
e) making recommendations to the CESG for the progression of WG documents as they approach key decision gates along the various document tracks;
f) demonstrating and certifying that formal review procedures have been properly followed prior to recommending the advancement of a document;
g) communicating the dates of CESG meetings to the WG, BOF, and SIG chairs so that they may schedule the completion of their work prior to this time;
h) notifying the WG, BOF, and SIG chairs as to how and when their work is to be presented to the AD for review;
i) deciding if Area meetings are to be held, and if so, setting the date, location, and agenda for each Area meeting (it is strongly recommended that periodic face-to-face co-located meetings of the WGs, BOFs, and SIGs in a particular Area should be held to maximize opportunities for cross-pollination of ideas);
j) chairing Area meetings, ensuring that every WG, BOF, or SIG presents its work in a satisfactory manner and that Area decisions are made through a process of consensus;
k) ensuring that all Area work follows the set of architectural principles agreed to by the CESG and is properly synchronized with work in other areas and with the smooth evolution of the large installed base of CCSDS-compatible mission-support infrastructure;
l) working with the WG, BOF, and SIG chairs to prepare detailed reports of overall status, progress and problems for presentation at CESG meetings (as necessary, the AD may request specific WG, BOF, or SIG chairs to attend CMC meetings to discuss difficult issues);
m) verifying that all Normative Track documents are subject to the proper process of formal agency review by the WG chair;
n) maintaining the Area master-tracking list of relevant specifications as they progress through the standardization tracks;
o) making recommendations to the CESG to reconvene a WG to refresh a standard that has been finalized and deployed into operational use, and for which the WG is no longer active;
p) making sure that technical cross-pollination occurs among the various WGs by seeking frequent opportunities to hold Area meetings; and
q) seeking opportunities to advertise and promulgate the work of the Area by alerting WG, BOF, and SIG chairs to opportunities to publish results or participate in relevant conferences.
The preceding message (including attachments) is covered by the Electronic Communication Privacy Act, 18 U.S.C. sections 2510-2512, is intended only for the person or entity to which it is addressed, and may contain information that is confidential, protected by attorney-client or other privilege, or otherwise protected from disclosure by law. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error and destroy the original message and all copies.
-------------- next part --------------
An HTML attachment was scrubbed...
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 16878 bytes
More information about the CMC