1 / 15

Advanced Weather Interactive Processing System (AWIPS) Overview for System-of-Systems Workshop October 7, 2009

Advanced Weather Interactive Processing System (AWIPS) Overview for System-of-Systems Workshop October 7, 2009. Ronla Henry & Steve Schotz NWS – Office of Science and Technology. AGENDA. AWIPS Overview Mission and Functions Brief History AWIPS II Technology Infusion Scope and Milestones

adamdaniel
Download Presentation

Advanced Weather Interactive Processing System (AWIPS) Overview for System-of-Systems Workshop October 7, 2009

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Advanced Weather Interactive Processing System (AWIPS) Overview for System-of-SystemsWorkshopOctober 7, 2009 Ronla Henry & Steve Schotz NWS – Office of Science and Technology

  2. AGENDA • AWIPS Overview • Mission and Functions • Brief History • AWIPS II Technology Infusion Scope and Milestones • AWIPS II Architecture Overview • Major Software Components • Communications Interfaces • Standards and Formats • AWIPS II Extended Data Delivery Project Overview

  3. NEXRAD GOES/POES Warnings NCEPModels Watches Advisories ASOS Forecasts Buoys, River Gauges AWIPS Overview - Functions/MissionAWIPS is the Critical Link to the NWS Forecaster 169 separate AWIPS systems at 137 geographical locations AWIPS Communications AWIPS Workstations and Servers Service provided to 3066 US Counties 24 hrs/day, 365 days/yr. ~900 Workstations (total) ~1200 Servers (total)

  4. AWIPS Overview - Service Delivery Facilities in Six NWS Regions

  5. AWIPS ABrief History • The original prime contract for system development was awarded to PRC, Inc on December 29, 1992 • To replace Automation of Field Operations and Services (AFOS) • PRC, Inc later acquired by Northrop Grumman IT (NGIT) • Commissioned - 2000 • Operations phase of original contract expired on September 30, 2005 • Re-compete contract awarded to Raytheon Technical Services (RTS) on August 17, 2005 • Proposal included a high level plan to re-engineer AWIPS software into a Service Oriented Architecture (SOA), AWIPS II

  6. AWIPS II Technology Infusion Scope AWIPS II Technology Infusion (FY2005 – FY2015) • 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: (FY2006-FY2011) • Migration of WFO/RFC AWIPS (AWIPS I) to a modern Service Oriented Architecture (SOA) infrastructure executed incrementally through a series of task orders • Phase II: (FY2009-FY2012) – AWIPS SOA Extension • Creation of a seamless weather enterprise spanning NWS operations • Migration of NAWIPS into the AWIPS ISOA • Delivery of thin client to support for the Weather Service Offices, Center Weather Support Units, Incident Meteorologists, (e.g., Fire Weather, backup support for RFCs and National Centers) • Integration of Weather Event Simulator) • CHPS Integration into AWIPS SOA • Phase III: (FY2009 – FY2015) – Enterprise Level Enhancements • Data delivery enhancements: “Smart push-smart pull”data access • Integrated visual collaboration • Information generation enhancements • Visualization enhancements

  7. Migration Schedule

  8. AWIPS I to 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 • Objective is to make AWIPS II available for collaborative development

  9. AWIPS-II: Reference ArchitectureBased on Plug In Extensible services AWIPS-II Reference Architecture Enterprise Service Bus (ESB) - Camel <<Visualization Framework >> CAVE <<Service Framework >> EDEX Core Generic Services Meta Data Data Core Libraries

  10. AWIPS-II Dependencies: Open Source BasedUpdated Oct. 05, 2009

  11. AMC4 Americom Commercial Satellite SBP CSU/ DSU GINI CISCO 2514 DEMOD SBP CSU/ DSU CISCO 2514 Application Server Data Server CISCO 4500 Data Server Application Server Work Station SBIG CPID CPIC AS1A DS1A WK1B WFO or RFC CISCO 7000 DSIA AWIPS Network Control Facility AWIPS Communications Interfaces Source of AWIPS Satellite Imagery NOAAPort Receive System DEMOD SP1D NESDIS Non-Gov Data Users Comb HPA Mod AWIPS Master Ground Station Server Source of AWIPS Model Data Site AWIPS System AWIPS WIDE AREA NETWORK (NOAANET) SB1A NCEP NWSTG NEXRAD ASOS CRS RRS LDAD Other Gov, WMO, Academic, and Private Industry Interfaces

  12. AWIPS II Primary Standards & Formats • Ingested Data Formats • GRIB1/GRIB2 – Gridded data • NetCDF3 – Support AWIPSI/II interoperability • BUFR – Observational Data, e.g., soundings • METAR, SHEF – Surface and hydrological data • GINI – Satellite Imagery • OPRG L3 – Radar Imagery • Text Messages – Text products • Data Store Formats • PostGres – Metadata and select data type store, e.g., text • HDF5 – Binary store for grids, imagery and select observations • Product Distribution • NetCDF3 – NDFD Grids • ASCII Text – Text products

  13. AWIPS II Extended Data Delivery Overview • Objective – Develop robust data delivery system within AWIPS II infrastructure that enables efficient access to high volume datasets • Address significant growth in data volumes, e.g., ensembles, GOES-R, NPOESS and mitigate impacts on SBN • High-Level requirements in common with NextGen • Data registry and discovery services • “Smart” push/pull technology • Sub-setting by user selectable space, time, and parameter • Complex retrievals, e.g., derived parameters, coordinate transformations, etc • Ad hoc and subscription services • Operationally robust – supports availability, latency and security requirements for operational users • Multi-Phase Implementation • IOC Focus – NWS data providers, e.g., NOMADS, MADIS, possibly with basic services only, discovery, sub-setting – Target FY12

  14. AWIPS II Data Delivery – Significant Challenges

  15. QUESTIONS ????

More Related