1 / 82

TDWRData Supplemental Product Generator

This review presents the plan and progress on implementing the TDWR Supplemental Product Generator, evaluates the technical adequacy and risk resolution, assesses compatibility with requirements, and establishes physical and functional interfaces.

huertaa
Download Presentation

TDWRData Supplemental Product Generator

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. TDWRDataSupplemental Product Generator Preliminary Design Review October 14, 2004 Pete Pickard Office of Science and Technology Systems Engineering Center

  2. Purpose • This review is conducted to: • Present the plan and preliminary progress on the project to implement the TDWR Supplemental Product Generator • Evaluate the progress, technical adequacy, and risk resolution (on a technical, cost, and schedule basis) of the selected design approach, • Determine its compatibility with requirements specifications, • Evaluate the degree of definition and assess the technical risk associated with the selected approach, and • Establish the existence and compatibility of the physical and functional interfaces among the configuration item and other items of equipment, facilities, computer software, and personnel TDWRData PDR 14 October 2004

  3. Agenda • Project Scope • Project Background • Team Organization • Plan for Stage 4 (Operational Development) and Stage 5 (Deploy, Maintain, Assess) • Requirements Overview • Preliminary Design TDWRData PDR 14 October 2004

  4. Agenda (concluded) • Security Planning • Test Planning • Acquisition/Procurement Planning • Deployment Planning • Support Planning • Responsibility Transfer Planning • Next Steps TDWRData PDR 14 October 2004

  5. Project Scope - Phases • Proof of Concept • Four WFO-TDWR sites; WEB server images; completed successfully • Limited Production System • Development of Supplemental Product Generator, modeled on RPG • Standalone initially with SEC O&M • Field test (OAT) concludes in Q3 FY2005 at Proof of Concept sites • Full Scale Deployment • Begin Q3 FY2005 • Forecaster training through WDTB • Site and NRC ElTech training through NWSTC • O&M ultimately under NEXRAD program (Beginning FY2007) • MOA with FAA for TDWR access and O&M support TDWRData PDR 14 October 2004

  6. NWS/FAA MOA • This Agreement covers the following work: • Implementation of telecommunications links between TDWR units and NWS sites, or links between the high impedance taps of the TDWR to ITWS link to NWS sites. • Internal FAA coordination of approvals for TDWR-NWS connections. • NWS coordination of, and funding for, installation of TDWR-NWS telecommunications links. • FAA technician assistance to NWS in maintaining NWS telecommunications equipment at TDWR sites. • Informal sharing of information between local FAA and NWS contacts for TDWR outages and other issues. • NWS use and re-distribution of TDWR weather data. TDWRData PDR 14 October 2004

  7. Project Scope - CONOPS • General concept • Enable WFO forecasters to use TDWR products to support forecasts and warnings in a manner similar to the way they use WSR-88D products. • Use AWIPS radar product request tools and D2D display tools • Complementary rather than primary operational data • Principal users • WFO forecasters initially; wide range of NWS and other users potentially • Operational availability • Similar to WSR-88D, 96% of time that TDWR is operating • TDWR operating status a function of FAA O&M priorities and procedures TDWRData PDR 14 October 2004

  8. Project Scope – CONOPS (concluded) • Operational impacts • More radar data to analyze, with 5 cm wavelength increase in attenuation & range/velocity folding • Improved warning accuracy and reduced false alarms for tornadoes and other severe weather • Potential use for numerical model data assimilation • Organizational impacts • Deployment dependent on AWIPS DX implementation to avoid data server capacity issue • NWS-FAA MOA to enable NWS access to TDWR units • Training • Maintenance concept will include site ElTech support • Potential need for NWS infrastructure capacity enhancements to meet future requirements • Product distribution beyond local WFO • Central collection of products and base data • NCDC archiving TDWRData PDR 14 October 2004

  9. MSP BOS NEXRAD DTW MKE TDWR JFK/LGA CLE ORD PIT PHL CMH EWR MDW SLC BWI DAY MCI DCA IND IAD DIA CVG ADW LAS ICT STL SDF TUL RDU BNA CLT PHX OKC MEM ATL DFW DAL MSY MCO IAH HOU TPA PBI FLL MIA SJU Guam Project Scope – TDWR Sites TDWRData PDR 14 October 2004

  10. Project Background - Mission • Addresses NWS mission needs and NOAA Strategic Goals. • The NWS requires the best possible information on developing thunderstorms to support tornado, severe thunderstorm and flash flood warnings. • TDWR data would complement WSR-88D data with: • Coverage: data for cone of silence and longer ranges of WSR-88D • Timeliness: base elevation update every minute; volume updates every 3 minutes • Spatial resolution: 150 meter linear resolution; potential for ½ degree angular resolution TDWRData PDR 14 October 2004

  11. Project Background - Benefits • By using FAA weather radar data to complement WSR-88D data, benefits can be realized in the following areas: • Long-range low-level phenomena • Different viewing perspectives for a given storm • Potential mitigation of range folding obscuration • Backup during outages • Data in areas of incomplete coverage • Multiple Doppler analysis • Improved “best info” mosaics • Improved quality control of WSR-88D data • Improved precipitation estimates • Alleviate effects of the WSR-88D cone of silence TDWRData PDR 14 October 2004

  12. G3 Core Documents • 1) Need • Identification • Document • 2) Statement of Need • 3) Operations Concept • 4) Operational Reqs. • 5) Program Plan 6) Business Case 7) Requirements Document 8) Operational Development Project Plan 9) Deployment Decision Document 10) Deployment, Maintenance & Assessment Plan G4 Core Documents G2 Core Documents G1 Core Documents Operations and Services Improvement Process G4 G3 G1 G2 Research & Analysis Deploy, Maintain, & Assess Stage 3 Validation Stage 2 Stage 5 Operational Development Stage 4 Stage 1 Need/Opportunity Collection TDWRData PDR 14 October 2004

  13. OSIP Status • Stage 2 and Stage 3 documentation completed • Stage 3 (Research and Analysis) completed • Gate 3 held on 17 August 2004 approved proceeding with Stage 4 TDWRData PDR 14 October 2004

  14. Team Organization • Program Management (OST) • Project Lead (OST) • Project Engineer (OST) • Requirements (OCWWS, OST) • Design, Development (OST) • Maintenance and Logistics (OST, OPS) • Operational Assessment Testing (OST, OPS) • Integration Testing (OST, FSL, NGIT) • Training (NWSTC, WDTB, OST) • Deployment Planning (OST, OPS) • Contracts (OFA) TDWRData PDR 14 October 2004

  15. Plan for Stage 4 and Stage 5 • Other Key Milestones • CDR Q1 FY2005 • Deployment begins Q3 FY2005 TDWRData PDR 14 October 2004

  16. NWS Requirements OverviewOperational Requirements • TDWRData Operational Requirements Document describes the operational capability, technical support, and performance parameters • Continuous operations, 96% availability when TDWR operational • Receive highest spatial and temporal resolution available from TDWR unit • Deploy with spatial resolution consistent with existing product formats • Base reflectivity, velocity and spectrum width product generation for all elevation angles TDWRData PDR 14 October 2004

  17. NWS Requirements OverviewOperational Requirements (concluded) • Product formatting compliant with WSR-88D RPG ICDs • Product request, display and manipulation with same AWIPS tools used for WSR-88D products • Design includes support for implementing additional products • Initial archiving through existing local AWIPS 7-day product archiving capability • Additional NWS archiving requirement is TBD • Level 2 data logging is available on SPG • Requirement for storage to physical media is TBD TDWRData PDR 14 October 2004

  18. SPG Requirements OverviewIntroduction • TDWR SPG Definition - all HW & SW for • base data ingest from the TDWR • real-time generation, storage, and distribution of products • control, status monitoring, and error detection • display and data entry by operational user (as required) • For the purpose of system specification requirements definition, the TDWR SPG is viewed as a subset of the functionality of the WSR-88D RPG. • Only those requirements identified for IOC are presented. TDWRData PDR 14 October 2004

  19. SPG Requirements OverviewIntroduction • High Level Requirements • base data ingest directly from the TDWR • produce products formatted the same as corresponding WSR-88D products • initial product set to include base data products • initially support NWS primary users (AWIPS) • distribute products to AWIPS leveraging the existing radar product request/distribution interface (RPS lists and one-time requests) • products designed and formatted to facilitate operational display via D2D on AWIPS TDWRData PDR 14 October 2004

  20. SPG Requirements OverviewIntroduction • Design Goals • The SPG design should reuse as much of the WSR-88D RPG software as possible. • Design should facilitate adding derived products to the product set • Design should facilitate expansion to include ingest of other FAA radars (ARSR-4, ASR-9, ASR-11) TDWRData PDR 14 October 2004

  21. SPG Requirements OverviewIntroduction • RPG requirements contained in the WSR-88D System Specification served as a guide in developing derived SPG requirements. • RDA, PUP, RMS, MLOS, and BDDS related requirements were not included. • Functional and performance requirements were based upon the initial TDWR product list and a reduced set of product distribution interfaces. • Generally requirements were stated in a manner to be similar to but not more restrictive than corresponding RPG requirements. TDWR data are 'complementary' data. TDWRData PDR 14 October 2004

  22. SPG Requirements OverviewInterface Requirements • External Interfaces • TDWR • Based upon the Terminal Doppler Weather Radar (TDWR) Interface Control Document - NAS-IC-31058603-01 • Product Distribution - limited to AWIPS LAN connection • Interface Control Document for the RPG to Class 1 User - 2620001H • Interface Control Document for the RPG to Class 2 User - 2620007A • Internal Interface • TDWR data to be converted to WSR-88D radial data messages and WSR-88D status messages TDWRData PDR 14 October 2004

  23. SPG Requirements OverviewFunctional Requirements • Data Quality • Range Unfolding - Only requirement is to identify areas contaminated with clutter or overlaid echoes • Data Processing • Transform TDWR data into WSR-88D radial data messages & WSR-88D status messages • Convert azimuth in degrees magnetic to degrees true North • Handle the hazardous mode scan in such a way that • AWIPS can step through the two sequences of increasing elevation angles during product display • AWIPS can step through the redundant base elevation scans TDWRData PDR 14 October 2004

  24. SPG Requirements OverviewFunctional Requirements • Monitor & Control - Status Information • TDWR Status Parameters - monitor available parameters: Average Transmitter power, PRF, Radar Data Output, & TDWR Mode Operability Status • SPG Status Monitoring - same as RPG status except no requirement for printing TDWRData PDR 14 October 2004

  25. SPG Requirements OverviewFunctional Requirements • Monitor & Control - SPG Control • Startup, Restart, & Controlled shutdown - in addition to no requirement for radar control, there are no requirements related to a distributed architecture • Product Generation Control - no requirements relating to alert category • SPG Reconfiguration - manual reconfiguration capability. No requirements relating to multiple processors / redundant sites. NOTE: there are no TDWR control functions including control of VCP and clutter suppression. TDWRData PDR 14 October 2004

  26. SPG Requirements OverviewFunctional Requirements • Product Generation - All products conform with WSR-88D product format IAW the RPG to Class 1 User ICD and the WSR-88D Product Specification • Initial Product Suite • Base Products (truncated to 70,000 feet MSL) • Reflectivity (16 level RLE & 8-bit to 90 km and 276 km) • Velocity (16 level RLE & 8-bit to 90 km) • Spectrum Width (8 level RLE to 90 km) • Alphanumeric Products - Free Text Message • Product Storage - Capability identical to the RPG. TDWRData PDR 14 October 2004

  27. SPG Requirements OverviewFunctional Requirements • Product Distribution • Limited to AWIPS LAN connection • Class 1 User - RPS list and one-time request capability. No requirement for alert product distribution. • Class 2 User - One-time request capability • Product Archive (Archive III) - no requirement on SPG • Archive Level II Data – no operational requirement. SPG tool exists for logging TDWR data for research purposes. TDWRData PDR 14 October 2004

  28. SPG Requirements OverviewFunctional Requirements • Adaptation Data & Control - no RDA / PUP related data • Comm Interface & Control - limited to Class 1 and 2 with no requirement for dial-up connectivity • Power Failure Recovery & Overload Control - same as RPG • Security Requirements - similar to RPG (differences related to the subset of interfaces implemented) TDWRData PDR 14 October 2004

  29. SPG Requirements OverviewSystem Characteristics • Performance Requirements • SPG Full Load Definition - reduced product and external interface set • Response Time Requirements - only requirements relating to SPG functions. • System Configuration • 1 TDWR base data interface • Class 1 interface: 1 - minimum, 4 - full load • Class 2 interface: 4 - minimum, 8 - full load TDWRData PDR 14 October 2004

  30. SPG Requirements OverviewSystem Characteristics • Reliability / Maintainability / Availability (RMA) • same as the RPG • Total Preventive Maintenance (TPM) factor pertaining to the SPG has not been established. • Environmental Conditions - SPG to be operated within an office environment of an NWS WFO. TDWRData PDR 14 October 2004

  31. SPG Requirements OverviewSystem Characteristics • Hardware Design and Construction • COTS requirements and standards apply • Software Design • Portability - POSIX and use of standard languages • Extensibility - defined API interface for applications • Data Processing Reserve - same as RPG • Expandability - same as RPG except no requirements relating to archive devices, additional communication lines, and BDDS interfaces. TDWRData PDR 14 October 2004

  32. Preliminary Design – System Overview – Option ADirect TDWR Connectivity TDWRData PDR 14 October 2004

  33. Preliminary Design - System Overview – Option BFAA Comms Circuit Tap TDWRData PDR 14 October 2004

  34. Prelimnary Design - System Overview - WFO ConfigurationMultiple TDWRs TDWRData PDR 14 October 2004

  35. Preliminary Design – HardwareRack Elevations TDWRData PDR 14 October 2004

  36. Preliminary Design – System Overview – Summary • TDWR data flow to WFO is transmit only (UDP). • TDWR data flows to one WFO only. • A WFO may have up to four associated TDWRs • A firewall at WFO protects AWIPS from FAA network. • The SPG processes data for display by AWIPS D2D. • A KVM controls and configures the SPG. • All procured hardware will be consistent with ORPG and ORDA baseline equipment. • TDWR to use surplus AWIPS racks. TDWRData PDR 14 October 2004

  37. Preliminary Design – System Overview – Summary Cont. • Option A • BCA and costing based on Option A. • Pro - Benefit from competitive pricing from communication carriers. • Con – NWS equipment is located in FAA shelters. Possible FAA coordination issues with maintenance. • Option B • Costing for Option B is being processed. • Con – NWS forced to use FAA communications carrier. • Pro – No NWS equipment located in FAA shelters. TDWRData PDR 14 October 2004

  38. Supplemental Product GeneratorPreliminary Design - Software • SPG Software • Development Team • Warren Blanchard (NWS) - Communications • Andy Stern (Mitretek) - Pre-Processor • Ning Shen (RSIS) - Products, Tools TDWRData PDR 14 October 2004

  39. Supplemental Product GeneratorSoftware Overview • SPG Software • Built from CODE ORPG Build 6 Linux system • Implements existing TCP/IP radar product user ICDs • Adds TDWR specific components • Removes/disables unused ORPG components • AWIPS Software • Changes minimized by duplicating WSR-88D interfaces • New radar added by configuration/localization changes • TDWR specific radar products added as just new radar products TDWRData PDR 14 October 2004

  40. Supplemental Product GeneratorSoftware Overview • The Supplemental Product Generator (SPG) • Processes TDWR base data • Leverages the ORPG infrastructure for algorithm/development environment • Creates and distributes 88D-Like products • Advantages of this approach: • Same user capabilities as the WSR-88D • Maximum reuse of ORPG and AWIPS software • Reduce the amount of new software to develop • Reduce risk, cost, schedule and maintenance • Increase return on investment • Linux being embraced by AWIPS & ORPG • ORPG is a proven operational system with a full support organization TDWRData PDR 14 October 2004

  41. Supplemental Product GeneratorSystem Design • SPG-specific new software modules • TDWR communications manager • TDWR radial data pre-processor • TDWR product generation algorithms • Modifications to baseline ORPG • System & external communications configuration • Site adaptation data definitions • TDWR Volume Coverage Patterns (VCP) • Human Computer Interface (HCI) modifications • New supporting tools • Data logging, data pump, data simulator • Documentation, metrics TDWRData PDR 14 October 2004

  42. Supplemental Product GeneratorCommunications Manager • The communications manager is a daemon that: • Receives UDP data packets or command packets • Controls communications line status & handles exceptions • Builds a complete TDWR base data radial • Forwards the completed Data Structure to a Linear Buffer High Level Data Flow – Communications Manager TDWR Comm Manager TDWR Pre-proc. Process Base Data RESP.1 RESP.0 TDWR Data Translated to 88D Radial Messages UDP Data TDWR Raw Data LB TDWRData PDR 14 October 2004

  43. Supplemental Product GeneratorRadial Data Pre-Processor • The radial data pre-processor is a daemon that: • Receives TDWR radial, status & supplemental messages • Handles needed administrative functions • Internal sequence numbers, status messages, QC • Translates data into complete RDA radial messages High Level Data Flow – Radial Data Pre-Processor Process Base Data TDWR Comm Manager TDWR Pre-proc. RESP.1 RESP.0 TDWR Data Translated to 88D Radial Messages UDP Data TDWR Raw Data LB TDWRData PDR 14 October 2004

  44. Supplemental Product GeneratorAlgorithm Generation • The SPG algorithm generation routines: • Receives 88D-formatted messages from Base Data LB • Uses the ORPG infrastructure and CODE services • Controls some VCP fields to enable looping in AWIPS • Generates ICD-compliant products for Class I users High Level Data Flow – Algorithm Generation Algorithms PBD BD LB Prod LB RESP.0 TDWR Data Translated to 88D Radial Messages Process Base Data Base Data LBs 88D-Like Algorithms Product LB TDWRData PDR 14 October 2004

  45. Task Input Output (Product ID) Trigger Frequency Task 10 REFLDATA (79) Short range 8-bits refl (180) Start of Elev Per Elev Task 10 REFLDATA (79) Short range 4-bits refl (181) Start of Elev Per Elev Task 10 REFLDATA (79) Long range 8-bits refl (186) Start of Vol Per Vol Task 10 Task 11 Task 11 Task 12 COMBBASE (96) COMBBASE (96) COMBBASE (96) REFLDATA (79) Short range 8-bits vel (182) Short range 4-bits vel (183) Long range 4-bits refl (187) Short range 4-bits spw (185) Start of Elev Start of Elev Start of Vol Start of Elev Per Elev Per Elev Per Vol Per Elev Supplemental Product GeneratorSPG Base Products TDWRData PDR 14 October 2004

  46. Supplemental Product GeneratorSystem & External Comms Config. • Un-configure extraneous WSR-88D RPG components with SPG unique versions of configuration files • Comms_link.conf - reduce number and type of communications lines & communications managers to TDWR and TCP/IP users • Tcp.conf – reduce # of TCM user connections to 16 • User_profiles – reduce classes to class 98 (AWIPS) and class 2 (OTR) • Site_info.dea – define site specific configuration, (MLOS, RMS, BDDS, Archive III, radar name, Lat., Long., elevation, etc. of TDWR radar sites) TDWRData PDR 14 October 2004

  47. Supplemental Product GeneratorSystem & External Comms Config. • Modify configuration files • Data_tables – remove extraneous data store definitions; add SPG unique data stores • Product_generation_tables – remove WSR-88D specific products; add SPG unique products • Product_tables – remove WSR-88D product attributes; add SPG product attributes. • Task_table – remove WSR-88D specific tasks & operational processes, extraneous startup & restart commands; add SPG tasks & operational processes, SPG specific startup & restart commands TDWRData PDR 14 October 2004

  48. Supplemental Product GeneratorScan Strategies – Monitor Mode • TDWR Monitor Mode • 17 elevations • Max elev angle 60 deg • 1 long range (refl only) • Elev 2 & 3–same angle • Duration ~6 min TDWRData PDR 14 October 2004

  49. Supplemental Product GeneratorMonitor Mode Comparisons TDWRData PDR 14 October 2004

  50. Supplemental Product Generator Monitor Mode (BWI) SPG VCP 90 TDWRData PDR 14 October 2004

More Related