Field of the Invention

The present invention relates to a monitoring system for monitoring the status of a roof mounted fall protection system or a console system, wherein the attached mount ing elements each have a unique identification. Users are able to access the database storing the data associated with the mounting system and the mounting elements via dedicated user profiles. Background of the Invention

It is known to install fall protection system on the roof construction of a building for providing safety for workers located on the roof. The workers are able to couple their personal safety harness to the anchoring system while performing the installation, maintenance or service of the roof construction or equipment mounted on the roof. This enables the workers to move freely and safely around on the roof.

The fall protection system may comprise a set of anchoring points on the roof and a safety wire connected to each anchoring point, such as provided by the applicant. A bracket or anchor is attached to the roof construction at each anchoring point. Such fall protection system may be installed by certified installers or by specialists. After installation, the installer or specialist has to manually fill in information on the service manual about the installation site and type of fall protection system.

Further, such fall protection systems have to be regularly inspected in order to ensure that they are working properly. If damages or other critical issues are detected during the regular inspection, then the damaged or defect component has to be repaired or replaced before the fall protection system can be used again. A hardcopy of the ser vice manual and service history of the fall protection system is normally stored at the installation site. The servicer has to manually fill out the information about the result of the inspection, which adds to the total service time. However, this hardcopy may be difficult to find, or it may even be lost. This may lead to uncertainty about whether the fall protection system is safe to use or not. In such instances, workers wanting to ac- cess the roof has to contact the installer of the fall protection system or the owner of the building in order to determine, if the fall protection system is safe to use or not.

One provider of a fall protection system offers a managed service agreement where the customer, i.e. the site owner, is able to view the inspection history and current sta tus of the fall protection system, as well as the training certification of staff. The in stallation and inspection of the fall protection system, as well as the training of the staff, are all performed by the provider of the fall protection system. This online ser vice simply provides an electronic version of the service manual and service history that may be viewed and printed by the site owner only. It appears that the data man agement is performed solely by the fall protection system provider.

AU 2008201650 A1 discloses a system for monitoring the status of a fall protection system comprising a plurality of anchors, each having a tag with two rows of printed numbers for marking the last date of inspection. The tag may alternative comprise a barcode which can be read using a scanner or a RFID microchip where the stored data can be read and updated using a scanner.

WO 2017/041805 A1 discloses an anchor for attachment to the roof structure. The document is silent about how to monitor the status of the anchor.

US 7464001 B1 discloses a method of monitoring the status of personal protection equipment, where a RFID tag incorporated into the personal protection equipment is initially scanned and information about the personal protection equipment is stored in both a local database and in the RFID tag. During inspection, the RFID tag is scanned and the inspection results are entered via the scanner and stored on both the local da tabase and in the RFID tag.

There is thus a need for an alternative way of monitoring the status and inspection history of the fall protection system.

Object of the Invention

An object of the invention is to provide a monitoring system and method that solves the abovementioned problems. Another object of the invention is to provide a monitoring system and method that allows workers to enter and update data in a simply manner.

Yet another object of the invention is to provide a monitoring system and method that provide easy access for the workers to view the status of the system.

A further object of the invention is to provide a monitoring system and method that is flexible and accessible to multiple users.

A further object is to provide a safe and effective system that provides the required security of a complete system with different parts originating from different origins such as manufacturers, installers, and servicers.

Description of the Invention

One object is achieved by a method of monitoring a status of a roof mounted fall pro tection system comprising a mounting system with mounting elements. The method comprises acts as will be disclosed.

There is an act of a user accessing data stored in a database via a dedicated user pro file and via a dedicated user interface on a mobile computing device and wherein the accessed data represents the status of at least one mounting element that is associated with the mounting system. The status may be if the mounting system is safe or not safe to use.

There may be a unique identification associated e.g arranged relative to a mounting element. There may be at least one unique identification arranged relative to the at least one mounting element.

Thus such system allows easy and instant status about the safety of the system and thus provides the user, such as an installer (i.e. a person installing or maintaining the system) or a servicer (i.e. a person servicing or inspecting the system), of information about the system. The method also allows accumulating or summing the status of each element in the system. Thus a mounting element might have been reported faulty or a service period expired. Thus a single element may result in the whole system being flagged as unsafe and point to a repair, service, or inspection to be performed.

The status may be monitored at the mobile computing device such as a mobile device (smart phone, tablet or alike). The status may also be monitored centrally and repairs or service may be performed on that basis.

A roof mounted system may be a site that can be defined as a project. A site may comprise one or more roofs that can be defined as a section.

