CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No.

62/412,978, filed October 26, 2016, the entirety of which is hereby incorporated by reference into the present application.

FIELD OF TH E INVENTION

[0002] In various embodiments, the present invention generally relates to tools, techniques, and algorithms for assessing liquid spill risk for areas in which liquids are stored. In more specific embodiments, the present invention relates to assessing and quantifying spill risk for an area or facility in which containers of liquid have been stored.

BACKGROUN D

[0003] Many commercial enterprises employ a variety of liquids in their processes and operations. For example, entities in the manufacturing, fuel distribution, and chemical plant sectors may use many different kinds of liquids in their industrial processes. Proper spill management for liquids and their storage containers is crucial for these enterprises, especially with respect to hazardous or toxic liquids which may require special precautions and careful handling. Spilled liquids can cause harm to personnel, damage to property and equipment, and adversely impact a company from financial and legal liability perspectives.

[0004] However, many facilities have no defined, unified view of the risks represented by a given liquid storage area, let alone across an entire facility or across multiple storage facilities within an organization. Even the most engaged and sophisticated facilities typically rely on a few "rule of thumb" guidelines to benchmark

spills. Unfortunately, such guidelines have limited applicability and even when consistently applied can often cause more harm than good. For example, a facility might perform a test by spilling a five-gallon bucket in its parking lot, measuring a ten-foot radius spread for the liquid, and then creating a liquid spill guideline that every gallon of the liquid spreads two feet. While that may be approximately true for a five-gallon bucket, applying the same guideline to a 275-gallon intermediate bulk container (IBC) could result in a spill radius which is incorrectly and excessively inflated. Because many facilities do not have the resources, knowledge, or inclination to apply advanced mathematics to their spill risk assessments, they instead may inappropriately apply flawed guidelines or ignore the risks altogether.

[0005] Even with regard to sophisticated facilities who possess an enhanced understanding of their liquid spill risks, staging even a benign test spill of a "harmless" liquid like water may be infeasible because of delicate electronics or equipment, the potential for slip and fall injuries, production downtime, and cleanup labor/materials. Usually the higher risk spill areas in a facility are also of higher commercial significance, and thus are often the most difficult in which to stage practical experiments or test spills.

[0006] These issues are further compounded by the fact that federal, state, and local laws and regulations are often loosely defined yet can have significant potential negative legal and financial impacts on the facility. For example, within the text of certain regulations facilities must follow with regard to spill kit preparedness, ambiguous terms such as "sufficient quantities" or "in areas where spills, leaks or ruptures may occur" are

used. Because there may be no logic, calculation, table of acceptable values, or other objective measures to gage compliance, the laws and regulations are typically open to significant interpretation by facility management which can expose the company to significant legal liability.

[0007] In view of the above problems, what are needed are enhanced tools, techniques, and algorithms which can provide an analytical framework by which facilities can evaluate the risks associated with whether an area is realistically and competently prepared for a liquid spill in the area.

SUMMARY

[0008] Tools, techniques, and algorithms are provided which reflect an analytical framework and logical approach by which facilities can evaluate the risks associated with their liquid storage areas. In various embodiments, an algorithm can be used to perform a spill risk assessment and to generate an improvement path in the response to the assessment. The results of the risk assessment can be translated into physical changes to transform the storage area to reduce future spill risk. [0009] In one embodiment, a method is provided for assessing spill risk in a liquid storage area having at least one liquid storage container stored therein. The method may involve receiving input data associated with a largest capacity liquid storage container stored in the area; applying, with a processor of a computer system, a computer- implemented algorithm programmed for: calculating a spill reach value for the largest capacity container, and calculating at least one risk facet value associated with the area; and outputting, by the processor, a risk assessment summary associated with at least the calculated spill reach value and the calculated risk facet value.

[00010] The method may comprise determining, by the processor, an improvement path in response to the calculated spill reach value and the calculated risk facet value; and, physically modifying at least a portion of the liquid storage area in response to at least a portion of the determined improvement path. In certain

embodiments, the method may further comprise calculating multiple spill reach values for the largest capacity container in response to multiple surface slopes. In one aspect, the algorithm may be programmed for calculating the spill reach value for the largest capacity container in response to a type of fluid. In various embodiments, the risk facet value may include one or more of an area drain risk value, area liquid risk value, response pressure value, a spill kit capacity value, a spill kit distance value, a spill kit visibility value, a blocker distance value, a blocker visibility value, a drain condition determination, or combinations thereof.

BRIEF DESCRIPTION OF THE FIGURES

[00011] FIG. 1 includes an example of a process flow diagram for performing a spill risk assessment in accordance with various embodiments of the invention.

[00012] FIG. 2 schematically displays an example of a liquid storage area.

[00013] FIG. 3A and 3B include examples of input data capture worksheets.

[00014] FIG. 4 illustrates an example of an output screen representing a spill risk assessment performed in connection with the area of FIG. 2.

[00015] FIGS. 5A, 6A, 7A, 8A and 9A include a tabulation of input data and calculated values associated with various liquid storage areas. [00016] FIGS. 5B, 6B, 7B, 8B and 9B include output screen displays illustrating results connected with the calculated values associated with FIGS. 5A, 6A, 7 A, 8A and 9A

(respectively).

[00017] FIG. 10 includes an example of an output screen associated with a fueling and rail area.

[00018] FIG. 11 illustrates an example of an online version of an output screen having numerical risk ratings associated with various risk facets.

[00019] FIG. 12 illustrates an example of an output screen associated with a parts washer area in a building.

[00020] FIGS. 13 and 14 illustrate example output screens associated with developing improvement paths for certain examples of liquid storage areas.

[00021] FIG. 15 includes an example of an output screen associated with developing improvement paths with a particular liquid storage area, including a numerical count of risk facets both before and after the improvement path has been implemented.

[00022] FIG. 16 schematically displays physical transformations and modifications to the storage area of FIG. 2 after an improvement path has been implemented.

[00023] FIG. 17 includes an example of a computer system architecture in which various input data, calculations, and algorithms can be executed in association with various spill risk assessment embodiments described herein.

DESCRIPTION

[00024] The inventors have developed enhanced tools, techniques, and algorithms which can provide an analytical framework and logic by which facilities can evaluate the risks associated with whether an area is realistically and competently prepared for a spill involving liquid stored in the area. In various embodiments, the invention satisfies long felt needs in the industry by addressing problems that have plagued the industry for an extended period of time.

[00025] For example, embodiments of a spill risk assessment algorithm described herein can significantly alleviate or resolve many issues in different kinds of facilities which employ liquids in their operations. In one aspect, the algorithm creates a developed, robust, and universal view of spill-related risks. By building on a physics-based model for liquid spills occurring at a facility, the algorithm provides a measured and measurable view of spill-related risks. Prior to the development of this algorithm, facilities had no defined, unified view of the risks represented in a given liquid storage area, let alone across an entire facility or across multiple facilities within the same enterprise.

