iTwin IoT or an alternative for structural monitoring?

In brief

• iTwin IoT is a cloud-based IoT monitoring product built on iTwin Platform, with extensive 3D and spatial context.
• Bentley's official documentation confirms an open sensor API, FTP, manual and automatic data, alerts, reports, cases and a mobile app.
• Inclify focuses on automatic HTTP/JSON data, measurement dashboards, acknowledged alarms, chain inclinometry and dynamic analysis.
• Not needing a 3D model is not a weakness of iTwin; it means part of its value may remain unused.
• The safest approach is to compare both processes on one data sample and the same acceptance criteria.

Comparison method and verification date

We verified the comparison on 30 August 2026. We describe iTwin IoT features only on the basis of Bentley's official pages and iTwin Platform developer documentation. Inclify features come from the current product scope. We do not compare prices, because both solutions require a quote for a specific scope.

This is an important caveat. Products evolve, and a marketing page is not a contract. In procurement, ask both suppliers to confirm functions, limits, licensing model, data location, SLA and exit plan in the current offer. If a function is not publicly documented, we do not treat it here as either present or absent. It goes on the list of questions for the demo.

A focused monitoring process means a solution whose basic work unit is a measurement, a channel, an alarm state and an operator decision, rather than a federated digital twin model.

This is not a synonym for "less mature product". It is a different problem scope. A large infrastructure owner may need iTwin IoT for one portfolio and a simpler process for short-term construction monitoring. An integrator may connect both levels through an API. The buying question is therefore not "which product has more features?" but "which features reduce our risk or decision cost?".

What iTwin IoT is, according to Bentley

The official iTwin IoT page describes the product as a cloud-native IoT monitoring platform for infrastructure, built on iTwin Platform. It centralizes sensor data, analytics and alerts, and shows results in charts, dashboards, maps and 3D digital twins.

The spatial scope is broad. Bentley lists design models from multiple CAD formats, reality meshes from photogrammetry, point clouds, ArcGIS layers, WMS and WMTS, sensors in real 3D positions, deformation vectors, alert heat maps and 4D navigation through historical models and IoT data. The official description also includes remote sensing.

The data acquisition layer is not limited to hardware from one manufacturer. The product page points to a sensor-agnostic API, automatic FTP file ingest, manual and automatic data, and storage of raw data alongside sensor configuration. The Sensor Data API is intended for sensor manufacturers and external sources; the documentation shows a connection-device-sensor hierarchy and the ability to send observations for generic sensors.

In operational use, Bentley documents threshold alerts, sensor network status alerts and correlation alerts between two metrics. Recipients can receive e-mail, mobile notifications or in-app messages. The reporting module compiles information and data and schedules document distribution by e-mail. A separate case management process allows tickets related to a change, a model element or an alarm, assignment to a person or role, comments, attachments, images and labels.

The mobile app is used to commission the sensor network, access data and collect manual readings in the field. This is an important difference when a project combines automation with manual measurements.

Functional comparison: facts, not checkbox count

The table does not award points for simply having a feature. If an operator never uses a 3D model, three rows of spatial advantage do not improve the decision. If, however, the sensor needs to be viewed against a reality mesh, GIS layers, the design and the progress, a flat dashboard may be insufficient regardless of alarm quality.

We deliberately wrote "needs confirmation" in two rows. The public iTwin IoT page describes rich time analytics, trends and different chart types, but for a specialized inclinometer profile or a precisely defined vibration analysis, you should ask for a customer-data demo. The lack of specificity in this table is not a statement that the function is absent.

Choose iTwin IoT when digital context is part of the decision

1. The sensor must be visible on the real 3D asset

If the user must move from an alert to a model element, see geometry, point cloud, reality mesh and map layers, iTwin IoT solves a broader problem than a classic dashboard. The iTwins and IoT case documentation shows the use of Sensor Data API to present data, track trends and generate automatic alerts in an iTwin environment.