A roof mounted system may comprise mounting elements manufactured and test ed/verified by the manufacturer and then installed according to stand ards/specifications. As such a mounting element may be born with a safe to use status and a roof mounted system may be installed in such a way that each mounting element is reported installed according to specifications and tested as required. As time passes a service period may expire on a roof or a site and a user will be warned accordingly.

Likewise one or more mounting elements may be serviced or repaired. A new section may be added which again adds complexity to the management of the roof or site.

As will be outlined in the following there may be multiple aspect of such system.

In an aspect the accessed data further represents the status of personal safety equip ment configured to be attachable to the mounting system.

There may be a unique identification associated e.g. arranged relative to the personal safety equipment. There may be at least one unique identification arranged relative to the at least personal safety equipment.

Generally an additional mounting element may be attached to the mounting system.

In such case the method and system is particularly advantageous. The roof mounted system may be as outlined above and with more aspects. As such it is possibly to monitor if the roof mounted system is safe or not. At the same time an installer or ser- vicer may use equipment such as a harness. Such equipment may be handled as mounting element, but now the personal safety equipment may be maintained or ser viced by the installer or servicer, whom might be different from the manufacturer or site or roof owner. Such user with personal safety equipment will then be able to mon itor both the status of the mounting system and the personal safety equipment and both. In fact it may be possible to handle or monitor situations where a specific com bination of a mounting system according to specific standard and personal safety equipment by the definitions in the standard expires.

In an aspect an object is achieved by a method of monitoring the status of a roof mounted system, such as a fall protection system or a roof console system, comprising the acts of:

- installing a mounting system on a roof structure of a building, wherein at least one mounting element of the mounting system is attached to the roof structure, wherein at least one unique identification is arranged relative to the at least one mounting ele ment,

- an installer accessing data stored in a database via a dedicated installer user profile by reading or entering the at least one unique identification using a mobile computing device,

- the installer entering data associated with the installation of the at least one mounting element into the database via a dedicated user interface on the mobile computing de vice, wherein the data associated with installation of the at least one mounting element is linked with data associated with the mounting system in the database.

A person skilled in the art will appreciate that data may include status, information or time aspects of validity or periods.

This provides an improved data monitoring that allows status of the mounting system to be monitored from the installation to decommission. The present method enables access to the monitoring data to be shared between different end users, thereby in creasing the flexibility of the monitoring system. Further, the present method allows the users to access and enter data in a fast and simple manner without having to resort to a paper based system. The roof construction of a building is normally installed by roofers of a roofing pro vider. The roof structure is inspected regularly during the warranty period in order to maintain the integrity of the roof structure. If damages or defects are detected, then these have to be repaired. This may be done by the roofing provider or a service pro- vider. This ensures that the roof structure follows the legal requirements.

Further, the mounting system is normally installed by certified installers of an installa tion provider. In example, the installation provider may be the mounting system pro vider or the roofing provider, if the roofers have the required certification. If the in- stallers do not have the required certification, then the mounting system might not be installed correctly and may then fail in critical situations. In example, the certification of the installers may be performed by the mounting system provider. This allows the mounting system, e.g. the fall protection system, to be installed at the same time as the roof structure. This also allows that the installation is performed correctly.

During installation, the installer accesses the database using a mobile computing de vice by reading or entering the unique identification of a mounting element. This may be done via an app stored on the mobile computing device, or by using the functions of the mobile computing device. In example, the installer may scan the unique identi- fication via a scanner application or algorithm in the mobile computing device. Alter natively, the installer may enter the unique identification in the app or on a dedicated web site. Alternatively, the mobile computing device may communicate with a trans mitter or transceiver on the mounting element via a wireless connection, where a unique identification code is transferred to the mobile computing device. This allows the installer to quickly identify and access data associated with a particular mounting element.

Subsequently, the installer enters information about the mounting element into the database, such as an installation site (e.g. a site), a system name, a sub-system name (e.g. a section name), an installation date, or other relevant data. Further, the location data (e.g. GPS data) of the placement of the mounting element may be entered, or loaded, into the database. Additionally or alternatively, an image of the installed mounting element may be loaded into the database for documentation. This allows a particular mounting element to be linked to a particular mounting system in the data- base. This allows for a quick and simple registration of an installed mounting system compared with conventional hardcopy solutions.

