Release Notes 6.0

Introduction

Release 6.0 is a major baseline, delivering major new functionality and rolling up a number of resolved issues. The release can be found at the following locations:

  • On the FTP site: /Staff/Software/Pitram/6.0.0-Release

  • On the shared network drive: \\PER-SRV-DFS\Installs\Pitram Installation\6.0.0-Release\

New Functionality and Enhancements

New User Interface: Drill and Blast

An important feature of Pitram version 6 is an updated user interface for the Drill and Blast module in Pitram Portal. The old Silverlight screens have been replaced with an HTML5/Angular UI preserving the same workflows and ease of navigation you are familiar with, but with a modern look and feel.

The renewed user interface allows the module to be displayed in modern browsers like Google Chrome or Microsoft Edge.

New User Interface: Pitram Mobile

Another important feature of Pitram version 6 is a modernized user interface in Pitram Mobile. Most of the screens have been remade to provide a new modern look and feel with improved navigations.

Pitram Upgrade Service

The Pitram Upgrade Service provides the highly requested functionality to automatically update Data Acquisition and Event Editor applications whenever there is an update. From Pitram 6.0, a new service will be included in the Control Room installation that will check for updates from the Pitram server. The site administrator can configure how they want the applications to be updated, via Reference Data Editor – see Pitram Upgrade Service.

Location Status Rules

Keeping track of location status is an important element of underground mine management and a key capability of Pitram. Pitram Location Status Rules provide functionality to automate location status tracking and minimise manual interaction by the Control Room operators. Previously limited to data captured in Data Acquisition, this functionality has now been extended so that “No Prompt” rules can be triggered by any data captured in Pitram including Pitram Mobile, Pitram Connect and third-party applications via PRIS. Rules that require an action by a user are still limited to only being triggered in Data Acquisition.

Pitram Licensing

In Pitram 6.0 we have introduced the Pitram Licensing Service (PLS) which works with Micromine Licensing Studio (MLS) to automate how a Pitram site is licensed. Once sites are moved over to subscription pricing, PLS will automatically refresh a site license to include, add or remove modules, extend expiration dates and will no longer require a Pitram Specialist to manually copy licence files. Some new screens have also been added to Pitram Portal to enable site administrators to view licence information and request updates if required. For more information, refer to Micromine Licensing Service and Pitram Licence Service Installation Guide.

Other Enhancements

Reporting

Issue Description

DM-29646

Loader Cycle Status Report

DM-29835

Fix Export to Excel data only column alignment

DM-29597

New Standard report: TKM Report

DM-29883

Create Standard report for pre-start checklist

Pitram Portal

Issue Description

DM-29781

Optimize rendering time for Movement page

DM-30196

Hide "Allow Editing Of Transactions" option from the Materials Management

DM-27879

Add Encryption options to Mail Config

DM-30148

PRIS - add proper logging and tracing for API

Pitram Control Room, Pitram Mobile, Pitram Servers

Issue Description

PR-30324

Implement data transfer from pre-start checklist in Mobile to Pitram Server DB

PR-30232

Migrate context menus in DA to support themes

PR-30759

The new Helper X2 firmware requires a handshake

PR-30751

Helper-X firmware HelperX HXG_00_05 doesn't work with Mobile

PR-30641

PRIS support for new shift task properties: Auto complete on equipment status or location change

PR-30359

Mobile - F5 Diagnostics screen not showing predictions from Pitram Vision

PR-29557

PV - add support for Orlaco EMOS camera

PR-30380

Rewrite the Alarm dialogs to WPF

PR-30395

Migrate Pitram installers to Inno Setup

PR-30172

Mobile - SPGT - receive tags without ID shifting

PR-27001

Configure mandatory measure entry - Pitram Mobile

PR-29946

Activate Context Menu Config for Person

PR-30767

SPGT - new protocol 2.2 for external antennas

PR-22750

Administrator will be notified to restart Mobile if required

Issues Resolved

Reporting

Issue Description

DM-29821

Equipment Timeline report

DM-29730

MTBF Report totals incorrect

DM-30259

Repair Status reports calculation

DM-29644

Equipment status total hours are exceeding calendar hours

DM-29986

Report: Equipment Timeline with Measures handling error

DM-29911

Error running Location Status Report for multiple months

