Basements of properties located in a potential area of flooding are particularly vulnerable to flooding through basement windows. Although prevention is sometimes possible if the property owner/manager can divert the flow of water (e.g., using sand bags), often the owner/manager is unable to mitigate the damage, especially in the event of a flash flood.
During a flood, major damage is caused by water and debris getting into a building. This can be caused by the breaking of basement windows due to the force of the floodwater, or the force of an object being carried by water hitting the window. Once the window breaks, water and mud are free to flow into the basement, causing massive damage. Many people do not have or cannot afford flood insurance to cover damage.
In most cases, any kind of shutter is normally manually deployed or installed at the time it is needed. But flash flood warnings do not leave enough time for manual intervention. Indeed, the homeowners may not even be home to perform the task.
Our solution to this common problem is a deployable waterproof shield that protects a building from flooding during a flood. The flood shield consists of a casing (sometimes referred to as a box or frame hereinafter) that is attached to an exterior wall surrounding an opening (e.g., a window or a door) in the building. The flood shield may be attached to the building after its construction, or may be configured with the building during construction. The shield is in one of two states: deployed or non-deployed. The shield starts in the non-deployed state. In the non-deployed state, the window is unobstructed so that it can be opened fully, allowing both air and light to pass freely and to allow egress. Since the box is outside of the window casing, the view out the window is entirely unobstructed.
In the event of a flood, the shield is deployed. There are a number of ways the shield can be activated, which are discussed later. The activation of the shield causes a waterproof, impenetrable material to cover the entire opening of the casing and prevents any water from getting through or past the shield. The material itself, described later in more detail, is flexible so that it can be stored in a rolled up state when not deployed, but is impenetrable to both water and hard objects that might come in contact with it. Once deployed, the window is protected from both floodwaters and from debris being carried by the water. When the event is over, the shield can be re-stowed so that it can be ready for use at a future time.
In one embodiment, a deployable flood shield prevents ingress of water through an opening. An outer frame is positioned to surround the opening and has a top channel, a bottom channel, a left channel and a right channel. A flexible shield is stored within the bottom channel prior to deployment and has a left edge retained by the left channel and a right edge retained by the right channel. Seals are configured with each of the bottom, left, and right channels for sealing between the bottom, left, and right channels and the flexible shield when deployed. A controller deploys the flexible shield to prevent the ingress of water into the opening.
In another embodiment, a method prevents ingress of water through an opening, and includes the steps of receiving a deploy command, driving, for a predefined period, a motor to deploy a flexible shield to block the opening, and preventing the flexible shield from retracting. The deployed flexible shield is held in position by a frame around the opening.
As shown in
Shield 106 is flexible and easily rolled-up for compact storage within bottom channel 116. Shield 106 is also significantly cheaper to manufacture, as compared to standard metal shutters that may be used to secure windows and doors during inclement weather.
Top channel 108 may include a compartment 110 for storing control electronics (see controller 1100 of
Flood shield 100 also includes a motor 120 and drive gear 121 for deploying flood shield 100. Although shown external to frame 102, motor 120 and drive gear 121 may be positioned within frame 102 without departing from the scope hereof. For example, motor 120 and drive gear 121 may be configured within top channel 108. Drive gear 121 is configured such that shield cannot retract once deployed. For example, drive gear 121 may include a ratchet mechanism that prevents flexible shield 106 from retracting once deployed.
A left edge 416 of flexible shield 106 is positioned within, and retained by, left passage 402 such that flexible shield 106 passes through left slot 403. Left slot 403 has seals 412, 413 positioned on either side of slot 403 and running the entire length of slot 403. A right edge 418 of flexible shield 106 is positioned within, and retained by, right passage 404 such that flexible shield 106 passes through right slot 405. Right slot 405 has seals 414, 415 positioned on either side of slot 405 and running the entire length of slot 405. Seals 412, 413 and seals 414, 415 form a substantially watertight seal with shield 106 when deployed and allow shield 106 to pass therebetween during deployment.
As shown in
A top edge 107 of flexible shield 106 is strengthened by a bar 708 that extends between left channel 112 and right channel 114. Material 506 is permanently attached to bar 708. In one embodiment, material 506 is wrapped around bar 708 and stitched such that bar 708 is retained within top edge 107 of shield 106. In an alternate embodiment, bar 708 is an inverted “U” shape and compressed onto a top edge of material 506 to form top edge 107.
Rod 904 is rotated, during deployment of flood shield 100, by a motor 120 via drive gear 121. As rod 904 rotates, cable 802 is wound around rod 904 at winding area 903. A similar cable and wind up area are positioned in the upper left portion of flood shield 100. Thus, as rod 904 is rotated by motor 120, shield 106 is pulled off of, and up from, roller 702 within bottom channel 116. As shield is pulled up, left and right edges 416, 418 of shield 106 slide upwards within passages 402, 404, respectively, until top edge 107 of shield 106 reaches top channel 108.
Bottom channel 116 includes a retracting mechanism 804 that has a spring 806 coupled with roller 702 and bottom channel 116. As shield 106 is deployed and roller 702 rotates, spring 806 is wound up. Retracting mechanism 804 thereby applies a tension to shield 106 during deployment. A pull 914 is provided to allow a user to retract flexible shield 106, as may be required for emergency egress through opening 153. In one embodiment, pull 914 is coupled via a channel 916 to drive gear 121 and operates to disengage the ratchet mechanism such that retracting mechanism 804 automatically retracts flexible shield 106. Pull 914 is for example positioned on an inside surface of flood shield 100 that is accessible from opening 153 when flood shield 100 is deployed. In one embodiment, pull 914 is positioned on an inner reachable surface (e.g., a lower end of right channel 114, or an inward facing surface of bottom channel 116) of flood shield 100. Releasing pull 914 causes ratchet mechanism within drive gear 121 to reengage, allowing for normal operation of flood shield 100.
Memory 1104 is shown storing software 1110 that has machine-readable instructions that when loaded and executed by processor 1102 perform functionality of controller 1100 as described herein. Memory is also shown storing a status 1112 that represents a current status of flood shield 100 determined by controller 1100. For example, software 1110 may monitor voltage of battery 1160 and store an indicator (e.g., good/bad or the measured voltage, etc.) thereof within status 1112. Optionally, flood shield 100 includes one or more sensors 1140 coupled with controller 1100. For example, sensor 1140 may sense a deployment status of flood shield 100, to indicate whether shield 106 is fully deployed. In another embodiment, one or more sensors 1140 are positioned within flood shield 100 to sense environmental conditions, such as pressure (internal and external to shield 106), temperature (internal and external to shield 106), and so on. Flood shield 100 may include and report information from other sensors without departing from the scope hereof.
In one embodiment, controller 1100 includes multiple receivers/transceivers 1108 such that any one of a wireless local area network (e.g., Wi-Fi), a cellular network as used by mobile phones, and a radio transmitter may be used to communicate with flood shield 100. Flood shield 100 may thus be monitored and controlled by any of these communication means.
Controller 1100 may receive, within receiver/transceiver 1108, a deploy command 1109 from one or more of remote control device 1180, mobile device 1190, remote server 1150 via Internet, and a radio transmitter (e.g., an emergency signal). In one example of operation, a user presses deploy button 1182 of remote 1180 to transmit a wireless signal indicating the required deployment to receiver/transceiver 1108. In another example of operation, receiver/transceiver 1108 detects a broadcast emergency signal and initiates deployment automatically. In another example of operation, an owner of a property uses mobile device 1190 (e.g., a smart phone) to automatically send deploy command 1109 to flood shield 100, via receiver/transceiver 1108 and a Wi-Fi network or a cellular network. In another example of operation, deploy command 1109 may originate from a remote service center and is received by receiver/transceiver 1108 of flood shield 100 via Wi-Fi and/or cellular networks. Optionally, software 1110 may authenticate deploy command 1109 to ensure the source of the command is a source authorized to deploy flood shield 100. In one embodiment, deploy command 1109 includes at least one security feature that is identified and/or checked by software 1110 as an indication of authenticity of deploy command 1109 and its source.
Wireless Network Connectivity
For example, if a property is equipped with a wireless local area network, Wi-Fi, flood shield 100 may be configured to communicate via that network. Flood shield 100 may be added to the network in a similar manner to other devices (e.g., computers, TiVo, Nest, TVs, BluRay devices, etc.). Once connected to the network, flood shield 100 may also connect to the Internet, thereby allowing remote monitoring and control of flood shield 100. With appropriate authorization, status 1112 of flood shield 100 may be remotely monitored and controlled from anywhere with Internet connectivity. For example, status and control of flood shield 100 may be available using a web browser and/or an app (running on a smart device).
Cellular Network Connectivity
Not all homes are equipped with a wireless local area network (Wi-Fi). Therefore, receiver/transceiver 1108 may be configured to communicate using a cellular network instead of, or as well as, Wi-Fi. For example, the cellular network may provide communication with the Internet in the absence of Wi-Fi.
In one embodiment, receiver/transceiver 1108 is configured to receive an emergency broadcast signal via a cellular network. During severe weather, upon receiving the emergency broadcast signal, controller 1100 may be configured to automatically deploy flood shield 100. Thus, commands from an owner, or a service center, are not needed to protect the property.
Radio Frequency (RF) Receiver
Whether or not one or both of Wi-Fi and cellular networks are available, receiver/transceiver 1108 is configured to receive RF signals, for example as generated by nearby remote control device 1180. Remote control device 1180 is similar to a garage door opener, for example, and includes a deploy button 1182, that upon activation, transmits an RF signal to receiver/transceiver 1108. Remote 1180 allows a homeowner to deploy flood shield 100 by pressing deploy button 1182 while remote 1180 is in range of flood shield 100. Remote 1180 may be configured (e.g., paired) to control one or more specific flood shields 100. For example, one remote control device 1180 may be paired with multiple flood shields 100 such that all are deployed simultaneously upon activation of deploy button 1182.
Upon receiving a “deploy” command via receiver/transceiver 1108, processor 1102 executes software 1110 to control motor driver 1106 to drive motor 120 to deploy flood shield 100.
Controller 1100 may also receive a status request, via receiver/transceiver 1108, and respond by sending, via receiver/transceiver 1108, information of status 1112 in reply. That is, mobile device 1190 may request a status from controller 1100, receiving and displaying status 1194 in response. Thus, the user of mobile device 1190 may view a current status of flood shield 100 and remotely deploy flood shield 100.
A server 1150 may communicate with controller 1100 to receive status 1112 and to automatically deploy flood shield 100. Server 1150 may be run by a service company that monitors status 1112 of flood shield 100 and deploys flood shield 100 when needed, for example as determined from emergency information relevant to the installed location of flood shield 100. By monitoring status 1112 of flood shield 100, servicing of flood shield 100 may be scheduled as needed. In one operational example, server 1150 monitors a plurality of flood shields 100 that are deployed on buildings within an area susceptible to flooding. When server 1150 learns (e.g., from a government agency) of possible flooding in that area, server 1150 sends “deploy” commands to the plurality of flood shields 100 and verifies successful deployment through monitoring of status 1112.
In one embodiment, controller 1100 periodically sends status information to one or both of server 1150 and mobile device 1190.
Once deployed, flood shield 100 is able to hold the pressure and force of a flood as well as the force of blunt objects and debris that could be hurdled at it. The design ensures that water cannot seep past the edges. When properly installed, flood shield 100 prevents water and debris from entering a basement via the windows/doorways/openings it is protecting.
In step 1202, method 1200 waits to receive a deploy command. In one example of step 1202, software 1110 monitors input from receiver/transceiver 1108 to wait for a deploy command to be received from any of remote 1180, mobile device 1190, and server 1150. Step 1204 is optional. If included, in step 1204, method 1200 authenticates the deploy command received in step 1202. In one example of step 1204, software 1110 identifies an authentication feature of deploy command 1109 as authentication of the source of deploy command 1109.
Step 1206 is an optional decision. If, in step 1206, method 1200 determines that the deploy command is authentic, method 1200 continues with step 1208; otherwise method 1200 continues with step 1202.
In step 1208, method 1200 activates the deployment motor. In one example of step 1208, software 1110 controls motor driver 1106 to drive motor 120, which winds cables 802 onto winding area 903 and pulls shield 106 from roller 702 until top 107 reaches top channel 108 after a predefined period.
In step 1210, method 1200 deactivates the deployment motor. In one example of step 1210, software 1110 controls motor driver 1106 to switch off power to motor 120 after the predefined period.
Changes may be made in the above methods and systems without departing from the scope hereof. It should thus be noted that the matter contained in the above description or shown in the accompanying drawings should be interpreted as illustrative and not in a limiting sense. The following claims are intended to cover all generic and specific features described herein, as well as all statements of the scope of the present method and system, which, as a matter of language, might be said to fall therebetween.
This application claims priority to U.S. Patent Application Ser. No. 61/894,807, titled “Flood Shield Systems and Methods”, filed Oct. 23, 2013, and is incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
3401527 | Palmer | Sep 1968 | A |
3796010 | Carlson | Mar 1974 | A |
4073147 | Nomura | Feb 1978 | A |
4349296 | Langeman | Sep 1982 | A |
4377352 | Goodstein | Mar 1983 | A |
4488386 | Thompson | Dec 1984 | A |
4692961 | Brown | Sep 1987 | A |
4693042 | Villarreal | Sep 1987 | A |
4754696 | Sarazen et al. | Jul 1988 | A |
5077945 | Koeniger | Jan 1992 | A |
5460572 | Waltz et al. | Oct 1995 | A |
5487701 | Schedegger et al. | Jan 1996 | A |
5645373 | Jenkins | Jul 1997 | A |
5943832 | Russell | Aug 1999 | A |
5944445 | Montgomery | Aug 1999 | A |
5984575 | Knott, Sr. | Nov 1999 | A |
6029405 | Wood | Feb 2000 | A |
6287050 | Montgomery et al. | Sep 2001 | B1 |
6327819 | Kurose | Dec 2001 | B1 |
6393782 | Berridge et al. | May 2002 | B1 |
6425707 | Baxter | Jul 2002 | B1 |
6427396 | Harrison | Aug 2002 | B1 |
6427718 | Stringam | Aug 2002 | B1 |
6485231 | Montgomery et al. | Nov 2002 | B2 |
6588979 | Pasij | Jul 2003 | B1 |
6623209 | Waters, Jr. | Sep 2003 | B1 |
6691761 | Alkhoury | Feb 2004 | B1 |
6692187 | Sprengle et al. | Feb 2004 | B2 |
6737968 | Ergun | May 2004 | B1 |
6884002 | Fuller | Apr 2005 | B1 |
6931802 | Jones et al. | Aug 2005 | B2 |
6991403 | Hendee | Jan 2006 | B1 |
7261492 | Hendee | Aug 2007 | B2 |
7497644 | Cohen | Mar 2009 | B1 |
7523589 | Smith | Apr 2009 | B1 |
7546710 | Abbott | Jun 2009 | B2 |
7549252 | Vaughn | Jun 2009 | B2 |
7552565 | Smith | Jun 2009 | B1 |
7600944 | Keating | Oct 2009 | B1 |
7926539 | Hurst et al. | Apr 2011 | B1 |
7951291 | Nino | May 2011 | B2 |
7972081 | Linares | Jul 2011 | B2 |
8246272 | Heitz | Aug 2012 | B1 |
8277645 | Jarvis et al. | Oct 2012 | B2 |
8308396 | Shook | Nov 2012 | B2 |
8375664 | Gower et al. | Feb 2013 | B2 |
8613171 | Dudash | Dec 2013 | B2 |
20010015038 | Cadalso | Aug 2001 | A1 |
20010015266 | Yates | Aug 2001 | A1 |
20020080038 | Smith | Jun 2002 | A1 |
20030026658 | Wu | Feb 2003 | A1 |
20030082007 | Liou | May 2003 | A1 |
20030110717 | Rodriguez | Jun 2003 | A1 |
20030167696 | Chen | Sep 2003 | A1 |
20040194426 | Shapero | Oct 2004 | A1 |
20040200169 | Hung | Oct 2004 | A1 |
20040267385 | Lingemann | Dec 2004 | A1 |
20050081447 | Kline | Apr 2005 | A1 |
20050129463 | Craig | Jun 2005 | A1 |
20050163570 | Cullen | Jul 2005 | A1 |
20050210777 | Baughn et al. | Sep 2005 | A1 |
20080098679 | Chan | May 2008 | A1 |
20090025317 | Wirz et al. | Jan 2009 | A1 |
20090252557 | Fisher | Oct 2009 | A1 |
20100006239 | Kraeutler | Jan 2010 | A1 |
20100032105 | Drifka | Feb 2010 | A1 |
20100043298 | Anhamm | Feb 2010 | A1 |
20100306533 | Phatak | Dec 2010 | A1 |
20110108214 | Komatsu | May 2011 | A1 |
20110154752 | Grover et al. | Jun 2011 | A1 |
20110283620 | Drifka | Nov 2011 | A1 |
20110284249 | Wong | Nov 2011 | A1 |
20110296774 | Tremaine, III | Dec 2011 | A1 |
20120005960 | Tseng | Jan 2012 | A1 |
20120137584 | Thomas | Jun 2012 | A1 |
20130061522 | Alexander et al. | Mar 2013 | A1 |
20130094906 | Rijlaarsdam | Apr 2013 | A1 |
20130199516 | Snyder | Aug 2013 | A1 |
20130272794 | Osborne | Oct 2013 | A1 |
20130340340 | Fukagawa | Dec 2013 | A1 |
20140110066 | Rijlaarsdam | Apr 2014 | A1 |
Number | Date | Country | |
---|---|---|---|
20150107170 A1 | Apr 2015 | US |
Number | Date | Country | |
---|---|---|---|
61894807 | Oct 2013 | US |