During installation, the installer, or roofer, may alternatively access the database by reading or entering a unique identification positioned relative to the mounting system. The unique identification may be entered or read in a similar manner as described above. The installer may then enter or load information about the mounting system, such as the system name, the sub-system name (e.g. section name), location data (e.g. GPS data or a postal address) and/or an image of the mounting system, as described above. This allows the unique identification to be linked to a particular mounting sys tem in the database.

Alternatively, all or more of the data associated with the mounting system may be entered into and stored in the database prior to the installation, e.g. via an administra- tion module. The installer may then select these pre-stored data from the database in stead of entering these data. This further saves time for the installer as he/she only has to register a minimum of data during the installation.

After installation, the installer may perform a handover process to complete the instal- lation process. In example, the installer may access the database by reading or enter ing the unique identification of the mounting system, alternative of one mounting el ement. The installer may then enter information about the handover, such as the hand over date and other relevant data. These data are stored in the database for documenta tion. This allows for a quick and simple handover of the mounting system.

According to one embodiment, the method further comprises the acts of a servicer performing an inspection of the mounting system, where the servicer accesses the data stored in the database via a dedicated servicer user profile by reading or entering the one unique identification using a mobile computing device, and further entering data associated with the inspection into the database via a dedicated user interface on the mobile computing device and linking the data associated with the inspection with at least the data associated with installation of the at least one mounting element and/or the data associated with the mounting system in the database. The mounting system and the mounting elements may be inspected at regular intervals by a servicer of a service provider. The servicer is preferably certified so that the in spection is performed according to the legal requirements and/or the warranty re quirements set up by the mounting system provider. In example, the certification of the servicers may be performed by the mounting system provider.

The servicer may access the data stored in the database using a mobile computing de vice by reading or entering the unique identification of the mounting system and/or of a mounting element. This may be done via the app stored on the mobile computing device or by using the functions of the mobile computing device, as mentioned earlier. In example, the servicer may scan the unique identification via the scanner application or algorithm in the mobile computing device. Alternatively, the servicer may enter the unique identification in the app or on the dedicated web site. Alternatively, the mobile computing device may communicate with the transmitter or transceiver on the mount- ing element via the wireless connection, where the unique identification code is trans ferred to the mobile computing device. This allows the servicer to quickly access the data associated with that mounting element and the mounting system.

During the inspection, the servicer may follow a guide and/or a check list and note the result of each point of the check list. In example, the guide and/or check list may be stored in the database and transferred to the mobile computing device upon request. The guide and/or check list may then be displayed to the servicer during inspection. The servicer may enter information about the inspection into the database, such as inspection date, observations made during the inspection, indication of whether the mounting system or mounting element has passed the points of the check list, or other relevant data. The data associated with the inspection may then be stored in the data base and linked to that mounting element and/or to the mounting system. This allows the servicer to quickly enter results of the inspection. The servicer may inspect all or some of the mounting elements and/or other equip ment of the mounting system. The result of each inspection may be entered into the database by the servicer via the mobile computing device. A status indicator or mes sage of the mounting system may be generated by the server which may be displayed to the servicer and other users. This allows any worker to quickly view the status of the mounting system at any time without having to consult a hardcopy version of the inspection history.

According to one embodiment, the method further comprises the acts of a worker gen erating the at least one unique identification, where the worker accesses the database via a dedicated manufacturer user profile using a computing device, and further enters data associated with the production of the at least one mounting element into the data base via a dedicated user interface on the computing device.

The mounting element may be a specific mounting element.

The data associated with the mounting elements may be generated by a worker during manufacturing. The worker may access the database via a dedicated manufacturer user profile using a computing device and enter information about the mounting element. Alternatively, all or more of the information may be selected from one or more lists or menus already stored in the database. The information may be, but not limited to, a unique identification code or serial number, a production date, type of mounting ele ment, special features of the mounting element, or other relevant data. These data are then stored in the database so that the mounting element may be identified at a later time.

Further, the worker may generate, e.g. program, the unique identification associated with that mounting element. In example, the unique identification may comprise the above unique identification code or serial number. The unique identification may sub sequently be positioned on or fastened to the mounting element and used to identify the mounting element in the database.

Further, the worker may generate, e.g. program, another unique identification associ ated with the mounting system. In example, this unique identification may also com prise a unique identification code or serial number. This unique identification may be arranged on or form part of a sign, e.g. a safety sign, configured to be installed relative to the mounting system, e.g. at an opening or ladder providing access to the roof struc ture. The unique identification and, optionally, information about the mounting system may be displayed on the sign. Thus, allowing the mounting system to be identified in the database.

