This invention relates generally to a system and method for tracking refrigerant loss and repairing commercial HVAC and refrigeration systems. More specifically, it relates to system for complying with the EPA's regulations governing equipment using ozone depleting refrigerants.
In Section 608 of Title IV of the Clean Air Act Amendments of 1990, Congress called for the Environmental Protection Agency (“EPA”) to promulgate regulations regarding the use, recycling, and disposal of ozone-depleting substances. Included in these ozone-depleting substances are industrial process and commercial refrigeration systems. Pursuant to this statutory mandate, the EPA enacted a series of regulations, which are summarized in a document that it prepared in conjunction with the Chemical Manufacturers Association, entitled “Compliance Guidance for Industrial Process Refrigeration Leak Repair Regulations Under Section 608 of the Clean Air Act,” dated October 1995, which is incorporated herein by reference in its entirety. A copy of this document is attached hereto as Attachment “A.”
Recently, the EPA has levied several significant fines for failure to comply with these Section 608 regulations regarding class I or class II refrigerants. Class I refrigerants are generally chlorofluorocarbon (“CFC”) refrigerants or any refrigerant mixture containing a CFC. Class II refrigerants are hydrochlorofluorocarbon (“HCFC”) refrigerants or any refrigerant mixture containing an HCFC. The regulations require, among other provisions, that owners or operators of commercial refrigeration systems track refrigerant leaks, repair the equipment using certified technicians, and retrofit or retire systems exceeding a certain leak threshold. The regulations also require an appropriate record keeping of these activities surrounding the refrigeration systems.
Accordingly, there is a need in the art for a system or method for tracking refrigerant loss in equipment subject to the EPA regulations and ensuring compliance with those regulations. There is a further need for a system for complying with the extensive requirements relating to repair, retrofit, or retirement of refrigeration systems.
The present invention, in one embodiment, is a network-based equipment management system. The system includes first database including a plurality of characteristics relating to a piece of equipment located at a site. The system also includes a server including software for tracking a refrigerant characteristic of the piece of equipment. The server also includes further software to generate a notification relating to the refrigerant characteristic.
In another embodiment, the present invention is a method of equipment management. The method includes maintaining at a first database a plurality of characteristics relating to a piece of equipment located at a site. The method further includes tracking with software a refrigerant characteristic of the piece of equipment based on the plurality of characteristics, the software being in a server. The method also includes generating at the server a notification relating to the refrigerant characteristic.
While multiple embodiments are disclosed, still other embodiments of the present invention will become apparent to those skilled in the art from the following detailed description. As will be apparent, the invention is capable of modifications in various obvious aspects, all without departing from the spirit and scope of the present invention. Accordingly, the drawings and detailed description are to be regarded as illustrative in nature and not restrictive.
The asset database 32 includes general asset information relating to all the client's assets and maintenance information for each asset. The asset information may include site information relating to all sites where the client has assets, including site location, identification of assets at the site, and other relevant site information. The asset information may also include manufacturer information, supplier information, warranty information, and any other relevant information for each asset. If the asset is one part of a system comprised of more than one asset, the asset information may include system information, including the system name, description of the system, identification of the assets in the system, system status, along with any other relevant information. The system status options may include, without limitation, normal operation, provisional operation, under repair, or being retrofitted.
According to one embodiment, if the asset is a piece of refrigeration equipment, the asset database 32 includes refrigeration equipment information and repair, retrofit, or retirement information. The refrigeration equipment information may include identification of the type of refrigeration equipment. For example, the asset may be HVAC equipment. The refrigeration equipment information may also include an EPA category, certification type required of the service provider by the EPA, the amount of refrigerant when the asset is fully charged, the refrigerant charge determination method, the refrigerant type, the refrigerant circuit the equipment is associated with, all past work orders (including the amount of refrigerant used) that have been performed on the system, or any assets attached to the system, such as refrigerated cases or HVAC systems, and any other relevant information. Some options for the refrigerant charge determination method may include measurement, calculation, manufacturer's information, or establish range. Examples of refrigerant type include R-22, 12/152a blend, 22/115 blend, and 401A (MP39). Further, the database 32 can include any additional information known to be useful in asset management.
The service provider database 34 includes general service provider information and certification information for each service provider available to service an asset. The service provider information may include the name of the service provider, a description, an address, a phone number, a mobile phone number, a fax number, an e-mail address, a username and password to log onto the system of the present invention, technician names, and any other relevant information. The certification information may include a qualification type, a certificate number, an expiration date for the certificate, a status, and any other relevant information. According to one embodiment, the certification information is associated with technicians.
In an alternative embodiment, the system of the present invention is implemented in conjunction with a network-based enterprise asset management system for managing the assets of a distributed enterprise. One example of such a system is disclosed in co-pending U.S. patent application Ser. No. 09/883,779, entitled “Method and System for Managing Enterprise Assets,” filed on Jun. 18, 2001, which is incorporated herein by reference in its entirety.
According to one embodiment, the system of the present invention performs the calculation using information in the asset database, including pounds of refrigerant in a full charge and days since refrigerant last added. Alternatively, the system of the present invention calculates the leak rate for a piece of equipment for any desired time period based on more than one service event. In a further alternative, the system calculates the leak rate for an entire system, an entire site, or an entire enterprise (comprised of more than one site).
Alternatively, data is collected for the equipment database 32 with a survey tool. In a further alternative, data is collected for any database in the system with a survey tool. One example of such a tool is disclosed in co-pending U.S. patent application No. 60/444,437, entitled “Site Equipment Survey Tool,” filed on Feb. 3, 2003, which is incorporated herein by reference in its entirety.
If the equipment is subject to the regulations and based on the client, the site (i.e., location), and the particular piece of equipment, a certified service provider is selected (block 48) who completes the necessary repairs to the equipment and refills the refrigerant if necessary. In one embodiment, the service provider then completes an associated work order (block 50). The details of the repair are then recorded (e.g., entered into a database) and associated with the piece of equipment repaired (block 52). A leak rate for the refrigeration system (which may include other components) is then calculated (block 54) as described herein.
According to one embodiment, the system 100 receives information from the asset using a notification system. One example of such a system is disclosed in co-pending U.S. patent application Ser. No 60/433,179, entitled “Notification System,” filed on Dec. 13, 2002, which is incorporated herein by reference in its entirety.
To limit access to authorized users, in one embodiment, the subject invention allows for various types of users and users at various distributed sites to have distinct levels of access. For example an enterprise or store user, in one embodiment, has full access to all assets and all pending work orders pertaining to his or her store. A service provider user has access to all assets of a type that he services and all work orders that he is responsible for fulfilling. These assets may include assets located at various distributed sites and may even include assets owned by distinct enterprises. An equipment manufacturer may have access to the assets at the various distributed sites that it manufactured.
Levels of access can be controlled by specifying securable or configurable attributes for each system user. These attributes can be specified by a system administrator, who may be an enterprise asset management company or may be with the enterprise itself. In one embodiment, the securable attributes are pre-defined based on the type of user. For example, user can have access to assets based on hierarchical levels within an enterprise. If the user is a regional manager, he will have access to assets in all of the locations of his store within his region. If the user is manager of a particular location, access may be limited to assets within that particular location.
The user's level of access can also be defined by his assigned roles and rights. Like the User's securable attributes, the user's roles and rights may be pre-specified by using a type of user, such as a “store manager.” Based on the user's type, he is given certain rights and roles. In one example, the rights that are granted or denied include the right to create new users (having access at the current user's level or below), the right to add or modify assets, and the right to submit work orders.
Returning to
In one embodiment, a notification report is triggered when the calculated leak rate exceeds the maximum EPA guidelines. In other words, a notification is generated if the leak rate exceeds 35% for a refrigeration system and 15% for an HVAC system. In another embodiment, notification is generated when the leak rate reaches a specified percentage of the guideline leak rate. An exemplary user interface for allowing a system user to specify reports is shown in
The schedule for providing notification is then selected (block 72). According to one embodiment, the notification is a report that can be scheduled to be distributed on a routine basis, such as daily, weekly, or monthly. Alternatively, the report can be scheduled for a one-time distribution. In a further alternative, the notification is an alert that is scheduled to be distributed only upon the crossing of a predetermined threshold related to one of the criteria. For example, the alert may be sent when the leak rate for a particular asset or system reaches a predetermined amount, when the number of service events related to refrigerant in a particular asset or system reach a predetermined number, or when the amount of refrigerant added to a particular asset or system reaches a predetermined amount.
A location for distribution of the notification is then selected (block 74). The location may be the e-mail addresses of one or more people. Alternatively, the location may be one or more telephone numbers. In a further alternative, the location is any known location for sending an electronic notification. Finally, the notification information is saved to the system of the present invention (block 76). A further aspect of the present invention is a system for coordinating the repair of refrigeration equipment pursuant to the EPA Section 608 requirements. The guidelines allow for either repair or retrofit.
If the first fix attempt is unsuccessful, the system provides notification relating to the deadline for a second fix attempt (block 82). According to one embodiment, the notification is a mandatory notification sent out on the date of the deadline. Alternatively, the system is modifiable to allow for a notification at some point prior to the date of the deadline. In a further alternative, the system provides for both a prior notification and the mandatory notification on the date of the deadline.
If the first or second fix attempt is successful, the system allows for notification relating to the deadline for mandatory follow-up testing (block 86). According to one embodiment, the notification is a mandatory notification sent out on the date of the deadline. Alternatively, the system is modifiable to allow for a notification at some point prior to the date of the deadline. In a further alternative, the system provides for both a prior notification and the mandatory notification on the date of the deadline.
If the first and second fix attempts are unsuccessful, the system allows for changing the status of the asset or removing the asset from the system due to retirement (block 84). Alternatively, the system allows for further notifications relating to further fix attempts.
The system further provides notification relating to the deadline to submit a request to the EPA for an extension of the deadline of additional time is needed to complete the plan (block 92). According to one embodiment, the notification is a mandatory notification sent out on the date of the deadline. Alternatively, the system is modifiable to allow for a notification at some point prior to the date of the deadline. In a further alternative, the system provides for both a prior notification and the mandatory notification on the date of the deadline.
If a request for an extension is granted, the system allows for notification relating to the extended deadline to complete the retrofit or retirement of the asset (block 94). According to one embodiment, the notification is a mandatory notification sent out on the date of the extended deadline. Alternatively, the system is modifiable to allow for a notification at some point prior to the date of the extended deadline. In a further alternative, the system provides for both a prior notification and the mandatory notification on the date of the extended deadline.
If no request for an extension is submitted or the request is not granted, the system allows for providing notification relating to the deadline to complete the retrofit or retirement of the asset (block 96). Alternatively, the system allows for additional notifications as additional deadlines are added during the retrofit or retirement process.
In an alternative embodiment, the system 30 prompts for the required inputs and generates a customized plan for repair/retirement/retrofit, based on responses from the user. In one alternative embodiment, the system 30 recommends a repair or retrofit plan, based on the responses from the user. In another embodiment, a standard plan is generated and communicated to the user. In a further embodiment, all documents and instructions associated with the plan are stored on one of the databases to facilitate dissemination to all responsible parties as needed.
Although the present invention has been described with reference to preferred embodiments, persons skilled in the art will recognize that changes may be made in form and detail without departing from the spirit and scope of the invention.
This application is a continuation of application Ser. No. 10/429,619 filed May 5, 2003, which claims the benefit of U.S. Provisional Application No. 60/432,120, filed Dec. 9, 2002, and said application Ser. No. 10/429,619 filed May 5, 2003, is a continuation-in-part of U.S. patent application Ser. No. 09/883,779, filed on Jun. 18, 2001, which claims the benefit of U.S. Provisional Application No. 60/212,234, filed on Jun. 16, 2000, and U.S. Provisional Application No. 60/288,827, filed on May 5, 2001.
Number | Name | Date | Kind |
---|---|---|---|
4612620 | Davis et al. | Sep 1986 | A |
4688026 | Scribner et al. | Aug 1987 | A |
4755957 | White et al. | Jul 1988 | A |
4989141 | Lyons et al. | Jan 1991 | A |
5079930 | Beaverson et al. | Jan 1992 | A |
5198774 | Williams, II et al. | Mar 1993 | A |
5231841 | McClelland et al. | Aug 1993 | A |
5434775 | Sims et al. | Jul 1995 | A |
5537313 | Pirelli | Jul 1996 | A |
5572438 | Ehlers et al. | Nov 1996 | A |
5629687 | Sutton et al. | May 1997 | A |
5732401 | Conway | Mar 1998 | A |
5748956 | Lafer et al. | May 1998 | A |
5752244 | Rose et al. | May 1998 | A |
5758126 | Daniels | May 1998 | A |
5821937 | Tonelli et al. | Oct 1998 | A |
5831610 | Tonelli et al. | Nov 1998 | A |
5845265 | Woolston | Dec 1998 | A |
5859778 | Kuroda et al. | Jan 1999 | A |
5860286 | Tulpule | Jan 1999 | A |
5910776 | Black | Jun 1999 | A |
5918207 | McGovern et al. | Jun 1999 | A |
5923850 | Barroux | Jul 1999 | A |
5946662 | Ettl et al. | Aug 1999 | A |
5956658 | McMahon | Sep 1999 | A |
5980090 | Royal, Jr. | Nov 1999 | A |
5987903 | Bathla | Nov 1999 | A |
5996889 | Fuchs et al. | Dec 1999 | A |
6088796 | Cianfrocca et al. | Jul 2000 | A |
6128602 | Northington et al. | Oct 2000 | A |
6154738 | Call | Nov 2000 | A |
6169979 | Johnson | Jan 2001 | B1 |
6211782 | Sandelman et al. | Apr 2001 | B1 |
6237020 | Leymann et al. | May 2001 | B1 |
6293114 | Kamemoto | Sep 2001 | B1 |
6298333 | Manzi et al. | Oct 2001 | B1 |
6385510 | Hoog et al. | May 2002 | B1 |
6430542 | Moran | Aug 2002 | B1 |
6437692 | Petite et al. | Aug 2002 | B1 |
6460082 | Lumelsky et al. | Oct 2002 | B1 |
6650346 | Jaeger et al. | Nov 2003 | B1 |
6892546 | Singh et al. | May 2005 | B2 |
6952680 | Melby et al. | Oct 2005 | B1 |
7032241 | Venkatachary et al. | Apr 2006 | B1 |
7062389 | Johnson et al. | Jun 2006 | B2 |
7062446 | Suhy, Jr. et al. | Jun 2006 | B1 |
7124059 | Wetzer et al. | Oct 2006 | B2 |
7142949 | Brewster et al. | Nov 2006 | B2 |
7149701 | McKinney | Dec 2006 | B2 |
7196621 | Kochis | Mar 2007 | B2 |
7259675 | Baker et al. | Aug 2007 | B2 |
7304573 | Postma | Dec 2007 | B2 |
7333880 | Brewster et al. | Feb 2008 | B2 |
7369968 | Johnson et al. | May 2008 | B2 |
7440871 | McConnell et al. | Oct 2008 | B2 |
7474218 | Johnson et al. | Jan 2009 | B2 |
7496532 | Johnson et al. | Feb 2009 | B2 |
7512523 | Johnson et al. | Mar 2009 | B2 |
7647207 | McConnell et al. | Jan 2010 | B2 |
20010047383 | Dutta | Nov 2001 | A1 |
20020059364 | Coulthard et al. | May 2002 | A1 |
20020070971 | Brown et al. | Jun 2002 | A1 |
20020138361 | Chen | Sep 2002 | A1 |
20020143693 | van Soestbergen et al. | Oct 2002 | A1 |
20030069743 | Nordrum | Apr 2003 | A1 |
20030154141 | Capazario et al. | Aug 2003 | A1 |
20040019511 | McKinney | Jan 2004 | A1 |
20040024662 | Gray et al. | Feb 2004 | A1 |
20040078306 | Whiteley et al. | Apr 2004 | A1 |
20040095237 | Chen et al. | May 2004 | A1 |
20040111697 | Johnson et al. | Jun 2004 | A1 |
20040162642 | Gasper et al. | Aug 2004 | A1 |
20040193449 | Wildman et al. | Sep 2004 | A1 |
20040225676 | Johnson et al. | Nov 2004 | A1 |
20040249515 | Johnson et al. | Dec 2004 | A1 |
20050021710 | Johnson et al. | Jan 2005 | A1 |
20050086163 | Johnson et al. | Apr 2005 | A1 |
20050109829 | Postma | May 2005 | A1 |
20050154669 | Streetman | Jul 2005 | A1 |
20050205658 | Baker et al. | Sep 2005 | A1 |
20050246190 | Sandor et al. | Nov 2005 | A1 |
20050248454 | Hanson et al. | Nov 2005 | A1 |
20060142961 | Johnson et al. | Jun 2006 | A1 |
20060161450 | Carey et al. | Jul 2006 | A1 |
20060170889 | Honda | Aug 2006 | A1 |
20060187026 | Kochis | Aug 2006 | A1 |
20060256308 | Honda | Nov 2006 | A1 |
20070010914 | Johnson et al. | Jan 2007 | A1 |
20070043538 | Johnson et al. | Feb 2007 | A1 |
20070096899 | Johnson et al. | May 2007 | A1 |
20070260405 | McConnell et al. | Nov 2007 | A1 |
20070268138 | Chung et al. | Nov 2007 | A1 |
20080177605 | Zimmerman | Jul 2008 | A1 |
20080243687 | Johnson et al. | Oct 2008 | A1 |
20080255899 | McConnell et al. | Oct 2008 | A1 |
20090018884 | McConnell et al. | Jan 2009 | A1 |
20100070404 | McConnell et al. | Mar 2010 | A1 |
20100070423 | McDonnell et al. | Mar 2010 | A1 |
20100121770 | Johnson | May 2010 | A1 |
20100138190 | McConnell et al. | Jun 2010 | A1 |
Number | Date | Country |
---|---|---|
1566875 | Aug 2005 | EP |
10340846 | Dec 1998 | JP |
2004-301825 | Oct 2004 | JP |
WO 9941717 | Aug 1999 | WO |
WO 9966436 | Dec 1999 | WO |
WO 0017984 | Mar 2000 | WO |
0173612 | Oct 2001 | WO |
WO 0197146 | Dec 2001 | WO |
WO 0207365 | Jan 2002 | WO |
WO 02090914 | Nov 2002 | WO |
WO 2005048328 | May 2005 | WO |
WO 2005062351 | Jul 2005 | WO |
Number | Date | Country | |
---|---|---|---|
20090126388 A1 | May 2009 | US |
Number | Date | Country | |
---|---|---|---|
60432120 | Dec 2002 | US | |
60212234 | Jun 2000 | US | |
60288827 | May 2001 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 10429619 | May 2003 | US |
Child | 12360747 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 09883779 | Jun 2001 | US |
Child | 10429619 | US |