Hermetry ships five ready-made IoT applications. Each one is built only from what every organisation already has: device profiles with telemetry keys, alarm rules and commands, sites and assets, dashboards with several pages, and flows. You can start from one instead of building every board and rule by hand, and then change anything.
The five solutions
| Solution | For | Profiles | Board pages |
|---|---|---|---|
| Water site | Water tanks and pump stations in zones: levels, pumps, alarms, a process diagram | Tank, Pump station | Site · Regions · Tank levels · Alarms · Tank · Pump station · Diagram |
| Remote sites | Unmanned sites (for example telecom shelters): environment, doors, leaks, smoke, UPS units, cameras | Site controller, UPS | Sites · Alarms · Site · History · UPS · Camera |
| Weather stations | Weather stations: temperature, humidity, pressure, rain, wind | Station | Stations · Station |
| Sensor regions | Temperature and humidity sensors in regions, with per-sensor limits and a floor plan | Sensor, Weather station | Regions · Alarms · Region · Sensor · Weather |
| Personnel tracking | People with trackers: position, zone, falls, SOS, battery | Tracker | Trackers · Zones · Tracker |
Each solution has its own page in Ready solutions with every key, rule and page.
Two ways to use a solution
| Templates (you choose them) | A full installation | |
|---|---|---|
| What you get | The solution’s dashboard as a board template, and its flows as flow templates | Profiles with telemetry keys, alarm rules and commands; sites, assets and relations; sample devices with their limit attributes; the boards; the flows |
| Who does it | Any member who may create dashboards (and flows) | Set up by the platform, not from a page in the console |
| Your devices | You pick your own profiles, devices and sites when you apply the template | Sample (demo) devices are created; you replace them with yours |
Use a board template
- Open Dashboards and select New dashboard.
- Under Start from, pick the solution’s template (for example Water site). The preview shows its pages and cards.
- Answer the template’s questions. A template holds no device of anyone’s organisation, so it asks you to pick, for example, the profile whose devices it shows and the site it covers.
- Enter a Title and select Create.
The board is created with the solution’s pages. Cards that need data the template cannot ask for are left out or replaced by a simpler form:
- cards that read relations between assets and devices (the pumps a tank controls, the UPS that feeds a site, the sensors placed on a region’s plan),
- cards that run a compute script (the weather readings table, the tracker’s route map).
If a widget is not available to you, the board says how many widgets were left out.
Use a flow template
On the IoT host of Automation, start a new flow from a template and pick one of the solution flows:
- four alarm-notification flows that tell the Admin role when an alarm of the solution’s devices opens and clears (and, for personnel tracking, when it is acknowledged),
- the UPS root flow of Remote sites, which stores the readings like the default root flow and adds a watchdog per UPS unit that raises a warning (
ups_a_offline,ups_b_offline) when a unit stops reporting.
A template flow listens to every profile until you pick the profiles. A flow that notifies people is a risk if it runs on the wrong devices: check its profiles before you enable it. See Flow templates.
A full installation
When a solution is installed in full, Hermetry creates the profiles, assets, sample devices, boards and flows in one go, and keeps them up to date when the solution changes (cards someone added are kept). The notification flows are stored switched off until a person enables them. Whether a full installation is available for your organisation is decided by the people who run your installation; ask Hermetry support. See Install a solution.
Demo devices or your own
The solutions expect certain telemetry keys, such as air_temp, air_hum and battery. Your devices probably use other names. Three ways to fit them together:
- Rename in a flow. Keep your devices as they are and rename or convert their keys in the root flow before they are stored. Best when many devices of one kind send the same names.
- Change the board. Edit the cards to read your keys. Best when you have only a few cards.
- For LoRaWAN sensors, save a copy of the codec with your preferred output names.
Some solution features also need data you provide:
| Solution | You provide |
|---|---|
| Sensor regions | Limit attributes on each sensor (maxTempThreshold, minTempThreshold, warnTempThreshold, and the humidity ones); a floor-plan image on the region and each sensor’s position on it. |
| Remote sites | Thresholds per site (highTempThreshold and others); a relation from each UPS to the site it feeds. |
| Personnel tracking | The zone each tracker is in, reported by the tracker or its gateway. Hermetry does not work out zones from positions. |
| Weather stations | Nothing extra; the rain counter has a reset command. |
See Adapting a solution to your devices.
Next step
Build your first dashboard to understand the cards the solution uses, or open the solution’s page in Ready solutions.