1. 1 Steve Hughes Steve.Hughes@jpl.nasa.gov Daniel J. Crichton Dan.Crichton@jpl.nasa.gov NASA/JPL January 16, 2007 CCSDS Information Architecture Working Group Overview System Engineering Area Plenary

2. 2 IAWG Charter The focus of this working group is to define a reference Space Information Architecture that encompasses the capture, management and exchange of data for both flight and ground environments across the operational mission lifecycle. Goals: 1. Define a reference end-to-end space information architecture for interoperability and cross- support that encompasses both flight and ground data system operations and provides a common framework for use by standards and systems developers. The reference space information architecture includes: a. standard functional components for information management b. definition of standard interfaces for information management c. standards in information representation d. standards in defining information processes 2. Define and leverage common methods for representing information architectural views; and 3. Address application layer information management issues including application protocols and data handling and ensure that they are dealt with in a clear and consistent way throughout the end-to-end system; and 4. Work with the SEA System Architecture and MOIMS WGs

3. 3 IAWG Work Overview Deliverables –Information Architecture (RASIM) Status: draft Green Book, under review by agencies Latest version sent out for final comment prior to this meeting –Updates made based on conversations at the Rome meeting –Registries and Repositories Architectures –Domain-specific Information Architectures Mission Operations Science Principles Separation of the data and software architectures Identification of core information services Movement towards standards for each of the components/services Provide agency interoperability at the data level Leverages COTS-based architectural model (E.g. service-oriented/grid architectures) Leverages other standards efforts/concepts

4. 4 External Science Community Data Acquisition and Command Mission Operations Instrument /Sensor Operations Science Data Archive Science Data Processing Data Analysis and Modeling Science Information Package Science Team Relay Satellite Spacecraft / lander Spacecraft and Scientific Instruments Information Object Simple Information Object Telemetry Information Package Science Information Package Instrument Planning Information Object Science Information Package Science Products - Information Objects Planning Information Object Science Information Package Common Meta Models for Describing Space Information Objects Common Data Dictionary end-to-end End-to-End Space Information Architecture

5. 5 Overview Establish information architectural standards –Standards based Data Architecture Dublin Core ISO-11179 Ontologies –Semantic Web Data Models Metadata Models Standard Representation (XML, RDF, etc) –Standards based Software Architecture Components (Registries, Repositories) COTS-based messaging framework Configurations (legal topologies, interconnections, behaviors) Prototyping Activities –IPR Prototype –SANA SCID/GSCID Prototype –XML Registry Prototype –International Planetary Data Alliance

6. 6 Technical Approach (Information View) 1. Information Objects 2. Information Models 3. Meta Models

7. 7 Mission Planning Mission Analysis Monitor & Control Directive Generation Data Acquisition Directive Management Domain Data Models Local Data Models Repository Service Registry Service Query Service Product Service Common Schema & Dictionaries Representative Functional Objects Information Management Functional Objects Metadata / Resources Data Objects Query / Results Technical Approach

8. 8 Proposed Registry Work Plan Identify classes/types of registries Identify relationship to what exists –Standards –Models Develop space-domain use cases for registry classes/types –Within CCSDS (SANA, Security, SLE, Navigation, …) –Within Agencies (mission operations, science data systems, etc) Define registry requirements Agency Prototyping Define registry reference/architecture model –Recommended model –Recommended standards

9. 9 * From the IAWG and GSFC/JPL TIM (Aug 2006) Reference set of class types for Registries*

10. 10 Mapping Registry Classes to Standards

11. 11 Space Domain Use Cases Space domain use cases are specific instances of generic registry classes instantiated to support the end-to-end space domain architecture These use cases define: –What registries are needed –How they are used –What functions are needed –How they fit into the overall space domain architecture (both mission and science operations) Contrast to generalized use cases for registries

12. 12 Recent Accomplishments AreaDescriptionDate IPR/IAWGHeld TIM @ GSFCMay 2006 IAWGHeld Meeting in RomeJune 2006 IPR/IAWGDeveloped and Demonstrated integrated Information Services and IPR/XFDU packaging testbed August 2006 IAWG/IPRHeld TIM @ JPLAugust 2006 IAWG/IPRProduced strawman registry architecture plan December 2006 IAWGSent draft green book for reviewJanuary 2007

13. 13 This week’s focus Finalize RASIM green book comments Joint IPR/IA WG discussions on registries –Agree on classes –Discuss use cases –Agree on approach/plan Begin discussion of RASIM reference patterns (i.e. how do you apply/organize RASIM concepts/components for space data systems usage?) –RASIM Reference Patterns for Mission Operations –RASIM Reference Patterns for Science Data Systems Application to other WGs –SANA – Registry-type components coupled w/ data architecture specification –XSG – Data architecture specification –IPR – Packaging specification integrated into RASIM-based architecture

14. 14 Backup

15. 15 NVO as an example

16. 16 PDS as an example

17. 17 DSMS as an example

18. 18 SANA as an example