This IoT As a Service (IOTaaS) solution is based on a subscription featuring:
- Sensors data can be monitored in Real-Time and visualized from Widgets and Maps in Dashboards.
- Sensor’s historical data (up to 1 year) can be visualized from Charts in Dashboards. Statistical data is calculated and displayed in the chart.
- Multiple dashboards can be easily created and fully customized.
- Easy-to-use Wizards and Solutions-based templates are available to create ready-to-use widgets and dashboards.
- Dashboards can be shared with other people, creating links to access them. Optionally, these links can have an expiration date, to limit the access in a future time.
- Actions Rules and Automation
- Action Rules based on sensor’s value conditions (like “Temperature greater than 30°C”) can trigger User Notifications.
- Automation is possible by setting Actions like “Turn on a Valve/Light”, based on a sensor’s value condition or a preset schedule.
- Sensor’s data anomalies notifications based on Action Rules Conditions.
- Device’s Health notifications to inform the user regarding device status conditions (low battery, weak signal, went offline, etc.).
- All events (from Sensor’s data anomalies and Device’s Health conditions) are recorded (up to 3 months) and can be visualized in a dashboard.
- Users can subscribe to daily/weekly/monthly reports with a summary of activity from all or selected sensors. Charts with sensor data, device health and events reported can be included in these reports.
- Users can export device sensor data in CSV format, to share with other people or upload to other systems for further process or analysis.
- Data Export feature allows a preset range (7/30/90/180/365 days) or a custom range of dates to select.
- Before exporting, users can inspect and analyze the data in a chart and a table, for further comprehension. Statistic information is also provided, based on the range of dates selected.
The IoT Platform provides the following features:
- Account owners can grant access to other people to collaborate, and set restrictions to specific operations.
- Device owners can register the devices in a one-click procedure, making it extremely easy and straightforward to set up a LoRaWAN device, either to a public or private network. Normally, this process requires a deep technical knowledge, but our platform hides all these details from the user.
- Registered devices can be de-registered to transfer ownership to other people.
- Device Remote Configuration: device’s parameters such as reporting interval, alarms, working mode, etc. can be configured from the cloud.
- Device Health Monitoring (Device Status): device’s battery level, wireless signal strength, online/offline state, and last report can be checked from the cloud.
- A default Notification list is created when the account owner signs up. This list uses the Account ‘s email default.
- Notifications can be set up to send alerts and messages using email, SMS or Push Notifications (user should install a mobile App).
- Additional Notification lists can be created, including other recipients to alert specific groups of people based on the nature of the anomaly (i.e.; supervisors, operators, contractors, etc.)
- Alerts and Messages from Action Rules and Device Management can address any of these Notification lists.
- A notification recipient can subscribe to more than one list, to be notified for multiple notification topics.
An IoT hardware device is provided as part of the subscription. The specific device type depends on the solution (check Sensors specifications section). Device’s installation does not require a technician and it can be done by the user. The device uses LoRaWAN communications which is a low-power, long-range, open wireless communication protocol widely used in the US/Europe and many other countries (check https://lora-alliance.org/ for more information). Thus, a LoRaWAN network coverage is required for this service to operate (check Network requirements).
A LoRaWAN-compatible Network is required for the service to operate. Communications costs are included in the service, but the customer has to choose one of the following options:
This is the most convenient case as it does not require a LoRaWAN Gateway, avoiding further setup and configuration. However, public network coverage might not be available in your location (where sensors will be deployed). Please check in this link to ensure this option is supported: https://explorer.helium.com/ Enter the sensor deployment address in the search bar (located at the upper right of the page) and check if there is coverage, looking for a green hexagon covering your location. At the left side, the available gateways (called hotspots) are shown; the more the available hotspots, the better the connectivity.
This option requires a gateway to be installed at the customer site, to provide LoRaWAN wireless coverage to the installed sensor devices. Gateways require an internet connection (ethernet or WiFi) to operate. Customers are required to provide this internet access. Normally, one gateway is sufficient to cover a large facility, but depending on the building, more than one might be needed. Although communications costs are covered, there might be initial costs associated with this option. Please contact us for more details.
When the user subscribes to this IoTaaS solution, a sensor device is shipped to the user. Once it arrives, the user must register the device using the device Serial Number. When the device is commissioned to the LoRaWAN network, the device can be turned on and the sensor's data will show up in the device dashboard, confirming everything works fine. Lastly, the user can deploy the device to the desired location.