AWIPS Evolution Update

S&T Committee

28 Feb 2006

Jason Tuell

April 19, 2023 2

Overview

• Review of AWIPS Evolution Objectives

• Raytheon task order

• IWT

• Constraints

• Summary

April 19, 2023 3

AWIPS EvolutionObjectives

• Update infrastructure to incorporate modern, service oriented, network centric architecture (OSIP #04-005).

– Establish network-centric Enterprise Architecture and Infrastructure for AWIPS– Establish greater integration between AWIPS and NAWIPS

• Expanded use of common libraries for decode, hydrological and meteorological algorithms, data access, and services

• Ability to exchange and edit graphical information between systems in real time

• Data delivery/Information architecture (OSIP #05-040)– Enable access to data independent of its location, i.e., provide access to data not

resident locally at the WFO or RFC.– Migrate AWIPS to a modern, robust and sustainable data architecture

• Visualization (OSIP #05-021)– Build a common AWIPS visualization environment (CAVE) that will be used by all

applications• Collaboration (OSIP #05-042)

– Provide infrastructure for real time graphical collaboration between WFOs, RFCs and centers for enhanced internal collaboration

– Provide infrastructure for real time collaboration with other NOAA entities– Provide infrastructure for collaboration with trusted partners, e.g., Emergency

Managers• Information Generation (OSIP #05-041)

– Establish infrastructure for Enterprise Service Back up– Standardize templates for all NWS text products– Establish infrastructure for GIS integration in generation and delivery of services

April 19, 2023 4

AWIPS EvolutionOutcomes

• Increased access to ever expanding amounts of environmental data needed for decision making

• Increased flexibility to seamlessly transfer operational functions and responsibilities between WFOs and National Centers to support new concepts of operation

• Reduction of software O&M costs and potentially reduced hardware technology refresh costs

• Increased integration of AWIPS and NAWIPS• Improved research to applications throughput

April 19, 2023 5

Approach to Migrating AWIPS to a New Operational Concept

AWIPS for

the 1990sAWIPS for

the year 2010

FY-08 PAC

AWIPS Evolution

Budget Initiatives

AWIPS Re-Compete

O&M Cost Savings

funding migration

to an SOA WFO Centric Architecture Little AWIPS/NAWIPS Integration High software Maintenance Costs Poor RTO efficiency Fire Hose Data Distribution

Supports New Ops Concept More flexible in Production/Delivery Increased AWIPS/NAWIPS Integration Improved RTO efficiency Increased access to data for decision making Reduced software O&M costs Flexible data delivery

A Services Oriented Architecture is necessary but not sufficient to

get us to a new Operational Concept and a more flexible AWIPS

April 19, 2023 6

Establishing a Service Oriented Architecture

• Raytheon Continuous Technology Refresh Task– Will define and implement target architecture– Will develop AWIPS Development

Environment and Software Development Kit for future software development

– Will migrate current baseline and future baseline modifications into new architecture

April 19, 2023 7

Raytheon Task Order #1

• Create Software Product Improvement Plan (PIP)– Task start - 1 March (approximate)– Duration 3 months

• Technical Interchange Meetings– DC - 7-9 March– GSD - 21-22 March– Kansas City 5-6 April

April 19, 2023 8

Raytheon Task Order #2

• Data modeling and data and workflow analysis– Task start - 12 May– Duration – ~ 3-4 months

• Analysis of data workflow leading to system and data architectures

April 19, 2023 9

AWIPS Evolution & OSIP

• CTR will be executed under the AWIPS Evolution SON– Raytheon to follow OSIP

• Integrated Work Team being formed

• Enhancements from the subordinate SONS to be implemented after the new architecture is delivered

April 19, 2023 10

AWIPS EvolutionIWT

• IWT members solicited– Regions– NCEP– GSD– HQ Offices

• OST, CIO, OCWWS, OOS

• Near Term IWT tasks– AWIPS ConOps– Operational Requirements

April 19, 2023 11

AWIPS Evolution IWTConOps & Operational Requirements

• Build upon existing documentation and current capabilities– Original requirements and specifications– National Academy Study leading to the Build 5.2.2 end of

development milestone– Changes due to introduction of digital services

• Plan to align AWIPS ConOps work along service areas– Create smaller teams to focus on each area– Integrate like elements

• Integrate and anticipate Tiger Team output– Aviation and NWS ConOps teams

• Derive Infrastructure Operational Requirements from AWIPS ConOps

April 19, 2023 12

FY08 Budget Status

• Increases in PAC and O&M budgets above the line, not funded– Additional funding for LFW driven software

development not funded

• O&M budget affected by ~$4.3M reduction– O&M budget problems projected for FY08 due

to increasing Government FTE labor costs

April 19, 2023 13

Recent Activities

• Management Plan drafted– Defines how we work with Raytheon– Defines roles and responsibilities within the Government– Integrates Raytheon proposal with OSIP

• Preparations for IWT• Alternative planning

– Alternatives defined to provide interim collaboration, visualization and data delivery prototoypes

– May be useful for supporting CONOPS, Aviation demonstrations

• Preparations for upcoming PPBES cycle• Working linkages to other NOAA programs and activities

April 19, 2023 14

Constraints

• CONOPS and Aviation Tiger Teams– Schedule for AWIPS Evolution and some team activities not well

aligned– Good news is that most system level needs identified already

incorporated in existing AWIPS Evolution SONs

• NOAA Data Management Standards - GEO IDE– AWIPS will have to comply with emerging NOAA wide data

standards– AWIPS largely in compliance now; move to SOA aligned with

NOAA activities

• Success in 09 PPBES may require focus on NOAA and goal objectives as benefit or outcome of AWIPS evolution

April 19, 2023 15

Summary

• Raytheon CTR task about to start– Implement SOA, migrate baseline then

enhance functionality

• AWIPS Evolution IWT being formed– ConOps and Operational Requirements

critical part of OSIP and input to Raytheon activities

• The fun, and hard work, is about to start!