1 CCSDS Information Architecture Working Group SEA Plenary Daniel J. Crichton, Chair NASA/JPL 12 September 2005

2 IAWG Charter F 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. F 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

A View of a Space Data System Information Architecture Cross Support Services Spacecraft Onboard Interface Services Space Internetworking Services Space Link Services Mission Operations and Information Management Services Commodity Communications & Navigation Systems Systems Engineering Source: A. Hooke, NASA/JPL Information Architecture Long term – End-to-End Integration NEAR TERM Science Data Systems  Common Info Models  Repositories  Registries Ground Systems  Common Info Models  Product Services  Registries

4 Status of WG F Technical Green Book – Reference Architecture for Space Information Management CCSDS G-1 – September 2005 Version ä Incorporates updates resulting from NASA TIM between MOIMS/GSFC and SEA/JPL in August ä Major updates since Fall and Spring CCSDS Meetings ä Integrated CNES OMG MDA concepts ä Working to be consistent with OAIS F Ontology developed based on white book. Captured in Protégé. F Initial discussions between GSFC and JPL to look at jointly working together between IA and IPR to focus on registries efforts ä One day TIM at GSFC in August discussed XML-based services

5 Overview F Define both the information view and functional the functional view for managing information across the space domain end-to-end. F Focus on “Application Information Objects”

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

7 OAIS Mapping

8 Data and Metadata Objects F Data Objects: represent the data as is physically present using a sequence of bits ä Without a metadata object the utility is decreased. No data structure is known… F Metadata Objects: special class of data objects that describe the structure, (syntactic) validity, interrelationships, and (semantic) rules of a data object and its respective structural elements.

9 Classifying Information Objects F Primitive Information Objects ä Minimal metadata including (name, type, size, date) F Simple Information Objects ä Structured domain metadata F Information Packages ä Aggregation of information objects

10 End-to-End Space Information Architecture 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

11 Functional Objects 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

12 Advanced Information Management Objects Types F Repository Service Objects ä Provide common components for management of information objects. Provides for short-term and long-term management. F Registry Service Objects ä Provide common components for management/discovery of metadata F Product Service Objects ä Provides specialization for access, transformation of information objects F Query Service Objects ä Manages routing of queries in order to discover and locate the appropriate product service objects, as well as repository service objects

13 Repository Functional Object Classes Repository Object TypeObject PropertiesObject Description Data StorePrimitive Component (e.g., DBMS, and File system) Basic Data Store component described in Section 3.1 sits behind Data Store Object and supports Repository Interface to get and put data (lower level data such as streams and bits) Operational ArchiveComponent that stores data products and higher level products, possibly including metadata. Supports retrieval of data products through possibly complex methods, and processing. No support for permanence. Stores products for short term (e.g. less than 10 years), and allows retrieval of products. Advanced Component supporting retrieval of possibly complex data products, including their metadata. Repository where writes are frequent and reads are frequent. Data products stored in this type of archive will be updated and versioned. Examples of products stored in this archive are command sequence products sent using spacecraft telemetry. Long-term ArchiveStores products for long term archiving, and supports basic archive functionality. Archive for long-term preservation of data products, and data permanence. Supports basic archive functional interfaces (e.g. get, put).

14 Registry Functional Object Classes Registry TypeReturn Object TypesQuery Interface Parameters Metadata RegistryData Dictionaries, Data ElementsQuery for Data Element properties, or Data Element IDs, or Data Dictionary IDs Service RegistryService Endpoints, Service Metadata (interface properties, interface type, return schema) Query for Service properties Resource RegistryData Products, Resource Registry Locations Data Resource properties

15 FY05 Plan AreaDescriptionDate IAWGHold SEA IAWG MeetingApril 2005 IPR/IAWGHold Joint Meeting on Registries with IPR April 2005 IPR/IAWGIPR/IA Technical Interchange Meeting + XML Planning August 2005 IAWGPublish current whitebook as a technical document for CCSDS (green book) September 2005 IPR/IAWGDiscuss registry-based services and thrust between IA and IPR December 2005

16 NASA XML-based Services Meeting 2:00- 2:15 Overview of Goals of Session Dan Crichton 2:15-2:45 JPL work on XML enterprise services Dan Crichton/P Shames 2:45-3:15 GMSEC usage/rqmts for using XML Dan Smith or Representative 3:30-4:00 DSMS usage/rqmts for using XML T McVittie or Representative 4:00-4:30Exploration/C3I usage of XML Bob Bradford 4:30-5:00CCSDS SLE usage of XML Erik Barkley 5:00-5:30CCSDS IPR/IA Registry Repository Study Dan Crichton/Lou Reich 5:30-600Action items/planning for Toulouse meeting

17 Agenda for Atlanta IAWG Agenda Date/Time: Wednesday, September 14, 2005 Chair: Dan Crichton Agenda 09:00 AM – 09:15 AM Agenda Review 09:15 AM – 12:00 PM Discussion on updates to IA document 12:00 PM - 01:30 PM Lunch 01:30 PM - 02:30 PM Discussion on IA/IPR NASA TIM 02:30 PM – 05:00 PM Next steps and planning for IAWG Reference implementations Formalization of interfaces Working with MOIMS Best practices Information Infrastructure Specification (E.g., Registries and Repositories)