Field Service Intelligence - Release 9.41

Release Date: May 2026

We have been enhancing Field Service Intelligence since the last release, adding new features and addressing known issues to improve quality.

Some features may require additional setup by Totalmobile. If needed, reach out to your Account Manager for access details.

These Release Notes cover the following:

What's New

  • Laminar Data Migration – Expanded Customer Rollout

    Enhancement have been made to the Laminar ingestion framework, extending it to additional customer environments.

    A significant number of additional customer environments have been migrated to the Laminar data ingestion framework. Migrations cover the full range of supported environment types — including Job Management (Connect), the Mobile Working (Mobilise) databases Datamart and Totalmobile, Referral Management (Carelink), and Dynamic Scheduling (Optimise) — as applicable per deployment. Further Laminar environment provisioning was also completed to support new customer on-boarding.

    This means a broader customer base is now on the modern, reliable Laminar framework, delivering improved ingestion consistency, near-real-time data sharing, and reduced maintenance overhead across those environments.

  • Operational Monitoring Dashboards

    New monitoring dashboards have been added to surface Laminar platform and pipeline performance data.

    A suite of Azure and Databricks dashboards have been created to provide real-time visibility into Laminar pipeline health and ingestion status. A baseline Insight dashboard surfaces key operational metrics, and an internal end-to-end timeliness metric has been introduced to track the time from a field event (button press) through to data availability in Databricks. Spike investigations confirmed the feasibility and measurement approach for this latency monitoring.

    This means teams gain proactive visibility into platform performance, enabling faster identification and resolution of pipeline issues before they impact customers.

  • Care Reports – Expanded Deployment & Versioning

    Enhancements have been made to Care Report deployment coverage and version management.

    Care Reports have been deployed to additional production environments and a consistent versioning approach has been introduced to improve change management and traceability across deployments. Semantic model refresh timings have been updated for Referral Management (Carelink) reports.

    This means Care Reports are now available to a wider set of customers, with a standardised versioning structure which improves deployment confidence and makes it easier to manage report changes across environments.

  • AI & Data Science – Predictive Capabilities

    New predictive modelling capability has been developed for Visit Duration and No-Access forecasting.

    An initial No-Access (NA) prediction pipeline has been developed for Visit data creation, with AM/PM variation analysis and data quality review completed. Visit Duration prediction models have been built including feature engineering and a feasibility study assessing production readiness.

    This means foundational AI prediction capabilities are now in place for Visit Duration and No-Access forecasting, moving the platform towards proactive field service decision support.

  • Platform & Infrastructure Improvements

    Enhancements have been made to data pipeline processing, component configuration, and environment provisioning.

    Silver batch processing steps have been reordered to improve pipeline execution efficiency, and shift is_excluded logic has been moved to the silver layer for cleaner data modelling. A Hide Text switch has been added to the Gen 2 table column component, providing more flexible report configuration. The MIN_IDLE_GAP_SECONDS value has been updated to 60 seconds to improve non-productive activity detection accuracy. The latest semantic model and Insight Reports have been deployed to all Insight tenants, and new development tenants have been provisioned to support ongoing internal testing.

    This improves pipeline reliability and processing efficiency, provides more accurate non-productive calculations, and greater flexibility in how report components are configured.

Fixes

Ref

Description

IPA-2568, IPA-2684, IPA-2685, IPA-2686, IPA-2687, IPA-2689, IPA-2690

An issue has been fixed with the Velocity Report across all components: Overview, Hour, Day, Worker, Table, Tile Card, and DOTs visual, where calculation errors were affecting all Velocity Report components. This has been resolved, and all Velocity metrics now return accurate aggregated values across customer environments.

IPA-1430, IPA-1455

An issue has been fixed with the League Table in Gen 3 environments, where the League Table KPI values were exceeding 100 in certain calculations. A cap has been applied so values cannot exceed the correct maximum, preventing misleading efficiency figures from appearing in the table.

IPA-1720

An issue has been fixed where there were calculation errors in the EPI Activity Table across all environments. These have been corrected, ensuring accurate values are displayed for activity-level metrics across all supported environments.

IPA-2835

An issue has been fixed with the Productivity Day top chart in Power BI, where it was not factoring in non-productive data when calculating productivity figures. This has been corrected so the chart reflects a complete and accurate view of worker productivity including non-productive periods.

IPA-2875, IPA-2917

An issue has been fixed with the FSI License Count Report and the Service User Breaks Report, where incorrect values were being displayed. Both reports have been corrected to surface accurate data.

IPA-810, IPA-2776, IPA-2807

An issue has been fixed with the Geofence Accuracy (comp1) calculations in Gen 2 environments, where it was always returning null in affected Gen 2 environments due to a calculation error. The root cause has been investigated and resolved. Separately, Geofence Accuracy was calculating correctly on Insight Hub but not appearing on the League Table in Gen 2 — this has also been corrected. In environments where the geofence calculation was always generating 0 or null, the underlying issue has been addressed.

IPA-1527

An issue has been fixed across all environments to worker name display, where in certain configurations, workers were being displayed using their system username rather than their display name. Where the username is a number or non-descriptive identifier this caused confusion in reports. Worker names now display correctly across all environments.

IPA-2598, IPA-2733

An issue has been fixed with the Shift workflow bubbles, where Completed Shifts were incorrectly appearing in the Working bubbles view, and the Shift workflow bubbles were not showing the correct shift state data. Both issues have been resolved so that bubbles accurately reflect current Shift status.

IPA-2808

An issue has been fixed where migration errors were affecting address data across multiple customer environments had been identified and have now been resolved.

IPA-2887

An issue has been fixed where closed tasks without a task_start_datetime value were not being handled correctly in OPI, causing data gaps in task-level reporting. These are now processed correctly.

IPA-1459

An issue has been fixed with the Task and Visit location pins on the map not being plotted accurately, following the Job Management (Connect) lat/long integration. Pin positions now correctly reflect the location data provided through the integration.

IPA-2839

An issue has been fixed with the Laminar Scheduler where large tables were hitting the Databricks query cap during Laminar Scheduler runs, causing processing failures. The scheduler has been updated to handle large tables correctly without exceeding query limits.

IPA-2849

An issue has been fixed with the FSI Web App organisation table where data was not being uploaded in tenants where the Databricks environment name and the frontend environment name were mismatched. This has been resolved so uploads complete successfully regardless of naming alignment between the two.