System and method for reinsurance of air purification

Abstract

A chemical disinfection process for vehicles using chlorine dioxide and titanium dioxide with calculated re-treatment formulas and schedules based on bacterial infestation data. Systems and methods that include client devices and servers that monitor and control a chemical disinfection process. The system generates a surety arrangement that facilitates re-treatment and electronic notification alerts to chemical solution vendors, dealers and vehicle owners.

Claims

1. A method of chemically disinfecting an interior of a vehicle comprising: testing the interior for a first microbial infestation level; dispensing a first airborne suspension having a first chemical composition into the interior; testing the interior for a second microbial infestation level; making a comparison of the first microbial infestation level to the second microbial infestation level; deriving a second chemical composition based on the comparison; and, dispensing a second airborne suspension having the second chemical composition into the interior.

2. The method of claim 1 further comprising: dispensing the first airborne suspension into the interior at a first pressure level; deriving a second pressure level based on the comparison; and, dispensing the second airborne suspension into the interior at the second pressure level.

3. The method of claim 2 further comprising: dispersing the second airborne suspension into the interior at the second pressure level of about 20% higher than the first pressure level.

4. The method of claim 2 further comprising: dispersing the first airborne suspension into the interior at the first pressure level of about 95 PSI.

5. The method of claim 1 further comprising: preparing the first chemical composition having the following formula: TABLE-US-00001 Alcohols, C12-C14, ethoxylated 0.1%-10% DI Water 70%-80% Titanium Dioxide .sup.1%-30% Diethylamine Acetate .sup.1%-30% Diethylammonium Dihydrogen Phosphate .sup.1%-30% 2-Propanol 0.1%-10% Ethanol 0.1%-5% Chlorine Dioxide 0.1%-10% Methyl Chloro Isothiazolinone 0.1%-5% Methyl Isothiazolinone 0.1%-5%.

6. The method of claim 5 wherein the titanium dioxide has a first particle size and further comprising: preparing the second chemical composition according to the following formula: if the comparison shows the second microbial infestation level is between about 0% and about 50% of the first microbial infestation level, then use the first chemical composition as the second chemical composition; if the comparison shows the second microbial infestation level is between about 50% and about 70% of the first microbial infestation level, then use the first chemical composition but decrease the first particle size to about 20 microns to achieve the second chemical composition; and, if the comparison shows the second microbial infestation level is between about 70% and about 90% of the first microbial infestation level, then use the first chemical composition but decrease the first particle size to about 20 microns and increase the percentage of chlorine dioxide in the first chemical composition by about 5% to achieve the second chemical composition.

7. The method of claim 6 further comprising: if the comparison shows the second microbial infestation level to be above about 90% of the first microbial infestation level, then increase a flowrate of the second airborne suspension by about 20%.

8. The method of claim 1 further comprising: waiting a predetermined period of time between the step of dispensing the first airborne suspension and the step of testing the interior for a second microbial infestation.

9. The method of claim 8 further comprising: sending an electronic notification at an expiration of the predetermined period of time.

10. The method of claim 8 further comprising: creating a surety obligation based at least in part on the predetermined period of time.

11. The method of claim 10 further comprising: providing that the surety obligation require a compensation for the step of dispensing the second airborne suspension.

12. A method of increasing the effectiveness of chemically disinfecting a vehicle interior comprising: testing the vehicle interior for a first bacterial infestation level; applying a first airborne suspension having a first chemical composition into the vehicle interior at a first application flowrate; waiting a predetermined period of time; testing the vehicle interior for a second bacterial infestation level; making a comparison between the first bacterial infestation level and the second bacterial infestation level; deriving a second chemical composition based on the comparison; dispensing a second airborne suspension having the second chemical composition into the vehicle interior at a second application flowrate; and, creating a surety obligation for a reimbursement amount for applying the second airborne suspension to the vehicle interior.

13. The method of claim 12 further comprising: paying the reimbursement amount.

14. The method of claim 12 further comprising: sending a notification related to the step of dispensing the second airborne suspension.

15. The method of claim 14 wherein the step of sending further comprises: providing a computer system for sending the notification; and, providing an electronic message, sent through the computer system, as the notification.

16. The method of claim 12 wherein the first chemical composition has a first bacterial lethality, and the second chemical composition has a second bacterial lethality; and, wherein the step of deriving a second chemical composition further comprises increasing the second bacterial lethality to a lethality greater than the first bacterial lethality.

17. The method of claim 12 further comprising: setting the second application flowrate to be about the same as the first application flowrate.

18. The method of claim 12 wherein the step of creating a surety obligation further comprises: reducing the reimbursement amount by a penalty amount.