According to one embodiment, the method further comprises the act of displaying at least status information of the mounting system to a user of the mounting system and/or a site owner in a dedicated user interface on a mobile computing device, where user and/or the site owner accesses the data stored in the database via a user profile by reading or entering the one unique identification using the mobile computing device.

The site owner and/or a user of the mounting system may access the data stored in a database by reading or entering the unique identification of the mounting system and/or of a mounting element using a mobile computing device. At least the status indicator or message may be displayed to the site owner on the app or the dedicated web site and/or to the user. Further, the data associated with the mounting system may also be displayed to the site owner and/or the user. In example, the user may be any worker having to access the roof in order to perform a particular task. In particular, this allows the site owner or worker to quickly determine if the fall protection system is safe to use or not.

Optionally, information about any service agreement between the site owner and a particular service provider may further be displayed to the site owner and/or to the user, e.g. a third-party service provider. In example, status information about an active service agreement may be displayed on the app or the dedicated web site, e.g. the name of the service provider, an indicator of whether the service agreement is active or not, or other relevant data. This allows the site owner to quickly determine if a ser vice agreement has lapsed or not. This also provides information to a third-party ser vice provider whether a service agreement with a certified service provider exists or not.

According to one embodiment, during inspection, a test is performing on at least one selected mounting element using a test device, wherein the data associated with the selected mounting element is updated with documentation of the test and/or a test re sult. The servicer may use a test device to test the mounting elements during inspection. The test device may be coupled to the mounting element and the servicer may start the test. Optionally, an image of the test setup may be loaded into the database via the mobile computing device for documentation. Optionally, a guide for performing the test may be displayed to the servicer on the app or the dedicated web site. Upon com pletion of the test, the service may enter the test result into the database via the mobile computing device. This allows the servicer to monitor the status or integrity of each mounting element. The test result may simply be an indicator of whether the mounting element has passed the test or not. Alternatively or additionally, the servicer may enter the value of the test result and/or any comments to the test.

If a mounting element fails the test, then the servicer may uninstall that mounting el- ement and install a new mounting element. The servicer may via the mobile compu ting device mark the failed mounting element as decommissioned in the database. The servicer may then add data associated with the new mounting element to the present mounting system via the mobile computing device. This new data may then be stored in the database. This allows the user to view any replacements made to a mounting system via the administrator module.

According to one embodiment, a test procedure is performed on the selected mounting element, wherein the test device generates a visual indication or an audio notification of the rest result.

The test procedure may be described in the displayed guide, or in a guide associated with the test device. The test device may in a simple configuration be configured to generate an audio notification when the mounting element passes the test. If no audio notification is generated, then the mounting element has not passed the test. This may be done by comparing the measured value with a threshold value, where the audio notification may be generated when the measured value exceeds the threshold value.

Additionally or additionally, the test device may be configured to generate a visual indication of the test result. In example, this may be done by text (e.g. PASS or FAIL) or a coloured indicator (e.g. a first colour indicates PASS while a second colour indi cates FAIL). In example, this may be done by a numbered value (e.g. value must above the threshold value). Other means of visual or audio indicators may be used. According to one embodiment, the test result is wirelessly transferred from the test device to the mobile computing device, where the test result is further transferred to and stored in the database.

The test device may be fitted with wireless communications means for communicating with the mobile computing device. In example, the wireless communications means may comprise a Bluetooth antenna, a WIFI antenna, a NFC antenna, an optical trans mitter or transceiver, a RF transmitter or transceiver, or other suitable communications means. The mobile computing device may be a corresponding receiver or antenna for receiving a wireless signal from the test device. The wireless signal may at least com- prise the test result. The test result may then be transferred further to the database and stored together with the data associated with that mounting element. This allows the test result to be automatically uploaded, e.g. transferred, to the database via the mobile computing device. Optionally, the servicer may capture an image of the test result displayed on the test device using the mobile computing device. The image may then be transferred to the database and stored along with the data of that mounting element for documentation. This allows the test result to be verified by analysing the captured image. According to one embodiment, the acts of installing the mounting system and inspec tion of the mounting system are performed by the same entity, or by different entities.

The present method allows the installation of the mounting system and the subsequent inspection to be performed by different entities or providers, where both providers are able to access the data associated with the mounting system. Thus, the installer differs from the servicer. This differs from the conventional service agreement described ear lier and provides a more flexible monitoring system as different users are able to track the monitoring history of the mounting system. The installation and inspection may also be performed by the same entity or provider. Thus, the installer is also the servicer, or vice versa. This allows the inspection and installation to be performed by the same certified worker, or different certified work ers within the same provider.

