SYSTEM AND METHOD FOR MONITORING ROOFTOP ACCESS

Abstract

A system and method for managing maintenance and repair of a commercial building roof that creates an access event log each time a roof location is accessed and precipitation event log is created each time precipitation occurs at the roof location to narrow the search for access events possibly resulting in roof damage causing a roof leak. A centralized computing system accessible by remote computing devices at each rooftop location is accessed to create an access event log when personnel access the roof. The computing system collects weather data for each rooftop location based on the global position coordinates for the rooftop location. Upon discovery of a roof leak, a system query will identify access events occurring since the latest precipitation event after which no leaks were reported to identify a list of potential causes for the roof damage. The system and method may also be used to consolidate roof maintenance, inspection, and repair to improve asset management.

Claims

1. A system and method for monitoring and controlling personnel access to a rooftop area which also monitors precipitation on the rooftop to identify potential personnel access events causing roof leaks, the system and method comprising the steps of: providing a computing system; providing a data storage system operably managed by the computing system and configured for receiving and storing information for a roof location, the information comprising baseline roof information including at least global position coordinates of the roof location, an access event log for the roof location, and a weather event log for the roof location; providing a remote interface device proximate to the roof location enabling entry of access record event information from an individual requiring access to the roof location and communicating the access event information to the access event log in the data storage system; providing a weather event monitoring system for identifying precipitation events occurring at the roof location and communicating precipitation event data to the weather event log; storing by the data storage system access record log information and precipitation event data for the roof location; and upon discovery of a roof leak at the roof location, querying the data storage system to identify the access record log information and the precipitation event data occurring at the roof location to prior to discovery of the roof leak to develop a list of individuals having accessed the roof location and possibly caused the roof leak.

2. The system and method of claim 1, wherein the computing system is a server accessible via the internet.

3. The system and method of claim 1, wherein the computing system further comprises software and a user interface enabling selective monitoring and query of the data storage system by a user.

4. The system and method of claim 1, wherein the remote interface device comprises a computing device and an access code, the access code configuring an interface with the computing system by the computing device by connecting to the data storage system via the internet and creating an entry in the access event log.

5. The system and method of claim 4, wherein the computing device is a portable computer, tablet, or smartphone operating a remote software application to configure interface with the computing system.

6. The system and method of claim 5, where the computing device comprises an optical scanner, and the access entry apparatus comprises scannable image which, when scanned by the optical scanner on the computing device accesses the computing system to create the entry in the access event log.

7. The system and method of claim 1, wherein access record event information comprises event date, identity of the individual or organization accessing the roof location, and purpose for accessing the roof location.

8. The system and method of claim 1, wherein the weather event monitoring system is a third-party system providing precipitation event data specific to the global position of the roof location and communicating the precipitation event data to the weather event log over the internet.

9. The system and method of claim 1, wherein the roof location information further comprises roof composition information, roof installation records, roof inspection reports, roof repair records, or pictures of all or portions of the roof.

10. A system and method for monitoring and controlling personnel access to a rooftop area which also monitors precipitation on the rooftop to identify potential personnel access events causing roof leaks, the system and method comprising the steps of: providing a computing system accessible via the internet; providing a data storage system managed by the computing system and configured to receive and store information for a roof location, the information comprising baseline roof information including at least global position coordinates of the roof location, an access event log, and a weather event log; providing a remote interface apparatus proximate to the roof location enabling an individual requiring access to the roof location to access the computing system and create an entry in the access event log; providing a weather event monitoring system for identifying precipitation events occurring at the roof location and communicating precipitation event data to the weather event log; providing a control interface for accessing the computing system; storing by the computing system in the data storage system access record log information and precipitation event data for the roof location; and upon discovery of a roof leak at the roof location, querying of the computing system by a user of the user interface to identify the access record log information and the precipitation event data occurring at the roof location to prior to discovery of the roof leak to develop a list of individuals that accessed the roof location and may have damaged the roof location and caused the roof leak.

11. The system and method of claim 10, wherein the access entry apparatus comprises a scannable code which, when scanned with a portable computing device by the individual requiring access to the roof location, connects to the data storage system via the internet and creates an entry in the access event log.

12. The system and method of claim 11, where the scannable code is connected to an access key required for the individual to access to the roof location.

13. The system and method of claim 10, further comprising the steps of: providing a locking apparatus for controlling personnel access to the roof location; and permitting personnel access to the roof location by setting the locking apparatus to a released configuration only after the entry in the access event log is created.