19. The method of claim 12 wherein the step of waiting a predetermined period of time further comprises: creating a re-application schedule for applying the second airborne suspension and a third airborne suspension.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) In the detailed description of the preferred embodiments presented below, reference is made to the accompanying drawings.

(2) FIG. 1 is a system diagram of a preferred embodiment.

(3) FIGS. 2A-2H are a sequence diagram of a method performed by the system for performing chemical application process and monitoring re-treatment.

(4) FIG. 3 is a method of reinsurance of treatment obligations between a dealership and an insurance underwriter.

(5) FIG. 4 is a method for the performance of obligations between a dealership and a product vendor.

(6) FIG. 5 is a method for the performance of obligations between a dealership and a vehicle owner.

(7) FIG. 6 is a method for the performance of obligations between dealership and product vendor.

(8) FIG. 7 is a method for the performance of obligations between dealership and Insurance Underwriter.

(9) FIG. 8 is a table of chemical components for a preferred embodiment of an aqueous solution of TiO2.

(10) FIG. 9 is a graph of test results of bacteria level measurement data.

(11) FIG. 10 is a graph of test results of bacteria level measurement data.

(12) FIG. 11 is a graph of test results of bacteria eradication levels.

DETAILED DESCRIPTION

(13) Referring to FIG. 1, system 100 includes several networked devices, including user client device 104, administration server 116, administration client device 128, dealer server 140, dealer client device 152, surety server 164, surety client device 176, vendor server 188, and vendor client device 105. System 100 operates to control the chemical application process based on measurements from the process and based on the type of vehicle to which the process is being applied.

(14) User client device 104 includes: set of processors 106, memory 108, and network connection 114. Set of processors 106 includes at least one processor to execute programs stored in memory 108. Memory 108 includes apps 110 and data 101, which include instructions that are executable by set of processors 106 to perform the functions of system 100. Network connection 114 connects user client device 104 to internet 102. In a preferred embodiment, user client device 104 is used by the owner of the vehicle to purchase a package of at least one application spread out over at least one year and to schedule the applications.

(15) Administration server 116 includes: set of processors 118, memory 120, and network connection 126. Set of processors 118 includes at least one processor to execute programs stored in memory 120. Memory 120 includes apps 122 and data 124, which include instructions that are executable by set of processors 118 to perform the functions of data 101. Network connection 126 connects administration server 116 to internet 102. In a preferred embodiment, administration server 116 is used to settle and control the transactions between the dealer and the surety through interactions with dealer server 140 and surety server 164.

(16) Administration client device 128 includes: set of processors 130, memory 132, and network connection 138. Set of processors 130 includes at least one processor to execute programs stored in memory 132. Memory 132 includes apps 134 and data 136, which include instructions that are executable by set of processors 130 to perform the functions of data 124. Network connection 138 connects administration client device 128 to internet 102. In a preferred embodiment, administration client device 128 is used to control the processing performed by administration server 116.

(17) Dealer server 140 includes: set of processors 142, memory 144, and network connection 150. Set of processors 142 includes at least one processor to execute programs stored in memory 144. Memory 144 includes apps 146 and data 148, which include instructions that are executable by set of processors 142 to perform the functions of data 136. Network connection 150 connects dealer server 140 to internet 102. In a preferred embodiment, dealer server 140 is used host a website that is accessible by user client device 104 and dealer client device 152 for purchasing, scheduling, and performing the chemical application process.

(18) Dealer client device 152 includes: set of processors 154, memory 156, and network connection 162. Set of processors 154 includes at least one processor to execute programs stored in memory 156. Memory 156 includes apps 158 and data 160, which include instructions that are executable by set of processors 154 to perform the functions of data 148. Network connection 162 connects dealer client device 152 to internet 102. In a preferred embodiment, dealer client device 152 is used by a sales person at the dealership to initiate, setup the scheduling for, and perform the chemical application process as well as to interact with administration server 116 to submit new insurance requests and insurance claims.

(19) Surety server 164 includes: set of processors 166, memory 168, and network connection 174. Set of processors 166 includes at least one processor to execute programs stored in memory 168. Memory 168 includes apps 170 and data 172, which include instructions that are executable by set of processors 166 to perform the functions of data 160. Network connection 174 connects surety server 164 to internet 102. In a preferred embodiment, surety server 164 is used to process insurance underwriting and claim requests.

(20) Surety client device 176 includes: set of processors 178, memory 180, and network connection 186. Set of processors 178 includes at least one processor to execute programs stored in memory 180. Memory 180 includes apps 182 and data 184, which include instructions that are executable by set of processors 178 to perform the functions of data 172. Network connection 186 connects surety client device 176 to internet 102. In a preferred embodiment, surety client device 176 is used monitor and control the activity of surety server 164.