According to one embodiment, the method further comprises the act of a user of a provider accessing a dedicated administration module stored on a server, where the user manages selected set of data stored in the database wherein the selected set of data is linked to that provider.

The provider, e.g. an administrator, may access the data stored in the database using a computing device via a dedicated administrator module stored on the server. The ad ministrator module may be dedicated to that provider and enables the user to manage all mounting systems and mounting elements linked to that provider. The user may enter, edit or update data associated with a particular mounting system and/or data associated with a particular mounting element. This allows the provider to monitor upcoming inspections as well as previous inspections and the status of each mounting system. This also allows the user to enter data associated with a monitoring system prior to installing the monitoring system.

The administrator module may further provide the user with an overview of its em ployees or workers registered in the database. The user may access the user profile of a selected worker via the administrator module, wherein the user is able to view the status of the certification of that worker. The user may download the stored documen- tation of a particular mounting system and/or of a particular mounting element.

The data stored in the database may be updated continuously or periodically while the installer or servicer enters data, or upon a request from the installer or servicer via the app or the dedicated web site. This allows the data to be quickly accessible in the da- tabase which may reduce the latency of the monitoring system.

It is understood that some data may not be updated, but remain unchangeable. In ex ample data about the manufacturer, manufacturing date, manufacture standards, manu- facturer tests etc. There may be data such as test data and quality control data that is unchangeable. Thus quality control can easily be achieved and standards adhered to. Likewise some data may not be changed; ever. An object of the invention is further achieved by a system for monitoring the status of a roof mounted system, such as a fall protection system or a roof console system, comprising:

- a mounting system configured to be installed on a roof structure of a building, wherein at least one mounting element of the mounting system is configured to be attached to the roof structure, wherein at least one unique identification is configured to be arranged relative to the at least one mounting element,

- a database comprising at least data associated the at least one mounting element, and

- means adapted to execute the acts of the method as described above. The present invention provides a monitoring system with increased flexibility as the data stored in the database is accessible to different users. The present monitoring sys tem also enables an installer to enter data associated with a mounting system in a quick and simple manner using a mobile computing device. This saves time when installing and inspecting the mounting system. This provides a mounting system which is safe to use and where users are able to track the inspection history of the mounting system at any time.

The database is accessible to different providers as well as different workers within that provider where each user is registered in the monitoring system. The database may thus be accessed via dedicated user profiles assigned to each provider or worker. The mounting system may thus be monitored from installation to decommission.

According to one embodiment, the mounting system is a fall protection system or a console system for the mounting of external components.

The present mounting system is particular suited for the installation on foil or felt roofs, but may also be used for other types of roofs. The roof structure may be a flat roof, or a sloped roof. The mounting system preferably comprises a plurality of mounting elements attached to the roof structure. However, the mounting system may also comprise just one mounting element. Further elements may be connected or coupled to each of the mounting elements. The mounting element may comprise means for providing a wa- tertight attachment so that water or moisture is prevented from entering the roof struc ture. In example, the means may be a mechanical seal, an integrated foil or felt flange or other suitable sealing means. The foil or felt flange may, in example, comprise a self-adhesive layer, or an adhesive layer that is bonded to the roof surface by applying heat or pressure. Alternatively, a sealant or sealing means may be applied after at- tachment of the mounting element in order to provide the watertight attachment.

In example, the mounting system may be a fall protection system where the mounting elements may be mounting anchors. Each mounting anchors may define an anchoring point for the fall protection system where a wire may be connected to each mounting anchors. Alternatively, a single eye may be connected to one or more of the mounting anchors. Each monitoring anchor may be fitted with a unique identification, as de scribed earlier. Such fall protection systems are known and will not be described in details. In example, the mounting system may be a console system for the mounting of exter nal equipment, such as solar panels, ventilators, air conditioning units, or the like, where the mounting elements may be mounting console feet. Each mounting console foot may define an anchoring point for the console system which is adapted to the installation of the external equipment.

The fall protection system may also be integrated into the console system to form a combined system.

The test device may be configured to perform a test on the mounting anchors, such as a pull test. Such test devices, as well as the test procedure, are known and will not be described in details. The test device may be modified with a visual or audio indicator, as described earlier, for providing a visual or audio indication of the test result. The test device may also be modified with wireless communications means for transferring the measured test result to the database via the mobile computing device for documen tation.

The mobile computing device may be a mobile phone, a smartphone, a tablet, a pha- blet, a PDA, or another suitable mobile computing device. The computing device may be a stationary computer, a laptop, a notebook, an end user terminal, a tablet, a pha- blet, a smartphone, or another suitable computing device.