[00026] The algorithm can reduce or eliminate the practice of rough estimation or "rule of thumb" type guidelines for assessing spill behaviors. Because many facilities do not have the time, knowledge, or other resources necessary to apply advanced mathematics to liquid spill assessments, they instead apply flawed guidelines or ignore the risks altogether. The algorithm also allows for acquiring knowledge of spill behavior in areas where staging a controlled spill is infeasible and/or dangerous. Using the present algorithm can take the place of or supplement performing spills tests where even "harmless" liquids such as water can cause significant damage to equipment or risk of injury to employees.

[00027] In addition, the algorithm can be used to develop tactical and specific knowledge to help facilities comply with otherwise vague local, state and federal environmental rules, regulations, and laws. Therefore, use of the algorithm can assist a facility with reducing negative impact in the form of adverse financial consequences or legal liability.

[00028] In various embodiments, the algorithm reflects objective tools and techniques which facilities can use to evaluate if a liquid area is adequately prepared for a spill of its comparatively largest container. The algorithm can also be used to improve a liquid storage container area and to develop a coherent approach to spill response preparations. The algorithms and tools described herein can be embodied as computer- implemented instructions stored on a mobile device, smartphone, desktop computer system, tablet, laptop, or other computing device. In one example, an algorithm can be used to calculate spill related risks associated with a liquid container storage area. In certain embodiments, spill related risks may be assessed in connection with a number of available emergency spill kits or spill response kits, for example, among other aspects of a given liquid storage area.

[00029] FIG. 1 illustrates one example of an embodiment of a method for assessing liquid spill risk within an area of interest in accordance with various embodiments of the present invention. FIG. 2 schematically illustrates an example of a storage area 202 which can be analyzed by a risk spill assessment algorithm. In the example shown, the area 202 includes a liquid storage container 204 which has been determined to be the comparatively largest single container (e.g., by capacity or volume) within the area 202, for example. The area 202 further includes a drain 206 (e.g., storm drain) which may connect to a sewer system external to the area 202. A spill kit 208 can be provided in the area 202 to allow personnel in the area 202 to address a spill event involving liquid the container 204, for example. Also, a drain blocking device 210 can be provided to cover or seal the drain 206 during a container spill event.

[00030] At step 102, various input data associated with the storage area 202 can be captured or collected by an analyst or measurement device, for example. FIG. 3A illustrates one example of a data capture worksheet which can be used to capture input data for the area 202. FIG. 3B illustrates a different example of a data capture worksheet which can be accessed online through a computer or computing device, for example. As shown, the area 202 may be given a name 302 or other identifier at step 102A, and one or more photos or other images associated with the area 202 can be captured. In certain embodiments, one or more standardized names may be used to classify areas and facilities to facilitate perform meta-analysis across multiple facilities.

[00031] At step 102B, the types of liquids 304 stored in the area 202 (e.g., represented as variables TYPi, TYP2, TYP3, etc.) may be recorded. The type of liquid may be defined and categorized from a variety of different liquids, such as water-based; oils, oil- based; flammables; fuels; corrosives; oxidizers; aromatic solvents; as well as another flexible class for other kinds of liquids (e.g., "Others"). Those skilled in the art can appreciate that an analyst may determine the best fit for liquid type designation for the given liquid or liquids stored in the area 202.

[00032] At step 102C, a capacity 306 of the largest container (LRG _CU rrent) in the area

202, when there are multiple containers in the area 202, can be determined. The capacity 306 may be quantified as a volume (e.g., gallons or liters), for example. Collection of capacity data 306 recognizes that if the largest capacity container 204 is spilled in a worst- case, realistic scenario, then this container 204 would result in the largest spill radius, which is of primary consideration in understanding and calculating risks. Calculated spill radius derived from this largest volume container 204 plays a significant role in understanding risks and problem resolutions throughout the processing of the algorithm (see below).

[00033] At step 102D, a distance from liquid area to kit ( DTK _CU rrent) value 308 between the container 204 and the nearest spill kit 208 can be measured and recorded. This input data captures how far away the nearest emergency spill response supplies are from the location of the liquid stored in the container 204. Related calculations evaluate the accessibility of these essential supplies in the event of a liquid spill event.

[00034] At step 102E, a value for absorbent capacity of nearest spill kit (SKC _CU rrent) can be recorded. This input allows for the effective understanding of observed in situ spill kit absorbent capacity and its suitability given the risks and settings in the liquid storage area

202.

[00035] At step 102F, a distance from liquid area to drain/escape (DTD _CU rrent) value

310 between the container 204 and the nearest drain 206 can be measured and recorded. This input data captures how far away the nearest potential escape point for liquid is from the liquid storage container 204. This data represents a point where, if the liquid reaches the drain 206, then the spill will be unrecoverable or challenging to clean up, and the spill will likely involve regulatory penalties and/or significant cost or complexity to resolve.

[00036] At step 102G, a distance from drain to blocker (DTB _CU rrent) value 312 between the container 204 and the nearest drain blocker 210 can be measured and recorded. This input data captures how far away the nearest drain sealing device is from the drain. This distance is important because it is used to calculate how quickly and adequately a drain could be sealed in the event of a spill that could potentially reach the drain.

[00037] Input data processed by the various methods and algorithms described herein can be entered manually by an operator, downloaded from an external data source, and/or can be collected automatically by one or more types of sensors, measurement tools, or other devices programmed to capture or collect the input data. In certain embodiments, input data may represent a digital or informational transformation of a state, dimension, quality, or other aspect of a physical object or tangible article. In the process of collecting input data for use by a spill risk assessment algorithm, a variety of devices or equipment may be used. For example, a digital camera of sufficient resolution can be used to provide different images or viewpoints of a liquid storage area. For example, and as described below in more detail, a camera can be used to capture specific visual information and vantage points necessary for an analyst to derive values for spill kit obstruction factor, spill Kit visibility, blocker obstruction factor, and blocker visibility. A laser measure with supplemental means of targeting in addition to the laser trace can also be used to obtain distance measurements, for example. Distances in a facility may vary significantly, ranging from a few feet to hundreds of feet, which makes laser-based measurement devices desirable for collecting data. Furthermore, the laser can be used to qualitatively evaluate the number of obstructions along a straight path, and the presence of such obstructions may be used to modify distance values. The supplemental means of targeting can be helpful, as many of the storage areas are outdoors and in bright sunlight, for example, where observing the laser trace over longer distances can be challenging, even with special laser glasses. For this reason, in certain embodiments, a device comprising a laser-aligned camera and crosshair with variable zoom can be used to show precisely where a

measurement is being taken. This function can be useful for measuring along horizontal surfaces (e.g., an outdoor storm drain in a parking lot), as it can be difficult to place a conventional laser trace accurately.

[00038] Those skilled in the art can appreciate that the absence of one or more pieces of input data (e.g., an area where there is no drain 206, or in which the drain 206 may be self-contained, dumped, or trapped) can affect the processing of the risk spill assessment algorithm (see below), which may result in excluding a corresponding risk facet from the analysis (e.g., "N/A" may appear as the corresponding risk phrase for "Drain Condition").