(21) Vendor server 188 includes: set of processors 190, memory 192, and network connection 198. Set of processors 190 includes at least one processor to execute programs stored in memory 192. Memory 192 includes apps 194 and data 196, which include instructions that are executable by set of processors 190 to perform the functions of data 184. Network connection 198 connects vendor server 188 to internet 102. In a preferred embodiment, vendor server 188 is used to host a website that is accessed by dealer client device 152 to determine the appropriate settings for the chemical application process based on one or more of the type of vehicle, amount of interior space, amount of interior surface area, the number of previous applications, the length of time since the last application, and pre-application measurements.

(22) Vendor client device 105 includes: set of processors 107, memory 109, and network connection 111. Set of processors 107 includes at least one processor to execute programs stored in memory 109. Memory 109 includes apps 115 and data 113, which include instructions that are executable by set of processors 107 to perform the functions of data 196. Network connection 111 connects vendor client device 105 to internet 102. In a preferred embodiment, vendor client device 105 controls and monitors the activity of vendor server 188 as well as updates the data, formulas, and information used to determine the parameters of the chemical application process.

(23) Referring to FIGS. 2A through 2H, sequence diagram 2000 illustrates a preferred embodiment of the method used by system 100. The devices of system 100 generate alerts, requests, and messages that are sent to one or more other devices of system 100. Upon receiving alerts, requests, and messages, the respective devices activate and generate subsequent data alerts, requests, and messages based on one or more of: pre-existing data on the device; data received in the alerts, requests, and messages received by the device; and, data retrieved from other devices in response to the data received in the alerts, requests, and messages. In a preferred embodiment, for each of the messages generated and passed by the system, the device generating the message generates a cryptographic hash value from the information in the message, a random number, and a previously generated cryptographic hash value. In a preferred embodiment, the cryptographic hash value includes a predetermined number of leading zero bits in order to be acceptable by system 100. Several different random numbers are attempted in order to generate the cryptographic hash value with an acceptable number of leading zeros.

(24) At step 2028, user client device 2002 generates a user selection request. In a preferred embodiment, user client device 2002 is activated in response to input from an input/output device such as a one or more of a keyboard, mouse, and touch sensitive screen and the input is used to identify the selection of the number of chemical process applications and the duration between the chemical process applications, which are encoded into the user selection request. In the context of TiO2 disinfection of a vehicle, the selection may be of a time period for re-application of the TiO2 solution, such as one re-application annually for 1, 5, 10, or 15 years.

(25) At step 2030, user client device 2002 sends the user selection request to dealer server 2008.

(26) At optional step 2032, dealer client device 2010 generates a dealer selection request. A dealer selection request is useful when the user has no smart phone and the dealer makes the selection for the user on the dealer client device.

(27) At optional step 2034, dealer client device 2010 sends the dealer selection request, which is received by dealer server 2008.

(28) At step 2036, an approval code is generated by dealer server 2008.

(29) At step 2038, dealer server 2008 sends the approval code, which is received by user client device 2002.

(30) At optional step 2040, dealer server 2008 sends the approval code, which is received by dealer client device 2010.

(31) At step 2042, user client device 2002 displays the approval code.

(32) At optional step 2044, dealer client device 2010 displays the approval code.

(33) At step 2046, a vehicle selection alert is generated by dealer client device 2010.

(34) At step 2048, the vehicle selection alert is sent from dealer client device 2010 to vendor server 2016.

(35) At step 2050, the vehicle selection alert is sent from dealer client device 2010 to dealer server 2008.

(36) At step 2052, the vehicle selection alert is sent from dealer server 2008 to vendor server 2016.

(37) At step 2054, the vehicle selection alert is transmitted from vendor server 2016 and subsequently received by vendor client device 2018.

(38) At optional step 2056, vendor client device 2018 displays the vehicle selection alert.

(39) At step 2058, an application process update alert is generated by vendor server 2016.

(40) At step 2060, vendor server 2016 sends the application process update alert, which is received by dealer client device 2010.

(41) At optional step 2062, the application process update alert is sent from vendor server 2016 to dealer server 2008.

(42) At optional step 2064, the application process update alert is sent from dealer server 2008 to dealer client device 2010.

(43) At optional step 2066, the application process update alert is transmitted from vendor server 2016 and subsequently received by vendor client device 2018.

(44) At optional step 2068, the application process update alert is displayed by vendor client device 2018.

(45) At step 2070, dealer client device 2010 displays the application process update alert.

