Beyond Monitoring is a better fit when a project needs one environment for automatic and manual measurements, offline work, GIS, scheduled reports, or a standard deployment in the client's infrastructure. Inclify fits an automatic sensor process where confirmed alarms, data quality, inclinometer profiles and vibration analysis are key. Without separating these needs, the request for quotation will compare two different service classes.
In brief
- Beyond Monitoring is, according to Sixense, an online GIS and data platform available as SaaS and in the client's infrastructure, with an app for manual measurements offline.
- Inclify is an online service focused on automatic data intake through HTTP/JSON; it has no manual series entry, no native offline app and no standard local deployment offering.
- Inclify has a confirmed alarm process: thresholds, hysteresis, no data, acknowledgment, repeat blocking, temporary mute, e-mail, SMS and in-app notifications.
- Do not buy width "for later". Each required data type should have an owner, a usage frequency and an acceptance test.
- The pilot must cover flow failure, not only a correct panel: missing data, configuration change, export and operator response.
The status of Beyond Monitoring functions was verified on 30 August 2026 on the official Sixense website. We describe only the scope publicly declared. We do not assess performance quality, price or functions available in individual deployments.
Two different answers to the same problem
A tailor-made platform is an environment whose sources, calculations, views and workflows are configured for a specific operation. A focused SaaS delivers a smaller, repeatable set of processes. It fits only when the project requirements stay within its boundaries.
Sixense describes Beyond Monitoring as a platform for managing, visualising and reporting geotechnical, structural and environmental data. The system integrates different sensors and external sources, including photos, documents and work progress. It has an online GIS, configurable processing, alarms, dashboards, automatic or manual reports and a mobile app for collecting and validating manual readings offline. The manufacturer offers a SaaS cloud model and a variant in the client's infrastructure for sensitive facilities.
Inclify solves a narrower problem. A recorder or concentrator sends automatic data through HTTP/JSON. The platform validates frame time and structure, stores UTC, applies project equations, shows data on dashboards and evaluates alarms. It has a ready-made vertical chain inclinometer profile, dynamic event analysis, a data quality report and an operational alarm history. The service is online by default. Installation in the client's infrastructure can be discussed separately, but it is not a ready-made catalogue option.
The difference is not simply "large versus small". A broad platform supports more source classes, but it requires design work for their configuration and responsibilities. A narrower SaaS has a smaller standard scope and should not be forced into a contract that requires functions it does not have. A sound purchase starts with a fit-and-gap analysis, not with the number of features.
Four questions that decide the choice before the demo
Are manual readings part of the source system
If technicians are to go out with a probe, level, total station or another instrument and enter results in the field without coverage, the requirement is clear. Sixense declares a mobile app for manual measurements, validation and offline work. Inclify does not have a form for manual series entry or import of CSV/XLSX files with measurements. A reference can be set in it, but that does not replace a field campaign.
This criterion should have a result of "meets" or "does not meet". Do not write a general "the system supports manual data" in the request for quotation. Define the device, format, offline work, validation, corrections, approver, synchronisation and audit trail. The remaining criteria are organised by the platform selection checklist.
Do you need GIS as the main interface
Beyond Monitoring is publicly described as an online GIS with map services. This matters in linear infrastructure, tunnels, rail, large excavations and spatially distributed programmes. If the daily decision starts from a map and its relation to work progress, ask for a demo on the plan of your project.
Inclify offers dashboards, charts, tables, alarm views, documents and contextual data. It should not be sold as a digital twin or a full GIS. If the map is only one context, the narrower interface may be enough. If it is the core working model, there is a functional gap.
Is on-premise a condition or a preference
Sixense declares an on-premise variant in the client's infrastructure for sensitive locations. Inclify is an online service by default, and a local deployment requires an individual discussion. Do not write "local deployment preferred" if security really requires it. Define network segmentation, updates, backup responsibility, RTO, RPO, service oversight and service access. The full decision matrix is in the cloud or client's infrastructure guide.
If the local deployment results only from habit, calculate the maintenance cost over the full contract period. A server in a cabinet does not update itself, and application availability tells you nothing yet about the freshness of field data.
Are you buying a platform or an expert service
Sixense combines software with many years of experience and monitoring services. That is a separate scope in a complex programme, where the supplier is expected to design, install, interpret and maintain the entire system. Inclify can also be delivered turnkey with sensor selection and installation, as a platform for existing sources, or as a pilot. The expert scope of both offers must be compared separately from the product functions.
In the request for quotation, separate four items: instrumentation design, installation, platform and interpretation. Then it is clear whether you are paying for software, engineer responsibility, field service, or all of these elements.
Beyond Monitoring and Inclify: a fair fit-and-gap analysis
| Requirement | Beyond Monitoring according to Sixense | Inclify - current scope | Purchasing verdict |
|---|---|---|---|
| Automatic sensors of many types | declared integration of various formats and acquisition systems | HTTP/JSON under an explicit contract | both for pilot on a trial frame |
| Manual measurements offline | native mobile app, collection and validation | none | requirement excludes Inclify |
| GIS and map services | online GIS | dashboards, not a full GIS | choice depends on the main process |
| Photos, documents, work progress | declared external sources | document library and documentation widget; no work progress process | confirm required workflow and metadata |
| SaaS | declared cloud hosting | standard delivery form | both, compare responsibility and SLA |
| Client infrastructure | declared variant | individual arrangement, not standard | Beyond has a publicly described variant |
| Scheduled reports | automatic or manual reports by preference | engineering reports in the panel, CSV/images/XLSX; no automatic PDF | required artefact decides |
| Alarms | configurable system, managed from the app | thresholds, NO_DATA, hysteresis, acknowledgment, repeat blocking, temporary mute | test the full procedure |
| Organisational escalation | scope needs confirmation | no automatic escalation chain | procedure remains on the human side |
| Data quality | must be confirmed in the pilot | cadence, completeness, gaps and freshness report | force a controlled gap |
| Chain inclinometer | concrete view compatibility must be shown | profile from fixed base, A/B/resultant, configuration versions | compare the same chain |
| Vibration analysis | scope must be verified in the current product | time history, FFT, 21 third-octave bands, RMS/MAX | same frame and reference result |
| Audit trail | scope must be confirmed | configuration changes before/after, alarm history | run a change scenario |
| Polish interface and support | to be agreed in the offer | available | check with end users |
This table shows why a simple yes/no list can mislead. Both systems have alarms, but it matters whether the alarm has acknowledgment, an owner, a mute function and history. Both have reporting, but only a specific document will tell you whether the report meets the contract. Both can store data, but the purchase is decided by the output format and configuration context.
Illustrative scenario: a metro project with automatic and manual measurement
Imagine a section of metro construction. The project includes automatic piezometers, chain inclinometers and force sensors, but also weekly levelling measurements and manual readings in places with no connectivity. The investor requires GIS, a monthly report and work in its own infrastructure. This is an illustrative example, not a description of a client deployment.
In this setup, Beyond Monitoring covers a larger share of the requirements: it publicly declares integration of many formats, a manual offline app, GIS, reports and a client-infrastructure variant. Inclify can handle the automatic part, the inclinometer profile, data quality and alarm response, but it will not close the entire scope in one product. These gaps must be written down before the choice.
Change the conditions. The project has only automatic sources, a standard online service, and the key questions are: did the data arrive, is the wall profile changing, who acknowledged the alarm, and is one vibration event complete. Then GIS and manual data entry may remain unused, and the focused Inclify process covers the stated scope.
The conclusion is not "buy the smaller one". It is: buy exactly the scope that has an owner and an use case. A function without a process is a cost of configuration, testing, training and updates.
What should be included in the acceptance scenario
A sales presentation shows the system in an ideal state. Acceptance should test the non-ideal state. Prepare ten scenarios.
- a correct frame with current time and a known value;
- one missing expected measurement;
- a longer transmission pause;
- a delayed measurement with the original time;
- a trial with the wrong unit or structure;
- crossing the warning and alarm levels;
- return below the threshold with hysteresis;
- a threshold change by an administrator;
- export of a selected period together with a gap;
- issuing data and configuration after pilot completion.
If the project requires manual measurements, add offline work, correction of an incorrect entry and approval by a second person. If it requires the client's infrastructure, add network loss, backup restore, version update and an expired certificate. If it requires vibration, add a complete and incomplete signal with a reference FFT result.
Each scenario has four fields: input, expected result, maximum time and evidence. "The alarm works" is not a criterion. "The state changes after evaluation of the data, SMS reaches the named person, acknowledgment records the user and time, and the audit shows the active threshold" is.
Comparison limits: when not to migrate
Do not migrate only because the new interface looks simpler. If Beyond Monitoring or another system already has hundreds of sources configured correctly, people know the procedures, reports go into the contract, and the maintenance cost is acceptable, the value of change must exceed the migration risk.
Do not migrate without issuing history and configuration either. Measurements without units, references, equations and threshold versions may look like a complete archive, but they do not allow the decision to be recreated. First make a trial export and reproduce one chart in an independent tool.
Do not try to replace an organisational problem with a platform. The absence of an on-call person, unapproved thresholds and an outdated TARP will not disappear after a logo change. The system can deliver a message, record acknowledgment and show evidence. It will not define responsibility in the contract. The response rules are described in the alarm response plan.
What Inclify looks like
An Inclify pilot starts from an existing automatic source. The team checks the sample frame, time, units, frequency and equations. If the recorder or concentrator can send HTTP/JSON, the sensors do not need to be replaced. The platform can also accept history through the same channel with original UTC times. It is not intended for importing files with manual series.
After connection, a dashboard is built for a specific decision, not for every available field. Thresholds work per channel, a separate alarm detects missing data, and users choose notification channels and the minimum state. Acknowledgment records the person and the time. Mute has a deadline. There is no automatic escalation after a lack of acknowledgment and no mobile push notifications.
The quality report shows real cadence, completeness, gaps and freshness. For a vertical inclinometer, the platform preserves geometry versions and calculates the profile from a fixed base. For vibration, it shows the time history, FFT and 21 third-octave bands. Engineering reports run in the panel; data can be issued as CSV, a chart as an image, and dynamic results as XLSX. There is no automatic PDF report.
Fit-and-gap checklist before the request for quotation
Copy this list into the request for quotation and mark each item as: required, desirable or out of scope.
- automatic sources and their protocols;
- manual instruments, validation and offline work;
- maps, GIS, photos and work progress;
- formulas, references and configuration versioning;
- threshold alarm, missing data, hysteresis and response procedure;
- SMS, e-mail, in-app notifications, mobile app and delivery requirements;
- contract report, format, schedule and signature;
- export of measurements, results, configuration and log;
- SaaS, on-premise, RTO, RPO and update responsibility;
- roles, tenant isolation and service access;
- measurement retention and short-term diagnostic data;
- migration method and system exit test.
Do not award points for a function that is "available after configuration" without estimating the configuration and maintenance effort. In a tailor-made system, that is a major part of the total cost of ownership. In SaaS, by contrast, you must honestly price the workarounds for functions outside the core.
FAQ
How does Beyond Monitoring differ from Inclify?
Beyond Monitoring is described by Sixense as a broad platform and web GIS that combines many formats, external sources, manual offline measurements, reports and SaaS and on-premise variants. Inclify focuses on automatic HTTP/JSON, stream quality, alarms with response history, chain inclinometers and dynamic analysis. The difference concerns scope, not only the interface.
Does Inclify support manual field measurements?
Not as a measurement series. The platform does not have an app for manual readings offline or import of series from CSV/XLSX. You can manage a device reference and project documents, but that is a different process. If manual campaigns are part of the source of truth, the requirement must be solved with another tool or with a platform that shows the full process in a pilot.
Does Beyond Monitoring work on-premise?
Yes, according to the official Sixense website, an on-premise variant is available for sensitive sites, alongside cloud SaaS. The label alone does not define operational responsibility. The offer must specify servers, updates, backups, monitoring, RTO/RPO, certificates and support access. Inclify does not currently offer on-premise as a standard catalogue variant.
Does Inclify have a mobile app for alarms?
Inclify has a responsive interface and in-app notifications through a private real-time channel, as well as e-mail and SMS. It does not have a native mobile push app or manual offline work. The user can set preferred channels and the minimum state, acknowledge an alarm and mute it until a specified date.
Which system is cheaper?
Public pages do not provide a fair basis for comparing the total cost of the same scope. You need to compare licence or subscription, configuration, integrations, hosting, manual processes, reports, support and maintenance over several years. First align the mandatory scope. A cheaper platform with an expensive workaround can have a higher total cost of ownership than a broader solution.
How do you compare systems without production migration?
Run a parallel pilot, for example on an illustrative sample of 10 to 30 automatic channels. Both systems should receive the same data and thresholds. Check correct reading, a gap, missing data, alarm, return with hysteresis, configuration change, export and data release. If manual entries, GIS or client infrastructure are required, add separate scenarios and required evidence.
Sources and further reading
- Sixense: Beyond Monitoring - official platform page - scope of sources, alarms, reports, offline app, SaaS and on-premise; accessed 30.08.2026.
- Sixense: Monitoring & Testing - context of engineering and monitoring services.
- ISO 18674-1:2015 - general principles of geotechnical monitoring.
- NIST SP 1800-32: security for industrial IoT systems - architecture and risks for device data.
- JRC/CIRIA: observational method - link between monitoring and actions.
- How to connect existing recorders to an online platform - technical conditions for a pilot without replacing sensors.
What next
If you have a request for quotation or a source list, send it for requirements compliance review. The Inclify team will state in writing what works as standard, what requires agreement, and what the platform does not support today.