According to one embodiment, the unique identification is a multi-dimensional code, an identification tag, or a device comprising a wireless transmitter or transceiver.

The unique identification may simple be configured as a multi-dimensional barcode or QR-code comprising a unique identification code. The barcode or QR-code may be arranged on a sticker which may be attached directly to the mounting element, or to a sign. The sign may then be connected to the mounting element, or installed relative to the mounting system. The barcode or QR-code may also be integrated into the sign or the mounting element. The barcode or QR-code may then be read by a scanner or scanning algorithm in the mobile computing device.

The unique identification may also be a unique identification or serial number printed or stamped into the mounting element or the sign. This unique identification or serial number may then be entered, alternative scanned, into the mobile computing device.

Alternatively, the unique identification may be a wireless communications device comprising a Bluetooth antenna, a WIFI antenna, a NFC antenna, an optical transmit ter or transceiver, a RF transmitter or transceiver, or other suitable communications means. The wireless communications device may communicate wirelessly with the mobile computing device and transfer the unique identification code which is used to identify that mounting element.

Alternatively, the unique identification may be a passive or active RFID tag config ured to communicate wirelessly with the mobile computing device for transferring the unique identification code. An object of the invention is also achieved by a computer program comprising in structions to cause the means as described above to execute the acts of the method as described above.

Access to the database is managed by a server which is able to communicate with the various computing device of the different providers and/or the database. The server comprises a computer program configured to control access to the data stored in the database. The server, e.g. the computer program, is further configured to control the communication with the user, e.g. via the app in the mobile computing device or via the dedicated web site.

The computer program may use a plurality of dedicated user profiles and/or adminis trator modules to identify a particular user, such as the installer, the servicer, the ad ministrator, the site owner, the manufacturing worker or other users. Each user may be registered in a user database which may be checked by the computer program each time an attempt to access the database is made. If a user is identified by the computer program, then access to the data may be set up according to that user profile. If a user is not identified by the computer program, then the computer program, e.g. the server, may restrict access to the database and transfer general status information about the mounting system to the user.

An object of the invention is additionally achieved by a server having stored thereon the computer program as described above.

The server may be a dedicated server in communication with a dedicated database. Alternatively, the server and database may be configured as a database server or file server. However, other configurations of the server and database may be used.

An objective may be achieved by a system for monitoring a status of a roof mounted fall protection system. The system comprises the following subjects.

There is a mounting system with mounting elements and at least one unique identifi cation arranged relative to the at least one mounting element. There is a database server configured to store data that represents the status of at least one mounting element that is associated the unique identification of the mounting sys tem, which status is if the mounting element is safe or not safe to use, There is a mobile computing device configured to read or enter the unique identifica tion of the mounting system and configured with a dedicated user interface configured to communicate data that represents the status of at least one mounting element that is associated the unique identification of the mounting system and which status is if the mounting element is safe or not safe to use.

As such the mounting system shares the same advantages as described for the corre sponding acts.

In example a manufacturer may provide the system including the mounting elements pre-tested or pre-verified. Likewise site or roof owner may provide the system and the status of the mounting elements may be established during installation, service or in spection. The system will allow easy access and up-to date monitoring capabilities.

In an aspect the system further comprises personal safety equipment configured to be attachable to the mounting system, wherein the personal safety equipment is associat ed with a unique identification.

The personal safety equipment may be configured as disclosed as with the disclosed functionality according to the methods and acts.

Furthermore the database server is configured to store data that represents the status of at least one personal safety equipment that is associated the unique identification of the personal safety equipment, which status is if the personal safety equipment is safe or not safe to use.

The database server may be configured as disclosed as with the disclosed functionality according to the methods and acts. The mobile computing device is configured to read or enter the unique identification of the personal safety equipment and configured with a dedicated user interface con figured to communicate data that represents the status of at least one personal safety equipment that is associated the unique identification of the personal safety equipment and which status is if the personal safety equipment is safe or not safe to use.

The mobile computing device may be configured as disclosed as with the disclosed functionality according to the methods and acts.

Description of the Drawing

The invention is described by example only and with reference to the drawings, wherein:

Fig. 1 shows an exemplary embodiment of a system for monitoring the status of a roof mounted system according to the invention,

Fig. 2a-b show exemplary user interfaces of the worker entering data associated with the production of the mounting element,

Fig. 3 shows an exemplary user interface of the installer entering data associated with the mounting system,

Fig. 4a-c show exemplary user interfaces of the installer when completing the in stallation of the mounting system,