(46) At step 2072, application process measurements are collected by dealer client device 2010. In a preferred embodiment, process measurements are the bacteria count from a selected surface sample or group of surface samples. In an alternate embodiment, the process measurements are TiO2 thickness for a given surface sample or group of surface samples.

(47) At step 2074, dealer client device 2010 generates an application measurements alert. The application measurements alert, in a preferred embodiment, is a report including a summary of the application process measurements.

(48) At step 2076, dealer client device 2010 sends the application measurements alert to dealer server 2008.

(49) At step 2078, a product application report is generated by dealer server 2008.

(50) At step 2080, dealer server 2008 sends the product application report to dealer client device 2010.

(51) At step 2082, the product application report is displayed by dealer client device 2010.

(52) At step 2084, a surety request is generated by dealer client device 2010. In a preferred embodiment, the surety request is a request from the dealer, to the administrator, for initiation of an insurance contract for the TiO2 re-application.

(53) At step 2086, a surety request alert is sent from dealer client device 2010 to administration server 2004.

(54) At optional step 2088, the surety request alert is sent from dealer client device 2010 to dealer server 2008.

(55) At optional step 2090, dealer server 2008 sends the surety request alert to administration server 2004.

(56) At optional step 2092, the surety request alert is sent from administration server 2004 to administration client device 2006.

(57) At step 2094, the surety request alert is displayed by administration client device 2006.

(58) At step 2096, a surety approval request is generated by administration server 2004. In a preferred embodiment, the administrator requests an insurance contract from the surety to insure the TiO2 re-application.

(59) At step 2098, administration server 2004 sends a surety approval request alert to surety server 2012.

(60) At optional step 2100, surety server 2012 sends the surety approval request alert to surety client device 2014.

(61) At optional step 2102, surety client device 2014 displays the surety approval request alert.

(62) At step 2104, a status and approval code is generated by surety server 2012. In a preferred embodiment, the approval code is generated when the surety issues an insurance contract for re-application of the TiO2.

(63) At step 2106, the status and approval code is transmitted from surety server 2012 and subsequently received by administration server 2004.

(64) At optional step 2108, administration server 2004 sends the status and approval code, which is received by administration client device 2006.

(65) At optional step 2110, the status and approval code is sent from surety server 2012 to surety client device 2014.

(66) At optional step 2112, surety client device 2014 displays the status and approval code.

(67) At optional step 2114, administration client device 2006 displays the status and approval code.

(68) At step 2116, a status and approval code report is generated by administration server 2004.

(69) At step 2118, the status and approval code report is transmitted from administration server 2004 and subsequently received by dealer client device 2010.

(70) At optional step 2120, the status and approval code report is sent from administration server 2004 to dealer server 2008.

(71) At optional step 2122, the status and approval code report is transmitted from dealer server 2008 and subsequently received by dealer client device 2010.

(72) At step 2124, dealer client device 2010 displays the status and approval code report.

(73) At optional step 2126, administration server 2004 sends the status and approval code report to administration client device 2006.

(74) At optional step 2128, administration client device 2006 displays the status and approval code report.

(75) At step 2130, a user product application request is generated by user client device 2002.

(76) At step 2132, user client device 2002 sends the user product application request, which is received by dealer server 2008.

(77) At optional step 2134, a dealer product application request is generated by dealer client device 2010.

(78) At optional step 2136, dealer client device 2010 sends the dealer product application request to dealer server 2008.

(79) At step 2138, an application schedule is calculated and an alert is generated by dealer server 2008.

(80) At step 2140, the product application schedule alert is sent from dealer server 2008 to dealer client device 2010.

(81) At step 2142, the product application schedule alert is displayed by dealer client device 2010.

(82) At optional step 2144, dealer server 2008 sends the product application schedule alert to user client device 2002.

(83) At optional step 2146, the product application schedule alert is displayed by user client device 2002.

(84) At step 2148, application process measurements are collected by dealer client device 2010. Hence, efficacy of the TiO2 re-application is measured through bacteria count or TiO2 thickness for a given surface or set of surfaces. This measurement is taken before the second application of TiO2 to the vehicle.

(85) At step 2150, a vehicle selection and measurement alert is generated by dealer client device 2010. In a preferred embodiment, the vehicle selection is made by the dealer in order to identify which vehicle is being treated.

(86) At step 2152, the vehicle selection and measurement alert is sent from dealer client device 2010 to vendor server 2016.

(87) At optional step 2154, the vehicle selection and measurement alert is sent from dealer client device 2010 to dealer server 2008.

(88) At optional step 2156, the vehicle selection and measurement alert is sent from dealer server 2008 to vendor server 2016.

(89) At optional step 2158, vendor server 2016 sends the vehicle selection and measurement alert to vendor client device 2018.

