jason tuell office of science and technology n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Jason Tuell Office of Science and Technology PowerPoint Presentation
Download Presentation
Jason Tuell Office of Science and Technology

Loading in 2 Seconds...

play fullscreen
1 / 16

Jason Tuell Office of Science and Technology - PowerPoint PPT Presentation


  • 81 Views
  • Uploaded on

The Evolution of AWIPS NWS Partner’s Meeting 20 June 2007. Jason Tuell Office of Science and Technology. Overview. Why AWIPS Evolution? What is it? Outcomes and Objectives Re-architecture Approach Roadmap What does AWIPS II mean to the Partners? Summary.

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 'Jason Tuell Office of Science and Technology' - ahava


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
jason tuell office of science and technology

The Evolution of AWIPSNWS Partner’s Meeting20 June 2007

Jason Tuell

Office of Science and Technology

overview
Overview
  • Why AWIPS Evolution?
  • What is it?
  • Outcomes and Objectives
  • Re-architecture Approach
  • Roadmap
  • What does AWIPS II mean to the Partners?
  • Summary
slide3
Case for change briefed to NWS Corporate Board – Nov 2004

AWIPS Present State Summary

Hardware

AWIPS hardware was in good shape

Communications Infrastructure

AWIPS communications infrastructure was in OK shape

Data

AWIPS Data was in need of improvements

Software

AWIPS software was in critical need of improvements

Costly software development, maintenance and inability to meet NWS and customer needs

Corporate board direction to focus on addressing software shortcomings

Plan and requirements developed

Shaped portions of the AWIPS O&M re-compete activity

WHY?
what is awips evolution
What is AWIPS Evolution?
  • AWIPS Evolution
    • A long-term project which delivers a modern, robust software infrastructure that provides the foundation for future system level enhancements
  • AWIPS II
    • Implements a modern Services Oriented Architecture (SOA) infrastructure
    • First output of AWIPS Evolution and provides the foundation for all subsequent improvements
  • AWIPS Evolution System Improvements
    • Integration of “orphan” systems (e.g., Weather Event Simulator)
    • Migration of N-AWIPS into the SOA to create a seamless weather enterprise that supports all levels of NWS operations from National Centers to WSOs
    • Data Delivery Enhancements
      • “Smart push-smart pull” data access
      • Katrina satellite WAN back up
    • Integrated visual collaboration
      • Graphical collaboration at all levels of the weather enterprise extending to trusted external partners
    • Visualization Enhancements
    • Information Generation Enhancements
      • Re-architecture of the generation of all NWS products and services
awips evolution objectives
AWIPS EvolutionObjectives
  • Establish Service Oriented Architecture for AWIPS and NAWIPS
    • Create a seamless weather enterprise that supports all levels of NWS operations from National Centers to WSOs
    • Build a common development environment that will be used by all developers
    • Establish infrastructure for GIS integration
  • Enable access to data independent of its location, i.e., provide access to data not resident locally at the WFO or RFC.
  • Provide infrastructure for real time graphical collaboration between
    • WFOs, RFCs and centers for enhanced internal collaboration
    • Other NOAA entities and
    • Trusted partners, e.g., Emergency Managers
  • Implement a Common AWIPS visualization environment (CAVE) used by all applications
  • Standardize generation of NWS products and services
awips evolution outcomes
AWIPS EvolutionOutcomes
  • Short-term (1-3 years)
    • Shorten transition of research to operations
    • Improve software O&M and technology refresh
      • Fewer DRs and TTs
      • Focus on hardening and productionizing for life cycle support
    • Minimize adverse impacts on operations from software and hardware upgrade
  • Long-term (3-10 years)
    • Increase integration of hydrologic and meteorological activities
    • Improve performance and functionality of AWIPS
    • Increase integration of AWIPS and National Center AWIPS
    • Improve collaboration at all levels of NWS operations
    • Increase access to all environmental data for decision making
