InnerWeb
Skip to main content

Safety system pilot: recommendations for the IT department

The IT department usually asks the same questions: where does it run, what does it need to see in our network, and does it replace something we already have? In the InnerWeb pilot the answers are short, but they require an informed decision before the start. Below are seven recommendations for IT and OT.

100 m
indicative spacing of transmitters on plant roads
Source: card

Who these recommendations are for

The page is written for IT administrators, OT specialists and architects who receive word from the safety manager or the plant director that a pilot of a new system is coming. They usually hear two sentences at that point and are expected to decide whether the pilot is safe for the network and whether it duplicates existing solutions.

The answers in this text cover three areas: the instance, the network and integrations. Each has a short recommendation and its justification.

Recommendations for the instance

The first question is where the pilot server runs. In most plants the pilot runs on a separate instance with a small number of licences, to keep it apart from the production environment. This gives IT the certainty that the test does not touch critical systems.

1. Set up a separate pilot instance

A separate instance with licences for a dozen or so people makes it possible to test the system without affecting other systems. After the pilot the data can be kept and moved to the production installation, as described on the page about moving to production.

2. Decide who owns the licences

The cooperation model assumes that the implementation partner carries out the deployment and maintenance, while the licence is granted directly by the software vendor under a separate agreement. IT should know whom to contact on technical matters and whom on licensing matters, and reflect this in the purchasing procedure.

Sample pilot kits by type

Sample pilot kits by typeBar chart: 50 transmitters in the no-movement pilot and 100 transmitters in the patrol pilot on one route.020406080100transmittersNo-movement pilot: 50 transmitters50No-movement pilotPatrol pilot (one route): 100 transmitters100Patrol pilot (one route)
Source: InnerWeb pilot kits (indicative)

Recommendations for the network

The most common IT concern is the need to open the network to new devices. In the no-movement pilot this concern is largely unfounded, because the LTE watch has its own SIM card and does not require integration with the plant's network. Traffic from the devices goes through the mobile operator, not through the internal network.

3. Plan transmitter placement with IT and OT

BLE transmitters do not need data cabling or IP addresses in the plant network. Their placement follows the geometry of the site: on plant roads about every 100 m, and inside a building 1 transmitter per 100-200 m². The position comes from signals of several transmitters averaged on the map, without GPS. IT and OT should approve only the mounting locations and the power supply, not the network architecture.

4. Check how mobile devices are managed

Watches with SIM cards are managed through MDM. The IT department should know who has access to the management console, what the update policy is and what happens when a device is lost.

Recommendations for integrations

InnerWeb is an independent system that complements the client's existing systems, such as access control, time and attendance (RCP), HR and ERP. The pilot does not replace any of them, so IT does not need to plan the replacement or migration of these systems.

5. Do not start with integrations

The pilot is meant to show how the system works in one area. Integrations with access control, time recording or the ERP are best planned after the results are assessed. When the pilot moves to production, the scope of integrations follows from experience and is not guessed.

6. Ask about modules and their status

Not every function is available on every installation. The voice assistant is a pilot on one server, enabled by a flag, and the mRCP module is disabled by default. IT should establish with the vendor which modules are in the pilot scope, to avoid disappointment.

7. Record the boundaries of responsibility

It is worth writing on one page who is responsible for the server, the devices, the transmitters and the data. Such a record makes the conversation with the auditor easier, and also the move to production.

What IT gains after the pilot

After the pilot the IT department has concrete data: what traffic looked like, which requirements users raised, which integrations turned out to be needed. It can then plan the production deployment with a precision that no catalogue specification offers.

If the plant decides not to move to production, IT is not left with an unnecessary burden. The pilot instance is separate, and the devices operate on their own SIM cards.

Video

Frequently asked questions

Does the pilot require opening the plant's network?

In the no-movement pilot, no. The LTE watch has its own SIM card, so it does not require integration with the plant's network. BLE transmitters do not need IP addresses in that network.

Does InnerWeb replace the access control or time recording system?

No. InnerWeb is an independent system that complements the client's existing systems, including access control, time and attendance (RCP), HR and ERP.

Who provides the licence and the maintenance?

The implementation partner carries out the deployment and maintenance, and the software vendor grants the licence directly under a separate agreement.

Is the voice assistant available in the pilot?

Not on every installation. It is a pilot on one server, enabled by a flag, and the mRCP module is disabled by default. The scope of modules is set before the start.

Talk to the IT department

We will prepare a short summary of the pilot requirements for IT and OT. Book a call to agree the instance, the transmitter power supply and the module scope.

Let's talk