Upload
maliyah-womer
View
217
Download
0
Tags:
Embed Size (px)
Citation preview
THE VOICEKick-Off Meeting
ESRIN, 03/03/2004
THE VOICE KO 203/03/2004
Agenda 9:00 - Welcome and Introduction (30’, ESA) THE VOICE Consortium Introduction (10’, DAT) THE VOICE Study Logic & Management (15’, DAT) Focus on Technologies and Earth Science VOs:
Service Requirements (20’, DS) eCollaboration Technology Survey (20’, SSL) ES-generic Collaborative Environment Definition (20’, DAT)
Coffee Break
Focus on Prototype scenarios: ES-generic Collaborative Environment Set Up (15’, DAT) ENVISAT Cal/Val Prototyping Activities (30’, DS) GMES Open Service Partnership Prototyping Activities (30’, SSL) Open Agricultural Services Prototyping Activities (30’, SESA)
Contractual issues (15’, DAT)
Lunch
Brainstorming on Earth Science requirements vs. technologies (until 17:00, All)
17:00 - Conclusions (ESA) and Adjourn
THE VOICE KO 303/03/2004
Introduction to THE VOICEWhat is it?
An ESA funded project with the following objectives:1. The identification of the common and generic technology
elements essential for the establishment of a collaborative environment that supports web-based domain-specific vertical organisations;
2. Identification of common interface mechanisms for data, applications and service establishment, including “exchange languages” for the interaction and exploitation of available resources;
3. Implementation of prototypes, i.e. the implementation of collaborative environments with representative applications and services for domain-specific vertical organisations involving the Earth science domain.
THE VOICE KO 403/03/2004
Introduction to THE VOICE Who is composing the Consortium?
Industrial partnerswith good basic technological competence and complementary excellence,with strong complementary backgrounds in application disciplines,already involved in several on-going activities on e-collaboration environments at National and EU level.
THE VOICE KO 503/03/2004
Introduction to THE VOICE Why?
Partners’ traditional focus is on innovation, with a long record of international RTD projects
The new enabling technologies such as GRID, Web Services, Workflow, Wireless, P2P are shaping the future of ICT market, paving the way to concept of ambient intelligence, a fundamental gap in information society foundations, as WWW was in the 90’s
Collaborative environments are a typical application field where a merge of these technologies is required and may be profitably transferred towards several complex thematic disciplines
THE VOICE KO 603/03/2004
Introduction to THE VOICE Which focus?
Four space related disciplines have been preliminarily identified as potential candidates:
ENVISAT Cal/Val
GMES Open Service Partnership
Open Agricultural Services Other application fields
[TBD], such as meteorological services, urban, coastal,…
THE VOICE KO 703/03/2004
THE VOICE Study Logic - 1
Phase 1
ServiceRequirements
Review
InfrastructureDefinition
Review
ES domainCollaborativeEnvironment
Definition
Service Requirementsfor e-Collaboration
in ES domain Sectors
Vertical Org. AndService Requirements
Identification
ENVISAT Cal/Val
OtherES domain
Vertical Org.
GMES Open Service Partnership
OpenAgricultural
Services
e-CollaborationTechnology
Recommendations
WebServices
GIS
e-CollaborationTechnology
Survey
OtherTechnologies
WorkflowManagement
Grid Wireless/Mobile
to Phase 2
THE VOICE KO 803/03/2004
THE VOICE Study Logic - 2
Phase 2
NewPrototype
3
PrototypesDemonstration & Test
Prototyping
ENVISAT Cal/Val
ES domainCollaborativeEnvironment
Set Up
Final Presentation
OpenAgricultural
Services
GMES Open Service
PartnershipNew
Prototype2
NewPrototype
1
from Phase 1
THE VOICE KO 903/03/2004
THE VOICE Schedule
WBS Task Name
00000 THE VOICE
10000 Phase 1
Ph1-KO Phase 1 Kick-off
Ph1-PM#1 Phase 1 Progress Meeting #1
SRR Service Requirements Review
Ph1-PM#2 Phase 1 Progress Meeting #2
IDR Infrastructure Definition and Detailed Testbed Plan Review
11000 Study Management
12000 Service Requirements
13000 e-Collaboration Technology Survey
14000 ES-generic Collaborative Environment Definition
20000 Phase 2
Ph2-KO Phase 2 Kick-off
Ph2-PM#1 Phase 2 Progress Meeting #1
Ph2-PM#2 Phase 2 Progress Meeting #2
Ph2-PM#3 Phase 2 Progress Meeting #3
Ph2-PM#4 Phase 2 Progress Meeting #4
PDT Prototypes Demonstration and Test
Ph2-PM#5 Phase 2 Progress Meeting #5
FP Final Presentation
21000 Study Management
22000 ES-generic Collaborative Environment Set Up
23000 Prototype Design, Implementation and Test
23200 ENVISAT Ozone Cal/Val
23300 GM ES Open Service Partnership
23400 Open Agricultural Services
Ph1-KO
Ph1-PM#1
SRR
Ph1-PM#2
IDR
Ph2-KO
Ph2-PM#1
Ph2-PM#2
Ph2-PM#3
Ph2-PM#4
PDT
Ph2-PM#5
FP
M-2 M1 M3 M5 M7 M9 M11 M13 M15 M17 M19Q1 Q3 Q5 Q7
THE VOICE KO 1003/03/2004
Service Requirements (1)
ServiceRequirements
TechnologySurvey
EnvironmentDefinition
EnvironmentSet-up
SpaceGRID
EU DataGrid
MASS
GREASE
GridStart
…
Use Cases & ServiceRequirements
THE VOICE KO 1103/03/2004
Service Requirements (2)
Assessment of existing inventories on eCollaboration in Earth Sciences, e.g. SpaceGrid (*) EU DataGrid (*) GREASE MASS (*) CEOS-Grid (*) NASA’s Information Power Grid (*): to be provided by ESA
Identification of sectors related to Earth Science and typical use cases, e.g. …..see next slides
THE VOICE KO 1203/03/2004
Use Case Mission AnalysisInstrument Simulation
Using an atmosphere and/or instrument model
AtmosphereModel
InstrumentModel
Orbit Model
Level 2Algorithm
Level 1bProcessor
DownlinkModel
Level 0Processor
Parameters
Results
Parameters
THE VOICE KO 1303/03/2004
Testing with hardware test data
HardwareModel
Orbit Model
Level 2Algorithm
Level 1bProcessor
DownlinkModel
Level 0Processor
Results
Parameters
Use CaseInstrument Testing
THE VOICE KO 1403/03/2004
Testing & validation using operational data
Level 2Algorithm
Level 1bProcessor
OperationalInstrument
ValidationResults
Data from otherinstruments
Compareresults
Use CaseInstrument Validation
THE VOICE KO 1503/03/2004
“Service requirements”
Functional requirements
Compute
Compute
Transfer & StoreResults
Retrieve and transfer
Compute
Browse
Retrieve and transfer
Browse
Transfer & StoreResults
Transfer & StoreResults
THE VOICE KO 1603/03/2004
Service Requirements (3)
Co-operation with operational entities possibly to be involved in the prototyping activities Cal/Val, GMES (support by SciSys), ….?
Set-up, distribution and analysis of questionnaire Derived generic model from inventory of e-
Collaboration functional needs Service requirements determination based on
the assessment of specific needs in EO e-Collaboration
Prepare for prototyping (what, how, selection of applications, ….)
THE VOICE KO 1703/03/2004
eCollaboration Technology Survey
Goals To identify technologies helpful for VOs To identify [emerging] Standards for those
technologies To identify the [emerging] tools To identify (a) suite(s) of such tools for a
generic infrastructure
THE VOICE KO 1803/03/2004
Generic, but not too much so needs to be focussed ...
Target Vertical Organisations (i.e. borderlines) User Segments EO / Earth Sciences (only?) Sources within and outside ESA – all integrated
Researchers (s.a. Universities) and Commercial (e.g. Products)
Products and Services – all integrated and offered
eCollaboration Technology Survey
THE VOICE KO 1903/03/2004
Technology areas include GRID (both data access and processing) Webservices Wireless, mobile and Peer-to-Peer (P2P)
Conferencing E-mail and established “offline” communication
methods (s.a. newsgroups and forums) Document sharing (centralised + distributed)
and configuration management
eCollaboration Technology Survey
THE VOICE KO 2003/03/2004
GRID Data access (s.a. ESA’s OpenGRID or DataGRID) Large numerical processing (shared
infrastructure) Resource management and scheduling “Standard” middleware – Globus and Unicore
Points to be addressed by the survey GRID seems ideal for us – but is it? What Standards are emerging (e.g. OGSA, OGSI) What extras does {GRID + webservices}
provide? Security
eCollaboration Technology Survey
THE VOICE KO 2103/03/2004
Webservices WSDL XML and SOAP COM, CORBA and .NET
Points to be addressed by the survey XML is CPU and volume costly
metadata only for large EO products? SOAP interoperability (i.e. standards) &
messaging WSDL interoperability (.NET, Java) Security
eCollaboration Technology Survey
THE VOICE KO 2203/03/2004
Wireless, mobile and P2P Remote, low bandwidth, unreliable
i.e. typically “in the field” usage P2P - simple services (file and device sharing)
Points to be addressed by the survey PDA usage P2P and GRID potential convergence ...
... but in which areas ... and to what extent
eCollaboration Technology Survey
THE VOICE KO 2303/03/2004
Conferencing Tools Virtual Rooms Videoconferencing System
(VRVS) AccessGRID inSORS
eCollaboration Technology Survey
THE VOICE KO 2403/03/2004
Traditional “Offline” information sharing E-mail Newsgroups Forums
Is there any need to survey anything here?
eCollaboration Technology Survey
THE VOICE KO 2503/03/2004
Document sharing Public (and controlled) “read” access Shared, but private, “review” access Private and shared “update” access
Tools Business Collaborator
with configuration management MS SharePoint
two versions, one with CM, one without (Lotus Notes)
eCollaboration Technology Survey
THE VOICE KO 2603/03/2004
ES-generic Collaborative Environment Definition – Step 1
Analysis of ES domain requirements, classification according to main functionality and different layers of the reference infrastructure:
Data Management Service Management User Management
Connectivity, Security, Resource Integration
Workflow Management
Workspace Sharing Data Knowledge Risk Management
…Videoconferencing
Activity Dependant Functionality
Basic Functionality
Common Functionality
Acces Portals Collaboration Applications Layer
Collaboration Middleware Layer
AugmentedConnection Layer
Data Management Service Management User Management
Connectivity, Security, Resource Integration
Workflow Management
Workspace Sharing Data Knowledge Risk Management
…Videoconferencing
Activity Dependant Functionality
Basic Functionality
Common Functionality
Acces Portals
Data Management Service Management User Management
Connectivity, Security, Resource Integration
Workflow Management
Workspace Sharing Data Knowledge Risk Management
…Videoconferencing
Activity Dependant Functionality
Basic Functionality
Common Functionality
Acces Portals Collaboration Applications Layer
Collaboration Middleware Layer
AugmentedConnection Layer
THE VOICE KO 2703/03/2004
ES-generic Collaborative Environment Definition – Step 1
Applications Layer will contain any useful high-level functionality that is needed for ES domain eCollaboration.
Connection Layer will contain requirements related to connectivity like for instance the ones related to network performance requirements, connection topology, storage and computational resource, security issues.
THE VOICE KO 2803/03/2004
ES-generic Collaborative Environment Definition – Step 1
Middleware Layer will contain requirements split according to the main basic functionality: User Management, the ones related to single user
management, like enrolling, authentication, accounting, rights and priorities handling, and group management;
Data Management, the ones related to data representation, archiving, registration, access, sharing, search, retrieval;
Service Management, the ones related to service providing, registration, search, invocation, composition enabling;
Workflow Management, the ones related to complex and integrated service/data access and any other kind of service composition.
THE VOICE KO 2903/03/2004
ES-generic Collaborative Environment Definition – Step 2
Selecting for each functionality the most effective technology
This mapping must be performed taking into account well defined parameters already analysed in the eCollaboration Technology survey: availability, easiness in integration, maturity
and standardisation are among the most important to be considered
Collaborative Elements definition will result from mapping functionality and related technology
THE VOICE KO 3003/03/2004
ES-generic Collaborative Environment Definition – Step 3
Integration and harmonisation of identified Collaborative Elements will provide the ES Collaborative Environment design
SpaceGRID outcomes on defining technological hints for providing seamless access to data, application and resources in the EO domain will also be taken in due account
THE VOICE KO 3103/03/2004
ES-generic Collaborative Environment Definition – Ph2 Plan
Definition of a detailed plan for providing ESA with an effective testbed for the Collaborative Environment where the proposed prototypes will be developed and deployed in the Phase 2
In order to prepare for the prototype design and development activities of Phase 2, during Phase 1 each of the Consortium partners involved in these activities will suitable tailor the proposed prototypes
THE VOICE KO 3203/03/2004
ES-generic Collaborative Environment Definition – Ph2 Plan
For each prototypes the following information will be identified and reported: Actual actors that will be involved in the
prototypes Collaborative Elements needed to enable
required interactions Required interfaces mechanisms between
Collaborative Elements, either they are already available or they have to be developed
Workflow Management mechanisms that will be used to rule the Vertical Organisation activity
THE VOICE KO 3303/03/2004
ES-generic Collaborative Environment Definition – Ph2 Plan
In practice, starting from: ES Collaborative Environment design; detailed description of the prototypes that will
be deployed;
a significant subset of the environment will be selected and a detailed plan for setting it up and make it operable will be provided.
THE VOICE KO 3403/03/2004
ES-generic Collaborative Environment Set Up
Set up at ESRIN premises a possibly generic Collaborative Environment infrastructure for ES domains that: is compliant with the Collaborative Environment
definition provided in Phase 1 fulfils the purpose of the proposed prototyping
activities in Phase 2 within the ESRIN available resources and infrastructure
THE VOICE KO 3503/03/2004
ES-generic Collaborative Environment Set Up
The tasks range from the actual set up of ESRIN resources available for THE VOICE study, through the support in tools installation on the relevant platforms, up to the support in prototypes operations The intention for the Agency to procure other
resources shall be confirmed at Phase 1 Kick Off A first specification of such resources, defined in an
iterative way with the Consortium, would be provided by Agency mid-Phase 1, and the actual resources or a plan when they will be available to the Consortium at Phase 2 Kick Off
THE VOICE KO 3603/03/2004
ENVISAT Cal/Val Prototyping Activities
Criteria for Cal/Val prototype Knowledge of the instrument Knowledge of the data processing Availability of data User interaction e-collaboration Risk assessment
Focus for Cal/Val prototype Ozone from ENVISAT SCIAMACHY (and GOMOS, MIPAS)
combined with potential data from GOME, OMI, and GOME-2 Support by KNMI (and….) Backup: water quality (MERIS)
THE VOICE KO 3703/03/2004
ENVISAT Cal/Val Prototyping Activities
Collaborative Environment for Calibration and Validation of Instruments Onboard ENVISAT, including e.g.
ESA Processing and Archiving Centres (PAC) EUMETSAT Satellite Application Facilities (SAF) NASA Distributed Active Archive Centres (DAAC) Calibration and Validation Data Centres (such as NILU) Instrument Specific Data Centres (such as SCIAMACHY Data
Centre) Scientific Institutions
THE VOICE KO 3803/03/2004
ENVISAT Cal/Val Prototyping Activities
Actors in ENVISAT Cal/Val Expert Support Laboratories NILU Cal/Val Data Centre Validation Groups ESA Sensor Performance and Product Assessment
Section Quality Working Group ESA Post-Launch Support Office ESA PDS (Payload Data Segment) Flight Operations Segment
THE VOICE KO 3903/03/2004
ENVISAT Cal/Val possible actors in their
relationshipConfiguration
Correlative dataQualityWorkingGroup
ESA Sensor Performanceand Product Assessment
Section (ESRIN)
ESA PDS(Payload
Data Segment)
ESL(Expert Support
Laboratories)
ESA FOS(Flight OperationsSegment) (ESOC)
NILU Cal/ValData
Centre
ValidationGroups
Calibration/ValidationOperations and settings
Analysis
Analysis Products
ESA Post-LaunchSupport Office
(ESTEC)
THE VOICE KO 4003/03/2004
VOICE Cal/Val Prototype Environment
The Internet
Firewall
User
Dutch SpaceIntranet
Workflowtool
32-Node DAS-2Cluster at LIACS
(Leiden, NL)
at ESRIN
32-Node DAS-2Cluster at NIKHEF(Amsterdam, NL)
Workflowtool
User
32-Node DAS-2Cluster at VU
(Amsterdam, NL)
The Internet
User
OrganizationLAN
Service Tools
Clienttool
32 Node DAS-2Cluster at LIACS
(Leiden, NL)
32-Node DAS-2Cluster at NIKHEF(Amsterdam, NL)
Clienttool
User
72-Node DAS-2Cluster at VU
(Amsterdam, NL)
TerasSupercomputer
at SARA(Amsterdam, NL)
15-Node Clusterat ESA/ESRIN
(Rome, IT)
Instrument Data
Calibration Data
(assuming we maintainaccess to Grid resources)
THE VOICE KO 4103/03/2004
GMES Open Service Partnership Prototyping Activities
What is GMES? (I promise to be brief….) What is an open service partnership? What is the size of the problem?
Individual Service – Terrafirma All services
What are the implications? Making the technology work for GMES – First
Thoughts Individual Service All Services
What will make a successful prototype?
THE VOICE KO 4203/03/2004
GMES Open Service Partnership Prototyping Activities
Global Monitoring for Environment & Security Single focus for operational EO in Europe – EC & ESA Funding streams being established
Mission Statement:The GMES initiative seeks to bring together the needs of
society associated with the issue of environment and security with the advanced technical and operational capability offered by terrestrial and space borne observation systems.
It is a direct response to the growing concerns amongst policy makers to ensure access to information on the environment at global, regional and local scales without sacrificing independence in the relevant policy areas.
THE VOICE KO 4303/03/2004
GMES Open Service Partnership Prototyping Activities
ESA GMES Service Element Contracts Stage 1: Consolidation, 20 months Policy Based user driven service with Cost Benefit Stage 2: Implementation, to 5 years, 10 yr vision
10 projects defining architectures, 2 more starting:
•Sage•CoastWatch•Icemon•GMFS•Northern View
•Terrafirma•ROSES•RISK EOS•URBAN Services•GSE Forest Monitoring
New Contracts Starting:•Humanitarian Aid•Atmosphere
THE VOICE KO 4403/03/2004
GMES Open Service Partnership Prototyping Activities
What is an open service partnership? Vision (Achache) to federate the fragmented
supply base for EO products in Europe Technically a method of organising multiple
suppliers to create connectivity and capacity to make GMES happen
Challenges standard business philosophy
THE VOICE KO 4503/03/2004
User Domain: “Shop window”
Information Provider Domain
Data Provider Domain (ESA)
Value Adding Company (VAC) Domain
Service Delivery Chain Overview
ProcessProcess Informatio
n
Informatio
n
Earth
Observatio
n Data
Earth
Observatio
n Data
Terrestrial
data
Terrestrial
data
SatelliteSatellite
DiscoverDiscover
Order /
Pay
Order /
Pay
DeliveryDelivery
Process /
Interpret
Process /
Interpret
THE VOICE KO 4603/03/2004
1 2 3 4
a b dc
5
i ii iii iv v vi vii viii VACs
Information Providers
Users
1 - Current Situation – Fragmented Supply
1 2 3 4
a b dc
5
i ii iii iv v vi vii viii VACs
Information Providers
Users
Open Service Partnership
2 - Open Service Partnership “federating” supply of specific products to all users
1 2 3 4
a b dc
5
i ii iii iv v vi vii viii VACs
Information Providers
Users
Open Service Partnership
3 - Open Service Partnership redistributing limited field information among users
Open Service Partnership: Principles
THE VOICE KO 4703/03/2004
In order to define an infrastructure…
ESA GMES GSE
Architecture
Definition
ESA GMES GSE
Architecture
Definition
Current Systems:User Systems Inventory
Precursor Systems
Inventory
Current Systems:User Systems Inventory
Precursor Systems
Inventory
User Service
Needs:Service prospectus
User Needs Analysis
Policy Review
User Service
Needs:Service prospectus
User Needs Analysis
Policy Review
Production NeedsStrategic Plan
Service Portfolio
Production NeedsStrategic Plan
Service Portfolio
Standards:Service Level Agreements
User Standards Handbook
Standards:Service Level Agreements
User Standards Handbook
Data Needs &
VolumeEO Data Sources
Non EO Data Sources
Data Needs &
VolumeEO Data Sources
Non EO Data Sources
TechnologyWhat is possible?
What is acceptable to partners?
TechnologyWhat is possible?
What is acceptable to partners?
THE VOICE KO 4803/03/2004
GMES Open Service Partnership Prototyping Activities
What is the size of the problem? Individual Service – Terrafirma
Detailed information available: Urban Subsidence using InSAR techniques (ERS /
EnviSat) Every large city in Europe (some 200) Off the shelf processed data Geological surveys providing value adding and supply
All services Information from ESRIN (Campbell) Shows the size of the vision (gulp!)
THE VOICE KO 4903/03/2004
THE VOICE KO 5003/03/2004
Data volume / Processes
0
10
20
30
40
50
60
70
80
90
100
1 2 3 4 5 6 7 8 9 10 11 12 13 14
years since beginning of project
no
of
citi
es p
roce
ssed
per
yer
0
500
1000
1500
2000
2500
3000
3500
4000
4500
5000
no
of
scen
es r
equ
ired
per
yea
r
No of cities
No of scenes
THE VOICE KO 5103/03/2004
GMES total data demand (not all services)
S e rvice Type
Fre
qu
ency
Du
rati
on
(d
ays)
Eu
rop
ea
n
To
tal
Eu
rop
ea
n
Ye
arl
y L
oa
d
Glo
ba
l To
tal
Glo
ba
l Ye
arl
y
Lo
ad
S e a ice & ice be rg m onitoring da ily 180 31 5580 185 33300
EEZ surve illa nce (oil slicks, fishing, ships) da ily 365 38 13870 278 101470
Tota ls 69 19450 463 134770
Fore st Are a w e e kly 180 239 6214 2695 70070
Agriculture Are a w e e kly 180/ 365 30 781 836 21737
ICZM inform a tion se rvice s 3 ye a rs 180 220 73 525 175
Urba n Are a s m onthly 365 177 2124 264 3168
P ublic infra structure (da m s, dyke s) m onthly 365 31 372 224 2688
P ublic infra structure (pipe line ) m onthly 365 100 1200 300 3600Tota ls 797 10764 4844 101438
Fore st Are a w e e kly 180 330 8580 6896 179296
Agriculture Are a w e e kly 180/ 365 77 2002 2136 55536
Urba n Are a s m onthly 365 177 2124 264 3168
P ublic infra structure (da m s, dyke s) m onthly 365 31 372 224 2688
P ublic infra structure (pipe line ) m onthly 365 100 1200 300 3600Tota ls 715 14278 9820 244288
Ann ual obs e r vatio n s ce nar io
Num ber of Standard SAR Scenes (100x100 km )
per coverage
Ann ual obs e r vatio n s ce nar io
Num ber of W ide-sw ath ScanSAR Scenes (400x400 km )
per coverage
Ann ual obs e r vatio n s ce nar io
Num ber of M ulitispectra l Scenes (160x160 km )
per cov e rage
NB:Overlap &Cloud
THE VOICE KO 5203/03/2004
What are the implications for the architecture? Data flows: Connectivity and throughput Data Processing: Capacity and scheduling Creating value: integrating data to make information Supply Chain: Ordering, scheduling and delivery
Possible Technologies? Open Standards for geographic information Distributed Processing …?
Implications: Terrafirma
THE VOICE KO 5303/03/2004
Terrafirma: Data Flows
MissionArchiveMissionArchive
MissionArchivesMissionArchives
Acquisition
ArchiveRetrievalArchive
RetrievalProcessing
ChainProcessing
Chain
ImageryRequestImageryRequest
Local Level 1INSAR
Archive
Local Level 1INSAR
Archive
QualityControlQualityControlSatellite
TaskingSystem
SatelliteTaskingSystem
Data Processing
InformationDistribution
Organisation
Process
Data Store
Geologicaland
ReferenceData
Geologicaland
ReferenceData
Key
ReferenceData
ReferenceData
Data flowLevel 1 ProductLevel 2 ProductLevel 3 Product
Request Level 2/3ProductArchive
Level 2/3ProductArchive
Local Level 0
Raw dataArchive
Local Level 0
Raw dataArchive
ExpertOperator Expert
Operator
cataloguecatalogue
Geological Survey /Civil Engineer
Geological Survey /Civil Engineer
End UserEnd User
InformationProvider
InformationProvider
MissionArchiveMissionArchive
MissionArchivesMissionArchives
Acquisition
ArchiveRetrievalArchive
RetrievalProcessing
ChainProcessing
Chain
ImageryRequestImageryRequest
Local Level 1INSAR
Archive
Local Level 1INSAR
Archive
QualityControlQualityControlSatellite
TaskingSystem
SatelliteTaskingSystem
Data Processing
InformationDistribution
Organisation
Process
Data Store
Geologicaland
ReferenceData
Geologicaland
ReferenceData
Key
ReferenceData
ReferenceData
Data flowLevel 1 ProductLevel 2 ProductLevel 3 Product
Request Level 2/3ProductArchive
Level 2/3ProductArchive
Local Level 0
Raw dataArchive
Local Level 0
Raw dataArchive
ExpertOperator Expert
Operator
cataloguecatalogue
Geological Survey /Civil Engineer
Geological Survey /Civil Engineer
End UserEnd User
InformationProvider
InformationProvider
THE VOICE KO 5403/03/2004
Terrafirma: Issues
MissionArchiveMissionArchive
MissionArchivesMissionArchives
Acquisition
ArchiveRetrievalArchive
RetrievalProcessing
ChainProcessing
Chain
ImageryRequestImageryRequest
Local Level 1INSAR
Archive
Local Level 1INSAR
Archive
QualityControlQualityControlSatellite
TaskingSystem
SatelliteTaskingSystem
Data Processing
InformationDistribution
Organisation
Process
Data Store
Geologicaland
ReferenceData
Geologicaland
ReferenceData
Key
ReferenceData
ReferenceData
Data flowLevel 1 ProductLevel 2 ProductLevel 3 Product
Request Level 2/3ProductArchive
Level 2/3ProductArchive
Local Level 0
Raw dataArchive
Local Level 0
Raw dataArchive
ExpertOperator Expert
Operator
cataloguecatalogue
Geological Survey /Civil Engineer
Geological Survey /Civil Engineer
End UserEnd User
InformationProvider
InformationProvider
MissionArchiveMissionArchive
MissionArchivesMissionArchives
Acquisition
ArchiveRetrievalArchive
RetrievalProcessing
ChainProcessing
Chain
ImageryRequestImageryRequest
Local Level 1INSAR
Archive
Local Level 1INSAR
Archive
QualityControlQualityControlSatellite
TaskingSystem
SatelliteTaskingSystem
Data Processing
InformationDistribution
Organisation
Process
Data Store
Geologicaland
ReferenceData
Geologicaland
ReferenceData
Key
ReferenceData
ReferenceData
Data flowLevel 1 ProductLevel 2 ProductLevel 3 Product
Request Level 2/3ProductArchive
Level 2/3ProductArchive
Local Level 0
Raw dataArchive
Local Level 0
Raw dataArchive
ExpertOperator Expert
Operator
cataloguecatalogue
Geological Survey /Civil Engineer
Geological Survey /Civil Engineer
End UserEnd User
InformationProvider
InformationProvider
1: Massive amounts of data needed: Will current order /
transfer systems suffice?
2: Huge increase in processing load: How do VACs cope?
3: Where is the level 1 data stored and how is it managed /
accessed?
4: How to manage the workload? Which VAC does
what and when?
6: How does the information provider organise the
workload?
5: How does the user discover the service and order / pay for
products?
7: How does the information provider produce the
information?
8: How are products re-used?
9: How accessible is this data?
Processing chain
GIS System
L2/L3Local
archive
L1archive
ManualOrderingsystem
Ancillarydata
UserUserGIS
Shopwindow
TerraFirma
Informationprovider
Level 1 ProcessingSAR Archives
L1 catalogue
Architecture at year 2 – Information Provider with Manual System, Level 1 Data Transfer to local copy: dotted line = manual, solid = connected
L1LocalCopy
Processing chain
Scheduler
workflow
GIS Inf. productionL2/L3Local
archive
L1archive
Orderingsystem
E-Commerce
Ancillarydata
UserUserGIS
Shopwindow
TerraFirma
Informationprovider
Level 1 ProcessingSAR Archives
L1 catalogue inc.spatial coverage
WMS / WFS
Architecture at year 5 – Information Provider with Full System, Level 1 Data Transfer on Demand
Tradesman’s Entrance
Architecture at year 10, assuming fast delivery / monitoring and L2/L3 catalogue
Transactions Monitor
Security
Processing chain
Scheduler
FD/monitoring
workflow
GIS Inf. productionL2/L3Local
archive
WMS/WFS
L1archive
WFS
Orderingsystem
E-Commerce
Ancillarydata
WMS/WFS
UserUserGIS
Shopwindow
TerraFirma
Informationprovider
Level 1 ProcessingSAR Archives
L2/L3 catalogue inc spatial coverage
WMS / WFS
L1 catalogue inc.spatial coverage
WMS / WFS
THE VOICE:Use of OGC to provide a seamless archive within the OSP
THE VOICE: Use of OGC WFS/WMS in creating seamless access for production chain
THE VOICE: Use of GRID toScale up processing and facilitate better Connectivity to ESA archives
THE VOICE KO 5803/03/2004
User Domain: “Shop window”
Information Provider Domain
Data Provider Domain (ESA)
Value Adding Company (VAC) Domain
Another Layer Needed?
ProcessProcess
Informatio
n
Informatio
n
Earth
Observatio
n Data
Earth
Observatio
n Data
Terrestrial
data
Terrestrial
data
SatelliteSatellite
DiscoverDiscover
Order /
Pay
Order /
Pay
DeliveryDelivery
Process /
Interpret
Process /
Interpret
GMES
Pre-Production
Mosaic etcMosaic etc
THE VOICE KO 5903/03/2004
Prototype: Updated Workflow.
Evaluate The Key Technology opportunities within the three Terrafirma OSP issue areas
Evaluate The Key Technology opportunities within the three Terrafirma OSP issue areas
Gather Test data / metadata
Gather Test data / metadata
Gather Algorithm information
Gather Algorithm information
Establish & Document Prototype Requirements
Establish & Document Prototype Requirements
Develop PrototypeDevelop Prototype
Internal TestingInternal Testing
Demonstrate & capture Customer Feedback
Demonstrate & capture Customer Feedback
Refine PrototypeRefine Prototype
Deliver PrototypeDeliver Prototype
Check with other prototypes to avoid duplication of effort and agree focus amongst voice consortium
Check with other prototypes to avoid duplication of effort and agree focus amongst voice consortium
Evaluate The Key Technology opportunities within the three Terrafirma OSP issue areas
Evaluate The Key Technology opportunities within the three Terrafirma OSP issue areas
Gather Test data / metadata
Gather Test data / metadata
Gather Algorithm information
Gather Algorithm information
Establish & Document Prototype Requirements
Establish & Document Prototype Requirements
Develop PrototypeDevelop Prototype
Internal TestingInternal Testing
Demonstrate & capture Customer Feedback
Demonstrate & capture Customer Feedback
Refine PrototypeRefine Prototype
Deliver PrototypeDeliver Prototype
Check with other prototypes to avoid duplication of effort and agree focus amongst voice consortium
Check with other prototypes to avoid duplication of effort and agree focus amongst voice consortium
Check against allGSE Projects (Campbell)
Use outputs of BNSC Study
Implications of prototypefindings for wider GMES
THE VOICE KO 6003/03/2004
GMES Open Service Partnership Prototyping Activities
What will make a successful prototype? Relevance to the development and delivery of GMES
Specific issues for one service? More generic issues for entire service offerings?
Obvious benefits to GMES Warms GMES community (including ESA) to technology
solutions Operationally deliverable in the timescales of GMES
(i.e. before 2008) Without specifics it will be impossible to excite those
who are responsible for GMES in ESA and EC
THE VOICE KO 6103/03/2004
Open Agricultural ServicesPrototyping Activities
A prototype to support rural areas activities particular focus - forest management
Three primary methodologies small, economical properties - middle Europe
field measurement - office post processing - 10 year remeasurement
large natural forest - Scandinavia mix satellite imagery & field measurement
dry climate - Mediterranean fire protection
Main challenge - high labour cost
THE VOICE KO 6203/03/2004
Improve Operational Effectiveness
Reduce dependence on field measurement Open access to satellite imagery
Reduce processing Access existing services
Make field work more productive Location-based services eg route planning
THE VOICE KO 6303/03/2004
Collaborative Processes
Interoperability standards Data structures aligned to forestry management
context Formalised service descriptions for discovery Mobile & location management systems Workflow to simplify complex processes Publish & subscribe mechanisms Commercial mechanisms
THE VOICE KO 6403/03/2004
Collaboration Part 1
Service & data publication
User identity Shared views
THE VOICE KO 6503/03/2004
Part 2
THE VOICE KO 6603/03/2004
End -user Support
Lesprojekt Sluzby - Cz Forestry management & wireless system for
rural use Bacchus project – F/I
Viticulture in Southern France and Center Italy Rhône Poulenc Agro - F
Precision agriculture, efficient decision-making tools, sustainable agriculture
Government Forestry Agency - I/Ger? To be identified