slide1 l.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
AWIPS II Evolution Overview 16 May 2008 Steve Schotz Office of Science and Technology PowerPoint Presentation
Download Presentation
AWIPS II Evolution Overview 16 May 2008 Steve Schotz Office of Science and Technology

Loading in 2 Seconds...

play fullscreen
1 / 20

AWIPS II Evolution Overview 16 May 2008 Steve Schotz Office of Science and Technology - PowerPoint PPT Presentation


  • 329 Views
  • Uploaded on

AWIPS II Evolution Overview 16 May 2008 Steve Schotz Office of Science and Technology. Purpose. AWIPS II Evolution Scope AWIPS II Evolution Schedule AWIPS II Evolution Improvements AWIPS II High Level Architecture. AWIPS Evolution Scope. AWIPS Evolution (FY2005 – FY2014)

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 'AWIPS II Evolution Overview 16 May 2008 Steve Schotz Office of Science and Technology' - emily


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
slide1

AWIPS II Evolution Overview16 May 2008

Steve Schotz

Office of Science and Technology

purpose
Purpose
  • AWIPS II Evolution Scope
  • AWIPS II Evolution Schedule
  • AWIPS II Evolution Improvements
  • AWIPS II High Level Architecture
awips evolution scope
AWIPS Evolution Scope
  • AWIPS Evolution (FY2005 – FY2014)
    • A long-term project which delivers a modern, robust software infrastructure that provides the foundation for future system level enhancements for the entire NWS enterprise

Phase 1: AWIPS II – Migration of WFO/RFC AWIPS (FY2007-FY2009)

    • Implements a modern Services Oriented Architecture (SOA) infrastructure
    • First output of AWIPS Evolution and provides the foundation for all subsequent improvements

Phase II: AWIPS II Extended - Creation of a seamless weather enterprise spanning NWS operations (FY2009-FY2010)

    • Migration of NAWIPS into the AWIPS II SOA
    • Delivery of thin client
      • Support to the Weather Service Offices and Center Weather Support Units
    • Integration of “orphan” systems (e.g., Weather Event Simulator)
    • CHPS Integration into AWIPS II SOA

Phase III: AWIPS II enterprise enhancements (FY2009 – FY2014)

    • Data delivery enhancements
      • “Smart push-smart pull” data access
    • Integrated visual collaboration
    • Visualization enhancements
    • Information generation enhancements
slide4

AWIPS EvolutionRoadmap

2007

2008

2009

2010

2011

2012

2013

2014

Baseline Application Migration

WES Integration

IOC

FOC

NWS Integrated Collaboration

Phase 2

Phase 3

= Calendar Year

= Fiscal Year

IOC

3-D Visualization

AWIPS II

AWIPS II

OTE / Deployment

AWIPS II – Open Source

Governance Model

Integrated support to FAA, Fire Weather and WSOs

NAWIPS Migration

AWIPS II

Extended

Thin Client

Collaboration with Emergency Managers

CHPS

AWIPS II

Enhancements

Smart push-smart pull data access

IOC

FOC

Streamlined Generation of Products

slide5

AWIPS II

Roadmap

3

4a

Meshed Topology

4b

Analysis

ADE Training Development

PIP

ADETraining

Migration Planning

RTSIRAD

ADE Development

AWIPS II 1.0

12/05/07

Migration

Strategy

2010

2006

2007

2008

2009

AE OSIP Gates

2

MPLS

OBx

8.3

9

7

8

8

10

Deployment

OB 9 Dev & Test

New Release

Paradigm

SW CTR (AWIPS II)

NWS New Capability Development in ADE

O & M Transition

O & M Transition Prep & Coordination

Baseline Application Migration

OTE / Deployment Support

Note: Task bar colors are

For speaker reference only

“User” Functional Tests

ADE Local App Training

Local App Migration

C & A

OTE

= Calendar Year

Deployment

Deployment Planning

= Fiscal Year

Field Ops Training

-- ITO, ESA

