CROSS-REFERENCE TO RELATED APPLICATIONS

[001] This application claims the benefit of priority of Israeli Patent Application No. 294852 filed July 18, 2022 titled SYSTEM FOR MONITORING SAFETY AND METHOD OF USE THEREOF, the contents of which are incorporated herein by reference in their entirety.

FIELD OF THE INVENTION

[002] The present invention relates generally to safety monitoring. More specifically, the present invention relates to systems and methods for safety monitoring and management.

BACKGROUND OF THE INVENTION

[003] One of the dangers of the construction industry is workplace accidents, specifically falls. While in most places it is mandatory by law to enter a construction site with proper safety gear, safety gear can only be effective if used correctly. A safety harness, which is commonly used in high-altitude construction operations, is used to secure a worker to a fixed point (e.g., an anchor). The construction worker wearing the harness may be secured to an anchor via a rope, a buckle, a fastener (e.g., a carabiner), etc. which allows the free movement of the worker through the site while preventing accidents. However, safety harnesses can only stop a worker from falling if they are secured to a fixed point and can only prevent injuries if secured properly. For example, an anchor secured at a higher point than the worker (e.g., a ceiling) may be intended to secure the worker via a fastening point on the back of the harness, in order to keep the worker upright in case of a fall.

[004] Furthermore, a manager or supervisor of a construction site may not be able to know if any or all of the workers they are supervising are following standard operating procedures of securing their harnesses. Thus, in the case of a worker not being secured properly, it is difficult to respond in time to prevent an accident.

[005] Therefore, a solution is needed that monitors the safety of a worker operating within a construction site and ensures proper use of a safety harness, and may allow a safety manager of the construction site to manage safety measures compliance in the site. SUMMARY OF THE INVENTION

[006] Embodiments of the present invention are directed to a method of monitoring safety of a user of a wearable computing device, associated with the user, the method comprising: determining the user is in a hazardous zone based on a proximity of the wearable computing device to a landmark device; determining one or more required measures; determining the user’s compliance with the one or more required measures, based on indications received from one or more fasteners associated with the wearable computing device, and issuing a compliance indication, based on the determined compliance.

[007] In some embodiments, the proximity of the wearable computing device and the landmark device is determined based on communication between the wearable computing device and the landmark device over a Bluetooth Low-Energy (BLE) network. In some embodiments, the method further comprises identifying the landmark device, where the determination of one or more required measures is further based on the identification of the landmark device. In some embodiments, the method further comprises sending the compliance indication to a remote computing device.

[008] Some embodiments of the present invention are directed to a system for monitoring safety of a user, the system comprising: a wearable computing device; at least one landmark device; and at least one fastener, wherein each of the at least one fasteners has an unfastened state and a fastened state, and wherein the wearable computing device comprises: a processor, configured to determine compliance with one or more required safety measures based on a proximity to the at least one landmark device and the state of the at least one fastener.

[009] In some embodiments, the landmark device comprises: a processor, and a communication module configured to send an indication of proximity to the wearable computing device. In some embodiments, the wearable computing device is further configured to: determine a proximity to the at least one landmark device, representing a distance between the wearable computing device and the at least one landmark device; identify the at least one landmark device; determine the one or more required safety measures based on the identity of the at least one landmark device; determine the user’s compliance with the one or more required safety measures, based on the state of the at least one fastener, and issue a compliance indication, based on the determined compliance. [0010] Some embodiments of the present invention are directed to a system for monitoring safety of a user, the system comprising: a harness, comprising: at least one fastener, wherein each of the at least one fasteners has an unfastened state and a fastened state, and a wearable computing device, and at least one landmark device, wherein the wearable computing device comprises: a processor, configured to determine compliance with one or more required safety measures based on a proximity to the at least one landmark device and the state of the at least one fastener.

[0011] In some embodiments, the at least one landmark device comprises: a processor, and a communication module configured to send an indication of proximity to the wearable computing device. In some embodiments, the wearable computing device is further configured to: determine the proximity to the at least one landmark device, representing a distance between the wearable computing device and the at least one landmark device. In some embodiments, the wearable computing device is further configured to: identify the at least one landmark device, and determine the one or more required safety measures based on the identity of the at least one landmark device.