[00039] At step 104, the input data collected at step 102 can be input into a computer-implemented risk spill assessment algorithm, which calculates various risk facet values associated with potential liquid spill risks in the area 202.

[00040] At step 106, an initial calculation for spill reach can be calculated for the largest capacity container 204. In certain embodiments, a spill class is applied to the overall algorithm, depending on the size of the largest container 204. This spill class allows for more specific fine tuning of the underlying algorithm and its output results. Spill class embodies the knowledge that comparatively smaller containers of liquid can behave differently from comparatively larger liquid containers. [00041] For the spill reach calculation, the algorithm may calculate multiple reaches

(e.g., radii) of a spill of the largest liquid container 204 as positioned in the area 202. These multiple radii may be based on hypothetical spills on surfaces of zero, one, and five degrees of slope, for example, and may account for the permeability of the underlying substrate (e.g., impermeable sealed concrete vs. permeable soil). Unless a specific liquid type is specified, the base case is that the algorithm uses the physical characteristics of mineral oil as the spilled liquid, as mineral oil reflects common center-lined characteristics of the types of liquids used and spilled in facilities. For example, mercury has notably different physical characteristics, but as a practical matter is usually never spilled in quantity.

[00042] The algorithm has the capability to calculate spill reach given a change in various physical characteristics. For high-tolerance applications, these physical

characteristics can be modified to reflect the actual liquid used in the examined area. It can be seen that various risks calculated by the algorithm can be derived from the calculation of multiple spill reaches which can be used in different capacities to bound risks.