(90) At optional step 2160, vendor client device 2018 displays the vehicle selection and measurement alert.

(91) At step 2161, the vehicle selection and the measurements are compared. In a preferred embodiment, the comparison is against one or more formulas in a database that identify the spray pressure, spray duration, and chemical composition as functions of the vehicle interior volume, vehicle interior surface area. The database also includes one or more tables that specify changes to spray pressure, spray duration, and chemical composition based on the materials of the interior and manufacturer of the vehicle. Spray pressure, spray duration, and chemical composition are all included in the settings and parameters in an application process update alert.

(92) If the measurement is below about 50%, of its prior level, then substantially the same particle size, chlorine dioxide percentage, and pressure are used as from that last treatment. In a preferred embodiment, when the bacteria level, measured in relative light units (RLUs), is in a range of about 50% to about 70% of its prior level, then the particle size of the airborne suspension is adjusted from about 30 microns downward to about 20 microns. In this way, a greater depth of surface penetration is achieved. When the bacteria level is in the range of about 70% to about 90% of the prior level then in addition to reduction in particle size, the percentage of chlorine dioxide by weight is increased by about 5%. In this way, the suspension is adjusted to become more lethal to recurring bacteria. In situations above 90%, the application pressure and flowrate are increased by about 20% in addition to the adjustment in particle size and increased chlorine dioxide. In a preferred embodiment, initial application pressure is between about 90 psi and about 100 psi. In a preferred embodiment, initial application flowrate is 2.5 oz/min.

(93) At step 2162, vendor server 2016 generates an application process update alert. In a preferred embodiment, an application process update alert is generated when an application of the TiO2 suspension is complete.

(94) At step 2164, vendor server 2016 sends the application process update alert, which is received by dealer client device 2010.

(95) At optional step 2166, vendor server 2016 sends the application process update alert to dealer server 2008.

(96) At optional step 2168, the application process update alert is sent from dealer server 2008 to dealer client device 2010.

(97) At optional step 2170, vendor server 2016 sends the application process update alert to vendor client device 2018.

(98) At optional step 2172, vendor client device 2018 displays the application process update alert.

(99) At step 2174, the application process update alert is displayed by dealer client device 2010.

(100) At step 2175, the application process is performed, which is further described in FIG. 5. In a preferred embodiment, the user of dealer client device 2010 follows the instructions received from vendor server 2016 for generating correct chemical composition of the TiO2 solution and using the correct pressure spray settings.

(101) At step 2176, dealer client device 2010 collects application process measurements. In a preferred embodiment, this measurement is taken after the second application of TiO2 so that a comparison can be made prior application process measurements.

(102) At step 2178, an application measurements alert is generated by dealer client device 2010.

(103) At step 2180, the application measurements alert is sent from dealer client device 2010 to dealer server 2008.

(104) At step 2182, a product application report is generated by dealer server 2008. In a preferred embodiment, the report includes a measure of efficacy of the TiO2 application and the number of TiO2 applications left for the term of the insurance contract.

(105) At step 2184, the product application report is sent from dealer server 2008 to user client device 2002.

(106) At step 2186, user client device 2002 displays the product application report.

(107) At step 2188, the product application report is transmitted from dealer server 2008 and subsequently received by dealer client device 2010.

(108) At step 2190, dealer client device 2010 displays the product application report.

(109) At step 2192, a surety claim request is generated by dealer server 2008. In a preferred embodiment, the claim request is a request for payment under the insurance contract.

(110) At step 2194, dealer client device 2010 sends a surety claim request alert to administration server 2004.

(111) At optional step 2196, dealer client device 2010 sends the surety claim request alert, which is received by dealer server 2008.

(112) At optional step 2198, the surety claim request alert is transmitted from dealer server 2008 and subsequently received by administration server 2004.

(113) At optional step 2200, the surety claim request alert is sent from administration server 2004 to administration client device 2006.

(114) At optional step 2202, administration client device 2006 displays the surety claim request alert.

(115) At step 2204, a claim approval request is generated by administration server 2004.

(116) At step 2206, a claim approval request alert is transmitted from administration server 2004 and subsequently received by surety server 2012.

(117) At optional step 2208, the claim approval request alert is sent from surety server 2012 to surety client device 2014.

(118) At optional step 2210, surety client device 2014 displays the claim approval request alert.

(119) At step 2212, surety server 2012 generates a claim status and approval code.

(120) At optional step 2214, surety server 2012 sends the claim status and approval code, which is received by surety client device 2014.

(121) At optional step 2216, surety client device 2014 displays the claim status and approval code.

(122) At step 2218, the claim status and approval code is transmitted from surety server 2012 and subsequently received by administration server 2004.