[0012] In some embodiments, the wearable computing device is further configured to: determine the user’s compliance with the one or more required safety measures, based on the state of the at least one fastener, and issue a compliance indication, based on the determined compliance. In some embodiments, the system further comprises a remote computing device, where the wearable computing device is further configured to send the compliance indication to the remote computing device.

[0013] In some embodiments, the hazardous zone may be represented by at least a first- level hazardous zone and a second-level hazardous zone, each respectively determined by a first and a second distance between the wearable computing device and the landmark device. The required safety measures may further include: for the first-level hazardous zone, a requirement of a first one or more fasteners of a plurality of fasteners, associated with the wearable computing device, to be fastened; and for the second-level hazardous zone, a requirement of a second one or more fasteners of a plurality of fasteners, associated with the wearable computing device, to be fastened. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The subject matter regarded as the invention is particularly pointed out and distinctly claimed in the concluding portion of the specification. The invention, however, both as to organization and method of operation, together with objects, features, and advantages thereof, may best be understood by reference to the following detailed description when read with the accompanying drawings in which:

[0015] Fig. 1 illustrates a wearable computing device according to some embodiments of the invention;

[0016] Figs. 2A and 2B are illustrations of devices according to some embodiments of the invention;

[0017] Fig. 3A is an illustration of a landmark device according to some embodiments of the invention;

[0018] Fig. 3B is an illustration of a fastener according to some embodiments of the invention;

[0019] Fig. 4 is an illustration of a landmark device according to some embodiments of the invention;

[0020] Fig. 5 is an illustration of a harness according to some embodiments of the invention; [0021] Fig. 6 is a block diagram of a system for monitoring safety according to some embodiments of the invention;

[0022] Fig. 7 is a block diagram of a system for monitoring safety according to some embodiments of the invention;

[0023] Fig. 8 is a block diagram of a system for monitoring safety according to some embodiments of the invention;

[0024] Fig. 9 is a flowchart of a method of monitoring safety according to some embodiments of the invention;

[0025] Fig. 10 is a block diagram of a computing device according to some embodiments of the invention, and

[0026] Fig. 11 is a flowchart of a method of monitoring safety of a user of a wearable computing device according to some embodiments of the invention.

[0027] It will be appreciated that for simplicity and clarity of illustration, elements shown in the figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements may be exaggerated relative to other elements for clarity. Further, where considered appropriate, reference numerals may be repeated among the figures to indicate corresponding or analogous elements.

DETAILED DESCRIPTION OF THE PRESENT INVENTION

[0028] One skilled in the art will realize the invention may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. The foregoing embodiments are therefore to be considered in all respects illustrative rather than limiting of the invention described herein. Scope of the invention is thus indicated by the appended claims, rather than by the foregoing description, and all changes that come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein.

[0029] In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the invention. However, it will be understood by those skilled in the art that the present invention may be practiced without these specific details. In other instances, well-known methods, procedures, and components have not been described in detail so as not to obscure the present invention. Some features or elements described with respect to one embodiment may be combined with features or elements described with respect to other embodiments. For the sake of clarity, discussion of same or similar features or elements may not be repeated.

[0030] Reference is now made to Fig. 1 showing an illustration of a wearable computing device, which may be included in a system for monitoring safety according to some embodiments of the invention. A wearable computing device 100 may include a processor 110 and a communication module 120.

[0031] Processor 110 of wearable computing device 100 may be configured to determine compliance with one or more required safety measures based on one or more received signals, as discussed herein. In some embodiments, processor 110 may send the determined compliance to a remote computing device (e.g., a server), as further illustrated and discussed herein with respect to Fig. 8. In some embodiments, processor 110 may be processor 2 of computing device 100, further illustrated and discussed herein with respect to Fig. 10.

[0032] Communication module 120 may be configured to receive indication of proximity to one or more landmark devices (e.g., via a Bluetooth Low-Energy network), as further discussed herein. In some embodiments, communication module 120 may be configured to communicatively connect to a network (or server), as further discussed herein with respect to Fig. 8. In some embodiments, communication module 120 may be configured to send a signal to processor 110, for example, upon receiving one or more signals from a nearby landmark device.

[0033] Wearable computing device 100 may include a housing 150 (e.g., a plastic enclosure) configured to house components of the wearable computing device 100. In some embodiments, housing 150 may include a removable cover 152, for example, in order to access components of wearable computing device 100.

