NETWORKS, SYSTEMS AND METHODS HAVING A HYDRATION PLAN CONTROL SYSTEM FOR WILDFIRE MITIGATION
20230293924 · 2023-09-21
Assignee
Inventors
Cpc classification
A62C37/36
HUMAN NECESSITIES
A62C35/60
HUMAN NECESSITIES
International classification
Abstract
There is provided networks, systems and displays for providing derived data and predictive information for use in emergencies; and in particular for use in wildfire emergencies. More particularly, there is provided systems, equipment and networks for the monitoring and collecting of raw data regarding fire emergencies, both real time and historic. In embodiments, this raw data is then analyzed to provide derived data, predictive data, virtual data, and combinations and variations of this data, which depending upon the nature of this data may be packaged, distributed, displayed and used in various setting and applications to mitigate, avoid and manage the emergency, including a wildfire emergency. In an embodiment the external fire management system has a control system that has hydration plan control commands.
Claims
1. An external fire management system for a structure, the system comprising: a. a system comprising plurality of sprinkler heads; wherein the sprinkler heads are in fluid communication with a source of a hydration material; wherein the sprinkler heads are located on exterior of a structure; wherein the structure defines a footprint of the structure; b. a control system; wherein the control systems is in control communication with the system; c. the control system comprising hydration plan control commands; d. wherein the hydration plan control commands are configured to receive an input, and thereby upon recipe of the input provide the hydration material to a predetermined first zone; and provide the hydration material to a second zone; e. wherein the first zone defines an area that extends uniformly from 4 to about 7 feet away from the structure and thereby the first zone defines a first zone footprint that is larger than and the same shape as the footprint of the structure; and, f. wherein the second zone defines an area that extends uniformly from 15 to about 30 feet away from the structure and thereby the second zone defines a second zone footprint that is large than and the same shape as the footprint of the structure and larger than and the same shape as the first zone footprint.
2. The system of claim 1, wherein hydration material comprises water, foam or a mixture of water and foam.
3. The system of claim 2, wherein the input is one or more of data from a hydration sensor, a signal from a sensor located in the first zone, data from sensor located in the second zone, a signal comprising date information, a signal from a controller, a signal from a GUI located at the structure, a signal from a network and data from a network.
4. The system of claim 3, wherein the sprinklers heads define a sprinkler pattern.
5. The system of claim 4, wherein the sprinkler pattern comprises a first sprinkler pattern and a second sprinkler pattern; wherein the first sprinkler pattern covers 100% of the first zone; wherein the second sprinkler pattern covers 100% of the first zone and at least 90% of the second zone.
6. The system of claim 1, wherein the hydration plan control commands define a hydration plan.
7. The system of claim 6, wherein the hydration plan comprises a maintenance hydration plan.
8. The system of claim 7, wherein the hydration plan comprises a prewetting hydration plan.
9. The system of claim 8, wherein the hydration plan comprises an in-event soak hydration plan.
10. An external fire management system for a structure, the system comprising: a. a plurality of sprinkler heads; wherein the sprinkler heads are in fluid communication with a source of a hydration material; wherein the sprinkler heads are located on the exterior of a structure; wherein the structure defines a footprint of the structure; b. a control system; wherein the control systems is in control communication with a system for delivering the hydration material through the sprinkler heads; c. the control system comprising hydration plan control commands; d. wherein the hydration plan control commands are configured to provide the hydration material to a first zone at a first hydration rate; and provide the hydration material to a second zone at a second hydration rate; e. wherein the first zone defines an area that extends uniformly from 4 to about 7 feet away from the structure and thereby the first zone defines a footprint that is large than and the same shape as the footprint of the structure; and, f. wherein the second zone defines an area that extends from 15 to about 30 feet away from the structure.
11. The system of claim 10, wherein hydration material comprises water, foam or a mixture of water and foam.
12. The system of claim 11, wherein the sprinklers heads define a sprinkler pattern.
13. The system of claim 12, wherein the sprinkler pattern comprises a first sprinkler pattern and a second sprinkler pattern; wherein the first sprinkler pattern covers 100% of the first zone; wherein the second sprinkler pattern covers 100% of the first zone and at least 90% of the second zone.
14. The system of claim 10, wherein the hydration plan control commands define a hydration plan.
15. The system of claim 10, wherein the hydration plan comprises a maintenance hydration plan.
16. The system of claim 10, wherein the hydration plan comprises a prewetting hydration plan.
17. The system of claim 10, wherein the hydration plan comprises an in-event soak hydration plan.
18. An external fire management system for a structure, the system comprising: a. a means for delivering a hydration material to a predetermined area adjacent to a structure; wherein the means for delivery comprises in fluid communication a plurality of distribution heads; valves; pipes; and a source off a hydration material; the means for delivery further comprising a motive means for flowing the hydration material through the distribution heads; b. wherein the hydration material comprises water; c. wherein the means for delivering is configured to deliver the hydration material to a first zone of the predetermined area adjacent to the structure; d. wherein the means for delivering is configured to deliver the hydration material to a second zone of the predetermined area adjacent to the first zone of the predetermined area; e. a control system; wherein the control systems is in control communication with the means for delivery; the control system comprising hydration plan control commands.
19. The system of claim 18, wherein the hydration plan control commands define a hydration plan.
20. The system of claim 18, wherein the hydration plan comprises a maintenance hydration plan.
21. The system of claim 18, wherein the hydration plan comprises a prewetting hydration plan.
22. The system of claim 18, wherein the hydration plan comprises an in-event soak hydration plan.
23. An automated method of maintaining a hydration level in a first and a second zone surrounding a structure to mitigate the risk of a wildfire event, the method comprising: a. a control system comprising a hydration plan control commands; the control system operating an external fire management system to hydrate an area surround a structure in accordance with a hydration plan; b. whereby the area surrounding the structure is maintained at a predetermined level of hydration.
24. An system for obtaining, evaluating and displaying in a predictive manner, information and data regarding fire emergencies, the system comprising: a. a plurality of units configured to provide raw data regarding a fire; i. wherein each unit comprises a communication node on a communication network; ii. wherein at least one of the plurality of units is a mobile unit, comprising a processor and a GUI; and, iii. wherein at least one of the plurality of units is a fixed unit comprising a processor and a GUI; b. a source of derived data regarding one or more of the fire location, an hydration level of combustible materials, a weather condition, a fire movement, a path of a fire, a traffic condition, available water, water usage, a power grid, and electrical usage; i. wherein the source of derived data comprises a communication node on the communication network; c. a processor comprising a communication node on the communication network, thereby placing the processor in communication with the source of derived data and at least one of the plurality of units; d. the processor capable of performing a first predictive computation to determine a change of state event from the raw data and the derived data; e. whereby the processor determines predictive information comprising a probability for the change of state event, and wherein the processer communicates the predictive information to the network, for display by one or more of the units; and, f. a controller in control communication with an external file management system, the controller comprising a processor, a memory and a hydration plan control commands.
25. A system for obtaining, evaluating and displaying information and data regarding wildfires, EFMSs and mobile units, the system comprising: a. a plurality of mobile units configured to receive and transmit information, data or both regarding a wildfire, an EFMS or both, and over a network; i. wherein the units comprise a node on the network; ii. wherein the units comprise a means to determine the location of the unit; iii. wherein the unit comprising a processor, a memory device and a GUI; iv. wherein the information or data comprises one or more of a location of a fire, a location of smoke, a location of embers, a direction of movement of a fire, and an evacuation route; b. a plurality of fixed units configured to receive and transmit information and data over the network; i. wherein each unit comprises a node on the network; ii. wherein each units comprising a processor and a memory device; and, iii. wherein each unit is a component of an EFMS; c. wherein at least one of the mobile units is in control communication with at least one of the fixed units; and a controller in control communication with an external file management system, the controller comprising a processor, a memory and a hydration plan control commands
Description
BRIEF DESCRIPTION OF THE DRAWINGS
[0051]
[0052]
[0053]
[0054]
[0055]
[0056]
[0057]
[0058]
[0059]
[0060]
[0061]
[0062]
[0063]
[0064]
[0065]
[0066]
[0067]
[0068]
[0069]
[0070]
[0071]
[0072]
[0073]
[0074]
[0075]
[0076]
[0077]
[0078]
DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0079] The present inventions relate to networks, systems and the providing of derived data, predictive information, and adaptive strategies for use in multivariable component systems and activities, and in particular, for use in wildfire mitigation, management and suppression, including wildfire emergency response management. In particular, the present inventions relate to systems, networks and methods that provide derived data, predictive data, adaptive strategies, virtual data and combinations and variations of these, for multivariable component systems, such as for use in wildfire mitigation and management and suppression, including wildfire emergency response management.
[0080] More particularly, in embodiments, the present inventions relate to systems, equipment and networks for the monitoring and collecting of raw data regarding wildfire responses, real time, historic and both. This raw data is then analyzed to provide derived data, predictive data, adaptive strategies, virtual data, and combinations and variations of this data, which depending upon the nature of this data may be packaged, distributed, displayed and used in various settings and applications.
[0081] Embodiments of the present inventions relate to systems, equipment and methods for the monitoring, control and management of hydration levels in the area surrounding a structure for the prevention, mitigation and management of wildfires. In preferred embodiments, the hydration levels are determined, established or maintained for predetermined areas surrounding a structure. Further, embodiments of the present inventions include predetermined hydration plans, including, plans based upon raw data, derived data, predictive data, adaptive strategies, virtual data, and combinations and variations of this data.
[0082] In general, embodiments of the present inventions include embodiments of an EFMS that have hydration plans, and in particular predetermined hydration plans, that are a part of the system, and in particular, a part of the control system. The hydration plan, is a protocol or method of operation for the EFMS, that is operated by a series of control commands in the control system. Thus, the hydration plan can be contained in the control system (e.g., in, as a part of, or in control communication with the controller for the EFMS) and is contained in that system, or resides in that system, as hydration plan control commands, i.e., as a computer program, controller commands; algorithm, set of computer instructions and the like. The hydration plan can be stored and updated in the cloud, can be stored on local controllers and updated from the cloud, can be locally updated and combinations and variations of these. The hydration plan, and the hydration plan control commands, in general monitor the hydration levels of combustible materials in the area around a structure and then activate the EFMS to maintain or manage the hydration levels of those combustible materials to as provided in the hydration plan. Thus, in preferred embodiments the EFMS is in control communication with, or has as part of its control system, hydration plan control commands, and thus is capable of implementing the hydration plan.
[0083] In a general, embodiments of an EMFS having hydration plan control commands, for carry out the hydration plan, the EMFS can have and can receive input from devices that directly or indirectly monitor the hydration levels of combustible materials in predetermined areas, i.e., zones, that surround the structure. The devices for monitoring the hydration levels of combustible materials, can include for example: soil moisture sensors; moisture sensors on, or in, vegetation; visual sensors (e.g., color of vegetation); humidity sensors; temperature sensors; data input, memory and processors that can predict or determine hydration levels and hydration trends, and combinations and variations of these and other devices. The zones are primarily configured based upon a predetermined distance from the structure. The zones may also be configured based upon natural fire breaks, fire risk and other geographic or environmental factors.
[0084] Thus, there is typically a first, or inner zone, which is adjacent to the structure and extends out from the structure a few feet to yards (meters). There is typically a second zone, which is adjacent to the first zone (or which can be overlapping) and extends outwardly from the first zone further away from the structure by a few feet to a few yards (meters). In the two-zone embodiment, the second zone would be the outer zone. There can also be a third zone, in which case, the second zone would be considered the middle zone, and the third zone would be considered the outer zone. The third zone would be adjacent to the second zone (overlapping or not over overlapping) and extends outwardly from the second zone further away from the structure by a few feet to a few yards (meters). Additional, zones extending further away from the structure may also be used.
[0085] Generally, the hydration plan, and hydration plan control commands, can have predetermined, derived or both, hydration levels for each zone, and then operate the EFMS to maintain those hydration levels. The hydration levels for each zone can be the same or different. The hydration levels can be varied based upon for example: season, weather conditions, and wildfire information and data. Thus, for example, the hydration levels for each zone can be: (i) predetermined, e.g., a higher level of hydration during fire season, e.g., higher hydration level in inner zone, or both zones; (ii) they can be determined by the control system based upon incoming data, e.g., active fire near structure, which would increase hydration levels in both inner and outer zones, or inner zone first, then outer zone, if/as fire approached; (iii) user input, e.g., setting a desired hydration level, e.g., higher, hydration level for one or more zones; (iv) local zoning, water use requirements, including water use requirements during an active fire event; (iv) based upon derived data, e.g., fire risk conditions calculated based upon real time raw data; and (v) combinations and variations of these, as well as other factors.
[0086] In general embodiments of these EMFS having a hydration plan and the hydration plan method, e.g., the hydrating of the surrounding combustible materials in the areas or zones surrounding the structure, can be configured to remotely protect structures during a wildfire. The system has a source of data that identifies or defines an area around a structure and provides the hydration level of combustibles around that structure and in the area.
[0087] The area can be a series of areas, with each area having a periphery that extends out further from the structure. In this manner the amount of hydration of the combustible material in each of these areas is provided.
[0088] These areas could be concentric, e.g., concentric circles, squares, ovoids or rectangles. These areas can be based upon the shape, e.g., foot print, of the structure, and thus extend outwardly from that foot print by a set distance, and thus the shape of the area would be a larger but similar shape foot print to the structure. These areas can be any geometric shape with one being located inside the other and having a common center point, or different center points. These areas could be overlapping, and partially overlapping (e.g., along the lines of Venn diagrams). These areas could follow the exact shape of the foot print of the structures, thus being a set distance from each wall. The areas can take into account multiple structures, e.g., garage, shed or coach house. These areas may also be based upon, or shaped, to take into consideration the natural contours of the land around the structure, fire breaks such a highway or rivers, and likely wind patterns, among other natural factors, to further define the shape and size of the areas. These areas can use one or more, and combinations and variations of the foregoing shapes and arrangements.
[0089] The areas can also be determined based primarily upon the amount of hydration of the combustibles around the structure. Thus, in periods when the combustibles are very dry, i.e., low levels of hydration (less than 50% water content, less than 25% water content, less than 10% water content, and less than 5% water content) the area can be expanded to provide a large area around the structure for mitigation and monitoring purposed.
[0090] The areas can be hydrated based upon specific amounts of water being applied to the area or zone. Thus, Home Ignition Zone 0 (HIZ0), which is adjacent to the structure, i.e., the inner zone or area, can have a primary hydration amount of: about 2″ of water per 24 hour period; about from 1″ to about 2″ of water per 24 hour period; about 0.7″ to 1.2″ of water per 24 hour period; and, preferably for an HIZ0 having distance from the structure of 5 feet, 1″ of water per 24 hour period.
[0091] The next zone away from HIZ0, and adjacent to HIZ0, which is HIZ1, (outer zone for two zone embodiment, middle zone for three zone embodiment) can be hydrated based upon specific amounts of water being applied to the area or zone. Thus, Home Ignition Zone 1 (HIZ1), which is adjacent to HIZ0 can have a primary hydration amount of: about 1″ of water per 24 hour period; about from 0.5″ to about 1.2″ of water per 24 hour period; about 0.3″ to 0.8″ of water per 24 hour period; about 0.1″ to 0.3″ of water per 24 hour period; and preferably for an HIZ1 having distance from the structure that is adjacent to HIZ0 (e.g., 5 feet from the structure) and extends out to 30 feet from the structure, 0.25″ of water per 24 hour period.
[0092] After the primary hydration amount is applied, it is preferable that a replenish amount of water is applied to the area or zone, and that this is applied daily during dry conditions, red flag warnings, high fire risk conditions, and combinations and variations of other factors.
[0093] Thus, for HIZ0, for each 24 hour period following the primary hydration, a replenishment hydration amount of: about 1″ of water per 24 hour period; about from 0.3″ to about 0.8″ of water per 24 hour period; about 0.4″ to 0.9″ of water per 24 hour period; and preferably for an HIZ0 having distance from the structure of 5 feet, 0.5″ of water per 24 hour period. These others factors can be received, determined or both from data and information provided to the control system for the EFMS having a hydration plan.
[0094] Thus, Home Ignition Zone 1 (HIZ1), which is adjacent to HIZ0 can have a replenishment hydration amount of: about 0.4″ of water per 24 hour period; about from 0.1″ to about 0.4″ of water per 24 hour period; about 0.10″ to 0.25″ of water per 24 hour period; and preferably for an HIZ1 having distance from the structure that is adjacent to HIZ0 (e.g., 5 feet from the structure) and extends out to 30 feet from the structure, 0.13″ of water per 24 hour period.
[0095] The level of hydration that is maintained in the various zones, e.g., HIZ0, HIZ1, HIZ2, etc. can be measured by Fuel Moisture Content (“FMC”). Fuel moisture content is the percentage of a given fuel's weight, represented by water, based on the dry weight of the fuel. Thus, it is: Percent Moisture Content=Weight of Water/Oven-dry Weight of Fuel×100. It is noted that moisture content can be greater than 100 percent because the water in a fuel particle may weigh considerably more than the dry fuel itself. For example, a green leaf may contain three times as much water as there is dry material, leading to a moisture content of 300 percent. Moisture content of duff and organic soil can be over 100 percent. In embodiments the EFMS establishes and maintains a FMC in HIZ0 from about 100% to about 400%, from about 200% to about 300%, about 100% or more, about 200% or more and about 300% or more. The EFMS establishes and maintains an FMC in HIZ1 from about 100% to 300%, from about 70% to about 150%, about 75% or more, about 100% or more, and about 150% or more. The EFMS establishes and maintains an FMC in HIZ2 from about 25% to 100%, from about 30% to about 50%, about 50% or more, about 60% or more, and about 100% or more. Combination and variations of these established and maintained FMCs may be utilized, as well as, higher and lower amounts.
[0096] Further, the hydration plan, and the hydration plan control commands, can be configured to keep combustibles wet enough so that an ember attach will not ignite them. For example, the ignition point for dry grass and leaves is about 13.6 MJ/m.sup.2, the ignition point for dry cushions and dry fabric (e.g., yard furniture) is about 7.5 to 19.7 MJ/m.sup.2, and the ignition point for dry pine wood is about 18.1 MJ/m.sup.2. The energy from a typical ember attack is about 52.2 MJ/m.sup.2. In general, a preferred hydration plan will keep these materials saturated. The plan will account for hydration time (e.g., about 20 hours for wood to become saturated) amount of water needed for saturation, and evaporation. For example, about 43 gallons/100 sq ft (e.g., 62 inches of water) can be used to keep these materials saturated, under certain conditions. However, it is preferred to have a safety factor and thus use 62 gal/100 sq ft (e.g., 1 inch of water) By saturating these materials, as well as, other materials, their ignition point is raised, i.e., it takes more energy for them to ignite. It requires about 65.9 MJ/m.sup.2 to heat and evaporate 1 inch of water. Thus, when these materials are saturated their ignition points are above the energy from an ember attack, and thus the amber attack will not ignite them. For example, saturated pine wood has an ignition point of 62.6 MJ/m.sup.2, which is well above the 52.2 MJ/m.sup.2 from a typical amber attack Moreover, if the area surrounding the structure is saturated, any spot fires that may occur should be self-extinguishing.
[0097] The control system can receive information about evaporation, calculate evaporation rates based upon data, used historic data, use real time data, and combinations and various of these to determine the amount of water needed in the hydration plan to compensate for evaporation. In extreme conditions materials can lose 0.5 inches of water per day. Typical California summers see water loose from evaporation of about 0.25 inches per day. Thus, the hydration plan can be based upon, e.g., designed to compensate for, these typical evaporation rates, preferably with a safety factor added in, e.g., 50%.
[0098] Embodiments of the hydration plans can limit the flow rate to about 24 gpm. Generally, the hydration plan will provide for periods on operation, e.g., cycles, and then periods on no operation. In embodiments hydration maintenance cycles can use about 2.5 gpm, and initial hydration cycles can use about 5 gpm.
[0099] In an embodiment the primary (e.g., initial) and replenish (e.g., maintenance) amounts of hydration for HIZ0 and HIZ1 are such that there is no need to apply water to HIZ2.
[0100] The data and information about the amount of hydration in the combustibles surround the structure can come from any available source. Moisture sensors can be located around the structure. The moisture sensors and hydration system can be of the type used for agriculture to monitor crops. It can contain moisture sensors located in the ground, or at or near the ground to determine moisture levels, and hydration levels of combustibles.
[0101] The data and information about the amount of hydration in the combustibles can also come from historic data. In this manner hydration levels based upon prior weather conditions can be analyzed and used to predict, and provide a derived hydration levels based upon current conditions. Optical sensors may also be employed to determine hydration level based upon color or visual condition of the combustibles.
[0102] The data and information about the amount of hydration in the combustibles can also come from publicly available sources, such as the depart of agriculture, local fire management systems, and weather and climate services.
[0103] The data and information about the amount of hydration in the combustibles can come from adjacent structures and other monitoring systems.
[0104] The data and information about the amount of hydration, from one, more than one, and all of these as well as other sources, is used by the EMFS for several purposes. The EMFS system, using the hydration plan control commands, can determined the amount of water needed to increase the hydration level in one or more of the areas around the house to an acceptable level. The EMFS can evaluate, one or more of, the amount of available water, predicted weather patterns, fire hazard level and other factors, to determine and implement a hydration plan, e.g., amount, time, duration, and location, of sprinkler usage to obtain an optimum hydration level based upon one or more and all of these factors.
[0105] The evaluation of the hydration data and information, and the formulation of hydration plans can be done by the EMFS systems at a local control and processing system, it can be done by a remote control and processing system, it can be done by a distributed control and processing systems and combinations and variations of these.
[0106] The hydration data and information can also be used by the EMFS system to determine the amount, duration and time of the application of fire suppressions materials, e.g., water, foam, when a fire is detected. In this manner, the minimal amount of fire suppression material can be used that are necessary, based upon hydration data and information, to suppress the fire and protect the structure.
[0107] Turning to
[0108] The fire emergency communication system 100 has several nodes or communication points, each node or communication point having one or more receiving device, monitoring device, transmitting device and combinations and variations of these. There is a node 110 that is associated with a residential area, e.g., a nodal area. There is a node 105 that is associated with a rural area, e.g., a nodal area. There is a node 103 that is associated with an area having access to a limited access highway, e.g., an intersection nodal area. There is a node 104 that is associated with an urban area, e.g., an urban nodal area. Each of these nodes, also has a number of individual nodes within, or associated with them. The individual nodes within a node, form a nodal area, nodes that are mobile can move from one nodal area to another nodal area.
[0109] It is understood, that one, tens, and hundreds of nodal areas, each having one, tens and hundreds of nodes, can be associated with the communication system 100, and network 101. Moreover, multiple networks, such as network 101, can be associated with, or a part of, the communication system 100.
[0110] The number and types of nodal areas may vary, from situation to situation, community to community, from public services team/organization to public services team/organization and may vary before, during and after a wildfire.
[0111] The number and types of individual nodes, in any given nodal area, may vary, from situation to situation, community to community, from public services team/organization to public services team/organization and may vary before, during and after a wildfire.
[0112] In the embodiment of
[0113] Further these nodes may be viewed as sub-nodes of a larger node. For example fire emergency communication system 101 could be included as a sub-node in a larger communication network, having one, tens, hundreds of similar fire emergency communications systems.
[0114] The individual nodes typically and preferably have GUI. They may have associated keyboards, key pads, touch screens, voice control, etc., and combinations and variations of these. The GUI have displays that among other things have graphics for providing information about traffic, fire location, evacuation, evacuation routes, location of gas stations, location of first responders, as well as, the ability to have user input of real time data, e.g., user location, presence of ambers, visibility, proximity to fire, traffic conditions. Preferably, icons, windows or screens are provided on the GUI by an application (app) that is loaded onto a mobile device, such as a smart phone, tablet or vehicle GPS/navigation system. The GUI may also be configured to provide real time, historic, derived, predictive, and virtual data. The GUI may be configured to have private access on the then network to another node on the network. For example, mobile device 140 may have a private communications path with dwelling 112, enabling mobile device to display real time raw data (e.g., images, temperature) of the conditions around dwelling 112 and send instruction to dwelling 112. For example, to activate a fire suppression system for dwelling 112. The monitoring unit of dwelling 112 may also have a processor, or be in communication (control communication) with the processing system to automatically activate the fire suppression system for dwelling 112, sent notifications to mobile device 140 recommending activation of the fire suppression system for dwelling 112, as well as, sending notice that the fire suppression system has been activated. The notices may also be broadcast over the entire network, only to the area where the node or dwelling is located, only to first responders (e.g., emergency services, fire, police, ambulance etc.) and combinations and variations of these.
[0115] The network 101, has several communication pathways. These pathways may be over the same routes, or portions of the network 101, they may share some but not all routes, they may be totally separate, and combinations and variations of these. Each route or pathway may have its own proprietary communication protocol, it may use a publicly available protocol. The protocols may include, but are not limited to CoAP, MQTT, AMQP, WAMP, LoRAWAN, LoRa, IPv4, or IPv6. The communication, e.g., the data and information set over the pathway may be encrypted, protected, or otherwise encoded, such that only an intended recipient can receive it, for example a predetermined recipient, e.g., an individual who has taken the necessary steps to rightfully receive information and data from the data processing assembly 139.
[0116] Each individual node preferably has the ability to receive and transmit data and information. However, a node only needs the ability to receive or transmit data or information. For example, in some embodiments of monitoring stations they may only transmit data and information.
[0117] Turning to the residential area 110, there is shown a schematic representation of an example of a residential area. (The residential area may be a part of, adjacent or far removed from the other areas in the system.) The residential area 110 has street 111. The various node in this area each have communication pathways: dwelling 112 has communication pathway 112a, mobile device 115 has communication pathway 115a, mobile device 116 (which is in dwelling 114) has communication pathway 116a, first responder 117 has communication pathway 117a, school 118 has communication pathway 118a. In addition, dwelling 114 has a private security system that has a communication pathway 114a to a private security provider. As discussed below, such nodes, e.g., 114, can be brought into the system 100, by the private security provider feeding, i.e., providing or transmitting, data and information from its network or customers to the processing system 139.
[0118] Turning to the rural area 105, there is shown a schematic representation of an example of a rural area. (The rural area may be a part of, adjacent or far removed from the other areas in the system.) The rural area 110 has winding, narrow country road 107, a large area 108 (shown by dotted line) that contains significant fuel sources for a wildfire, and power lines 106. The various nodes in this area each have communication pathways: first responder unit 120 has communication pathway 120a, monitoring station 121 has communication pathway 121a, dwelling 122 has communication pathway 122a, cell tower fixed data collection and transmission device 137 has communication pathway 137a, and monitoring station 138 has communication pathway 138a. And, airport 125, which is adjacent to residential area 110 and rural area 105 has communication pathway 125a,
[0119] Turning to the limited access highway area 103, there is shown a schematic representation of an example of a limited access highway and its surroundings. (The limited access highway area may be a part of, adjacent or far removed from the other areas in the system.) The limited access highway area 103 has a multilane limited access highway 131 having multiple on and off ramps, e.g., 132, and a street 130. The various nodes in this area each have communication pathways: monitoring station 136 has communication pathway 136a, mobile device 140 has communication pathway 140a, and first responder 133 has communication pathway 133a.
[0120] Turning to the urban area 104, there is shown a schematic representation of an example of an urban area. (The urban area may be a part of, adjacent or far removed from the other areas in the system.) The urban area 104 has a street 141 that intersects street 142. The various nodes in this area each have communication pathways: traffic camera/red light camera 151 has communication pathway 151a. And a fixed data collection and transmission device (e.g., positioned on or with a cell tower 152) adjacent to the urban area 104, has communication pathway 152a. In addition, business 150 has a private security system that has a communication pathway 150a to a private security provider. As discussed below, such nodes, e.g., 150, can be brought into the system 100, by the private security provider feeding, i.e., providing or transmitting, data and information from its network or customers to the processing system 139.
[0121] Emergency Management (head quarter, command center, etc.) 143, has communication pathway 143a, police department 144 has communication pathway 144a, fire department 145 has communication pathway 145a, ambulance service 146 has communication pathway 146a, and hospital 147 has communication pathway 147a.
[0122] The network 101 has pathway 102 that connects the network to processing system 139 (as shown in greater detail in
[0123] The network 100 can have multiple private pathways. For example, a dwelling can have an external fire protection system that has a control system, sensors, actuators and communication pathway. This external fire protection system has a private communication pathway with processing system 139, as well as, with one or more mobile devices that also connect to processing system 139 and directly or through the processing system to the control system of the dwelling's fire protection system. There may be tens, hundreds or more of these private pathways. As the processing system 139 receives more data and information it can determine if recommendations to start a particular dwelling's fire protection system should be sent, or if the command to start the system should be sent. This can also be done on an area by area basis.
[0124] Thus, for example, the processing system 139 is receiving real time raw data from multiple nodes in the network that provide real time information about, for example traffic patterns, location of fire, speed of fire, direction of movement of the fire, wind speed and direction, humidity, number and location of persons, location of first responders. The processing system 139 also has access to historic data, such as prior weather, prior fire patterns, prior traffic patterns, surveys of fuel sources for the fire, and geographic terrain. The processing system using the real time raw data, and preferably, but not necessarily, the historic data can provide derived data about fire movement, traffic patterns, resource allocation, preferably this derived data can be predictive data. Different forms, and types of this derived data and predictive data can then be transmitted out onto the network to different nodes. For example, the information a mobile device may receive could be limited to the status of a fire suppressions system linked to that device, the proximity of the fire, the predicted path of the fire, traffic and suggested evacuation routes. The information provided to first responders and emergency management HQ could be far more extensive. For example, historic data about the number of dwellings having external fire suppression systems in a particular area, the fuel sources in that area, coupled with real time raw data about the number of people in that area, could be used to determine the placement of first responders, and the need for evacuations.
[0125] Nodes, nodal areas, individual nodes may be organized and configured into various sub-nodes. These sub-nodes can be private or semi-private or public. For example, a company could have a private sub-node for its employees, and within that a sub-node for its fleet of vehicles. Similarly, a school could have a sub-node for its children and parents. A sub-node could include all of the nodes that are external fire management systems, and then have sub-nodes for particular types of system, e.g., by provider, level of services, etc.
[0126] Turning to
[0127] Unit 199 receives and provides information, data and control communication to and from the data processing system 190 to the network 101. Data to individuals is sent along pathways 180 for standard data and content, and along path 181 for premium data and content. For example, standard data may show only public service announcements and other official information from the authorities. Premium data, can show predicted fire movement, number and location of external fire management systems (and their status over time).
[0128] Both of these individual data streams, sets or packets, e.g., data for individuals, travels along pathway 102 of network 101. This data for individuals travels along pathway 102 to a smart phone, tablet, such as an iPad®, a GUI in an automobile (dash display), or other GUI, where one or more of raw data, derived data, adaptive strategy information and predictive data are presented on the display. Thus, for example, data may travel along pathway 181 to pathway 102 to one or more individual pathways (e.g., 113a) or to a nodal area, e.g., 110, or the entire network. The data is then displayed on the GUI associated with the node (e.g., 113) and information may be input into the GUI and then transmitted along the individual pathway to the network pathway 102, to a pathway, e.g., 181.
[0129] The other pathways from unit 199, e.g., pathway 182, 184, 186, etc., are for other custom or special communication or sub-networks. Thus, by way of example, pathway 182 can be for controlled communication for external fire management systems. Realtime raw data, derived data, adaptive strategy information and predictive data may be sent to a user's mobile node, a fixed node on the external fire management system and both. The user can then monitor the information and elect to send a command to the external fire management system to, for example, become read, to operate, or to operate upon a certain set of conditions. The system 139 can send predictive data, e.g., recommending that the external fire management system is activated. The system 139 can also send information, data, or a command to one or more external fire management systems that cause the system(s) to operate.
[0130] In this manner the system 139 can provide derived data and adaptive strategies, to individuals and entire areas, in a direct response to changing fire conditions. This provides the ability to save fire suppression resources (i.e., water, foam) until they are absolutely needed, to use them in the most efficient manner, both on a micro level (each individual system, or structure) and on a macho level, (most efficient use of systems, and activation/operation strategy to protect an area).
[0131] By way of example, pathway 184 can be non-public and exclusive to fire response teams. Pathway 185 can be non-pubic and exclusive to all first responders. Pathway 183 is for communication with network television and social media. This pathway allows specified data and information from the system 139 to be broadcast to a GUI 186, e.g., a TV or computer monitor, on public networks and social medial.
[0132] Generally, the sources for incoming raw data for use in, or to form a basis for, the algorithms and mathematical computations that a processor performs to provide derived data and predictive information and adaptive strategies, can come from various sources, including for example: individual mobile devices (e.g., input from persons, first responders, emergency services, satellites), fixed monitoring devices (e.g., cell tower mounted devices, external fire suppression system, fire services, weather services, traffic monitors, first responders, emergency services, etc.).
[0133] Because of the complexity and unpredictability of wild fires, fire emergency and the reactions of persons, although a single approach may be used, in an embodiment a multi-approach system approach is used, the multi-approach having two, three, four or more approaches performed at the same time to determine a set of approach values for a given event at a given point in the fire emergency. These approach values, e.g., probability of event occurring, are then given weightings based upon their individual accuracy for a particular point in the fire emergency, e.g., rural fire, fire size, population levels, population density in relation to ingress and egress routes, start (activation) of an external fire management system, number of EFMSs in a location, etc. The weighted approach values are then combined to provide a predicted value, i.e, derived data of a predictive nature, such as for example an adaptive strategy, a recommendation to activate a particular EFMS, a warning to evacuate, etc.
[0134] Generally, the EFMS, such as the systems in
[0135] Turning to
[0136] The time T, 325, or provided 326) when the prediction of even 300 is possible to occur is then selected by an individual, e.g., emergency services person, home owner, school principal, etc.
[0137] Weighting factors X, X′, X″ based upon T are then applied to the predicted values 311, 312, 313 to render weighted predicted values 321, 322, 323. Preferably the weighting facts are predetermined 326 for each value of T, or they may be determined based upon predetermined parameters at the time of use. The weight values can be any integer, or fraction. The weighted predictive values 321, 322, 323 are then combined to provide a predicted value 340 for event 300 at time Z, e.g., 80% chance that fire reaches “Shady Acers” in the next 90 minutes. The resulting predicted value 340 is then transmitted to, accessible by and combinations and variations of these a network (e.g, 101) of fire emergency communication system (e.g., 100)
[0138] Turning to
[0139] The statistical approach 401 uses real time raw data, real time derived data and historical derived data in an appropriate probability distribution, such as a gamma probability distribution, beta-binomial probability distribution, standard normal probability distribution, beta probably distributions, or the Dirichlet probability distribution. Thus, for example approach 401 can use current fire position, current humidity, current wind speed, and current wind direction, to project the probability of the fire reaching location A, over a period of time ΔT into the future.
[0140] The time T, 425, when the prediction of even 444 is possible to occur is then selected by an individual, e.g., emergency services person, home owner, school principal, etc.
[0141] Weighting factors X, X′, X″ based upon T are then applied to the predicted values 411, 412, to render weighted predicted values 421, 422. Preferably the weighting facts are predetermined 426 or each value of T, or they may be determined based upon predetermined parameters at the time of use. The weight values can be any integer, or fraction. The weighted predictive values 421, 422 are then combined to provide a predicted value 440 for event 444 at time Z, e.g., 80% chance that fire reaches “Shady Acers” in the next 90 minutes. The resulting predicted value 440 is then transmitted to, accessible by and combinations and variations of these, a network (e.g, 101) of fire emergency communication system (e.g., 100)
[0142] As ΔT becomes larger the uncertainty around probability value 411 increases. Thus,
[0143] The deterministic model approach 402 has higher certainty in predicting events that are not as far out into the future, i.e., smaller ΔT values. In particular the deterministic model approach 402 has greater certainty of its values as larger amount of data are acquired from the fire emergency.
[0144] Other forms of derived data use generalized machine learning algorithms such as Support Vector Machines to predict or classify fire emergency events. These predictions or classifications are forms of derived data. One possible prediction is the probability that a fire will jump a highway or natural barrier. Support Vector Machines may be trained on historical data to create a classifier that can predict the probability that fire will behave in a certain manner.
[0145] Inferential techniques can be used to determine traffic patterns and availability of ingress and egress routes. These techniques would take as input raw data and/or other pieces of derived data. Inference could be performed, for example, via use of heuristics based on traffic pattern knowledge, real time traffic information from waze, google maps etc., or statistical techniques for pattern recognition.
[0146] In some uses, derived and predictive data and virtual data are displayed to users through a client, e.g. a web browser. These data are sent to the client from a server, or from other clients. In some situations, the client will request new data constantly because it is difficult to know if a particular piece of data has been updated. Preferably, the client and/or server is able to determine which data are likely to have changed at a point in time, and therefore prioritize the communication of data that are likely to have changed. This scheme decreases unneeded communication between clients or between clients and servers. The server may determine that particular data are likely to have changed and push that data to the client, or the client may determine that particular data are likely to have changed and request those data from another client or a server.
EXAMPLES
[0147] The following Examples are provided to illustrate various embodiments of systems, devices, methods, and uses and displays of derived, predictive “adaptative strategies and virtual data. These Examples are for illustrative purposes, may be prophetic, and should not be view as, and do not otherwise limit the scope of the present inventions.
Example 1
[0148]
Example 1A
[0149] The controller 580 of Example 1A is in control communication with a hydration plan control commands. These control commands can reside entirely in the controller 590 (e.g., the memory associated with the controller and be executed by the processor in the controller), they can reside in the cloud and be executed by a cloud based processor, they can be distributed between the cloud and the controller 580, i.e., between the cloud and the local controller. The hydration plan control commands provide for the system to operate and implement a hydration plan.
[0150] The hydration plan control commands, and thus the hydration plan which they provide, can be updated, for example, via the cloud, via the network, locally and combinations and variations of these.
[0151] The control system sends control commands to activate and operate the EMFS, sends commands to a local controller to activate and operate the EMFS and combinations and variations of these depending upon the net work and controller configuration. These control commands, among other things, start and stop the operation of the EMFS, thus these commands determine, among other things, the number of cycles, time between cycles, duration of a cycle, as the hydration plan is carried out through the operation of the EFMS. The stop commands, i.e., deactivate and stop operation of the EFMS can be based upon a timer, monitored hydration levels, as well as, other factors.
Example 2
[0152] The EFMS and devices of US Patent Publication 2019/0262637, the entire disclosure of which is incorporated herein by reference, form a node or nodes on the fire emergency communications system. One, two, ten or more structures in an area can have these EFMS.
Example 3
[0153] An emergency management control network and system, e.g., the embodiment of
Example 4
[0154] Turning to
[0155] The anonymous browsing that is accessed through screen 603 can be for example: [0156] Intended to allow a zero-commitment test drive [0157] No account information—uses phone location as a default [0158] All free functionality except: [0159] Only one Push Notification whenever the app is entered in AB mode, a single push notification is sent that illustrates what could be received if signed in with an account (free or otherwise) [0160] Wherever a location is required for functionality, the phone's location is used by default, and the option to enter an address is offered [0161] Whenever any data is entered (address. Group name. Group Members. Follow a news source or fire event, etc.), a reminder is shown stating that no data will be saved for future use unless signed in
[0162] The free version of the application that is accessed through screen 604 can be for example: [0163] Becomes the “trial” version because it offers a ‘taste’ of every premium feature, but there is no expiration [0164] Partial account information—just email address and home address, mobile number [0165] All Premium features with the following limitations: [0166] Only one home location [0167] Only one Emergency Group with only two members [0168] Only 1-2 News sources [0169] Only (2 or 3) Push notifications/month [0170] When any feature limit above is reached, user is presented with option to have more with Premium
[0171] The premium version of the application that is accessed through screen 606 can be for example: [0172] All major features of the app [0173] Complete account information, including payment [0174] No limitations (we may want some limitations on number of groups, members, etc., but high enough that it full capacity is rarely used)
[0175] The system owner version of the application that is accessed through screen 607 can be for example: [0176] All premium features of the application [0177] Plus monitoring, control, and activation of a EFMS
Example 5
[0178] Turning to
Example 6
[0179] Turning to
Example 7
[0180] Turning to
Example 8
[0181] Turning to
Example 9
[0182] Turning to
Example 10
[0183] Turning to
Example 11
[0184] Screens and functionality for a unit functioning as an anonymous user on a node on the network can have access to and show maps, of the area, and these maps can contain information such as fire location, predicted path of fire, location of first responders, evacuation routes, etc. These screens are available to premium users and systems owners, and can also be available to free users.
Example 12
[0185] Turning to
[0186] System 1200 provides an outer coverage zone 1201 that has an outer boundary 1221. The outer boundary 1221 is 30 ft from the walls 1224 of the house. The system 1200 provides an inner coverage zone 1220, that has an inner boundary 1222. Boundary 1222 is 5 ft from the walls 1224. The system 1200 has distribution heads 1202, 1203, 1204, 1205, 1206, 1207, 1208, 1209. When the system is activated, these distribution heads provide foam, water and combinations of foam and water to zone, 1220, zone 1201, and combinations and variations of these zones. The system is installed in a house that has an outer roof line 1203, that extend outwardly from the outer walls 1224, and thereby defines an eave. The zones 1201 and 1220 can be further subdivided into sub-zones. In this manner the system can be operated to provide water, foam, etc. to various sub-zones and combinations of sub-zones.
[0187] In an embodiment the inner boundary 1222 can be about 4 feet or about 3 feet from the walls 1224, as well as, more than 5 ft, about 6 ft, and less than 8 ft from the walls 1224. In an embodiment the outer boundary can be about 25 feet or about 20 feet from the walls 1224, as well as, more than 30 ft, about 35 ft, and less than 50 ft from the walls 1224.
Example 13
[0188] In an embodiment there is provided an EFMS 1300 of the type shown in
Example 14
[0189] Turning to
Example 15
[0190] Turing to
Example 15A
[0191] Either or both of the controllers of Example 15 are in control communication with hydration plan control commands. These control commands can reside entirely in one or both of the controllers (e.g., the memory associated with one of the controllers and be executed by the processor in the controller), they can reside in the cloud and be executed by a cloud based processor, they can be distributed between the cloud and the controllers, i.e., between the cloud and the local controllers. The hydration plan control commands provide for the system to operate and implement a hydration plan.
[0192] The hydration plan control commands, and thus the hydration plan which they provide, can be updated, for example, via the cloud, via the network, locally and combinations and variations of these.
[0193] The control system sends control commands to activate and operate the EMFS, sends commands to a local controller to activate and operate the EMFS and combinations and variations of these depending upon the net work and controller configuration. These control commands, among other things, start and stop the operation of the EMFS, thus these commands determine, among other things, the number of cycles, time between cycles, duration of a cycle, as the hydration plan is carried out through the operation of the EFMS. The stop commands, i.e., deactivate and stop operation of the EFMS can be based upon a timer, monitored hydration levels, as well as, other factors.
Example 16
[0194] Turing to
Example 16A
[0195] Either or both of the controllers of Example 16 are in control communication with hydration plan control commands. These control commands can reside entirely in one or both of the controllers (e.g., the memory associated with one of the controllers and be executed by the processor in the controller), they can reside in the cloud and be executed by a cloud based processor, they can be distributed between the cloud and the controllers, i.e., between the cloud and the local controllers. The hydration plan control commands provide for the system to operate and implement a hydration plan.
[0196] The hydration plan control commands, and thus the hydration plan which they provide, can be updated, for example, via the cloud, via the network, locally and combinations and variations of these.
[0197] The control system sends control commands to activate and operate the EMFS, sends commands to a local controller to activate and operate the EMFS and combinations and variations of these depending upon the net work and controller configuration. These control commands, among other things, start and stop the operation of the EMFS, thus these commands determine, among other things, the number of cycles, time between cycles, duration of a cycle, as the hydration plan is carried out through the operation of the EFMS. The stop commands, i.e., deactivate and stop operation of the EFMS can be based upon a timer, monitored hydration levels, as well as, other factors.
Example 17
[0198] In embodiments the systems, e.g., an EFMS, the second controller of a two controller embodiment, such as the embodiment of Examples 15, 15A, 16, and 16A the servers and processors in the cloud (e.g., API) can perform, require or both, validations before an EFMS is activated to disperse water, foam or both. Thus, if information is received indicating that a fire is near by the structure, this information held, and then validated with other information to confirm the accuracy of the initial information. One, two, three or more validations can be performed before an activation. Because these systems can have a large number of related inputs, the time for this validation will be very short. For example, less than 1 minute, less than 30 seconds, less than 15 seconds, less than 10 second. Moreover, this information can be stored and shared between EMFSs, the API, or other memory devices. This information will be location based. Thus, in this manner, in an embodiment, the validations can take place in even shorter periods and time, and essentially be instantaneous.
Example 17A
[0199] Either or both of the controllers of Example 17 are in control communication with hydration plan control commands. These control commands can reside entirely in one or both of the controllers (e.g., the memory associated with one of the controllers and be executed by the processor in the controller), they can reside in the cloud and be executed by a cloud based processor, they can be distributed between the cloud and the controllers, i.e., between the cloud and the local controllers. The hydration plan control commands provide for the system to operate and implement a hydration plan.
[0200] The hydration plan control commands, and thus the hydration plan which they provide, can be updated, for example, via the cloud, via the network, locally and combinations and variations of these.
[0201] The control system sends control commands to activate and operate the EMFS, sends commands to a local controller to activate and operate the EMFS and combinations and variations of these depending upon the net work and controller configuration. These control commands, among other things, start and stop the operation of the EMFS, thus these commands determine, among other things, the number of cycles, time between cycles, duration of a cycle, as the hydration plan is carried out through the operation of the EFMS. The stop commands, i.e., deactivate and stop operation of the EFMS can be based upon a timer, monitored hydration levels, as well as, other factors.
Example 18
[0202] An embodiment of the present networks and systems can be configured and implemented to manage a hurricane emergency.
Example 19
[0203] In an embodiment, enhancements in speed can be achieved by inter controller communication on the network. For example, one controller can let another controller know that it has activated, and if a second controller lets other controllers know it has been activated, then there is logic that can be applied to activate the controller receiving the activate information. The communication path for communicating between controllers does not need to be via the cloud, but rather through radio communication, such as a LoRa type system, including LoRaWAN®.
Example 20
[0204] An embodiment of an EMFS, systems of Examples 15, 15A, 16 and 16A uses a LoRaWAN® network architecture. In an embodiment this architecture is deployed in a star-of-stars topology in which gateways relay messages between end-devices and a central network server. The gateways are connected to the network server via standard IP connections and act as a transparent bridge, simply converting RF packets to IP packets and vice versa. The wireless communication takes advantage of the Long Range characteristics of the LoRaO physical layer, allowing a single-hop link between the end-device and one or many gateways. All modes are capable of bi-directional communication, and there is support for multicast addressing groups to make efficient use of spectrum during tasks such as Firmware Over-The-Air (FOTA) upgrades or other mass distribution messages.
[0205] In an embodiment the EMFS, for use in this Example, is for instance one of the type of systems of Examples 15 and 16.
Example 21
[0206] An embodiment of the EMFS system has a UPS of the type shown in
Example 22
[0207] Historic, actual, predictive, and derived hydration level data and information, and combinations and variations of these is used to determine the configuration of an EMFS. In this manner the hydration level data and information can form a basis in whole or part, to determine the number and placement of sprinkler heads, the amount of fire suppression material to be stored in the system.
[0208] Predictive hydration level data and information can be used to determined modifications that may be need to existing EMFS, to future, e.g., increased needs of the system to protect the structure. Thus, for example additional sprinkler heads, large capacity storage tanks for foam, could be recommended by the control system, for addition to the system.
Example 23
[0209] Embodiments of the EFMS, including any of the Examples, having one, two, tens, and hundreds, of individual structures and individual EMFS. These systems form a platform as a distributed network and based upon hydration data and information, historic, actual, derived, predicted, and combinations and variations of these, the platform determines optimum strategies for the use of available water to increase hydration levels in a manner that is optimum for the platform.
Example 24
[0210] The embodiments of the EFMS, including any of the Examples provide notifications to individuals, such as on hand held devices, fire crews and emergency management teams. The systems are also configured to receive input and control compunctions from one or more of these groups.
Example 25
[0211] Embodiments of the EFMS, including any of the Examples, are reconfigured and adapted for use with, as a part of, or integrated with, an internal fire suppress systems for the protection of the interior of structures. These internal systems can be integrated with, and preferable are a part of the distributed network of EMFS. The internal systems may rely upon the same source of fire mitigation material as the EMFS for the structure or they may have a completely separate source. Further, there may be a common back up source of fire suppression material that can be used, if needed, by both the EMFS and internal system.
[0212] The internal systems can similarly provide and receive information, communication and control communication from users, e.g., home owner, emergency management personal.
Example 26
[0213] A satellite system is configured to provide information to, and to manage embodiments of the EFMS, including any of the Examples.
Example 27
[0214] A system of drones, alone or in conjunction with the satellite system of Example 26, is configured to provide information to, and to manage embodiments of the EFMS, including any of the Examples.
Example 28
[0215] An EMFS system, including any of the Examples, or a separate system, is configured to provide water, or a cleaning solution, to solar panels. These systems can be installed on individual structures, e.g., solar panels on the roof of a house, or they can be utilized to protect large solar energy farms. These systems can be operation, on a timer, but preferably they are operated based upon fire conditions, for example, ash and particulate density in the air (actual, derived from fire conditions and wind conditions, or both).
Example 29
[0216] Turning to
[0217] A system 1500 having a hydration plan and hydration control commands is associated with a structure 1501 to be protected from wild fire. The structure 1501 has an EFMS. The EMFS system and its hydration plan establishes a first area (Home Ignition Zone (“HIZ”) 0 (zero), i.e., HIZ0) 1502. The distance 1512 for the permitter of HIZ0 1502 from the outer walls of the structure 1501 can be from about 1 to 20 feet, 10 feet or less, 5 feet or less, and preferably the distance 1512 is about 5 feet. It being understood that HIZ0 is adjacent to, and can include the outer surface of, the outer wall of the structure 1501.
[0218] The EMFS system and its hydration plan establishes a second area (HIZ1) 1503. The distance 1513 for the permitter of HIZ1 1503 from the outer walls of the structure 1501 can be from about 5 to 50 feet, 40 feet or less, 30 feet or less, and preferably the distance 1513 is about 25 feet. It being understood that HIZ1 is adjacent to HIZ0 (slight overlap with HIZ0 can occur).
[0219] The EMFS system and its hydration plan establishes a third area (HIZ2) 1504. The distance 1514 for the permitter of HIZ2 1504 from the outer walls of the structure 1501 can be from about 10 to 200 feet, 150 feet or less, 70 feet or less, 60 feet or less, and preferably the distance 1514 is about 50 feet. It being understood that HIZ2 is adjacent to HIZ2 (slight overlap with HIZ2 can occur).
[0220] The system 1500, and area 1504 are configured in part based upon a natural fire break, as shown by river 1550.
Example 30
[0221] Embodiments of the EFMS having hydration plans and hydration control commands, including any embodiments of the Examples having hydration plans, can have and can maintain predetermined condition based hydration levels as shown in Table 1.
TABLE-US-00001 TABLE 1 Hydration levels to be maintained by EMFS (Hydration Level as soil % water content by weight) Minimal Hydration Recommended Optimum hydration level hydration level level HIZ0 10-15% 25% 35+% HIZ1 5%-10% 20-25% 25+% HIZ2 5%-10% 10-15% 20-25% Hydration levels are by way of example and are for high-risk fire conditions
Example 31
[0222] Turning to
[0223] In this embodiment the zones around the structure exactly follow the shape of the structure, including having sharp corners. Thus, the shape, e.g., the foot print, of the zones follow and enlarge, and preferably exactly follow and enlarge, the foot print of the structure.
[0224] A system 1600 having a hydration plan and hydration control commands is associated with a structure 1601a, having an ancillary structure 1601b (e.g., patio, outdoor kitchen, garage) to be protected from wild fire. The structures 1601a, 1601b, have an EFMS. The EMFS system and its hydration plan establishes a first area (HIZ0) 1602. The distance 1612 for the permitter of HIZ0 1602 from the outer walls of the structures 1601a, 1601b, can be from about 1 to 20 feet, 10 feet or less, 5 feet or less, and preferably the distance 1612 is about 5 feet. It being understood that HIZ0 is adjacent to, and can include the outer surface of, the outer wall of the structures 1601, 1601b.
[0225] The EMFS system and its hydration plan establishes a second area (HIZ1) 1603. The distance 1613 for the permitter of HIZ1 1603 from the end of H1Z), can be from about 5 to 50 feet, 40 feet or less, 30 feet or less, and preferably the distance 1613 is about 25 feet. It being understood that HIZ1 is adjacent to HIZ0 (slight overlap with HIZ0 can occur). Thus, the distance for the permitter from HIZ1 from the structure outer walls is typically the sum of distances 1613+1612.
Example 32
[0226] Embodiments of the EFMS having hydration plans and hydration control commands, including any embodiments of the Examples having hydration plans, can provide hydration amounts and rates based upon predetermined conditions, e.g., a wildfire event, as shown in Table 2.
TABLE-US-00002 TABLE 2 Hydration amounts and Timing in Face of Wildfire Event Primary Hydration Replenishment amount Hydration amount HIZ0 1″ over 24 hours 0.5″ per each 24 hours after primary hydration HIZ1 0.25″ over 24 hours 0.13″ per each 24 hours after primary hydration
Example 33
[0227] Embodiments of the EFMS, including any of the Examples, have discrete “scenes” or “modes” hi the controller firmware of the EFMS controller, or in the control system in the cloud, or both, that act according to the exposure of the property, e.g., risk exposure, and then put the hydration plan into action, e.g., implement the hydration plan through the hydration control commands. For example, one mode may be a red flag warning mode, another a utility shutdown, another an evacuation mode, another an imminent fire mode, another a dry fuel moisture seasonal activation mode. There would be others that align with exposure (both real and perceived exposure, as well as, actual, predictive and derived exposure).
[0228] These modes could be triggered manually by selection of the user on their app or at their controller GUI located at the property; they can also be activated automatically by the integrated/network systems control system and software ingesting data (e.g., receiving data and information, whether from push, pull, or combinations of these and other ways of receiving data and information into the control systems) that is relevant to a certain property or properties, and then selecting the appropriate mode of protection; and combinations and variations of these manual and automatic modes. For example, an algorithm, e.g., logic on a controller, is configured such that if data is ingested indicating low fuel moistures for an area, then it can trigger activation of the EFMS in that area (such as at night when it will not interrupt the homeowner). The homeowner can opt into this feature on their app or an insurer or fire service can also opt in on behalf of their portfolio or their service area. The system may run all zones or select certain zones.
[0229] In this manner the use of hydration is coupled with exposure risks based upon actual, historic, predictive and derived data to protect and mitigate the risk to the structure from wildfire.
[0230] Additionally, the identification of the exposure (e.g., risk level, risk factors) and selection of data that is operable for the activation of systems is an embodiment of the present systems and methods. Selecting single or multiple data sources that determine fuel moisture, or fire exposure (ground based, satellite based, actual perimeters, spread modeling of where a fire can travel and expose, weather variables, etc.) are all integral in determining exposure in real time, actual, derived and predictive approaches.
Example 34
[0231] Turning to
[0232] In embodiments, the larger sprinkler patterns cover at least 95%, at least 98%, at least 99% and 100% of the area of HIZ0. In embodiments, the smaller pattern covers at least 98% of the area of HIZ0, at least 99% of the area of HIZ0 and 100% of the area of HIZ0. In embodiments, the larger sprinkler patterns cover at least 95%, at least 98%, at least 99% and 100% of the area of HIZ1. Combinations and variations of these coverages can implement, and can be implemented based upon the exposure of the property, e.g., risk.
Example 35
[0233] Embodiments of the EFMS having a hydration plan, and hydration control commands, including any of the embodiments of the Examples, can be configure for operation in a manner that makes, and maintains, the environment around the structure to be too wet to burn.
[0234] Thus, HIZ0 is five feet from the outer walls of the structure being protected, and has a footprint that follows the footprint of the structure. HIZ1 is adjacent to the outer edge of HIZ0 and extends outwardly therefrom to a distance that is 30 feet from the structure (e.g., HIZ1 starts at 5 feet away from the structure, i.e., adject to HIZ0, and extends 25 additional feet away from the structure). The system has two types of sprinkler heads that provide two patterns, small and large. The small patterns and the large patterns completely overlap over HIZ0, i.e., 100% overlap of HIZ0. The small patterns and the large patterns can also have a 60-70%, or greater, overlap for the entire protected area around the structure.
[0235] In exposures, e.g., risk factor, where ambers are present or likely to be present, a preferred wetting rate of about 1 inch of precipitation in 24 hours is provided to HIZ0I and HIZ1 receives about 0.25 inches of precipitation in 24 hours.
[0236] The system can also be configured to apply 0.75 inches, about 1.25 inches, about 1.5 inches, and about 2 inches, of precipitation per 24 hours to HIZ0. The system can also be configured to apply about 0.5 inches, about 0.75 inches, and about 1 inch of precipitation per 24 hours to HIZ1. Combinations and variations of these precipitation rates are contemplated. For example, depending on conditions and size of the zones, lower HIZ0 rates may be used in conjunction with higher HIZ1 rates. These rates, as well as, combinations and variations of them can also be used in a 3 zone system.
Example 36
[0237] Hydration plan control commands can have one or more different hydration plans. These hydration plans can be implemented by the control system executing the hydration plan control commands, and operating the EMFS to hydrate the zones surrounding a structure.
[0238] The hydration plans can have a series of operation cycles, or cycles, when the EFMS is operating and delivering water to the zones.
[0239] The usage rate of water during operation of a hydration plan can be about 25 gpm during a wetting cycle.
[0240] During fire seasons, before an actual fire event, prewetting hydration plans can be implemented. In these prewetting hydration plans, for example, three to four hydration cycles, i.e., operation of the EMFS to wet the zones, occur 1 to 2 times a week, with each cycle providing about 0.25% the amount of full hydration, e.g., ¼ inch of precipitation in 24 hours, where full hydration is 1 inch in 24 hours.
[0241] Maintenance hydration plans can be used to address evaporation, and in particular during high levels of evaporation. In these maintenance hydration plans, for example, about 6 hydration cycles, i.e., operation of the EMFS to wet the zones, occur in a 24 hours period, with the total wetting of all 6 cycles being about 50% the amount of full hydration, e.g., ½ inch of precipitation in 24 hours, where full hydration is 1 inch in 24 hours.
[0242] During a fire event, e.g., ambers present, active fire within predetermined distance, evacuation order, etc., an in-event soak, or soak, hydration plan can be used. In these soak hydration plans, for example, about 12 hydration cycles, i.e., operation of the EMFS to wet the zones, occur in a 24 hours period, with the total wetting of all 12 cycles being about 100% the amount of full hydration, e.g., 1 inch of precipitation in 24 hours, where full hydration is 1 inch in 24 hours.
[0243] In a preferred embodiment the control system has all three types of hydration plans, and can automatically switch from the operation of one plan to the next based in part of information and data provided to the control systems over the network.
Example 37
[0244] For the implementation of hydration plans, the fire suppression material, which as used in a hydration plan, would be considered the hydration material, can be water, a combination of water and foam, and foam. In a preferred embodiment, during an operating cycle, the hydration material is initially a water foam combination. For example, a 1:400 solution (foam:water by volume) of class A fire fighting foam approved by the USFS. This foam solution helps to break the surface tension of the water to accelerate absorption into vegetation and combustible fuels. The solution is preferably biodegradable, non-toxic, and requires no cleanup. The solution would be delivered preferably during the first ⅓ of the cycle, with the last ⅔ of the cycle being water.
Example 38
[0245] Turning to
[0246] This EMFS has, is in control communication with a control system that has hydration plan control commands, which can be in the controller 1804, in a controller on the cloud, or combinations of these. The control system operates that hydration plan.
[0247] The hydration plan control commands, and thus the hydration plan which they provide, can be updated, for example, via the cloud, via the network, locally and combinations and variations of these.
Example 39
[0248] Turning to
[0249] The manifolds are modular, so that a system can have one, two (as shown), three, four or more modules depending upon the number of sprinkler heads used in the system. This EMFS can perform all of the various functions of EMFS set forth in this Specification.
[0250] This EMFS has, is in control communication with a control system that has hydration plan control commands, which can be in the controller 1804, in a controller on the cloud, or combinations of these. The control system operates that hydration plan.
[0251] The hydration plan control commands, and thus the hydration plan which they provide, can be updated, for example, via the cloud, via the network, locally and combinations and variations of these.
[0252] It is noted that there is no requirement to provide or address the theory underlying the novel and groundbreaking performance or other beneficial features and properties that are the subject of, or associated with, embodiments of the present inventions. Nevertheless, various theories are provided in this specification to further advance the art in this important area, and in particular in the important area of lasers, laser processing and laser applications. These theories put forth in this specification, and unless expressly stated otherwise, in no way limit, restrict or narrow the scope of protection to be afforded the claimed inventions. These theories many not be required or practiced to utilize the present inventions. It is further understood that the present inventions may lead to new, and heretofore unknown theories to explain the operation, function and features of embodiments of the methods, articles, materials, devices and system of the present inventions; and such later developed theories shall not limit the scope of protection afforded the present inventions.
[0253] The various embodiments of networks, systems for providing and displaying data and information set forth in this specification may be used in the above identified fields and in various other fields. Additionally, these embodiments, for example, may be used with: existing networks, emergency systems, social media systems, alert systems, broadcast systems, as well as other existing equipment; future systems and activities; and such items that may be modified, in-part, based on the teachings of this specification. Further, the various embodiments set forth in this specification may be used with each other in different and various combinations. Thus, for example, the configurations provided in the various embodiments of this specification may be used with each other. For example, the components of an embodiment having A, A′ and B and the components of an embodiment having A″, C and D can be used with each other in various combinations, e.g., A, C, D, and A. A″ C and D, etc., in accordance with the teaching of this Specification. The scope of protection afforded the present inventions should not be limited to a particular embodiment, configuration or arrangement that is set forth in a particular embodiment, example, or in an embodiment in a particular Figure.
[0254] The invention may be embodied in other forms than those specifically disclosed herein without departing from its spirit or essential characteristics. The described embodiments are to be considered in all respects only as illustrative and not restrictive.