Why closed networks are common in plants
In many production plants the IT and OT departments block all outbound traffic from servers in segments linked to production. This is a justified protective practice: it reduces the risk of data leakage and of communication with unknown addresses. For a system that is meant to send alarms, it means that a different delivery path has to be planned.
The partner is responsible for the rollout and maintenance, so it leads this conversation with the IT and OT departments. The manufacturer provides the mechanisms, and the client decides which of the permissible solutions to choose.
How the system behaves without outbound traffic
When the client's network blocks all outbound traffic from the application host, webhook alarms are stored durably in a queue. An external poller collects them over an inbound channel and delivers them onward, to the notification platform or to on-call phones. The alarm is not lost, even if the host cannot open a connection to the internet on its own.
For the partner this means the network requirements can be limited to an inbound channel and an agreed place where the poller runs. The IT and OT departments keep their policy of blocking outbound traffic, and the system still performs its alarm function.
Sample time budget of the alarm path in the acceptance test
List of points to agree with the IT and OT departments
Below are the points the partner should discuss before installation. It is best to write them down in a short record of agreements signed by both sides.
- where the poller sits and who is responsible for maintaining it
- which inbound channel is allowed and from which addresses
- how long messages are kept in the queue when the poller is unavailable
- who monitors the state of the queue and which thresholds trigger a report
- which alarm delivery channels to phones are allowed in the plant
- how to proceed during planned network outages
Integration with the client's systems in a closed network
The platform offers a REST API in versions 1 and 2 with JWT authentication, and webhooks to the automation platform. In a network without outbound traffic, integrations with internal systems, for example access control, are usually run inside the segment, and only the delivery of alarms to the outside goes through the poller.
InnerWeb does not make or replace access control readers and integrates with the client's existing access control system. A partner that is also the installer of the access control system has an easier conversation, because it knows the network segments and the access rules.
Roles in the system and administrative access
Roles in the system and the permissions matrix let you configure access for administrators, security, OHS and the coordinators of external companies without any change to the code. In a closed network it is worth limiting the partner's administrative access to the host to agreed service windows, and recording in the maintenance agreement who may connect and when.
Also settle how the partner handles a category A report if remote access requires the client's consent. The sample SLA provides for a reaction in 12 hours and a repair in 8 hours, so the consent procedure must fit within those times.
Tests before acceptance
Before acceptance, test the whole alarm path: trigger the event, check the entry in the queue, the pickup by the poller and the delivery to the phone. Record the time of each step. Also test with the poller disconnected, to confirm that messages wait in the queue and arrive after the connection is restored.
Video
Frequently asked questions
Is an alarm lost when the host has no outbound traffic?
No. Webhook alarms are stored durably in a queue, and an external poller collects them over an inbound channel and delivers them onward.
Who maintains the poller?
This should be agreed with the IT and OT departments and recorded in the maintenance agreement or in the record of agreements.
Does the plant's network policy have to change?
Usually it is enough to allow the agreed inbound channel. The block on outbound traffic from the application host can remain in place.
Let's plan a deployment in a closed network
We will discuss the webhook queue and the poller with your IT and OT departments. Book a call or a demo.
Let's talk