[0034] Wearable computing device 100 may include a warning unit 180 configured to alert the user of wearable computing device 100. For example, warning unit 180 may be, or may include, an audio indicator or piezo buzzer, configured to produce an audio indication, such as a loud beep, a siren and the like, upon receiving one or more signals (e.g., as sent by processor 110). In some embodiments, warning unit 180 may produce a loud beep or audio alert in order to alert the user. In some embodiments, warning unit 180 may include an audiovisual indication, such as a blinking light and beeps, or the like. It should be appreciated that other alerting or warning methods and units may be used.

[0035] Reference is now made to Figs. 2A and 2B showing illustrations of devices which may be included in a system for monitoring safety according to some embodiments of the invention.

[0036] Wearable computing device 100, as seen in Fig. 2A, may be associated with a proximity sensor 500, as seen in Fig. 2B. Proximity sensor 500 may be configured to determine the proximity between the wearable computing device 100 and at least one landmark device, as discussed herein. In some embodiments, proximity sensor 500 may be, or may include, a magnetic field sensor, configured to detect an electro-magnetic field (e.g., as may be produced by landmark device 400, further illustrated and discussed herein with respect to Fig. 4). In some embodiments, upon proximity sensor 500 detecting an electromagnetic field, proximity sensor 500 may be configured to send a signal to processor 110 of wearable computing device 100 (e.g., via communication module 120 communicatively connected to proximity sensor 500). In some embodiments, upon processor 110 receiving a signal from proximity sensor 500, processor 110 may send a signal to warning unit 180, for example, to warn the user of a hazardous zone nearby. According to some embodiments, proximity sensor 500 may determine an approximate distance from landmark device (200 in Fig. 3A) based on properties of the signal proximity sensor 500 receives from the landmark device (e.g., the intensity of the signal, the frequency of the signal, etc.).

[0037] Furthermore, in some embodiments, processor 110 may be configured to communicate the information about the determined distance (or specific ranges thereof) from the landmark device (200 in Fig. 3A), to warning unit 180. Warning unit 180 may be further configured to alter warning signals or at least one characteristic thereof, correspondingly to the determined distance (or specific ranges thereof). E.g., warning unit 180 may generate signal having different volume, frequency, or pitch, corresponding the determined distance (e.g., the shorter the determined distance, the higher volume, frequency, or pitch is), thereby, respectively informing user of the gradually increasing danger, upon approaching the respective landmark device).

[0038] Reference is now made to Fig. 3A and 3B showing illustrations of components which may be included in a system for monitoring safety according to some embodiments of the invention.

[0039] A landmark device 200 may include a processor 210 and a communication module 220. Communication module 220 may be configured to send an indication of proximity to one or more wearable computing devices 100 (e.g., via communication module 120 of each wearable computing device 100). In some embodiments, processor 210 may be configured to receive one or more signals, for example, from wearable computing device 100. In some embodiments, processor 210 may be configured to send an identity (e.g., a unique identifier) of the respective landmark device 200 to wearable computing device 100. In such embodiments, one or more required measures (further discussed herein with respect to Fig. 7) may be based on the received identity of landmark device 200.

[0040] Landmark device 200 may further include at least one mounting point 240 (e.g., a hole), for example, in order to secure landmark device 200 to a fixed point (e.g., a steel beam). In some embodiments, landmark device 200 may further include a fastening point 230, configured to connect with a fastener (e.g., fastener 300 of Fig. 3B).

[0041] Fastener 300 may include a buckle 330, where buckle 330 may have a fastened and unfastened state. In some embodiments, buckle 330 may connect with a fastening point 230 of a landmark device 200. Fastener 300 may further include a switch 335, configured to sense if buckle 330 is in a fastened or unfastened state. For example, switch 335 may sense that buckle 330 is fastened if buckle 330 is connected to fastening point 230 of landmark device 200. In some embodiments, switch 335 may be configured to send a signal containing the buckle state (e.g., fastened or unfastened) to at least one of: a landmark device 200, and a wearable computing device 100. Fasteners 300 may be selected from non-limiting examples including: buckles (e.g., automotive seatbelt buckles), carabiners, locking snap hooks and/or other fasteners as known in the art. In some embodiments, fastener 300 may be selected based on the intended use, for example, supporting the body weight of a worker in the case of a fall.

