Release Notes 6.0

Introduction

Release 5.0 is a major baseline, delivering major new functionality and rolling up a number of resolved issues.

While it may be necessary to provide some information contained in these release notes to clients as part of the normal consultancy process, the information provided should be relevant to, and personalised for, the individual client.

Pitram release 6.0 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\

The installer programs for Pitram Portal and the Dome Connector have been migrated from InstallShield to Inno Setup. An intuitive sequence of wizard pages are presented.

See Dome Connector & Pitram Portal Installers for more details.

 

An import feature of Pitram version 5 is an improved user interface for Data Acquisition and the Event Editor. The new interface provides the same workflows and ease of navigation you are familiar with, but with a modern look and feel.

A different theme may be applied to the application at runtime. Currently, two visual styles are available for selection: Dark and Light.

 

A feature of Pitram version 5 is an improved user interface for Activity Sheets in the Pitram Portal. The new interface provides the same workflows and ease of navigation you are familiar with, but with a modern look and feel.

The Activity Sheets module has also been fully migrated to HTML and Javascript, thereby removing any dependency on Microsoft Silverlight.

 

Pitram can now be configured to pass data from equipment operating outside of the mine network and back to the Pitram Server, solving a long-standing “Last Mile” communication challenge inherent in many mining operations.

The solution uses the mine’s existing network infrastructure and specially configured Pitram Mobile units to pass data between each other. Light vehicles servicing production drills, for example, may be fitted with a headless computer in order to pass the data.

Alternatively, trucks running Pitram Mobile may be configured to collect and pass data from underground loaders working outside of the mine’s network coverage.

In addition, the services which make this data transfer possible can now identify and log the health of underground access points within range. These logs are important when rolling out the solution, but also offer an additional service which can be used to assess the health and the suitability of a mine’s network infrastructure to run Pitram Mobile.

 

Auto Task Completion

For Shift Plan tasks created in Data Acquisition, it is now possible for those tasks to be completed automatically.

In order to change the status of a task automatically:

  1. The task must be Commenced, and

  2. The Equipment or Location must be in an appropriate state for completion, as defined by the task:

    • A Location task may be completed automatically if the location status changes from how it is defined in the task.

    • An Equipment task may be completed automatically if either the equipment status or the equipment location change from how they are defined in the task.

Task Template Dependencies

Task templates can now be created with dependencies preconfigured.

When dragging a task template or multiple tasks from a template into a Shift Plan, if the tasks have predecessors defined in the task definition, a dependency link is now created automatically. Note that dependencies are only created when multiple dependent tasks are dragged at the same time and will not be created retrospectively if the template tasks are individually created.

Pitram Connect

When running Pitram Connect on a tablet device, if the Shift Planner module is used, Shift Plan tasks can also be accessed.

Based on roles and permissions, the user is able to view the plan and create or modify tasks. The ability to view shift plans on mobile phones will be added in an upcoming version of Connect. This will provide an optimised view for smaller devices.

To improve usability, Pitram Mobile now provides multiple measure entry screens. The multiple measure entry screens may be configured, per mobile screen profile, to allow for the entry and submission of multiple measures at the same tim, rather than one by one.

The multiple measure entry screens can also be configured to suit certain activity types such as the development of different drive profiles.

See Multi Measure for more details.

 

Other Enhancements

Reporting

Issue Description
DM-28991 Location Status Report - Add Summary
DM-29523 Active stockpile Summary report layout changes
DM-29521 Equipment Timeline report issue
DM-29225 New Standard Drill and Blast Report with blasted time

Pitram Portal

Issue Description
DM-29220 Token based authentication for Integrations.
DM-26793 Olap - Update Installer to add status dimensions to Measure Fact
DM-28699 Selected date range display is confusing when production periods are used
DM-29606 PV - add RD options for network adapter configuration
DM-23950 PLOD sheet permissions - Edit and View.
DM-29185 Create audit table for targets value changes
DM-29244 OLAP Extend the Date dimension to cover longer period
DM-29297 Create PRIS call to get layers from the Grade Control staging tables
DM-29567 Activity Sheet - extend tracing for sheet processing
DM-29505 Ref Data - Language attribute should use a select list instead of free text.
DM-29439 Audit for reprocessing, locking and unlocking shifts
DM-29645 Reporting - Re-order 'Selected Values' for period selections in reporting
DM-25972 Stock Management - adjust location drop box width

Pitram Control Room, Pitram Mobile, Pitram Servers