14. The system and method of claim 13, wherein the locking apparatus is operably controlled by the computing system in a locked configuration preventing access to the roof location by the individual or an unlocked configuration allowing access to the roof location by the individual.

15. The system and method of claim 10, wherein the roof location information further comprises roof composition information, roof installation records, roof inspection reports, records of repairs, or pictures of all or portions of the roof.

16. The system and method of claim 10, wherein the weather event monitoring system is a third-party system providing precipitation event data specific to the global position of the roof location and communicating the precipitation event data to the database via the internet.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The advantages of this invention will be apparent upon consideration of the following detailed disclosure of the invention, especially when taken in conjunction with the accompanying drawings wherein:

[0014] FIG. 1 is a flow chart illustrating a system and method for managing maintenance and repair of a commercial building roof by monitoring personnel access to the roof embodying the present invention;

[0015] FIG. 2 illustrates a timeline of events typically occurring in the system and method for managing a building roof using the present invention;

[0016] FIG. 3 is a diagram of the basic architecture of one embodiment of the system for implementing the method of the present invention;

[0017] FIG. 4 is a diagram illustrating the means of accessing the computing system embodying the resent invention; and

[0018] FIG. 5 shows an exemplar scannable code used for accessing the system of the present invention using a portable remote computing device.

DESCRIPTION OF THE PREFERRED EMBODIMENT(S)

[0019] Many of the fastening, connection, processes and other means and components utilized in this invention are widely known and used in the field of the invention described, and their exact nature or type is not necessary for an understanding and use of the invention by a person skilled in the art, and they will not therefore be discussed in significant detail. The various components shown or described herein for any specific application of this invention can be varied or altered as anticipated by this invention and the practice of a specific application of any element may already be widely known or used in the art by persons skilled in the art and each will likewise not therefore be discussed in significant detail. When referring to the figures, like parts are numbered the same in all figures.

[0020] FIG. 1 presents a flow chart illustrating the process of managing maintenance and repair of commercial building roofs by monitoring personnel access to each roof location. Initial data input 100 for each roof location monitored by the system is first added to the database. Baseline information identifying the building, owner, location, global positioning coordinates, size and type of the roof, age of the roof, and any other information that might benefit roof maintenance and the monitoring program is entered. Each building/roof location is assigned a unique identifier consistent with normal database management practices. Data specific to each roof location may then easily be accessed using the unique identifier or other searching criteria.

[0021] Using the location of each building, the database is configured to receive weather input 110, specifically precipitation events 160, occurring at each roof location in the system. Third-party commercial weather services may be used to automatically provide precipitation data to the system so that precipitation events may be entered into the database for each roof location in the database. A threshold may be applied so that only precipitation events 160 exceeding an amount that is likely to breach a damaged roof (e.g., 0.25 inches in a 24-hour period) are entered into the database.

[0022] The database may also include photographs of the roof and condition assessments reflecting the then current state of the roof on specific points in time.

[0023] Maintenance and repair records for the building roof location may be added to the database. Maintenance records may include service calls for equipment located on the roof and inspection reports for equipment or roofing. Developing a comprehensive log of the material condition of the roof, repairs, precipitation history, and personnel access history, allows the system to be used for identifying potential sources of damage to the roof surface leading to leaks and to assist in preventative maintenance and roof replacement planning. Minimally, each roof should be inspected 120 as it is entered into the database. Damage should be repaired, if necessary, to provide a known, leak-free baseline in the system.

[0024] A key aspect in relation to roofing maintenance is to maintain a log of all personnel accessing the roof and the purpose of their access. Access to building roofs is generally controlled by a locked access hatch inside the building or a lock ladder outside of the building. Requiring all personnel who need to access the roof 130 to initiate and complete a roofing access record 160 in the system as a prerequisite to being granted access greatly improves the integrity of the maintenance log. The access report is initiated when the personnel access the system 140 using a scannable code available at the roof location. In one embodiment, the unique identifier for the roof location is associated with a scannable code 51 (e.g., a Quick Response or “QR” code) that may be provided to the service or maintenance technician along with the keys for roof access. An exemplar scannable code 51 is shown in FIG. 5. Such a code is easily provided on a fob attached to the access key(s). A technician using a code scanner application for a smart phone or similar portable device can access the database via the internet and generate a new access visit record in the database upon arrival at the roof location. The scannable code might also be provided on a label or the like located adjacent to the roof access location.

