1 / 21

ALERT2 Protocol Performance

National Flood Workshop Houston, Texas October 2010. ALERT2 Protocol Performance. Don Van Wie, Telos Services R. Chris Roark, Blue Water Design, LLC. ALERT2 Concentration Protocol is in production in Overland Park/KCMO for repeater-to-base path

neron
Download Presentation

ALERT2 Protocol Performance

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 Flood Workshop Houston, Texas October 2010 ALERT2 Protocol Performance Don Van Wie, Telos Services R. Chris Roark, Blue Water Design, LLC

  2. ALERT2 Concentration Protocol is in production in Overland Park/KCMO for repeater-to-base path ALERT2 is operating in parallel with ALERT on repeater-to-base leg in Urban Drainage and Flood Control District ALERT2 Implementations

  3. UDFCD: ALERT v ALERT2 side-by-side comparisons • 8 months, 2 million ALERT messages analyzed • Overland Park: Logging at repeater sites permits exact determination of ALERT2 losses • Early June storms with partial logging • Full month analysis for September 2010 Studies

  4. Demonstrate reliability of hardware in normal operating environment Quantify the relative performance of ALERT/ALERT2 Verify or and adjust the operating parameters based on operations at a production scale Purpose of testing

  5. No hardware failures ALERT2 data loss “over the air” is typically less than 5 reports per 10,000 over any path that is suitable for ALERT Relative ALERT2 performance improves as traffic rates increase RF-only Preamble has been extended 55 msec Slot variance study shows 0.5 second slots are possible The Bottom Line

  6. 10 BWD Modulator/Encoders • 6.5 years of unit time accumulated • 4 BWD Demodulator/Decoders • 4.75 years of combined operation • About half of equipment is in unconditioned environment • NO Failures! HARdware performance

  7. Udfcd overview

  8. Alert To alert2 direct comparison

  9. Recent Overland Park performance

  10. June 8 o.p. storm alert losses

  11. alert2 performance in rain event

  12. Comparison of losses – june 11-12

  13. Smoky hill traffic – alert2 only

  14. Smoky hill traffic – alert on alert2

  15. Alert2 performance v traffic load

  16. Variance from expected slot time

  17. Outliers in GPS CLOCK Setting

  18. To eliminate false setting by anomalous readings: • Limit correction based on plausible drift rate • Lengthen time in lock before taking readings Coming improvements to gps synchronization algorithm

  19. Lengthened preamble affects capacity • Affects first block only • Impact diluted as traffic increases • Size of required deadband controls available slot time; 100 msec will be adequate • 500 msec slots can be used for most gage sites • Capacity of 1 channel is 120 gages, 331 KBytes/ hour • 2 sec slot (repeater) can carry 630 Kbytes/hour or 157,500 ALERT Messages Implications for channel capacity

  20. Ready for new ALERT Concentrator applications Low power repeater for 2011 Vendors are working on gage applications Implementation of Protocol Application layer What’s next…

  21. Thank you

More Related