Evolution of AWIPS Jason Tuell

21
Evolution of AWIPS Jason Tuell Office of Science and Technology

Transcript of Evolution of AWIPS Jason Tuell

Page 1: Evolution of AWIPS Jason Tuell

Evolution of AWIPS

Jason Tuell

Office of Science and Technology

Page 2: Evolution of AWIPS Jason Tuell

Overview

• Background– Corporate Board direction– Implementing actions– Preparations for FY08

• FY08 planning and actions• Alternatives for the near term• Summary

Page 3: Evolution of AWIPS Jason Tuell

Background

• Briefing to Corporate Board Nov 2004– Defined present state summary and challenges– Proposed formation of dedicated body to define

what needs to be done next

• Corporate board direction to form Programming Branch

Page 4: Evolution of AWIPS Jason Tuell

Present State: Summary Challenges

Hardware• Funding for 3 year hardware refresh

cycle critical• Large backlog in changes to site hw

drawingsCommunications Infrastructure• Bandwidth for IFPS intersite

coordination on WAN• Bandwidth for new radar data on

WAN• Funding for transition to new

NWSNET WAN• TG must get by for at least 2 years

with current architecture

Software• Too many development organizations and

environments for our current management structure

• Too Many Major Software Changes• Major software installs take too long• Too many uncoordinated development

efforts going on concurrently• Too many inconsistencies between user

interfaces• Inadequate Documentation of Code Base• Software Architecture is unreliableData• Takes too long to get new data added to

SBN• implement a new WAN data distribution

method to supplement SBN

Page 5: Evolution of AWIPS Jason Tuell

Present State: Summary Conclusions

Hardware• AWIPS hardware is in good shape

– No critical deficiencies– Product improvement plan is in

place, funded and on schedule– Challenges are manageable with

existing resourcesCommunications Infrastructure• AWIPS communications

infrastructure is in OK shape– No critical deficiencies– Product improvement plan is in

place, partially funded and on schedule

– Challenges are manageable with moderate infusion of resources

Software• AWIPS software is in critical need of

improvements– Some critical deficiencies– No product improvement plan is in

place and no plans or funding to create one

– Software development is un-sustainable at current pace

– Challenges are un-manageable without significant infusion of resources

Data• AWIPS Data is in need of improvements

– Some deficiencies.• Numerous outstanding field

requirements not being met – Product improvement plan is in place

and partially funded but needs more funding for bandwidth increases

– Challenges are manageable with moderate infusion of resources.

Page 6: Evolution of AWIPS Jason Tuell

Corporate Board ActionNovember 2004

• Form dedicated office to address AWIPS IT services– 5-8 people

• Formulate an integrated product improvement plan– Build roadmap– Manage enterprise so system shortfalls don’t

worsen– Identify staffing and deliverables

Page 7: Evolution of AWIPS Jason Tuell

Programming Branch

• Jason Tuell, SEC• Darien Davis, FSL• Ronla Meiggs, SEC• Joe Gofus, OHD• Mark McInerney, MDL• Part time

– Cindy Woods, PPD– Chung Wu, SEC– Franz Zichy, SEC– V. Lakshmanan, NSSL

Page 8: Evolution of AWIPS Jason Tuell

FY08 Preparation

• SONs defined for AWIPS evolution– Information Architecture/data delivery

• Need for improved data base structures and data access, independent of local site data

– Visualization• Improved, standard visualization architecture

– Collaboration• Internal and external collaboration

– Information generation• Consolidation and expansion of technologies (GIS, XML, etc.)

Page 9: Evolution of AWIPS Jason Tuell

AWIPS Vision

• Services Oriented Architecture• Decoupling of data and applications• Decoupling of data access and local data

storage• Separation of applications from the

infrastructure

A secure, reliable, more flexible and sustainable system tailored to the needs of the field

Page 10: Evolution of AWIPS Jason Tuell

FY08 PPBES

• Submitted budget for FY08-13– Included increases to address re-architecture

and new software development for LFW– Tech refresh profile largely unchanged

• Looking for opportunities in FY06-07– Defining SOWs for tasks in FY06

Page 11: Evolution of AWIPS Jason Tuell

Capability Outputs

FOC Information Architecture (phase II) FOC Enterprise Service Backup

Collaboration Prototype IOC Information Generation

LFW driven software developmentFY10

IOC Collaboration FOC Information Generation

WRIP Deployment Complete LFW driven software developmentFY11

100% ProgramCurrent ProgramYear

No entry requiredFY05

No entry requiredFY06

FOC Collaboration LFW driven software developmentFY12

FOC Information Architecture (phase I) IOC Visualization

