|
Introduction to CCSDS |
The Consultative Committee for Space Data Systems (CCSDS) was formed in 1982 by letter of agreement, signed by responsible officials of the participating national and international space agencies
Since its formation, the CCSDS has developed and published many documents (“Recommendations for Space Data System Standards”, herein usually referred to as “CCSDS Standards”), the majority of which have become full international standards. Over 100 CCSDS documents are currently active and applicable in widespread use across the international space community. Note that CCSDS Recommended Standards may be adopted as the basis for international agreements, or they may be incorporated into local standards that form the controlling documentation for such agreements.
In 1990, Technical Committee 20 (TC 20) of the International Organization for Standardization (ISO) formed Subcommittee 13 (SC 13), Space Data and Information Transfer Systems. Recognizing CCSDS as a leading international authority in developing standards for space-related information technologies, ISO agreed that CCSDS has the primary responsibility for technical development of standards that are approved by ISO TC 20/SC 13.
The purposes of the CCSDS are contained in the Charter (above). Broadly, they are to provide an international forum in which the CCSDS agencies can discuss common space data communications and service-based needs and arrive through consensus at standard solutions to those needs, thereby increasing efficiency and interoperability among agencies, and decreasing costs
This Strategic Plan has been approved by the CCSDS Member Agencies. It is intended that the Strategic Plan should be updated whenever necessitated by changing events (or at least every 5 years) to redefine the organization’s current objectives, domains for standardization, and strategic goals. The Strategic Plan also serves to reaffirm the cooperative agreements entered into by the founding and continuing members of the CCSDS
CCSDS’ online Collaborative Work Environment (CWE) supports this Strategic Plan by providing organizational details, charters of each working group, project definitions and resource matrices, online polling, and a host of other collaborative tools designed to assist in document development and lead to better understanding of the CCSDS. The CWE is maintained by the CCSDS Engineering Steering Group, and is updated in real time as charters are approved.
| CCSDS Operating Concept |
The CCSDS executes its business in accordance with document CCSDS A02.1-Y-4 Organization and Processes for the Consultative Committee for Space Data Systems. Within the terms of that document, the CCSDS provides the environment and infrastructure whereby:
1. The international space community—the member and observer space agencies and their commercial partners—can openly discuss common problems associated with implementing space mission information and communication systems so as to identify where standard solutions will be beneficial.
2. Technical experts within the community can develop the necessary standards and practices. The resources needed for these activities are provided primarily by the participating agencies at levels commensurate with their individual requirements. Where mutual interests exist, the CCSDS will develop technical alliances with other organizations as appropriate.
3. The community can formally review and comment on those standards and practices as their development progresses.
4. The CCSDS Member Agencies can approve the publication of standards and practices when their review is complete and consensus is achieved.
5. The approved standards and practices are made available for adoption and use across the community.
In the process of developing CCSDS standards, the community
will, as a first priority, adopt existing standards and approaches rather than
developing something new. If an existing standard or innovative technical
approach cannot be adopted as is, the second priority is to adapt it to fit the
needs of the space community. As a final resort, when nothing exists that can
be adopted or adapted, the community will develop new technical approaches to
meet the needs of the spaceflight community. This is the basis of the CCSDS
mantra to “adopt/adapt/develop”, in that order.
Additionally, in providing these functions, the CCSDS is committed to:
- allowing the CCSDS participating agencies (at their individual discretion) to open the standardization process, on a voluntary basis, to all interested parties across their government, private sector, and academic space communities;
- using experimentation, prototyping, and demonstration as integral components of standards development;
- encouraging partnerships between space agencies and the commercial sector to produce commercial off-the-shelf (COTS) hardware and software so that the standards can be used to build space mission communication and information systems that are scalable, quick to integrate, low in cost, and interoperable among different users.
While the primary objective of CCSDS will always be to encourage cooperative spaceflight missions through interoperability of data and communications systems, there is a secondary objective of encouraging commercial development of standardized components to improve efficiency and reduce cost. As a result, the scope of CCSDS occasionally may include “intra-operability” between components of an agency’s spaceflight systems, as well as interoperability between agencies. This could be to support (in rare cases) application migration between agencies (by development of application programming interfaces) as well as commercialization of plug-in components with standardized system interfaces. While these are allowable CCSDS objectives for some projects, they will always be secondary in priority to the goal of interoperability to enable multinational spaceflight missions.
| CCSDS Target Missions and “CCSDS Conformance” | Standardization is widely recognized as a vehicle to stimulate the development of world markets. To help develop space as an international marketplace, CCSDS standards aim to support the data information, communications, and service needs of a wide, but not totally inclusive, set of space missions. Primary CCSDS target missions include civilian spacecraft and landed vehicles operating in Earth orbit, within the Earth-Moon system, in deep space, and on and around other Solar System bodies.
While no kind of mission—civil, military, commercial, robotic, piloted—is specifically excluded from the interests of CCSDS, it is recognized that some spacecraft provide specialized data-handling services that are well supported by their own user communities or by other standardization bodies. For example, commercial voice, data, and video broadcasting satellites may use their own transponder data communications protocols, and commercial Earth-observing satellites may use their own private data distribution protocols, yet they both may use CCSDS standards to support other parts of their mission infrastructure—such as Tracking, Telemetry, and Command (TTC) functions. As a natural consequence, CCSDS is constantly motivated to consider the establishment of formal and technical liaisons with other organizations as a means for expanding space data systems standardization on a worldwide basis.
CCSDS therefore aims to perform the necessary outreach to seek the widest possible set of target missions. There are multiple interfaces at which “CCSDS conformance” may be achieved by following defined CCSDS interface standards, protocol/information proformas and profile requirements lists. However, conformance with a single particular standard will not necessarily result in interoperability unless both parties to the data exchange also agree to use the same “stack” of underlying standards. | CCSDS Objective | The objective of the CCSDS is to harmonize and lead the worldwide standardization of space mission information and communication systems, thus promoting international cooperation and enabling these space systems to be effectively integrated with their terrestrial data communications and information systems counterparts.
| Rationale | CCSDS provides the means whereby space agencies can reach voluntary consensus on standardized solutions to common problems associated with the design of compatible space mission information and communication systems. The fruits of that consensus are made available across the space community in the form of new international standards, along with hardware and software (e.g., a future CCSDS Open Source Library) that facilitate their adoption. Standardization (through standardized products and COTS products) enhances the international exploration and exploitation of space by increasing the use and value of the information gathered, while simultaneously realizing significant savings in cost and development time for all participants.
| CCSDS Management, External Relations, and Outreach Strategic Goals | In order to maximize the benefits of standardization, CCSDS has as an objective to disseminate the results of its standardization activities and promote their worldwide adoption. This includes promotion of CCSDS standards within the member organizations’ programs and outreach towards other space communities. Tracking and reporting the infusion of the standards in space programs within member organizations also serves this purpose
CCSDS shall promote:
- the use of CCSDS standards within projects and technical support sections of the CCSDS Member Agencies;
- that CCSDS standards are adopted by—either in whole or in part—the missions of a large majority of all civil, military, and commercial spacecraft that are launched.
CCSDS facilitates adoption of its standards and support to its users by providing:
- online capabilities that give an expanded capability to support CCSDS users
- software implementations and tutorial information;
- information on benefits which would be gained as a result of adopting each CCSDS standard.
In order to increase the productivity and impact of the standardization activities, it is important to increase the number of agencies that actively contribute to the development of new standards in CCSDS by leveraging the agencies’ resources and expertise.
CCSDS will continue its strong relationships and ties with ISO to further the stature and pre-eminence of CCSDS standards in the international community
CCSDS has achieved greater international visibility by responding to requests for support to other governing and coordinating bodies on the topic of spaceflight. An example of this is the report that CCSDS provided to the United Nations Committee on the Peaceful Uses of Outer Space; the Working Group on the Long-term Sustainability of Outer Space Activities. CCSDS shall continue to provide responses to such requests, and will further seek out additional opportunities for similar outreach
In order to extend the CCSDS body of standards with sufficient lead time to keep pace with the new requirements of space missions to be flown in the coming decades, CCSDS shall conduct continuing outreach that will build liaisons with CCSDS stakeholders (space missions and space mission support organizations) as well as with other standardization organizations and with other space communities. The new requirements include:
- constellations of spacecraft in the vicinity of the Earth and the Moon;
- constellations of spacecraft in deep space;
- orbiting and in-situ landed vehicles deployed around and on other Solar System bodies;
- commercial and military missions;
- space- and ground-based cross support among an increasingly interdependent set of international users.
| CCSDS Standardization Concept | CCSDS exists to develop the necessary agreements that allow standard communications data-handling services to be exposed at the major interfaces between participating organizations. When such a standard service is offered by one organization and is used by another, an instance of CCSDS cross support has occurred. When information flows automatically across the interface so created in accordance with standard data exchanges or protocols under well-defined interoperable profiles, an instance of CCSDS interoperability has occurred.
It is a CCSDS core requirement that recommended standards and practices must be developed to facilitate interoperability and cross support.
In order to satisfy this requirement, CCSDS establishes technical areas for standardization. Although they are intended to be relatively stable entities, areas may be added or deleted in response to a changing space mission environment.
As shown in Figure 1, six technical areas form the current working structure of CCSDS. Each area contains narrowly chartered working groups (not shown here) that concentrate on the production of specific recommended standards and practices within the theme of that parent area.
Figure 1: CCSDS Technical Areas of Standardization
As shown in Figure 1, six technical Areas form the current working structure of CCSDS. Each Area contains narrowly chartered Working Groups that concentrate on the production of specific recommended standards and practices within the theme of that parent Area.
- The Spacecraft Onboard Interfaces Services area shall define the onboard data-handling interface between payloads or subsystems and their carrier spacecraft.
- The Space Link Services area shall define the data-handling interfaces between multiple free-flying spacecraft/landed elements, and between free-flying spacecraft/landed elements and their ground support networks.
- The Cross Support Services area shall define the data-handling interfaces between ground support networks and ground user facilities.
- The Mission Operations and Information Management Services area shall define the mission control application protocols and services that traverse the logical (end-to-end) interface between user facilities and payloads/subsystems in space, and between multiple ground-user facilities.
- The Space Internetworking Services area supports the Mission Operations and Information Management Services area and shall define the end-to-end data communications protocols and services that traverse interface between user facilities and payloads or subsystems in space.
- The Systems Engineering Area supports each of the other five areas and shall define the common or cross-cutting conventions and interfaces that support the end-to-end architecture.
| CCSDS High-Level Goals | Preface
The overall goal as expressed in the CCSDS Charter is the enabling of interoperable spaceflight missions by producing standards in the communications and data systems area. The strategic goals that follow are intended to be unique approaches to better enable that charter
Overall Strategic Goals
The CCSDS Mission Statement is “Advancing technology, with international agreement to use that technology”
In order to enable the next generation of spaceflight missions, CCSDS is aiming at technology evolution and innovation through the process of developing, validating, maintaining and promoting a body of unique space data systems standards, focusing on interoperability of space systems and cross-support between space organizations.
CCSDS shall keep pace with the new requirements of space missions to be flown in the coming decades for scientific, exploration, commercial, and defense purposes, as reflected in relevant roadmaps of participating agencies and inputs and recommendations of other organizations and bodies, like the Interagency Operations Advisory Group (IOAG), International Space Exploration Coordination Group (ISECG) and others.
CCSDS shall keep pace with technology advancements in the industry. While we respect and learn from requirements of current missions, future missions are the primary target of CCSDS standards. CCSDS strives to develop new interoperability capabilities, which will enable a new set of missions, some of which are not even yet envisioned.
Technical Strategic Goals
The strategic technical objectives and goals below are not intended be all-inclusive of ongoing CCSDS work, nor are they grouped by organization or teams within CCSDS; rather, they are intended to be the more strategic and high-level initiatives guiding the current and future direction of the CCSDS as a whole. Grouping of the goals naturally reflects the direction of the CCSDS organization and the common-sense breakdown of technical disciplines
TECHNICAL GOAL 1
To define innovative, secure, widely applicable
communication standards and related architectures that facilitate
interoperability and cross support and meet the challenges and anticipated
needs of the future projects, including:
- the use of higher frequency bands (radio frequency
and optical);
- the achievement of higher data rates and volumes
with simultaneously greater spectral efficiency through more capable protocols,
modulation, coding, and compression techniques;
- the achievement of higher accuracy distance and
velocity measurements of near-Earth and deep-space missions;
- the use of secure communication protocols and
links to protect associated systems and information flows
TECHNICAL GOAL 2
To define a complete suite of interoperable, cross support planning, data delivery, and control service interfaces, implementing an efficient management of the cross support services, providing end-to-end solutions, and meeting mission challenges, including:
- integrated mission planning for combined interagency operations taking into account resource needs;
- simplification and improved efficiency of cross support service request, delivery, and governance;
- call-up of international cross support during spacecraft emergencies;
- a complete suite of cross support interfaces supporting forward- and return-data transfers, radiometric data, monitor data, and service control;
- cross support file transfer operations such as: radiometric, Delta Differential One-way Ranging (Delta-DOR), off-line data, and space file transfer.
TECHNICAL GOAL 3
To define the full suite of mission operations standard functions and services to enable ground and onboard interoperability at the Application Layer level in support of complex joint collaborative missions and of the standardization of the corresponding ground data systems, in order to meet the needs of future projects, including:
- implementation of multi-mission spacecraft and instrument mission operations services;
- exchange of mission plans between cooperating agencies;
- conjunction assessment, navigation, tracking, and trajectory prediction;
- interoperability of robotic systems for cross-agency support
TECHNICAL GOAL 4
To define an integrated set of space internetworking standard services in support of end-to-end communications between applications for the full scope of future joint collaborative missions, covering the entire Solar System, and meeting future project needs, including:
- jointly conducted human and robotic operations;
- management of space-to-space and direct-to-Earth links as part of the network;
- sensor web and other innovative technologies for low Earth orbit (LEO) operations;
- application to the space domain of well-established internetworking technologies;
- fully automated routing across networks end-to-end;
- end-to-end file and message transfer operations.
TECHNICAL GOAL 5
To define reference onboard communications architectures and services supporting efficient data-handling applications and future system evolution, including:
- standardized avionics architectures;
- advanced technologies, such as wireless communications and software-defined radios;
- innovative approaches such as plug-and-play approaches and electronic data sheets;
- onboard autonomy capabilities.
TECHNICAL GOAL 6
To define cross-cutting functions and end-to-end system architectures, in support of interoperability and cross support, overarching and underpinning the above goals, and facilitating addressing global challenges, including:
- cyber security;
- reference system architectures;
- information models and architectures;
- systems-of-systems interoperability;
- CCSDS support services and capabilities.
|
CCSDS Area Objectives and Goals
SYSTEMS ENGINEERING AREA | The objective of the Systems Engineering Area (SEA) is to address system-wide architectural and engineering topics that are so pervasive that they span over all, or several, other CCSDS areas. This work includes development of specific standards and guidelines, development of system architectures and models, coordination/collaboration with other areas, and otherwise supporting CCSDS and CMC engineering and operational goals.
The SEA system architecture tasks include end-to-end reference architecture, architecture analysis and description methods, and related cross cutting terminology topics. The SEA security architecture and standards are to be used by other CCSDS areas requiring security guidance and services. The Delta-DOR services touch upon the Cross Support Services (CSS) and Space Link Services (SLS) areas, and Mission Operations and Information Management Services (MOIMS) may be involved in planning for use of these services. The information architecture and registry services also cross cut MOIMS, CSS, Space Internetworking (SIS), and other Services. Extensible Markup Language (XML) standards and guidelines and other special cross-cutting topics that are guided by SEA affect all of the other areas. As system or information architecture standards are developed, SEA will coordinate with the other CCSDS areas and working groups to develop approaches that align with CCSDS goals for interoperability and cross support. The strategic goals of the SEA are listed below.
| Click Here to View the SYSTEM ENGINEERING GOALS |
|
MISSION OPERATIONS AND INFORMATION MANAGEMENT SERVICES AREA | The objective of the MOIMS area is to address all application-level standards and their associated information management that are required to operate spacecraft and robots, and their ground system in response to mission requirements and any data handling and archival systems making use of the information gathered by the mission. The focus of this area is primarily on the Mission Operations (MO) data and services that are required for preparing and conducting space mission operations and the archival systems maintaining the information obtained. These application-level standards will facilitate the availability of plug-in components exposing standard service interfaces, which will allow a simplified and economical assembly of both space and ground segments and enable interoperability and operations automation. Consistency at data and service level within MOIMS shall be achieved by adherence of new standards to the MO Service Framework and the Reference Model for Open Archival Information Systems (OAIS).
The MOIMS area needs to coordinate with:
- the CSS area that is responsible for the interfaces between the mission control systems and the ground network/stations, including for ground station planning and scheduling;
- the SEA area on matter regarding the CCSDS System Architecture, Security and XML guidelines;
- the SOIS area on matter related with potential MO services on-board;
- all areas, including within MOIMS, for the provision of consultancy and support on the potential use of the MO Service Framework;
- the SANA on matter regarding practices for registries and repositories.
The strategic goals of the MOIMS area are listed below.
Click Here to View the MISSION OPERATIONS AND INFORMATION MANAGEMENT SERVICES AREA GOALS |
CROSS SUPPORT SERVICES AREA | The CSS area addresses how the services of an agency’s TTC network are made available to another agency’s mission spacecraft. This includes addressing data transfer services and their management. The data transfer services involve both space link (to/from TTC network ground station to mission spacecraft) and terrestrial link (to/from TTC network ground station to the mission ground data system). The space link data transfer encoding/protocol schemes are subject to the SLS area and are not defined by the CSS area. The terrestrial data transfer services, with regard to transfer mission data and observations such as ground station tracking data, are addressed by the CSS area. The management of both the space link and data transfer services is also addressed by the CSS area. Proper definitions of the services and management of these services depends on a reference architecture definition and also agreed, internationally recognized terms for the functional components of this architecture. The terrestrial data transfer services and management data format definitions may be incorporated into mission operations end-to-end recommendations of the MOIMS area. The strategic goals of the CSS area are presented below.
Click Here to View the CROSS SUPPORT SERVICES AREA GOALS |
SPACECRAFT ONBOARD INTERFACE SERVICES AREA | The objective of the Spacecraft Onboard
Interface Services (SOIS) area is to address the services and protocols used by
communication networks within a spacecraft and within close proximity of the
spacecraft. These are applicable to the core spacecraft platform as well as to
the interfaces with both internal and external payloads and extra-vehicular
activities. SOIS also covers the use of wireless technology for ground, space
and planetary surface communication within the spacecraft and within close
proximity to the spacecraft.
The long-term goal of the SOIS area is to encourage the standardization of interfaces and on-board data exchange mechanisms such that spacecraft building blocks, which may range from individual sensors and actuators to complete units, may be developed and utilized with minimum or no change.
As part of this objective, the way in which spacecraft device and interface information is presented is being analyzed and standards are being proposed for specifying such information in electronic, machine-readable format. This aspect is intended to reduce the effort required for spacecraft development and testing by automating the process of code generation and database import. The area will also evaluate other opportunities which may benefit from international standards.
The SOIS area needs to coordinate the following:
- the seamless extension of CCSDS SLS and SIS into the spacecraft by developing and deploying standardized onboard data communication services and data exchange mechanisms;
- the use of terrestrial wireless technology
- the seamless coupling of SOIS with the ground services defined by the MOIMS area;
- the definition of an architecture interface standardization (SEA), following also in particular the European initiatives European Coordination for Space Standardization (ECSS), SAVOIR (Space Avionics Open Interface Architecture) and relevent U.S. architecture groups. (NASA's Core Flight System (cFS) and Future Airborne Capability Environment (FACE) ).
- the adoption of SEA security recommended standards and practices;
- the SANA recommended practices for registries and repositories.
The strategic goals of the SOIS area are presented below.
Click Here to View the SPACECRAFT ONBOARD INTERFACE SERVICES AREA GOALS |
SPACE LINK SERVICES AREA | The objective of the SLS area is to address all of the point-to-point communications links and protocols that interconnect a spacecraft with its ground-support system, or with another spacecraft, by developing standards for efficient and reliable space link communications systems addressing nominal as well as emergency scenarios. Specific attention is given by SLS to needs for higher data rates and better link performances, standard security mechanisms, the growing presence and importance of space-to-space links as well as lower cost, mass, and power.
SLS area objectives focus on Layers 1 & 2 (of the Open Systems Interconnection [OSI] protocol stack)—i.e., the Physical Layer and the Data Link Layer. This means that SLS concentrates in particular on radio-frequency and optical systems, modulation, synchronization and channel coding, and
data link protocols, for both long-haul (e.g., spacecraft-to-ground) and proximity links (e.g., orbiter-to-lander). Moreover SLS concentrates also on two additional functions essential on the space link: data compression for end-to-end data transfer optimization, and ranging for accurate orbit determination.
The SLS area needs to coordinate:
- with CSS for the identification of relevant parameters for service management;
- with CSS for the inner behavior (i.e., the implementation aspects and not the terrestrial interface characteristics) of the CSTS to be made available to other agencies;
- with MOIMS and CSS if the need of standardized exchange of meteorological and orbital data will be required for optical communications;
- with SEA for Delta-DOR issues;
- with SEA for development, adoption and integration of security-related recommended standards and practices;
- with SIS for layering interfaces and reliability;
- the SANA-recommended practices for registries and repositories.
The strategic goals of the SLS area are presented below.
Click Here to View the SPACE LINK SERVICES AREA GOALS |
SPACE INTERNETWORKING SERVICES AREA | The objective of the SIS area is to address the communications services and protocols supporting end-to-end communications among applications, particularly where those communications may span multiple heterogeneous physical and data link technologies. Areas addressed by SIS include the networking infrastructure to support application-to-application communication onboard a single spacecraft, communications among multiple spacecraft, and communications between space-based applications and their counterparts on Earth and/or other planetary bodies. Specifically, note that the Service Catalog 2 of the Interagency Operations Advisory Group (IOAG) "identifies the cross-support service types that should be provided by the ground tracking assets operated by the IOAG member agencies participating in the Solar System Internetworking (SSI) based on DTN [Delay-Tolerant Networking] and / or IP [Internet Protocol] technologies." The SIS area focuses on these service types and related services. As such, the SIS area deals with communication services and protocols that are independent of specific link technology (as a lower layer bound) and independent of application-specific semantics (as an upper bound). Thus the SIS area covers essentially the Network through Transport Layers of the OSI reference model. The SIS area also develops application support protocols where the services provided are intended to operate over an internetworked infrastructure. An example of such an application support protocol is the Asynchronous Messaging Service (AMS), which is intended to be invoked by applications to effect message exchange. The Bundle Protocol, a central element of DTN, uses the underlying communication and infrastructure services provided by the SLS and SOIS areas and any other onboard networks, and provides the networked connectivity needed by applications developed in other CCSDS areas such as MOIMS and SOIS. This enables the SIS services to provide hardware-independent mechanisms for identifying end systems and to provide communications services that allow users to operate the same way whether communication is over a single data link layer or over multiple hops. The suite of capabilities developed by the SIS area, centered on the DTN architecture, accommodates all ranges of delay, interactivity, and directionality, although not all protocols are appropriate for all environments.
The
SIS area needs to coordinate the following:
- SIS security mechanisms need to be consistent with other security mechanisms at other layers in the stack, such as those deployed at the link layer.
- The MOIMS area is developing Mission Operations data and services that might, depending on mission design choices, need to be deployed over SIS infrastructure. SIS needs to coordinate with MOIMS to ensure that such missions can efficiently use MOIMS data and services over SIS internetworks.
- The internetworking technologies developed by SIS need to be managed during operations. Since the deployed internetworks will typically span agency boundaries, the management mechanisms need to be coordinated with CSS for ground station interfaces and with MOIMS for application-level services required for operations, in particular for network management.
- The SOIS area is advocating for the use of wireless technologies for both onboard and inter-spacecraft communication. SIS needs to coordinate with SOIS and provide protocols that support internetworked communication over a mix of wireless technologies and/or heterogeneous wireless/wired scenarios.
- SOIS also develops a set of onboard services that SIS can leverage (e.g. file and packet storage services). SIS needs to coordinate with SOIS to ensure that SIS requirements are reflected in the SOIS designs.
- SIS coordinates the internetworking mechanisms it develops, where reasonable, with similar mechanisms and capabilities defined for use with the terrestrial Internet, and in particular defined by the Internet Engineering Task Force (IETF) and Internet Research Task Force (IRTF). This coordination is nominally achieved by operating the Bundle Protocol over the terrestrial Internet, and other networks based on the Internet architecture, as if these networks were underlying link services. By coordinating with these terrestrial standards in this way, SIS ensures that CCSDS' needs are addressed in the terrestrial standards and that the terrestrial protocols can be made to interoperate with the CCSDS versions. This will allow CCSDS to, for example, leverage commercially-available implementations of Bundle Protocol routers on the ground.
Click Here to View the SPACE INTERNETWORKING SERVICES AREA GOALS |
CCSDS MANAGEMENT COUNCIL | The objective of the CCSDS Management Council (CMC) is to provide the executive management oversight of the organization. The CMC is responsible for staying technically and politically informed about important long-term issues in the field of international space mission cross support and for keeping an eye on the “big picture” of the CCSDS program of work. The CMC provides oversight for the whole CCSDS technical organization and of support organizations like the Secretariat and the SANA. The technical work of the SANA is specifically guided by the SANA Steering Group (SSG).
The objective of the CCSDS Management Council (CMC) is to provide the executive management oversight of the organization. The CMC is responsible for staying technically and politically informed about important long-term issues in the field of international space mission cross support and for keeping an eye on the “big picture” of the CCSDS program of work. The CMC provides oversight for the whole CCSDS technical organization and of support organizations like the Secretariat and the SANA. The technical work of the SANA is specifically guided by the SANA Steering Group (SSG).
Click Here to View the CCSDS MANAGEMENT COUNCIL GOALS |
|
|