[CESG] Re: [Cesg-all] Results of Recent CMC Polls

[Shames, Peter M (312B)]

Dear CMC members,

In order to resolve the issues raised in this poll, all of the references to DLR, JAXA, and UKSA in relationship to any level of support for the proposed tasks in the re-start of the SEA SAWG, except for JAXA support of the RMP,  have been removed.

If this now meets the intent of these provisions please do what is necessary to authorize the re-start of this CCSDS Working group.

Thank you.

Best regards, Peter Shames



From: <cesg-all-bounces at mailman.ccsds.org<mailto:cesg-all-bounces at mailman.ccsds.org>> on behalf of CCSDS Tech Support <ccsds_techsupport at aiaa.org<mailto:ccsds_techsupport at aiaa.org>>
Date: Wednesday, January 13, 2016 at 7:28 PM
To: CMC <cmc at mailman.ccsds.org<mailto:cmc at mailman.ccsds.org>>
Cc: CCSDS Engineering Steering Group - CESG All <cesg-all at mailman.ccsds.org<mailto:cesg-all at mailman.ccsds.org>>
Subject: [Cesg-all] Results of Recent CMC Polls

CMC E-Poll Identifier: CMC-P-2015-12-002 Request to re-start the System Architetcure Working Group (SEA-SA)

Results of CMC poll beginning 07 December 2015 and ending 21 December 2015:

              Adopt:  6 (66.66%) (CNES, CNSA, CSA, ESA, INPE, NASA)
              Adopt Provisionally:  3 (33.33%) (DLR, JAXA, UKSA)
              Reject:  0 (0%)
              Reject with Comments:  0 (0%)

Results are based on responses from 9 out of 11 members (81.81%).

No response was received from the following Agencies:

             ASI
             FSA

Provisions

DLR - can not provide any extra resources at the moment for this WG.
JAXA - agrees with the WG re-start and provide resource for the Registry Management Policy. However, JAXA could not find an appropriate resource to the CCSDS Mission Operations (Application Layer) Architecture.
UKSA -  cannot currently commit any additional resources to this activity


Secretariat Interpretation of Results:  Adopted Provisionally
Resulting CMC Resolution:               CMC-R-2015-12-008
Inferred Secretariat Action:               Once Provisions Met, Approve Charter and Projects, Update Mailing Lists and CWE Org Chart.

* * * * * * * * * * * * * * * * * * * *

CMC E-Poll Identifier: CMC-P-2015-12-003 Approval of Reclaiming Simulator SCIDs from the Registry

Results of CMC poll beginning 08 December 2015 and ending 22 December 2015:

              Adopt:  7 (77.77%) (CNSA, DLR, ESA, INPE, NASA, UKSA)
        Adopt Provisionally:  2 (33.33%) (CNES, JAXA)
              Reject:  0 (0%)
              Reject with Comments:  0 (0%)

Results are based on responses from 9 out of 11 members (81.81%).

No response was received from the following Agencies:

             ASI
             FSA

Provisions

CNES - agrees on the following:
- the first action should be for all agencies to return the unused codes as it is obvious there are many (SC no longer in operations) ; this is considered the most efficient action to recover SCIds.
- no SCId should be allocated to simulators from now.
CNES agrees on the principle but will put a condition on the assigned GSCIds for simulators:
- when the list of those affected is provided by SANA, some time is needed to run a coordination with the projects and SANA should only remove these SCIds when the Agency representative will confirm agreement.
- as simulators are mainly version 1 SCIds, with more margins for new allocation, the additional delay is estimated acceptable ; however, CNES will first process the version 2 Ids, if any.

JAXA - agrees on the resolution. However, coordination on reclaiming SCIDs which have been assigned for satellites under development take sometime, and this circumstance should be taken into account.

Secretariat Interpretation of Results:  Adopted Provisionally
Resulting CMC Resolution:               CMC-R-2015-12-009
Inferred Secretariat Action:              Once Provisions Met, SANA Reclaim Simulator SCIDs.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/cesg/attachments/20160201/5262c0a1/attachment.html>