awips ii re architecture approach
AWIPS IIRe-Architecture Approach
  • Perform “black-box” conversion
    • Preserve existing functionality, look and feel on top of new infrastructure
  • Thorough field validation and acceptance before deployment
  • No loss of functionality
    • Deployed system current with deployed AWIPS capability (i.e., OB9)
  • Use open source projects - No proprietary code
    • JAVA and open source projects enable AWIPS II to be platform and OS independent
      • No plans to move from Linux
  • Objective is to make AWIPS II available for collaborative development
    • OS, Platform independence allows non-Linux based research to be easily integrated into AWIPS II
slide8

AWIPS IIRoadmap

AE OSIP Gates

2

3

4a

Meshed Topology

4b

Analysis

ADE Training Development

PIP

ADETraining

Migration Planning

RTSIRAD

ADE Development

AWIPS II 1.0

06/22/07

Migration

Strategy

2010

2006

2007

2008

2009

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

slide9

AWIPS EvolutionRoadmap

2007

2008

2009

2010

2011

2012

2013

2014

Baseline Application Migration

IOC

FOC

Data Delivery

Phase 1 Collaboration

Phase 2

Phase 3

= Calendar Year

IOC

FOC

Information Generation

= Fiscal Year

IOC

Visualization

AWIPS II

AWIPS II

OTE / Deployment

Governance Model

NAWIPS Migration

SOA

Enhancements

Thin Client

WES Integration

AWIPS II

Enhancements

awips ii what does it mean to the partners
AWIPS IIWhat does it mean to the Partners?
  • Transition (Mid 2009 - mid 2010)
    • Limited changes during transition
    • Only minor updates to products and services
  • AWIPS II – 2010
    • More robust infrastructure
    • Faster software installations – less downtime while delivering new software
awips ii what does it mean to the partners1
AWIPS IIWhat does it mean to the Partners?
  • AWIPS II – 2011
    • Thin client support
      • Integrates CWSUs, WSOs and Incident Meteorologists
    • NAWIPS migrated to SOA
      • One infrastructure for meteorological applications spanning operations from National Centers to WSOs
    • Improved satellite back up for terrestrial network
      • Improves continuity of operations during Katrina-like events
    • Smart push-smart pull data delivery
      • Improved access to broader sets of data than is currently delivered over the SBN
    • Integrated graphical collaboration
      • Improved coordination at all levels of NWS weather enterprise
awips ii what does it mean to the partners2
AWIPS IIWhat does it mean to the Partners?
  • AWIPS II – 2012-2014
    • Extend graphical collaboration
      • NOAA offices
      • Trusted external partners, e.g., DHS and Emergency Managers
    • Smart push-smart pull data delivery
      • Extend data services to other NWS services for product delivery
    • Re-architect generation of products and services
      • More responsive to customer requests, e.g. CAP
      • Streamline process so developers and meteorologists focus on content vice format
summary
Summary
  • AWIPS Evolution underway!!
    • ADE/SDK 1.0 delivered June 14, 2007
  • Application migration underway
    • Migration Plan delivered June 2007
    • AWIPS baseline migration to be completed FY09
  • Deployment complete FY10
  • AWIPS II will deliver capabilities that enable NWS to be more responsive to Partner requirements
awips ii features
AWIPS II Features
  • AWIPS Development Environment (ADE)
    • Used by all AWIPS developers (National, Regional, & Local)
    • Developers concentrate on new capabilities, not re-implementing existing ones (i.e. screen I/O, communications protocols, data access routines, logging routines, or other previously developed capabilities)
    • Software can be developed on a variety of platforms
  • Robust infrastructure for improved software O&M
    • Use of plug-ins: visualization extensions; new data types and transforms
    • System level, remediation, core services reduce system complexity
    • Improved support for local requirements (e.g., local apps, scripts, plug-ins)
  • Common AWIPS Visualization Environment (CAVE)
    • Provides a common development and execution environment for AWIPS GUIs (e.g. D2D, NMAP, GFE, etc.)
    • Ability to pan/zoom large data sets (Raster & Vector) with flexibility over data rendering
    • GIS tools
    • Thin Client (Web Browser) enabled
awips ii risks and challenges
AWIPS IIRisks and Challenges
  • Performance
    • Supporting the short fuse warning mission
    • Handling large global data sets
  • Schedule
    • Completing the migration and testing
  • Migration of local applications
    • Local applications outside the baseline and not a Raytheon responsibility