Issue Description
PR-29065 Automated Train Visualizer
PR-29273 ESS - add caching mechanism for rollover event queries
PR-29524 ESS Cache - Disable cache in configuration or because of errors
PR-29087 Collect SPGT Tags battery life info
PR-29382 Include Pitram Vision detailed description in HardwareState
PR-29004 Clear downloaded from Mobiles logs/videos automatically
PR-28108 Convert DB Message log tables to logs (1-st GSS migration)
PR-29536 Remote download of system viewer logs from Mobile
PR-28960 Control tracing configuration for Mobiles from RD.
PR-29170 New column in Mobile Health panel - Equipment Function
PR-29351 Show deleted and edited events in EE
PR-27822 Pitram Mobile - manage applife settings from the ref data
PR-29293 Add Client DB and all Mobile configuration files request dialog functionality
PR-28018 DCU - Add device status icon to mobile
PR-30076 Show previous entered SMU value in Mobile on numpad view
PR-28772 Need to add numbering of rows to all panels
PR-28770 Need to add filtering by equipment model to Text Messenger
PR-29964 PV - add option to check and reconfigure ethernet adapter
PR-29237 PV - adjust logging levels of some predictions
PR-29340 Pitram Mobile - disable PVS for equipment without PV profile
PR-29432 Localization for Pitram Vision Player & Pitram Train Visualizer
PR-28696 Improve Signs Location Searching/Filtering
PR-28695 Allow line spacing to be recognised once a sign is confirmed
PR-28983 Mobile - SPGT - protocol v2
PR-29644 Extend existing PRIS call equipment material movement to allow to set material
PR-25872 Mobile - Add Task Progress information to Task Details screen
PR-29848 Replace Num Pad in mobile with a new WPF version
PR-30103 Create GSW icon in EE/DA
PR-27847 Mobile - Add duration percentage to details in My Tasks list
PR-24883 Filter on any matching text in DA - Shift planner - Task - Location picker

Issues Resolved

Along with the newly resolved issues listed below, Pitram 5.0 also includes resolutions to all issues addressed in the version 4.17.4 and older.

Reporting

Issue Description
DM-29637 Truck Cycles Duration Graph - Missing Movement & Combined Duration
DM-29134 Update Shift Statistics report fetch command
DM-29323 Location Status report joining issue
DM-29536 Cobar Timeline Report
DM-29174 Equipment Hours report - some equipment's hours are missed
DM-28834 MTBF report not showing correct count
DM-29625 Truck Cycles Duration report shows a lot rows than cycles.
DM-29730 MTBF Report totals incorrect
DM-29338 Current Sign Report not generating with all data
DM-29509 Equipment Hours report error

Pitram Portal

Issue Description
DM-29163 Change port in the default value for the ReferenceData Publisher address
DM-27854 Reference Data - Dialog box for UTF-8 export
DM-27828 Reporting - data browser export has wrong encoding for Russian language
DM-29065 PRIS - v1/materials-management/movements/grades/search call case sensitive
DM-29130 Material Management - improve export of movements
DM-29028 PRIS - equipment/measures/summary/search - input datetime of shift change
DM-29133 IT security - View Audit logs role provides access to all system configuration
DM-28889 Negative stockpiles are displayed incorrectly in Materials Management
DM-28949 GradeControlJundeeMovementSource fails when material is null?
DM-28891 User cannot set targets (-ve UTC Timezone Issues)
DM-28986 Manage Roles - Read Access and No Access don't work correctly
DM-29022 Active List Description higlighted by default
DM-29089 Stockpile Viewer Time Changed to 24hr Instead of Windows Setting
DM-29375 DOMEConnector consumes memory trying to view Grade Control movements
DM-29496 Problem indication processed shifts
DM-29686 Unable to load Stocks
DM-29231 The Read Access restriction for the Surveying doesn't work
DM-29418 Error when entering targets module
DM-29402 Stockpile Viewer - Location Active List sorting (and Material list)
DM-29424 Scheduled Reports - No access to completed jobs
DM-29634 Selected parameters show as alphabatical order
DM-29608 After an update there is missing shift, SHKEY issue
DM-29482 Grade Control Internal Command Failing
DM-29275 Cannot run the Daily Targets report for the YEAR period and budget selected
DM-29356 Deleted Active Lists
DM-29578 Pitram Portal - unable to open audit logs
DM-29683 DOME Excel data only report doesn't match with PDF report
DM-29678 Activity Sheets - processing fails for duplicate records without an error message
DM-25224 Change to "Week" Report parameter grouping in Materials Management

Pitram Control Room, Pitram Mobile, Pitram Servers

