1

CCSDS Information Architecture Working Group

SEA Plenary

Daniel J. Crichton, Chair

NASA/JPL

12 September 2005

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

A View of a Space Data SystemInformation Architecture

Cross SupportServices

SpacecraftOnboardInterfaceServices

SpaceInternetworking

Services

SpaceLink

Services

Mission Operationsand Information

Management Services Commodity Communications &

Navigation Systems

Systems Engineering

Source: A. Hooke, NASA/JPL

Information Architecture Long term – End-to-End Integration

NEAR TERMScience Data SystemsCommon Info ModelsRepositoriesRegistries

Ground SystemsCommon Info ModelsProduct ServicesRegistries

4

Status of WG

Technical Green Book – Reference Architecture for Space Information Management CCSDS 312.0-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

Ontology developed based on white book. Captured in Protégé.

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

Define both the information view and functional the functional view for managing information across the space domain end-to-end.

Focus on “Application Information Objects”

Middleware and Messaging

Comm Layer

Metamodel

Information Components

ApplicationInformation

Object

Domain Model

Metamodel

Information Components

ApplicationInformation

Object

Domain Model

Middleware and Messaging

Comm LayerCommon Protocols - TCPIP, ...

Common Messaging - SOAP, JMS, ...

Common Functions - Registry, Repository, ...

Common or Mediated Metamodel - DEDSL, ISO1179, UML

Common or Mediated Domain Models --Planetary Data Systems, EOSDIS, ...

Information Exchange - Science, Mission, etc, Data Products, Observations, SLE Objects, ...

Communications

Software/Application

Data Architecture/ Content

6

Technical Approach (Information View)

1. Information Objects

2. Information Models

3. Meta Models

Application Information Object

(AIO)

Data Object

Metadata Object

described by

Metamodels

Domain Models

DataDictionary

Schema/Ontology

prescribed by

instance of

Metadata ObjectData Object

Application Information

Object

Has a Has a

describes

M3

M2

M1

M0

ISO11179 UML model

MOF( Meta- Oject Facility)

Domainmodel

DataDictionary

MODELS

XMLSchema

M3

M2

M1

M0

ISO11179 UML model

MOF( Meta- Oject Facility)

Domainmodel

Application Information

Object

DataDictionary

MODELS

XMLSchema

OMG - Hierarchy of Models

7

OAIS Mapping

Data Object Metadata Object

8

Data and Metadata Objects

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…

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

Primitive Information Objects Minimal metadata including

(name, type, size, date)

Simple Information Objects Structured domain metadata

Information Packages Aggregation of information

objects

Data Metadata

[0101011110..] NameTypeDate….

Primitive Application Information Object

Information Package

Application Information

ObjectMetadata Object

Packaging Information

Has AHas Many

describes

10

End-to-End Space Information Architecture

External Science

Community

Data Acquisition

and CommandMission

OperationsInstrument /Sensor Operations

ScienceData

Archive

ScienceData

Processing

Data Analysis and

Modeling

Science Information Package

Science Team

Relay Satellite

Spacecraft / lander

Spacecraft andScientific Instruments

Information ObjectInformation Object

Simple Information Object

Telemetry Information Package

Science Information Package

Instrument Planning

Information Object

Science Information Package

Science Products - Information Objects

PlanningInformation

Object

Science Information Package

• Common Meta Models for Describing Space Information Objects• Common Data Dictionary end-to-end

11

Functional Objects

MissionPlanning

MissionAnalysis

Monitor &Control

DirectiveGeneration

DataAcquisition

DirectiveManagement

Domain Data

Models

Local Data

Models

RepositoryService

RegistryService

QueryService

ProductService

Common Schema &

Dictionaries

RepresentativeFunctional

Objects

InformationManagement

FunctionalObjects

Metadata /Resources

DataObjects

Query /Results

12

Advanced Information Management Objects Types

Repository Service Objects Provide common components for management of information objects.

Provides for short-term and long-term management.

Registry Service Objects Provide common components for management/discovery of metadata

Product Service Objects Provides specialization for access, transformation of information objects

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 Type Object Properties Object Description

Data Store Primitive 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 Archive Component 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 Archive Stores 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 Type Return Object Types Query Interface Parameters

Metadata Registry Data Dictionaries, Data Elements Query for Data Element properties, or Data Element IDs, or Data Dictionary IDs

Service Registry Service Endpoints, Service Metadata (interface properties, interface type, return schema)

Query for Service properties

Resource Registry Data Products, Resource Registry Locations

Data Resource properties

15

FY05 Plan

Area Description Date

IAWG Hold SEA IAWG Meeting April 2005

IPR/IAWG Hold Joint Meeting on Registries with IPR

April 2005

IPR/IAWG IPR/IA Technical Interchange Meeting + XML Planning

August 2005

IAWG Publish current whitebook as a technical document for CCSDS (green book)

September 2005

IPR/IAWG Discuss 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:30 Exploration/C3I usage of XML Bob Bradford

4:30-5:00 CCSDS SLE usage of XML Erik Barkley

5:00-5:30 CCSDS IPR/IA Registry Repository Study Dan Crichton/Lou Reich

5:30-600 Action 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)