Data Information and Management System
for the DFD Multi-mission Earth Observation Data
Stephan Kiemle, German Aerospace Center DLR
Page 1 > DIMS
Stephan Kiemle > 2005-11-18
Outline
Multi-mission payload ground segment functions
System definition approach
Service oriented architecture
Operational scenarios
systematic
request driven
Conclusion
Multi-mission
Payload
Ground Segment
EO
Applications
Page 2 > DIMS
Stephan Kiemle > 2005-11-18
Multi-mission Payload Ground Segment Functions
Ordering
Data ingestion and processing
Data preservation (inventory and
archive)
User services and online data access
Ordering of existing/producible products
and future acquisitions, subscription
handling
Product generation and delivery
Monitoring and control
Online Access
Delivery
Preserving
Mon. & Control
Ingestion/Processing
O3
10110010
00010101
10111001
01000100
O3
700
600
500
300
240
Page 3 > DIMS
Stephan Kiemle > 2005-11-18
System Analysis and Design Approach
Multi-mission
reuse facilities to reduce development costs and operations risks
better exploitation and added value by combination of data of different
missions
Payload data handling outlives mission lifetime
Historical data access through near-realtime data access
Complex value-adding and cross-mission production, mission planning
(ordering of future products), data subscription and online access
Definition of scope
Analysis of actors and use cases
Definition of scenarios and requirements
Deduction of abstract services
Page 4 > DIMS
Stephan Kiemle > 2005-11-18
Design Methods for Sustainability
Focus on common functions, processes and business data (“digital products”,
“user order”, “production request”)
Abstraction and Generalisation: hide mission-specific details without loosing
functional context
Encapsulation: transport mission-specific information in generalised interfaces,
plug in modules for specific functions
Standardisation: strong way of assimilation, imposing common structure and
behavior, ensuring external connectivity
Use case “new mission integration”
Identification of required functions
Configuration of new workflows
Specific extension of data structures
Page 5 > DIMS
Stephan Kiemle > 2005-11-18
Towards a Service Oriented Architecture
Context Analysis
Basic
Process
Basic
Process
Basic
Process
Scenario
Scenario
Scenario
Scenario
Scenario
Scenario
Scenario
Scenario
Scenario
Definition of detailed scenarios
Abstract Service Abstract Service Abstract Service
Abstract Service Abstract Service
System decomposition
Component
Component
Component
Component
Component
Persistence, communication protocols, network infrastructure, hardware
Page 6 > DIMS
Stephan Kiemle > 2005-11-18
Operational Scenarios
Overview
Systematic, data driven processes
regular and autonomously repeated activity
functional chain initiated and maintained by products being
ingested, processed, archived, transformed and distributed
Request driven processes
typically initiated by external users or applications requesting data or
services
unsystematic, unpredictable events
functional chain initiated and maintained through requests being
created, submitted and processed
for planning, acquisition, processing, tailoring and delivery of products
Page 7 > DIMS
Stephan Kiemle > 2005-11-18
Operational Scenarios
Systematic, Product Data Driven Processes
1.
Systematic data ingestion
acquired sensor data, auxiliary data
download data files
extract metadata, transform format, generate quicklook
bundle and ingest new structured reference product
DIMS:
Ingestion service based on
Processing System Management (PSM)
25 instances of 13 missions
Product Files
Metadata
Ingestion System
Management
Algorithms
Product Library (PL) service
Cache
Reference Product Library
Products
Inventory
Archive
Pickup
Point
Page 8 > DIMS
Stephan Kiemle > 2005-11-18
Operational Scenarios
Systematic, Product Data Driven Processes
2.
Systematic data processing
continuously generate higher level products
processing chaining
long term preservation of common interest reference products
trade-off between usage and required storage and generation resources
DIMS:
Processing service based on
Processing System Management (PSM)
18 instances of 8 missions
Subscribe
Processing System
Management
Algorithms
Cache
Reference
Products
Product Library
Inventory
Archive
Product Library (PL) service with product
availability notifications
Page 9 > DIMS
Stephan Kiemle > 2005-11-18
Operational Scenarios
Systematic, Product Data Driven Processes
3.
Near-realtime processing and delivery
continuously generate and disseminate products
service agreement, no ordering/accounting
Product Files
Metadata
NRT Proc. System
DIMS:
Pickup
Point
NRT processing service based on
Processing System Management (PSM) with
Online Product Generation & Delivery (OPG)
blade
2 instances of 2 missions
Management
Algorithms
Cache
Reference
Products
Pickup
Point
Page 10 > DIMS
Stephan Kiemle > 2005-11-18
Operational Scenarios
Systematic, Product Data Driven Processes
4.
Product publishing
continuous but selective publishing of products
web portals, other external systems
format conversion, thumbnail generation, metadata portrayal
online
archive
Publisher
Management
Algorithms
DIMS:
Publisher service based on Processing System
Management (PSM)
1 instance for multiple missions
Subscribe
Cache
Reference
Products
Product Library
Inventory
Archive
Page 11 > DIMS
Stephan Kiemle > 2005-11-18
Operational Scenarios
Systematic, Product Data Driven Processes
5.
User services
continuous but selective upload of products
online user catalogue with collection/browse, other external systems
future products/acquisitions visibility (mission planning)
online product ordering, order options for acquisition,
scene selection, processing and delivery
EOWEB
eoweb.dlr.de
DIMS:
User Interface service framework (UI/UL)
3 instances for upload to the systems EOWEB,
ESA MMMC, EUMETSAT UMARF
EOWEB user services http://eoweb.dlr.de
ESA
MMMC
EUM
UMARF
Metadata
Quicklooks
User Orders
Product Library
Inventory
Archive
Subscribe
Reference
Products
UIS
Loader/
UIS
UISLoader/
Loader/
Interface
Interface
Interface
Page 12 > DIMS
Stephan Kiemle > 2005-11-18
Operational Scenarios
Request Driven Processes
1.
Ordering of existing and producible products
order validation: consistency, authorisation
price depending on order options, reductions and metadata values (e.g.
cloud/land cover)
order confirmation, delivery papers, invoice
trigger production chain (producible products)
User Orders
Pickup
Point
trigger tayloring and delivery (online/media)
DIMS:
Ordering Control service (OC)
Production Control service (PC) for superior
processing chains, 3 instances
Online/offline Product Generation & Delivery
service (OPG)
UIS
Loader/
UIS
UISLoader/
Loader/
Interface
Interface
Interface
Online/Offline
Prod. Gen.&Delivery
Ordering Control
Delivery
Products
Query Product Library
Production
Control
Inventory
Archive
Rules
Delivery Products
Production
Requests
Page 13 > DIMS
Stephan Kiemle > 2005-11-18
Operational Scenarios
Request Driven Processes
2.
Mission planning - ordering of future products
future scenes predictable …
future coverages plannable ...
… based on region of interest and sensor parameters
mission planning order with additional acquisition options and priority
(influencing the price)
acquisition as step 0 in production chain, including planning and
commanding (mission operations segment), reception and ingestion
Ordering Control
DIMS:
EOWEB with swath coverage service
Production Control service (PC) generates acquisition
planning requests for mission operations segment
Downlink contains acquisition request information
Production
Control
Rules
Acquisition
Planning
Request
Production
Requests
Page 14 > DIMS
Stephan Kiemle > 2005-11-18
Operational Scenarios
Request Driven Processes
3.
Standing ordering
subscription on newly available products
regular processing/delivery of products matching condition
mission planning of repeated acquisitions
regular scheduling of future scenes/coverages
Subscribe
DIMS:
Central Ordering Control service (OC) manages
subscriptions and repeated acquisitions
Ordering Control
Product Library
Inventory
Product Library service sends notifications
on newly available products
Archive
Production
Control
Rules
Acquisition
Planning
Request
Production
Requests
Page 15 > DIMS
Stephan Kiemle > 2005-11-18
Operational Scenarios
Monitoring and Control Processes
Monitoring and alarm
supervise systematic processes and system load
notify operator on critical states and failures
activity failure, runs out of time, abnormal inactivity
Service operating
human operator interaction in scenarios
order and production management, quality control
product/mission analysis, ad-hoc queries
analyse failures, resume production
Reporting
DIMS:
Monitoring & Alarm service (MA)
Operating Tool client (OT) as single GUI integrating all DIMS services
Page 16 > DIMS
Stephan Kiemle > 2005-11-18
Conclusion
Operational experience is very valuable for completeness of scenario definition
in the payload ground segment design phase
Design basis of abstract services allows architecture being flexible for
enhancements for new operative tasks in the multi-mission context
Functions of a payload ground segment have to support
systemtic, data driven processes,
request driven processes and
monitoring and control processes
as provided by DLR’s Data Information and Management System (DIMS)
Page 17 > DIMS
Stephan Kiemle > 2005-11-18
Service Operating Example
Atmospheric Product QA with DIMS Operating Tool
Page 18 > DIMS
Stephan Kiemle > 2005-11-18