GIS in a Loosely Coupled Environment. (Making GIS an Enterprise Commodity) Peter Trevelyan, Graham Mallin, Jeremy Tandy ESRI UC San Diego 2007 June 18th © Crown copyright
Page 1
Outline of the Talk?
What does the Met Office do? Where does GIS fit into our IT strategy? Where does GIS fit into our customers strategy? What kind of Architecture do we want? A new production process.
© Crown copyright
Page 2
What does the Met Office do?
© Crown copyright
Page 3
Some Issues:
Part of Ministry of Defence Trading fund Employs 1,700 people 100 sites world wide Founded 1854
© Crown copyright
Page 4
Our international standing Leading member of World Meteorological Organization (WMO) World Area Forecast Centre for civil aviation Regional hub of WMO Global Telecommunication System Leading role in WMO World Climate Programme Leading role in world scientific community
© Crown copyright
Page 5
ublic services
National Severe Weather Warning Services Shipping Forecast Storm Tide Forecast Service Atmospheric pollution Education
© Crown copyright
Page 6
National Severe Weather Warning Service (NSWWS)
Set up following the 1987 Storm with the help of
Cabinet Office from the pre-existing Flash Warning service
NSWWS provides support to the 9public at large via media 9civil emergency authorities 9MOD
© Crown copyright
Page 7
Private sectors
© Crown copyright
Transport Energy Leisure Commercial Marine Independent Media Retail Insurance Construction
Page 8
Health forecasting
Weather sensitivity Your health is sensitive to the weather
© Crown copyright
Falls - broken bones Heart attacks Strokes Asthma Bronchial complaints Flu epidemics
Page 9
What are the problems we want to solve?
© Crown copyright
Page 10
Some Issues: A number of business application require a GIS business layer; Traditionally each application has its own solution space; Difficult to integrate output with collaborating partners; Difficulty in integrating GIS output originating from different GIS vendors; Creating a SDI (Spatial Data Infrastructure); The Met Office is a provider of environmental solutions i.e. it is not a mapping service.
© Crown copyright
Page 11
What kind of world would we like? One that makes the following GIS functions through standard interfaces available to any consumer. What do we mean by GIS functions?
Geoprocessing, Mapping, Discovery of data and their relationships, Exporting and importing data.
© Crown copyright
Page 12
The Met Office IT strategy:
© Crown copyright
Page 13
So how do we achieve this?
We Need a radically new approach; What technologies do we have available;
© Crown copyright
Distributed Services; High speed connectivity; Commodity hardware; Advent of standards (W3C, OASIS, ISO, OGC etc); Remote invocation i.e. web services,
Page 14
Use of Standard Interfaces Open Geospatial Consortium (OGC) have defined a number of specifications for accessing geospatial information .. Maps, Features and Grids. Simple web-service interfaces has lead to widespread adoption. Service specifications adopted by ISO.
© Crown copyright
Page 15
Use of Standard Interfaces Adoption of these standards means much of the hard work in specifying interfaces has already been done. Standards-based approach allows us to integrate services outside the Met Office. Still need to use non OGC interfaces to exploit COTS solutions.
© Crown copyright
Page 16
Met Office Future IT Architecture Our future IT will be based on composite applications taking the best of what we have making it available dynamically to web browsers
GPS
Additional real-time data
Data products Specifications
Decision Support
Mapping Data Observations
Models
Analysis
Maps, static content
Met Office real-time data
© Crown copyright
Page 17
The IT strategy of our customers: The Ministry of Defence is moving to a netcentric approach. The is a much greater appreciation of the use of standards. The realisation that no single system can solve all the problems, thus: A much greater need for the IT strategy to support a heterogeneous approach. A recognition that individual systems must be procured on the basis the they will form a part of the whole. © Crown copyright
Page 18
The Advent of SOA (So what is it?)
© Crown copyright
Page 19
SOA Concepts
Service Registry Discover
Publish
Service Description
Service Description
Invoke Service Consumer
© Crown copyright
Service
Result
Service Provider
Page 20
Interactive web-client vision Providing context for decision support: high-quality mapping layered weather data Integrated external information geoprocessing derived features real-time data
© Crown copyright
Page 21
Composite Applications
Business Function
Elemental Business Function Plot Contours
Plot Met.
Render Image
Draw Map
Existing System
GPCS © Crown copyright
Horace
Radarnet
ESRI Page 22
Functionality = Service
Plotted Obs Plotted Coastal Obs outlines
NWP data Satellite imagery Annotated fields
© Crown copyright
Page 23
GIS across the network:
Map Visualization Client
WFS
ML features Weather data).
WMS
ESB
WFS
Arc Gis Server
Weather images/ Non-met features Arc SDE Background Map © Crown copyright
Page 24
OGC and GRIDS
Internet Response (CF-Netcdf File)
Request
Geoserver
CF-Netcdf Output Formatter
WCS Oracle
GeoTools CoverageStore
Grib
FieldsFiles
Netcdf Library Netcdf © Crown copyright
Page 25
Standard Data Formats Rendered into a map AND queried by a user or….
A user makes a request and gets back GML based data which can be ….
… formatted into a report or ….
… read and used by any enabled application © Crown copyright
Page 26
Principles of the proposed new production process:
© Crown copyright
Page 27
Proposed new production process: The heart of this strategy is to make the process “product definition” centric by using a document (the (Product Definition File) that will:
© Crown copyright
Describe the content, content layout and the method (or service binding) by which the content is created. Centrally stored and catalogued (Products and services database) Hold a host of metadata, including details such as customer, ownership, format, destination etc.
Page 28
Proposed new production process:
Each graphic will be made up by aggregating layers e.g. radar, satellite, cartographic etc. Each layer will be provided by a separate service that will be accessed across the network. Only supported service for any particular layer e.g. radar imagery, plotting observations, mapping, geoprocessing, contouring etc. Geoprocessing will be an added value service.
© Crown copyright
Page 29
The Registry
© Crown copyright
Page 30
Design and implementation of a registry
Model the information that makes up the customer and services relationships. Based on use of concepts within the OGC WRS (Web Registry Service). WRS is based on ebRIM and ebXML that are fast becoming industry de-facto standards. Registry holds both technology and commercial information and their relationships.
© Crown copyright
Page 31
What is a registry? - definition A registry is an information system on which a register is maintained A register is a controlled list of information (ISO19135 Geographic Information – procedures for item registration) Registry
© Crown copyright
Page 32
Information hub
Portal
Registry
When combined with a portal, the registry acts as a hub within the distributed data infrastructure …
Providing an aggregated view of content from numerous, heterogeneous information resources
Information resources © Crown copyright
Page 33
Focal-point Registry provides focal-point: Portal Search & browse by exposing iscovery metadata
Service invocation
Data
Registry
Discovery metadata © Crown copyright
Propagating best practice, standards and governance
Discovering and exploiting information resources and services Discovery metadata for content offerings Service metadata for binding to information resources
Service metadata Page 34
Design of the Catalogue
© Crown copyright
Page 35
Creating products using a SOA
© Crown copyright
Page 36
SOA Orchestration
service
service
service
service
service
Orchestration Engine
Orchestration rules
© Crown copyright
Page 37
SOA Orchestration
service
service
service
service
service
Orchestration Engine
Orchestration rules
© Crown copyright
Page 38
Putting it all together
Legacy DB
Legacy
DMMS
ATD data
ArcIMS
WFS
ebRIM Catalogue
Scheduler
FPS
read Catalogue
Produce XML stream
S1
Layout WMS
S2
other
S3 ..
Aggregate
ESB (Enterprise Service Bus)
© Crown copyright
Page 39
Registry to document definition
Application
XML Message
Registry
ESB Message Queue © Crown copyright
Page 40
Connecting to the services
XML Message
Parser
HTTP XML Message
RMI XML Message
ESB http Gateway
ESB rmi Gateway
Service
service
Graphic © Crown copyright
service
ESB
Graphic Page 41
Document preparation
Email
Text
PDF
Logo
Word
Graphic
JPEG
ftp
Copy
Open Document Layout Defn © Crown copyright
Page 42
Example Output
© Crown copyright
Page 43
Lightning data rendered from GML data.
© Crown copyright
Page 44
A Sig Weather chart and USG map combo
© Crown copyright
Page 45
Gaia
© Crown copyright
Page 46
The Future:
© Crown copyright
Page 47
Future SOA Architecture customer content creation and data services Met Office systems – thin or thick client
customer systems – thin or thick client
human workflow
Met Office content creation and data services ESB batch workflow registry
scheduling
customer information © Crown copyright
Page 48