Vista Data Vision and Inclify: a fair comparison of two approaches

VDV is a mature Bentley product with token licenses and local or cloud installation. Inclify is a Polish online platform with procedural alarms, FFT and chain inclinometers. We compare the approaches across 20 criteria, with sources, and show how to run a parallel pilot without risk.

Inclify Team Aug 21, 2026 updated Aug 30, 2026 23 min read
Direct answer

Vista Data Vision (VDV) is mature Bentley Systems software for managing data from data loggers, licensed by tokens and installed locally or in the cloud. Inclify is a Polish online structural monitoring platform that is designed to combine sensors, procedure-based alarms, vibration analysis and engineering reports in one panel. They differ in model, not in "quality". The choice depends on whether you are buying a data tool or a monitoring service.

In brief

  • VDV (Bentley) supports many loggers and data sources, has alarms with four thresholds and rate-of-change alarms, automatic reports, calculated variables and "burst" data from vibration loggers, all confirmed by public documentation.
  • The VDV license is based on tokens assigned to project items; local installation requires your own Windows server. Bentley now promotes iTwin IoT as a "more advanced" platform, but there is no official VDV end-of-support date.
  • Inclify is an online platform: OK / WARNING / ALARM / NO_DATA states, alarm acknowledgment and muting with a deadline, FFT and tercials, chain inclinometers, engineering reports, Polish-language interface and support.
  • Stay with VDV if you have a portfolio of projects with active licenses, a hard requirement for local installation, or integrations and alarms that Inclify does not have.
  • The cheapest way to decide: a parallel pilot on one asset with existing loggers - the current system keeps running unchanged.

Disclaimer: we are comparing approaches, not assigning scores

Vista Data Vision is a mature, widely used product. Bentley describes it as software for "Instrumentation Data Monitoring And Management" (Bentley product page), and in its acquisition announcement of 29 April 2021, Bentley called VDV and sensemetrics leaders in infrastructure instrumentation software and sensor management (Bentley Systems announcement). We do not intend to grade VDV - we have no basis for that, and that is not the point of this text.

The point is different. If you are an SHM engineer, geotechnical engineer or contract director and you search for "Vista Data Vision alternative" or "Vista Data Vision price", it is usually because you are facing a decision and worrying about two things. First: that you will be left with a license for a product the vendor is slowly replacing with something else. Second: that migration will break data continuity, frustrate the team and end with a return to the old system after six months. Both concerns are rational, and both can be controlled - that is what this text is about.

We base every hard VDV feature on public documentation, mainly help.vistadatavision.com, as of 22 August 2026, and we cite the source: in the table as a footnote number, in the text as the name of the documentation page. Where we could not find something, we say clearly "no information in public documentation" - which does not mean the function does not exist, only that we cannot confirm it. If you know VDV better and spot an error, write to us and we will correct it.

For broader context on what structural monitoring is and how the "sensor to SMS" architecture works, see the structural monitoring (SHM) guide.

What Vista Data Vision is in 5 sentences

Vista Data Vision is software for collecting, visualising and managing instrumentation data, originating in Reykjavik and now owned by Bentley Systems - the acquisition was announced on 29 April 2021 (Bentley Systems announcement). VDV accepts data from many sources: Campbell Scientific (CSI), Geokon, Sigicom, Axilog, GSS, Loadsensing, Ackcio, Profound, total stations, SAA (Measurand), manual inclinometer probes and files via FTP, SFTP or network drive (VDV documentation: Data Source). Licensing is token-based: "Different items in VDV have Token values associated with them", and project consumption is the number of items multiplied by their token value (VDV documentation: License Overview). The system can be installed locally - the documentation requires current Windows Server, at least 8 GB RAM and 4 CPU cores - or used in a cloud version reached through vdvcloud.com login (VDV documentation: Server Side; Bentley product page). Bentley also states that it is developing iTwin IoT as a "more advanced condition monitoring platform", and the vistadatavision.com domain now redirects to the iTwin IoT page (Bentley product page; iTwin IoT page).

What Inclify is in 5 sentences

