Purpose

This page summarises the network connectivity (firewall/ports), data flow, and security controls required to deploy IntelliAM’s wireless condition monitoring solution (slow speed sensors, on-site gateway, third-party cloud, and IntelliAM Azure platform).

Connectivity requirements for customer IT/OT and firewall teams

The on-site gateway requires outbound access to the internet to transmit sensor data and (where enabled) to support vendor maintenance and time synchronisation.

Mandatory outbound firewall rules (standard operation)

Allow outbound TCP 443 (HTTPS) from the gateway to:

• isee.icareweb.com (Europe) / isee.gw.icareweb.com
• Endpoints (as provided for the deployment region):
  • 54.93.176.77
  • 3.68.164.185
  • 3.73.189.202

Additional outbound firewall rules (recommended)

These are not always needed; but handle troubleshooting and firmware upgrade tasks.

Vendor maintenance:

• saltmaster.icareweb.com, TCP 4505–4506
• gws.icareweb.com, TCP 22 (SSH)
• Time synchronisation:
• pool.ntp.org, UDP 123

On-site wireless communications (no customer network routing required)

• Sensors communicate to the gateway over IEEE 802.15.4 (2.4 GHz, 2400–2483.5 MHz).
• This traffic stays local (sensor-to-gateway) and does not traverse the customer IP network.

What data is transmitted

• Vibration waveforms and spectra (raw and derived metrics)
• Shock pulse / ultrasonic indicators
• Temperature (sensor/internal)
• Device status (battery, signal strength, connectivity)

Data flow (high level)

• Gateway sends sensor data to the vendor cloud over HTTPS (TCP 443).
• IntelliAM’s Azure platform polls the vendor cloud via secured REST APIs (typically every 30 minutes) and processes the data to generate insights and maintenance actions, which are then made available via web application and email (as applicable).

Security controls

• Transport encryption: TLS 1.3 for HTTPS/API traffic
• API security: JWT-based authentication for third-party APIs
• IntelliAM platform controls: Azure Key Vault for secrets, Entra ID with RBAC, and audit logging

Data privacy

• No personal data (PII) is required for sensor data processing.
• Customer operational data is stored with logical separation controls and governed by retention policies (raw data commonly retained for a defined period, processed outputs retained for trending and reporting, subject to agreement).