Release Notes 2026
Introduction
Release 2026 is a major baseline, delivering major new functionality and rolling up a number of resolved issues.
New Functionality and Enhancements
Asset Health via VIMS Integration
The VIMS integration is designed to automatically collect and process asset health data from the VIMS (Vital Information Management System) installed on CAT mining equipment; feeding this information directly into Pitram’s asset health module. Signals from VIMS; such as engine hours, temperatures, and other diagnostic parameters, are mapped to Pitram asset health readings.
Data is sampled at configurable intervals, with system-enforced minimums to protect both performance and data quality. Asset health readings are stored in a time series database and can trigger Pitram events based on predefined thresholds or conditions.
Each equipment model and VIMS specification version can have its own profile, ensuring that the correct parameters are captured and interpreted for asset health monitoring. The system is designed to adapt to new VIMS specification versions without requiring code changes. This approach ensures robust, maintainable, and scalable integration of VIMS data into Pitram for improved equipment monitoring and operational insights.
Volvo J1939 Integration
Volvo integration enables Pitram Mobile to collect and process operational data directly from Volvo trucks via the CAN bus, supporting key measures such as engine hours, fuel level, and payload. Data from the truck’s J1939 signals is decoded and mapped to Pitram measures using a dedicated Volvo profile and integration mapping. This process ensures that asset health readings are accurately captured and Pitram events (like engine hours, fuel changes, and payload dumps) are sent to Pitram servers for further processing and reporting. The system uses smoothing algorithms for fluctuating signals (such as fuel level) and configurable logic for event triggers, ensuring reliable and consistent data capture across different truck models and site conditions.
For payload management, the integration captures payload values at specific operational moments - such as when the truck’s body-down signal transitions, and when the load cycle changes from loaded to unloaded. Auxiliary signals (like gear lever and load cycle state) are also collected to support accurate event generation. The architecture is designed to accommodate multiple Volvo truck models and evolving DBC (database) files, allowing for flexible adaptation as new versions or site requirements emerge. This integration streamlines data flow from the truck to Pitram, supporting efficient fleet management and operational analysis for end users.
Komatsu KOMTRAX J1939 Integration
Komatsu integration is designed as a direct replacement for sites currently using the SKZ integration. Like SKZ, it collects operational data from the truck’s CAN bus and generates the same set of Pitram events - such as fuel level, payload, engine hours, odometer readings, and cycle states (loading, hauling, traveling empty). This ensures a seamless transition for existing sites, with all key metrics and event logic preserved, while leveraging a dedicated Komatsu hardware profile and updated integration mapping for improved flexibility and maintainability.
For users, this means that the Komatsu integration will feel familiar, providing the same automated capture and reporting of truck metrics as SKZ, but with enhanced support for different Komatsu models and future updates. The system continues to use smoothing algorithms to handle fluctuating values (such as fuel level) and supports flexible configuration to accommodate different truck models and evolving DBC file versions.
Loadrite J1939 Integration
Loadrite integration enables Pitram to collect payload data directly from Loadrite weighing systems using the J1939 CAN bus interface; replacing the legacy integration that relied on a COM port connection. This approach allows Pitram to receive weighing events, such as bucket weights added by the operator, through broadcast CAN messages which are then decoded and mapped to Pitram events using the existing Loadrite hardware profile and integration mapping. The integration is designed to be scalable and supports multiple Loadrite models and DBC file versions, ensuring compatibility with future hardware updates.
For users, this means that payload data is captured automatically and reliably, with each weighing event (e.g., when the operator presses the Add button) generating a corresponding Pitram event.
Tracking Carry Back in Transcale and Loadscan Integrations
The updated Transcale and Loadscan integrations now support direct tracking and adjustment of payload readings using actual measured carry back values, eliminating the previous reliance on manual average-based adjustments. Both connectors have been enhanced to identify and process carry back events, with new configuration options (the SendCarrybackAdjustment flag) enabling the system to send and handle payload readings specifically marked as carry back. When a carry back reading is detected, the system automatically generates an adjusted payload by subtracting the carry back value from the previous payload - ensuring the adjustment only occurs when a valid previous payload exists and the result is not negative.
PRIS API and data model changes support this functionality, introducing a GenerateCarrybackAdjustment property to the relevant measure model. When enabled, the backend locates the previous payload event, applies the carry back adjustment, and generates a new event with the correct timestamp. This enhancement provides more accurate payload data, removes the need for manual or average-based corrections, and improves reporting and operational insights for sites using Transcale and Loadscan integrations.
Deviation Tracking Enhancements
Two new deviation tracking types have been included in Pitram15.0:
-
Cycle Status Too Long - Monitors configured equipment and raises a deviation notification if any equipment remains in a specified cycle status (such as Hauling) longer than the configured threshold.
-
Location Status Too Long - Monitors the status of configured locations within a defined location classification and raises a deviation notification if a location remains in a specified status (such as Marked) longer than the configured threshold.
Polygonal Waypoints
Pitram now supports defining waypoints as complex polygons in addition to traditional circles. This enhancement enables users to accurately represent irregularly shaped operational zones or areas within a mine site. Users can configure polygonal waypoints by specifying multiple border points (vertices), with the system storing these as the BorderPoints attribute.
All standard waypoint functionalities; such as triggering rules, logging equipment entry/exit, and status updates, now work seamlessly with polygonal waypoints. Rules are triggered when equipment enters the defined polygonal area. Polygonal waypoints can be imported from Micromine Origin and Beyond or third-party software and the system uses optimised algorithms for fast detection and processing of equipment within these areas.
TONKM Calculation Based on GPS Distance
The new functionality enables automatic calculation and reporting of both horizontal and vertical Tonne-Kilometre (TONKM) values for material movements using GPS data. The system now computes two measures: horizontal TONKM, based on the distance travelled, and vertical TONKMV, based on elevation changes. These calculations occur when equipment is in the hauling state. The results are stored in the Pitram reporting database and used to generate reports on average transportation distance and elevation lift using mass-weighted formulas.
UI Enhancements
Location Change Display in Pitram Mobile
Previously, when a loader operator changed the location of a truck in Pitram Mobile, the new location was immediately displayed on the truck - even if the truck was still in the Hauling cycle and had not reached the dump point. This often led to confusion for truck operators, as their displayed location would update before the hauling cycle was complete. The enhancement now ensures that the location for the truck is only updated after the operator presses the Dump button, completing the hauling cycle. Any notifications about a location change are also delayed if the equipment is in the Hauling or Queue at Dump cycle states, only appearing after the dump is finalised.
Additionally, a new configuration attribute, DisplayParentAllocationNotifications, has been added to the Operational Profile. When enabled (alongside DisplayAllocationNotification), this attribute displays a notification when the parent allocation changes, providing clearer guidance to operators.
Separate Source from Assigned Location in Pitram Mobile
The new enhancement streamlines how equipment sources and allocations are displayed and managed in the mobile interface, reducing confusion for users. For new installations, updated widgets are automatically configured, while existing sites require manual updates to widget and action types to align with the new standards.
This update clearly distinguishes between the Source location and the Assigned Location. It also allows separation of Assigned Location (always a location) and Allocation (which can be equipment or a location).
Source Location Change Display in Pitram Mobile
Previously, when a loader operator changed a loader’s source location in Pitram Mobile, the new source location was immediately displayed on the truck - even if the truck was still in the Hauling cycle and had not reached the dump point. This often led to confusion for truck operators, as their displayed source location would update before the hauling cycle was complete. The enhancement now ensures that the truck’s source location is only updated after the operator presses the Dump button, completing the hauling cycle. Any notifications about a location change are also delayed if the equipment is in the Hauling or Queue at Dump cycle states, only appearing after the dump is finalised.
Additionally, a new configuration attribute, DisplayParentAllocationNotifications, has been added to the Operational Profile. When enabled (alongside DisplayAllocationNotification), this attribute displays a notification when the parent allocation changes, providing clearer guidance to operators.
Flexible Source Location Override by Operator
For installations with Pitram Vision and Positioning, Pitram Mobile now allows operators to manually override the automatically detected source location, with configurable persistence of the override. This addresses issues with missing or faulty beacons and gives operators more control over data accuracy in material movement tracking.
Columns Ordering in Materials Management
The Movements grid column order is now configurable via a database setting, allowing specific clients to customize the order of key columns (such as placing Material next to Source) without requiring code changes. No UI is provided for this; it is a back end configuration.
Option to Enable/Disable Stockpile Viewer Alarm
A new configuration option allows users to enable or disable the visual alarm in the Stockpile Viewer, providing greater flexibility while maintaining Min/Max value visibility.
Change Material Type in Pitram Connect
Pitram Connect now allows users, primarily Geologists, to change the material type of a location directly from the application, enabling real-time updates in the field. This eliminates the need to wait until the end of a shift to make changes on a desktop system, improving responsiveness and operational accuracy. The current material type is displayed on the main location card, with an option labelled Set material for quick edits. Users can select the new material along with the date and time of the change, provided they have Location write permissions.
Equipment Summary by Mine Region in Pitram Connect
Pitram Connect now lets users filter equipment summaries by Mine Region; addressing the needs of sites operating across multiple regions. A region selector is available via a dropdown on Tablet/Windows and through the hamburger menu on phones. By default, no filter is applied (All Mine Regions). When a region is selected, equipment cards show only activity that occurred while the equipment was in that region, and totals (e.g., tonnes moved) reflect region‑specific activity. Equipment currently outside the selected region still appears but is visually highlighted, and users can optionally hide equipment not presently in the chosen region. The equipment details pop up always shows the current state for the equipment, independent of the region filter.
Pitram Service Management Enhancements
Watchdog Service Recovery After Server Restart
Previously, the PITRAM Watchdog service did not reliably restart after a server reboot because its startup mode was set to Automatic instead of Automatic (Delayed Start). This caused contention during system startup and prevented the service from starting as expected. The enhancement now sets the Watchdog service to Automatic (Delayed Start) by default; reducing startup conflicts and ensuring reliable recovery. The installer applies this setting automatically, but manual verification is recommended during upgrades from older versions.
To further improve resilience, a scheduled task named PitramCheckAndStartWatchdog is created when PITRAM Management Tools are installed. This task runs five minutes after system startup and attempts to start the Watchdog service if it is not running, retrying up to 10 times at 30-second intervals. The task can be disabled if needed, and upgrades will re-enable it if previously turned off. These changes ensure the Watchdog service recovers consistently after server restarts, minimising downtime and reducing the need for manual intervention.
Other Enhancements
Pitram Portal
| Issue | Description |
|---|---|
| DM-33544 | GPS calculated distance TKM and TKMV report |
| DM-33441 | Changing Pitram Support Inbound Address |
| DM-33400 | Materials Management table columns - change header location |
| DM-33376 | PLS - handle the licence update |
| DM-33241 | Cancelling long running reports |
| DM-33181 | Option to disable stockpile alarms |
| DM-31900 | Show fired location in Grades/Stockpile Surveys pages in Materials Management |
| DM-33312 | Material Movements with Original Source |
Reporting
| Issue | Description |
|---|---|
| DM-33523 | SVR Ground Support |
| DM-33396 | Adding Shift Column in The Equipment Timeline Report |
| DM-33361 | Expand Repair States Report to add location and comments |
| DM-33295 | Material Movements by Material Type remove equipment filter |
| DM-33269 | Modify Adhoc Report to include sort by Source, Destination and Measure |
| DM-33448 | Extend Source and Destination columns to fit description in Equipment Period Location Destination report |
| DM-33407 | Revert Equipment Measures by Location report back to old format |
| DM-33194 | Standard Report Update - Current Sign Register |
Pitram Control Room, Pitram Mobile, Pitram Servers
| Issue | Description |
|---|---|
| PR-35837 | Modify the logic to solve "CodeMeasure" is not a Movement Measurement issue in PRIS |
| PR-35997 | Add Volvo DBC file to repository |
| PR-35963 | Waypoint criteria - Current waypoint duration |
| PR-35815 | BMSync null exception |
| PR-35803 | Pitram Vision - Flexibility of source location override by operator |
| PR-35782 | Register the User Name from Pitram Connect to the EE |
| PR-35695 | Create new Deviation Categories\Action |
| PR-35595 | VIMS Integration - Extend Equipment Health Service |
| PR-35594 | VIMS Integration - Implement Mobile HW for VIMS |
| PR-35322 | Assigning Mobile Unit to another unit |
| PR-35315 | Event Editor - EventTime windows position with multiple display problem |
| PR-35173 | Event Editor - Loading historic shift with large reference data set can take too long |
| PR-35164 | Calculate distance by GPS |
| PR-33109 | Improved the search algorithm in DA and EE |
| PR-35312 | Enhancement Request - Tracking Carryback using the Transcale and Loadscan Connectors |
| PR-30926 | Add Mine Region option to Pitram Connect |
| PR-35597 | BM - Dump Location contour (waypoint complex polygon) |
| PR-35266 | Truck Location Change |
Pitram Connect
| Issue | Description |
|---|---|
| PR-33935 | Add Set material capability for locations |
| PR-35809 | Virtualise the log file viewer (make more efficient for large files) |
| PR-30926 | Add Mine Region option to Pitram Connect (Requires PITRAM/PRIS >=v15) |
| PR-36061 | Add Operator Name to equipment card |
| PR-36165 | Add equipment to location allocation |
| PR-35966 | Complete project and library updates/overhaul for iOS and Android. Better support for Android >= v15 Edge to Edge. |
Issues Resolved
Pitram Portal
| Issue | Description |
|---|---|
| DM-33601 | Shift Processing - Unable to perform initial sync on Dome Connector start up |
| DM-33514 | Reference Data Publish Error: "Object reference not set to an instance of an object" |
| DM-33452 | Unable to lock a shift |
| DM-33442 | Possible Bug - Reporting |
| DM-33425 | Material Management - Reconciliation - missing tonnes reconciled values for some movements after publish |
| DM-33362 | Syntax Error when Deploying Views with special characters in database name. |
| DM-32996 | Incorrect grades in Stock Management (LIFO location) |
| DM-33404 | Reference Data | Incorrect translation to Spanish | Dilution Method |
Reporting
| Issue | Description |
|---|---|
| DM-33563 | Equipment Timeline Report date format in US |
| DM-33393 | Operators Exceeding Status Specified Time Limit Filtering and Summary Based on Period |
| DM-33390 | Operator Timeline Report Filtering and Decimal Places |
| DM-33248 | Movements Summary Report not returning data / not showing intermediate stockpiles |
Pitram Control Room, Pitram Mobile, Pitram Servers
| Issue | Description |
|---|---|
| PR-35863 | Checklist does not update when Pitram Mobile is in Multi-Equipment mode |
| PR-36065 | Operator not deallocating when assigned to a Location |
| PR-35916 | Controlled areas - DA Signs disappearing |
| PR-35768 | No Operator displayed in Grid View in Location Activity Panels in DA |
| PR-35761 | Unable to Calibrate Measures in DA |
| PR-35603 | DA Crashes after setting up Location Activity Panel and Switching to Grid View |
| PR-36057 | Pitram Vision - Display Measure is incorrect in the Equipment control |
| PR-35996 | Unable to apply Location Measures against Profiles in DA |
| PR-35993 | Root Cause Analysis - Watchdog did not recover after server restart |
| PR-35971 | Pitram Mobile | Shift Tonnes System Query not updating in second shift roster |
| PR-35968 | GetLocationAllocation performance issue |
| PR-35959 | Bluetooth service restart causes multiple subscriptions to the same events |
| PR-35948 | BLE - Loader populated mac-equipment list with one wrong equipment code |
| PR-35947 | BMS Disconnect issue |
| PR-35936 | BLE - Equipment published wrong Mac address |
| PR-35913 | PRIS - Add suggested response reset with the hope this will fix the corrupt response data when logging set to debug level |
| PR-35904 | IP Addresses disappearing in Mobile Health Panel |
| PR-35094 | AdHoc Service hosted network is stopped and not recovered |
| PR-35891 | DA overrides the shift task status received from Mobile |
| PR-35890 | Truck movements not showing in Materials Management |
| PR-35840 | BMS stops responding / freezes |
| PR-35831 | Bad control character in string literal in JSON - Error in Pitram Connect |
| PR-35813 | BMS overload |
| PR-35808 | Highlighted search function removed when searching for Equipment, Location, and People on a Token |
| PR-35778 | Use "Contains" Search inconsistent in DA/EE |
| PR-35769 | Enter Measures Profiles Column Chooser preferences not saving |
| PR-35765 | Data Acquisition Location activity grid is empty and showing codes, not descriptions, for display measures |
| PR-35736 | Peer To Peer not forwarding all events from Loader |
| PR-35677 | Event Editor - Hangs on opening shift if there is no permissions to access configuration |
| PR-35600 | Signs showing as Open in Reporting Database |
| PR-35335 | System flagging operator as unqualified |
| PR-35278 | Pitram Mobile Task Status change Error |
| PR-34814 | Backspacing when adding/editing event location deletes all text |
| PR-28414 | Some personnel show as not deallocated in reports |
Pitram Connect
| Issue | Description |
|---|---|
| PR-35698 | Shift planner should scroll to current shift when switching rosters |
| PR-35751 | Sort the list of attributes in attributes selection list |
| PR-35795 | Add material to the location view search filter |
| PR-35799 | Equipment performance OID charts updates (filter out non OID, show current primary status as opposed to current status group) |
| PR-35800 | On equipment view cards, put primary status as first row |
| PR-35831 | Bad control character in string literal in JSON - Error in Pitram Connect |
| PR-36188 | (Android only) Add observation button not responding on Android tablet |
| PR-36152 | Found that if a Shift plan task fails from some other reason than a server validation, it is not retried |
| PR-36188 | Add observation button not responding on Android tablet (Android only) |
| PR-36217 | Pitram Connect inputs no longer raise when keyboard is invoked (Android only) |
| PR-36154 | Selected time font color had bad contrast on Windows and Android (N/A to iOS) |
| PR-36345 | Issues with Windows version connecting to a localhost PRIS on some machines (Windows only) |
Service Pack 1
Bug Fixes & Improvements
| Issue | Description |
|---|---|
| Pitram Portal | |
| DM-33710 | Pitram Services Management: Dome Connector Tracing |
| DM-33694 | DomeAnalysisService.XMLA CalendarEndDATE expiry for OLAP cube |
| DM-33666 | Dome Report - Truck Cycles by Loader report is getting session expired error |
| DM-33598 | Reference Data Templates - Issue if space included |
| DM-33721 | V_Timeline output of Duration is incorrect |
| DM-33715 | SMU Readings Standard Report is not working |
| DM-33708 | 854 Movement Summary Report error when selecting Destination |
| DM-33706 | Stockpile Summary Report with incorrect percentages for Elements |
| DM-33685 | Truck Cycles Report Not returning data |
| DM-33678 | Some train data captured in activity sheets appear with no date/time and incorrect values in Train Activity Reports |
| DM-33665 | Report for Truck Cycles Duration not reflecting correct payload tonnages |
| DM-33597 | 854 The report shows each cycle of the equipment overlapping |
| Pitram Control Room, Pitram Mobile, Pitram Servers | |
| PR-36308 | Set event source to Mobile Menu when event generated with Operator Override |
| PR-36182 | EE Freezing when edits are done |
| PR-36292 | All the events in event editor have an error code |
| PR-36249 | After Upgrade to 14.3 RDS and BMS are unable to start |
| PR-36243 | Event Editor - Primary Status and Measures not in alphabetical order when editing events |
| PR-36132 | Trucks occasionally not going into certain truck cycle states when leaving excavator Loading/Hauling/Queuing radius |
| PR-36092 | Token icon pop up window issue |