hilscher-logo

Mobile alerting with tracking & escalation for Hilscher

signl4-hilscher

 Why SIGNL4

The integration of SIGNL4 with Hilscher enables production staff and service technicians to be alerted quickly and reliably when problems are detected or even before problems arise, no matter where they are.

Production managers have no time to check the dashboards of each and every machine on the shop floor. Therefore it is important to get a notification if some machine needs attention. This gives time to take care of the actual tasks and provided peace of mind, because you are actively alerted when necessary.

 How it Works

SIGNL4 alerts teams and on-call teams on their mobile devices when disruptions in production are detected. Persistent notifications and acknowledgement requirements ensure that issues will be handled before it is too late.

The integration of Hilscher with SIGNL4 can be done via different interfaces, for example via email or webhooks. Here we show the integration using webhooks and Node-RED.

 Integration Capabilities

  • Production staff is alerted via mobile push, text and call
  • Staff can acknowledge and take ownership for critical events that occur
  • Alerts are escalated in case of no response
  • Communicate within an alert to address a particular problem
  • Inbound webhook or email establishes connection from Hilscher to SIGNL4
  • On-call scheduling to alert the right people at the right time

 Scenarios

  • Industrial IoT
  • Industry 4.0
  • IoT Service Alerting
  • IoT Device Management
  • IT, Manufacturing, Utility, Oil and Gas, Agriculture, etc.
FS_neu_2

SIGNL4 receives critical information from Hilscher

Event categorization, routing and automated delivery

Persistent Notifications by push, text and voice call with Tracking, Escalation and Confirmation to Staff on Duty

HOW TO INTEGRATE
In our example, we use a demo setup that consists of several components and covers the entire range from sensor to user alerting.

A distance sensor is connected via IO-Link to an IO-Link Master, then the data is received from a PLC and from there it goes into the Hilscher Edge Gateway. Then an MQTT Broker is used to transfer the data to Node-RED. The Node-RED flow then checks the alerting conditions and then used the SIGNL4 node to send the alert to the SIGNL4 team (or close the alert when resolved).

hilscher-demo

This is how the Hilscher demo setup looks like.

hilscher-node-red

The Node-RED sample flow gets the sensor data via MQTT and then sends (or closes) the alert using the SIGNL4 nodes.

The flow is available here.

ALERT OPTIMIZATION
SIGNL4 can further increase the visibility of alerts through its Signals and Services section. Augmenting the color and icon of alerts will provide more relevant information at a glance without having to open the alert.

alertoptimization

Change alert color and override title + text 

Override text, colors and titles are triggered by keywords set within the mobile app.

Related Integrations

Amazon Alexa

Business / IoT

AppGyver

Business / IoT / IT Ops

AT&T IoT Platform

IoT / IT Ops

AWS IoT Button

Industry 4.0 / IoT

Axonize

Industry 4.0 / IoT

Azure IoT

IoT

Camunda BPM

Business / IoT

Crosser

Industry 4.0 / IoT / IT Ops

Cumulocity

IoT

ELEMENT IoT

Industry 4.0 / IoT

Flic

Business / IoT

GitHub Actions

IoT / IT Ops

Google IoT Core

Industry 4.0 / IoT

Healthchecks.io

IoT / IT Ops

IBM App Connect

IoT / IT Ops

Icinga2

IoT / IT Ops

ifm IO-Link

Industry 4.0 / IoT / production

InfluxDB

IoT / IT Ops

Instana

IoT / IT Ops

IXON Cloud

Industry 4.0 / IoT

Kaa IoT

Industry 4.0 / IoT

Kaseya

Business / Industry 4.0 / IoT

Elasticsearch / Kibana

IoT / IT Ops

Losant

Industry 4.0 / IoT

Ready for a free 30-days trial?

Paste your AdWords Remarketing code here