(123) At optional step 2220, the claim status and approval code is transmitted from administration server 2004 and subsequently received by administration client device 2006.

(124) At optional step 2222, the claim status and approval code is displayed by administration client device 2006.

(125) At step 2224, a claim status report is generated by administration server 2004.

(126) At step 2226, the claim status report is sent from administration server 2004 to dealer client device 2010.

(127) At optional step 2228, administration server 2004 sends the claim status report to dealer server 2008.

(128) At optional step 2230, the claim status report is transmitted from dealer server 2008 and subsequently received by dealer client device 2010.

(129) At step 2232, the claim status report is displayed by dealer client device 2010.

(130) At optional step 2234, administration server 2004 sends the claim status report to administration client device 2006.

(131) At step 2236, administration client device 2006 displays the claim status report.

(132) Referring to FIG. 3, a method 300 of organizing repeated treatments of TiO2 solution to a vehicle interior will be described. Beginning at step 305, the dealership enters into a contract with the product vendor, whereby the dealership agrees to use system 100. At step 310, a vehicle owner enters into a contract with the dealership, whereby the vehicle owner will receive treatments with the TiO2 solution. At step 315, the dealership reports that a contract has been agreed to via dealer client device 152, and the system 100 alerts the vendor. At step 320, the dealership treats the vehicle with TiO2 solution. At step 325, the dealership optionally enters into a contract with an administrator, whereby the administrator interfaces with surety servers 164 and surety client devices 176 on behalf of the dealership. At step 330, the dealership enters into a surety contract with a surety, whereby the surety guarantees the contract between the dealership and a vehicle owner. At step 335, the dealership performs additional treatments of the vehicle reports them via dealer client device 152. At step 340, the dealership may optionally generate and transmit a notice to the surety of a claim under the surety contract. At step 341, the claim is either accepted or denied. The method then repeats steps 335 through 341 as the vehicle owner returns to the dealership for future reapplications of the TiO2 solution, until the contract between the dealership and the vehicle owner expires.

(133) Referring to FIG. 4, a method 400 for generating and transmitting notices between a dealership and a vendor. Beginning at step 405, the dealership enters into a contract with the vendor. At step 410, the vendor determines a dealer cost Y. In one embodiment, Y is a fixed amount charged to the dealership, calculated based on the amount of TiO2 solution that the dealership orders. In another embodiment, Y is a recurring cost assessed to the dealership at set time intervals, such as monthly or quarterly. In a preferred embodiment, Y is a fixed cost per customer contract. At step 415, the vendor ships the dealership an initial amount B (in gallons) of TiO2 solution, equipment for the application of the TiO2 solution, and training materials instructing the dealership in the proper use of the equipment and application of the TiO2 solution. At step 420, the vendor enters dealership into the allocation software. The allocation software functions to track usage of TiO2 solution and generate corresponding shipment alerts and billing entries. In one embodiment, the allocation software runs on dealer server 140, and is configured to transmit notifications to vendor client device 105, vendor server 188, or both. In a preferred embodiment, the allocation software runs on the vendor server 188 and is accessible by vendor client device 105 and dealer client device 152 via the internet 102. At step 425, the vendor records in the allocation software the shipment of the TiO2 solution to the dealership. At step 430, the dealership receives the shipment of TiO2 solution, application equipment, and training materials, and trains the appropriate staff to treat vehicles with TiO2 solution. At step 435, the dealership determines a treatment price A. In one embodiment, A is a fixed cost per treatment. In another embodiment, A is a sliding scale depending on the number of previous treatments applied to that vehicle, with higher values of A assigned when the vehicle has gone for long periods of time without treatment. Other embodiments are possible, and determination of A may be influenced by a number of factors, including the make, model, and age of the vehicle, the climate, especially the amount of sunlight and moisture experienced or expected, and known driving habits of the vehicle owner, such as infrequent uses of the vehicle and storage away from sunlight. At step 440, the dealership determines a reapplication period P, measured in months. At the end of reapplication period P, the vehicle will need to be re-treated with TiO2 solution. In a preferred embodiment, reapplication period P is between about 6 and about 18 months, and ideally 12 months. At step 445, the dealership determines a set of treatment contracts [K.sub.1, K.sub.2, K.sub.3 . . . ] to be offered to vehicle owners. Set of contracts [K.sub.1, K.sub.2, K.sub.3 . . . ] may be offered in increments of reapplication period P. Vehicle owners may agree to enter into a contract K.sub.n such that K.sub.n lasts for (nP) months and involves (n+1) treatments. At step 450, the dealership determines a set of prices [X.sub.1, X.sub.2, X.sub.3 . . . ] corresponding to set of contracts [K.sub.1, K.sub.2, K.sub.3 . . . ]. In a preferred embodiment:
X(A(n+1))+YEq. 1