[0042] Reference is now made to Fig. 4 showing an illustration of a landmark device 400 which may be included in a system for monitoring safety according to some embodiments of the invention.

[0043] Landmark device 400 may include a processor 410 (e.g., a current controller), and a wire 420 configured to relay a current, for example, from processor 410. In some embodiments, a landmark device 400 may include substantially similar components (e.g., a communication module) to landmark device 200, illustrated and discussed herein with respect to Fig. 3.

[0044] In some embodiments, landmark device 400 may be configured to produce a substantially significant magnetic field E as illustrated. It may be noted that directional arrows in Fig. 4 may be for illustrative purposes only, and magnetic field E may emanate in any direction as produced by processor 410. In some embodiments, wire 420 may be shaped in a loop or fence as illustrated to produce a magnetic field significant enough to be detected (e.g., by proximity sensor 500) from a predefined distance therefrom, where a height h may be, for example, at least 1 meter, and a width w of wire 420 may be, for example, at least 10 meters. In some embodiments, wire 420 may be placed to mark a hazardous zone, for example, an open elevator shaft or a building edge without a railing. It should be appreciated that the height h may affect the properties of the magnetic field E created by landmark device 400. For example, in order to create a magnetic field E that is detectable by proximity sensor 500, from approximately 2 meters, the distance between the horizontal wires of the landmark device, should be at least between 0.8 - 1 meters. The current I also affects the magnetic field, and controlling both the distance between the wires and the current I, may allow controlling the area of the hazardous zone or the distance from the landmark device 400 from which the magnetic field is detectable. [0045] Reference is now made to Fig. 5 showing an illustration of a harness which may be included in a system for monitoring safety according to some embodiments of the invention. [0046] A harness 1000 may include wearable computing device 100, which may be associated with proximity sensor 500. Hamess 1000 may be a safety harness, for example, as used in the construction industry, configured to fasten to a user (or worker) via one or more buckles or straps included within harness 1000.

[0047] Hamess 1000 may include at least one fastener 300a, 300b, and 300c. The at least one fastener 300 (e.g., 300a, 300b, and 300c) may be located at any point along the harness depending on the intended use. For example, a fastener 300a may be located at a back of harness 1000, in order to secure the user to a mounting point (or landmark device) intended for the user’s back. In another example, fasteners 300b and 300c may be located at sides of harness 1000, in order to secure the user to a mounting point intended for the user’s sides. [0048] Upon either proximity sensor 500 detecting a hazardous zone or wearable computing device 100 receiving indication of proximity to a landmark device, a number of required measures may be determined. For example, if the identifier of the landmark device received by computing device 100, indicates that it is marking an open elevator shaft, and thus a fall risk is determined, computing device 100 may determine which of the at least one fasteners 300 are required to be fastened (e.g., a back fastener 300a must be in a fastened state) in order to comply with the safety measures required in this hazardous zone. In some embodiments, computing device 100 may send an alert (e.g., via warning unit 180) to the user based on the state of fasteners 300. In some embodiments, upon the user’s compliance with the required measures (e.g., all respective fasteners secured), an alert may be deactivated.

[0049] In some embodiments, computing device 100 may be further configured to determine the number of said required safety measures further based on the determined distance to the landmark device, thereby determining different levels of hazard. E.g., if it is determined that the user carrying computing device 100 is at the first distance (e.g., a value of said distance within a range, e.g., 5-10 meters) to the landmark device (e.g., in the first- level hazardous zone), computing device 100 may keep sending an alert (e.g., via warning unit 180) while a first fastener (e.g., backwards oriented one) is in the unfastened state, and stop alerting the user once the first fastener is in the fastened state. If it is determined that the user carrying computing device 100 is at a second distance (e.g., a value of said distance within a range, e.g., 0-5 meters) to the landmark device (e.g., in the second-level hazardous zone), computing device 100 may keep sending an alert (e.g., via warning unit 180) while at least one of the first fastener (e.g., backwards oriented one) and second fastener (e.g., sidewards oriented one) are in the unfastened state, and stop alerting the user only once each of the first and second fasteners are in the fastened state, as may be required by the safety measures.

