The Collaborative Radar Acquisition Field Test (CRAFT): Next Steps Kelvin K. Droegemeier University of Oklahoma 2 nd Level II Stakeholders Workshop 26-27.

Slides:



Advertisements
Similar presentations
Shape of a Network.
Advertisements

Banking our next Million Customers Mobile Money Summit 21 – 22 November 2008 Bank South Pacific.
Motorola Confidential Proprietary MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names.
Chapter 4 Computer Networks
COMPUTER NETWORK TOPOLOGIES
Computer Network Topologies
Top 10 Ways Of Reducing Your Data Center Infrastructure Operating Costs.
Nilesh Agre Wedashree Jalukar Neelima Shahi Group Members.
© 2007 Cisco Systems, Inc. All rights reserved.ICND1 v1.0—1-1 Building a Simple Network Exploring the Functions of Networking.
Based on Data Communications and Networking, 4 th Edition. by Behrouz A. Forouzan, McGraw-Hill Companies, Inc., 2007 Dr. Mznah Al-Rodhaan Chapter 1 Introduction.
CP Networking1 WAN and Internet Access. CP Networking2 Introduction What is Wide Area Networking? What is Wide Area Networking? How Internet.
Unisys Weather Information Services Presentation for NWS Partners Meeting Partner Perspective June 2010 Ron Guy, Director Unisys Weather
Marwan Al-Namari Week 2. ADSL : Asymmetric Digital Subscriber Line Ethernet networks - 10BASE-T - 100BASE-TX BASE-T BASE-TX (Cat5e.
8.
Business Continuity and DR, A Practical Implementation Mich Talebzadeh, Consultant, Deutsche Bank
Web Caching Schemes1 A Survey of Web Caching Schemes for the Internet Jia Wang.
Update On The NEXRAD Agency Plans For Near Real-Time WSR-88D Base Data Collection And Distribution Tim Crum, Ph.D. Radar Operations Center (ROC) NWS Focal.
Semester 4 - Chapter 3 – WAN Design Routers within WANs are connection points of a network. Routers determine the most appropriate route or path through.
Copyright©2008 N.AlJaffan®KSU1 Chapter 8 Communications and Networks.
Core 3: Communication Systems. On any network there are two types of computers present – servers and clients. By definition Client-Server architecture.
Firewalls and VPNS Team 9 Keith Elliot David Snyder Matthew While.
Network Topologies.
This is the way an organisation distributes the data across its network. It uses different types of networks to communicate the information across it.
Route Planning and Evaluation
November 2009 Network Disaster Recovery October 2014.
1 Wide Area Network. 2 What is a WAN? A wide area network (WAN ) is a data communications network that covers a relatively broad geographic area and that.
Server and Short to Mid Term Storage Funding Research Computing Funding Issues.
1 IT Governance 2006 Strategy/Business Case Presentation Department of Human Services.
Project CRAFT: A Test Bed for Demonstrating the Real Time Acquisition and Acrhival of WSR-88D Base (Level II) Data Presented to UCAR/Unidata Program 12.
Network Design Essentials
Chapter 4: Computer Networks Department of Computer Science Foundation Year Program Umm Alqura University, Makkah Computer Skills /1436.
Comparing modem and other technologies
Server Virtualization: Navy Network Operations Centers
OSC (Ohio Supercomputer Center) 1224 Kinnear Road, Columbus, OH (614) www.osc.edu THIRD FRONTIER OVERVIEW OPLIN MEETING April.
Update on the Collaborative Radar Acquisition Field Test (CRAFT): Planning for the Next Steps Kelvin K. Droegemeier University of Oklahoma Presented to.
Enterprise Storage A New Approach to Information Access Darren Thomas Vice President Compaq Computer Corporation.
Networking By Nachiket Agrawal 10DD Contents Network Stand Alone LAN Advantages and Disadvantages of LAN Advantages and Disadvantages of LAN Cabled LAN.
Co-location Sites for Business Continuity and Disaster Recovery Peter Lesser (212) Peter Lesser (212) Kraft.
Definitions What is a network? A series of interconnected computers, linked together either via cabling or wirelessly. Often linked via a central server.
The University of Bolton School of Games Computing & Creative Technologies LCT2516 Network Architecture CCNA Exploration LAN Switching and Wireless Chapter.
1 LAN design- Chapter 1 CCNA Exploration Semester 3 Modified by Profs. Ward and Cappellino.
WIPO Pilot Project - Assisting Member States to Create an Adequate Innovation Infrastructure to Support University – Industry Collaboration.
LAN Switching and Wireless – Chapter 1 Vilina Hutter, Instructor
Intro to Network Design
Accounting Information System By Rizwan Waheed M.Com 710.
Chapter 21 Topologies Chapter 2. 2 Chapter Objectives Explain the different topologies Explain the structure of various topologies Compare different topologies.
The McGraw- AS Computing LAN Topologies. The McGraw- Categories of LAN Topology.
9 Systems Analysis and Design in a Changing World, Fourth Edition.
Welcome to the 2 nd WSR-88D Level II Data Stakeholders Workshop!!
SHAPE OF A NETWORK COPYRIGHT BTS TOPOLOGY The way the computers are cabled together Four different layouts Logical topology describes the way data travels.
Chapter2 Networking Fundamentals
Adoption and Use of Electronic Medical Records (in Federally Qualified Health Centers) and Supporting an ASP Community Care Network of Virginia, Inc.
Ministry of Science and Technology Mozambique Research and Education Network - MoRENet Jussi Hinkkanen Ministry of Science and Technology Mozambique.
WEEK 11 – TOPOLOGIES, TCP/IP, SHARING & SECURITY IT1001- Personal Computer Hardware System & Operations.
Network Topologies.
3/12/2013Computer Engg, IIT(BHU)1 CLOUD COMPUTING-1.
1 Unidata Policy Committee 5 February Level II Data Access & Distribution Linda Miller Roots Roots Why Level II Data? Why Level II Data? CRAFT CRAFT Applications.
Shape of a Network 10/10/07. Topology  The way the computers are cabled together  Four different layouts  Logical topology describes the way data travels.
Network Funding Model Recommendation May Click to edit Master title style Click to edit Master subtitle style Technology. It’s Happening Here. 
SIP & How It Relates To YOUR Business. Jeff S. Olson Director of Marco Carrier Services David Bailey-Aldrich Technology.
Physical Network Topology. When working with a network What is Physical Topology????? The physical topology of a network refers to the configuration of.
Introduction Chapter 1. Introduction  A computer network is two or more computers connected together so they can communicate with one another.  Two.
An Introduction to Local Area Networks An Overview of Peer-to-Peer and Server-Based Models.
Ad-hoc Networks.
Semester 4 - Chapter 3 – WAN Design
Computer Network Topologies
Network Configurations
Wide Area Network.
Designing a local area network
Tailor slide to customer industry/pain points
Presentation transcript:

The Collaborative Radar Acquisition Field Test (CRAFT): Next Steps Kelvin K. Droegemeier University of Oklahoma 2 nd Level II Stakeholders Workshop September 2002 Norman, Oklahoma NCDC

n Grant funding for CRAFT communication links and personnel is nearly exhausted (data will stop flowing from CAPS sometime in November) n The private and academic sectors are finding value in real time Level II data n A real time Level II NWS collection system –is likely more than 1 year away –may not provide the latencies and reliability needed by the private sector for the short term –may be perfectly suited for meeting all needs in the longer term n What options exist? n How can we maximize the benefits to all stakeholders: Government, industry, academia? The Issues Before Us

n A wide range of potential options exists, all of which require Government approval –Shut CRAFT down and wait for the NWS system n Timeline not yet defined n Not clear the NWS system will meet non-Government user needs n We likely won’t know until the system is in place n If it does meet all user needs, we’re set n If it does not, no alternative will exist (might take months to create) –Continue the present collaborative system (58 radars) or expand to all 120 NWS radars (lots of sub-options) –Create a stand-alone system that includes all 120 NWS WSR-88D radars, serves as a back-up to whatever the NWS implements, and has 7x24 support, improved reliability, etc n Must consider administration of system (later in talk) n The ideal perhaps is a partnership among all groups, with “partnership” defined many ways Options

Suppose the NWS Deploys and Manages its Own Level II Distribution System (a very sensible approach)

CRAFT as a Scalable System: The Current Concept Expanded for “Operational” Deployment

LDM Server Logical Network Topology

LDM Server Logical Network Topology At the moment, OU is the only server – Single points of failure (server and line from each radar) OU

Logical Network Topology LDM Server Universities NOAA Laboratories NOAA Joint Institutes NCAR/UCAR MIT/Lincoln Lab NWS Regional HQ, NCEP Centers, RFCs NCEP Centers, RFCs

Logical Network Topology LDM Server These already exist!! Universities NOAA Laboratories NOAA Joint Institutes NCAR/UCAR MIT/Lincoln Lab NWS Regional HQ, NCEP Centers, RFCs NCEP Centers, RFCs

Logical Network Topology LDM Server via phone lines or commodity Internet Abilene Backbone (no commercial traffic) Commodity Internet

LDM Server

Abilene Network LDM Server

Abilene Network Each LDM “Hub Site” Carries all 88D data on Abilene “bus”-- redundancy LDM Server

HUB

Abilene Network LDM Server

Abilene Network Commodity Internet LDM Server

Abilene Network Commodity Internet LDM Server

Abilene Network Commodity Internet LDM Server

Abilene Network Commodity Internet LDM Server

Abilene Network Commodity Internet Customers LDM Server Private Company Dedicated or Commodity LDM Server

Abilene Network LDM Server

n NOAA runs its own operational ingest system but allows connections to the BDDS of each NWS radar n The CRAFT configuration –Is completely scalable to more nodes or radars –Is highly redundant (each major hub server contains all of the data) –Is highly reliable (loss of a major hub has minimal impact) –Leverages existing infrastructure –Links easily to other networks (e.g., AWIPS) –Has significant capacity for future growth (dual-pol, phased array) –Could have dual communication lines from each radar –Could serve as a backup system for the NWS Features of this Concept

n Many variants exist n May require enhancements to LDM, e.g., multi-cast n Must consider support of LDM to the commercial sector n Key point is to create a national hierarchical distribution system along the lines of the current Unidata IDD Features of this Concept

Primary Ingest Node

Relay Node

Leaf Nodes

8 Scenarios (6 Detailed) and Provisional Costs

n Scenario #1: Maintain the current system of 58 radars with OU as the single ingest node –Assumptions n Line charges paid by same groups as now, at the same rates Possible Scenarios

n Scenario #1: Maintain the current system of 58 radars with OU as the single ingest node –Assumptions n Line charges paid by same groups as now, at the same rates –6 Sea Grant sites: $31K/year –6 SRP sites $72K/year –21 MIT sites$200K/year –4 Florida sites $5K/year –10 OU sites $80K/year –11 other sites FSL, NASA, GTRI, SLC, RAP, SEA (no cost estimates available) n Total leveraging is ~ $450,000 per year Possible Scenarios

n Scenario #1: Maintain the current system of 58 radars with OU as the single ingest node –Assumptions n Line charges paid by same groups as now, at the same rates n No significant s/w development or 7x24 QOS n Maintain current OU staff levels (C. Sinclair at 1.0 FTE and S. Hill at 0.5 FTE) n $20K for h/w replacement, $10K for travel (per year) n $1K for supplies (per year) n KD, DJ, DE at 1 month each (1.0 FTE) (per year) –Yearly cost: $355,000 (could be reduced by shifting some existing lines to cheaper alternatives) –Advantages n No additional h/w costs (above replacement) n Continue using a proven reliable infrastructure Possible Scenarios

–Disadvantages n Not all radars are included n Continue with heterogeneous communications infrastructure, latency problems n Relies on existing groups to continue paying their local costs n Little increase in QOS (i.e., no 7x24) n 56K lines will continue to fall behind in weather n Single ingest system at OU provides no redundancy n Reliance upon university for private sector mission- critical needs n No clear path to deal with data volume increase; however, this may not be critical if NWS system is available relatively soon Possible Scenarios

n Scenario #2: Same as Scenario #1, but add the remaining 64 NWS radars –Additional assumptions n New CAPS technical staff member ($40K/year) for QOS and other work n $100K in one-time costs for PCs n $200K for one-time line installation costs and routers n $50K in travel n $5K for supplies n $50K in h/w replacement costs and hot spares n 30 new lines cost average of current OU lines; rest cost $50/month based on DSL/cable modem –Year-1 cost: $1.3M (could be reduced by shifting some existing lines to cheaper alternatives) –Beyond Year-1: Estimate $900,000/year Possible Scenarios

–Advantages n No additional h/w costs (above replacement) n Continue using a proven reliable infrastructure n All 120 NWS radars available n Improved QOS via 2 nd OU staff person Possible Scenarios

–Disadvantages n Not all radars are included n Continue with heterogeneous communications infrastructure, latency problems n Relies on existing groups to continue paying their local costs n Little increase in QOS (i.e., no 7x24) n 56K lines will continue to fall behind in weather n Single ingest system at OU provides no redundancy n Reliance upon university for private sector mission- critical needs Possible Scenarios

n Scenario #3: Same as Scenario #2, but add UCAR as a second Abilene ingest node –Additional assumptions n $100K in computer hardware at UCAR n One new UCAR technical staff member –Year-1 cost: $1.5M (could be reduced by shifting some existing lines to cheaper alternatives) –Beyond Year-1: Estimate $1.2M/year –Note: Could possibly add MIT/LL as third redundant node, but this has not been discussed with them Possible Scenarios

–Advantages n No additional h/w costs (above replacement) n Continue using a proven reliable infrastructure n All 120 NWS radars available n Improved QOS via 2 nd OU staff person n Greatly improved redundancy, reliability, latencies Possible Scenarios

–Disadvantages n Not all radars are included n Continue with heterogeneous communications infrastructure, latency problems n Relies on existing groups to continue paying their local costs n Little increase in QOS (i.e., no 7x24) n 56K lines will continue to fall behind in weather n Single ingest system at OU provides no redundancy n Reliance upon university for private sector mission- critical needs (not clear that UCAR can provide needed QOS) Possible Scenarios

Scenario Summaries (1-3) No. Radars Ingest Nodes CommunicationsInfrastructureQOS Yearly Cost Scenario 1 58OU Current Heterogeneous Mix* Low$0.36M Scenario 2 122OU Current Heterogeneous Mix* Med $1.3M (Yr 1) $0.9M (Yr 2) Scenario OU & UCAR** Current Heterogeneous Mix* High $1.5M (Yr 1) $1.2M (Yr 2) * Leverages $450K/year paid by other organizations ** Could try and add MIT/LL as third node

n Scenario #4: Same as Scenario #3, but with a national telecommunications carrier providing uniform delivery service to the additional 64 radars only –Additional assumptions n AT&T line costs for 2-year contract for 64 additional radars is $850,000/year. n Mixture of T1, DSL n Note that these costs have not been negotiated and likely could be reduced substantially (might also be able to eliminate T1 lines) n Removes need for one-time installation charges and router costs n Still have the costs of the 64 new LDM PCs –Yearly cost: $2.1M (hope this could be brought down to $1.6 or $1.7M with tough negotiation) Possible Scenarios

–Advantages n No additional h/w costs (above replacement) n Continue using a proven reliable infrastructure n All 120 NWS radars available n Improved QOS via 2 nd OU staff person n Greatly improved redundancy, reliability, latencies n Uniform networking for 64 radars n QOS should be much higher (AT&T rapid response) Possible Scenarios

–Disadvantages n Not all radars are included n PARTLY heterogeneous communications infrastructure, latency problems n Relies on existing groups to continue paying their local costs n Little increase in QOS (i.e., no 7x24) n 56K lines will continue to fall behind in weather n Single ingest system at OU provides no redundancy n Reliance upon university for private sector mission- critical needs Possible Scenarios

Scenario Summaries (1-4) No. Radars Ingest Nodes CommunicationsInfrastructureQOS Yearly Cost Scenario 1 58OU Current Heterogeneous Mix* Low$0.36M Scenario 2 122OU Current Heterogeneous Mix* Med $1.3M (Yr 1) $0.9M (Yr 2) Scenario OU & UCAR** Current Heterogeneous Mix* High $1.5M (Yr 1) $1.2M (Yr 2) Scenario OU & UCAR** AT&T for New 64 Radars High $1.6 to $2.1M * Leverages $450K/year paid by other organizations ** Could try and add MIT/LL as third node

n Scenario #5: Same as Scenario #4, but with a national telecommunications carrier providing uniform delivery service to all radars –Additional assumptions n AT&T line costs for 2-year contract for all radars is $1.4M/year. n Mixture of T1, DSL n Note that these costs have not been negotiated and likely could be reduced substantially (might also be able to eliminate T1 lines) n Removes need for one-time installation charges and router costs n Still have the costs of the 64 new LDM PCs –Yearly cost: $2.8M (hope this could be brought down to $2.2 or $2.3M with tough negotiation) Possible Scenarios

–Advantages n No additional h/w costs (above replacement) n Continue using a proven reliable infrastructure n All 120 NWS radars available n Improved QOS via 2 nd OU staff person n Greatly improved redundancy, reliability, latencies n Uniform networking for ALL radars n QOS should be much higher (AT&T rapid response) n Increased bandwidth needs (e.g., dual-pol, new VCP, ¼ km by ½ degree resolution) could be handled by the telecomm carrier “automatically” Possible Scenarios

–Disadvantages n Not all radars are included n PARTLY heterogeneous communications infrastructure, latency problems n Relies on existing groups to continue paying their local costs n Little increase in QOS (i.e., no 7x24) n 56K lines will continue to fall behind in weather n Single ingest system at OU provides no redundancy n Reliance upon university for private sector mission- critical needs Possible Scenarios

Scenario Summaries (1-5) No. Radars Ingest Nodes CommunicationsInfrastructureQOS Yearly Cost Scenario 1 58OU Current Heterogeneous Mix* Low$0.36M Scenario 2 122OU Current Heterogeneous Mix* Med $1.3M (Yr 1) $0.9M (Yr 2) Scenario OU & UCAR** Current Heterogeneous Mix* High $1.5M (Yr 1) $1.2M (Yr 2) Scenario OU & UCAR** AT&T for New 64 Radars High $1.6 to $2.1M Scenario OU & UCAR** AT&T for ALL Radars High $2.2 to $2.8M * Leverages $450K/year paid by other organizations ** Could try and add MIT/LL as third node

n Scenario #6: Use NWS River Forecast Centers as points of aggregation –May make sense only if the NWS wishes to pursue a non-AWIPS collection strategy –The general CRAFT concept still could be applied n Scenario #7: Use the Planned NWS Distribution System n Scenario #8: Create a System Operated Entirely by the Private Sector (no university or UCAR involvement) Other Scenarios

n Points of Reference (for the sake of argument) –Must be able to ensure 7x24 service (high reliability) –Latency must be as low as possible –Government receives data at no cost but could/should cost share overall expenses in light of benefits to NCDC (direct ingest for long-term archive), NCEP, FSL, NWS Offices (Level II recorders) –Educational institutions receive data at no cost –Presumably don’t want another “NIDS arrangement” n Options –For-profit private company –University-based consortium –Not-for-profit 501(c)3 –University-based center (e.g., Wisconsin for satellite data) –Others? Administrative Structure

n Sustaining the operation of CRAFT beyond November n Establishing private sector requirements –Reliability –Latency –Hardware and software support n Meeting private (and academic) sector needs in the short, medium and long term n Administrative issues (including data access rules) n Dealing with future data volumes n Further analysis of system capabilities –Impact of weather on data reliability/latency –Networking simulation Key Items for Discussion