(134) where: X=contract price A=cost/application n=number of treatments Y=dealer cost

(135) Referring to FIG. 5, a method 500 for the treatment of a vehicle with TiO2 solution. Beginning at step 505, the dealership cleans the interior of the vehicle in preparation for treatment of the interior with the TiO2 solution. Soap and water plus a diluted solution of chlorine bleach is recommended. The TiO2 solution is an aqueous solution of TiO2 that leaves TiO2 nanoparticles embedded in the surfaces of a vehicle's interior. Thorough cleaning is required before treatment with TiO2 solution to allow the TiO2 sufficient contact of the suspension with all interior surfaces. At step 507, bacteria contamination levels are tested and logged. At step 510, the dealership determines the formula of the TiO2 solution to be applied and configures the application equipment. In a preferred embodiment, the contamination test results are entered into the system, which then derives a proper formulation and pressure settings. In another embodiment, the dealer client device 152 receives notifications from vendor server 188 with instructions regarding the proper formula to use based on test results. In an alternate embodiment, the vendor prepares the solution and the dealership receives it pre-mixed based on a generalized application schedule. The application equipment is configured to produce the proper airborne suspension. In a preferred embodiment, the initial application includes particle sizes of between about 20 and 40 microns. In a preferred embodiment, the application equipment is a physical suspension vaporizer that is configured to produce droplets with a diameter of approximately 25 to 30 microns delivered at about 95 psi. In a preferred embodiment, the physical suspension vaporizer is a B&G fogger model no. 2300 available from B&G Equipment, Co. of Atlanta, Ga. At step 515, the dealership seals all vehicle openings, then applies the suspension through an intake air vent or window of the vehicle. In one embodiment, approximately 4 ounces of TiO2 solution dispensed for a 4 passenger vehicle. In a preferred embodiment, the amount is calibrated based on the interior surface area known to exist for the make and model of the vehicle. The amount of adjustment is approximately 20% less for 2 passenger vehicles and 20% more for 6 passenger vehicles. In general, addition of 20% more solution is added for every addition of 2 passenger capacity. At step 520, the vehicle resealed. The vehicle is left undisturbed for 1-2 minutes to allow the suspension to cure. At step 525, interior surfaces are wiped, removing the excess (now dry) solution, leaving TiO2 nanoparticles embedded in all interior surfaces. At step 530, the vehicle is certified as treated. In one embodiment, the certification may comprise applying a sticker to the vehicle, indicating that it has been treated with the TiO2 solution. In another embodiment, the certification may comprise a database entry, recording that the vehicle has been treated with the TiO2 solution in the records of the dealership. In a preferred embodiment, the certification comprises placing a sticker with the date of the treatment on the vehicle windshield, to be replaced when future treatments are applied. At step 535, the dealership logs into the allocation software via dealer client device 152 and reports that a treatment was applied. At step 540, the dealership returns the vehicle to the owner.

(136) Referring to FIG. 6, a method 600 for tracking the performance of the dealership and the vendor. Beginning at step 604, the dealership logs into the allocation software. At step 605, the dealership elects to either proceed to step 610 and report the treatment of a vehicle, or proceed to step 640 and report the existence of a new contract with a vehicle owner. Proceeding then to step 610, the dealership reports that a vehicle was treated with the TiO2 solution. The method continues to step 615, whereby the allocation software logs the treatment by the dealership, and updates a corresponding database entry to reflect a lower amount for the dealership's inventory amount of the TiO2 solution. In one embodiment, the allocation software subtracts amount of solution used from the inventory amount. At step 620, the allocation software compares the new database entry reflecting the dealership's inventory amount of solution to a threshold shipment amount. If the dealership has more inventory than the threshold shipment amount, then the method proceeds to step 635, and the program terminates. At step 620, if the dealership's inventory amount is less than the threshold amount, then the method proceeds to step 625. At step 625, the allocation software triggers a request for shipment from the vendor. At step 630, the vendor ships replacement supplies to the dealership. At step 631, the program terminates.

(137) Returning to step 605, if the dealership reports a new contract, then the method proceeds to step 640. At step 640, the dealership uses the allocation software to record that a new contract for TiO2 solution treatments. The dealership inputs the relevant data for the contract, including the vehicle owner contact information, number of future retreatments of the vehicle and the time intervals at which retreatments are required. The method then proceeds to step 645, where the allocation software creates a billing entry, reflecting the amount Y owed by the dealership to the vendor. In one embodiment, the allocation software accumulates billing entries and generates a periodic bill sent to the dealership. The method then proceeds to step 650, whereby the dealership pays the vendor payment Y.