[0025] Once scanned, the system creates a new access log entry into which the technician is required to enter identifying information for the service vendor, purpose for the service call, and, at the completion of the visit, identify any anomalies or other occurrences that might have caused damage to the roof (e.g., a tool dropped onto the roof). The system may also allow the service technician to supply photos of the roof, whether to confirm as-found or as-left conditions or simply to bring issues to the attention of the building owner or the roof maintenance contractor.

[0026] The system may provide a confirmation notification to the building manager and/or roofing monitoring entity that a roof access log report has been initiated and/or completed to assist the building manager and/or roofing monitoring entity in monitoring activities occurring at the building location and assuring compliance with the system requirements.

[0027] Reports of leaks 170 are also entered into the database system as the leaks are identified. These may be entered by a building manager or other employee at the location by accessing the system using a remote terminal, such as an internet-connected computer. Upon entry of a leak report, the system may automatically initiate a service request to a roofing vendor. Data in the system including precipitation events, maintenance and repair allows a timeline of events leading up to the discovery of the leak to be determined. Assuming that a leak would be reported following a precipitation event, the system can produce a potential cause report 180 identifying all roof access activities that occurred prior to the precipitation event that resulted in the leak report but after precipitation events that did not result in a leak report. Reviewing the potential cause report enables the most likely causes of the leaks to be identified and the responsible parties held accountable for repairs 190 to the roof damage.

[0028] FIG. 2 illustrates a timeline of based on the above description. In the exemplar figure, investigating the cause of the reported roof leak would focus on access events 153, 154 occurring during the period between precipitation events 161, 162. Access events 151, 152 which occurred prior to precipitation event 161 did not result in detected roof leakage and are less likely to have been a contributing factor in the detected leak.

[0029] A diagram of a representative monitoring system 5 for implementing a process to manage maintenance and repair of a commercial building roof by monitoring personnel access to the roof is shown in FIG. 3. The system 5 comprises a computing system 10, a data storage system 20, and a network means 30 for data input and output exchange between the computing system 10 and a plurality of remote interface devices 40. The system 5 may be implemented using the internet wherein the computing system 10 and data storage system 20 functions are fulfilled by an on-line server and database accessible using software and the interface device 40. The interface devices 40 can be any portable computing device or apparatus capable of accessing the system server over the internet such as a computer or a smart phone. FIG. 4 illustrates the connection of the remote interface devices 40 to the computing system 10. Roof locations 62 may provide remote interface devices 42 that are pre-configured to communicate with the computing system. Roof locations 61 provide a scannable code 51 that when entered into a portable computing device 41 connects to the computing system 10. A software application operable on the remote interface device 41 (e.g., a smart phone) streamlines the interface for convenience of the service personnel. Service personnel may be a repair or service technician servicing roof-mounted equipment at the roof location 60, the building owner/manager, or the roof maintenance contractor. It is noted that most smart phones and tablets may be used to scan a QR code (FIG. 5) which will then automatically load a pre-defined internet URL. As more companies incorporate tablet/smart phone application into normal work processes, it becomes increasingly likely that personnel requiring access to the roof will have the necessary technology available. This preferred interface provides ease of use that is desirable; simplifying access to the system improves the likelihood of compliance by all personnel requesting access to a particular roof within the system.

[0030] It is recognized that some service personnel may not have access to the necessary hardware/software that allows access to the monitoring system 5. Building owners or operators could easily provide access to a remote interface device in the form of a tablet or computer workstation so that the service technician could complete the access entry form.

[0031] Leaks are reported by a building manager or other employee at the location when detected. Reporting may be by contacting the operator/manager of the computing system or by interfacing directly with the database using a remote interface device. Creating a leak report for the rooftop location may have an interface that differs for the access log interface to solicit the information necessary to evaluate the leak and determine a potential cause. Once reported, the access event logs and the precipitation event logs may be queried by the computing system to identify access events occurring since a previous precipitation event for which no leaks were reported. This query identifies personnel who accessed the roof location and the work performed and may identify activities with the potential to have damaged the roof and caused the leak. The query is preferably performed by a roofing manager charged with responsibility for the rooftop monitoring computing system. A control interface 50 is provided to enable such queries as well as to conduct software maintenance and updates to the system. The control interface may connect to the computing system via the internet.

[0032] It will be understood that changes in the details, materials, steps and arrangements of parts which have been described and illustrated to explain the nature of the invention will occur to and may be made by those skilled in the art upon a reading of this disclosure within the principles and scope of the invention. The foregoing description illustrates the preferred embodiment of the invention; however, concepts, as based upon the description, may be employed in other embodiments without departing from the scope of the invention.