Fig. 5 shows further details of the monitoring system of fig. 1,

Fig. 6a-b shows exemplary user interfaces of the installer entering data associated with the installation of the mounting element,

Fig. 7a-g show exemplary user interfaces of the servicer entering data associated with the inspection of the mounting system,

Fig. 8a-b shows an exemplary user interface of an unknown user accessing the data base, and

Fig. 9 shows an exemplary user interface of the administrator module displaying the selected mounting systems and mounting elements linked with that provider.

In the following text, the figures will be described one by one, and the different parts and positions seen in the figures will be numbered with the same numbers in the dif- ferent figures. Not all parts and positions indicated in a specific figure will necessarily be discussed together with that figure.

Reference list

1. Mounting system, roof mounted system

2. Roof structure

3. Building

4. Mounting element

5. Unique identification

6. Sign

7. Fall protection system

7a. Wire bracket

8. Console system

8a. Mounting frame

9. Database

10. Computing device

11. Data associated with the production of the mounting element

11a. Unique identification number

l ib. Other rel evant data

12. Mobile computing device

13a. Data associated with the mounting system

13b. Location data

13 c. Data associated with test of the mounting element

14. Administrator module

15. Information associated with a handover

16. Data associated with the mounting element

17. Data associated with inspection of the mounting element

18. Test device

18a. Display unit

18b . Audio generator

19. Updated documentation of mounting element

20. Documentation of damaged mounting element

21. Data associated with inspection of the mounting system

22. Wireless communications device Detailed Description of the Invention

Fig. 1 shows an exemplary embodiment of a system for monitoring the status of a roof mounted system, where the mounting system 1 is installed on a roof structure 2 of a building 3. Here, the mounting system 1 is installed on a flat roof structure.

The mounting system 1 comprises one or more mounting elements 4 configured to be attached to the roof structure 2. Here, the mounting elements 4 are configured as safe ty anchors for the installation of a fall protection system 7 or a console system 8. The fall protection system 7 comprises one or more brackets 7a shaped to hold a wire. The console system 8 comprises a mounting frame 8a adapted for the installation of exter nal equipment, such as solar cells, a roof deck, air conditioning units, ventilators or the like.

A unique identification 5 is arranged relative to the mounting elements 4. Here, the unique identification 5 is configured as a QR-code arranged on a sign 6 connected to the mounting element 4. Other types of unique identification 5 may be used instead.

The system further comprises a database 9 for storing data associated with the mount ing system 1 and the mounting elements 4. The database 9 comprises a unique identi- fication number associated with each mounting element 4. The database 9 may be accessed by dedicated users using a computing device 10 or a mobile computing de vice (see fig. 3), as described later.

An initial act of the method will now be described in reference to figs. 1 and 2. A worker accesses the database 9 using the computing device 10 via a dedicated manu facturer user profile. This may be done during production, or during preparation of the mounting system 1.

The worker enters data 11 associated with the production of the mounting element 4, such as a unique identification number 11a or other relevant data 1 lb, as illustrated in fig. 2a. The entered data 11 are then stored in the database 9, as illustrated in fig. 2b, and optionally a report of the entered data is generated. The worker further generates the unique identification 5 which is linked with that mounting element 4. The unique identification 5 is then arranges relative to the mounting element 4. Further details of the system and further acts of the method will now be described in reference to fig. 3 to fig. 8b.

An installer accesses the database 9 during installation using the mobile computing device 12 via a dedicated installer user profile. The database 9 is accessed by reading the unique identification 5 of the mounting element 4, e.g. via an application, using the mobile computing device 12.

The installer then enters data 13 associated with the installation of the mounting ele- ment 4, as illustrated in fig. 6a. The data 13 includes, but not limited to, data 13a asso ciated with the mounting system, and location data 13b of the placement of the mount ing element 4. Data 13c associated with an initial test of the mounting element 4 is optionally also entered into the database 9. These data 13a, 13b, 13c are subsequently stored in the database 9, as illustrated in fig. 6b, and optionally a report of the entered data is generated. The data 11a, l ib are thus linked with the data 13a, 13b, 13c in the database 9.

The data 13a associated with the mounting system 1 may instead be pre-entered via a dedicated administrator module 14, and stored in the database 1 prior to installation. The installer is then able to select these data 13a, when accessing the database 9 dur ing installation.