[00043] With regard to step 106, calculate initial spread time TV _S = .023462*((Gravity at sea level, as ft./sec ^A 2)*(Volume of largest container/spill, as gal)*(Density of liquid, as lb./ft ^A 3)/(Surface tension of liquid, as dyne/cm). Then calculate L.2 = ((Surface tension of liquid, as dyne/cm)* (Volume of largest container/spill, as gal, LRG _CU rrent)*(lnitial spread time, TV _s )/(Viscosity of liquid, as centipoise)) ^A l/4. Next, calculate maximum spill diameter (spill reach) on flat surface, SDo = ((L2)* 1.413142)*2. Then calculate spill reach on flat surface using margin of safety coefficient, CSDo = (SDo)*2; calculate spill reach on one-degree incline, CSDi = (CSDo)*2.4; and, calculate spill reach on five-degree incline, CSD5 =

(CSDo)*3.2.

[00044] At step 108, the algorithm can be programmed to calculate various risk facets associated with the area 202. These risk facets 108 include, for example and without limitation, calculated or determined values associated with area drain, area liquid, response pressure, spill kit capacity, spill kit distance, spill kit visibility, blocker distance, blocker visibility, and drain condition.

[00045] At step 108A, an area drain risk facet calculation can be performed. This facet value is the expansion of the previously calculated spill reach on one-degree incline (CSDi) as compared to the distance from the liquid area to the nearest drain or escape point ( DTDcurrent)- This facet 108A represents the risk that a spill of the largest volume container 204 in a given area 202 could reach the nearest drain 206 or escape point if unimpeded by responders. First, calculate initial area drain risk distance coefficient, ADRdc =

( DTDcurrent)/CSDi with theoretical minimum is set at 0. Next, apply logic evaluation of ADRdc on an area drain risk spectrum to generate an area drain risk phrase. In order to create a risk spectrum which is useful, the function assigns risk levels based on tiers of ADRdc values, including the following examples of ADRdc values which can be assigned to a corresponding area drain risk phrase:

ADRdc of O to .167, "Critical" ADRdc of .168 to .334, "Very High" ADRdc of .335 to .501, "High" ADRdc of .502 to .668, "Elevated" ADRdc of .669 to 1, "Moderate" ADRdc of 1.01 and above, "Lower"

[00046] Next, step 108A may solve for distance from liquid area to nearest drain/escape to reach a "Lower" area drain risk level. Because a key output of the algorithm is to create specific, prescriptive, physical improvements to an area, a minimum distance from liquid area to nearest drain/escape can be calculated to achieve the "Lower" area drain risk phrase (DTDLower), wherein DTDi_ ₀ wer = 1.01*CSDi.

[00047] At step 108B, an area liquid risk facet calculation can be performed.

Categorically, there are a few factors at play when determining the risks presented by the liquids in a given area: danger to personnel and settings presented by a single type of liquid by itself; multiple types of liquids representing additional complexity within a class of liquids (e.g., multiple types of liquids within the class "Corrosives" in a given liquid area); and, the added complexity and danger represented by an area containing multiple and distinct classes of liquids, each requiring a specific and unique response. Calculating the area liquid risk facet 108B may first involve compiling types of liquids. For each type of liquid noted (e.g., TYPi, TYP2, TYP3, etc.), assign a corresponding value of 1. Next, compile types of liquids into larger classes and capture in-class response difficulty (i.e., ICD), a coefficient reflecting the relative complexity of responding to a spill of that liquid class, when considered in isolation. For example, responding to a single water-based spill is relatively straightforward compared to a spill of a corrosive, due to the added dangers, incompatibilities, and specialized supply selection required to respond to a corrosive spill:

[00048] Then, as part of step 108B, total class complexity (TCC) can be compiled. TCC is a coefficient reflecting the compounded complexity a responder would face when responding to a spill of an as-yet unidentified liquid, which could conceivably be of any of the classes of liquids within an area. For example, two commonly used liquids in industry are water and sulfuric acid. If those two liquids are used in the same area, there is significant personnel risk resulting from those liquids being confused, as they are both clear and relatively odorless. The potential for confusion of two liquid classes is further compounded in the case of large spills presenting high mental pressure or cognitive load, which can be accounted for in the response pressure risk facet (see below). Examples of TCC values include the following:

Number of Liquid Classes TCC

present 2 1.4

3 1.8

4 2.2

5 2.6

6 3

Next, step 108B may involve calculating an area liquid risk coefficient as follows: ALR _C = TCC* ((ICDi*TYPi)+( ICD2*TYP2)+( ICD3*TYP3)+(ICD4*TYP4)+(ICD5*TYP5)+(ICD6*TYP ₆ )). Logic evaluation of ALR _C on an area liquid risk spectrum can be performed to create an area liquid risk phrase. Examples of ALR _C values and their corresponding area liquid risk phrases include the following:

ALRc of 45 and above, "Critical" ALRc of 30 to 44.99, "Very High" ALRc of 10 to 29.99, "High" ALRc of 3 to 9.99, "Elevated" ALRc of 2 to 2.99, "Moderate" ALRc of 1 to 1.99, "Lower"

[00049] At step 108C, a response pressure risk facet calculation can be performed.

Because the algorithm can be used to model the risks present before and during spill response for a given liquid area, the human factor is significant. Response pressure is a synthesis of area drain risk (ADRdc) and Area Liquid Risk (ALR _C ), indexing and normalizing each to a 100-point scale, as they use separate coefficient scales in their respective calculations. Response pressure reflects the further compounded risk represented by liquids more dangerous to personnel being located at distances closer to drains. This reflects the reality that as liquids are more likely to reach a drain (ADRdc), personnel have less time to respond and experiences higher cognitive load and stress. If personnel have little time to respond, and there are multiple classes of harmful liquids in the area (ALR _C ), this represents high potential for personnel to misidentify a dangerous liquid while under time pressure.

[00050] To calculate the response pressure risk facet at step 108C, a risk pressure coefficient (RPc) can be calculated as follows: RP _C = (100*(ALR _c /45)+((l-ADR _dc )* 100). Next, logic evaluation of RP _C can be performed to create a response pressure risk phrase RP _C as follows:

RPc of 175 and above, "Critical" RPc of 117 to 174.99, "Very High" RPc of 47 to 116.99, "High" RPc of 6.60 to 46.99, "Elevated" RPc of O to 6.59, "Lower"

[00051] At step 108D, a spill kit capacity risk facet calculation can be performed. This facet considers the ability of the nearest spill kit to absorb and retain a spill of the largest container in a given area. It also accounts for higher area drain risk requiring marginally higher absorbent capacity, such as when responders are faced with high pressure and little time, absorbent placement may be neither optimal nor perfectly efficient. As part of step 108D, logic evaluation of spill kit absorbency (SKA _C ) for area drain risk (ADRdc) can be determined as follows:

ADRdc risk SKAc

phrase

"Critical" 1.2

"Very High" 1.1

"High" 1.05

"Elevated" 1

"Moderate" 1

"Lower" 1

[00052] Next, a spill kit absorbency coefficient (SKC _C ) can be calculated as SKC _C =

(SKCcurrent/LRGcurrent)/SKA _c . Logic evaluation of SKCc on a spill kit absorbency spectrum can be performed to create a spill kit absorbency risk phrase, examples of which follow:

SKCc of 1.001 and above, "Excellent" SKCc of .751 to 1.00, "Very Good" SKCc of .501 to .750, "Good" SKCc of .301 to .500, "Borderline" SKCc of 0 to .300, "Not Acceptable"

[00053] At step 108E, a spill kit distance risk facet calculation can be performed. This facet considers the realities of spill kit placement, and how near a liquid area a spill kit should be in order to respond effectively to a spill of the largest container. This facet also takes into account two additional factors. First, it builds on five distinct spill classes, as the relationship between the volume of the largest container in an area (LRG _CU rrent) and distance to spill kit (DTKcurrent) is not linear. For example, a lab area with a one-liter largest container realistically can locate a very small spill kit a variety of places in that lab. In the case of a

20,000-gallon tank, however, the ratio of volume to distance needs significant adjustments to account for the far larger scale of spill and facility. Second, as response pressure (RP _C ) increases, the spill kit distance reduction coefficient (SKD _rc ) also increases. This reflects that in areas with high response pressure, spill kits should be located more closely to the liquid area. This also reflects the reality that in high pressure spill response situations, having a spill kit easily seen and accessed becomes an increasingly important aspect of effective spill response.

[00054] As part of the assessment performed at step 108E, an analyst may view photographs of the spill kit in situ, as taken from the liquid area, and select from predetermined descriptors to characterize the path between the liquid area and the spill kit. The selection is then assigned a corresponding spill kit obstruction factor (SKO), examples of which are as follows:

[00055] Next, DTK _CU rrent can be adjusted using the SKO to generate a more accurate adjusted distance to spill kit value (DTKadj). Because these distances affect the time required by personnel to respond to a spill, it is useful to take them into consideration. For example, a spill kit 30 feet away with a clear line of site from the liquid storage container 204 is more likely to be remembered and utilized effectively in spill response than a spill kit which is 30 feet away that is located in another storage area. In this example, DTKadj =

( DTK _C urrent)* (SKO). Also, logic evaluation of a spill kit distance reduction coefficient (SKD _rc ) can be performed to generate a response pressure risk phrase (RP _C ), such as the following: RPc risk phrase SKDrc

"Critical" .3

"Very High" .15

"High" .10

"Elevated" .05

"Lower" 0

[00056] Also, as part of step 108E, a spill kit distance coefficient can be calculated as

SKDc = (1-MSKc )*(( DTKadj /((l-SKDrc)*CSD ₀ )). In the presence of a one-person mobile spill kit, MSKc can be .1, otherwise it may be zero. In certain embodiments, spill class distance coefficient SKD _c or SKDad _j can be evaluated according to the nearest fit based on the capacity of the largest container 204 (LRG _CU rrent) to designate a spill kit distance risk phrase as follows:

[00057] At step 108F, a spill kit visibility risk facet can be calculated. This facet may rely on analyst evaluation of the visibility of the spill kit, but does not need to rely on the subjective evaluation of the analyst. This calculation employs a photograph taken of the spill kit in situ, from which the analyst reports various points or angles of visibility. The analyst views the photograph of the spill kit in situ, as taken from the liquid container 204 location, and selects from pre-determined descriptors for what is seen. The selection is then assigned a corresponding spill kit visibility score (unadjusted), SKV _un , as follows:

[00058] In certain embodiments, a logic evaluation can be performed to derive spill kit visibility adjusted for response pressure (SKVadj). In cases of elevated response pressure, the algorithm may require increased visibility to achieve the same spill kit visibility risk phrase. For example, an area with a "Critical" level of response pressure might be required to have a spill kit that is more easily visible than a similar area with an "Elevated" response pressure, as responders might be assumed to be more likely to overlook a nearby kit in times of high stress or duress. Examples of values for SKVadj are shown in the table below:

[00059] Also as part of step 108F, logic evaluation of SKV _a dj on a spill kit visibility risk spectrum can be performed to generate a spill kit visibility risk phrase (SKV _C ), as shown in the following examples:

[00060] At step 108G, a blocker distance risk facet can be calculated. This facet considers the realities of drain blocker/drain sealing apparatus 210 placement, and how near a drain 206 a blocker 210 should be in order to respond effectively to a spill of the largest container 204. This facet may consider additional factors. First, it can build on five distinct spill classes, as the relationship between the volume of the largest container in an area (LRG _CU rrent) and distance from drain to blocker (DTB _CU rrent) is not linear. Second, as Response Pressure (RP _C ) increases, the drain blocker distance reduction coefficient (DTB _rc ) also increases, reflecting that in areas with high response pressure, blockers should be located more closely to the drain in a liquid storage area. This reflects the reality that in high pressure spill response situations, having a drain blocker easily seen and accessed becomes an increasingly acute and significant benefit.

[00061] As part of the processing at step 108G, an analyst may view a photograph of the blocker in situ, as taken from the drain 206 or escape point, and then select from predetermined descriptors to characterize the path between the drain 206 and the blocker 210. The selection is then assigned a corresponding blocker obstruction factor (BO), examples of which are as follows: User selection based on level BO

of obstruction between

drain/escape point and

blocker

"Completely clear, line of 1

sight"

"One obstruction or an aisle" 1.1

"A few obstructions, 1.2

somewhat straight path"

"Highly obstructed" 1.5

"In a separate area or behind 2

doors"

DTBcurrent can be adjusted by using the BO to result in the more accurate adjusted distance to spill kit value (DTB _a d _j ). Because these distances affect the response time of personnel during a spill event, it is useful to take them into consideration. This adjustment can be calculated as DTBad _j = (DTB _C urrent)*(BO). Next, logic evaluation of blocker distance reduction coefficient (DTBrc) in connection with generating a response pressure risk phrase (RP _C ), as shown in the following examples:

[00062] A blocker distance coefficient (DTB _C ) can be calculated as DTB _C = DTB _a dj/((l-

DTB _rc )*CSDo)). Logic evaluation can be performed for DTB _C or DTBadj according to the nearest fit based on capacity of largest container (LRG _CU rrent) to designate a blocker distance risk phrase, as shown in the following examples: LRGcurrent of LRGcurrent of LRGcurrent of LRGcurrent of LRGcurrent of up to 5 5.01 to 55 55.01 to 330.01 to 2000.01 to gallons gallons 330 gallons 2000 20000 gallons gallons

"Excellent" 0 to 1 DTBc O to .5 O to .25 O to 20 O to 10

DTBc DTBc DTBadj DTBadj

"Very Good" 1.01 to 1.5 .501 to .7 .251 to .35 20.01 to 40 10.01 to 20

DTBc DTBc DTBc DTBadj DTBadj

"Good" 1.51 to 2.5 .701 to 1 .351 to .45 40.01 to 50 20.01 to 30

DTBc DTBc DTBc DTBadj DTBadj

"Borderline" 2.51 to 4.2 1.01 to .451 to .7 50.01 to 75 30.01 to 40

DTBc 1.68 DTBc DTBc DTBadj DTBadj

"Not 4.201 and 1.681 and .701 and 75.01 and 40.01 and

Acceptable" above DTB _C above DTB _C above DTB _C above above

DTBadj DTBadj

[00063] At step 108H, a blocker visibility risk facet calculation can be made. While this facet may rely on analyst evaluation of the visibility of the blocker, it does not necessarily rely on subjective evaluation by the analyst. This calculation may be based on a photograph taken of the blocker in situ, from which the analyst reports points or angles of visibility. The analyst may view the photograph of the blocker in situ, as taken from the drain/escape point, and then select from pre-determined descriptors for what is seen. The selection is then assigned a corresponding Blocker Visibility score (unadjusted), BV _un , examples of which are as follows:

"Clear visibility from 2 4

points"

"Clear visibility from 1 point" 3

"Partial visibility from 1 2

point"

"No visibility" 1

[00064] Next, logic evaluation can be performed to derive blocker visibility adjusted for response pressure (BVadj). In cases of elevated response pressure, the algorithm may require increased visibility to achieve the same blocker visibility risk phrase. For example, an area with a "Critical" level of response pressure might be required to have a blocker that is more easily visible than a similar area with an "Elevated" response pressure, as responders may be assumed to be more likely to overlook a nearby blocker in times of high stress or duress. Examples of BVadj are shown in the following table:

[00065] Logic evaluation of BVadj can be performed on a blocker visibility risk spectrum to generate a blocker visibility risk phrase (BV _C ), as follows:

[00066] At step 1081, a drain condition risk facet may be determined. This may be a subjective, non-calculated facet based on the analyst's experience to judge the likelihood of a urethane panel to be able to cover and seal the drain 206 as shown in the photograph. This judgment may be based on the smoothness and uniformity of the surface surrounding the drain 206 grate, for example, as this is the sealing interface for many commonly available drain sealing or spill diverting solutions.

[00067] At step 110, a summary of the various risk facet calculations and

determinations made in accordance with step 108 can be aggregated and displayed on an output screen. FIG. 4 illustrates an example of an output screen representing a spill risk assessment performed in connection with the area 202 shown in FIG. 2.

[00068] Further examples of input data, calculations, and determinations of spill risk assessments are provided in FIGS. 5A through 12. FIGS. 5A, 6A, 7A, 8A and 9A include a tabulation of input data and calculated values associated with various liquid storage areas (e.g., Sample Area 1 through Sample Area 5, respectively). FIGS. 5B, 6B, 7B, 8B and 9B include output screen displays illustrating the results of the calculated values associated with each storage area in FIGS. 5A, 6A, 7A, 8A and 9A (respectively). FIG. 10 includes an example of an output screen associated with a fueling and rail area. FIG. 11 illustrates an example of an online version of an output screen having numerical risk ratings associated with various risk facets. FIG. 12 illustrates an example of an output screen associated with a parts washer area in a building.

[00069] At step 112, one or more improvement path recommendations can be calculated to provide specific and prescriptive recommendations. In certain embodiments, improvement path recommendation calculations can be performed by solving for each of the earlier risk calculations to achieve the lowest possible risk assessment without effecting "major" changes to the area 202 or its infrastructure. For example, moving a physical drain is rarely feasible and would in most cases constitute a "major" change to the area 202.

[00070] With regard to improvement path calculations for the area drain risk facet, the facility would take every feasible physical measure to reduce drain risk in an area, including having drain sealing apparatus and spill response supplies appropriately located, resulting in an overall area drain risk of "Lower". [00071] With regard to improvement path determination for response pressure, this calculation reflects the "Lower" area drain risk resulting from the adoption of the full improvement path recommendations, and averages it with an unadjusted area liquid risk to reflect the new response pressure for the improved area (RP _p0 st). Because area drain risk is set to "Lower" it has a value of zero which is averaged with area liquid risk and then indexed to a 100-point scale: RP _ip = (0+(100*(ALR _c /45). Next, logic evaluation of RPip can be performed to generate a post-improvement path response pressure risk ph rase ( RPpost), as follows:

[00072] In certain embodiments, determining an improvement path for spill kit capacity reflects the optimal spill kit absorbency for a given area, the minimum absorbency that will reach the "Excellent" risk phrase for spill kit capacity. The base absorbency necessary to achieve an "Excellent" spill kit capacity rating (SKCi _P ) can be calculated for the largest container (LRG _CU rrent), while accounting for a higher area drain risk requiring marginally higher absorbent capacity (SKA _C ). Therefore, spill kit capacity rating for the improvement path can be calculated as SKCi _P = (SKA _c * LRG _CU rrent)+l. In certain aspects, SKCi _P can be adjusted by a selected class absorbency factor (CAF) to reflect the expected maximum absorbency provided by spill kit in the event of a spill of the largest container, as follows:

2000.01 to 20000 Cap at 1000 gallons

gal total absorbency

maximum

[00073] Next, a recommended single spill kit capacity per area (SKC _p0 st) can be calculated. Where the recommended SKC _p0 st absorbency exceeds that available in a single spill kit, supplemental cavalry absorbency (CA _p0 st) can be calculated by subtracting SKC _p0 st from maximum single spill kit absorbency (MAX _S i<). In the situation where LRG _CU rrent > 2000, then SKCpost = 1000; where LRG _CU rrent <= 2000, then SKC _pos t = (SKC _ip *CAF); and, where SKA _pos t > MAXsk, then CA _pos t = SKA _pos t - MAX _sk .

[00074] With regard to determining the improvement path for spill kit distance, this calculation reflects the maximum optimal distance the spill kit should be located from the liquid storage area while still achieving an "Excellent" risk phrase for spill kit distance. This recommended distance is described as SKD _pos t. In cases where Cavalry Absorbency (CA _pos t) is required, its maximum distance from the liquid area while still reaching a corresponding "Excellent" risk phrase can be described as CAD _pos t. The following is an example of logic evaluation of LRG _CU rrent to obtain corresponding SKD _exc value:

[00075] Calculation of maximum spill kit distance from liquid area to achieve

"Excellent" risk phrase (SKD _pos t) can be provided as: where LRGcurrent <=330, then SKD _pos t = l-(SKD _rc - MSKc)*(CSDo *SKD _exc ); and, where LRGcurrent >330, then SKD _pos t = SKD _exc .

Calculation of maximum perimeter distance of cavalry absorbency (CA _pos t) to achieve "Excellent" risk phrase for spill kit distance equivalent for cavalry absorbency (CAD _pos t) can be provided as: where CA _pos t >0, then CAD _pos t = CSD5.

[00076] Regarding the improvement path calculation for spill kit visibility, this calculation reflects the points of visibility to be added (SKV _pta dd) to the current spill kit points of visibility (SKVptcurr) to reach the "Excellent" risk phrase for spill kit visibility (SKVi _P ). First, SKVptpost can be set to a value corresponding to "Excellent" risk phrase (e.g., SKV _p t _P ost = 3). Next, logic evaluation of SKV _a dj can be performed to derive current points of visibility (SKVptcurr), as follows:

[00077] Then, calculation of additional points of visibility to be added to current spill kit visibility (SKVptadd) can be conducted to achieve an "Excellent" risk phrase for spill kit visibility (SKVip). This can be calculated as SKV _pta dd = SKVptpost - SKV _ptC urr.

[00078] Improvement Path calculation for blocker distance reflects the maximum optimal distance the blocker 210 should be located from the drain 206 or escape point while still achieving the "Excellent" risk phrase for blocker distance (DTE ). This recommended distance is described as DTB _p0 st. Logic evaluation of LRG _CU rrent to obtain a corresponding DTBexc value can be conducted as follows:

[00079] Calculation of maximum blocker distance from liquid storage area to achieve

"Excellent" risk phrase (DTB _p0 st) can be performed while also considering the effect of distance reduction for higher levels of response pressure (DTB _rc ): where LRGcurrent <=330, then DTBpost = (l-( DTB _rc ))*(CSD ₀ * DTB _exc ); and, where LRGcurrent >330, then DTB _pos t = DTB _exc

[00080] The improvement path calculation for blocker visibility reflects the points of visibility to be added (BV _pta dd) to the current blocker number of points of visibility (BV _ptC urr) to reach the "Excellent" risk phrase for Blocker Visibility (BVi _P ). First, set BV _p t ost to value corresponding to "Excellent" risk phrase (e.g., BV _p t _P ost = 3). Then, logic evaluation of SKV _a dj can be applied to derive current points of visibility (SKV _p t _CU rr), as follows:

[00081] Calculation of additional points of visibility to be added to current blocker visibility ( BVptadd) can be performed to reach "Excellent" risk phrase for Blocker Visibility (BV _ip ). Therefore, BV _pta dd = BV _ptp0 st - BV _ptcU rr.

[00082] An improvement path calculation for drain condition creates specific directions based on the earlier analyst view of the ability of the drain 206 to be sealed liquid-tight with a urethane panel, for example. In essence, when the analyst observes an eroded sealing surface and assigns a "Borderline" risk phrase for Drain Condition, then the corresponding improvement path for drain condition may read: "Consider leveling drain surface with epoxy; keep the drain surrounds clear and free of debris and gravel to allow liquid-tight sealing of drain" or an equivalent instruction.

[00083] FIGS. 13 and 14 illustrate example output screens associated with developing improvement paths with particular liquid storage areas. It can be seen that these screens display risk assessments before and after the improvement path has been implemented in the area. FIG. 15 includes an example of an output screens associated with developing improvement paths with a particular liquid storage area, including a numerical count of risk facets both before and after the improvement path has been implemented.

[00084] At step 114, the liquid storage area 202 may be transformed in accordance with recommendations developed by performing the above spill risk assessments. As shown in FIG. 16, various elements of the area 202 have been physically moved or modified in response to performing the assessment. For example, a spill kit with an appropriate level of absorbency has been positioned within 20 feet of the largest capacity liquid storage container 204. In another example, the drain blocker 210 has been moved to within 20 feet of the drain 206. It can be seen that no "major" changes to the area 202 were

recommended, such as moving the drain 206 or moving the location of the storage container 204, for example.

[00085] FIG. 17 includes an example of a computer system architecture in which various input data, calculations, and determinations can be executed in association with various spill risk assessment embodiments described herein. In the example shown, a spill risk assessment system 1702 may include a computer processor (e.g., server 1704) and various modules 1706-1714 which perform various tasks or provide functionality within the system 1702. For example, an algorithm module 1706 may be programmed to perform various risk facet calculations. An input data module 1708 may be programmed to receive, process, and/or store data collected or derived from a given liquid storage area 1716. An output summary module 10 may be provided to generate and display summaries of calculations performed by the spill risk assessment algorithm. In another example, an improvement path module 1712 may be programmed to perform improvement path calculations. It can be appreciated that one or more other modules 1714 might also be provided in the system 1702 to execute various tasks. The system 1702 may also be operatively associated with one or more suitable electronic data storage media 1718 for retaining or accessing data such as risk assessment data.

[00086] In certain aspects, one or more measurement devices 1720 (e.g., laser-based devices) may be employed within the area 1716 to capture input data. Likewise, various types of data input devices 1722 (e.g., mobile devices, computers, laptops, etc.) may be employed within the area to collect and transmit data to the system 1702. In various embodiments, communications between the system 1702 and devices 1720, 1722 used within the area 1716 can be enabled through a variety of communication media or communication means 1724 (e.g., Internet, intranet, VPN, wireless, etc.)

[00087] The examples provided herein are provided merely for the purpose of illustrating the various potential embodiments of the present invention. No particular aspect of a given screen display, output screen, schematic, or flow chart is necessarily intended to limit the scope of the present invention. [00088] In various embodiments, various modules or platforms can be used to practice certain aspects of the invention. For example, software-as-a-service (SaaS) models or application service provider (ASP) models may be employed as software application delivery models to communicate software applications to clients or other users. Such software applications can be downloaded through an Internet connection, for example, and operated either independently (e.g., downloaded to a laptop or desktop computer system) or through a third-party service provider (e.g., accessed through a third-party web site). In addition, cloud computing techniques may be employed in connection with various embodiments of the invention.

[00089] Moreover, the processes associated with the present embodiments may be executed by programmable equipment, such as computers. Software or other sets of instructions that may be employed to cause programmable equipment to execute the processes may be stored in any storage device, such as a computer system (non-volatile) memory. Furthermore, some of the processes may be programmed when the computer system is manufactured or via a computer- readable memory storage medium.

[00090] It can also be appreciated that certain process aspects described herein may be performed using instructions stored on a computer-readable memory medium or media that direct a computer or computer system to perform process steps. A computer-readable medium may include, for example, memory devices such as diskettes, compact discs of both read-only and read/write varieties, optical disk drives, and hard disk drives. A computer- readable medium may also include memory storage that may be physical, virtual, permanent, temporary, semi- permanent, and/or semi-temporary, including non-transitory varieties thereof. Memory and/or storage components may be implemented using any computer-readable media capable of storing data such as volatile or non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writeable or re- writeable memory, and so forth. Examples of computer- readable storage media may include, without limitation, RAM, dynamic RAM (DRAM), Double- Data-Rate DRAM

(DDRAM), synchronous DRAM (SDRAM), static RAM (SRAM), read-only memory (ROM), programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory (e.g., NOR orNAND flash memory), content addressable memory (CAM), polymer memory (e.g., ferroelectric polymer memory), phase- change memory, ovonic memory, ferroelectric memory, silicon-oxide-nitride- oxide-silicon (SONOS) memory, magnetic or optical cards, or any other type of media suitable for storing information.

[00091] A "computer," "computer system," "computing apparatus," "component," or

"computer processor" may be, for example and without limitation, a processor,

microcomputer, minicomputer, server, mainframe, laptop, personal data assistant (PDA), wireless e-mail device, smart phone, mobile phone, electronic tablet, cellular phone, pager, fax machine, scanner, or any other programmable device or computer apparatus configured to transmit, process, and/or receive data. Computer systems and computer-based devices disclosed herein may include memory and/or storage components for storing certain software applications used in obtaining, processing, and communicating information. It can be appreciated that such memory may be internal or external with respect to operation of the disclosed embodiments. In various embodiments, a "host," "engine," "loader," "filter," "platform," or "component" may include various computers or computer systems, or may include a reasonable combination of software, firmware, and/or hardware. In certain embodiments, a "module" may include software, firmware, hardware, or any reasonable combination thereof.

[00092] In various embodiments of the present invention, a single component may be replaced by multiple components, and multiple components may be replaced by a single component, to perform a given function or functions. Except where such substitution would not be operative to practice embodiments of the present invention, such substitution is within the scope of the present invention. Any of the servers described herein, for example, may be replaced by a "server farm" or other grouping of networked servers (e.g., a group of server blades) that are located and configured for cooperative functions. It can be appreciated that a server farm may serve to distribute workload between/among individual components of the farm and may expedite computing processes by harnessing the collective and cooperative power of multiple servers. Such server farms may employ load- balancing software that accomplishes tasks such as, for example, tracking demand for processing power from different machines, prioritizing and scheduling tasks based on network demand, and/or providing backup contingency in the event of component failure or reduction in operability. [00093] In general, it will be apparent to one of ordinary skill in the art that various embodiments described herein, or components or parts thereof, may be implemented in many different embodiments of software, firmware, hardware, and/or modules thereof. The software code or specialized control hardware used to implement some of the present embodiments is not limiting of the present invention. For example, the embodiments described hereinabove may be implemented in computer software using any suitable computer programming language such as .N ET or HTML using, for example, conventional or object-oriented techniques. Programming languages for computer software and other computer-implemented instructions may be translated into machine language by a compiler or an assembler before execution and/or may be translated directly at run time by an interpreter. Examples of assembly languages include ARM, MIPS, and x86; examples of high level languages include Ada, BASIC, C, C++, C#, COBOL, Fortran, Java, Lisp, Pascal, Object Pascal; and examples of scripting languages include Bourne script, JavaScript, Python, Ruby, PHP, and Perl. Various embodiments may be employed in a Lotus Notes environment, for example. Such software may be stored on any type of suitable computer- readable medium or media such as, for example, a magnetic or optical storage medium. Thus, the operation and behavior of the embodiments are described without specific reference to the actual software code or specialized hardware components. The absence of such specific references is feasible because it is clearly understood that artisans of ordinary skill would be able to design software and control hardware to implement the embodiments of the present invention based on the description herein with only a reasonable effort and without undue experimentation.

[00094] Various embodiments of the systems and methods described herein may employ one or more electronic computer networks to promote communication among different components, transfer data, or to share resources and information. Such computer networks can be classified according to the hardware and software technology that is used to interconnect the devices in the network, such as optical fiber, Ethernet, wireless LAN, HomePNA, power line communication or G.hn. The computer networks may also be embodied as one or more of the following types of networks: local area network (LAN); metropolitan area network (MAN); wide area network (WAN); virtual private network (VPN); storage area network (SAN); or global area network (GAN), among other network varieties.

[00095] For example, a WAN computer network may cover a broad area by linking communications across metropolitan, regional, or national boundaries. The network may use routers and/or public communication links. One type of data communication network may cover a relatively broad geographic area (e.g., city-to-city or country-to-country) which uses transmission facilities provided by common carriers, such as telephone service providers. In another example, a GAN computer network may support mobile

communications across multiple wireless LANs or satellite networks. In another example, a VPN computer network may include links between nodes carried by open connections or virtual circuits in another network (e.g., the Internet) instead of by physical wires. The link- layer protocols of the VPN can be tunneled through the other network. One VPN application can promote secure communications through the Internet. The VPN can also be used to separately and securely conduct the traffic of different user communities over an underlying network. The VPN may provide users with the virtual experience of accessing the network through an IP address location other than the actual IP address which connects the access device to the network.

[00096] The computer network may be characterized based on functional relationships among the elements or components of the network, such as active networking, client-server, or peer-to-peer functional architecture. The computer network may be classified according to network topology, such as bus network, star network, ring network, mesh network, star-bus network, or hierarchical topology network, for example. The computer network may also be classified based on the method employed for data communication, such as digital and analog networks.

[00097] Embodiments of the methods and systems described herein may employ internetworking for connecting two or more distinct electronic computer networks or network segments through a common routing technology. The type of internetwork employed may depend on administration and/or participation in the internetwork. Non- limiting examples of internetworks include intranet, extranet, and Internet. Intranets and extranets may or may not have connections to the Internet. If connected to the Internet, the intranet or extranet may be protected with appropriate authentication technology or other security measures. As applied herein, an intranet can be a group of networks which employ Internet Protocol, web browsers and/or file transfer applications, under common control by an administrative entity. Such an administrative entity could restrict access to the intranet to only authorized users, for example, or another internal network of an organization or commercial entity. As applied herein, an extranet may include a network or internetwork generally limited to a primary organization or entity, but which also has limited connections to the networks of one or more other trusted organizations or entities (e.g., customers of an entity may be given access an intranet of the entity thereby creating an extranet).

[00098] Computer networks may include hardware elements to interconnect network nodes, such as network interface cards (N ICs) or Ethernet cards, repeaters, bridges, hubs, switches, routers, and other like components. Such elements may be physically wired for communication and/or data connections may be provided with microwave links (e.g., IEEE 802.12) or fiber optics, for example. A network card, network adapter or NIC can be designed to allow computers to communicate over the computer network by providing physical access to a network and an addressing system through the use of MAC addresses, for example. A repeater can be embodied as an electronic device that receives and retransmits a communicated signal at a boosted power level to allow the signal to cover a telecommunication distance with reduced degradation. A network bridge can be configured to connect multiple network segments at the data link layer of a computer network while learning which addresses can be reached through which specific ports of the network. In the network, the bridge may associate a port with an address and then send traffic for that address only to that port. In various embodiments, local bridges may be employed to directly connect local area networks (LANs); remote bridges can be used to create a wide area network (WAN) link between LANs; and/or, wireless bridges can be used to connect LANs and/or to connect remote stations to LANs.

[00099] As employed herein, an application server may be a server that hosts an API to expose business logic and business processes for use by other applications. Examples of application servers include J2EE or Java EE 5 application servers including WebSphere Application Server. Other examples include WebSphere Application Server Community Edition (IBM), Sybase Enterprise Application Server (Sybase Inc), WebLogic Server (BEA), JBoss (Red Hat), JRun (Adobe Systems), Apache Geronimo (Apache Software Foundation), Oracle OC4J (Oracle Corporation), Sun Java System Application Server (Sun Microsystems), and SAP Netweaver AS (ABAP/Java). Also, application servers may be provided in accordance with the .N ET framework, including the Windows Communication Foundation, .NET Remoting, ADO.N ET, and ASP.N ET among several other components. For example, a Java Server Page (JSP) is a servlet that executes in a web container which is functionally equivalent to CGI scripts. JSPs can be used to create HTML pages by embedding references to the server logic within the page. The application servers may mainly serve web-based applications, while other servers can perform as session initiation protocol servers, for instance, or work with telephony networks. Specifications for enterprise application integration and service-oriented architecture can be designed to connect many different computer network elements. Such specifications include Business Application Programming Interface, Web Services Interoperability, and Java EE Connector Architecture.

[000100] Embodiments of the methods and systems described herein may divide functions between separate CPUs, creating a multiprocessing configuration. For example, multiprocessor and multi-core (multiple CPUs on a single integrated circuit) computer systems with co- processing capabilities may be employed. Also, multitasking may be employed as a computer processing technique to handle simultaneous execution of multiple computer programs.

[000101] Although some embodiments may be illustrated and described as comprising functional components, software, engines, and/or modules performing various operations, it can be appreciated that such components or modules may be implemented by one or more hardware components, software components, and/or combination thereof. The functional components, software, engines, and/or modules may be implemented, for example, by logic (e.g., instructions, data, and/or code) to be executed by a logic device (e.g., processor). Such logic may be stored internally or externally to a logic device on one or more types of computer-readable storage media. In other embodiments, the functional components such as software, engines, and/or modules may be implemented by hardware elements that may include processors, microprocessors, circuits, circuit elements (e.g., transistors, resistors, capacitors, inductors, and so forth), integrated circuits, application specific integrated circuits (ASIC), programmable logic devices (PLD), digital signal processors (DSP), field programmable gate array (FPGA), logic gates, registers,

semiconductor device, chips, microchips, chip sets, and so forth.

[000102] Examples of software, engines, and/or modules may include software components, programs, applications, computer programs, application programs, system programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, procedures, software interfaces, application program interfaces (API), instruction sets, computing code, computer code, code segments, computer code segments, words, values, symbols, or any combination thereof. Determining whether an embodiment is implemented using hardware elements and/or software elements may vary in accordance with any number of factors, such as desired computational rate, power levels, heat tolerances, processing cycle budget, input data rates, output data rates, memory resources, data bus speeds and other design or performance constraints.

[000103] Additionally, it can be appreciated that the embodiments described herein illustrate example implementations, and that the functional elements, logical blocks, modules, and circuits elements may be implemented in various other ways which are consistent with the described embodiments. Furthermore, the operations performed by such functional elements, logical blocks, modules, and circuits elements may be combined and/or separated for a given implementation and may be performed by a greater number or fewer number of components or modules. As will be apparent to those of skill in the art upon reading the present disclosure, each of the individual embodiments described and illustrated herein has discrete components and features which may be readily separated from or combined with the features of any of the other several aspects without departing from the scope of the present disclosure. Any recited method can be carried out in the order of events recited or in any other order which is logically possible.

[000104] U nless specifically stated otherwise, it may be appreciated that terms such as "processing," "computing," "calculating," "determining," or the like, refer to the action and/or processes of a computer or computing system, or similar electronic computing device, such as a general purpose processor, a DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein that manipulates and/or transforms data represented as physical quantities (e.g., electronic) within registers and/or memories into other data similarly represented as physical quantities within the memories, registers or other such information storage, transmission or display devices.

[000105] Certain embodiments may be described using the expression "coupled" and "connected" along with their derivatives. These terms are not necessarily intended as synonyms for each other. For example, some embodiments may be described using the terms "connected" and/or "coupled" to indicate that two or more elements are in direct physical or electrical contact with each other. The term "coupled," however, also may mean that two or more elements are not in direct contact with each other, but yet still co-operate or interact with each other. With respect to software elements, for example, the term "coupled" may refer to interfaces, message interfaces, application program interface (API), exchanging messages, and so forth.

[000106] Although various systems described herein may be embodied in software or code executed by general purpose hardware as discussed above, as an alternative the same may also be embodied in dedicated hardware or a combination of software/general purpose hardware and dedicated hardware. If embodied in dedicated hardware, each can be implemented as a circuit or state machine that employs any one of or a combination of a number of technologies. These technologies may include, but are not limited to, discrete logic circuits having logic gates for implementing various logic functions upon an application of one or more data signals, application specific integrated circuits having appropriate logic gates, or other components, etc. Such technologies are generally well known by those of ordinary skill in the art and, consequently, are not described in detail herein.

[000107] The flow charts and methods described herein show the functionality and operation of various implementations. If embodied in software, each block, step, or action may represent a module, segment, or portion of code that comprises program instructions to implement the specified logical function(s). The program instructions may be embodied in the form of source code that comprises human-readable statements written in a programming language or machine code that comprises numerical instructions recognizable by a suitable execution system such as a processing component in a computer system. If embodied in hardware, each block may represent a circuit or a number of interconnected circuits to implement the specified logical function(s). [000108] Although the flow charts and methods described herein may describe a specific order of execution, it is understood that the order of execution may differ from that which is described. For example, the order of execution of two or more blocks or steps may be scrambled relative to the order described. Also, two or more blocks or steps may be executed concurrently or with partial concurrence. Further, in some embodiments, one or more of the blocks or steps may be skipped or omitted. It is understood that all such variations are within the scope of the present disclosure.

[000109] Whereas particular embodiments of this invention have been described above for purposes of illustration, it will be evident to those skilled in the art that numerous variations of the details of the present invention may be made without departing from the invention.