[0050] It shall be understood that the described aspects of controlling compliance with safety measures, and, in particular, the state of the specific fasteners, should not be considered limited to the fasteners (e.g., fasteners 300) that are to be connected to a stationary fastening point (e.g., fastening point 230) only. Said aspects may also relate to fasteners used for connecting together portions of the harness itself in order to facilitate proper harness positioning on the user’s body. E.g., said fasteners may include leg adjustment fasteners, chest adjustment fastener, and waist adjustment fastener. Accordingly, in some embodiments, switch 335 of the respective fastener (e.g., leg adjustment fasteners, chest adjustment fastener, or waist adjustment fastener) may be configured to send a signal of its state (e.g., fastened or unfastened), to processor 110. Processor 110 may be further configured to send a signal to warning unit 180, for example, to warn the user of the respective fastener being in the unfastened state.

[0051] Additionally or alternatively, in some embodiments, warning unit 180 may be further configured to remind user to tighten up the required straps of the harness. Such a reminding message may be triggered, e.g., when processor 110 receives a signal from switch 335 of a specific fastener (e.g., chest adjustment fastener) of changing state from unfastened to fastened, which may indicate that user is preparing to enter the hazardous zone.

[0052] According to some embodiments, wearable computing device 100 may not receive an identification of landmark device 200 or 400. In such cases, where the wearable computing device 100 receives a signal indicating proximity to a landmark device, but does not receive a specific identifier of the landmark device, required safety measures may be determined according to the type of anchoring or fastening device located in the hazardous zone. For example, if in the hazardous zone a single buckle fastening device is placed, the appropriate safety measures may be buckling to the single buckle, via back fastener 300a of harness 1000. If, however, the fastening device has two buckles, the appropriate safety measures may be buckling via the two side fasteners 300b and 300c of harness 1000. [0053] It should be understood that, according to the embodiments described above, proximity to the landmark device (e.g., landmark device 200) and the state of the fastener (e.g., fastener 300) are considered two factors evaluated in combination in order to trigger an alert (e.g., when the user wearing the harness (e.g., harness 1000) is close to the landmark device, but the required fastener is in the unfastened state). However, in some alternative embodiments, these two factors may be evaluated separately (e.g., separate warnings may be provided for informing user of being in the hazardous zone (close to the respective landmark device, e.g., landmark device 200) and of having specific fastener (e.g., fastener 300) in the unfastened state), or any other required logic may be applied in this respect. Therefore, the present invention shall not be considered limited in this regard.

[0054] Reference is now made to Fig. 6 showing a block diagram depicting a system 2000 for monitoring safety according to some embodiments of the invention.

[0055] A system 2000 for monitoring safety may include at least one wearable computing device 100. In some embodiments, system 2000 may include at least one element or component discussed with respect to harness 1000, illustrated and discussed with respect to Fig. 5 herein. At least one wearable computing device 100 may receive indication of proximity to one or more landmark devices 200. In some embodiments, one or more wearable computing devices 100 may receive indication of proximity to one or more landmark devices 200, as illustrated and discussed herein with respect to Figs. 3A and 3B. For example, a wearable computing device 100 may receive indication of proximity to a landmark device 200 via respective communication modules 120 and 220, where communication module 220 is configured to send an indication of proximity to communication module 120 (e.g., via a Bluetooth Low-Energy connection).

[0056] In some embodiments, upon one or more wearable computing devices 100 receiving indication of proximity to one or more landmark devices 200, communication module 120 of computing device 100 may send a signal indicating a proximity status to processor 110. In some embodiments, upon processor 110 receiving a proximity signal, processor 110 may send a signal to a warning unit 180 in order to alert a user of wearable computing device 100.

[0057] Reference is now made to Fig. 7 showing a block diagram depicting a system 2000 for monitoring safety according to some embodiments of the invention. [0058] A system 2000 for monitoring safety may further include at least one fastener 300. In some embodiments, upon one or more wearable computing devices 100 receiving indication of proximity to one or more landmark devices 200, at least one required measure may be determined by the one or more wearable computing devices 100. As referred to herein, a “required measure” refers to a physical condition that a user of wearable computing device 100 must comply with, for example, fastening a fastener. In some embodiments, a required measure may be based on the received identity of a nearby landmark device 200, as discussed with respect to Figs. 3A and 3B . For example, upon wearable computing device 100 receiving a signal containing the identity of one or more nearby landmark devices 200, processor 110 of wearable computing device 100 may determine that one or more fasteners 300 are required to be fastened. In such embodiments, processor 110 may send a signal to warning unit 180 to alert the user. In some embodiments, upon processor 110 receiving at least one indication that all required measures are met (e.g., as received by respective switches 335 indicating all fasteners 300 are fastened), processor 110 may send a signal to warning unit 180 to deactivate the alert.

