1 / 21

Evolution of AWIPS

Evolution of AWIPS. Jason Tuell Office of Science and Technology. Overview. Background Corporate Board direction Implementing actions Preparations for FY08 FY08 planning and actions Alternatives for the near term Summary. Background. Briefing to Corporate Board Nov 2004

awynter
Download Presentation

Evolution of AWIPS

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. Evolution of AWIPS Jason Tuell Office of Science and Technology

  2. Overview • Background • Corporate Board direction • Implementing actions • Preparations for FY08 • FY08 planning and actions • Alternatives for the near term • Summary

  3. 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

  4. Hardware Funding for 3 year hardware refresh cycle critical Large backlog in changes to site hw drawings Communications 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 unreliable Data Takes too long to get new data added to SBN implement a new WAN data distribution method to supplement SBN Present State: Summary Challenges

  5. 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 resources Communications 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. Present State: Summary Conclusions

  6. 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

  7. 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

  8. 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.)

  9. 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

  10. 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

  11. Support AWIPS Operational Builds 4 & 5 • Development for AWIPS Operational Build 6 • FXNet staging OB3 look alike • Visualization Prototype development (ALPS) Year Current Program 100% Program • 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 FY05 No entry required FY06 No entry required FY07 No entry required • 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 FY08 IOC Information Architecture (phase I) IOC Enterprise Service Backup Visualization Prototype WRIP Contract Award WRIP System Development Begins LFW driven software development • FXNet staging OB7 look alike • Support AWIPS Operational Builds 8 & 9 • Development for AWIPS Operational Build 9 & 10 FY09 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 • 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 FY10 FOC Information Architecture (phase II) FOC Enterprise Service Backup Collaboration Prototype IOC Information Generation LFW driven software development • 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 FY11 IOC Collaboration FOC Information Generation WRIP Deployment Complete LFW driven software development FY12 FOC Collaboration LFW driven software development Capability Outputs Note – See backup slides #22 – 31 for ONE Outputs

  12. 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

  13. 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

  14. 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

  15. Data DeliveryInitial capability • Provide real time remote access with auto update for non-local numerical model data

  16. 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

  17. 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

  18. 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

  19. 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

  20. 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

  21. 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

More Related