IOC Information Architecture (phase II) Information Generation Prototype

WRIP System Development Complete WRIP Deployment Begins

LFW driven software development

FY09

IOC Information Architecture (phase I) IOC Enterprise Service Backup

Visualization Prototype WRIP Contract Award

WRIP System Development Begins LFW driven software development

FY08

No entry requiredFY07

•Support AWIPS Operational Builds 4 & 5•Development for AWIPS Operational Build 6•FXNet staging OB3 look alike•Visualization Prototype development (ALPS)

•FXNet staging OB4 look alike•Support AWIPS Operational Builds 6 & 7•Development for AWIPS Operational Build 7 & 8•Distributed data development•Tech transfer of visualization

•FXNet staging OB6 look alike•Support AWIPS Operational Builds 7 & 8•Development for AWIPS Operational Build 8 & 9•Tech transfer of visualization•Distributed data prototype

• FXNet staging OB7 look alike• Support AWIPS Operational Builds 8 & 9• Development for AWIPS Operational Build 9 & 10

• FXNet staging OB8 look alike• Support AWIPS Operational Builds 9 & 10• Development for AWIPS Operational Build 10 & 11

• FXNet staging OB9 look alike• Support AWIPS Operational Builds 10 & 11• Development for AWIPS Operational Build 11 & 12

• FXNet staging OB10 look alike• Support AWIPS Operational Builds 11 & 12• Development for AWIPS Operational Build 12 & 13

• FXNet staging OB11 look alike• Support AWIPS Operational Builds 12 & 13• Development for AWIPS Operational Build 13 & 14

Note – See backup slides #22 – 31 for ONE Outputs

Page 12: Evolution of AWIPS Jason Tuell

Challenges in near term

• Funding increase isn’t realized until FY08• Foundation work needs to be done in next

two years to prototype different concepts• Evolving concepts of operation

– Nested services and demonstration in FY08

Page 13: Evolution of AWIPS Jason Tuell

Alternative planningFocus on FY06, 07

• Focus of determining what is needed to support new concepts of operation– Great Lakes demonstration in FY08 (at least according

to white paper and LFW PBA)

• Capabilities needed - our evaluation– Enhanced collaboration– Improved data delivery

• Other supporting capabilities– Grid algorithm toolkit

Page 14: Evolution of AWIPS Jason Tuell

Enhanced CollaborationInitial Minimum Capability

• Real time exchange and visualization of common graphical objects (e.g., fronts, meteorological symbols, etc.) between applications, offices and national centers– Paradigm shift on collaboration and

coordination

Page 15: Evolution of AWIPS Jason Tuell

Data DeliveryInitial capability

• Provide real time remote access with auto update for non-local numerical model data

Page 16: Evolution of AWIPS Jason Tuell

FY06 Objectives and Tasks

• Objective– Demonstrate static exchange and display of a set of

common graphical objects between different systems (both AWIPS and NAWIPS)

• Tasks– Define common graphical objects (XML)– Enable display on AWIPS via prototype IGC rewrite

via plug in– Define messaging agent for notification– Grid algorithm toolkit development

Page 17: Evolution of AWIPS Jason Tuell

FY07Objectives and Task

• Objective– Enable enhanced collaboration via the real-time

exchange and display of objects between systems and applications

– Enable real time remote access to numerical model data

• Tasks– Expand XML definitions of common graphical objects– Enable real time notification and update on posted

information, e.g., graphical objects or model data– Grid algorithm toolkit development

Page 18: Evolution of AWIPS Jason Tuell

FY06 and FY07 ActivitiesMapping onto SONs

• Information architecture– Real time event notifications– Remote real time access to numerical model data

• Visualization– Prototype of updated IGC and plug in concept– Addition of drawing capability for D2D, GFE (medium risk)– Display of graphical objects on D2D, GFE and NAWIPS

• Collaboration– Exchange of graphical information between systems and

applications

Page 19: Evolution of AWIPS Jason Tuell

Near term milestones

• FY06 SOWS due end of July• Five year roadmap for AWIPS due to

Corporate Board end of August• AWIPS recompete award – this summer

Page 20: Evolution of AWIPS Jason Tuell

Re-architecture and the Re-compete

• Programming branch working on the first parts of detailed planning

• Re-compete vendor to become integral part of the planning team

• Execution will be joint Government and contractor activity

Page 21: Evolution of AWIPS Jason Tuell

Summary

• Programming Branch formed to delivery detailed five year roadmap to Corporate Board– Address critical AWIPS deficiencies

• FY08 PPBES inputs delivered• Detailed alternative planning for near term

(FY06/07) underway