1 / 97

NextGen Network Enabled Weather

NextGen Network Enabled Weather. Table of Contents. Introduction & Background High-Level Segment 1 View & Transition Service Adaptors & Data Flow Spreadsheet Architecture Demonstrations & Capability Evaluations Backup. Table of Contents. Introduction & Background 4-D Wx Data Cube

cleave
Download Presentation

NextGen Network Enabled Weather

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. NextGen Network Enabled Weather

  2. Table of Contents • Introduction & Background • High-Level Segment 1 View & Transition • Service Adaptors & Data Flow Spreadsheet • Architecture • Demonstrations & Capability Evaluations • Backup

  3. Table of Contents • Introduction & Background • 4-D Wx Data Cube • Architecture • High-Level Segment 1 View & Transition • Backup

  4. Introduction & Background

  5. The Basis for the NNEW Program

  6. NextGen Goals from NextGen CONOPS v2 • Network-Enabled Information Access • Performance-Based Services (now Performance-Based Operations and Services) • Weather Assimilated into Decision-Making • Layered, Adaptive Security • Broad-Area Precision Navigation (now Positioning, Navigation, and Timing [PNT] Services) • Aircraft Trajectory-Based Operations (TBO) • Equivalent Visual Operations (EVO) (the characteristics of which are described throughout this concept) • Super-Density Arrival/Departure Operations.

  7. NNEW Objectives Provide universal access to required wx data envisioned by NextGen 4-D Wx Data Cube Establish SWIM compatible Wx Service Oriented Architecture (SOA) within FAA Establish interagency wx SOA Adopt/develop standards Develop capability for discovery across different taxonomies (e.g., JMBL and Climate & Forecast) Develop capability for dynamic brokering between heterogeneous clients (e.g., WCS client) and providers (e.g., JMBL providers) Develop discovery metadata guidance Develop FAA wx service-oriented & physical architecture

  8. 4-D Wx Data Cube

  9. What is the 4-D Wx Data Cube? • Data from various publishing systems—but not the publishing systems themselves • Software that provides capabilities for • locating and retrieving data • subsetting of data and a number of other functions • Service adapters to support legacy systems

  10. 4-D Wx Data Cube Functions • Locating and retrieving data • A feature of a SOA that requires: • Registry/Repository • SOA services • Subsetting of data (geographically, by time, & by wx parameter) • Being enabled by adopting new data formats, namely: • netCDF-4 for gridded data • Weather Exchange Model (WXXM) for non-gridded data

  11. Registry/Repository • An ebXML reg/rep based on Organization for the Advancement of Structured Information Standards(OASIS) standard is being used for the Cube • Supports • design-time discovery • At design-time, a service provider or consumer uses a registry to discover information about an abstract service, including all the details needed to build server and client-side software • runtime discovery • At runtime, applications discover instance-specific information, such as the individual addresses of each service • The reg/rep software is a commercial product developed by a firm working closely with the NNEW Program

  12. Metadata • Data about data • Resides in the registry/repository • Provided by data providers • Makes it practical to search for data in the Cube • The Content Standard for Digital Geospatial Metadata (CSDGM), Vers. 2 (FGDC-STD-001-1998) is the US Federal Metadata standard • U.S. is working toward using the international standard—ISO 19115 • NNEW has developed Metadata Guidelines for the 4-D Wx Data Cube that provides guidance for metadata within the bounds of the standards

  13. SOA Services • FAA has adopted Open Geospatial Consortium (OGC) Standards—NOAA has not yet made a decision—could adopt JMBL • OGC Standards • Web Coverage Service (WCS) for gridded data • Web Feature Service (WFS) for non-gridded data • Also probably Web Mapping Service for information available only in map form • Joint METOC Broker Language (JMBL) • Developed and used by DoD • Software—Reference Implementations (RI)—is currently being developed for WCS & WFS

  14. Wx Data Representation • netCDF-4 • a set of software libraries and machine-independent data formats that support the creation, access, and sharing of array-oriented, scientific data • WXXM • Defines a common vocabulary for exchanging weather information between organizations • Being developed jointly by NNEW and EUROCONTROL

  15. Data Format Development • Data encoded in netCDF-4 and WXXM have been or are being developed for numerous products, including, for example: • NEXRAD Level III products & mosaics • METARs, TAFs, SIGMETs, PIREPs • CIWS products • ITWS products • CIP, FIP, GTG • Model data

  16. 4-D Wx Data Cube Additional Functions • Provided by the RIs • Support a variety of geographic projections & conversions among them • Conversions among measures of height • Archiving • Provided by the reg/rep • Dynamic brokering between heterogeneous clients using the ontology • Complex Retrieval Processing • A set of functions currently being defined

  17. Dynamic Brokering & Mediation • Dynamic brokering between heterogeneous clients • Provides the ability to search for data among sources using different terminologies • Mediation • Provides the ability to change data retrieved from one terminology to another

  18. Ontology • The 4-D Wx Data Cube may contain data that use two different sets of terminologies: Climate & Forecast (C&F) and JMBL • An ontology is needed to enable searching for datasets registered in the Registry/Repository in a vocabulary-independent manner • This ontology is under development

  19. Complex Retrieval Processing (CRP) • CRP will include functions such as • Combining data into a single response when responding to a request for data along a flight path • Archiving data and retrieval of archived data • Centralized auditing • Mediation

  20. Architecture

  21. 4-D Wx Data Cube Context 21

  22. 4-D Wx Data Cube Conceptual Architecture Automation Systems Weather Systems 4-D Wx Data Cube TFM Planners NWP TFMS ERAM Sector Controllers ITWS System Data Retrieval AOC STARS RASP Avionics Weather Related Services System Data Ingest Weather Related Services Dispatchers MADIS Terminal Controllers Pilots 22

  23. 4-D Wx Data Cube SOA Context Consumers Forecast Systems AOC Automation TFMS Automation Interaction Services “Translation Services” Mission Services Content Management Services CRP Services Basic 4-D Wx Data Services Data Acquisition Services AIM Services Flow/Flight Services Providers Net-Enabled Services 4-D Wx Data Cube Other Services CRP – Complex Retrieval Processing 23 ERAM Automation Weather Systems Forecast Systems

  24. 4-D Wx Data Cube High-Level Physical Architecture Consumer Automation Weather Data End Users Consumer Automation Weather Data End Users Weather Data End Users Origin Server Distribution Server Weather Provider System Consumer Automation Distribution Server FTI WAN 4-D Wx Data Cube Registry/ Repository Origin Server Distribution Server Weather Provider System

  25. Notional Interagency Architecture External DMZ Reg/Rep NAS Incoming Distribution Server NAS Outgoing Distribution Server Data Filter = NNEW Provided System = NWS Provided System SupportEnclave FAA Data Providers Output Edge Servers Reg/Rep Origin Servers NOAA Gateway CRP Servers Internal DMZ NWS Data Providers FAA Enterprise Cube Input Edge Servers FTI IP WAN NWS IP Networks Reg/Rep Distribution Servers Distribution Server Distribution Server Cube Output Edge Servers Weather Data Consumers Consumer Automation Consumer Automation NOAA Enterprise Weather Data Consumers Weather Data Consumers Support Enclave Core Enclave 25

  26. Interagency Data Exchange Sequence“Caching Proxy” Start: End User Makes request requiring weather information Data retrieved From NWS on 1st data request and then cached locally. FAA/NWS Security Boundary* Subsequent requests May be serviced directly * details of the security boundary not depicted 26

  27. Interagency Data Exchange Sequence (cont) Basic flow for a request/response exchange with NWS • Consumer Systems initially directed to an assigned Distribution Server by the Registry • In response to requests, Distribution Servers collect data from Origin Servers/Cube Input Edge Servers • Distribution Servers cache data locally for a limited amount of time. • Caching allows for quicker responses for multiple requests of the same data from the same Distribution Server Architecture is configurable and allows for transition of NextGen capabilities • Allows for growth of NextGen capabilities in NAS Automation • Allows for transition of Weather Data Providers per the NAS Roadmap 27

  28. Ongoing architecture work -Modeling & Simulation • Goals • Understand how the 4-D Wx Data Cube performs as user loads increase • Performance with legacy provider and consumer systems integrated via service adaptors • Performance with provider and consumers that employ NextGen capabilities and have adopted native, net-enabled interfaces • Understand trade-offs between latency and bandwidth • Tiered Distribution Server architecture • Number of Distributions Servers • Impact of interagency boundary gateways • Composed services • RMA • Products • Preliminary Analysis of NNEW Performance – July 2010 • Detailed Analysis of NNEW Performance – March 2011

  29. High-Level Segment 1 View & Transition

  30. NNEW & NWP Segment 1

  31. 2010 2011 2012 TWIP ITWS NWP ITWS NEXRAD NEXRAD WARP WINS RASP FBWTG NWP Prototype (NNEW Enabled) FS 21 FIS TFM Specialist TFM NAS Weather Architecture Segment 1 - 2015 Service Adaptor and Wx Architecture Development Legend Pilot Sensors Sources - / LLWAS R S End User System Display / ( ) Weather Processor Server Customer / ASR - WSP Terminal Communications Links ITWS ASR - 9 WX Interface ETMS ETMS Tower/TRACON Controller Consumer Cube Service Adaptor (CCSA) Local Displays Traffic Flow Specialists LLWAS - NE SD TDWR Provider Cube Service Adaptor (PCSA) Approach Controller NIDS NIDS Airline Operations Center Non- SOA/Cube Connection External Users SOA/Cube Connection ASOS / AWOS 4-D Weather Data Cube Prototype Local Displays Lightning TWIP 4-D Weather Data Cube Pilot Vendor ADAS ARTCC DSR Global Sources ETMS ETMS WMSCR En Route Controller ATOP ATOP MDCRS Meteorologists URET ERAM / URET Via Traffic Flow Specialists HOST ARINC DOTS + DOTS Oceanic ATC FDP2K FDP2K FDP2K NIDS NOAA Product NOAA Product ATCSCC Generation Generation Vendors ETMS ETMS Centers Centers Traffic Flow Manager DOTS DOTS + External Users Flight Services FSS Specialist Pilot Pilot CIWS Prototype

  32. NNEW Program Key Elements • Standards Development • Data Access Standards • Open Geospatial Consortium (OGC) standards, principally Web Coverage Service (WCS) and Web Feature Service (WFS) • Data Format Standards • GML, XML, and NetCDF-4 • Working with EUROCONTROL to develop a common data model • Metadata Standards • 4-D Wx Data Cube Architecture • High-level 4-D Wx Data Cube interagency architecture • Lower level architecture for FAA’s portion of 4-D Wx Data Cube

  33. NNEW Program Key Elements (cont) • Software Development • Registry/Repository • ebXML-compliant reg/rep obtained from a commercial source (Wellfleet) • Reference Implementations of WCS and WFS • Software that implements the WCS and WFS standards • Provides the mechanism to connect consumers with providers and return the data that are requested • Ontology • Enables searching for datasets registered in the Registry/Repository in a vocabulary-independent manner • Service adapters • Enables legacy systems to provide data to, or use data from, 4-D Wx Data Cube without rewriting the legacy system software

  34. NextGen Infrastructure Program Stack(Long-Term Outlook) ITWS Weather Systems/Programs (Data Producers/ Consumers) NNEW Weather-Specific Data Formats & Access Services Federated Registry/Repository and Registry Extensions Deployed weather data distribution hubs Runtime Registration (required for weather (especially for SAS) SWIM may or may not provide this Metadata tagging massive quantities of information for content Interagency coordination Ensuring appropriate weather info is available and published Retrieving only needed weather information Define business logic within the service container . . . . . . . . . . . RASP NWP AIM Flow Flight CATM Mission & Domain SOA Infrastructure/ Extended Services . . . . . SWIM Messaging, Security, Monitoring, Core Registry, DNS ? Cross-Domain SOA Infrastructure/ Core Services FTI Basic IP Connectivity Fault-Tolerant Backbone Physical Network Layer Infrastructure

  35. BACKUP

  36. WARP Briefing Terminal (BT) Replacement • When WARPs are decommissioned, the functions of the BTs needed to be accommodated • All data needed/used by the BTs will be net enabled • Recommendation: Utilize NIDS displays as the replacement for WARP BTs

  37. Service Adaptors & Data Flow Spreadsheet

  38. Service Adaptors (SA) • Purpose • Provide the capability for legacy systems to communicate with the 4-D Wx Data Cube • SAs come in two flavors • Provider Cube Service Adaptors (PCSA) • Consumer Cube Service Adaptors (CCSA)

  39. Service Adaptors (cont) • Currently identified Segment 1 SAs • PCSAs • RASP (complete) • ITWS (scheduled for FY10) • CCSAs • DOTS (scheduled for FY10) • ATOP (scheduled for FY10) • FDP2K (scheduled for FY11) • ITWS (scheduled for FY11) • TFMS (scheduled for FY11) • NIDS (scheduled for FY12) • ERAM/URET (scheduled for FY12)

  40. Service Adaptors (cont) • Service Adaptor Plan • For each identified system documented the • Current data flows (i.e., the sources and sinks for the weather products) • The presumed data flows at Segment 1 timeframe • Plan includes NWP even though no SA is required

  41. SA Plan Diagrams – CIWS Transition Current CIWS Flows Future

  42. SA Plan Diagrams – WARP Transition Current WARP Flows Future

  43. SA Plan Diagrams – ADAS/RASP Transition Current ADAS/RASP Flows Future

  44. SA Plan Diagrams – ATOP Transition Current ATOP Flows Future

  45. SA Plan Diagrams – DOTS Plus Transition Current DOTS Plus Flows Future

  46. SA Plan Diagrams – ERAM/URET Transition Current ERAM/URET Flows Future

  47. SA Plan Diagrams – FDP2K Transition Current FDP2K Flows Future

  48. SA Plan Diagrams – ITWS Transition Current ITWS Flows Future

  49. SA Plan Diagrams – TFMS Transition Current TFMS Flows Future

  50. SA Plan Diagrams – NIDS Transition Current NIDS Flows Future

More Related