InnerWeb
Skip to main content

BHP system pilot: server, instance and network in the questions IT administrators ask

The plant's network administrator usually asks the same questions: whether ports must be opened, where the server sits, what happens when outbound traffic is blocked, and whether the pilot leaves anything behind in the production network. Below are answers based on the architecture model and system functions, not on promises.

0
inbound ports on the plant network
Source: karta
443
the only outbound port to the instance (HTTPS)
Source: karta

Do inbound ports have to be opened on the plant network?

No. The architecture model prepared for the IT department has 5 zones: the plant site, users, the plant network, the customer's systems and the cloud in the EU. No inbound ports are opened on the plant network, and outbound traffic is limited to HTTPS on port 443 towards the instance address. For the administrator this means one firewall rule to add and one to verify in the logs.

This layout simplifies risk assessment, because the attack surface on the plant network side does not change: nobody from outside opens connections into the plant floor. Users' mobile devices connect to the instance on their own, and the BLE beacons on site are battery powered and have no connection to the corporate network.

Where does the instance run and what is customer isolation?

Each customer gets an isolated instance with its own database and its own mail system. One plant's data does not sit in the same database as another customer's data, and alerts are sent from a separate sender configured for that instance. In the cloud model the instance runs in a data centre in the EU.

The instance can also run in Docker containers on the customer's server (on-premise), and some environments run on Kubernetes. The choice follows the plant's policy: if the IT department does not allow data to leave its own network, the server stands in its infrastructure. The monthly pilot fee covers the server and the instance, so there is no need to buy a separate machine just for the test (indicative ranges from 2025-2026 deployments; individual pricing).

System footprint on the plant network

System footprint on the plant networkChart: zero inbound ports, one outbound HTTPS 443 port and five zones in the architecture model.012345pcsInbound portsInbound ports: 0 pcs0Outbound portsOutbound ports: 1 pcs1Model zonesModel zones: 5 pcs5
Source: Architecture model for the IT department (5 zones, HTTPS 443)

What to do when the network blocks outbound traffic from the application host?

Alarm webhooks are then stored durably in a queue and are not lost. An external poller collects them through a working inbound channel, meaning one the plant already allows. This is an emergency solution and it is worth being open about it: alarm delivery depends on the polling frequency, so the delay is on the order of one poller cycle, not fractions of a second.

When designing the pilot, record which alarms must reach the recipient immediately and which can wait for a cycle. Alarms concerning life and health are best handled by a channel that passes through the firewall without intermediaries. The queue ensures that a break in connectivity does not mean a lost event.

How does the system determine position and does it need GPS?

The system works without GPS. Position results from signals from many beacons averaged on the map. Plant roads are covered with beacons roughly every 100 m, and inside buildings the assumption is 1 beacon per 100-200 m2. For the network administrator the important point is that location does not require Wi-Fi or wired infrastructure, because the beacons have their own batteries.

The pilot in the rounds model assumes one real route with about 100 beacons and three mobile devices, so the network footprint is small: a few devices communicating with the instance over HTTPS.

What else should be settled with the IT department before the first meeting?

Five matters remain to be settled before the meeting: classification of the system as IT or OT, the directory service for accounts, IP addressing, the network interfaces of the gateway and application whitelisting. The detailed model is produced only after the site survey, so it is not worth guessing values in advance.

A good habit is to give the vendor one page with answers to these five points before installation. This shortens the remote preparation, which in the pilot takes about one week.

Video

Frequently asked questions

Does the pilot require changes to the firewall?

It requires one outbound rule: HTTPS 443 to the instance address. Inbound ports remain closed. Other matters concern addressing, the user directory and application whitelisting, and follow from the site survey.

Can the data stay on the plant's server?

Yes. The instance can run in Docker containers on the customer's server, and some environments run on Kubernetes. In that case the instance's database and mail stay within the plant's infrastructure.

Will an alarm be lost when outbound traffic is blocked?

No. The webhook is stored durably in the queue and collected by an external poller. Delivery time depends on the polling frequency, so for critical alarms set a separate, faster channel.

What does the monthly pilot fee cover?

The server, the instance, licences for 10 users, SLA, and 100 BLE beacons and 3 mobile devices (indicative ranges from 2025-2026 deployments; individual pricing).

Let's talk with the plant's IT department

We will prepare a one-page architecture model for your network and answer the administrator's questions before installation.

Let's talk