FIELD OF THE INVENTION The invention relates to computer-implemented data collection and storage systems, and in particular, data collection and storage systems for maintaining data about components of buildings.
BACKGROUND OF THE INVENTION Buildings, such as homes and other types of real property units, are complex systems comprising many separate and interacting components, including building materials, fixtures, appliances, and the like. Many of the components have associated installation and maintenance information, repair information, warranty information, and the like, that may be available to an installer, homeowner, occupant, or other interested party if the party knows how and where to find the information. Similarly, much construction-related information associated with a real property unit may be of value during its lifetime to the aforementioned parties as well as to a variety of other interested parties, such as insurance agents, real estate estimators, architects, city inspectors, and others, if the parties know how and where to access the information, and if, indeed, the desired information has been preserved.
Typically, however, much very useful information about a real property unit, and especially information that is generated during construction of the real property unit, is either not recognized as being of future value or is simply not preserved in a systematic, comprehensive, and logical manner.
For example, warranty information for components in a home or other building is typically not gathered and maintained in a manner that best serves the needs of the eventual owners of the building and the components. Many components of a new house are frequently covered by manufacturers' warranties, including kitchen appliances, heating/cooling systems, and bathroom fixtures. In addition to these visible components, other components, such as building materials, may also frequently be covered by warranties, unbeknownst to the ultimate homeowner or occupant. For example, packaging for vinyl siding or roofing materials or paint may contain warranty information that is thrown away without ever being brought to the homeowner's attention. Some warranties may be embedded in trade agreements with the builder of a home, such as a warranty on termite control work or on the workmanship of a roofer, and may not ever be given to a new home owner. Even when a home owner is left a folder or kitchen drawer full of warranty cards to fill out, the cards may sometimes require a serial number, model number, or other information from the component that is difficult or impossible to access once the component is installed.
Furthermore, registering a warranty does not spare the homeowner of subsequent confusion about the coverage. Expiration dates may be difficult to assess accurately because some products, like water heaters, have different warranty periods for different parts of the product. Many times it is difficult to know which component defects are covered by the builder and which are covered by the manufacturer, and for how long. Imprecise or out-of-date information provided to the manufacturer can complicate or nullify later coverage.
Warranties registered at the time of product purchase may incorrectly name a builder, contractor, or purchaser of a gift as the warrantee rather than the ultimate homeowner, and warrantee information is rarely updated upon sale or re-sale of a home. Warranty registration systems that register warranties at the time of product purchase or at the time of assumption of home ownership cannot typically provide installation date information that is frequently critical to warranty coverage, nor do they provide any mechanism for verifying, when required, that the component was installed by a certified or licensed installer.
With all of these difficulties, only about 2% of available warranties are typically registered with the manufacturer. Thus, manufacturers rarely know where, with whom, and by whom their products are installed. Manufacturers thereby lose the benefit of this valuable information for marketing and research purposes, as well as for accurately and efficiently providing homeowners with important safety alerts and recalls, maintenance information updates, and the like. Without accurate information about when and where their components are being installed, manufacturers also lose the opportunity to provide installers and users with updated or customized installation, maintenance, or use instructions that may take into account building type, geographical location, product compatibilities, or other such specialized considerations.
Currently available warranty registration systems typically rely on registrations at a point of sale or by an eventual home occupant. Such systems also typically use a street address to identify a component location, even though reliance on street addresses is known to be mistake-prone, at least in part because of misspellings and/or confusion between names like 2ndStreet and 2ndAvenue or between Grand Avenue N. and N. Grand Avenue. Furthermore, street names are occasionally changed over time, and accurate street names may not even be assigned at the time a component is purchased for a home in a new development. Currently available product information dissemination systems typically rely on a generic website format that does not provide for an interactive exchange of information between manufacturers and the eventual owners, users, installers, and repairmen of their products.
Systems are frequently even less well-developed for the gathering, maintaining, and disseminating of installation and care information for components of real property units.
SUMMARY OF THE INVENTION The present invention addresses these and other problems by providing a computer-based system for collecting, maintaining, and using information about buildings and their components, including, among others, construction, installation, maintenance, and use information. The computer-based system digitally links the physical address of an installed component to its manufacturer. One or more building identifier tags affixed to a building during construction include a unique building identifier for the building as well as access information allowing a user to access a computer-implemented repository of information about the building. The repository uses product identifier codes associated with components installed in the building to store information associated with the installed component The repository may comprise, among other types of information, information about components installed during construction of the building and their manufacturers, information about warranties associated with the components, information about the care and use of components in the building, information about workers who worked on the construction of the building, and/or information about quality checkpoints useful for checking and documenting the quality of construction of the building during construction. The repository may also facilitate registration of warranties and transmission of safety and recall information associated with building components, as well as targeted marketing of offers to residents of the building.
An embodiment of a computer-based communications system is described, wherein the system allows manufacturers of building components to identify and communicate with users associated with the building components. The communications system comprises: a product identifier code associated with a building component and affixed in a readable form to the building component or to the building component's packaging, a tag that is affixed to a real property unit at which the building component is or will be installed and that includes a unit identifier code that uniquely identifies the real property unit, and a computing system. The computing system is electronically accessible to a manufacturer of the building component and is configured to: receive an electronic notification that the building component associated with the product identifier code is or will be installed at the real property unit associated with the unit identifier code; electronically identify the manufacturer associated with the building component based on the product identifier code; transmit an electronic notification of the installation at the real property unit to the manufacturer; and provide the manufacturer with contact information that allows the manufacturer to transmit information to a user associated with the real property unit.
An embodiment of a system for collecting and maintaining information about components in a real property unit is described. The system comprises: a unit identifier tag that comprises a machine-readable and/or visually defined unit identifier code and that is affixed to a real property unit for uniquely identifying the real property unit, a product identifier code that identifies a component in the real property unit and that is affixed to the component or to packaging associated with the component, an input device for electronically obtaining the unit identifier from the unit identifier tag and the product identifier, and a software component. The software component is configured to receive the unit identifier code and the product identifier code from the input device and to store the unit identifier code and the product identifier code in a database record associated with the real property unit. The software component may be further configured to use the product identifier code to identify a manufacturer of the component and to communicate with the manufacturer.
An embodiment of a computer-implemented method for electronically registering a warranty for a building component used in the construction of a real property unit is described. The computer-implemented method comprises a step that includes receiving, at a computing system, information from an electronic device used during construction of a real property unit, wherein the information includes at least a unique unit identifier for the real property unit and a product identifier for a building component used in the construction of the real property unit. The computer-implemented method further comprises additional steps that include: using the product identifier to identify a manufacturer who manufactured the building component, establishing a computer-implemented contact with the identified manufacturer and providing information about the building component and about the real property unit in order to register a warranty for the building component, receiving a confirmation of the component's warranty registration, and storing a record of the warranty registration in the computing system.
An embodiment of a computer-implemented method for electronically providing current installation instructions for a building component used in the construction of a real property unit is described. The computer-implemented method comprises the steps of: receiving, at a computing system, information from an electronic device used during construction of a real property unit, wherein the information includes at least a unique unit identifier for the real property unit and a product identifier for a building component used in the construction of the real property unit; using the product identifier to identify a manufacturer who manufactured the building component; and establishing a computer-implemented communication with the identified manufacturer and providing information about the building component and about the real property unit in order to receive installation instructions for the building component.
An embodiment of a system for collecting, maintaining, and using information about construction, maintenance, and use features of buildings and their components is described. The system comprises one or more building identifier tags, a computer-implemented repository of information about the buildings, a first input device, and a building information access device. The one or more building identifier tags are affixed to buildings during construction of the buildings, and the one or more building identifier tags for each building including a unique building identifier for the building. The computer-implemented repository of information about the buildings comprises records associated with individual buildings. A record for a building includes the unique building identifier for the building and at least one of: information about components installed during construction of the building, information about manufacturers who manufacture the components installed in the building, information about warranties associated with the components, information about the care and use of components in the building, information about workers who worked on the construction of the building, and information about quality checkpoints useful for checking and documenting the quality of construction of the building during construction. The first input device is configured to electronically receive the unique building identifier and to send the unique building identifier to the computer-implemented repository of information. The building information access device is configured to electronically receive a request to access the computer-implemented repository of information. The building information access device is further configured to electronically receive a password and the unique building identifier for the building, and, if the password is valid, to use the unique building identifier to provide access to at least a portion of the records associated with the unique building identifier.
Neither this summary nor the following detailed description defines or limits the invention. The invention is defined by the claims.
BRIEF DESCRIPTION OF THE DRAWINGS A general architecture that implements various features of specific embodiments of the invention will now be described with reference to the drawings. The drawings and the associated descriptions are provided to illustrate embodiments of the invention and not to limit the scope of the invention. Throughout the drawings, reference numbers are re-used to indicate correspondence between referenced elements. In addition, the first digit of each reference number indicates the figure in which the element first appears.
FIG. 1 is a block diagram that provides a broad overview of one embodiment of a system for collecting, maintaining, and using information about construction, maintenance, and use features of real property units and their components.
FIG. 2 is a block diagram that provides a more detailed view of one embodiment of a central database system for use with the building information system depicted inFIG. 1.
FIGS. 3A and 3B depict two examples of building identifier tags.
FIG. 4A depicts one example of a web page for allowing users to interface with the central database system.
FIG. 4B depicts an example of a web page that allows a new home owner to register with the central database system.
FIG. 5 depicts one embodiment of a process for collecting, maintaining, and using information about construction, maintenance, and use features of real property units and their components.
FIG. 6 depicts one embodiment of a process for electronically registering a warranty for a building component used in the construction of a real property unit.
FIG. 7 depicts one embodiment of a process for electronically providing current installation instructions for a building component used in the construction of a real property unit.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Embodiments of systems and methods are described for collecting, maintaining, and using information about construction, maintenance, and use features of real property units and their components. In particular, a central database system, accessible to builders, owners, occupants, tradesmen, inspectors, manufacturers and other authorized parties of interest receives, maintains and provides information about real property units and their components.
Although the systems and methods have mainly been described for purposes of this disclosure as pertaining to homes, such as single-family detached residences, the systems and methods may pertain, in a variety of embodiments, to additional or alternative types of real property units. For example, in various embodiments, the central database system may receive, maintain, and provide information about duplexes and other multi-unit buildings, townhouses and other attached units, condominiums, apartments, as well as other types of buildings, such as offices and other commercial units, or even mobile home units.
Furthermore, the systems and methods have been described with reference to the figures to follow as receiving, storing, maintaining, and providing information about a variety of different “building components” or “products,” such as installed appliances, building materials, building systems, and other pre-manufactured components that are installed and/or otherwise used in a home. As will be described in greater detail, the information about the components may comprise, among other types of information, installation, use, and maintenance information, warranty information, product compatibility information, and the like. However, in a variety of embodiments, the systems and methods may also store warranty-related and other associated information for services that have been performed at the home, such as warranty information for pest control work, chimney maintenance, and the like, done at the home.
FIG. 1 is a block diagram that provides a broad overview of one embodiment of system for collecting, maintaining, and using information about construction, maintenance, and use features of real property units and their components. As depicted inFIG. 1, ahome100 is associated with unit identifier code (UIC)105 that may be encoded onto one or more home identifier tags110 which are affixed to thehome100. TheUIC105 uniquely identifies thehome100 and allows a variety of types of information about thehome100 to be easily stored and logically accessed in acentral database system120. A preferred embodiment includes a set of plastic cards that are affixed to thehome100, for example to its foundation, at the beginning of construction. The home identifier tags110 may include weatherproof bar codes, RFID devices, or other machine-readable or other systems of identification that allow thehome100 to be uniquely identified and in turn allow access to electronically stored data about thehome100, as will be described in greater detail in the disclosure that follows. As construction of thehome100 progresses, additional home identifier tags110 may be placed in other locations in thehome100, such as in an electric meter or sub panel, at a front entry foundation, in a basement, attic and garage and other areas as needed. Embodiments of thehome identifier tag110 will be described in greater detail with reference toFIGS. 3A and 3B.
As further depicted inFIG. 1, thehome100 includes one or more products or components with associated product identifier codes (PICs)115, which may be affixed to or encoded on the product and/or,the packaging of the products in a machine-readable or other form. Examples of products that may haveproduct identifier codes115 include, but are not limited to: appliances such as a dishwasher, garbage disposal, garage door opener, hot water system, thermostat system and the like; building components such as pipes, paint, roofing materials, windows and the like; and other installed components, such as lighting and plumbing fixtures, flooring and window treatment materials, and hardware for doors, cabinets, and closets. ThePIC115 may be used to identify the product type and themanufacturer170 of the product. ThePIC115 may be further used to uniquely identify the individual unit of the product that is being installed in thehome100.
Information about components in ahome100 may be stored in acentral database system120 or other type of computer-based system using thePIC115 for a component together with theUIC105 for thehome100 as indices. Furthermore, other construction-related and other information about thehome100 may be stored in thecentral database system120 in a form that is retrievable as a collective record of information about thehome100.
Although thecentral database system120 of the embodiment depicted inFIG. 1 resides in a single location, in other embodiments, thecentral database system120 may be implemented as a distributed system of hardware, software, and related components that function together across a variety of physical and/or geographical locations. Thus, the term “central” does not imply that all of the computers of thesystem120 reside in a common location; rather, the term is used to imply that these computers operate collectively as the main source of information about the associatedreal property units100 and their components.
Several types of entities may use theUIC105 and/or thePIC115 in conjunction with a computer-based communications system to send and receive information about thehome100 and/or about components in the home to and from thecentral database system120. Such entities include, but are not limited to: homeowners and/or occupants of thehome160; tradesmen, installers, repairmen, other construction workers, and/orinspectors150; builders and/orbuilding project developers140;manufacturers170 of the products and components used in thehome100; and otherauthorized parties180.
Theentities140,150,160,170,180 that use thecentral database system120 typically communicate with thecentral database system120 electronically, using a computer-basednetwork190 or other communications system, including, but not limited to, the Internet. Theentities140,150,160,170,180 may use any of a wide variety of computers or other electronic devices and any of a wide variety of communications techniques to access thecentral database system120. For example, the builder ordeveloper140 of ahome100 or housing development may initiate creation of a record for thehome100 in thecentral database system120, using a personal computer (PC) or other commonly available computer device. On the job site, aconstruction worker150, inspector, or supervisor may use any of a wide variety of wireless communications devices, such as personal digital assistants (PDAs), laptop or notebook computers, web-enabled cell phone devices, or the like to communicate with thecentral database system120. Alternatively, a computer device capable of communicating with thenetwork190, which has been ruggedized for use at a construction site, may be installed, semi-permanently at the job site for use in communications with thecentral database system120 during construction of thehome100. In other embodiments, information may be entered into an electronic device at the job site but may not be immediately transmitted to thecentral database system120 from the job site. Instead, the information may be transmitter later, such as when aninstaller150 with an electronic scanning device scans a home'sUIC105 and a component'sPIC115 at the jobsite and later uploads the scanned information onto a PC at another location for transmission to thecentral database system120. An owner oroccupant160 of thehome100 may similarly use any of the above-described devices, or others, to communicate with thecentral database system120. In some embodiments, a single computing device may be used to input both theUIC105 and thePIC115; in other embodiments, different computing devices may be used to input theUIC105 and thePIC115 separately.
In a preferred embodiment, an interface, such as a web site, for example, is provided through whichusers140,150,160,170,180 may access thecentral database system120. In addition to providing theUIC105 for the desiredhome100, users may be required to log in to thecentral database system120 using a pre-assigned passcode that may identify the type of user requesting access. A next web page for interacting further with the information in thecentral database system120 may be presented to the user based on the identified user type. The types of information about ahome100 that are accessible to a given user, and the types of information-access operations that can be performed (e.g., view, modify, delete, etc.), may be dependent upon the access rights or privilege level of that user (e.g.,owner160,developer140,manufacturer170,installer150, etc.), as will be described in greater detail with reference toFIG. 2. Furthermore, thecentral database system120 may implement an access control scheme to provide this functionality. In other embodiments, access may be controlled according to another scheme, or may be provided on an uncontrolled basis to users, who may or may not need to provide a passcode that identifies their type or privilege level.
TheUIC105 for thehome100 may be assigned by thecentral database system120 at the request of thebuilder140, preferably early in the design phase of thehome100. Information related to thathome100 may thus be collected and stored for the life of the home. Thebuilder140 may be prompted to enter any of a wide variety of types of information associated with thehome100 and, if applicable, with an overall development project of which thehome100 is a part. For example, thebuilder140 may enter information about the home's100 legal description, anticipated street address, anticipated construction schedule, size, number of stories, anticipated product and component list, including specific amenities such as fireplace, granite counters, paint selection by room, floor coverings, roofing material and type, and planned installation of various components such as rain gutters, swimming pools, filtration devices. Thebuilder140 may also enter information that may apply to some or all of the other homes in a development, such as builder name and contact information, geographic, climatic and geologic zones, links to blueprints and floor plans, links to relevant building and civil codes, anticipated construction schedule, job crew information, housing development information, and the like.
Thecentral database system120, together with the home'sUIC105 and thePICs115 of products in thehome100, may be further updated and used in a variety of ways by a variety oftradesmen150, including installers, inspectors, and later repairmen or other maintenance personnel. For example, aworkman150 hired to install an appliance or other product may use an electronic device to scan, electronically read, or otherwise capture the home'sUIC105 and the appliance'sPIC115 for transmission to thecentral database system120. In response, thecentral database system120 may access up-to-date installation information from themanufacturer170 that is stored bycentral database system120 or that is accessed from themanufacturer170 viacomputer network connection190 on an as-needed basis.
Although for purposes of this disclosure, amanufacturer170 is described as providing installation and other product-related information, as will be described in greater detail throughout this disclosure, it should be understood that another party, including, but not limited to, a representative or agent of themanufacturer170, may fulfill the functions described herein as being performed by themanufacturer170. For example, another party may perform functions related to warranty management, customer service, safety regulation compliance, replacement parts management, and marketing and promotion, either on behalf of themanufacturer170 or not. The use of the term “manufacturer” throughout this disclosure is to be understood to refer to amanufacturer170 or to another party who fulfills the functions described herein as being carried out by themanufacturer170.
When themanufacturer170 wishes to make available installation and/or maintenance instructions for a component that are customized based on the home's100 geographic location, climate zone, construction type, and/or other components used, thecentral database system120 preferably uses theUIC105 and thePIC115 to access stored information about thehome100 so that aninstaller150 may be provided with appropriate customized installation instructions for use at the job site. Such customized installation instructions may, for example, include specialized instructions for the home's local weather conditions or soil type or provide information about compatibility with other materials and products listed in thecentral database system120 as being used in thehome100.
In additional to installation instructions, amanufacturer170 may wish to provide an installer orother tradesman150 with access to a material safety data sheet (MSDS) that is mandated by the federal Occupational Safety and Health Administration (OSHA) to be included with many products. Typically, even when the original MSDS is outdated or lost, themanufacturer170 is still responsible for providing the safety information. The use of updated and downloadable MSDS safety sheets, along with warnings for specific interdictions, can help reduce jobsite injuries and improve product use.
For many warranted products and construction components, warranty coverage begins at the time of installation. Thus, preferably, thecentral database system120 is programmed, for at least some types of components, to initiate an automatic warranty registration process with the associatedmanufacturer170 at the time of installation. If desired, thecentral database system120 may prompt theinstaller150 to provide information useful for warranty registration. This provides a great improvement over warranty registration systems that require the eventual homeowner to enter information that may no longer be remembered or physically accessible. Furthermore, for warranties that are contingent on installation by a certified installer, or that provide incentives for installation by a certified installer, theinstaller150 may advantageously be prompted to provide certification information. Additionally, upon successful completion of the installation, photographic or other documenting data, such as initial operating temperatures or pressures, may be input by thetradesman150 and stored by thecentral database system120.
In some embodiments where thetradesman150 orbuilder140 provides a warranty to the owner160 (in addition to or as an alternative to the manufacturer170), the warranty information may be input to thecentral database system120 by thebuilder140 ortradesman150. For example, an agreement may be included to fix drywall cracks one time during the first year, to repair sticking doors the first year, to unclog any sewer pipe for the first ninety days, or offering a structural warranty for ten years. For some development projects, the same or similar warranties may be offered for allhomes100 in the project, and they may therefore be noted in association with theUICs105 of all includedhomes100.
Thecentral database system120 may provide access to a repository of information about warranties of the products in ahome100, including, for example, information about the duration, coverage, and conditions of the warranties. Thecentral database system120 may store some or all or none of the warranty information internally and may provide access links to some, all, or none of the information that is stored externally to thecentral database system120, such as information that is maintained on a computer website by amanufacturer170.
In some embodiments, thetradesman150 and thebuilder140 may use thecentral database system120 for communications with each other about thehome100. For example, thecentral database system120 may also provide clock-in/clock-out services fortradesmen150 working on construction of thehome100 so that abuilder140 in charge of overall construction of a home or housing development may be able to track the presence and progress of work crews at a job site. Thebuilder140 may use thecentral database system120 to identify workers working on the home, request input of license number or otherwise verify the worker's qualifications, and, in some embodiments, to record that specific installation instructions have been fulfilled. For example, thecentral database system120 may be able to receive and store electronic photographs that have been taken at the building site to document building progress and/or to document proper installation of building components.
Furthermore, thecentral database system120 may allow aninspector150, coming later to check the quality of a product's installation, to access customized checkpoint guidelines to insure correct installation.
Additionally, thecentral database system120 may keep a date-stamped or other log of installation, maintenance and repair events associated with a given product or component in thehome100. Currently, this important information is rarely available to subsequent repairmen, and it is unlikely to be remembered or even properly documented over the years of a product's lifetime in ahome100. Records of a product's maintenance history or feedback frominstallers150 in the field are even less likely to be currently available to the product'smanufacturer170, although such information would be very useful for a variety of marketing, monitoring, and product development purposes.
Thecentral database system120 may provide an owner and/or anoccupant160 of thehome100 with access to information about thehome100 and the components in the home, as has been discussed above. TheUIC105 may be given tonew owners160 once they are identified as such, allowing theowners160 privileges and access to thecentral database system120. Thecentral database system120 may also provideowners160 with certain information such as current percentage of construction completed, site progress inspection photos, floor plans and other house data so theowner160 can benefit and utilize these components in preparation for home ownership, including, for example, planning for furniture purchases, and the like.
Using thecentral database system120, theowner160 may view legal documents, disclosures, warranties, product information, paint and floor covering selections, and the like, that are stored in thecentral database system120 in association with the owner's160home100. Owners may forward pertinent documents to banks, appraisers, home inspectors, and the like, for their use during home construction or maintenance.Owners160 may update information associated with their home when remodeling or new products are installed.Owners160 may update data stored about the products in their home when routine, scheduled or unscheduled maintenance and repair is made. Owners may access stored information about qualified maintenance and/or repair persons for the components in theirhome100.Owners160 may further create and update a home inventory file to identify their personal belongings room by room for insurance purposes, or transfer their personal home inventory to a new physical property location.
Thecentral database system120 may differentiate between the information that it provides to owners and the information that it provides to home occupants. For example, if an occupant is renting thehome100, the occupant may be offered a more restricted set of information as compared to the owner, such as only a specified set of maintenance information and/or recall or use alerts and/or other specified information.
Thecentral database system120 may also provide an opportunity formanufacturers170 to communicate with the owner and/oroccupant160 of thehome100. For example, amanufacturer170 who wishes to issue a safety alert, product recall, or updated usage instructions may communicate with the owner and/oroccupant160 using access information received from thecentral database system120. Similarly, themanufacturers170 and/or other authorizedthird party entities180 may wish to identify owners and/oroccupants160 whosehomes100 are known to include an identified product or component and to offer them promotional opportunities regarding upgrading, servicing, replacing, or purchasing additional accessories for the identified product or component. For example, theowner160 may receive frommanufacturers170 and/or otherthird party vendors180 special offerings, online coupons, or the ability to automatically order replacement parts such as furnace filters, water filters or paint that is specifically identified for theirhome100.
Thecentral database system120 may include communications services, such as an email-type service, for the owners/occupants160 orother users140,150,170,180 of thecentral database system120. Alternatively or additionally, thecentral database system120 may store and provide access to communication preferences information supplied by the owners/occupants160. Such communication preferences may includes email addresses, mailing addresses, telephone numbers, and/or fax numbers, as well as any limitations imposed on their use, such as access only to certain types of entities or only for certain types of uses or only for certain hours of the day. Using the communications options provided by thecentral database system120, owners and/or occupants may order from thebuilder140 optional items for inclusion with construction of theirhome100, if within prescribed schedule and deadlines. Owners/occupants160 may further be afforded an opportunity to automatically communicate their acceptance of offers from third party vendors once payment information is stored.
In addition to theusers140,150,160,170 of thecentral database system120 that have already been described, a variety ofother entities180 may be authorized to access and use at least a portion of the information and services offered thecentral database system120. For example, a vendor may use thecentral database system120 to identify prospects for its products and/or services and may offer the products and/or services to theowners160 in a customized and targeted format. For example, a fireplace chimney cleaner may target only thosehomes100 that have wood burning fireplaces and that are more than three years old. Providers of pool cleaning or granite counter maintenance may identify and make offers toowners160 of thosehomes100 having such components. A plumbing contractor may target homes where his company performed the original work, pointing out that replacement parts for their particular fixtures are in stock and available.
Some entities may add information to thecentral database system120. For example, a home inspection entity may access thecentral database system120 the site to input information about significant defects discovered in thehome100, posting the findings to theappropriate UIC105, and links the associated report to thehome100, offering the report for sale to subsequent users
In addition to entities wishing to make targeted marketing offers, otherauthorized parties180 may wish to make use of information that is organized in an easily accessible format by thecentral database system120. For example, a real estate appraiser may download the original unit floor plan and compare it with the square footage measured at the site to determine if remodeling was performed, and may access information about other relevant features of the home. An insurer who supplies risk coverage for the builder may wish to assess certain risk profile information related to its policy. A potential purchaser of thehome100 may be given the UIC and authorization to access thecentral database system120 to determine the level of documented maintenance to the home. A builder or developer may access the history of maintenance performed on the property and thereafter alert the owner when prescribed maintenance has fallen below acceptable warrantable levels. A repair person who has received a customer service request to repair or perform maintenance on a component in thehome100 may access records that provide exact model information, past maintenance history, or other related information useful to have before and/or during the service visit.
A wide variety of uses and features have been described with reference toFIG. 1 for the systems and methods for collecting, maintaining, and using information about construction, maintenance, and use features of real property units and their components. However, the system configuration that is depicted inFIG. 1 is provided to exemplify and aid in explanation, and not to limit understanding of the scope of the systems and methods. Other types of entities may participate in the communications and information exchange described using theUIC110 and/orPICs115 as mediated by thecentral database system120. For example, a homeowners' association or property management group may use thecentral database system120 to fulfill its functions and/or to communicate with its members.
FIG. 2 is a block diagram that provides a more detailed view of one embodiment of thecentral database system120 for use with the building information system depicted inFIG. 1. As depicted inFIG. 2, users access thecentral database system120 through a user interface210 module. In a preferred embodiment, the information in thecentral database system120 is organized as a relational database that comprises a plurality of inter-linked virtual tables, or relations, which are indexed by theUICs105 of thehomes100 and/or by thePICs115 of the homes' components. Information about a givenhome100 or other real property unit may be extracted from the tables of thecentral database system120 based on the associatedUIC105 assigned to thehome100. The information stored in thecentral database system120 may also be organized according to another structural system for information storage and retrieval. Furthermore, thecentral database system120 may be implemented as a centralized system of hardware, software, and related components that function together in one physical location or thecentral database system120 may be implemented as a distributed system of hardware, software, and related components that function together across a variety of physical locations.
Thecentral database system120 may provide security protocols, such as one or more password systems, that allow access to information stored in thecentral database system120 only to authorized users. For example, homeowners may not want details about security systems installed in their homes to be available to all users who have access to thecentral database system120 and/or they may not want to allow unrestricted access to their contact information that may be stored in thecentral database system120. In some embodiments, different users may be granted different levels of viewing and/or editing privileges with regard to the information. Portions of the stored information may be accessible to a given user, while other portions are not.
For example, since building components are often shipped for use by either homeowners/occupants160 and other consumers or by installingcontractors150, who are likely of very different skill levels with respect to installation of the component,manufacturers170 are sometimes reluctant to provide advanced instructions for installing, servicing or troubleshooting a component in the normally packaged component instructions.Many manufacturers170 would prefer having the ability to limit the specific installation instructions, or alter them depending upon whether the product is being professionally installed or installed by a non-professional. By using a field wireless computer, aninstaller150 may scan thePIC115 to instantly register the component with thecentral database system120 and with themanufacturer170 as being installed at the location associated with the home'sUIC105, while simultaneously receiving updated instructions or checklists for installation by the manufacturer. Specific “vendor only” data may be transmitted directly to theinstaller170 without fear of such information being discovered or misinterpreted by an unqualified end user.
Furthermore, thecentral database system120 may include, for example, owner/occupant information270 that may list contact information and privacy preferences for the owners and/oroccupants160 associated with a givenUIC105, as well as associated dates of ownership and/or occupancy. In some embodiments, the contact information may include a telephone number, email address, or mailing address that may, if allowed by the owner and/oroccupant160, permit amanufacturer170 or other interested party to contact the owner and/oroccupant160 directly with product safety alerts, recall notices, informational bulletins, and/or promotional offers. The owner/occupant information270 may include one or more computer-accessible communications links for directly contacting the owner and/ oroccupant160. Additionally or alternatively, thecentral database system120 may provide a contact intermediary system (not shown) for managing the passing of communications to and from various users. The contact intermediary system, may, depending upon its configuration, allow messages to be sent to anowner160, for example, while protecting the owner's contact information from exposure to the public eye.
Thecentral database system120 may further comprise builder/project information240 that includes information about abuilder140 of ahome100. When ahome100 is built as part of a multi-unit development, the builder/project information240 may include other information that may be common and relevant to the houses or other real property units within the development. Information about expected overall project layout, expected street names, applicable local building laws and permits, blueprints, materials suppliers, subcontractors, building timelines, and geographical coordinates of the homes and any relevant soil or other geological information are examples of some types of information that may be stored with reference to the builder/project information240. Information common to multiple homeowners within a particular development may include information about the common areas such as the clubhouse or pool rules, legal documents such as soils or noise abatement reports, etc. A builder should be able to post documents that apply to all his projects (such as how to contact customer service), a particular project (such as soil reports, engineering to the site), a particular plan type or building number (for specific floor plans and details), and a specific unit (such as contracts, correspondence, and/or owner-specific components.)
Construction checkpoints information250 stored within thecentral database system120 may include up-to-date information about proper installation of various building components for thehome100.Construction checkpoints information250 may be provided toworkmen150 at the building site to instruct theworkmen150 as well as for quality control inspections of thehome100 during construction. In some embodiments, special conditions, such as geological or climatic conditions, or compatibilities between various building components, may be taken into account when providing instructions to theworkmen150. One suitable system for managing construction checkpoints is described in the Applicant's co-pending U.S. patent application Ser. No. 10/900,734, filed on Jul. 28, 2004, and entitled SYSTEMS AND METHODS FOR SELECTING AND PRIORITIZING CONSTRUCTION CHECKPOINTS, which is hereby incorporated herein by reference in its entirety. Thus, even before thehome100 is occupied and before any product warranties are registered, thecentral database system120 may provide up-to-date information about components to be installed in thehome100 for use by installers andother construction workers150.
Thecentral database system120 may further include a home construction history table260 that maintains a log of information gathered during construction of thehome100. Information about installation dates, installation crews, and any unusual occurrences may be stored in the home construction history table260.
Thecentral database system120 may additionally or alternatively include a home component warranty/history table280 that lists components in ahome100, as indexed by the home'sUIC105 and thecomponents PIC115. The table280 may include information such as installation date, installer name and certification, verification of proper installation procedure, warranty conditions and provisions, maintenance history, recommended service schedule, and the like.
Product data may further be included such that owners/occupants160 can readily access maintenance schedules, instructions and warnings customized to the home's100 features, as appropriate, from the manufacturer. Maintenance records may be collected to show that theowner160 has provided necessary maintenance to maintain coverage of the various warranties and service agreements.
Awarranty registration component285 may automatically register the warranty for a component newly added to thecentral database system120. Thewarranty registration component285 may access relevant data stored in thecentral database system120, such as stored owner/occupant information270 and/or may prompt theowner160 orinstaller150 for additional information used for registering the warranty. Thewarranty registration component285 may transmit the warranty registration information to themanufacturer170 and may receive confirmation of the warranty's registration.
InFIG. 2, thewarranty registration component285 is depicted as residing within thecentral database system120. As was noted with reference toFIG. 1, thecentral database system120 may be distributed across multiple computing devices and across multiple physical locations. Furthermore, thewarranty registration component285 may operate as an external computing unit that can communicate with thecentral database system120.
Additionally, thecentral database system120 may include a table of manufacturer contact information and/or associated storedinformation290. The information in the manufacturer table290 allows thecentral database system120 to communicate withmanufacturers170 of the components in thehome100 in order to receive up-to-date installation instructions, register warranties and provide component installation location information, and to receive safety alerts, promotional offers and the like for forwarding tohome owners160. In various embodiments, using thePICs115 of the components, thecentral database system120 may serve as a communications intermediary betweenmanufacturers170,builders140,installers150, andowners160. Thecentral database system120 may alternatively or additionally provide contact information so thatmanufacturers170,builders140,installers150, andowners160 may communicate directly amongst themselves, based upon pre-determined security rules defined by owner(s) of the data.
The manufacturer table290 may include information that correlatesPICs115 for various components with associatedmanufacturers170 for the components. Information about the components may be accessed from themanufacturers170 and transmitted to a requesting party on an as-needed basis and/or may be stored by thecentral database system120 for distribution to users as desired.
In some embodiments of thecentral database system120, maintenance schedules from eachproduct manufacturer170 are combined to form one logical maintenance schedule for thehome100, with options to allow owners/occupants160 to accept maintenance tasks, delay them, schedule them with a vendor, or cancel them. Warnings may be established if critical maintenance is not performed, alerting users, third-party maintenance vendors or providers of replacement products, such as filters or rain gutter cleaning.
The embodiment of thecentral database system120 depicted inFIG. 2 provides one example of a system for collecting, maintaining, using, and providing access to information about buildings and their components. In addition, upon reading this disclosure, other useful embodiments will be apparent to a practitioner of skill in the art.
FIGS. 3A and 3B depict two embodiments of building identifier tags110 that may be affixed to ahome100. The building identifier tags110 include the home'sUIC105, preferably in both machine-readable and human-readable formats. In the embodiment depicted inFIG. 3A, theUIC105 is provided as a bar code, machine-readable by a bar code scanning device, and as a string of alpha-numeric characters that may be manually input into an electronic communications device and/or may be machine-read by a device with optical character recognition (OCR) capabilities.
During construction of thehome100, several building identifier tags110 may be affixed to thehome100 in locations to provide access to theUIC105 as needed by installers/inspectors/repairmen150 and/or to owners andoccupants160. For example, abuilding identifier tag110 as inFIG. 3A may be folded, sealed in a plastic casing for protection and attached to the foundation of thehome100 during early stages of construction. If desired, even before construction, a copy of thebuilding identifier tag110 may be affixed, for example to a stake in the ground, the site where thehome100 will be built. As construction of the home progresses, additional copies of thebuilding identifier tag110 may be placed so as to be more easily accessible when needed. For example, once an electrical service panel has been installed, a copy of thebuilding identifier tag110 may be affixed therein.
Thebuilding identifier tag110 depicted inFIG. 3A further optionally includes the street address or legal description of thereal property unit100 and a suite number associated with theunit100. Furthermore, the examplebuilding identifier tag110 includes the World Wide Web address for thecentral database system120 so that a user with appropriate verification may use a network-enabled device to enter the designated Web address and theUIC105 in order to access thecentral database system120.
In other embodiments, thebuilding identifier tag110 may be equipped with radio frequency identification (RFID) technology.Tags110 with more passive forms of RFID may be read and used in much the same way that bar codes may be read and used, except that RFID tags are often able to store additional useful information beyond just thePID115.Tags110 with more active forms of RFID may “broadcast” their information to an RFID receiving device and may, in some embodiments, initiate communication with thecentral database system120. In still other embodiments of abuilding identifier tag110, other forms of information-transfer technology may be used to uniquely identify ahome100.
The product identifier codes (PICs) used to uniquely identify components used in the home may also be encoded using any of the technologies described above, including bar code technology, RFID technology, or other machine-readable and/or human-readable information transfer technology, and may be thus used to input and to access information about thehome100 and its components that is stored in thecentral database system120.
FIG. 3B depicts a second embodiment of abuilding identifier tag110 in which theUIC105 is provided as a machine-readable bar code and as a string of alphanumeric characters and in which a Uniform Resource Locator (URL) address is provided for accessing thecentral database system120 using the Internet or other computer network.
FIG. 4A depicts one embodiment of aweb page400 for allowing users to interface with thecentral database system120. Thesample web page400 shown is a home page for a givenUIC105 and thus allows an authorized user who has entered the home'sUIC105 and, in some embodiments, a security password, to access information about thehome100 and its components. In thesample web page400, the user is offered a menu of five actions. The user may access a message Inbox that stores emails and other communications, typically for use by theowner160 of thehome100. In this example, an alert notice is also posted above the menu, notifying the user that a new component-related alert has been sent to the Inbox. The menu further allows a user to access information about components in the home. This information may be accessed, among others, by a workman at the time of installation of the component, by an inspector wishing to inspect the quality of the installation, by an owner or occupant wishing to verify warranty and/or maintenance information, by a repairman wishing to repair the component, by an insurance broker or real estate agent wishing to assess the age and/or value of the components, or by other interested parties. The menu also allows a user to access information non-component related information about the home, including, for example, floor plans, construction photos, construction history information, and structural and/or civil reports related to the property, among others. In addition, the menu allows a user to update information stored in thecentral database system120 about thehome100, the components, or the owner and/oroccupant160.
In other embodiments, thewebpage400 associated with a givenUIC105 may provide these or other menu choices to a user of thecentral database system120. In addition, a variety of other web pages may provide users with opportunities to insert, delete, read, and use the information in thecentral database system120.
FIG. 4B depicts an example of aweb page420 that allows anew home owner160 to register with thecentral database system120. Thehome owner160 is requested to provide an email address and an access password. Thehome owner160 also provides information about whether or not he or she lives in thehome100, and whether or not he or she agrees to be notified with critical information about products in the home and/or to receive communications frommanufacturers170. In web pages that may be associated by link with theweb page420 ofFIG. 4B, thehome owner160 may access information related to progress of the home's construction, including viewing photos taken at the construction site, viewing the floor plan, viewing construction-related documents, and the like. Other web pages may allow thehome owner160 to access information about a home inventory of products, a home and/or component maintenance schedule, and a homeowner profile, as examples.
FIG. 5 depicts one embodiment of a computer-implementedprocess500 for collecting, maintaining, and using information about construction, maintenance, and use features ofreal property units100 and their components.
Inblock510, thecentral database system120 receives notification of anew home100 or other real property unit for which records are to be kept in the central database system. This information is typically, but not always, received from thebuilder140.
Inblock520, aunique UIC105 is assigned to thehome100 by thecentral database system120. Thebuilder140 or other party may enter additional available information associated with thehome100, such as information about the builder and thedevelopment project240 and information about theconstruction checkpoints250, which may be available even before construction on thehome100 begins.
Inblock530, during construction and after, thecentral database system120 continues to receive and store input about construction of thehome100 and, using thePICs115, about components being installed in the home.
Inblock540, during construction and after, thecentral database system120 uses thePICs115 to identifymanufacturers170 associated with the components. Thecentral database system120 may contact themanufacturers170, for example, to request installation information, to inform them that one of their components is being installed at thehome100 and that the owner and/or occupant of thehome100 may eventually be accessible using thecentral database system120, and/or to register the component's warranty with themanufacturer170. The database may alert the manufacturer of product interdictions with other products.
Product manufacturers may be provided specific information about thehome100, such as climate, type of installation, integrated components, anticipated use, and the like. Thus, themanufacturer170 may be able to electronically deliver specific maintenance and use instructions for that specific installation that go beyond the normally available, generic instructions. In fact, themanufacturer170 may create an electronic maintenance manual that is automatically customized to the home's100 features, based on data collected about its components, geographic area, and the like.
Inblock550, using theUICs105 and thePICs115, thecentral database system120 provides interactive access, throughout construction and afterwards; to the information about thehome100 and the components in the home to a variety of users, including, but not limited to, owners, occupants, builders, tradesmen, inspectors, and manufacturers. As one example, a published construction schedule for thehome100 may include milestones that trigger transmission of an alert to thehome owner160 indicating an opportunity to make decisions on paint color, selection of finishes, options such as adding electrical outlets, speaker pre-wire, and the like.
FIG. 6 depicts one embodiment of a process for electronically registering a warranty for a building component used in the construction of a real property unit. Inblock610, thecentral database system120 receives theUIC105 and thePIC115 for a component that is or will be installed in ahome100. Inblock620, thecentral database system120 uses thePIC120 to identify themanufacturer170 associated with the component. Inblock630, thecentral database system120 contacts themanufacturer170 electronically and registers a warranty for the component. Inblock640, thecentral database system120 receives confirmation that the warranty has been registered, and inblock650, thecentral database system120 stores a record of the warranty registration and, in some embodiments, of other information associated with the warranty.
FIG. 7 depicts one embodiment of a process for electronically providing current installation instructions for a building component used in the construction of a real property unit. Inblock710, thecentral database system120 receives theUIC105 and thePIC115 for a component that is or will be installed in ahome100. Inblock720, thecentral database system120 uses thePIC120 to identify themanufacturer170 associated with the component. Inblock730, thecentral database system120 contacts themanufacturer170 electronically and transmits information about the component and thehome100 to themanufacturer170. Inblock740, thecentral database system120 provides themanufacturer170 with access information for reaching users associated with the building component. For example, thecentral database system120 may provide themanufacturer170 with mailing, email, or telephone contact information for the owner/occupant, installer, and/or the developer so that themanufacturer170 may contact some or all of these users directly. Alternatively, or additionally, thecentral database system120 may provide communications services that allow thecentral database system120 to serve as an intermediary between the manufacturer andother users140,150,160,180.
Although the foregoing systems and methods have been described in terms of certain preferred embodiments, other embodiments that are apparent to those of ordinary skill, including embodiments that do not provide all of the features and advantages set forth herein, are also within the scope of this invention. Indeed, the novel methods and systems described herein may be embodied in a variety of other forms. Accordingly, the accompanying claims and their equivalents are intended to cover such forms or modifications as would fall within the scope and spirit of the invention.