[0059] In some embodiments, one or more landmark devices 200 may include a switch 235, configured to sense if a fastener 300 is secured to the respective landmark device 200. Switch 235 may be configured to send a signal containing an indication of fastening (e.g., a fastened or unfastened state) to processor 210, which may be sent to wearable computing device 100 (e.g., via a wire connecting switch 235 to processor 210). In such embodiments, upon wearable computing device 100 receiving at least one indication from at least one switch 235 (e.g., via communication module 220), processor 110 may send a signal to warning unit 180 to activate or deactivate an alert.

[0060] Reference is now made to Fig. 8 showing a block diagram depicting a system 2000 for monitoring safety according to some embodiments of the invention.

[0061] A system 2000 for monitoring safety may include a network 1010 configured to communicatively connect one or more wearable computing devices 100 and at least one manager device 900. In some embodiments, upon one or more wearable computing devices 100 receiving indication of proximity to one or more landmark devices 200, a notification 185 may be sent to a network 1010, e.g., via communication module 120 of wearable computing device 100. For example, upon processor 110 determining at least one required measure, and receiving an indication that the at least one required measure is not met, processor 110 may instruct communication module 120 to send a notification 185 to network 1010. In some embodiments, network 1010 may send one or more notifications (or alerts) 185 to at least one manager device 900. In some embodiments, the one or more notifications 185 may contain at least one of: an identity of wearable computing device 100, the at least one unmet required measure, and a location of wearable computing device 100 (e.g., via a GPS module included in wearable computing device 100, configured to determine a geographical location of wearable computing device 100).

[0062] In some embodiments, wearable computing device 100 may communicatively connect to network 1010 via a Global System for Mobile communication (GSM) connection. In some embodiments, wearable computing device 100 may be configured to send the one or more notifications 185 to network 1010 via Message Queueing Telemetry Transport (MQTT) messages.

[0063] In some embodiments, upon the at least one manager device 900 receiving a notification 185, manager device 900 may send a signal to one or more wearable computing devices 100 (e.g., via network 1010) in order to deactivate the alert (e.g., deactivate warning unit 180). For example, at least one manager device 900 may be configured to override an alert of warning unit 180, via processor 110 of wearable computing device 100 receiving a signal from the at least one manager device 900. In such embodiments, in case of a warning unit 180 producing a false alarm, a manager device 900 may be configured to override warning unit 180 and deactivate an alert thereof.

[0064] In some embodiments, manager devices 900 may be configured to monitor the location of wearable computing devices 100, e.g., via receiving intermittent signals over the network 1010 containing a location of wearable computing devices 100. In such embodiments, upon manager devices 900 detecting that one or more wearable computing devices 100 is located in a hazardous zone (e.g., as determined by the received location), manager devices 900 may be configured to send a signal to processor 110 of the one or more wearable computing devices 100 in order to activate an alert of respective warning units 180. [0065] Reference is now made to Fig. 9 depicting a flowchart which may be used to determine whether to alert a user of a harness 1000 or a system 2000 for monitoring safety according to some embodiments of the invention.

[0066] A logical reasoning process of whether to activate or deactivate an alert of a warning module 180 of wearable computing device 100 may be performed by wearable computing device 100 (e.g., via processor 110). A first determination may be decided by detecting at least one landmark device (e.g., landmark device 200 or 400). If a landmark device is not detected (e.g., not detected via a Bluetooth Low-Energy network, or a magnetic field is not detected), a determination is made to not alert the user, therefore not activating an alert of warning module 180. If at least one landmark device is detected, the reasoning process of processor 110 continues to a second determination.

