1 / 19

Ronla Henry NWS/OST/PPD

National Weather Service. AWIPS II Overview and Status AMS IIPS January 14, 2008. Ronla Henry NWS/OST/PPD. Overview. Contract Overview Infrastructure Review Government Activities Testing Training Site Migration Governance Getting Ready. Contract Overview. SOA Migration Task Orders.

guillermo-manzanero
Download Presentation

Ronla Henry NWS/OST/PPD

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. National Weather Service AWIPS II Overview and Status AMS IIPSJanuary 14, 2008 Ronla Henry NWS/OST/PPD

  2. Overview • Contract Overview • Infrastructure Review • Government Activities • Testing • Training • Site Migration • Governance • Getting Ready

  3. Contract Overview

  4. SOA MigrationTask Orders

  5. SOA MigrationRoadmap 3 4 ATI OSIP Gates 2 Meshed Topology MPLS Analysis ADE Training Development PIP ADETraining Migration Planning RTSIRAD ADE Development AWIPS II 1.0 07/15/08 Migration Strategy 2010 2006 2007 2008 2009 OBx 8.3 9 7 8 8 10 Deployment OB 9 Dev & Test New Release Paradigm SW CTR (AWIPS II) NWS New Capability Development in ADE O & M Transition O & M Transition Prep & Coordination Baseline Application Migration OTE / Deployment Support Note: Task bar colors are For speaker reference only “User” Functional Tests ADE Local App Training Local App Migration C & A OTE = Calendar Year Deployment Deployment Planning = Fiscal Year Field Ops Training -- ITO, ESA

  6. Infrastructure

  7. SOA MigrationRe-Architecture Approach • Perform “black-box” conversion • Preserve existing functionality, look and feel on top of new infrastructure • No loss of functionality • Deployed system current with deployed AWIPS capability (i.e., OB9) • Thorough field validation and acceptance before deployment • Use open source projects - No proprietary code • JAVA and open source projects enable AWIPS II to be platform and OS independent • ADE enables collaborative development • OS, Platform independence allows non-Linux based research to be easily integrated into AWIPS II

  8. <<Java>> HDF5DataStore <<Java>> DataLayer <<abstract>> BaseDao SOA Architecture – Logical Layered ViewLayers Separated By Simple APIs Client/Presentation Services JMX CAVE External Programs Mission Services Layer Mbean ProductSrv IngestSrv NotifySrv Hydro Models AdapterSrv AutoBldSrv PersistSrv IndexSrv SubscribeSrv UtilitySrv LAPS Security Services /Demilitarized Zone (DMZ) Enterprise Service Bus - Communication PurgeSrv StagingSrv FORTRAN/C/C++ Command Line Programs Data Access Layer Hibernate HDF5 API Localization Store Platform Layer PostgreSQL HDF5 Data Persistence Store Metadata Index Spatial Index

  9. Government Activities

  10. SOA MigrationTesting Approach • Purpose: • Provide feedback to Raytheon on TO software deliverables • Improve software quality in support of OT&E and Deployment • Layered Approach • IV&V (Independent Verification & Validation) • Testing Objective: Push the system; Test to break • Testing based on TO contents • Includes “menu mapping” exercise • UFE (User Functional Evaluation) • Testing Objective: Provide operational look at TO deliverables • Testing based on TO contents • Heavily focused on implementation variances of end-user functionality • OT&E (Operational Testing & Evaluation) • Testing Objective: Verify AWIPS-II operationally ready for deployment • Controlled testing environment at operational sites • Follows evaluation of TO11 http://www.nws.noaa.gov/ost/SEC/AE/Testing.htm

  11. AWIPS IITesting Status • IV&V • Continue to evaluate TO deliveries • Focusing on operational performance metrics • UFE • Conducted Forecaster Initial Testing • Evaluated software along side AWIPS • Assisted in developing operational scenarios • Continue to evaluate TO deliveries • Working side-by-side plan for TO11 testing • OT&E • Working OT&E plan • Signature Coordination, May 2009 • Expected to begin around November 30

  12. SOA MigrationTraining Approach • Purpose: • Ensure that developers able to utilize migrated software • Ensure that end-users able to configure, monitor, and administer system • Approach: • Development Organizations (GSD, MDL, OHD, SEC) planning and executing training • NWSTD involved in planning and executing operational training • Focus Areas: • Local Application Developer • Application Focal Point • System Administration http://www.nws.noaa.gov/ost/SEC/AE/Training.htm

  13. SOA MigrationTraining Status • Operational Training • Requirements Identified • Mechanism • Training for Trainers via Technical Interchange Meetings • Initial focus on preparing OT&E sites • Development Training • Completed

  14. SOA MigrationSite Migration Approach • Purpose: • Provide structured method to ensure local sites’ migration • Includes: • Local Application Migration • Site Migration • Application Configuration • Product Format Template Configuration • Approach: • Team (regions, HQ) plan/coordinate • Regions/Offices execute http://www.nws.noaa.gov/ost/SEC/AE/Site_Migration.htm

  15. AWIPS-II Site MigrationStatus • Local Application • NCLADT • Analyzed capabilities supporting local application migration in TO8 & TO9 • Provided input to Raytheon on capabilities provide (and to be provided) • Provided test cases supporting future TO deliveries • Developing a plan supporting local application migration based on TO10 capabilities • Site Migration • Identifying configuration/customization files within existing system • Identifying any changes resulting from SOA Migration activities • Investigating obtaining Raytheon assistance in this effort

  16. AWIPS-II GovernanceApproach • What is it? • Governance model controls the development, test, integration, configuration management, deployment and support of the new system -- both hardware and software • Why? • SOA offers new levels of flexibility and extensibility • New rules needed to exploit system capabilities, define limits • Tension between unlimited modifications and ability to support the baseline system http://www.nws.noaa.gov/ost/SEC/AE/Governance.htm

  17. AWIPS-II GovernanceStatus • Governance Sub-Teams • Release team • Working to document release paradigm • Concept includes • Monthly DR release • Quarterly “major” release • Local Application team • Began by reviewing existing policy • Restart in February, 2009 • Identify changes to policy and AIFM

  18. Getting Ready

  19. What can you do? • Focus on SOA Migration • Be Prepared • TO10 • Local application migration, including SmartTools • TO11 “Slices” • User Functional Evaluation • Side-by-side Testing • OT&E • Stay Informed • Weekly Topic Reports • Website Updates • http://www.nws.noaa.gov/ost/SEC/AE • Upcoming NWS Focus Articles

More Related