awips evolution nws enterprise improvements
AWIPS EvolutionNWS Enterprise Improvements
  • More responsive to partner needs – reduce development time of new products by 50%
  • Direct and integrated visual collaboration with all levels of NWS operations - National Centers, RFCs, WFOs, WSOs
  • Streamlined generation of products in industry standard formats
    • CAP, GIS, etc.
  • Expanded access to data for NWS and external partners
    • SBN enhancements, smart push-smart pull
  • Improved and integrated incident support for Emergency Managers and DHS
  • Better weather support for the FAA at CWSUs through enterprise level integration
awips evolution internal improvements
AWIPS EvolutionInternal Improvements
  • Free operations from technology constraints
    • Seamless, flexible and extensible weather enterprise that integrates all levels of NWS operations
    • Integrated service delivery via the migration of AWIPS and NAWIPS into a common Service Oriented Architecture
  • Improved continuity of operations
    • Streamlined service back up
    • Faster software installations
    • More stable operations – fewer bugs
  • Put new science into operations faster – more accurate warnings and forecasts
    • Enable collaborative development between local, national and outside developers
    • Open source – closed community – open up development to local apps developers and those outside traditional development community, e.g. NASA, academia
soa architecture logical layered view layers separated by simple apis

<<Java>>

HDF5DataStore

<<Java>>

DataLayer

<<abstract>>

BaseDao

SOA Architecture – Logical Layered ViewLayers Separated By Simple APIs

Client/Presentation Services

JMX

CAVE

External Programs

Mission Services Layer

Mbean

ProductSrv

IngestSrv

NotifySrv

Hydro Models

AdapterSrv

AutoBldSrv

PersistSrv

IndexSrv

SubscribeSrv

UtilitySrv

LAPS

Security Services /Demilitarized Zone (DMZ)

Enterprise Service Bus - Communication

PurgeSrv

StagingSrv

FORTRAN/C/C++

Command Line

Programs

Data Access Layer

Hibernate

HDF5 API

Localization

Store

Platform Layer

PostgreSQL

HDF5

Data Persistence

Store

Metadata

Index

Spatial

Index

awips ii ade high level system services soa services running in an esb container
AWIPS-II ADE High Level System ServicesSOA Services Running in an ESB Container

CORE SOA Services

JMX Remote

Service Management

Client

WAN Visible

ADE 1.0

Updated T06

Mbean

Mbean

Mbean

Mbean

Mbean

IngestSrv

StagingSrv

PersistSrv

PurgeSrv

IndexSrv

ProductSrv

AdapterSrv

CAVE

Visualization

Client

FileSystem

Meta Data Index

uEngine

Exec Adapter

Data Rendering

METAR Plug In

RDBMS via JDBC

Spatial Data Base

Manage Subscription

JNI Adapter

CAVE Bundles

Radar Plug In

HDF5 persistence

GFE IFPServer

Data Interrogation

Satellite Plug In

CAVE Procedures

GRIB Plug In

Wx Drawing

Wx Warning

Radar All Tilts

Hydro Visualization

Mbean

Mbean

Mbean

UtilitySrv

NotifySrv

AutoBldSrv

Collaboration

uEngine

Localization Data

Subscription Notify

XMPP

Color Tables

Maps and Topo

Enterprise Service Bus – HTTP, JMS, Virtual Memory, File Endpoints

Enterprise Service Bus – HTTP, JMS, Virtual Memory, File Endpoints

Services Independent of End Points

awips migration re architecture approach
AWIPS MigrationRe-Architecture Approach
  • Preserve existing AWIPS functionality
  • Minimize changes to user interfaces – “Black Box” conversion
    • Minimizes user training of forecasters and administrators
  • Leverage use of AWIPS II services, functionality and development tools to optimize migration
    • AWIPS II uses open source projects - No proprietary code
    • AWIPS II is platform independent
  • AWIPS functionality incrementally to AWIPS II to reduce risk
    • Multiple deliveries planned using RTS Task Orders