DM-30107

EE Data mismatch vs Equipment timeline with comments

DM-30078

Report Equipment timeline with maintenance comments error

DM-30203

MTBF Report Issue

DM-29768

"Object moved to here" in reports

Pitram Portal

Issue Description

DM-30260

Equipment Timeline With Maintenance Comments report does not display comments

DM-30205

Stockpile view keeps crashing

DM-30178

Issue pasting data in Targets module

DM-30126

Deploying Views Failing

DM-30099

Issue with exporting from Data Browser

DM-30090

Unable to use web display panel

DM-30083

Results from a Grade Control Procedure do not match Material Management

DM-30082

Activity sheets not filtering locations by Mine Region and shifts by users shift rosters

DM-30081

Targets in Dome changing themselves

DM-30079

DOME Ref Edit has a refresh on every attribute that makes you have to click twice when entering specific locations.

DM-30068

Shift reprocessing taking longer after the upgrade

DM-30065

Export to XLSX or CSV logs user out of Portal

DM-30064

Changes of values in the Targets are not saved through the Google Chrome

DM-30063

Activity Sheet decimal issue

DM-30060

Unable to create scheduled jobs

DM-30059

Scheduled Jobs disappearing from Dome

DM-30057

Activity Sheet non-responsive or poor performance

DM-30023

Stockpile Viewer showing incorrect Grade

DM-30018

Accounts are not disabled after a number of failed login attempts

DM-30017

Unable to reactivate account after automatic deactivation

DM-30007

Unable to log into Pitram Portal issue - Domain

DM-29970

Reports with a symbol "," in the title do not work in Google Chrome

DM-29932

Support Error Log scaling broken

DM-29924

Activity Sheet time error

DM-29904

Unexpected error while processing Activity Sheet

DM-29896

Data browser export to any format doesn't work

DM-29880

Missing scheduled jobs

DM-29867

Incorrect display of pop-up windows on the portal

DM-29865

Unable to open saved reports in the Library module

DM-29807

Mismatch between OLAP cube data and reporting data

DM-29806

Material grades import error

DM-29804

Task schedules are disappearing

DM-29789

Task schedules are duplicated

DM-29784

Error adding a user to the role

DM-29783

Incorrect authentication

DM-29701

Materials Management error

DM-29639

Random account created as integrated

DM-29441

Local user account losing role

DM-29425

Scheduled Jobs - Output description not working correctly

DM-29310

Shift flagged for reprocessing within the auto processing window

DM-28077

Google Chrome Report View bug

DM-25215

Local account converted to Integrated

Pitram Control Room, Pitram Mobile, Pitram Servers

Issue Description

PR-30899

Does not display truck payload tonne on Excavator Mobile

PR-30897

Issue with deleting tasks in Shift Planner

PR-30343

Some shift plan tasks have NULL fields in the reporting database

PR-30724

ESS was not available on Rasvumchorr

PR-30601

SKZ 1 and SKZ 2 configuration

PR-30583

Hanging TREKs when changing the operator

PR-29924

Efemcukuru - Pitram Mobile 3rd party applications

PR-30796

Helper-X 1-st gen doesn't work with Mobile 5.1, 5.2 and 6.0 handshake

PR-30881

Shift Planner task auto start not working

PR-30388

Mobile tablets keep flagging qualified operators

PR-30891

Event editor - Maintenance View - Add Event - Record exclusive status against equipment

PR-30878

Generated Measure issue from Multi Measures in Mobile

PR-30651

Corrupted logs delivered to server

PR-30916

DA - Material Movement has incorrect details when truck allocated to IDLE on second loader

PR-30906

Operator deallocation didn't work in the shift change (BMS double restart problem)

PR-30922

Corrupted Mobile.UpdateAgent.exe. config file

PR-30812

Odd dump generating while ore pass cleaning (SPGT 255m)

PR-30798

Vision Player - "can't serialize..." error

PR-30192

Pitram Vision - No predictions

PR-30686

Arrow Keys not working in dialogue box

PR-30634

Train Visualizer - couldn't parse SPGT log

PR-30721

Data acquisition location status drop down view

PR-30684

Tonnes In/Out UI does not reset after shift rollover

PR-30637

Event Editor - Event Source showing as "Manual"

PR-30635