[0067] A second determination may be decided by receiving an indication that at least one fastener (e.g., fasteners 300 of harness 1000) is fastened. For example, wearable computing device 100 may receive an indication containing a state of at least one fastener 300, as discussed herein. If an indication is not received, or an indication is received containing an unfastened state of the at least one fastener 300, a determination is made to alert the user. If an indication is received containing a fastened state of the at least one fastener 300, the reasoning process of processor 110 continues to a third determination.

[0068] A third determination may be decided by validating a compliance of all required measures corresponding to the detected landmark devices. For example, a “compliance” may be validated by comparing the received indications of at least one fastener 300 states to required measures of respective fastener 300 states, as discussed herein with respect to Fig. 7. If all received indications of fastener 300 states are compliant with all required measures (e.g., all back-oriented fasteners 300 connected to back-intended landmark devices 200), a determination is made to not alert the user or deactivate an alert. If received indications of fastener 300 are not compliant with all required measures, a determination is made to alert the user, for example, until a compliance is achieved.

[0069] Reference is now made to Fig. 10, which is a block diagram depicting a computing device, which may be included within an embodiment of harness 1000 or system 2000, according to some embodiments of the present invention. In some embodiments, computing device 1 is an embodiment of wearable computing device 100 of harness 1000 or system 2000, configured to determine compliance with one or more required safety measures based on one or more received signals or indications, as discussed herein. In some embodiments, computing device 1 is an embodiment of manager device 900, configured to receive an indication of safety (or notification 185), as discussed herein with respect to Fig. 8.

[0070] Computing device 1 may include a processor or controller 2 that may be, for example, a central processing unit (CPU) processor, a chip or any suitable computing or computational device, an operating system 3, a memory 4, executable code 5, a storage system 6, input devices 7 and output devices 8. Processor 2 (or one or more controllers or processors, possibly across multiple units or devices) may be configured to carry out methods described herein, and/or to execute or act as the various modules, units, etc. More than one computing device 1 may be included in, and one or more computing devices 1 may act as the components of, a system according to embodiments of the invention.

[0071] Operating system 3 may be or may include any code segment (e.g., one similar to executable code 5 described herein) designed and/or configured to perform tasks involving coordination, scheduling, arbitration, supervising, controlling or otherwise managing operation of computing device 1, for example, scheduling execution of software programs or tasks or enabling software programs or other modules or units to communicate. Operating system 3 may be a commercial operating system. It will be noted that an operating system 3 may be an optional component, e.g., in some embodiments, a system may include a computing device that does not require or include an operating system 3.

[0072] Memory 4 may be or may include, for example, a Random Access Memory (RAM), a read only memory (ROM), a Dynamic RAM (DRAM), a Synchronous DRAM (SDRAM), a double data rate (DDR) memory chip, a Flash memory, a volatile memory, a nonvolatile memory, a cache memory, a buffer, a short term memory unit, a long term memory unit, or other suitable memory units or storage units. Memory 4 may be or may include a plurality of possibly different memory units. Memory 4 may be a computer or processor non-transitory readable medium, or a computer non-transitory storage medium, e.g., a RAM. In one embodiment, a non-transitory storage medium such as memory 4, a hard disk drive, another storage device, etc. may store instructions or code which when executed by a processor may cause the processor to carry out methods as described herein.

[0073] Executable code 5 may be any executable code, e.g., an application, a program, a process, task or script. Executable code 5 may be executed by processor or controller 2 possibly under control of operating system 3. Although, for the sake of clarity, a single item of executable code 5 is shown in Fig. 1, a system according to some embodiments of the invention may include a plurality of executable code segments similar to executable code 5 that may be loaded into memory 4 and cause processor 2 to carry out methods described herein. [0074] Storage system 6 may be or may include, for example, a flash memory as known in the art, a memory that is internal to, or embedded in, a micro controller or chip as known in the art, a hard disk drive, a CD-Recordable (CD-R) drive, a Blu-ray disk (BD), a universal serial bus (USB) device or other suitable removable and/or fixed storage unit. Data related to AOI may be stored in storage system 6 and may be loaded from storage system 6 into memory 4 where it may be processed by processor or controller 2. In some embodiments, some of the components shown in Fig. 1 may be omitted. For example, memory 4 may be a non-volatile memory having the storage capacity of storage system 6. Accordingly, although shown as a separate component, storage system 6 may be embedded or included in memory 4.

