Evolution of AWIPS Jason Tuell Office of Science and Technology.

Slides:



Advertisements
Similar presentations
State of Indiana Business One Stop (BOS) Program Roadmap Updated June 6, 2013 RFI ATTACHMENT D.
Advertisements

Ninth Lecture Hour 8:30 – 9:20 pm, Thursday, September 13
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
Alternate Software Development Methodologies
Ronla Henry NWS/OST/PPD
1 National Weather Service Jason Tuell Office of Science and Technology The Evolution of AWIPS NWS Partner’s Meeting 20 June 2007.
Lecture 13 Revision IMS Systems Analysis and Design.
Chief – Science Plans Branch NOAA/NWS/Office of Science and Technology
1 Case Study: Starting the Student Registration System Chapter 3.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
COMP8130 and 4130Adrian Marshall 8130 and 4130 Test Management Adrian Marshall.
Defining the Activities. Documents  Goal Statement defines why helps manage expectations  Statement of Work what gets delivered defines scope  Software.
Plans for AWIPS Next Generation 1April 12, 2005 AWIPS Technology Infusion Darien Davis NOAA/OAR Forecast Systems Laboratory Systems Development Division.
Presented to: Aerospace Control and Guidance Systems Committee By: Stan Pszczolkowski, Manager, System Analysis Division Date: March 1, 2006 Federal Aviation.
SAS 03/ GSFC/SATC-ERAU-DoC Fault Tree Analysis Application for Safety and Reliability Massood Towhidnejad Embry-Riddle University Dolores Wallace & Al.
Typical Software Documents with an emphasis on writing proposals.
Server Virtualization: Navy Network Operations Centers
2Object-Oriented Analysis and Design with the Unified Process Objectives  Explain the purpose and various phases of the traditional systems development.
THE REGIONAL MUNICIPALITY OF YORK Information Technology Strategy & 5 Year Plan.
T Project Review RoadRunners [PP] Iteration
FirstEnergy / Jersey Central Power & Light Integrated Distributed Energy Resources (IDER) Joseph Waligorski FirstEnergy Grid-InterOp 2009 Denver, CO November.
Software Development Stephenson College. Classic Life Cycle.
Consult21 Information is subject to change and is for discussion purposes only. Any dates/timings are the current anticipated timescales and may be subject.
NWS Digital Services 1 Digital Services Update and Forecast Collaboration March 16, 2004 Shannon White Training Division.
NIST Special Publication Revision 1
1 THE NATIONAL SPACE WEATHER PROGRAM Sixth Symposium on Space Weather Session 1: Space Weather Agency Updates AMS Annual Meeting January 12, 2009 Mr. Samuel.
The Challenge of IT-Business Alignment
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Enterprise Storage A New Approach to Information Access Darren Thomas Vice President Compaq Computer Corporation.
1 This workshop is part of our commitment to periodically provide you with updated information about BPA’s contracting and project management processes.
Review of NWS IT Consolidation Efforts For HIC Meeting July 2006 Tom Schwein Team Leader of Desktop Management Tiger Team SOD CRH.
AWIPS-II Data Delivery Project Overview December 2013.
1 National Weather Service The Evolution of AWIPS NSTEP April 4, 2007 Ronla Henry.
1 National Weather Service Ronla Henry Office of Science and Technology AWIPS Technology Infusion NWS Partner’s Meeting 17 June 2008.
Reginald Lawrence, NOAA/NESDIS/OSD NOAA Direct Readout Conference
NOAA Satellite Proving Ground/User Readiness Meeting
OOI CI LCA REVIEW August 2010 Ocean Observatories Initiative OOI Cyberinfrastructure Architecture Overview Michael Meisinger Life Cycle Architecture Review.
Next Generation Warning Tool (NGWT) Jason Tuell Systems Engineering Center Office of Science and Technology.
National Weather Service Scott Jacobs David Plummer and Stephen Gilbert NOAA/NWS/National Centers for Environmental Prediction Jason Tuell, Steve Schotz.
Notes of Rational Related cyt. 2 Outline 3 Capturing business requirements using use cases Practical principles  Find the right boundaries for your.
1 Planning for Reuse (based on some ideas currently being discussed in LHCb ) m Obstacles to reuse m Process for reuse m Project organisation for reuse.
Fifth Lecture Hour 9:30 – 10:20 am, September 9, 2001 Framework for a Software Management Process – Life Cycle Phases (Part II, Chapter 5 of Royce’ book)
CHPS-AWIPS II Integration Jon Roe, Chris Dietz, Joe Gofus OHD/HL/HSEB Semi-Annual RFC HIC Meeting 29 July 2008.
AWIPS II Update Unidata Policy Committee Meeting J.C. Duh Chief, Program & Plans Division, Office of Science & Technology, NWS April 15, 2010.
Briefing Tool Update Herb Grote ESRL/GSD/ISB Boulder, CO June 13, 2006.
JRA Execution Plan 13 January JRA1 Execution Plan Frédéric Hemmer EGEE Middleware Manager EGEE is proposed as a project funded by the European.
1 Course of Action For Strengthening Transportation Communications and Coordination In the National Capital Region Presented by John M. Contestabile Maryland.
- Transition Update Briefing - Paul F. Moersdorf NOAA Climate Observation Program 3 rd Annual System Review April 27, 2005 TAO Tropical Atmosphere Ocean.
User Working Group 2013 Data Access Mechanisms – Status 12 March 2013
Last Updated 1/17/02 1 Business Drivers Guiding Portal Evolution Portals Integrate web-based systems to increase productivity and reduce.
US ATLAS Tier 1 Facility Rich Baker Brookhaven National Laboratory Review of U.S. LHC Software and Computing Projects Fermi National Laboratory November.
GRID Overview Internet2 Member Meeting Spring 2003 Sandra Redman Information Technology and Systems Center and Information Technology Research Center National.
Ruth Pordes November 2004TeraGrid GIG Site Review1 TeraGrid and Open Science Grid Ruth Pordes, Fermilab representing the Open Science.
PoDAG XXI: SEEDS SEED: NSIDC Potential Interactions NSIDC DAAC should prepare an evaluation of their desired future roles in "core activities" and in mission.
The principles of an object oriented software development process Week 04 1.
Prototyping life cycle Important steps 1. Does prototyping suit the system 2. Abbreviated representation of requirements 3. Abbreviated design specification.
Development through partnership Infrastructure Delivery Management Toolkit: 2010 Edition Delivery Process 2: Project Management 1.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Software Production ( ) Lecture 3: Dr. Samer Odeh Hanna (PhD) office: 318.
1 Options Clearing Corporation Encore Data Distribution Services April 22, 2004.
March 2004 At A Glance The AutoFDS provides a web- based interface to acquire, generate, and distribute products, using the GMSEC Reference Architecture.
PDS4 Project Report PDS MC F2F University of Maryland Dan Crichton March 27,
1 USDOT Next Generation Initiative Laurie Flaherty EMS Division, NHTSA.
IV&V Facility 7/28/20041 IV&V in NASA Pre-Solicitation Conference/ Industry Day NASA IV&V FACILITY July 28, 2004.
Managing the Project Lifecycle
JRA3 Introduction Åke Edlund EGEE Security Head
EOSDIS Data Preservation Archive (EDPA)
TPF-5(181) Research Management Database Business Analysis
Object Oriented Analysis and Design
Ebusiness Infrastructure Platform
Presentation transcript:

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

Present State: Summary Challenges 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 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 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.

Corporate Board Action November 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

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

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

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

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

Capability Outputs FOC Information Architecture (phase II) FOC Enterprise Service Backup Collaboration Prototype IOC Information Generation LFW driven software development FY10 IOC CollaborationFOC Information Generation WRIP Deployment CompleteLFW driven software development FY11 100% ProgramCurrent ProgramYear No entry requiredFY05 No entry required FY06 FOC CollaborationLFW driven software development FY12 FOC Information Architecture (phase I) IOC Visualization IOC Information Architecture (phase II) Information Generation Prototype WRIP System Development CompleteWRIP Deployment Begins LFW driven software development FY09 IOC Information Architecture (phase I)IOC Enterprise Service Backup Visualization PrototypeWRIP Contract Award WRIP System Development BeginsLFW 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 OutputsSee backup slides #22 – 31 for ONE Outputs

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

Alternative planning Focus 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

Enhanced Collaboration Initial 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

Data Delivery Initial capability Provide real time remote access with auto update for non-local numerical model data

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

FY07 Objectives 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

FY06 and FY07 Activities Mapping 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

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

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

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