geoss architecture for disaster management and risk assessment enterprise architecture concepts
Download
Skip this Video
Download Presentation
GEOSS Architecture for Disaster Management and Risk Assessment Enterprise Architecture Concepts

Loading in 2 Seconds...

play fullscreen
1 / 19

GEOSS Architecture for Disaster Management and Risk Assessment Enterprise Architecture Concepts - PowerPoint PPT Presentation


  • 128 Views
  • Uploaded on

GEOSS Architecture for Disaster Management and Risk Assessment Enterprise Architecture Concepts. John D. Evans, Ph.D. Global Science & Technology, Inc. / NASA Earth Science Technology Office Presented at CEOS-WGISS-32, Budapest, Hungary, 2011-09-27.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' GEOSS Architecture for Disaster Management and Risk Assessment Enterprise Architecture Concepts' - duy


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
geoss architecture for disaster management and risk assessment enterprise architecture concepts
GEOSS Architecture for Disaster Management and Risk Assessment

Enterprise ArchitectureConcepts

John D. Evans, Ph.D. Global Science & Technology, Inc. /NASA Earth Science Technology Office

Presented at CEOS-WGISS-32, Budapest, Hungary, 2011-09-27

using satellite data in disaster management and risk assessment
WGISS-32 – Budapest, HungaryUsing Satellite Data in Disaster Management and Risk Assessment

WGISS

People – Sensors – Data – Processes – Decision Support

using satellite data in disaster management and risk assessment1
WGISS-32 – Budapest, HungaryUsing Satellite Data in Disaster Management and Risk Assessment
  • Involves coordination and linking among
    • Activities of many Independent Parties
    • Different Contexts / Communities of Practice
      • Esp. Vocabulary & Semantics
      • Also Linguistic, Cultural, Economic, Political differences
    • Decisions and Operations using Satellite Data
      • => Greater Effectiveness; Greater Efficiency
  • Requires a shared, precise understanding of
    • Disaster Management and Risk Assessment processes (decisions, operations, etc.)
    • How those processes use (or could use) complex data streams from satellites
using satellite data in disaster management and risk assessment2
WGISS-32 – Budapest, HungaryUsing Satellite Data in Disaster Management and Risk Assessment
  • Involves coordination and linking among
    • Activities of many Independent Parties
    • Different Contexts / Communities of Practice
      • Esp. Vocabulary & Semantics
      • Also Linguistic, Cultural, Economic, Political differences
    • Decisions and Operations using Satellite Data
      • Effectiveness; Efficiency
  • Requires a shared, precise understanding of
    • Disaster Management and Risk Assessment processes (decisions, operations, etc.)
    • How those processes use (or could use) complex data streams from satellites

EnterpriseArchitecture

what s an enterprise architecture
WGISS-32 – Budapest, HungaryWhat\'s an Enterprise Architecture?
  • “A conceptual blueprint that defines the structure and operation of an organization ... to determine how [it] can most effectively achieve its current and future objectives.” (Wikipedia)
  • “A framework for understanding significant relationships among the entities of some environment, and for the development of consistent standards... based on a small number of unifying concepts … may be used as a basis for education and explaining standards to a non-specialist. (ORCHESTRA Ref. Model)
  • “A management practice for aligning resources to improve business performance and help agencies better execute their core missions” (US Federal Enterprise Architecture)
  • “A framework for ensuring IT investments enable the mission and are integrated, efficient and secure” (NASA)
enterprise architecture vs reference model
WGISS-32 – Budapest, HungaryEnterprise Architecturevs. Reference Model
  • An Enterprise Architecture describes the structure of an enterprise, including the business entities, their properties and behavior, and the relationships between these entities.
  • A Reference Model is a conceptual, technology-independent description of entities and relationships within a given environment. It includes a clear description of the problem to be solved, and the concerns of the stakeholders who need the problem solved.
  • These are interchangeable for our purposes – at least for now
what s an enterprise architecture1
WGISS-32 – Budapest, HungaryWhat\'s an Enterprise Architecture?
  • An enterprise architecture (/ reference model) is:
    • Guidance, not a fully detailed plan or blueprint
    • A tool, not a policy
    • A living document – not a fixed specification
  • Provides a logical rather than a physical view
    • Articulates a shared understanding of
      • Needed functions and
      • End-to-end data flows
    • But doesn’t attempt to create inventories of deployed resources