2. You combine multiple classes of information, not just time series

iTwin Platform is used to federate design, reality, IoT, GIS and business data. If value comes from their shared context, trying to recreate that in a lightweight measurement platform creates a second, thinner digital twin and your own integration debt.

3. You need manual and automatic observations in one tool

Bentley documents import of both data classes and mobile manual readings. For an organization where the field crew supplements the automatic network, this may be a basic requirement, not an extra.

4. An alert must turn into a managed issue

If the process requires assigning a case to a role or person, comments, attachments, images, labels and status tracking in the same environment, the official iTwin IoT case workflow is an important difference from simple alarm acknowledgement.

5. You are building your own application on a digital twin platform

The iTwin Platform provides open APIs and services for application development, digital twin management, visualization, reality data, change tracking, access control and integration. If the company is already investing in this ecosystem, sensor data become another layer in an existing architecture, not a separate island.

6. Correlation alerts, mobile push and scheduled documents are requirements

Bentley lists these functions explicitly. Inclify currently does not offer push notifications, correlation alarms or PDF export. Trying to work around each of these gaps with integrations can erase the benefit of a lighter deployment.

Choose a focused process when the decision starts with the channel and the threshold

1. The project concerns automatic point measurements

If data come from loggers and the main work is checking freshness, charts, thresholds, notifications and acknowledgement, model federation may not create extra value. A simpler information model can then reduce the configuration scope, but you need to test that hypothesis in a pilot with users.

2. You have existing devices and can send HTTP/JSON

Inclify accepts automatic frames with UTC time and raw values, and the history can be sent through the same interface. There is no measurement-file import and no manual form, so this is a good fit only when the integrator controls the transmission from the device or adapter. We describe the process in the guide to connecting existing loggers.

3. The alarm should have a simple, auditable workflow

Inclify distinguishes OK / WARNING / ALARM / NO_DATA, applies per-channel thresholds and hysteresis, and sends e-mail, SMS and in-app notifications. The user acknowledges the alarm, and the platform records who did it and when; temporary silencing until a specified time is possible. This is not a full case management workflow.

4. You need a ready-made chain inclinometer profile

The platform calculates the profile from a fixed anchor point upward, takes segment lengths into account and shows the A, B and resultant axes. The configuration is versioned, and after the first valid frame a profile and trend dashboard is created. This does not apply to manual readings with a probe.

5. You analyze recorded vibration events

Inclify shows the time history, FFT and 21 third-octave bands from 1 to 100 Hz. The available profile uses Butterworth filters, and the dynamic alarm compares RMS and MAX in the bands against a reference envelope. This is a specialized scope; it does not mean automatic compliance assessment against any standard.

6. You want to start with one asset and a clear test

A pilot makes sense when the criteria are narrow: data acceptance, time behavior, duplicate handling, NO_DATA state, alarm, acknowledgement, export and operating overhead. After the pilot, you can decide consciously whether you need richer digital twin context.

Two illustrative examples: the same sensor, a different decision

Example A: a portfolio with models and reality data

Illustrative example. The owner manages multiple assets, has design models, recurring point clouds, GIS layers and sensor data. After alerts, the team creates cases, assigns them to teams, attaches images and tracks closure. In this scenario, 3D context and case workflow are part of the process. iTwin IoT has a natural fit, and a lightweight platform would need an external tool for part of the work.

Example B: automatic monitoring of a temporary excavation

Illustrative example. The contractor has loggers sending measurements automatically, needs charts, thresholds, NO_DATA status, SMS and alarm acknowledgement logging. There is no 3D model and no manual field reading in the app. Here, a simpler process can reduce the configuration scope without losing the required function.

These are not recommendations for every asset. In the first case, you can still use a lighter platform as a data source, and in the second, iTwin IoT may work without full 3D use. The examples only show that the value of a feature depends on the process, not on the length of the feature list.

What this looks like in Inclify