Pitram Vision player doesn't show payload measure in real time

PR-30627

Missed dumps to truck

PR-30613

No Server logged time in EE

PR-30511

Record Attribute against equipment event in Event Editor

PR-30350

BMS crashed on Rasvumchorr

PR-30572

Columns missing from the Mobile Health Panel

PR-30496

Pitram server troubles and DA

PR-30485

DA Crashes when entering SMU Measures

PR-30352

ACSC to use "closest" waypoint

PR-30509

BMS – auto status change doesn't fire (no primary status set)

PR-30499

Vision Player - unhandled exception

PR-30500

Vision Player - name parsing

PR-30492

Event Editor failed to get this cell's value from the Business Model server

PR-30482

Data Acquisition error DAQ_0408

PR-30445

Event Editor - Maintenance mode doesn't disable the 'Movements' view

PR-30513

Incorrect data via PRIS call

PR-30116

After restart without communication, Mobile does not see the last status

PR-26121

DA - Unrelated Shift Planner warning displayed

PR-30535

Mobile Health Panel - Error resolving IP address

PR-22157

Drag to Location Activity Panel does not filter locations

PR-30718

Unable to click and drag equipment and operators to locations

PR-30837

Pitram Mobile - incorrect data in logs

PR-30836

Pitram Mobile - no data from SPGT

PR-30119

Group Status Location changes

PR-30528

Incorrect shift tasks in Reporting

PR-30697

DA freezes

PR-30731

Separate primary equipment measures from secondary equipment measures

PR-30792

Event editor showing flags when it shouldn't

PR-30609

Forwarded by P2P column shows equipment as 'unknown'

PR-30464

Enter measure screen delay

PR-30921

Truck Payload display remaining on top

PR-30516

Shift View Starts 3/4 Scrolled Down