Issue Description
PR-29127 Mobile Health Panel - Time last seen connected is incorrect
PR-28787 When the task is too long the lower fields don't fit on the screen
PR-28996 In the summary measure 'PIP_ME_19' is not correctly calculated for trucks
PR-29115 PRIS - get v1/shiftplansv1/1/ doesn't return propper task description
PR-29028 Pitram Vision Player - shows incorrect tag
PR-29940 Dump to truck Event has not been registered
PR-30168 No ACSC statuses before reboot
PR-29976 Model uploads to Movidius fail
PR-29370 Client ID is not showing in Database
PR-29037 Shift Planner removes equipment and status information for tasks
PR-29145 Random personnel showing allocated to equipment without reason
PR-29144 Dome Connector Memory Leak
PR-29488 Missing data elements in ESS
PR-29083 Panel on DA is not showing current equipment state
PR-28116 Event not displaying all values.
PR-29225 Lag when dragging a truck load (High Memory usage DA)
PR-29067 ACSC - waypoint expire problem
PR-29618 Pitram Mobile - involuntary restart of the system
PR-30133 Edited Events Not Showing up in Materials Management
PR-30174 Automatic Status Change rules doesn't fire
PR-29970 Incorrect data with DTT in Reporting
PR-30226 PITRAMBusinessModelServer crashed
PR-28729 DA - mobile health panel, translate request logs & videos window
PR-30104 DA - error DAQ_0429 when force update Mobile
PR-30088 Event Editor fails to start (slow logging issue)
PR-29822 Could not connect to services if IPv6 enabled
PR-29959 PRIS - error while creating a task
PR-29846 Shift Events Missing Data
PR-30002 Dome does not reprocess old shifts when starting reprocess manually

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:

    • Errorlogs
    • Maps
    • Profiles
    • ReportDefinitions
    • Reports
    • Runtime Services
    • SystemConfiguration
    • 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 pro- gram 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: or from the FTP Server, 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 DomeConnector 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 perform an uninstall of the product prior to upgrade.

    13. Upgrade the DomeConnector first, see Dome Connector Service Upgrade, and then upgrade the DomeWebDeployment.

    Copy over the ‘DOMEWEBInfrastructure.dll’ file from the \Patches folder to the \inetpub\wwwroot\DOME\bin directory, replacing 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. If Dome is to be used on the Dome server through IE, navigate to the System->Manage Scheduled Tasks screen to make sure that the version of Silverlight installed on the server is of a compatible version. If Silverlight prompts you to upgrade, accept the download and upgrade Silverlight.
  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 per- form an uninstall of 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.
  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.

    21. Set the value of the flag Enabled to true.

  21. Start the Pitram Watchdog service.

    22. 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 perform an uninstall of 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

If you are upgrading from version 4.17 to version 5.0, there is no need to run an upgrade on the DomeConnector side. This may be required, however, if you are upgrading from older versions.

If the DomeConnector Service does not start, an upgrade may be required (Check the Windows Event Viewer). If this is the case, it will be necessary to use the DomeConnector from the command line to perform an upgrade and migration:

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

with the relevant flag and parameters. Once the upgrade is complete, the DOME Connector Service can be started.

Event Server Service Upgrade

An Event Server Service upgrade must be performed after installing version 5.0, or after upgrading to version 5.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 5.0  
Pitram Portal (Dome) 5.0  
Pitram File Distribution Service 1.5  
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.8.0.48 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 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 DomeManagement
    • 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 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:

    6. 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:

    7. 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 of 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.pdf To configure the functionality, begin with the section Prerequisites.
Belaz Truck Integration Pitram_ Mobile_BELAZ_Integration.pdf To configure the functionality, see the section Mobile SKZ Configuration.
Pitram File Distribution Service Pitram_ File_Distribution_Services_PFDS.pdf To install and configure the new functionality, see the section Quick Installation Guide.
Pitram Speed Monitoring Pitram_ Speed_Monitoring.pdf To configure the functionality, see the section Reference Data.

Pitram REST

Integration Services

 Pitram_ REST_Integration_Services.pdf To configure the functionality, see the section PRIS Installation and Configuration.
Pitram Connect Pitram_ Connect.pdf To configure the functionality, see the section Prerequisites.
Certiq Integration Pitram_ Mobile_Certiq_Integration.pdf  
Sandvik DCU Integration Pitram_ Mobile_Sandvik_DCU_Integration.pdf  
Mobile Log Requests Pitram_ Mobile_Log_Requests.pdf