Mission Operations and Information Management Services Area

Mission Operations and Information Management Services Area The objective of the Mission Operations and Information Management Services (MOIMS) Area is to address all of the flight execution phase applications that are required to operate the spacecraft and its ground system in response to mission objectives, and their associated detailed information management standards and processes. The focus of this Area is primarily on the “mission operations” functions that occur on a timescale driven by the flight path of the space vehicle. In many cases a dedicated community conducts these mission operations, while “mission utilization” occurs on a timescale that is convenient for users and is often conducted by a separate community. The MOIMS Area ensures that application standards exist which facilitate the smooth transition of space mission information between the “mission operations” systems and the “mission utilization” systems.


 CCSDS.publicationViewer - VisualWebPart1

Currently 48 Books Listed
Navigation Data—Definitions and Conventions. Green Book. Issue 3. May 2010.
This Report contains technical material to supplement the CCSDS Recommended Standards for spacecraft navigation data. The topics covered include radiometric data content, spacecraft ephemeris, planetary ephemeris, tracking station locations, coordinate systems, and attitude data. This Report deals explicitly with the technical definitions and conventions associated with interagency cross-support situations involving the transfer of ephemeris, tracking, and attitude data. The current issue brings the Green Book up to date with the current issue of Orbit Data Messages (CCSDS 502.0-B-2) as well as the new Recommended Standards for Tracking Data Message and Attitude Data Messages (CCSDS 503.0-B1 and CCSDS 504.0-B-1, respectively).
Navigation Data Messages Overview. Green Book. Issue 1. December 2015.
This Informational Report contains background and explanatory material to supplement the CCSDS Recommended Standards for spacecraft navigation data.
Orbit Data Messages. Blue Book. Issue 2. November 2009.
The Orbit Data Message (ODM) Recommended Standard specifies message formats for use in transferring spacecraft orbit information between space agencies and commercial or governmental spacecraft operators. Issue 2 defines a new message, the Orbit Mean-Elements Message (OMM), and adds capabilities to the messages specified in the original issue. The current version of this document contains all updates through technical corrigendum 1, dated May 2012.
Technical Corrigendum 1 to CCSDS 502.0-B-2, Issued November 2009. Blue Book. Issue 2 Cor. 1. May 2012.
This Technical Corrigendum documents changes to CCSDS 502.0-B-2, Orbit Data Messages (Blue Book, Issue 2, November 2009).
Orbit Data Messages V2.0 Test Plan/Report. Yellow Book - Reports and Records. Issue 1. May 2010.
This report documents the prototype testing conducted on the CCSDS Orbit Data Messages (ODM), CCSDS 502.0-P-1.1.
Tracking Data Message. Blue Book. Issue 1. November 2007.
The Tracking Data Message (TDM) Recommended Standard specifies a standard message format for use in exchanging spacecraft tracking data between space agencies. The current version of this document contains all updates through technical corrigendum 1, dated September 2010.
Technical Corrigendum 1 to CCSDS 503.0-B-1, Issued November 2007. Blue Book. Issue 1 Cor. 1. September 2010.
This Technical Corrigendum documents changes to CCSDS 503.0-B-1, Tracking Data Message (Blue Book, Issue 1, November 2007).
Attitude Data Messages. Blue Book. Issue 1. May 2008.
The Attitude Data Messages Recommended Standard specifies two standard message formats for use in transferring spacecraft attitude information between space agencies. The current version of this document contains all updates through technical corrigendum 1, dated July 2015.
Corrigendum 1 to CCSDS 504.0-B-1, Issued May 2008. Blue Book. Issue 1 Cor. 1. July 2015.
This Corrigendum documents changes to CCSDS 504.0-B-1, Attitude Data Messages (Blue Book, Issue 1, May 2008).
XML Specification for Navigation Data Messages. Blue Book. Issue 1. December 2010.
The XML Specification for Navigation Data Messages Recommended Standard describes an integrated XML schema set that is suited to interagency exchanges of navigation data messages.
Conjunction Data Message. Blue Book. Issue 1. June 2013.
This Recommended Standard for Conjunction Data Message (CDM) specifies a standard message format for use in exchanging spacecraft conjunction information between data originators of conjunction assessments, satellite owner/operators, and other authorized parties. Such exchanges are used to inform satellite operator(s) of conjunctions between objects in space to enable consistent warning by different organizations employing diverse conjunction assessment techniques. The current version of this document contains all updates through technical corrigendum 1, dated June 2018.
Corrigendum 1 to CCSDS 508.0-B-1, Issued June 2013. Blue Book. Issue 1 Cor. 1. June 2018.
This Technical Corrigendum documents changes to CCSDS 508.0-B-1, Conjunction Data Message (Blue Book, Issue 1, June 2013).
Pointing Request Message. Blue Book. Issue 1. February 2018.
This Recommended Standard defines the Pointing Request Message (PRM), a standardized format that allows space agencies and operators to exchange information about requested (sequences of) changes to the attitude of the spacecraft or to an articulated spacecraft component.
Mission Operations Services Concept. Green Book. Issue 3. December 2010.
This CCSDS Informational Report presents a set of concepts, reference architecture, and service framework for Spacecraft Monitoring and Control (SM&C). The standardization of the SM&C interfaces by means of a service-oriented architecture will allow development of standardized SM&C infrastructure systems for seamless transfer of data across systems, and adoption of commercial-off-the-shelf applications for monitoring and control purposes. The result will be significant savings in the development of the flight components and the ground segment of future space missions.
Mission Operations Reference Model. Magenta Book. Issue 1. July 2010.
This Recommended Practice defines a mission operations reference model, which provides a common basis for coordinating the development of CCSDS Recommended Standards for mission operations service specifications and serves as a reference to maintain the consistency of those Recommended Standards.
Mission Operations Message Abstraction Layer. Blue Book. Issue 2. March 2013.
The Mission Operations Message Abstraction Layer (MAL) Recommended Standard defines the MAL in conformance with the service framework specified in the Mission Operations Services Concept Green Book (CCSDS 520.0-G-3). The current issue addresses the request to add a slight restriction to the MAL data model regarding polymorphism. In addition the WG took the opportunity to make a few additional changes: external data type specifications such as XML Schemas can now be used; XML is being moved to the SANA registry; type short forms are now integers rather than strings; optional fields in composites are now shown; lists are now a template rather than explicit types; unsigned integer and File data types have been added.
Mission Operations Common Object Model. Blue Book. Issue 1. February 2014.
This Recommended Standard defines the Mission Operations (MO) Common Object Model (COM) in conformance with the service framework specified in annex B of Mission Operations Services Concept (CCSDS 520.0-G-3).
Mission Operations Monitor & Control Services . Blue Book. Issue 1. October 2017.
This Recommended Standard defines the Mission Operations Monitor and Control services in conformance with the service framework specified in the Mission Operations Services Concept Green Book (CCSDS 520.0-G-3).
Mission Operations Message Abstraction Layer--JAVA API. Magenta Book. Issue 1. April 2013.
This Recommended Practice defines a Java API for the Mission Operations (MO) Message Abstraction Layer (MAL) specified in CCSDS 521.0-B-2.
Mission Operations--MAL Space Packet Transport Binding and Binary Encoding. Blue Book. Issue 1. August 2015.
This Recommended Standard defines the binding between the Mission Operations (MO) Message Abstraction Layer (MAL) specified in CCSDS 521.0-B-2 and the Space Packet Protocol specified in CCSDS 133.0-B-1. This binding allows MO Services to use the Space Packet Protocol as messaging technology.
Mission Operations--Message Abstraction Layer Binding to TCP/IP Transport and Split Binary Encoding. Blue Book. Issue 1. November 2017.
This CCSDS Recommended Standard specifies a binding of the Mission Operations Message Abstraction Layer (MAL) to TCP/IP using a split binary encoding for MAL data types.
Mission Operations--Message Abstraction Layer Binding to HTTP Transport and XML Encoding. Blue Book. Issue 1. June 2018.
This Recommended Standard specifies the binding between the Mission Operations (MO) Message Abstraction Layer (MAL) and the Hypertext Transfer Protocol (HTTP) and defines an XML encoding for MAL data types.
Mission Planning and Scheduling. Green Book. Issue 1. June 2018.
This Informational Report documents mission planning scenarios, use cases, and deployment architectures relevant to the creation of standards for mission planning and scheduling.
Telerobotic Operations. Green Book. Issue 1. November 2016.
This CCSDS Informational Report contains overview and descriptive material supporting analysis, requirements, descriptions of use, scenarios, etc., pertinent to the development of standards that support the safe, collaborative operation of mixed teams of human and robotic assets in the exploration of space.
Correlated Data Generation. Orange Book. Issue 1. July 2015.
This CCSDS Experimental Specification specifies a method for correlated data generation through the use of data acquired from diverse channels.
Space Data Systems Operations with Standard Formatted Data Units: System and Implementation Aspects. Green Book. Issue 5. February 1987.
This Informational Report concerns space data systems operations with Standard Formatted Data Units (SFDUs). It explains the rationale for operations with SFDUs, the initial operational requirements for SFDUs, and the major benefits to be expected from operations with SFDUs. The CCSDS conducts periodic reconfirmation reviews of its publications to assure their continued relevance. This Informational Report has been reconfirmed through May 2018.
Standard Formatted Data Units — Structure and Construction Rules. Blue Book. Issue 2. May 1992.
This Recommended Standard defines Standard Formatted Data Unit (SFDU) structures that will handle some of the problems of digital data interchange and several construction rules that will limit the SFDUs to a practical set that can exist in an open data system environment.
Standard Formatted Data Units — A Tutorial. Green Book. Issue 1. May 1992.
This Informational Report explains the rationale of the Standard Formatted Data Unit (SFDU) concept and outlines the Structure and Construction Rules with the help of examples. It supports the main SFDU Recommended Standard, CCSDS 620.0-B-2. The CCSDS conducts periodic reconfirmation reviews of its publications to assure their continued relevance. This Informational Report has been reconfirmed through May 2018.
Standard Formatted Data Units — Referencing Environment. Blue Book. Issue 1. May 1997.
This Recommended Standard defines multiple standard "file pointer" mechanisms that can be embedded into other data structures for the purpose of identifying and annotating a collection of files. It provides several transportable directory/file naming functionalities that may be used for data exchange with disks, tapes, and networks. The form of these "file pointer" mechanisms is based on the Parameter Value Language (PVL) Recommended Standard (CCSDS 641.0-B-2). They may be used with the CCSDS data packaging standard known as Standard Formatted Data Units (CCSDS 620.0-B-2), or they may be used independently. The CCSDS conducts periodic reconfirmation reviews of its publications to assure their continued relevance. This Recommended Standard has been reconfirmed through May 2018.
Standard Formatted Data Units — Control Authority Procedures. Blue Book. Issue 1. June 1993.
This Recommended Standard defines the responsibilities that must be assumed and the services that must be provided by the participating CCSDS Agencies in order to facilitate the creation and operation of the Control Authority organization. The primary function of this organization is to register and disseminate data description information. The CCSDS conducts periodic reconfirmation reviews of its publications to assure their continued relevance. This Recommended Standard has been reconfirmed through May 2018.
Standard Formatted Data Units — Control Authority Procedures Tutorial.. Green Book. Issue 2. November 1994.
This Report describes the Control Authority (CA) organization from both an implementer's and a user's perspective. This document serves as a companion document to Control Authority Procedures (CAP), CCSDS 630.0-B-1, and Control Authority Data Structures (CADS), CCSDS 632.0-B-1, and as such is intended to provide a tutorial for the procedures and services identified in the CAP and CADS Recommended Standards, background to assist in the effective implementation of the CAP and CADS Recommended Standards, and rationale and requirements for the CA organization. The CCSDS conducts periodic reconfirmation reviews of its publications to assure their continued relevance. This Informational Report has been reconfirmed through May 2018.
Standard Formatted Data Units — Control Authority Data Structures. Blue Book. Issue 1. November 1994.
This Recommended Standard extends the standardization of the Standard Formatted Data Unit (SFDU) concept in support of the digital transfer of space-related information. It specifies standards for expressing selected data description attributes and for their packaging with the data description. The resulting packages, called Control Authority Data Structures (CADS), are used to submit data descriptions to Control Authorities for registration and to disseminate data descriptions from Control Authorities. The CCSDS conducts periodic reconfirmation reviews of its publications to assure their continued relevance. This Recommended Standard has been reconfirmed through May 2018.
Parameter Value Language Specification (CCSD0006 and CCSD0008). Blue Book. Issue 2. June 2000.
The Parameter Value Language (PVL) Recommended Standard defines a human-readable, machine-processable language for naming and expressing data values. This update to the first issue of the Recommended Standard extends the PVL character set definitions to include the G1 set of ISO 8859-1 to support use of accented characters used in many languages. It also includes some clarifications and corrections to the original issue, including preservation of statement order within an object, and it updates the document style for consistency with current CCSDS style guidelines. Changes from the previous issue are flagged with change bars in the outside margin and summarized in the Document Control section (page v). The CCSDS conducts periodic reconfirmation reviews of its publications to assure their continued relevance. This Recommended Standard has been reconfirmed through May 2018.
Parameter Value Language — A Tutorial. Green Book. Issue 2. June 2000.
This Informational Report describes the Parameter Value Language (PVL) and provides a description of how and why one would use this language for information interchange. publications to assure their continued relevance. This Informational Report has been reconfirmed through May 2018.
ASCII Encoded English (CCSD0002). Blue Book. Issue 1. November 1992.
This Recommended Standard defines the usage of ASCII Encoded English and its representation as a data description language. The CCSDS conducts periodic reconfirmation reviews of its publications to assure their continued relevance. This Informational Report has been reconfirmed through May 2018.
The Data Description Language EAST Specification (CCSD0010). Blue Book. Issue 3. June 2010.
This Recommended Standard defines the EAST language used to create descriptions of data, called Data Description Records (DDRs). Such DDRs ensure a complete and exact understanding of the data and allow it to be interpreted in an automated fashion. A software tool is able to analyze a DDR, interpret the format of the associated data, and extract values from the data on any host machine (i.e., on a different machine from the one that produced the data). The current issue adds improvements/clarifications to the specification and adds a requirement to include the EAST version number in the logical part of a DDR. The CCSDS conducts periodic reconfirmation reviews of its publications to assure their continued relevance. This Recommended Standard has been reconfirmed through June 2022.
The Data Description Language EAST—A Tutorial. Green Book. Issue 1. May 1997.
This Informational Report describes the usage of the EAST language, its format, and construction rules as well as suggested practices. It is a companion document to CCSDS 644.0-B-3, The Data Description Language EAST Specification (CCSD0010). The CCSDS conducts periodic reconfirmation reviews of its publications to assure their continued relevance. This Informational Report has been reconfirmed through June 2022.
The Data Description Language EAST—List of Conventions. Green Book. Issue 1. May 1997.
This Informational Report establishes an evolving list of conventions used in the data generation process to produce real numbers. These conventions are referenced in EAST Data Descriptions (see CCSDS 644.0-B-3) and could be referenced in other Data Description Records (DDRs), written in other Data Description Languages (DDL). The CCSDS conducts periodic reconfirmation reviews of its publications to assure their continued relevance. This Informational Report has been reconfirmed through June 2022.
Data Entity Dictionary Specification Language (DEDSL)—Abstract Syntax (CCSD0011). Blue Book. Issue 1. June 2001.
The Data Entity Dictionary Specification Language (DEDSL) standardizes of the expression of semantic concepts that are to be carried with data. The Recommended Standard for DEDSL--Abstract Syntax provides the abstract definition of the semantic information that is required to be conveyed and presents the specification in a layered manner (attributes, entities, dictionaries). As such the actual technique used to convey the information is independent of the information content; therefore the same abstract standard can be used within different formatting environments, and the semantic information may be translated to different representations as may be needed when data are transferred across different domains. The CCSDS conducts periodic reconfirmation reviews of its publications to assure their continued relevance. This Recommended Standard has been reconfirmed through May 2018.
Data Entity Dictionary Specification Language (DEDSL)—PVL Syntax (CCSD0012). Blue Book. Issue 1. June 2001.
This Data Entity Dictionary Specification Language (DEDSL) Recommended Standard provides the Parameter Value Language (PVL) (CCSDS 641.0-B-2) implementation for the DEDSL--Abstract Syntax Recommended Standard (CCSDS 647.1-B-1) in order to provide a standardized computer processable expression of the semantic information which to be carried with data. The Recommended Standard for PVL Syntax provides a standard method to represent the attributes and their values, as defined by the Recommended Standard for Abstract Syntax, using the Parameter Value Language for the construction and interchange of data entity dictionaries. The CCSDS conducts periodic reconfirmation reviews of its publications to assure their continued relevance. This Recommended Standard has been reconfirmed through May 2018.
Data Entity Dictionary Specification Language (DEDSL)—XML/DTD Syntax (CCSD0013). Blue Book. Issue 1. January 2002.
This Recommended Standard provides a standard method to represent attributes and their values, as has been defined by the Abstract Syntax of the Data Entity Dictionary Specification Language (DEDSL) (CCSDS 647.1-B-1), using the Extensible Markup Language (XML) 1.0 Document Type Declaration (DTD) for the construction and interchange of data entity dictionaries. The CCSDS conducts periodic reconfirmation reviews of its publications to assure their continued relevance. This Recommended Standard has been reconfirmed through May 2018.
Data Entity Dictionary Specification Language (DEDSL)--XML/XSD Syntax . Orange Book. Issue 1. May 2018.
This Experimental Specification provides a new implementation of the Abstract Syntax of the Data Entity Dictionary Specification Language (DEDSL) (CCSDS 647.1-B-1) using the XML Schema definition for the construction and interchange of data entity dictionaries, while being fully compatible with the XML/DTD Syntax (CCSDS 647.3-B-1).
Reference Model for an Open Archival Information System (OAIS). Magenta Book. Issue 2. June 2012.
This Recommended Practice defines the Reference Model for an Open Archival Information System (OAIS). The current issue includes clarifications to many concepts, in particular, Authenticity with the concept of Transformational Information Property introduced; corrections and improvements in diagrams; addition of Access Rights Information to PDI.
Producer-Archive Interface Methodology Abstract Standard. Magenta Book. Issue 1. May 2004.
This Recommended Practice identifies, defines, and provides structure to the relationships and interactions between an information Producer and an Archive. This Recommended Practice defines the methodology for the structure of actions that are required from the initial time of contact between the Producer and the Archive until the objects of information are received and validated by the Archive. These actions cover the first stage of the Ingest Process as defined in the Open Information System (OAIS) Reference Model. This Recommended Practice describes parts of the functional entities Administration ('Negotiate Submission Agreement') and Ingest ('Receive Submission' and 'Quality Assurance'). The CCSDS conducts periodic reconfirmation reviews of its publications to assure their continued relevance. The CCSDS conducts periodic reconfirmation reviews of its publications to assure their continued relevance.This Recommended Practice has been reconfirmed through June 2022.
Producer-Archive Interface Specification (PAIS). Blue Book. Issue 1. February 2014.
This Recommended Standard provides the abstract syntax and an XML implementation of descriptions of data to be sent to an archive. These descriptions are negotiated agreements between the data Producer and the Archive and facilitate production of agreed data by the Producer and validation of received data by the Archive. The Recommended Standard includes an abstract syntax for describing how these data will be aggregated into packages for transmission and one concrete implementation for the packages based on the XML Formatted Data Unit (XFDU) standard.
Producer-Archive Interface Specification (PAIS)--A Tutorial. Green Book. Issue 1. September 2016.
This CCSDS Informational Report provides a tutorial for CCSDS 651.1-B-1, Producer-Archive Interface Specification (PAIS) (Blue Book, Issue 1, February 2014).
Audit and Certification of Trustworthy Digital Repositories. Magenta Book. Issue 1. September 2011.
This Recommended Practice defines an audit and certification process for assessing the trustworthiness of digital repositories.
Requirements for Bodies Providing Audit and Certification of Candidate Trustworthy Digital Repositories. Magenta Book. Issue 2. March 2014.
The Recommended Practice for Requirements for Bodies Providing Audit and Certification of Candidate Trustworthy Digital Repositories contains binding and verifiable specifications required to be fulfilled by organizations that perform ISO audits for assessing the trustworthiness of digital repositories using CCSDS 652.0-M-1, Audit and Certification of Trustworthy Digital Repositories, and provides the appropriate certification. The current issue has been updated to reflect input from ISO experts.
XML Telemetric and Command Exchange (XTCE). Blue Book. Issue 1. October 2007.
The XTCE data specification provides an information model and data exchange format for telemetry and commanding definitions (operational database) in all phases of the a spacecraft, payload, and ground segment life cycle: system design, development, test, validation, and mission operations.
Document Icon
CCSDS 660.0-G-1
File size 1309 KB
XML Telemetric and Command Exchange (XTCE). Green Book. Issue 1. July 2006.
This CCSDS Informational Report presents a set of concepts and tutorial on the XML Telemetric and Command Exchange (XTCE). XTCE is an XML based format aim at facilitating the exchange of spacecraft telemetry and command databases between different organizations and systems during any mission phase. Such a non-proprietary format avoids the need for customized import/export tools, and the validation and new implementation of mission databases, which are often error-prone. The scope of XTCE is limited to the exchange of satellite telemetry and commanding databases. XTCE can be used to exchange a database between spacecraft manufacturers, instrument manufacturers, and different systems of the ground segment. It can also be used as an exchange mechanism between different development teams or between missions, which enhances database re-use.
Document Icon
CCSDS 660.1-G-1
File size 1960 KB
XML Telemetric and Command Exchange (XTCE)--Element Description. Green Book. Issue 1. May 2012.
This Informational Report provides information for using Extensible Markup Language (XML) Telemetric and Command Exchange (XTCE) 1.1.
XML Formatted Data Unit (XFDU) Structure and Construction Rules. Blue Book. Issue 1. September 2008.
This Recommended Standard defines a technique for the packaging of data and metadata, including software, into a single package (e.g., file or message) to facilitate information transfer and archiving. It provides a detailed specification of core packaging structures and mechanisms that meet current CCSDS agency requirements and that augment the current CCSDS packaging and language Recommended Standards to accommodate the current computing environment and meet evolving requirements. This Recommended Standards leverages the wide community acceptance and usage of XML technologies by making the packaging manifest an XML document defined by the XML Schema specified in the document. The CCSDS conducts periodic reconfirmation reviews of its publications to assure their continued relevance. This Recommended Standard has been reconfirmed through June 2022.
Copyright 2017 © CCSDS/ASRC Federal Technical Services All rights reserved.