1 / 15

AWIPS

AWIPS. AWIPS II Overview and Status for HIC Conference. Tim Hopkins February 25, 2010. AWIPS II Near Term Milestones and Activities. Software Delivery DR5, 2/15/10 DR6 coming March 1 st Additional forecaster testing March 5  9 th

melosa
Download Presentation

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. AWIPS AWIPS II Overview and Statusfor HIC Conference Tim Hopkins February 25, 2010

  2. AWIPS II Near Term Milestones and Activities • Software Delivery DR5, 2/15/10 • DR6 coming March 1st • Additional forecaster testing March 5  9th • Focus on stability, localization and customization and local apps infrastructure Field Volunteer testers (Lead is Bill Gery) • Eric Thaler WFO BOU • Ken Pomeroy WRH SSD • Kristian Mattarochia WFO RNK • Paul Stanko WFO GUM • Preliminary Readiness Review, March 10th • Final TO11 software delivery, March 15th • System OT&E Readiness Review, March 16th

  3. Hardware Refresh Schedule * AWIPS II OT&E Pre-requisite Legend Green=1, Yellow=2, Red=3 General Status = simple average of all ratings, rounded to nearest integer (.5 rounded up), N/A’s not counted

  4. 5 4 3 2 1 2 3 4 5 1 Approach Approach Criticality L x C Trend M M – – Mitigate Mitigate Critical Decreasing (Improving) Decreasing (Improving) W W – – Watch Watch Med Increasing (Worsening) Increasing (Worsening) A A – – Accept Accept Unchanged Unchanged R R - - Research Research Low AWIPS-II Risk Matrix 7 1 80 - 100% Very High 2 L L 4 I I 60 - 80% High K K E E L L 40 - 60% Moderate 3 I I 6 H H O O 20 -40% Low O O D D 0 -20% Very Low Consequences

  5. Final Target:22 Final Target Date:3/15/2010 Work Weeks Left to Final: 3 Work Weeks Left to Next Target: 3 Project Critical Path: Yes Gov. Proj. Lead: SEC-Ed Mandel/Ashley Kells RTS Proj. Lead: N/A AWIPS-II Local Applications Migration Progress Critical Local Apps for System OT&E • Last Target: N/A • Current Actual: 7 Complete • Next Target: 22 SOTE Complete • Next Target Date:3/15/10 (Weekly) • Projected Completion Date: TBD • Resource Needs: TBD • Assuming that if the regions have accepted the app then they have the resources but this is still somewhat uncertain. • Associated Actions/Notes: • Regions demoted some from critical, so we are down to 22 now. • SEC is experimenting with assisting on some 5

  6. Critical Local Apps MigrationProgress

  7. Final Target:Zero (contract exit criteria, Hard) Final Target Date:3/15/10 (contract milestone, Hard) Work Weeks Left: 3 FBSO Submission Weeks Left: 0 FBSO Submission Rate(10/1->1/22): 55/wk. Projected Remaining Submissions: 0 Projected Total FBSO’s Remaining: 631 Projected Fix Rate Needed: 210/wk. Actual Fix Rate(2/5 -> 2/12) : 86.5/wk. (last:50) Project Critical Path: Yes!! Gov. Proj. Lead: SEC-Ed Mandel/Pete Pickard RTS Proj. Lead: Andre Tarro/Doug Lawson/Frank Griffith AWIPS-II Software Discrepancies ProgressOPENFix Before System OT&E DR’s (FBSO) • Projected Completion Date: 3/15/10 • Resource Needs: FFP contract task • Associated Actions/Notes: • 2/5/10 is last day to submit new FBSO’s • Estimated completion date at actual fix rate, assuming no more FBSO’s after 2/3/10: 4/12/2010 (last: 5/12/2010) • 631/86.5 = 7.3 (work weeks) 7

  8. Final Target:All Delivered FBSO’s Tested (Govt. Responsibility, Firm) Final Target Date:3/15/10 (contract milestone, Hard) FBSO Test Work Weeks Left: 3 FBSO Submission Weeks Left: 0 Projected FBSO Test Rate Needed: 56.4/wk. Actual FBSO Test Rate (2/5 -> 2/12) : 24.5/wk. Project Critical Path: Yes Gov. Proj. Lead: SEC-Ed Mandel/Tom Piper RTS Proj. Lead: N/A (Govt. Activity) AWIPS-II Software Testing ProgressFBSO DR Testing • Last Target: 29 (tested 27) • Next Target: 109 (Computed, Firm) • 1/29 DR4 delivery had 233 new FBSO fixes in it • Projected Completion Date: 3/15/10 • Resource Needs: A watch item • Associated Actions/Notes: • Activity is ramping up quickly 8

  9. If a test fails, the DR gets re-cycled back to Raytheon for resolution and then must be re-delivered and re-tested. This adds workload on both sides and reduces effective fix rate, adding to the likelihood of the #1 risk. AWIPS-II Software Testing ProgressFBSO DR Testing Closure Rate 9

  10. Final Target: All 12 Major Pieces of Hardware 100% Finalized and Tested by Govt. (implied TO11 exit criteria, Firm) = 12 x 100 Final Target Date:3/15/2010 Work Weeks Left(wwl): 2 Project Critical Path: Yes Gov. Proj. Lead: SEC-Ed Mandel/Jim Williams RTS Proj. Lead: Andre Tarro Mitigation: Best effort mitigation is indicated on the below chart by red and green being of matched percent complete, for any component that is >0% complete. Indication is that 11/11 components are in synch. Excellent!. 1/12 still not defined at all. Very Good. AWIPS-II Deployment Transition Planning (DTP) ProgressHardware+Software Architecture Component Progress* • Projected Completion Date: 3/15/2010 • Begin stability testing • Resource Needs: None • Associated Actions/Notes: • This is an issue that hinders govt. testing and deployment planning efforts across the board. Govt. has not required it from RTS sooner. RTS says it will be done in January (sometime). See associated risk mitigation. Architecture Overview DX1 – PostGres/Radar svr DX2 – Bup PostGres PX1 – LDM/Rehost apps PX2 – LDM/LDAD procs DX3 – Edex Primary DX4 – Edex Client LX - Cave XT – Text Workstation NAS – HDF5 CP1 – LDM Server CP2 – LDM Bup PV - TBD 10

  11. Product Improvement DashboardAWIPS Extended Activities Legend Green=1, Yellow=2, Red=3 General Status = simple average of all ratings, rounded to nearest integer (.5 rounded up), N/A’s not counted

  12. 5 4 3 2 1 2 3 4 5 1 Approach Approach Criticality L x C Trend M M – – Mitigate Mitigate Critical Decreasing (Improving) Decreasing (Improving) W W – – Watch Watch Med Increasing (Worsening) Increasing (Worsening) A A – – Accept Accept Unchanged Unchanged R R - - Research Research Low AWIPS-II Extended Risk Matrix 1 2 80 - 100% Very High L L I I 3 60 - 80% High K K E E 4 L L 40 - 60% Moderate I I H H 5 O O 20 -40% Low 6 O O D D 0 -20% Very Low Consequences

  13. AWIPS II Extended Milestones

  14. New OS/Hardware BaselineNotional Strategy • Notional! i.e. no OSIP project yet • One hardware suite to serve needs of RFC’s and NC’s • One hardware suite for WFO’s • Use Red Hat Server products virtualization capabilities to support two different configurations of RFC/NC hardware suite. • WFO’s would stay with current hardware refresh plan and workstation version of Red Hat and associated configuration • Result would be • Retain two hardware baselines (WFO & RFC/NC) • Increase OS baseline to two (RHEL Workstation and Server) • Increase OS/hardware configuration baseline to three • RFC configuration • NC configuration • WFO configuration • OSIP Project 07-059 (RFC AWIPS Configuration) should provide input to the above strategy. • Gate 2 is scheduled for April but documentation has not been updated for some time i.e. uncertain of current and recent past level of activity.

  15. NAWIPS Migration Integrated Schedule Mon 3/15/10

More Related