(138) Referring to FIG. 7, a method 700 for generating and transmitting notices between a dealership and a surety. Beginning at step 705, the dealership enters into a surety contract with a surety, guaranteeing performance of the dealership's contract with a vehicle owner. At step 710, the surety determines a premium amount W. At step 715, the dealership pays W to the surety. At step 716, the dealership determines the customer action, and the method then proceeds in one of three ways. If the vehicle owner returns to the dealership for a retreatment of the TiO2 solution, then the method proceeds to step 720. If the vehicle owner cancels the contract with the dealership, then the method proceeds to step 740. If the contract between the dealership and the vehicle owner expires, then the method proceeds to step 755.

(139) At step 720, the dealership determines the eligibility of the vehicle owner to receive a treatment. If the vehicle owner is eligible, the method proceeds to step 725, at which point the dealership provides the vehicle owner with a new treatment of the TiO2 solution. At step 730, the dealership re-certifies that the vehicle has been treated with the TiO2 solution. At step 735, the dealership generates and transmits to the surety notice that of a claim under the surety contract. At step 736, the claim is either accepted or denied.

(140) Returning to step 716, if the vehicle owner cancels the contract with the dealership, the method proceeds to step 740. At step 740, the surety determines a refund amount R or a cancellation penalty. In one embodiment, R is calculated by subtracting the per-treatment amount A (calculated in step 435) multiplied by n, the number of times that the vehicle has been treated already, from X, the total contract price. In a preferred embodiment:
R=X(Y+(An))Eq. 2

(141) where: R=refund amount or calculated penalty A=per-treatment amount X=total contract price Y=dealer cost

(142) At step 745, the dealership refunds R to the vehicle owner. At step 750, the dealership generates and transmits to the surety notice that of a claim under the surety contract. At step 751, the claim is either accepted or denied.

(143) Returning to step 716, if the contract between the dealership and the vehicle owner expires, then the method proceeds to step 755. At step 755, the dealership determines the expiration of the contract, and the method terminates.

(144) Referring to FIG. 8, table 800 of chemical ingredients, by % weight, for a preferred embodiment of a TiO2 aqueous solution for use in the vehicle application. Chemical Abstracts Service numbers are included in the center column. The solution is prepared by combining the water and TiO2 and mixing thoroughly, allowing the TiO2 to evenly disperse in solution. Other chemical components are added in rapid succession thereafter, while mixing. In a preferred embodiment, DI water is provided at 100 F. and is maintained as this temperature during agitation. TiO2 should dissolve in solution. If not, agitation is continued, while the temperature is raised to 120 F., until a homogenous solution is achieved.

(145) Referring to FIG. 9, graph 900 shows efficacy test measurement levels for multiple readings. The efficacy test measurements are performed on the vehicle before and then after the TiO2 application process. Tests can be done on the same surface or on a number of surfaces. However, the surface(s) tested must be the same from test to test. For example, initial reading 1 is performed when the vehicle is new. Readings 2, 3, and 4 are performed on the one year anniversaries when the vehicle is returned for re-application. In a preferred embodiment, the process settings and parameters are changed based on changes in measured bacterial infestation from test to test. The process parameters include the TiO2 solution formulation, the application pressure, and the curing time. The measurements are performed using relative light units (RLUs), which measure the amount of adenosine triphosphate (ATP) present on the surface. Adenosine triphosphate is used by organisms and organic matter as a unit of energy so that elevated levels of adenosine triphosphate indicate an increased likelihood of the presence of bacteria. In an example set of tests, reading 1 shows the before treatment value of 2.4 RLUs and an after treatment value of 0.1 RLUs. Reading 2 shows a before treatment RLU value of 4.4 and after treatment value of 0.025 RLUs. Reading 3 indicates a before treatment value of RLUs and an after treatment value of 0.4 RLUs. Reading 4 shows a before treatment value of 2.8 RLUs and an after treatment value of 0.2 RLUs.

(146) Referring to FIG. 10, graph 1000 shows bacterial levels. Graph 1000 may be provided by system 100 to user client device 104 with dealer server 140 after each time the vehicle is brought in treatment. In an example set of tests, the top line for untreated values had RLU measurements of 3, 3.1, 2.9, and 3.2 for readings 1 through 4. The bottom line shows after treatment readings 1 through 4 with RLU measurements of 0.2, 0.4, 1, and 0.1.

(147) Referring to FIG. 11, graph 1100 shows bacteria eradication test results. In an example set of tests, the relative frequency of non-zero readings is at 0.98 for untreated surfaces and at 0.15 for treated surfaces.