Implementation Procedure

  1. Preparation: Inform Site Controllers and other relevant personnel of change, back up licence files, Pitram/Dome/Control Room configurations and customisations.

  2. Preparation: Ensure that it will be possible to back up the server-side databases during the change implementation. This means ensuring:

    • Access to the databases is possible from SQL Server Management Studio
    • It is possible to back up the databases to a file, either on the network or removable media
    • There is enough disk space for the backup files
    • It is possible to access the backup files if a restore is needed.
  3. Back up the Pitram Server configuration machine folder:

    • The folder can be found at C:\ProgramData\Micromine\PITRAM or the equivalent location on an alternative drive.

    • It is not necessary to back up the profiles in the configuration folder, just the machine folder.
  4. Back up the IIS Dome Web Site Configuration:
    • The Dome (aka Pitram Portal) website can be installed in any location, it depends on where the wwwroot folder was located at the time that the Internet Information Services were installed. However, it is almost always installed at:
    • C:\inetpub\wwwroot\DOME\Configuration

    Backup the following folders from the configuration folder:

    • Error logs
    • Maps
    • Profiles
    • Report Definitions
    • Reports
    • Runtime Services
    • System Configuration
    • Backup the three XML files from the root of the configuration folder.
  5. Backup the Dome Site Configuration:

    • The Dome connector configuration is stored in the program files directory on the server. This can also be labelled the program files (x86) directory. Within the program files directory, it is stored in the \Micromine Pty Ltd\Micromine Dome Connector\Config directory, in a directory name that represents the site. This directory name will have been created at the time that Dome was installed.

    • Within the site name directory, there are three further subdirectories – Dome, Pitram and Production. Only three files are required to be backed up – they are the configuration .XML files in each of these subdirectories.

  6. Backup the Control Room Configuration:

    • The configuration folder contains the machine configuration and system display settings for individual logins.

    • For Windows 7, 8 and 10, the folder can be found at C:\ProgramData\Micromine\PITRAM or the equivalent location on an alternative drive.

    • Back up everything in the configuration folder.
  7. Copy the relevant upgrade executables from: \\PER-SRV-DFS\Installs\Pitram Installation\
    or from the FTP Server ftp://staff@ftp.micromine.com/Staff/Software/Pitram/ to a directory accessible by the Pitram servers.

  8. If Controllers wish to continue to enter events in ‘local mode’ through Data Acquisition, ensure all needed Data Acquisition Clients are running prior to shutting down the Pitram Server services.

  9. Stop all Pitram Server Services, including the Pitram Watchdog Service. After stopping the Pitram Watchdog Service, ensure that it has not restarted the other Pitram Services by refreshing the services window.

  10. Stop the Dome Connector service.

  11. Using MS SQL Server Management Studio, back up all Dome and Pitram Databases to a file or device, for easy restoring. If databases are large, consider backing up and truncating the transaction logs prior to the database model, or seeking approval to transition to a simple recovery model.

  12. Upgrade Dome. It is not necessary to uninstall the product prior to upgrade.

    Upgrade the Dome Connector first, see Dome Connector Service Upgrade, and then upgrade the Dome Web Deployment.

    Note: Since version 5, the ‘DOMEWEBInfrastructure.dll’ file does NOT need to be copied over from the \Patches folder to the \inetpub\wwwroot\DOME\bin directory to replace the old file.

    • Use F12 to open the Developer Tool.

    • Select the Network tab.

    • Click on the Clear Cache icon.

  13. Sign-in to the Pitram Portal as Dome Administrator and upgrade the databases. After successful database upgrade, sign out of Dome.

  14. Navigate to the Reference Data module and deploy the views. If time permits, sign out and restart the server(s).

  15. Sign-in to the Pitram Portal and check the error logs.

  16. Navigate to System -> Manage Services. For the Reporting Service, click on the Install button if it is grey.

  17. Upgrade Pitram Server, including MobileAppLife if installed. It is not necessary to uninstall the product prior to upgrade.

  18. Upgrade the Pitram Server databases. Open a command prompt, navigate to the Pitram Server Installation directory on the server, type:

    • 'Micromine.pitram.eventserver.exe – upgrade'

    and press the Enter key. Ensure no errors are reported in the command window or Windows Event Viewer.

    See also Event Server Service Upgrade.

  19. Enable the Business Model Server Web Services. This step is necessary if the version of software being upgraded is a release prior to version 4.6.0:.

  20. In the Machine folder (see step 3), open the file BmsWebServicesConfuguration.xml.

    Set the value of the Enabled flag to true.

  21. Start the Pitram Watchdog service.

    Launch the Pitram Server Management Console (PSMC) and connect to the Pitram Watchdog. If all Pitram services are already running, hit Refresh a few times to make sure they are stable. If they are not running, click on the ‘Start all’ button and ensure all services start. Again, hit Refresh a few times to make sure they are stable.

  22. Upgrade Pitram Control Room on one workstation. It is not necessary to uninstall the product prior to upgrade.

  23. Open Data Acquisition and Event Editor and ensure normal operation is experienced. Decide whether rollback is necessary. If it is, do it now.

Dome Connector Service Upgrade

A Dome Connector Service upgrade must be performed after installing version 6.0, or after upgrading to version 6.0. The upgrade is required to populate data in staging tables GradeControlProductGrade and GradeControlProductMovement in the DOMEProduction database. This will allow Materials Management to run in the optimised mode, providing improved performance.

From the command line, go to the folder where the executable (DOMEConnectorService.exe) of the Dome Connector Service is installed. The usual location is:

  • C:\Program Files (x86)\Micromine Pty Ltd\Micromine DOME Connector\DOMEConnectorService.exe

Execute the command:

  • DOMEConnectorService.exe -mmo [SiteName]

Once the migration is complete, the Dome Connector Service can be started.

Event Server Service Upgrade

An Event Server Service upgrade must be performed after installing version 6.0, or after upgrading to version 6.0.

From the command line, go to the folder where the executable (Micromine.Pitram.EventServer.exe) of the Pitram Event Server Service is installed. The usual location is:

  • C:\Program Files (x86)\Micromine Pty Ltd\PITRAM\Server

Execute the command:

  • Micromine.Pitram.EventServer.exe -update

Once the upgrade is complete, the Pitram Event Server Service can be started.

Applications Compatibility

To ensure that all Pitram services and applications work reliably, refer to the following table which describes the version dependencies between individual applications:

Application Version Notes

Pitram Servers, Control Room, Mobile

6.0

 

Pitram Portal (Dome)

6.0

 

Pitram File Distribution Service

1.6

 

Pitram REST Integration Services (PRIS)

1.0.0.51

PRIS for ICA Connector, PWB Connector and MPM Connector currently running on sites do not need to be upgraded.