Alternatively, the installer may read a unique identification 5’ of the mounting system 1 using the mobile computing device 12. The unique identification 5’ is arranged rela- tive to the mounting system 1, e.g. on a sign 6’ as illustrated in fig. 5. The installer is then able to enter the data 13a, as illustrated in fig. 3, which are then stored in the da tabase 9. The unique identification 5’ is thus linked with the data 13a, and indirectly the data 11a, 1 lb, 13b, 13c, in the database 9. Upon completion of the installation of the mounting system 1, the installer accesses the database 9 via the dedicated installer user profile by reading the unique identifica tion 5’ of the mounting system 1, as illustrated in fig. 4a. The installer may instead read the unique identification 5 of the mounting element 4, as illustrated in fig. 4b, and select to view the data associated with the mounting system 1. The installer then se- lects to enter information 15 associated with a handover of the mounting system 1, as illustrated in fig. 4c. This information 15 is then stored in the database 9 and, optional ly, a report of the entered information is generated. Afterwards, a servicer performing an inspection of the mounting system 1 is able to access the database 9 using a mobile computing device 12, 12’ via a dedicated ser vicer user profile. The database 9 is accessed by reading the unique identification 5, 5’ of the mounting system 1, as illustrated in fig. 4a, or of mounting element 4 using the mobile computing device 12, 12’, as illustrated in fig. 7a.

During the inspection, the servicer performs an inspection of mounting elements 4. The servicer accesses the data 16 associated with a selected mounting element 4 (see fig. 7a) and selects to enter data 17 associated with the inspection of that mounting element 4, as illustrated in fig. 7e.

Preferably, the servicer positions a test device 18 relative to the selected mounting element 4 and couples the test device to the mounting element 4. The servicer then performs a test on the mounting element in accordance with a test procedure. The ser vicer subsequently enters at least the test result as evidence of the test. The data 17 are then stored in the database 9, as illustrated in fig. 7b.

The test result is displayed visually to the servicer on a display unit 18a of the test device 18 and/or an audio generator 18b of the test device 18 generates an audio noti fication of the test result. This allows the service to quickly determine if the mounting element has passed the test or not.

Alternatively, the test device may comprise a wireless communications device 22 con figured to communicate with a corresponding wireless communications unit in the mobile computing device 12. The test result may thus be transferred automatically from the test device 18 to the mobile computing device 12, or upon request from the servicer. The transferred test result, along with the other data 17, is then stored in the database 9, as illustrated in fig. 7b. The servicer further accesses the data 16 associated with another selected mounting element 4 that are not tested. The servicer then selects to update the documentation 19 associated with that mounting element 4. Here, an image of the mounting element 4 is captured and uploaded. The documentation 19 is then stored in the database 9, as illus trated in fig. 7b.

If the mounting element 4 is damaged and need to be replaced, then the servicer may select to enter documentation 20 and, optionally, upload an image of the damaged mounting element 4. The documentation 20 is further stored in the database 9, as illus trated in fig. 7b. The servicer is subsequently able to select and view the inspection history of that mounting element 4, as illustrated in fig. 7b.

During the inspection, the servicer further performs an inspection of the mounting system 1. The servicer accesses the data 13 associated with the mounting system 1 (see fig. 4a) and selects to enter data 21 associated with the inspection of the mounting system 1, as illustrated in fig. 7f. The data 21 may, but not limited to, be entered ac cording to a check list 2G, as illustrated in fig. 7f.

Once the inspection is completed, the data 21 are stored in the database, as illustrated in fig. 7g, and optionally a report of the entered data 21 is generated.

A user of the mounting system 1 is able to access the database 9 using a mobile com puting device 12’. The user accesses the database 9 by reading the unique identifica tion 5, 5’ of the mounting system 1 or of the mounting element 4. At least the status of the mounting system 1 is displayed to the user, as illustrated in fig. 8a-b, so that he/she knows if the mounting system is safe to use (see fig. 8b) or not safe to use (see fig. 8a). The user may, in example, be the site owner, a window cleaner, or an external service provider wanting to service or install external equipment on the roof structure 2

Fig. 8a exemplifies a user on a roof without a harness i.e. without personal safety equipment. There is a warning on the dedicated user interface on the mobile device that the system i.e. the mounting system must not be used since the service date has expired. Fig. 9 shows an exemplary user interface of the administrator module 14 of a regis tered provider. The registered provider is the provider of the installer or servicer. The administrator module 14 is configured to provide to the user an overview 14’ of all selected mounting systems 1 and/or mounting elements 4 linked to that provider. The administrator module 14 is further configured to provide the user with an overview of the certified employees of that provider. The user is able to edit, enter or update the selected data via the administrator module 14.