Why data system standards?
Data systems coordinating standards developed from experience with STADAN, discussing operating environment and administrative decisions influence on implementation
SEARCH · Engineering Papers
Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.
Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.
Data systems coordinating standards developed from experience with STADAN, discussing operating environment and administrative decisions influence on implementation
Standardization of products and services is the only way world Space Agencies and their providers can achieve substantial reduction in development and operations cost. Current and future CCSDS tasks will continue to center around providing tools for it to happen. NASA and other Space Agencies welcome efforts of companies and technology and standards organizations to provide our missions with even more tools to succeed.
The NASA approach to data systems standardization is described. The major thrust of this activity is to assure effective use of NASA resources. The process by which standards are written, who writes them, and what subjects are covered, is briefly examined.
Stages in the development of planetary program data system standards since the inception of program standards in 1969 are identified as a review of the then existing data system element designs, the selection of canditate elements for additional standards, and the formation in 1972 of a Telecommunication Standards Committee for fulltime work in the final preparation of the standards. Further efforts in developing and implementing a complete set of standards within the possibly shortest time are planned.
NASA is participating in the development of international standards for space data systems. Recommendations for standards thus far developed are assessed. The proposed standards for telemetry coding and packet telemetry provide worthwhile benefit to the DSN; their cost impact to the DSN should be small. Because of their advantage to the NASA space exploration program, their adoption should be supported by TDA, JPL, and OSTDS.
The modifications being considered by the NASA-ESA Working Group (NEWG) for space-data-systems standardization to maximize the commonality of the NASA and ESA RF and modulation systems linking spaceborne scientific experiments with ground stations are summarized. The first phase of the NEWG project shows that the NASA MK-IVA Deep Space Network and Shuttle Interrogator (SI) systems in place or planned for 1985 are generally compatible with the ESA Network, but that communications involving the Tracking and Data Relay Satellite (TDRS) are incompatible due to its use of spread-spectrum modulation, pseudonoise ranging, multiple-access channels, and Mbit/s data rates. Topics under study for the post-1985 period include low-bit-rate capability for the ESA Network, an optional 8-kHz command subcarrier for the SI, fixing the spacecraft-transponder frequency-multiplication ratios for possible X-band uplinks or X-band nondeep-space downlinks, review of incompatible TDRS features, and development of the 32-GHz band.
The objectives of the Consultative Committee for Space Data Systems (CCSDS) include the identification of those common elements of space data systems which, if implemented in a standardized way, will significantly enhance the operation of future cooperative space missions. Recommendations of the CCSDS include packet telemetry and telecommand concepts, coding designs, ancillary data parameters and formats, and data exchange conventions. Consideration is given to the application of CCSDS recommendations.
Standards needed to interconnect applications data service pilots for data sharing were identified. Current pilot methodologies are assessed. Recommendations for future work are made. A preliminary set of requirements for guidelines and standards for catalogues, directories, and dictionaries was identified. The user was considered to be a scientist at a terminal. Existing and emerging national and international telecommunication standards were adopted where possible in view of new and unproven standards.
NASA has impaneled several internal working groups to provide recommendations to NASA management on ways to evolve and improve Earth Science Data Systems. One of these working groups is the Standards Process Group (SPC). The SPG is drawn from NASA-funded Earth Science Data Systems stakeholders, and it directs a process of community review and evaluation of proposed NASA standards. The working group's goal is to promote interoperability and interuse of NASA Earth Science data through broader use of standards that have proven implementation and operational benefit to NASA Earth science by facilitating the NASA management endorsement of proposed standards. The SPC now has two years of experience with this approach to identification of standards. We will discuss real examples of the different types of candidate standards that have been proposed to NASA's Standards Process Group such as OPeNDAP's Data Access Protocol, the Hierarchical Data Format, and Open Geospatial Consortium's Web Map Server. Each of the three types of proposals requires a different sort of criteria for understanding the broad concepts of "proven implementation" and "operational benefit" in the context of NASA Earth Science data systems. We will discuss how our Standards Process has evolved with our experiences with the three candidate standards.
Attention is given to an end-to-end Space Station Data System (SSDS) architecture which is based on internationally-recommended standards developed by the Consultative Committee for Space Data Systems (CCSDS). The proposed system uses simple modular building blocks that are recursively replicated and linked to construct essentially any desired data system configuration. The SSDS concept provides for a user-transparent data transport system which is entirely independent of the characteristics of the user data being transported, and in addition, has the flexibility to accommodate mission-induced changes in data traffic. SSDS physical elements include the following: (1) on-orbit local area networks, (2) space-to-ground, ground-to-space, and space-to-space data links, and (3) ground mission support facilities containing telemetry and telecommand data handling termini and preprocessing services.
This recommendation contains the detailed specification of the logic required to carry out the Command Operations Procedures of the Transfer Layer. The Recommendation for Telecommand--Part 2, Data Routing Service contains the standard data structures and data communication procedures used by the intermediate telecommand system layers (the Transfer and Segmentation Layers). In particular, it contains a brief description of the Command Operations Procedures (COP) within the Transfer Layer. This recommendation contains the detailed definition of the COP's in the form of state tables, along with definitions of the terms used. It is assumed that the reader of this document is familiar with the data structures and terminology of part 2. In case of conflict between the description of the COP's in part 2 and in this recommendation, the definition in this recommendation will take precedence. In particular, this document supersedes section 4.3.3.1 through 4.3.3.4 of part 2.
The Telerobotics Working Group of the Mission Operations and Information Management Services Area of the Consultative Committee for Space Data Systems is drafting a document that will help bound the scope of an eventual international standard for telerobotic operations services. This paper will present the work in progress and provide background for how the international community is beginning to define standards in telerobotic operations that will help ensure the success of complex missions to explore beyond Earth orbit.
A simple, top level logical reference model of the NASA Space Transportation System's end-to-end data system is being developed which can identify the functions and services of the system. Each function or service may be mapped into specific physical subsystems, so that interface relationships are evident and 'standard' protocols may be identified for development. By means of this interface standardization, subsystems can be designed not only independently and in parallel, but with confidence that when the subsystems are aggregated, the end-to-end system will operate efficiently and at low cost. This standardization effort has thus far been principally directed toward space-to-ground communications links.
Integrated tables of pressure, volume, and temperature for the saturated liquid, from the triple point to the critical point of the gases, have been developed. Tables include definition of saturated liquid curve. Values are presented in metric and practical units. Advantages of the new tables are discussed.
Explore the source record for details and available documents.
This paper will discuss data systems interface standards including the goals and benefits in their application to space flight programs. Recent trends toward increased international cooperation in space research and applications missions have resulted in a greater emphasis on compatible interface standards among the participating agencies. The discussion will highlight the Consultative Committee for Space Data Systems (CCSDS), a consortium of 19 space agencies formed in 1982 in order to provide a technical forum for developing guidelines for compatible data systems standards among cooperating space agencies worldwide. CCSDS effort is seen as contributing significantly to the objectives of the IAF's Symposium on Space Exploration.
Planetary data include non-imaging remote sensing data, which includes spectrometric, radiometric, and polarimetric remote sensing observations. Also included are in-situ, radio/radar data, and Earth based observation. Also discussed is development of a planetary data system. A catalog to identify observations will be the initial entry point for all levels of users into the data system. There are seven distinct data support services: encyclopedia, data index, data inventory, browse, search, sample, and acquire. Data systems for planetary science users must provide access to data, process, store, and display data. Two standards will be incorporated into the planetary data system: Standard communications protocol and Standard format data unit. The data system configuration must combine a distributed system with those of a centralized system. Fiscal constraints have made prioritization important. Activities include saving previous mission data, planning/cost analysis, and publishing of proceedings.