Pitram REST Integration Services (PRIS)

1.0.0.51

PRIS for ICA Connector, PWB Connector and MPM Connector currently running on sites does not need to be upgraded.

Pitram REST Integration Services (PRIS)

1.9.0.34

This version is required for PIP integration. PRIS for Pitram Connect, The ICA Connector, PWB Connector and MPM Connector are also supported by this version.

Pitram 3D

Micromine 2020

  

Rollback

If the Change Implementation is unsuccessful, the system should be rolled back to its pre-upgrade state immediately.

  1. Uninstall Pitram and Dome, in Control Panel. Also uninstall Pitram Control Room on Control Room PCs.
  2. Copy over and install previous versions of Pitram and Dome. Install Pitram Control Room on Control Room PCs.
  3. Stop all System Services:
    • This can be performed using the Pitram Server Management Console (PSMC), or services can be stopped individually. If using the PSMC, make sure that after all services are stopped, the Watchdog services are manually stopped.
    • Start-> Run-> services.msc will launch the Control Panel service management application.
    • Services to be stopped are, in this order: Pitram Business Model Server, Pitram Reference Data, Pitram Event Server Service, Pitram General Services, Pitram Watchdog Service, Dome Connector Service, Dome Management, World Wide Web Publishing Service.
  4. Backup all system databases on the database server. This may help in restoring data entered between the system upgrade and the rollback times. Alternatively, advise the site that they must re-enter all data entered in between those times after the system has been rolled back.
  5. Restore the Pitram Server configuration:
    Copy the backup files in the Machine folder over the top of the existing files and folders in the Configuration\Machine folder.
  6. Restore the Control Room PC Configuration:
    Copy the backup files in the Configuration folder over the top of the existing files and folders in the installed Configuration folder.
  7. Restore the Dome Web Site Configuration:
    • Restore the following folders from the backup into the c:\inet- pub\wwwroot\DOME\Configuration folder:

    • Errorlogs Maps Profiles

    • ReportDefinitions Reports

    • Runtime Services

    • SystemConfiguration

    • Restore the three XML files from the backup to the root of the c:\inet- pub\wwwroot\DOME\ configuration folder.

  8. Restore the Dome Site Configuration:
    • Restore the configuration.xml files from the backup to their original positions in the Program Files…\Micromine Pty Ltd\Micromine Dome Connector\Config… Dome, Pitram and Production sub directories.
    • The site may have multiple connectors. In this case, repeat the above restore for each of them.
  9. Start All Services:
    • Start-> Run-> services.msc will launch the Control Panel service management application.
    • Services to be started are, in this order: Pitram Watchdog Service, Pitram General Services, Pitram Event Server Service, Pitram Reference Data, Pitram Business Model Server, DomeManagement, Dome Connector Service, World Wide Web Publishing Service
  10. Using the Pitram Services Management Console, verify that it is possible to connect to the Watchdog service, and that all Pitram, Dome and IIS services are running.

    11. Ensure that Data Acquisition and Event Editor launch, and that canvasses and panels are displayed.

    Login to Dome, and ensure all collectors validate. Ensure all installed services are operational, including the Pitram service. Ensure a sample of reports can be executed.

Installation and Configuration Documents

Feature Documentation Notes

Pitram Mobile & Vision Setup

Pitram Mobile Vision Setup

To configure the functionality, begin with the Prerequisites section.

Belaz Truck Integration

Pitram Mobile BELAZ Integration

To configure the functionality, see the Mobile SKZ Configuration section.

Pitram File Distribution Service

Pitram File Distribution Services PFDS

To install and configure the new functionality, see the Quick Installation Guide section.

Pitram Speed Monitoring

Pitram Speed Monitoring

To configure the functionality, see the Reference Data section.

Pitram REST Integration Services

Pitram REST Integration Services

To configure the functionality, see the PRIS Installation and Configuration section.

Pitram Connect

Pitram Connect

To configure the functionality, see the Prerequisites section.

Certiq Integration

Pitram Mobile Certiq Integration

 

Sandvik DCU Integration

Pitram Mobile Sandvik DCU Integration

 

Mobile Log Requests

Pitram Mobile Log Requests

 

Pitram Licence Service

Pitram Licence Service Installation Guide