Release Notes 2025.5
Introduction
Release 2025.5 is a major baseline, delivering major new functionality and rolling up a number of resolved issues.
New Functionality and Enhancements
Shotcrete Movements
Shotcrete is a process used in underground mining to apply concrete or mortar onto surfaces, such as rock walls, for stabilisation and support.
In version 14.0, Pitram has introduced new functionality that supports the tracking and reporting of shotcrete movements from a Batch Plant to sprayed locations. The feature has been implemented in Data Acquisition (Shotcrete Panel) and Event Editor (Shotcrete View) and includes several key components:
-
Shotcrete manufactured in discrete batches can be labelled by a Batch Number.
-
An operator can record measures at the time of loading the mixing equipment (mixer).
-
A slump test can be carried out and recorded for each load of shotcrete.
-
Additives can be added to each load at the batch plant or mixer.
-
A mixer loaded at a batch plant can transfer shotcrete to other mixers or spraying equipment (sprayers).
-
A sprayer can be attached to a mixer where the mixer load is transferred to a sprayer during spraying. The sprayer is using an assigned location as the destination where shotcrete is sprayed.
-
A mixer load can be partially discharged to a sprayer at one location and partially discharged to a sprayer at another location.
-
Unused shotcrete can be discharged at a waste location.
The events related to shotcrete are processed by shift processing and stored in the reporting database.
Pitram Service Management Enhancements
Retrieval of Artefacts From Clients
In addition to the ability to download artefacts for the Pitram services implemented in the previous version, users can now conveniently collect these artefacts from various client applications, including Data Acquisition, Event Editor, and Pitram Mobile.
A new feature, the Client Requests screen, has been added to the Pitram Services Management web console. This screen displays a list of machines running Pitram client applications. For any selected machine, users can submit a request to transfer artefacts from all Pitram client applications operating on that machine. The artefacts available for transfer include logs, configuration files, the client database, and a snapshot of the Business Model. Once the request is processed, users can easily download the artefacts directly from their browser to their local machine.
Pitram Clients Version
Users can now easily access a comprehensive list of the deployed Pitram applications. This view provides essential information, including the IP address of the machine hosting each application, the current connection status, and the version of the Pitram applications in use. If the version of a client application differs from that of the Pitram server services, it will be highlighted.
SQL Server Health Check
It is now possible to effectively collect parameters related to the SQL Server service and monitor the health of Pitram databases deployed on the SQL server. This enhanced feature provides valuable insights into database disk usage, SQL system configuration parameters, maintenance plans, active connections, and the fragmentation of indexes utilised in Pitram databases. Additionally, to gain a clearer understanding of user engagement with Pitram, users can request a total count of recorded events.
Recovery History View
The Pitram Watchdog Service maintains an SQLite database that logs the activities of Pitram services along with their current status at any given moment. This functionality facilitates the monitoring of service performance and enables auditing of the recovery history for Pitram services. The recovery process is automated and designed to minimise system outages caused by service unavailability.
In the latest update, users can conveniently access the recovery history through a newly introduced web console screen called Watchdog Activity. This feature is available for every monitored Pitram service, providing a compact and clear view of recorded failure incidents alongside the subsequent recoveries of the services. Newly detected recoveries are highlighted with a warning ball sign displayed next to the affected service on the main services screen. Users have the option to acknowledge these warnings, which allows them to hide the notifications.
Health Summary View
The health check of Pitram functionality can generate warnings that provide valuable insights into system performance. These warnings can be explored in detail by navigating to the individual service screens. In addition to this detailed view, a new Health Summary screen consolidates all warnings into one convenient location. This screen highlights all warnings and offers a high-level overview of system recoveries and any discrepancies in the versions of the installed applications.
Reference Data Editor Enhancements
Audit History of Reference Data Updates
In Pitram 14.0, users have the capability to view the history of modifications made to reference data. This feature presents a detailed list of reference groups, tokens, and attribute values that have been added, edited, or deleted within a specified period. For records that have been edited, the display includes the new value, along with an option to request the original value for comparison purposes. Additionally, each modified record is accompanied by essential information such as the published version, the timestamp of the modification, the username who performed publishing, and the machine name utilised for publishing.
Ordering of Reference Data Attributes
Previously, reference data attributes within the reference data tree and the edit form were not organised in any particular order. In the new version, the attributes are now sorted in alphabetical ascending order by default, with required attributes displayed at the top for easier access. Additionally, the edit form has been enhanced to allow users the flexibility to apply a custom ordering of attributes, providing a more tailored experience.
Shift Reprocessing History
It is a common practice for Pitram users to review the history of previously executed shift reprocessings. To streamline this activity, the Pitram Service module in the Pitram Portal has been enhanced to include a comprehensive history of shift reprocessing. This feature offers users detailed insights, including the start and end times of each execution, the total duration, the username associated with the reprocessing, and the specific reference data version utilised.
Other Enhancements
Pitram Portal
Issue | Description |
---|---|
DM-33264 | Materials Management - Implement Read Access for Stockpile Viewer |
DM-33215 | Pitram Portal - Web Service Applications cache corrected |
DM-32902 | Investigate slow performance of Drill and Blast |
DM-32324 | Data Dumps flagging |
DM-33278 | DA - Deviation Tracking pop up |
DM-33111 | Refuge Chamber Report |
DM-32830 | Add Shift Reprocess history |
DM-32677 | Able to audit changes made in Reference Data Groups |
DM-32087 | Ability to order attributes of a reference data in Reference Edit |
Reporting
Issue | Description |
---|---|
DM-33351 | Contained Metals Report for V13 |
DM-33379 | Daily report V2 |
DM-33175 | Equipment Hours by Period/location showing all measures |
DM-33173 | Removing equipment from daily reports |
DM-33098 | Daily report showing correct values vs stock summaries |
DM-33084 | Daily Rehandled Ore Report to added to Daily, weekly and Monthly reports |
Pitram Control Room, Pitram Mobile, Pitram Servers
Issue | Description |
---|---|
PR-35460 | PLM Komatsu - Use value from the Final Mass Weight packet to record dump |
PR-35386 | PLM Komatsu integration simulator update |
PR-35345 | Pitram Vision - Operator Override for Source location |
PR-35340 | Mobile - PLM - Add support new structure of the FinalPayload packets |
PR-35336 | Mobile - PLM - improve logging of COM port data |
PR-35292 | PLM Komatsu integration test app update |
PR-35264 | BLE - Implement the "tag:distance" logs and support in Vision player |
PR-35258 | MDU Logs review |
PR-35246 | Move FileTransferLog DB file into the main client database |
PR-35218 | PRIS - Add Position Source to GET /v1/equipment/positions. |
PR-35206 | Investigate multiple shift planner events slowing PRIS query completion |
PR-35197 | Optimise position handling |
PR-35138 | Integration mapping rules - Add CreateMeasureIfUnchanged implementation |
PR-35123 | P2P - Deliver PV service logs via P2P |
PR-35092 | Location Favourites when assigning an equipment to a location |
PR-35091 | AdHoc Service collect Windows device and driver management info |
PR-35090 | AdHoc Service bigger delays on restart |
PR-35086 | AdHoc Service periodical Wifi adapter restart can't be switched off |
PR-34538 | Mobile - Nest sublocations in the selection list |
PR-34537 | Mobile - Make display of sublocation in the SourceAllocation widget optional |
PR-34319 | Prevent Truck's Primary Allocation defaulting to Equipment instead of Location in DA |
PR-35471 | Loadscan Connector Setup Error fixed |
PR-35244 | Ability to define and display multiple measures |
PR-35056 | Different colour to indicate Shift is dirty when P2P Events submitted for a shift in Pitram Portal |
PR-34533 | Down Substatus from Dropdown |
PR-34339 | Enhancement Request - Event Editor - Add Event |
Issues Resolved
Pitram Portal
Issue | Description |
---|---|
DM-33198 | Surveying Module - Development Advance |
DM-33086 | Duplicate events in Material Movements |
DM-33283 | Dome RefData required invisible field |
DM-33259 | Issues with Reference Data Import |
DM-33250 | Details tab in Pitram Service - Shifts blank |
DM-33229 | Portal login delay |
DM-33178 | DOME is not synchronising with the server. |
DM-33139 | Shiftboss assignment in Event Editor / Data Acquisition not showing in SQL & Reporting for only specific user |
DM-33123 | OLAP Cube Location Status Duration wrong calculation |
DM-33118 | Date filtering in Targets, Service and Material Movements Module |
DM-33097 | An exception generated when trying to adjust stock |
Reporting
Issue | Description |
---|---|
DM-33236 | Missing Header information Reports Data Only |
DM-33200 | Mismatch Rows in Excel (data only) when running the Equipment Measures by Location - Destination |
DM-33193 | Dashboards long loading time |
DM-33162 | Firing # which is blasted to appear in 24Hr Metric Report against explosive used. |
DM-33138 | Operator Timesheets report extracts however report file doesn't save, giving browser error |
DM-33072 | Reconciliation Summary Report fails extraction - internal command error object reference not set |
DM-33042 | Grade Movements by Destination Report Macros including Incorrect Data |
DM-32521 | The "Personal Assigned to Location" report is running but not showing results. |
Pitram Control Room, Pitram Mobile, Pitram Servers
Issue | Description |
---|---|
PR-35572 | Incorrect shift orders |
PR-35241 | Entering any measure within the Measures Tab in DA causes previously submitted measures to be recorded again |
PR-35586 | Mobile - Grouping attribute stops working |
PR-35399 | PLM Hardware Diagnostic screen LastSent display bug |
PR-35303 | BMS error and stopped issue. |
PR-35293 | Loader sends DirectPayload to itself |
PR-35280 | Mobile - Respect UseLoaderBucket flag from BMS settings |
PR-35270 | BLE - Configuration update occurs too often and floods the logs |
PR-35257 | Pitram Vision - 'Hauling' cycle generated before 'loading' |
PR-35177 | P2P Can't store the RD file for P2P on the Server |
PR-35176 | PV Dump to unknown location instead of DTT |
PR-35172 | DA closing unexpectedly |
PR-35121 | DA time misalignment causes incorrect sync for Mobile |
PR-35116 | PRIS - Reference data attributes will not return start and end date time for the ref group shift |
PR-35104 | AdHoc/Postman/PV empty logs |
PR-35101 | Daylight Saving manual time adjustment - No information displayed |
PR-35100 | Issue with Daylight savings and StatusChangeRules |
PR-35094 | AdHoc Service hosted network is stopped and not recovered. |
PR-35079 | Event Editor Maintenance View - Comments disappearing from the UI |
PR-34957 | Lock RD for 5 minutes on Mobiles with weak connectivity |
PR-34862 | Pop-up boxes not visible in DA and EE on specific display settings |
PR-34656 | Location Status not reverting back to its last known status |
PR-26402 | Shift Plan - Print Preview not showing actuals for resources with no tasks |
PR-24157 | Event Editor Activelist filtering |
Service Pack 1
Bug Fixes & Improvements
Issue | Description |
---|---|
Pitram Portal | |
DM-33361 | Expand Repair States Report to add location and comments |
DM-33295 | Material Movements by Material Type remove equipment filter |
DM-33269 | Reporting - 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-33426 | Report - Unable to run material management reports by 'Shift' |
DM-33442 | Possible Bug - Reporting |
DM-32996 | Incorrect grades in Stock Management (LIFO location) |
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 | |
PR-35837 | Modify the logic to solve this issue in PRIS: "CodeMeasure" is not a Movement Measurement |
PR-35815 | BMSync null exception |
PR-35863 | Checklist does not update when Pitram Mobile is in Multi-Equipment mode. |
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-35813 | BMS overload |
PR-35770 | DA - Location Activity Panel Grid view - unable to open the context menu |
PR-35769 | Enter Measures Profiles Column Chooser preferences not saving |
PR-35765 | DA 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-35735 | BM WaypointInferenceSettings don't work |
PR-35600 | Signs showing as Open in Reporting Database |
PR-35335 | System flagging operator as unqualified |