Inclify is a Polish online platform for automatic structural monitoring (SHM) and geotechnical monitoring, created by a team that has been designing and maintaining measurement systems for 15 years - from stadiums to hydraulic lock gates. It accepts data from any measurement channel of a logger or hub (the team's hardware offering includes more than 40 sensor types: vibrating wire, inclinometers including chain inclinometers, strain gauges, MEMS, piezometers and temperature sensors), and the loggers in the team's systems normally send readings every 15 minutes by default, or more often. Each channel has WARNING and ALARM thresholds with hysteresis, a NO_DATA state, SMS and e-mail notifications, and a procedure: acknowledgment (who took over and when) and muting always with a deadline. The platform calculates what engineers usually calculate manually: FFT spectrum and 21 one-third octave bands for vibration events, chain inclinometer displacement profile from the anchor, engineering reports (calibration debt, temperature compensation, 7/30-day risk, alarm tuning, data SLA). It is available in three models: turnkey monitoring, the platform only for existing sensors, or a pilot on one asset - with interface and support in Polish.

Table: 20 criteria that actually differentiate

The VDV column contains only what we found in public documentation (numbers in parentheses are footnotes below the table). "No information in public documentation" does not mean "does not exist". The Inclify column describes the platform as it is, including what it does not have - we prefer to state that ourselves rather than have you discover it after deployment. Before deciding, ask both vendors each of these questions directly; you have the full list of 30 questions in the platform selection checklist.

# Criterion Vista Data Vision Inclify
1 License model Tokens assigned to project items, token limit per project [1]; no public pricing found - quote from Bentley or a distributor Online service, quote on request (number of assets, sensors, cooperation model)
2 Hosting Local installation (current Windows Server, min. 8 GB RAM, 4 cores) or vdvcloud.com cloud [2] [3] Online service with no own server; installation in the client's infrastructure is possible by agreement, outside the standard offer
3 Data sources / loggers Long list: CSI, Geokon, Sigicom, Axilog, GSS, Loadsensing, Ackcio, SAA, Profound, total stations, file import from FTP/SFTP/drive [4] Any measurement channel from a logger or hub via HTTP/JSON; the team's hardware offering includes more than 40 sensor types
4 Reading interval Depends on the source (logger, file import) - an architectural feature, with no declared standard Any interval from the logger; in the team's systems, 15 min by default; the platform calculates the actual cadence and data completeness
5 Thresholds and alarm types Four thresholds Low / High / Low Low / High High with deadband [5]; Custom Alarms on average, rate of change or sum over a period, AND/OR conditions [6] WARNING and ALARM per channel with hysteresis, OK / WARNING / ALARM / NO_DATA states, vibration envelope alarm; no rate-of-change threshold (trend - in the 7/30-day risk report)
6 Alarm procedure Confirm per alarm or in bulk, repeat notification until confirmed, two contact groups, custom messages [5] [7]; muting with a deadline and a "who confirmed" record - no information in public documentation Acknowledgment with a record of who and when, muting always with a deadline (up to 365 days), SMS / e-mail / in-app notification according to user preferences; no escalation to additional people
7 Missing data Data Update Alarm - alarm when data do not arrive within the set limit, for the whole site or selected variables [8] NO_DATA as the fourth channel state; configurable window (default 60 min)
8 Vibration: FFT / tercials / envelope "Burst" data from loggers (Sigicom, Profound, CSI), frequency review of events against the project standard, predefined and custom standards [9] [10]; FFT, tercials, envelope - no information in public documentation Time history, FFT spectrum, 21 one-third octave bands 1-100 Hz, 4th order Butterworth filters, RMS/MAX envelope alarm per tercial
9 Inclinometers Import of SAA (Measurand) and manual probe readings (Digipro, Geosense, Gtilt, RST), A and B axes, displacement plots Depth / Distance / Elevation / Convergence [11] [12] [13]; IPI plots according to an older brochure [14] Chain (in-place): profile from the anchor, A/B axes and resultant, configurable segment lengths, maximum resultant displacement, automatic dashboard; no manual probe reading import
10 Reports Automatic daily / weekly / monthly / annual reports with charts, tables and displacement plot, sent to a contact group [15]; reports such as calibration debt, data SLA - no information Engineering reports in the panel: calibration debt, temperature compensation, 7/30-day risk, alarm tuning, data SLA; no PDF and no scheduled sending
11 AI - anomalies No information in public documentation Anomalies (z-score) calculated in the database + language model comment based on the calculated results; the function can be turned off
12 Interface language In help, localisation covers only date and time formats [16]; according to an older vendor page: English, built-in German and Spanish, other languages from a translation template [17]; we did not find a Polish version Polish
13 Support in Poland Vendor support (Bentley) and distributors; no information on support in Poland in public documentation Team in Poland, response to contact within 24 h
14 Time to connect existing sensors No declaration in public documentation (depends on the installation and integrator) A few days for loggers or hubs with HTTP/JSON; deployment with installation - from several to a dozen or so weeks
15 Data export Data Export Task with schedule and FTP delivery; data and chart download from the dashboard [18] [19] CSV for data tables (selected range), chart image, XLSX for dynamic signals; no PDF
16 API / data input Read-only API only (Bearer token, 200 requests/min, up to 20 variables and 10 000 values per variable per request) [20] [21]; data enter through vendor integrations, files and CSI connection [4]; we did not find a write endpoint for measurements HTTP/JSON from loggers and hubs (frames: UTC time, channel ID, raw values); history is sent through the same channel; no CSV/XLSX file import
17 Evidentiary value Alarm Log with status view at the moment of alarm [22]; raw frame log - no information in public documentation Communication log with raw frames (what, when, from which device), default 7 days, configurable period; audit trail of configuration changes (old / new value)
18 Roles and access From administrator to "view" user, roles, access per organisation / project, SSO (including Azure AD) [23] [24] Three permission levels (super administrator, client administrator, read-only), client data isolation, project portfolio in one panel; no per-project roles and no SSO
19 Context widgets No information in public documentation Weather and IMGW warnings, IMGW hydrology, GIOŚ air quality, USGS tremors, NOAA geomagnetic activity; 26 widget types in total
20 Cooperation model Bentley software; formerly also in the offer of hardware distributors - Geokon (2011 brochure) [14], Campbell Scientific Asia (now marked "RETIRED") [25] Turnkey (sensor selection + installation + platform), platform only for existing sensors, or a pilot on one asset

Footnotes to the table (accessed 22.08.2026):

  1. VDV Helpcenter - License Overview: https://help.vistadatavision.com/web-interface/license-overview
  2. VDV Helpcenter - Server Side: https://help.vistadatavision.com/server-side
  3. Bentley Systems - Vista Data Vision product page: https://www.bentley.com/software/vista-data-vision/
  4. VDV Helpcenter - Data Source: https://help.vistadatavision.com/data-source
  5. VDV Helpcenter - Configure Alarms: https://help.vistadatavision.com/alarm/configure-alarms
  6. VDV Helpcenter - Custom Alarms: https://help.vistadatavision.com/alarm/custom-alarms
  7. VDV Helpcenter - Alarm Overview: https://help.vistadatavision.com/alarm/alarm-overview
  8. VDV Helpcenter - Data Update Alarm: https://help.vistadatavision.com/alarm/data-update-alarm
  9. VDV Helpcenter - Viewing Burst Data: https://help.vistadatavision.com/burst-data/viewing-burst-data
  10. VDV Helpcenter - Burst-Standards: https://help.vistadatavision.com/burst-data/burst-standards
  11. VDV Helpcenter - SAA: https://help.vistadatavision.com/data-source/saa
  12. VDV Helpcenter - Manual Inclinometer: https://help.vistadatavision.com/data-source/manual-inclinometer
  13. VDV Helpcenter - Create Displacement Graph: https://help.vistadatavision.com/displacement-graph/create-displacement-graph
  14. Geokon - Vista Data Vision brochure (2011 version, Standard/Pro): https://www.geokon.com/product_images/uploaded_images/vdv.pdf
  15. VDV Helpcenter - Reports: https://help.vistadatavision.com/web-interface/reports
  16. VDV Helpcenter - Localization: https://help.vistadatavision.com/web-interface/localization
  17. Former vendor page "Languages and the translation of VDV" (vistadatavision.com/features/languages; the address now redirects to bentley.com, content available in search engine index)
  18. VDV Helpcenter - Data Export Task: https://help.vistadatavision.com/web-interface/data-export-task
  19. VDV Helpcenter - Dashboard: https://help.vistadatavision.com/dashboard
  20. VDV Helpcenter - API: https://help.vistadatavision.com/web-interface/api
  21. VDV API - OpenAPI 1.1.0 specification: https://apidocs.vdvcloud.com
  22. VDV Helpcenter - Alarm Log: https://help.vistadatavision.com/alarm/alarm-log
  23. VDV Helpcenter - Users in VDV: https://help.vistadatavision.com/web-interface/users-in-vdv
  24. VDV Helpcenter - SSO: https://help.vistadatavision.com/sso
  25. Campbell Scientific Asia - Vista Data Vision (marked "RETIRED"): https://www.campbellsci.asia/vista-data-vision

Three notes on the table. First, items 5-7 show that both systems have thresholds, notifications and missing-data detection, while VDV also has rate-of-change alarms that Inclify does not have - the difference lies in how deeply the procedure is built into the product (who took over, until when muted), and you can only check that live. Second, item 3 is a real strength of VDV: the list of supported sources is long and includes equipment that many measurement firms have worked with for years. Third, items 10 and 15 favour VDV if your clients expect reports sent on a schedule - Inclify generates reports in the panel, without PDF.

Where the real difference lies: data tool or monitoring service

A structural monitoring platform is software that collects measurements and turns them into a decision: threshold, alarm, responsible person, evidence. It is worth keeping this definition in mind, because the VDV documentation describes the product more as a data layer: imports from sources, virtual variables ("new calculated variables that are a mathematical function of one or more sensor readings" - VDV documentation: Virtual Variables), charts, reports, alarms, read-only API. This is a very flexible approach - but flexibility means that you build procedures, compensations and interpretation yourself or with an integrator.

Inclify goes the other way. Some things are "fixed" by design: a channel always has four states (OK / WARNING / ALARM / NO_DATA), an alarm always has an acknowledgment and muting path with a deadline, a chain inclinometer always has a profile from the anchor, a vibration event always has FFT and tercials. Less configuration freedom, more ready-made answers to the questions engineers actually ask. The price of that rigidity is real: if you need a rate-of-change alarm or a report sent every Monday at 7:00, VDV has that today, Inclify does not.

Illustrative scenario: excavation, two probes and one decision

Imagine a contract manager with a diaphragm wall, two chain inclinometers and six vibrating wire strut load cells. In the evening, deflection at 6 m depth increases. In a "data tool" approach, someone must first build the profile plot, a virtual variable for displacement from the anchor, an alarm on that variable and a contact list - all of it is possible, and VDV documentation shows both virtual variables and complex alarms with AND/OR conditions (VDV documentation: Custom Alarms). In a "monitoring service" approach, the same scenario is the default view: profile, channel state, SMS to the on-duty person, acknowledgment in the panel and a record of who took over. Both approaches lead to the same decision. The difference is the time and competence needed to reach it - a topic we expand on in the benchmark post 100x faster: from event to decision (this multiplier applies to periodic measurement versus continuous monitoring, not to any competitor comparison).

What it looks like in Inclify

On the project dashboard for the excavation, you see channel states, a chart with two axes - tilt against temperature, so you can separate daily "breathing" from a lasting trend - and an automatic chain inclinometer dashboard with a vertical profile. When the WARNING threshold is exceeded, you get an SMS and e-mail (according to your notification preferences), the alarm waits for acknowledgment, and if the crew is working at the wall and you know the cause of movement, you mute it for a defined time. The raw frame from the logger stays in the communication log (default 7 days, configurable period), and the measurements stay in the database without automatic deletion, so you can check exactly what came in and when. The AI analysis adds an anomaly comment (z-score), but the engineer makes the decision.

Is VDV being phased out? What is known, and what is not

This question comes up in almost every conversation about VDV, so we answer it exactly as the sources show, without adding anything. Facts: the vistadatavision.com domain redirects to the iTwin IoT page; the VDV product page at Bentley still exists and contains the sentence about a "more advanced condition monitoring platform, iTwin IoT" - without words about retirement, end of support or a date; Bentley describes iTwin IoT as the product that absorbed the capabilities of sensemetrics and VDV; VDV documentation and API are publicly available, and the API gives a support contact in the Bentley domain. On the other hand, Campbell Scientific Asia marks its VDV offer as "RETIRED - This product is no longer available" (Bentley product page; iTwin IoT page; Campbell Scientific Asia).

What this means for you: do not write in a board note that "VDV is retired", because that is not known. Write that the vendor promotes a successor platform and ask Bentley or the distributor for three things in writing: the VDV development plan, migration terms to iTwin IoT and the data release mode after the license ends. Ask the same three questions of every other vendor too, Inclify included.

When to stay with Vista Data Vision

Not every change makes sense. Stay with VDV if you recognise yourself in any of the points below.

You have a portfolio of projects with active licenses and an established process. If your team has spent years configuring virtual variables, reports and alarms in VDV, and clients receive those reports every week, the migration cost includes the license, training and reworking the configuration. VDV documentation shows export and import of virtual variables (VDV documentation: Virtual Variables) and bulk operations on alarms (help category "Bulk Alarm") - this is mature tooling and there is no reason to give it up without a clear benefit.

You have a hard requirement for local installation. Some clients, such as critical infrastructure operators or mines, require that data do not leave their network. VDV documents local installation on Windows Server and explains how to make backups and migrate to a new server (VDV documentation: Server Side). Inclify is delivered as an online service; installation in the client's infrastructure is technically possible, but that is a case for individual agreement, not a standard offer - if the requirement is absolute and urgent, VDV has a documented advantage here.

You need functions or integrations Inclify does not have. Direct import from total stations, SAA Measurand, import of manual probe readings in Digipro, Geosense, Gtilt and RST formats, control of Campbell loggers with commands from the interface, import of images from cameras, SSO with Azure AD (VDV documentation: Data Source, CSI, SSO). Add to that rate-of-change or period-sum alarms (Custom Alarms), reports sent on a schedule and scheduled FTP export. If any of these sources or functions are part of your daily work, ask first how Inclify would handle them before you start the conversation - the answer may well be "not yet".

You are a measurement service provider and want your own brand on the data. VDV documentation describes an Embed API for embedding charts and dashboards in external websites (VDV documentation: Embed API). If you are building your own client portal, that is a material function.

If you recognised yourself in two or more points, stay and return to this post when your licensing situation or client requirements change.

When Inclify is the better choice

You want to buy monitoring, not an IT project. If your team does not have someone who will maintain the server, configure virtual variables and write alarm procedures, a platform with a built-in procedure (acknowledgment, muting with a deadline, who took over) and ready-made engineering views shortens the path from installation to the first SMS. There are three cooperation models: turnkey with sensor selection and installation, platform only for your sensors, or a pilot on one asset.

You measure vibrations and chain inclinometers. If you have a vibration station and need to assess an event in one-third octave bands (for example under PN-B-02170 - SWD scales), or a diaphragm wall with chain inclinometers where every day you ask about maximum deflection and its depth - these calculations are native in Inclify, not something you need to build. VDV handles burst data from vibration loggers, with frequency review of events and project standards (VDV documentation: Viewing Burst Data), but we did not find FFT spectra, 21 one-third octave bands or an envelope alarm in the public documentation.

Management reads reports in Polish and asks, "is it safe?" Engineering reports - calibration debt, temperature compensation, 7/30-day risk assessment, data SLA - answer the questions that come up in meetings, not only in the measurement department. A Polish interface and support are for many teams not a convenience, but a condition for the system to actually be used by the site manager and asset owner.

You need evidence, not just a chart. A communication log with raw frames (for a configured period) and an audit trail of configuration changes (who, when, old and new value) let you reconstruct what came from the device and what someone changed in thresholds or equations in the meantime. In a dispute with a neighbouring excavation or after an incident, that is concrete evidence. How to set thresholds so alarms are reliable is described in a separate post on alarm thresholds in structural monitoring.

What this means for you: if your daily questions are "who took over the alarm", "how much was in tercials" and "at what depth is the maximum", not "how do I import a total station file", Inclify answers them without configuration.

How to run a parallel pilot without risk to current monitoring

A parallel pilot means running a second platform on the same data, without switching off the current one. It is the best way to compare not promises, but how both systems behave with your sensors and your people. Steps:

  1. Choose one asset with existing loggers. Ideally one with both static channels (vibrating wire, inclinometers) and at least one troublesome channel (temperature drift, transmission gaps).
  2. Send a copy of the data to the second platform. Loggers and hubs that can send data via HTTP/JSON can be connected to Inclify in a few days; the current flow to VDV remains untouched. Details are in the article how to connect existing loggers to an online platform.
  3. Copy the thresholds 1:1. The same WARNING/ALARM values on both sides. Otherwise you will be comparing configurations, not systems.
  4. Set an observation period and a list of events to compare. Illustratively: 4-6 weeks, including at least one transmission gap (how both systems showed missing data), one threshold exceedance (who got the SMS, who confirmed it, how long it took) and one temperature spike (did the two-axis chart distinguish breathing from trend).
  5. Invite people from outside the measurement department to the panel. Site manager, asset owner, someone from management. Ask them to answer one question without training: "is it safe today and how do you know?"
  6. Calculate total cost over the same horizon (for example 3 years) for both options. Licenses or subscription, server and its maintenance (if local), people time for configuration and reports, support. No amounts in this text - Inclify pricing is quote on request, and VDV tokens are priced by Bentley or a distributor.
  7. Decide based on events, not impressions. If after the pilot both systems behaved equally well and you have active VDV licenses, stay. If the difference was in procedure, response time or clarity for non-engineers, that is your answer.

Migration: what happens to existing loggers and history

Migration to Inclify does not mean replacing hardware. If the asset already has loggers or hubs that can transmit data via HTTP/JSON, the platform accepts them directly (frames with UTC timestamp, channel identifier and raw values, processed by project equations), and connection takes a few days. Vibrating wire sensors, inclinometers, strain gauges and MEMS remain in place. If the logger sends data only in another format, clarify this before the pilot - that is the first question we ask in the introductory call.

History from the previous system: Inclify does not have CSV/XLSX file import or a form for manual series entry. However, the archive can be sent through the same HTTP/JSON channel, with original timestamps - with no data age limit. In practice, this means exporting from VDV (Data Export Task) and sending the history once in frame format; the scope, who does it and how we verify consistency are agreed in the introductory call. It is worth doing this while the pilot is still running, before the old license expires.

FAQ

Does Vista Data Vision have an alternative on the Polish market?

Yes. Inclify is a Polish online platform for structural and geotechnical monitoring, accepting data from any loggers via HTTP/JSON, with procedure-based alarms, vibration analysis (FFT, tercials) and chain inclinometers. It differs from VDV in model: instead of a token license and local or cloud installation, it offers an online platform with turnkey deployment, the platform only for existing sensors, or a pilot on one asset.

How much does Vista Data Vision cost?

Public VDV documentation describes token licensing: project items have token values, and the sum gives project consumption (VDV documentation: License Overview). We did not find concrete prices or token values for individual items in public sources - they are quoted by Bentley or a distributor. Inclify also quotes individually, based on the number of assets, sensors and the cooperation model. In both cases, ask for a 3-year cost simulation.

Do I have to replace loggers to switch to Inclify?

No, if the existing loggers or hubs can send data via HTTP/JSON. In that case, connection takes a few days, and the sensors stay on the asset. If the logger communicates only in another format, we check that in the introductory call before you start the pilot. Full deployment with installation of new sensors takes from several to a dozen or so weeks.

Does VDV support inclinometers and vibration data?

According to the documentation, yes: VDV imports SAA Measurand data and manual inclinometer probe readings with A and B axis plots (VDV documentation: Manual Inclinometer, SAA), and displays burst data from vibration loggers (Sigicom, Profound, CSI) with a frequency review of events against the project standard (VDV documentation: Viewing Burst Data). We did not find FFT spectra, 21 one-third octave bands or a chain inclinometer profile calculated from the anchor in the public documentation.

Can I use VDV and Inclify at the same time?

Yes, and that is the recommended way to decide. A parallel pilot means sending a copy of data from the existing loggers to Inclify while keeping the current flow to VDV. For several weeks, you compare how both systems behave with the same thresholds: missing data, exceedance, acknowledgment, clarity for people outside the measurement department. Only then do you decide.

Is the comparison in this post objective?

It is fair within the limits of public sources. We base every VDV feature on documentation with a given address, and what we did not find we call "no information in public documentation" instead of guessing; in the Inclify column we also listed what the platform does not have. We do not evaluate VDV quality - we compare two approaches: a data tool with its own process around it versus a platform with a built-in procedure. This text is not legal advice or a commercial offer; before deciding, verify both systems on your own data.

Sources and further reading

What next

If you have an asset with existing loggers and want to compare both approaches on your own data, the simplest step is a parallel pilot on one asset: connection takes a few days, the current system keeps running unchanged, and you can still send the history during the pilot before the old license expires. See what the Inclify panel looks like, learn about the cooperation models and book a pilot call - we respond within 24 hours.

Keep reading

Related articles

All articles

Monitoring a structure? Book a demo

We will show the platform using an asset similar to yours and discuss where the measurement programme should start. No obligation.

Book a demo Explore the platform