what is the enterprise
WGISS-32 – Budapest, HungaryWhat is the Enterprise?
  • One starting point: GEOSS DI-06-09 charter (Use of Satellites for Risk Management):
    • Reducing loss of life and property from natural and human-induced disasters
    • More specifically: “Define and facilitate implementation of satellite constellations for risk management from a multi-hazard perspective. Undertake the consolidation of the validated requirements and examine options for system development and implementation.”
requirements for our enterprise architecture reference model
WGISS-32 – Budapest, HungaryRequirements for our Enterprise Architecture / Reference Model
  • Allow for regional differences – policies, economics, language, etc.
    • Not an abstract, one-size-fits-all architecture
  • Allow for a variety of types of disasters
  • Support both disaster response and risk assessment
  • Build on / be consistent with existing architectures and semantics
    • GEOSS Architecture Implementation Pilot - AIP3
    • GEOSS 10-Year Action Plan
    • UN-SPIDER
    • International Charter; others?
building an enterprise architecture architecture frameworks
WGISS-32 – Budapest, HungaryBuilding an Enterprise Architecture: Architecture Frameworks
  • An Architecture Framework defines levels, layers, or views used in constructing an enterprise architecture or reference model
    • e.g., Business / Applications / Data / Technology
architecture frameworks
WGISS-32 – Budapest, HungaryArchitecture Frameworks
  • ISO/IEC Reference Model for Open Distributed Processing (RM-ODP)
  • Seems like a good fit here:
    • Distributed data handling
    • Open systems approach
    • Used by related enterprise architectures:
      • GEOSS Architecture Implementation Pilot (AIP-3)
      • ORCHESTRA (European Union - Service Oriented Architecture for EU Risk Management)
      • INSPIRE (Infrastructure for Spatial Information in Europe)
enterprise viewpoint
WGISS-32 – Budapest, HungaryEnterprise Viewpoint
  • Enterprise questions to be addressed for GA4D:
    • What are the purpose and scope for the use of satellite data in Disaster Management and Risk Assessment?
    • What activities are involved?
    • In what organizational structures do (or must) these activities take place?
    • Who are the participants in these activities?
    • Who are the stakeholders for this architecture – who has (or should have) a say in how these activities draw on information from satellites (and elsewhere)?
    • What other enterprises are linked to this one?
    • Include Roles
    • Use cases

Scope

information viewpoint
WGISS-32 – Budapest, HungaryInformation Viewpoint
  • Information questions to be addressed for GA4D:
    • What observations or parameters are needed when responding to different kinds of disasters (or assessing their risk)?
    • In what forms does this information best support the enterprise?
    • What metadata are needed to ensure that data can be found and appropriately used?
    • What inter-dependencies exist among these data products?
    • What data transformations, interpretations, extractions, syntheses, etc. are needed between sensors and users?
information viewpoint1
WGISS-32 – Budapest, HungaryInformation Viewpoint
  • Observations types vs. Societal Benefit Areas

From GEO Task US-09-01a

Critical Earth Observation Priorities

Summary of Results • October 2010

information viewpoint2
WGISS-32 – Budapest, HungaryInformation Viewpoint
  • Observations types vs. Disaster Types

From GEO 10-Year Implementation Plan Reference Document • February 2005

computation viewpoint
WGISS-32 – Budapest, HungaryComputation Viewpoint
  • Information questions to be addressed for GA4D:
    • What service types are needed to make the necessary information available to users?(e.g., data access, visualization, catalog search)
    • How will these service types effect the data transformations, interpretations, extractions, syntheses, etc. that are needed between sensors and users?
    • What requirements apply to these services and interfaces (e.g., near-real-time performance, cross-community interoperability)
engineering viewpoint and technology viewpoint
WGISS-32 – Budapest, HungaryEngineering Viewpointand Technology Viewpoint
  • Engineering questions to be addressed for GA4D:
    • What interface types are needed to invoke the services described in the computation viewpoint? (e.g., stateless / stateful; pull / push)
    • What interface standards are needed to support interoperation between different communities?
  • Technology questions to be addressed for GA4D:
    • What satellite data streams are available? Needed?
    • What catalogs are available? Needed?
ad