[0075] Input devices 7 may be or may include any suitable input devices, components or systems, e.g., a detachable keyboard or keypad, a mouse and the like. Output devices 8 may include one or more (possibly detachable) displays or monitors, speakers and/or any other suitable output devices. Any applicable input/output (RO) devices may be connected to Computing device 1 as shown by blocks 7 and 8. For example, a wired or wireless network interface card (NIC), a universal serial bus (USB) device or external hard drive may be included in input devices 7 and/or output devices 8. It will be recognized that any suitable number of input devices 7 and output device 8 may be operatively connected to Computing device 1 as shown by blocks 7 and 8.

[0076] A system according to some embodiments of the invention may include components such as, but not limited to, a plurality of central processing units (CPU) or any other suitable multi-purpose or specific processors or controllers (e.g., similar to element 2), a plurality of input units, a plurality of output units, a plurality of memory units, and a plurality of storage units.

[0077] Reference is now made to Fig. 11, which is a flowchart of a method of monitoring safety of a user of a wearable computing device according to some embodiments of the invention. In some embodiments, steps S1005 to S1030 may be used to monitor the safety of a user of a wearable computing device 100 (e.g., wearable computing device 100 of harness 1000 or system 2000). In some embodiments, steps S1005 to S1030 may be performed by processor 110 of wearable computing device 100 or by any other suitable processor associated with wearable computing device 100. [0078] In step S 1005, a determination is made if a user of a computing device (e.g., wearable computing device 100) is in a hazardous zone, based on a proximity of the computing device and a landmark device (e.g., landmark device 200 or 400). For example, a computing device 100 may determine (e.g., by a processor 110 of computing device 100) that it is in a hazardous zone upon receiving indication of proximity to landmark device 200, as discussed herein. In some embodiments, computing device 100 may determine that it is in a hazardous zone upon detecting a magnetic field, e.g., from a landmark device 400, as discussed herein. [0079] In some embodiments, computing device 100 may determine that it is in a hazardous zone upon determining a distance between computing device 100 and a landmark device 200, for example, by processor 110 receiving a signal strength of proximity between computing device 100 and landmark device 200. In such embodiments, a predetermined distance (e.g., 1, 2, 5, and 10 meters, and any range and value herein between) representing a distance between devices 100 and 200 may be chosen to differ between a hazardous and non-hazardous zone. For example, a computing device 100 may determine that it is in a hazardous zone upon reaching a 5-meter distance (e.g., as received by computing a signal strength of the estimated distance between devices 100 and 200) to a landmark device 200. In some embodiments, an estimate of distance discussed herein may be computed from a signal strength (or “Received Signal Strength Indicator”) between two nearby devices over a Bluetooth Low-Energy network, as known in the art.

[0080] In step S1010, one or more required measures are determined. In some embodiments, the required measures are determined by processor 110 of computing device 100, upon detecting one or more nearby landmark devices 200 or 400. In some embodiments, the determination of required measures may be based on an identity of landmark devices 200, as discussed herein.

[0081] In step S1020, the user’s compliance with the one or more required measures may be determined. In some embodiments, the user’s compliance may be based on safety indications received from one or more fasteners associated with the computing device. For example, the user’s compliance may be determined (e.g., by processor 110) by comparing one or more received safety indications (e.g., as received by fasteners 300 or landmark devices 200) to one or more required measures determined in step S1010.

[0082] In step S1030, a compliance indication may be issued, based on the determined compliance. In some embodiments, a “compliance indication” may include issuing an alert to the user, via a warning unit 180 of computing device 100. In some embodiments, the compliance indication may be sent (e.g., via a network 1010) to at least one manager device 900, as discussed herein with respect to Fig. 8. In some embodiments, the compliance indication or alert may continue to alert the user until a compliance (as determined in step S 1020) is reached.

[0083] Unless explicitly stated, the method embodiments described hereinabove are not constrained to a particular order or sequence. Furthermore, all formulas described herein are intended as examples only and other or different formulas may be used. Additionally, some of the described method embodiments or elements thereof may occur or be performed at the same point in time.

[0084] While certain features of the invention have been illustrated and described herein, many modifications, substitutions, changes, and equivalents may occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the invention.

[0085] Various embodiments have been presented. Each of these embodiments may of course include features from other embodiments presented, and embodiments not specifically described may include various features described herein.