The Guardhat Platform takes data from the operational frontlines – via wearable devices, worker inputs and other sensors – and translates that data into actionable alerts and analysis.
The Guardhat Platform is unique in
- Its interoperability with a growing ecosystem of devices as well as IT and OT software applications.
- Extreme flexibility in terms of deployment architecture.
- Its ability to compile all sorts of structured and unstructured data – a large portion of the data people generate – such as audio, video and mobile biometric or environmental data – and aggregate, contextualize, and analyze that data to deliver actionable alerts and reporting.
The platform gives organizations deeper insight into their workforce and the ability to help them meet the challenges they face every day.
No. The Guardhat Platform is available via SaaS subscription without the purchase of Guardhat hardware. However, the platform relies on data from sensors and devices in the field, so some hardware is required. Guardhat integrates with a growing ecosystem of devices and legacy and emerging software solutions. It’s open and agnostic about the hardware that provide the data inputs.
If you are interested in trialing or seeing a demonstration of our platform, please Contact Us.
Guardhat offers intrinsically safe (ATEX / IECEx Zone 1 and C1D1 certified) devices and works with several third-party devices designed for HazLoc environments.
The Guardhat Platform is highly interoperable and captures a variety of worker data based on the application customers require. Worker privacy is core to our offering – across the device, system and process levels. Data can be anonymized, truncated or forgotten, based on customer needs. The types of data we regularly capture and utilize include:
- SOS and fall detection
- Proximity to dangerous or unauthorized zones, equipment and vehicles
- Proximity to other workers for social distancing and track-and-trace
- Biometric information on body temperature, heart-rate and exertion
- Environmental sensor readings to account for exposure to heat, gas, radiation, noise and more.
Guardhat devices support cellular, Wi-Fi and Bluetooth for connectivity to the Guardhat Platform. The system also supports third-party devices with LoRa and Ultra-Wideband technologies. Where no network is available, Guardhat devices use store-and-forward to collect location, sensor readings and key events are transmitted as soon as a network is available.
For a Guardhat system deployed on the Cloud, internet connectivity is required through the a network. For systems deployed on-premises (data center or edge location), internet connectivity is not required.
Detailed compatibility information can be found in our product specifications, if you have further questions, please Contact Us.
Connectivity testing is performed to ensure network performance meets the needs of customers specific use of the Guardhat Platform and selected devices. It requires measuring the Wi-Fi signal bandwidth and LTE signal to help determine the best solution for your needs and ensure implementation success.
The Guardhat team supplies a tool kit package to the site where the solution will be implemented and help on-site personnel to conduct the connectivity testing.
Good signal: -71 to -85 dBm on 3G; -91 to -105 dBm on 4G/LTE, the minimum required for low-resolution audio/visual streaming.
Fair signal: -86 to -100 dBm on 3G ; -106 to -110 dBm on 4G/ LTE, the minimum required for real-time location and telemetry.
Poor signal: -101 to -109 dBm on 3G; -111 to -119 dBm on 4G/LTE, may support reduced frequency location and telemetry, for data collection, will not support real-time data use cases.
Dead zone: lower than -110 dBm on 3G network; lower than -120 dBm on 4G/LTE network, will only support offline functionality.
An EVD0 reading signals the connection is 3G CDMA, which is not adequate for a solution with full audio/visual communication.
Excellent signal: -30 to -50 dBm supports all Guardhat use cases.
Good signal: -50 to -60 dBm is the minimum required for low-resolution audio/visual streaming.
Fair signal: -60 to -70 dBm is the minimum required for real-time location and telemetry.
Poor signal: -70 to -80 dBm may support reduced frequency location and telemetry, for data collection, will not support real-time data use cases.
Dead zone: lower than -80 dBm will only support offline functionality.
For non-audio/video use cases, with data refresh every 1 second or less, the network upload speed should be 3 Kbps or higher.
For audio/video streaming, 2 to 3 Mbps upload and download speed is required for each video stream, depending on desired video stream resolution. This resolution is configurable within the Guardhat system.
For lost or malfunctioning devices, first check the Guardhat Safety Control Center (SCC). The SCC will show the last known location of devices which may be lost or misplaced.
Any device that cannot be retrieved should be immediately marked as “Disabled” on the SCC Device Manager.
Any malfunctioning devices should be returned to Guardhat via issuing a request on the Guardhat Service Desk application. Access to the Guardhat Service Desk has been provided to designated support users within each customer organization. If you don’t know who your support users are, please reach out to us via the Contact Us page.
We recommend devices be stored and charged on customer premises in a secured location or in an area covered via video surveillance to prevent and detect unauthorized access to the devices. Charging lockers are recommended for secure storage.
If dynamically assigned, meaning more than one user shares a common device, users must login to the devices through a supported NFC card or log-in before using the devices and must logout after their shift or when they stop using the devices for the day.
When in transit, devices should be transported in Pelican cases or similar boxes with lock-and-key, to ensure there is no tampering in transit.
Any damaged batteries, charging docks, charging cables or devices present a safety hazard and should be immediately returned in a safe packaging through a request on the Guardhat Service Desk.