awips ii infrastructure promising attributes thus far
AWIPS II InfrastructurePromising Attributes Thus Far
  • Dynamic load balancing
    • Failover handled automatically!!!
    • Takes full advantage of all available hardware
    • Scalable hardware (clustering)
  • Significant performance improvements
    • Borrows techniques from video games - mathematically intensive calculations handed off to the graphics card; image remapping on the fly
  • Google Earth-like disclosure of imagery, grids and observations
    • Allows zooming in of satellite imagery with full resolution
    • Architecture is scale independent
  • Integrated drawing and graphical collaboration
    • Tools built into the infrastructure, implemented in 2011
  • Improved reliability
    • LESS CODE - Potential order of magnitude reduction in amount of software
    • Reduced code complexity

TM

summary
Summary
  • New SOA architecture defined and infrastructure delivered
    • ADE 1.0 delivered June 2007
    • TO8 Partial D2D Functionality Feb 2008
  • AWIPS I migration underway
    • AWIPS baseline migration to be completed FY09
  • NAWIPS Migration and “smart push- smart pull” work to start in FY09, delivery in FY11
  • Long term technology roadmap defined that supports many of the 4-D cube concepts
awips evolution data delivery
AWIPS EvolutionData Delivery
  • OSIP Project 05-040
  • Enables “smart push - smart pull” data delivery
    • Implements a discovery service within the SOA
    • Access to data not available locally
    • Freedom from the tyranny of the SBN
    • Enables consideration of new data delivery architecture
      • What data to you broadcast over SBN?
      • What data do you make available on servers?
  • Schedule
    • IOC - 2011 - software implementation for remote data access
    • FOC 2012 - enterprise configuration (servers, comms, etc.) that enables remote data access
awips evolution collaboration
AWIPS EvolutionCollaboration
  • OSIP Project 05-041
  • Objective
    • Integrated graphical collaboration throughout the NWS Weather Enterprise and beyond
    • Phase 1 - Integrated collaboration between all levels of NWS operations
    • Phase 2 - Collaboration between NWS offices and other NOAA entities
    • Phase 3 -Collaboration between NWS offices and trusted external partners, e.g., Emergency Managers
  • Schedule
    • Phase 1 IOC - 2011
    • Phase 2 IOC - 2012
    • Phase 2 IOC - 2013
awips evolution information generation visualization
AWIPS EvolutionInformation Generation & Visualization
  • OSIP Projects 05-042 (IG) and 05-021 (Vis)
  • Information Generation objective
    • Re-architect generation of all NWS products and services
    • Separation of content generation from formatting and dissemination
    • Enable faster response to emerging customer demands
  • Visualization objective
    • Common user interface - standardize User Interfaces across applications
    • 3-D visualization
    • Improve user interfaces based on latest principles and research
awips evolution governance model
AWIPS EvolutionGovernance Model
  • What is it?
    • Governance model controls the development, test, integration, configuration management, deployment and support of the new system -- both hardware and software
  • Why?
    • AWIPS II offers new levels of flexibility and extensibility
    • New rules needed to exploit system capabilities, define limits
    • Tension between unlimited modifications and ability to support the baseline system
  • Sample issues for consideration
    • Monolithic configurations no longer required -- how do we manage site specific configurations?
    • Plug ins can be down loaded and installed on demand
    • Scripting that modifies AWIPS menus, functions
  • Flexible Governance Model enhances open source implementation
    • Open source – closed community model
    • Path to baseline defined for local and externally developed applications
    • Definition of “sand box” for development and execution of local applications without impacting operations
awips ii testing
AWIPS IITesting
  • Objective: Deliver a system that delivers today’s functionality with no impact on operations
  • Layered testing strategy
    • Different testing phases overlap – functionality tested multiple times in different settings
    • Significant field participation in testing
  • ADE usage
    • Not formal testing, but expect to get feedback as developers use the ADE
  • Algorithm Verification & Validation –
    • Assist algorithm choice
    • Verify port of algorithms
  • Verification & Validation
    • Executed by dev orgs in controlled setting
    • Performance testing – Evaluate system against known and developing benchmarks
    • Acceptance testing – part of the task order acceptance process
  • Field Evaluation
    • Side by side testing of new system by field personnel in a “lab” environment
    • Testing at limited number sites in manner that doesn’t impact operations
  • Operational Test & Evaluation (OT&E)
    • Formal testing of the entire system
    • Tests system interfaces, operations, support, training, etc.