Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • The rendering shown here does not provide insight in how this state will be realized or cite its advantages. It is similar to an architectural rendering of a building. To get a true picture of how the house will be built, we need the blueprints for construction. User functions generally access from the top down. The hardware is at the lowest layer, then basic services, then mission services, then user interface Note that the term “services” is used for three of the layers. The next few slides discuss SOA basics.
  • PPT

    1. 1. Ronla Henry NWS/OST/PPD AWIPS Tech Infusion Overview and Status May 11, 2009 National Weather Service
    2. 2. Overview <ul><li>AWIPS Technology Infusion Scope </li></ul><ul><li>Infrastructure Review </li></ul><ul><li>Government Activities </li></ul><ul><ul><li>Testing </li></ul></ul><ul><ul><li>Training </li></ul></ul><ul><ul><li>Site Migration </li></ul></ul><ul><ul><li>Governance </li></ul></ul><ul><li>Getting Ready </li></ul>
    3. 3. AWIPS Technology Infusion Scope
    4. 4. AWIPS Technology Infusion Scope <ul><li>AWIPS Technology Infusion (FY2005 – FY2014) </li></ul><ul><ul><li>A long-term project which delivers a modern, robust software infrastructure that provides the foundation for future system level enhancements for the entire NWS enterprise </li></ul></ul><ul><li>Phase 1: (FY2007-FY2010) </li></ul><ul><ul><li>Migration of WFO/RFC AWIPS 1 to a modern Service Oriented Architecture (SOA) infrastructure </li></ul></ul><ul><li>Phase II: (FY2009-FY2011) – AWIPS SOA Extension </li></ul><ul><ul><li>Creation of a seamless weather enterprise spanning NWS operations </li></ul></ul><ul><ul><ul><li>Migration of NAWIPS into the AWIPS SOA </li></ul></ul></ul><ul><ul><ul><li>Delivery of thin client to support Incident Meteorologists, e.g., Fire Weather, </li></ul></ul></ul><ul><ul><ul><li>Integration of “orphan” systems (e.g., Weather Event Simulator to support training requirements) </li></ul></ul></ul><ul><ul><ul><li>Integration of Community Hydrologic Prediction System (CHPS ) into AWIPS SOA </li></ul></ul></ul><ul><li>Phase III: (FY2009 – FY2014) – Enterprise Level Enhancements </li></ul><ul><ul><ul><li>Data delivery enhancements: “Smart push-smart pull” data access </li></ul></ul></ul><ul><ul><ul><li>Visual collaboration enhancements </li></ul></ul></ul><ul><ul><ul><li>Information generation enhancements </li></ul></ul></ul><ul><ul><ul><li>Visualization enhancements </li></ul></ul></ul>
    5. 5. AWIPS Technology Infusion Roadmap Phase II AWIPS SOA Extension = Fiscal Year = Calendar Year OTE / Deployment Phase I AWIPS 1 Migration NAWIPS Migration Thin Client Phase III Enterprise Enhancements Data Delivery- Smart Push/Pull CHPS IOC FOC NWS Integrated Collaboration Phase 2 Phase 3 Streamlined Generation of Products IOC FOC 2007 2008 2009 2010 2011 2012 2013 2014 Baseline (AWIPS I) Application Migration WES Integration Advanced Visualization IOC
    6. 6. Service Oriented Architecture (SOA) Migration Task Orders Task Order (TO) Delivery Date Migrate primarily GFE capabilities (TO9) September 2008 Investigate technical issues/questions surrounding migration (TO-DTP) February 2009 Migrate of primarily Hydrologic capabilities (TO10) February 2009 Task Order Development and Transition Planning (DTP) March 2009 SOA Migration Complete (TO11) November 2009 Provide of technical materials supporting training preparation following TOs 8-11 (TO-T1) 3 weeks following TO delivery date
    7. 7. Infrastructure
    8. 8. SOA Migration Re-Architecture Approach <ul><li>Perform “black-box” conversion </li></ul><ul><ul><li>Preserve existing functionality, look and feel on top of new infrastructure </li></ul></ul><ul><li>No loss of functionality </li></ul><ul><ul><li>Deployed system current with deployed AWIPS capability (i.e., Operational Build 9 (OB9)) </li></ul></ul><ul><li>Thorough field validation and acceptance before deployment </li></ul><ul><li>Use open source projects - No proprietary code </li></ul><ul><ul><li>JAVA and open source projects enable AWIPS II to be platform and OS independent </li></ul></ul><ul><li>AWIPS Development Environment (ADE) enables collaborative development </li></ul><ul><ul><li>Operating System (OS), Platform independence allows non-Linux based research to be easily integrated into AWIPS II </li></ul></ul>
    9. 9. SOA Architecture – Logical Layered View Layers Separated By Simple App Programming Interfaces (APIs) Client/Presentation Services Platform Layer Mission Services Layer Data Access Layer Metadata Index Data Persistence Store Enterprise Service Bus - Communication Security Services / Demilitarized Zone (DMZ) Spatial Index Hydro Models LAPS FORTRAN/C/C++ Command Line Programs External Programs JMX PostgreSQL HDF5 Hibernate HDF5 API IngestSrv PersistSrv IndexSrv ProductSrv AdapterSrv NotifySrv SubscribeSrv AutoBldSrv PurgeSrv Mbean CAVE StagingSrv UtilitySrv Localization Store <<Java>> DataLayer <<abstract>> BaseDao <<Java>> HDF5DataStore
    10. 10. Government Activities
    11. 11. SOA Migration Testing Approach <ul><li>Purpose: </li></ul><ul><ul><li>Provide feedback to Raytheon on Task Order (TO) software </li></ul></ul><ul><ul><li>deliverables </li></ul></ul><ul><ul><li>Improve software quality in support of Operational Testing & </li></ul></ul><ul><ul><li>Evaluation (OT&E) and Deployment </li></ul></ul><ul><li>Layered Approach </li></ul><ul><ul><li>IV&V (Independent Verification & Validation) </li></ul></ul><ul><ul><ul><li>Testing Objective: Push the system (Stress testing); Test to break </li></ul></ul></ul><ul><ul><ul><li>Testing based on TO contents </li></ul></ul></ul><ul><ul><ul><li>Includes “menu mapping” exercise </li></ul></ul></ul><ul><ul><li>UFE (User Functional Evaluation) </li></ul></ul><ul><ul><ul><li>Testing Objective: Provide operational look at TO deliverables </li></ul></ul></ul><ul><ul><ul><li>Testing based on TO contents </li></ul></ul></ul><ul><ul><ul><li>Heavily focused on implementation variances of end-user functionality </li></ul></ul></ul><ul><ul><li>OT&E (Operational Testing & Evaluation) </li></ul></ul><ul><ul><ul><li>Testing Objective: Verify AWIPS-II operationally ready for deployment </li></ul></ul></ul><ul><ul><ul><li>Controlled testing environment at operational sites </li></ul></ul></ul><ul><ul><ul><li>Follows evaluation of TO11 </li></ul></ul></ul>http://www.nws.noaa.gov/ost/SEC/AE/Testing.htm
    12. 12. SOA Migration Training Approach <ul><li>Purpose: </li></ul><ul><ul><li>Ensure that developers able to utilize migrated software </li></ul></ul><ul><ul><li>Ensure that end-users able to configure, monitor, and administer system </li></ul></ul><ul><li>Approach: </li></ul><ul><ul><li>Development Organizations (GSD, MDL, OHD, SEC) planning and executing training </li></ul></ul><ul><ul><li>NWSTD involved in planning and executing operational training </li></ul></ul><ul><ul><ul><li>Focus Areas: </li></ul></ul></ul><ul><ul><ul><ul><li>Local Application Developer </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Application Focal Point </li></ul></ul></ul></ul><ul><ul><ul><ul><li>System Administration </li></ul></ul></ul></ul>http://www.nws.noaa.gov/ost/SEC/AE/Training.htm
    13. 13. SOA Migration Site Migration Approach <ul><li>Purpose: </li></ul><ul><ul><li>Provide structured method to ensure local sites’ migration </li></ul></ul><ul><ul><ul><li>Includes: </li></ul></ul></ul><ul><ul><ul><ul><li>Local Application Migration </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Site Migration </li></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>Application Configuration </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>Product Format Template Configuration </li></ul></ul></ul></ul></ul><ul><li>Approach: </li></ul><ul><ul><li>Team (regions, HQ) plan/coordinate </li></ul></ul><ul><ul><li>Regions/Offices execute </li></ul></ul>http://www.nws.noaa.gov/ost/SEC/AE/Site_Migration.htm
    14. 14. AWIPS Technology Infusion Governance Approach <ul><li>What is it? </li></ul><ul><ul><li>Governance model controls the development, test, integration, configuration management, deployment and support of the new system -- both hardware and software </li></ul></ul><ul><li>Why? </li></ul><ul><ul><li>SOA offers new levels of flexibility and extensibility </li></ul></ul><ul><ul><li>New rules needed to exploit system capabilities, define limits </li></ul></ul><ul><ul><li>Tension between unlimited modifications and ability to support the baseline system </li></ul></ul>http://www.nws.noaa.gov/ost/SEC/AE/Governance.htm
    15. 15. Summary
    16. 16. Summary <ul><li>AWIPS I application migration underway </li></ul><ul><ul><li>Eight incremental deliveries of infrastructure and functionality provided thus far for NWS testing and evaluation </li></ul></ul><ul><ul><li>Final incremental delivery of functionality (TO11) targeted for Fall 2009 </li></ul></ul><ul><ul><li>OTE begins – Winter 2009 </li></ul></ul><ul><ul><li>Deployment - 2010 </li></ul></ul><ul><li>AWIPS SOA Extension projects that will enhance NWS operations are underway </li></ul><ul><ul><li>NAWIPS migration in progress </li></ul></ul><ul><ul><ul><li>First incremental delivery of functionality provided to users for testing/evaluation, April, 2009 </li></ul></ul></ul><ul><ul><ul><li>Next incremental delivery targeted for Fall 2009 </li></ul></ul></ul><ul><ul><li>Thin Client, Data Delivery, CHPS, WES integration and Collaboration Projects </li></ul></ul><ul><ul><ul><li>Requirements definition, AWIPS SOA evaluation and prototyping - 2009 -> 2010 </li></ul></ul></ul><ul><ul><ul><li>IOC targeted for FY11 </li></ul></ul></ul>