Release Notes 2025
Introduction
Release 2025 is a major baseline, delivering major new functionality and rolling up a number of resolved issues.
New Functionality and Enhancements
Pitram Service Management Enhancements
New Installation and Upgrade Process
The installation process for the PITRAM Watchdog Service and the desktop application, Pitram Server Management Console, has undergone significant changes. In previous versions, these components were installed using the PitramServer.exe or DiagnosticTools.exe installers.
Starting with version 13, PitramServer.exe will no longer handle the installation or upgrade of the PITRAM Watchdog Service, as well as the Pitram Server Management Console. Instead, these applications will be automatically uninstalled during the upgrade process to version 13. It is important to highlight that the desktop application, Pitram Server Management Console, is no longer supported.
To streamline the installation process, a new installer, PitramManagement.exe, has been introduced. This new installer will manage the installation and upgrade of the PITRAM Watchdog Service, covering both master and agent services. It replaces the previous DiagnosticTools.exe installer, and along with the transition, the application has been renamed and the installation folder has been migrated.
For the new PITRAM Watchdog Service to function properly, it is essential that the .NET 8 hosting runtime is installed on the machine.
Pitram Services Management Web Console
A new web console, Pitram Services Management, has been implemented to replace the outdated desktop application, Pitram Server Management Console. The web console offers users enhanced flexibility, allowing access to the management tool from a web browser on any machine that can connect to the hosting server.
The web console application is hosted by the PITRAM Watchdog Service. Opening to http://<master-watchdog-address>:925 will load the Pitram Services Management home page showing a list of services that have been configured for monitoring.
Note: To use the Web Console on remote machines, make sure the communication port 925 is open on all servers hosting the watchdog master and watchdog agents.
In addition to overseeing and controlling the state of individual Pitram services, the web console offers essential insights into the performance metrics of the machines that host the watchdog master and agents. This includes vital information such as CPU specifications, available memory, disk space, OS version, and more. It ensures that users can effectively monitor system resources and maintain optimal functionality.
Retrieval of Artefacts
To simplify the collection of log files and configuration files for various Pitram server applications, the newly introduced Pitram Services Management web console offers users the convenience of downloading all relevant artefacts from a single location. Users have the flexibility to choose whether they want to download artefacts for a specific service or for all services simultaneously, enhancing the efficiency of the process. This improvement is designed to ensure that everyone can easily access the necessary files without any hassle.
Artefact Snapshots
In the event of an incident, the PITRAM Watchdog Service has the capability to seamlessly restart one or multiple Pitram services. This process typically occurs without any disruption to the users. Nonetheless, it remains crucial to thoroughly investigate the underlying cause of any issues that lead to automated recovery. Equally important is the need to back up all relevant artefacts from the time when the incident took place.
The latest version of Pitram Services Management introduces an automated feature that ensures all artefacts related to historical incidents are backed up efficiently. This enhancement aids in thorough investigations, preserving valuable data for analysis.
Navigation from Control Room to Pitram Services Management Console
In the event that any of the core Pitram services - namely ESS, GSS, RDS, or BMS - becomes disconnected, a warning sign will automatically appear in the footer bar adjacent to the Pitram services. This warning will include a hyperlink directing users to the Pitram Services Management web console. By clicking on this link, users will be taken to the web console, where they can easily check the current status of the Pitram services as well as potential reasons for any service interruptions.
This new feature is designed to reduce the number of outage calls regarding service failures that may occur due to site infrastructure issues, such as if the SQL server is down. Providing users with direct access to relevant information should enhance overall efficiency and streamline the troubleshooting process.
Custom Shift Duration
Traditionally, when a shift definition was created, it applied uniformly across all days of the week. However, a client has expressed the need for greater flexibility, requesting the ability to configure distinct shift definitions for different days. For instance, during weekdays, there will be three shifts, each lasting 8 hours, while on weekends, there will be two shifts, each spanning 12 hours.
In response to this request, a new functionality has been introduced in Pitram. This enhancement allows users to specify a shift definition for particular days, enabling the automated shift start feature to accurately determine which shift should be initiated. This development not only addresses the client's needs but also enhances the overall flexibility of shift management within the system.
Export and Import Data Acquisition Definitions
It is a common practice for users to utilise Data Acquisition across multiple machines, each operating with the same Canvas and Panel definitions. However, this can lead to the creation of distorted datasets, as there has previously been no way to synchronize Panel and Canvas definitions effectively.
Users can now export the definitions from one instance of Data Acquisition into a single compressed file. This file can then be easily imported into another instance of Data Acquisition, ensuring consistency and accuracy of profiles across all machines.
Automated Primary Status Change Configuration Changes
The configurations for various modules related to Automated Primary Status Change; such as GPS, measures, and accelerometer, were previously dispersed across two reference data groups: OperationalProfile and AutomatedIdleDetectionProfile. Additionally, the names of some attributes were not accurately conveying their intended meanings.
To resolve an identified issue with automated operating status change, the configuration for all modules has been consolidated into a single reference group, AutomatedIdleDetectionProfile. Furthermore, the related attributes now have more meaningful names, enhancing clarity and usability. This improvement aims to eliminate any undefined confusion regarding the configurations and their purposes, making it easier for everyone to understand and utilise the system effectively.
Bluetooth Positioning Enhancements
Filtering of Bluetooth Advertisements
In the previous version of the Bluetooth positioning system in Pitram, the performance could be compromised due to the processing of Bluetooth advertisement packets. A common issue arose when numerous Bluetooth devices transmitted advertisement packets, overwhelming receivers like Pitram Mobile with a high volume of data. Without an effective filtering mechanism in place, the Pitram mobile unit struggled to manage this influx efficiently.
In the latest version, we have introduced a robust filtering system that systematically eliminates irrelevant Bluetooth advertisement packets. This enhancement significantly boosts the overall performance of the positioning system, ensuring that the Pitram mobile unit can operate more efficiently.
Obtaining MAC Address
Pitram Positioning utilises MAC addresses to uniquely identify Pitram mobile devices engaged in Bluetooth communication with one another. This is particularly important in scenarios like "Dump to Truck," where loaders need to recognize a truck. In earlier versions, Pitram mobile units retrieved their MAC address from the Ethernet adapter using a hard-coded name, "Ethernet." If the adapter's name was changed - perhaps by the operating system after the installation of a new Ethernet adapter - the adapter named "Ethernet" might no longer be discoverable, preventing the retrieval of the MAC address.
Starting with version 13, this process has been enhanced. The MAC address is now obtained dynamically, eliminating reliance on the hard-coded name "Ethernet." The internal logic systematically inspects the network adapters in the following order: Wi-Fi adapter, Ethernet adapter, and then other network adapters, including virtual ones. This improvement ensures that the MAC address can be reliably obtained, even if the adapter names are modified.
Publishing of Contained Metal Consolidation
Historically, contained metal values have been published into the MEASURETIMESTAMP table. Starting from version 7, these values have also been recorded in the GradeControlProductGrade table. This enhancement has facilitated improved management of transaction scopes when storing contained metal records, ultimately leading to increased accuracy.
To accommodate a transition period for potential migration of reports and third-party integrations, Pitram has continued to support the storage of contained metal in both the MEASURETIMESTAMP and GradeControlProductGrade tables. However, this dual support has been adversely affecting system performance.
To enhance the performance of shift processing and improve the accuracy of reporting data, contained metal will now only be published into the GradeControlProductGrade table.
Note: Although not recommended, users still have the option to utilise a feature toggle to reactivate the legacy functionality that allows for the storage of contained metal in the MEASURETIMESTAMP table.
Service Domain User Account Security Mode
Recently, some sites utilising the Windows Account security mode for database access have reported a decline in performance within the Pitram Portal. This slowdown can often be attributed to excessive processing related to impersonation, a technique that allows code to execute under a different user context than the one who originally initiated the application. Clients typically opt for this security mode when a Windows domain account is necessary to access a database.
To address these performance issues, the newly introduced security mode, Service Domain Account, effectively eliminates the need for impersonation. With this mode, the Dome Connector operates under a Windows account designated for database access. This approach is particularly advantageous for sites that do not permit the creation of an SQL account - precluding the use of the SQL Account security mode - and require all applications to operate using a Windows account for database operations.
Overall, transitioning to the Service Domain Account security mode will enhance performance and simplify database access without the complications associated with impersonation.
Other Enhancements
Pitram Portal
| Issue | Description |
|---|---|
| DM-32949 | Change the misleading log type to "Information" from "Warning" |
| DM-32934 | Implement support for custom shift duration in BI Dashboards |
| DM-32923 | Implement support for custom shift duration in Activity Sheets |
| DM-32895 | Implement support for custom shift duration in Targets |
| DM-32894 | Review and Adjust period selector to support custom shift definitions |
| DM-32893 | Reference Data Editor - Add attribute to Shift definition reference group to select days of week |
| DM-32639 | Read comments from Material Management bulk survey imports |
| DM-31901 | Add location filter to Stockpile Surveys page in Materials Management |
| DM-32846 | Change Material Management location search function (Contains) |
| DM-32755 | Address Dome portal performance degradation |
| DM-26292 | Reload is required to load data for different elements within the same location or to load a different location within the same Period |
Reporting
| Issue | Description |
|---|---|
| DM-32974 | Plutonic End of Day report - fix header & footer |
| DM-32948 | AEO Sign Timeline report not displaying date of AEO sign changes, just updated time and reason |
| DM-32931 | Equipment Hours by Period report is showing more hours than expected |
| DM-32899 | Equipment Measures by Location - remove equipment column and subtotal |
| DM-32841 | Restore report to default to fix broken PLODs |
| DM-32823 | Personnel Hours (All Personnel) column adjustment |
| DM-32765 | Modify Stockpile Summary Report to include grade and Ctd Metal values for adjustments |
| DM-32746 | Shift Planner report to add Planned Start Date |
| DM-32627 | Report Adjustment: Equipment timeline with Operator |
| DM-32597 | Update Standard report Operator In Cab Validation Report to order by Equipment Description |
Pitram Control Room, Pitram Mobile, Pitram Servers
| Issue | Description |
|---|---|
| PR-34834 | Implement support for custom shift duration in Shift Comments |
| PR-34833 | Review and adjust Pitram Connect and PRIS calls returning shift definitions to support custom shift duration |
| PR-34832 | Implement support for custom shift duration in Shift Planner |
| PR-34831 | Implement support for custom shift duration in BMS |
| PR-34724 | Mobile units not connecting to services while in WIFI range |
| PR-34734 | Enable the ability to add additional Comments Category for the Comments feature in DA |
| PR-34730 | Warning message when character limit exceeded for Comments |
| PR-34729 | Order Comments Category in the UI Alphabetically |
| PR-34682 | Enhancement Request - Pitram Connect - Equipment View |
| PR-33993 | Pitram Connect - Add Location status timeline on Location details View |
| PR-33055 | Create Canvas and Panel Repository |
Issues Resolved
Pitram Portal
| Issue | Description |
|---|---|
| DM-32927 | Ref Data publishing failure and performance issues |
| DM-33030 | Issue with import in v12 |
| DM-32963 | Issue with the new reference data import |
| DM-32961 | Unable to import reference data |
| DM-32853 | Pitram portal - Subquery returned more than 1 value for a snapshot data window in Materials Management |
| DM-32852 | Pitram Portal Performance Issues |
| DM-32794 | Indonesian translations for reference group names causing "Deploy Reference Data" to fail |
| DM-33007 | Pitram Portal lost license |
| DM-32957 | Location Import - Invalid group name: Sublocation |
| DM-32929 | Missing measures (Truck Dump) requiring manual shift processing |
| DM-32928 | Pitram Portal - Surveying - Hauling Distance - unable to make edits when a browser is in Russian |
| DM-32913 | Issues with Operator Qualifications dropping |
| DM-32912 | Reference Data import fails when Portal is in non-English language |
| DM-32911 | Scheduled jobs fail extraction which contain Mine Level Description |
| DM-32867 | Pitram Portal (DOME) performance issue |
| DM-32847 | Material Management - Stocks screen location selector - an incorrect behaviour when you press Enter |
| DM-32808 | Material Movements Read only permission bug |
| DM-32793 | Issue with NCF state table |
| DM-32761 | Stocks in Material Management Crashes |
| DM-32748 | Targets Module crashes when Auto Log out time elapsed |
| DM-32740 | Material Management Loads Movements but Excel Export Blank |
| DM-32738 | Unexpected Error when exporting from Data Browser |
| DM-31444 | Stock Management Auto Load when switching element |
| DM-24980 | Warning Message: Exception occurred while trying to hide sections of a report |
| DM-32968 | Change of wording on Waypoint Action Definition |
Reporting
| Issue | Description |
|---|---|
| DM-33048 | SMU by Period preview error |
| DM-32988 | "Mean Time Between Failures" report didn't working some shift |
| DM-32803 | SMU Readings (Elapsed) To Date column using the wrong format |
| DM-32786 | Truck Cycles by Loader - Equipment filter bug |
| DM-32773 | MTBF truncate fetch error |
| DM-32973 | Equipment Measures by Period - Location report returning no data returned message despite the report returning data |
Pitram Control Room, Pitram Mobile, Pitram Servers
| Issue | Description |
|---|---|
| PR-34341 | Mobile is closing within 40-50 seconds after updating to version 11.0 |
| PR-34841 | Duplication of Location Status in DA |
| PR-34794 | DA: use "Contains" search option not working |
| PR-34722 | Pitram Mobile - Shortcut Measure Error - Configuration is invalid |
| PR-35015 | Data not flowing through within the Automatic shift processing window |
| PR-34940 | Missing measures from Reporting Database after shift end |
| PR-34922 | ESS failed to handle missing DB connection |
| PR-34902 | Error during ICV Submission |
| PR-34898 | IP Addresses disappearing in Mobile Health Panel |
| PR-34878 | Location Status Panel not displaying Current Location Status |
| PR-34860 | Measures tab taking a while to open window in DA |
| PR-34850 | Translate the dispatcher's decisions into Russian |
| PR-34829 | Issue with Operator Allocations (rollover case) |
| PR-34824 | Issue with Rollover status events in Allocation Time Stamp table |
| PR-34797 | Operator Qualification Violation Report showing violations when allocation event has been removed |
| PR-34699 | Incorrect Source Location of Movement Recorded |
| PR-34406 | Issue with Automated Operating Status Change |