Inclify is a Polish online platform focused on automatic structural and geotechnical monitoring. It can work as a software-only layer for existing devices, a turnkey delivery element or a pilot. The standard ingest method is HTTP/JSON; the platform does not support manual series entry or measurement-data import from files.

Users work on dashboards and charts, not in a 3D digital twin. The specialized scope includes chain inclinometer profiles, dynamic events with FFT and 21 third-octave bands, and alarms with hysteresis, NO_DATA status, e-mail, SMS, acknowledgement and silence until a date. The platform does not have mobile push, rate-of-change alarms, minimum exceedance time or automatic escalation to additional people.

The standard model is an online service. Installation in the customer's infrastructure is technically possible after an individual discussion, but it is not a standard offer. If on-premise is a requirement, treat it as a pre-demo criterion and read the cloud/on-premise matrix. A pilot can be limited to one asset, one data flow and a measurable alarm test.

Demo checklist for a side-by-side comparison

Ask both vendors to work on the same sample and record evidence for each item:

• [ ] Acceptance of current and historical samples with the original time.
• [ ] Behavior when the same observation is sent again.
• [ ] Visibility of a gap and the way missing data is signaled.
• [ ] Passage through warning and alarm levels.
• [ ] Return from alarm state and the hysteresis mechanism.
• [ ] List of notification channels and proof of delivery.
• [ ] Alarm takeover: acknowledgement or issue with an owner.
• [ ] Configuration change and history of values before and after.
• [ ] Required chart, map, section or 3D view type.
• [ ] Manual field measurement, if it is in scope.
• [ ] Inclinometer profile on customer data, if required.
• [ ] Dynamic analysis as needed by the project, not a generic presentation.
• [ ] Report for the real recipient and the required distribution format.
• [ ] Full-period export with identifiers and units.
• [ ] Role model for owner, consultant, contractor and observer.
• [ ] Data location, SLA, backups, RTO, RPO and incident handling.
• [ ] Five-year price with integration, support and exit cost.

A broader set of criteria is in the 30-question checklist for a monitoring platform. In a branded comparison, it is easiest to focus on the brand and skip the basic data tests.

Comparison limits and situations where Inclify does not fit

Public documentation does not show all configurations, modules, limits, licensing conditions or partner-only features. This comparison does not replace the current Bentley demo and offer. Especially specialized geotechnical or dynamic calculations should be confirmed on real data and written into the scope.

Inclify is not the right alternative when the requirement is a native 3D digital twin, federation of CAD, reality data and GIS, manual field readings in an app, a case workflow with attachments, mobile push notifications, automatically generated PDF documents, or a standard on-premise deployment in the customer's infrastructure. Nor should compliance with a standard be assigned to the platform just because it shows FFT or third-octave bands; interpretation belongs to the appropriate specialist.

iTwin IoT can be too broad only in a business sense: the organization may pay configuration and management time for functions it does not use. That does not mean a technical defect. Conversely, a lighter platform may look simpler but fail spatial and organizational requirements. The choice must be tied to the process, TCO and exit conditions.

We do not compare claims about "AI", failure prediction or savings, because they are not needed for a basic compatibility and gap analysis. If AI is a requirement, ask for the data source, validation method, human role, error mode and proof on data from your own asset.

Sources and further reading

1. iTwin IoT - official product page and feature list, Bentley Systems; accessed 30.08.2026.
2. Sensor Data API - Overview, Bentley Developer Portal; accessed 30.08.2026.
3. iTwins and IoT - use case, Bentley Developer Portal; accessed 30.08.2026.
4. iTwin Platform - official product page, Bentley Systems; accessed 30.08.2026.
5. iTwin Platform concepts, Bentley Developer Portal; accessed 30.08.2026.

What next

If you are deciding between iTwin IoT and a focused process, prepare one data sample, a list of required views and a response procedure. We will show which requirements Inclify meets, which it does not meet and what must be verified with Bentley. Schedule a parallel compatibility test, without assuming that the broader or lighter product should win in advance.