CAT FLEET & HEALTH V4.0.pdf

Cat® Fleet 4.0 Cat® Health 4.0 Release Notes

Contents

Table of Contents Change History

7

Overview

8

New and improved features

8

Platform

8

Installation

8

Deprecated features and functionality

8

Fleet on-board system changes

8

Resolved issues

8

Enhancements

8

Known issues

8


9

Health

10

Health web-based user interface

11

Measure Groups

13

Corporate Data Share and VIMS File Upload

14

Configuring VIMS or HIM to send events in real time

15

To configure VIMS 3G/HIM to send events to the office via communicator

15

To configure VIMS/HIM to send events using the Configure VIMS Wireless Messaging Health job 15 To configure VIMS to send events to the office in real time

16

Configuring Pollable Channels

17

Support for larger fleet diversity

18

Fleet web client

19

Opening the web client

19

Closing the web client

19

Remote Foreman's Terminal

20

Site Map

21

Travel Progress Monitor

22

KPI Dashboards

23

Production

24

Material Moved

24

Cumulative Material Moved

24

Cat® Fleet / Cat® Health 4.0 Release Notes

Page:2

Contents

Utilization

26

Loading

27

Shift Average

27

Rolling Average

28

Cumulative Duration

28

KPI Configuration Tool (Time Usage Model)

29

Real-time KPI Persistence

31

Update KPI Summaries XML

31

Run makeDataStores

31

Review KPIGen.properties

31

Update the Customer's KPI Summaries Universe

32

Create Dashboards or Reports that access real-time KPIs

32

Delays Email notification of delays

33 33

Delay Category Finder

34

Field Delay Type View

35

Delay Type Finder

36

Delay Type Editor

37

Site Monitor

38

Destination Assistant

39

Delay Work Order References

40

Delay Activities

43

Delay Activity Types

43

Delay Activity Classes

43

Attaching a Delay Activity Class to a Delay Type

44

Creating a Delay with Delay Activities

44

Splitting Delays with Delay Activities

45

Merging Delays

45

Delay Activities database changes Tables

46 46

Safety Checklist

47

Safety Check Record

48

Shift Change

49

Shift Change Finder

50


Page:3

Contents

Shift Change Editor

51

Setting a tie-down load state

52

Creating shift change tie-downs with penalty durations

53

How penalty durations are evaluated

55

Tie-Down Assignments

57

Shift Change Allocations Monitor

58

Sending operator messages to multiple machines

59

Outbound office message timeout

60


61

Travel Progress Manager drag and drop

63

Travel Progress Monitor configure options

64

Empty trucks

64

Loaded trucks

64

Station trucks

65

Personnel Editor

66

Site Editor - Rollback option for Surface

67

Sending Scheduled Assignments

69

Deleting Scheduled Assignments

70

Dragline Operational Statistics

71

Machine Class Capabilities

72

Machine Class Editor

73

Destination Chooser

74

Cycle Editor

76

Daylight Saving Timezones

77

On-board hardware configuration

78

Impact of the changes

79

Mining Blocks: Archive Page configuration

81

Assignment Options U-Turn policy

82

Data Share

83

Synchronizing Fleet and Terrain Data

84

Data synchronization preparation

85

Enabling data synchronization on Fleet

85

Machine associations

86

Platform


87

Page:4

Contents

Java

88

Memory sizes

89

GeoServer

90

Web Client

91

BusinessObjects 4.0

93

Knowledge Network

94

Hardware Requirements

95

KPISUM universe

96

Universe split for VIMS

97

Support SQL Server

98

Coordinated Universal Time (UTC)

99

Changed Reports

101

General changes affecting all reports

101

Specific report changes

101

New Reports

103

Validation

103

System Health

103

Health

103

Template Historical

103

Changed Objects comparison

104

Real-time KPIs

105

BORefresh end of life

106

Command for hauling Reference Implementation BIAR

107 107

Oracle RMAN

108

Third Party tool changes

109

Windows Task Scheduler

110

FTP Server

111

Installing Microsoft SQL Server 2008 R2 on Windows Server 2008 R2

112

Running Fleet on SQL Server

113

VM Snapshot - Known Issue

114

Installation

115

Installation procedure

116

Upgrading from release 3.x to release 4.x


116

Page:5

Contents

Upgrade path for minor releases

117

Exception running makeSpatialStores

117

Zip upgrade installation

118

Zip upgrade release artifacts

118

Zip upgrade steps

118

Exception running makeSpatialStores Troubleshooting GeoServer Exception error when running makeSpatialStores

119 120 120

Configuring Windows Auto Updates

122

Oracle Database 11g Express Edition

123

Health install and Licensing options

124

Health configuration changes

125

makeDataStoresHealth

125


126

VIMS 3G Download Job

127

BusinessObjects 3.x

128

Deski Reports

129

BORefresh

130

Oracle 10g

131


132

Fluid Transaction

133

On-board hardware changes

134

Startup connectivity check

135

Display deprecation

136

Health Information Module compatibility

137

Resolved issues

139

Enhancements

151

Known issues

159


Page:6

Change History Date

Change

Edited By

Version

7 December 2012

Draft

K Wilson

Draft

14 December 2012

Added Resolved Issues and Improvements for Build M6-1.

K Wilson

Draft

22 January 2013

Added Resolved Issues and Improvements for Build M6-2.

K Wilson

Draft

11 March 2013

Updated Resolved and Known Issues and Enhancements up to build M8-1.

K Wilson

Draft

8 April 2013

Updated Resolved Issues and Enhancements for build M8-2.

K Wilson

Draft

23 April 2013

Updated BusinessObjects Reports with changes in build 4.0 M-9.

K Wilson

Draft

29 April 2013

Updated Resolved Issues for build M9-1.

K Wilson

Draft

K Wilson

Draft

Updated Resolved Issues for build M10-1. 22 May 2013 Changed BusinessObjects section.

Information in this document is subject to change without notice. While every effort has been made to ensure that the information contained within this document and the features and changes described are accurate, Caterpillar cannot accept any type of liability for errors in, or omissions arising from, the use of this information. This document and all related documentation are the property of Caterpillar and may not be reproduced, transferred, sold, or otherwise disposed of, without the written permission of the owners.


Page:7

Overview

Overview Welcome to the release notes for Cat® Fleet and Cat® Health release 4.0 which delivers functionality and other improvements over those delivered in Fleet 3.1 and 3.1.1. These release notes have the following sections.

New and improved features This section comprises new and improved features in Fleet 4.0, starting with the major new features such as the Health and Fleet web clients, and moving into the improved and enhanced features such as Site Editor surface rollback and Machine Class capabilities.

Platform This section comprises new and updated platform information for Fleet 4.0, such as GeoServer and BusinessObjects 4.0.

Installation This section describes changes to, and requirements for, the Fleet 4.0 install process.

Deprecated features and functionality This section details features and functionality that has been deprecated from Fleet 4.0.

Fleet on-board system changes This section describes changes to Fleet on-board systems.

Resolved issues This section provides a lit of resolutions completed in Fleet 4.0 for previously identified issues.

Enhancements This section provides a list of enhancements in Fleet 4.0.

Known issues This section comprises the known issues in Fleet 4.0.


Page:8


New and improved features This section outlines the new and improved features in release 4.0.


Page:9

Health

Health The following sections describe the new features relating to Health.


Page:10


Health web-based user interface A new web-based Health user interface is available for monitoring real-time, or exploring historically logged, data from Caterpillar VIMS and third-party machines fitted with a Caterpillar third party interface (TPI) device. New viewers can be configured by users to display specific selections of health events, trend, cumulative and channel data from devices and the specific configuration stored and recalled by any other system user.

Timeline Viewer The Timeline Viewer provides a graphical view of real time (as it occurs on-board) and historical data, for multiple channels.

Spatial Viewer The Spatial Viewer provides a graphical view of spatial, real time (as it occurs on-board) and historical data, for multiple machines.

Event Monitor Viewer The Event Monitor Viewer provides two views of health events; one view presents event activation and deactivation in line with sensory data, the other view presents the data in tabular form. The location at which events occur is also automatically plotted on the adjoined site map.


Page:11


For more information, refer to the online help, or see the Heath chapter in the Fleet User manual.


Page:12

Measure Groups

Measure Groups With the introduction of the Health Monitor, a new concept of Measure Groups has been introduced to simplify the management of health monitors. You are able to define groups of trends, cumulative and channels, and provide the group with a custom name. Groups are visible to all users system-wide and can be used to simplify the creation of new health monitors around commonly targeted channels, trends and cumulative.


Page:13

Corporate Data Share and VIMS File Upload

Corporate Data Share and VIMS File Upload A new job has been introduced which allows for on-forwarding VIMS files from office software installations to multiple FTP and/or secure FTP locations. Scheduled regularly, this job simplifies VIMS file management and processes required to send files to Caterpillar, Dealer or alternative customer sites.


Page:14

Configuring VIMS or HIM to send events in real time

Configuring VIMS or HIM to send events in real time There are three options for configuring VIMS or HIM to send events in real time. All of them involve informing the device which Office IP Address to send events too. The options available are: 1.

Configure each machine by connecting to the web server (communicator) embedded in each device and setting the office IP address.

2.

Run the Configure VIMS Wireless Messaging Health job to send TMAC message to machine to alter its configured IP address.

3.

Run a system command to send TMAC message to the machine to alter its configured IP address.

To configure VIMS 3G/HIM to send events to the office via communicator Note: See your VIMS 3G or HIM setup manual for more detailed instructions. VIMS 3G and HIM 2.x come with an embedded web server often referred to as communicator. You can configure the device to send events to the office via communicator by setting the Office IP address. Do the following steps for each machine. 1.

Connect to communicator with a web browser.

2.

Open the administration page for the office IP address.

3.

Enter in the field IP address for the office software.

4.

Click Apply.

To configure VIMS/HIM to send events using the Configure VIMS Wireless Messaging Health job You can change the internally configured Office IP address of each device by running the Configure VIMS Wireless Messaging job, which sends a TMAC message to each machine selected in the job with the current office IP address. 1.

Click Jobs > Health > Configure VIMS Wireless Messaging.

2.

On the Standard Options tab, select the machines you wish to configure.


Page:15

Configuring VIMS or HIM to send events in real time 3.

Click Run.

To configure VIMS to send events to the office in real time 1.

Ensure the CommsServer is running.

2.

Start a Field Communications Monitor for diagnostics.

3.

In a command shell, run the following command (type it in as a continuous line):

mstarrun com.mincom.integ.field.handler.util.SendBroadcastSet For example: mstarrun com.mincom.integ.field.handler.util.SendBroadcastSet tmac://192.168.1.44:51889 172.30.44.34 4.

Monitor the Field Communications Monitor for an outgoing CmnBroadcastSet2 request and a corresponding CmnBroadcastSet2Response response.

5.

Monitor the machine for VIMS events, using Health Event Monitor.


Page:16

Configuring Pollable Channels

Configuring Pollable Channels Pollable channels are only configurable for VIMS 3G and TPI. The command for configuring pollable channels is as follows. mstarrun -b healthChannelSetup ,.. e.g. mstarrun -b healthChannelSetup T01,T02


Page:17

Support for larger fleet diversity

Support for larger fleet diversity Prior to release 4.0, Health supported a maximum number of different channels, trends and cumulative types. Newer versions of VIMS have increased the diversity of channel, trend and cumulative types, limiting the fleet diversity that a single install can support for Health reporting purposes. Release 4.0 removes this limitation through some underlying data storage structural changes. As a result, the profile database storage size, performance of VIMS file import and BusinessObjects reporting differ from prior versions of Health. The exact difference depends on many factors and is dependant on the specifics of the installation; in some cases improvements will be observed while in others a performance reduction will be observed. See the Compatibility Matrix document for more information on application sizing and performance guides.


Page:18

Fleet web client

Fleet web client The Fleet web client provides a web-interface version of the office software.

Opening the web client To open the web client, you need to open your Internet Browser, and enter the URL which will have been given to you in an email, or by a Customer Support representative. Select the Language you wish to view the software in, and enter the Username and Password that has been given to you. The web client opens displaying the Site Map as the default desktop. You are able to open other desktops such as Travel Progress Monitor and KPI Dasboards.

Closing the web client To close the web client, click the Options icon on the top right of the screen and click Log-Out, or close your browser window.


Page:19

Remote Foreman's Terminal

Remote Foreman's Terminal The Remote Forman’s Terminal (RFT) provides a low bandwidth view of the office software to a Foreman, who is looking at it primarily while in the field, allowing them to monitor the decisions made by the office software and the Mine Controllers. RFT can either be installed on individual laptops or accessed through a web browser. Installing on a laptop is recommended when low bandwidth support is needed. Any updates to the client are downloaded automatically on opening the client. For instructions on how to install and use the Remote Foreman’s Terminal, refer to the Fleet web client online help. The Remote Forman’s Terminal comprises the following. •

Site Map

•

KPI Dashboard

•


In addition the Remote Foreman’s Terminal •

is read-only.

•

will work on small screen laptops, for example, a Panasonic Toughbook™ with a screen resolution of 1024x768.

•

will work in low-connectivity wireless networks and function with a low bandwidth.

•

will work in both very high and very low light conditions.

•

provides accompanying online help.


Page:20

Site Map

Site Map The Site Map shows the current position and relevant information of machines in near real time. It allows a foreman to search and follow individual machines, and in the case of loading tools and processors, see which machines are on-route and queuing.


Page:21


Travel Progress Monitor The Travel Progress monitor shows the relative position, and allocation, of trucks to loading tools and processors. The Travel Progress Monitor in Remote Forman's Terminal is designed differently to the existing Travel Progress Monitor available in the desktop client. These changes include: •

truck travel direction has been swapped. Machines now travel right to left.

•

the timeline has been split, showing 0 to 10 minutes and then 10 minutes to the longest ETA.

•

when machines are on delay they are organized by their last known location.


Page:22

KPI Dashboards

KPI Dashboards The KPI desktop displays dashboards showing different KPIs. •

Production

•

Utilization

•

Loading

These metrics are a consolidation of different mining requirements.


Page:23

Production

Production On the Production screen you can choose to view Material Moved or Cumulative Material Moved information. On both screens you can filter by Loading Tool and Material, or choose to display All Loaders and All Materials.

Material Moved This view displays information relating to the number of tonnes (or the appropriate unit of measurement for your mine site) of material moved within the current shift. It indicates the following. •

The actual amount of material that has been moved for the current shift.

•

An estimate of how much material will be moved on the current shift, projected from the current progress and time remaining for the shift.

•

An hour-by-hour breakdown for the current shift, showing the amount of material that was moved per hour.

•

For the current hour, an indication of the likely figure at the end of the hour, estimated from current production and time remaining.

The screenshot below is an example only.

You can filter the data by machine and material by selecting the desired option from the filter buttons above the graph. These are shown below. Units may vary depending on the type of material selected. If multiple materials are selected the Mass unit is shown. For a single material, the unit is based on the type of material selected. For example, if set up correctly, Waste could be shown as BCM (Bank Cubic Meter).

Cumulative Material Moved Click the drop-down arrow by Material Moved and select Cumulative Material Moved. This view displays the cumulative material moved throughout the shift. The screenshot below is an example only.


Page:24

Production

The quantity of Prime and Rehandled material is displayed on an hour- by-hour basis. You can filter the data by machine and material by selective the desired option from the filter buttons above the graph. These are shown below. Units may vary depending on the type of material selected.


Page:25

Utilization

Utilization This screen displays the KPIs relating to the loading tool availability and utilization as a percentage within the current shift. The loading tool names are listed on the left of the graph, with the percentages along the bottom of the graph. Average availability and utilization are displayed as a line dropping down to the average percentage. The screenshot below is an example only.

Note: Only those loading tools which Cycles and KPIsummaries have determined have production numbers are displayed.


Page:26

Loading

Loading This screen displays loading tool specific KPIs. You can choose between the following three options: •

Shift Average The average Load, Hang, Queue and Spotting times for the loading tools across the entire shift.

•

Rolling Average The average times for the loading tools across the last five cycles only.

•

Cumulative Duration The total time the loading tool spent in each state for the shift. Note: Only those loading tools which Cycles and KPIsummaries have determined have production numbers are displayed.

An example screenshot of each is shown below.

Shift Average


Page:27

Loading

Rolling Average

Cumulative Duration


Page:28

KPI Configuration Tool (Time Usage Model)

KPI Configuration Tool (Time Usage Model) This feature is designed for creating a time usage model for NEW sites, not for updating the model at existing sites. In the future the feature will be expanded to be available for the conversion of existing sites. As this feature has a direct impact on production recording it should be configured by MineStar deployment or support personnel only. From release 4.0, you are able to use the Time Usage Model page in the office software to build the model graphically and then export the model as a generated piece of XML, rather than directly modifying the KPI Summaries definition file. This can then be incorporated into and used by the CyclesKpiSummaries engine. The Time Usage Model page is an Expert Mode page, and once you are in Expert Mode can be found by clicking Contents > Platform > Time Usage Model Finder. The Time Usage Model Finder allows you to create new models, view and open existing models, and delete models. An example of the opening screen of the Time Usage Model Editor page is below.

•

The top left panel is the Model Hierarchy Editor, which shows the model as a tree view.

•

The top right panel is the Model Attributes Editor.

•

The bottom panel shows a graphical representation of the structure of the time usage model. This only updates when a node in the tree is selected.


Page:29

KPI Configuration Tool (Time Usage Model) For more information on the Time Usage Model Finder and Editor, refer to the Fleet User manual.


Page:30

Real-time KPI Persistence

Real-time KPI Persistence Release 4.0 has the ability to store real-time KPIs appropriately identified and created in KPI Summaries. These KPIs are written to the database on a periodic basis established by a parameter configured in Supervisor. The data is presented through a view, and available to third party software such as BusinessObjects Dashboards. In future versions, this will be used within the office software user interface.

Update KPI Summaries XML There is a new option available in the KPI Summaries.xml file for persisting KPIs. Below is an example of a real-time KPI in the KPI Summaries.xml file that has been configured for storage in the database.

Run makeDataStores makeDataStores must be run after inserting or modifying KPISummaries.xml with the new KPI Summaries entries. Running makeDataStores creates the necessary database tables and views to allow third party software to access real-time KPI's. Below is an example of a view that will allow access to the real-time KPI's. SQL> desc cycle_k_truckcycleinfo; Name

Null?

Type

PRIMARYMACHINEOID

NOT NULL

NUMBER

PRIMARYMACHINENAME

VARCHAR2(1020)

HOLESBYDRILLFORSHIFT

NUMBER

HOLESBYDRILLFORSHIFT_Q

NUMBER

HOLESBYDRILLFORSHIFT_U

VARCHAR2(4000)

HOLESPERHOURBYDRILLFORPERIOD

NUMBER

HOLESPERHOURBYDRILLFORPERIOD_Q

NUMBER

HOLESPERHOURBYDRILLFORPERIOD_U

VARCHAR2(4000)

FEETBYDRILLFORSHIFT

NUMBER

FEETBYDRILLFORSHIFT_Q

NUMBER

FEETBYDRILLFORSHIFT_U

VARCHAR2(4000)

FEETPERHOURBYDRILLFORPERIOD

NUMBER

FEETPERHOURBYDRILLFORPERIOD_Q

NUMBER

FEETPERHOURBYDRILLFORPERIOD_U

VARCHAR2(4000)

Review KPIGen.properties After makeDataStores is run, the KPIGen.properties file contains entries that can be used to update the KPI Summaries universe at the customer site to expose real-time KPI's for use in reports and


Page:31

Real-time KPI Persistence dashboards. Below is an example of realtime KPI's shown in the KPIGen.properties file. Class.Realtime\ Kpis={Description->"Contains the persisted realtime KPIs."; Show->Boolean(true)} Class.Realtime\ Kpis.DrillKpis={Description->"Holes and feet drilled per hour and per shift"; Show->Boolean(true)}

Update the Customer's KPI Summaries Universe Using a manual process, or tools such as ImportUniverse and MergeUniverse, the customer's KPI Summaries universe can be updated to reflect the contents of the KPIGen.properties file. Below is an example of DrillKpi's shown in the Universe.

Below is an example of the view structure that is shown in the universe.

Create Dashboards or Reports that access real-time KPIs After the KPI Summaries universe has been updated, reports and dashboards can now be implemented that expose the Realtime KPI's.


Page:32

Delays

Delays There are two new delay pages. •


•


The following pages have changed. They are either delay pages, or have a delay option on them. •

Delay Type Finder

•

Delay Type Editor

•

Site Monitor

•


Email notification of delays An email notification is now sent when a delay ends as well as when the delay starts.


Page:33


Delay Category Finder This page allows you to create,edit and delete delay categories. You can specify a name and color for the delay, and this is reflected immediately in the legend of Delay Monitor. Note: Any addition or deletion of Delay Categories impacts KPI summaries. Please liaise with your MineStar support personnel before making this type of change.


Page:34


Field Delay Type View Use Field Delay Type View to •

preview which delay type hierarchies are being sent to which machine classes in the field.

•

ensure that the delay types are being sent out to the machine in the correct order. Note: The Field Delay Type View page presents a snapshot of the delay type hierarchy at the time it is opened. The page does not update dynamically.

Field Delay Type View can be found by opening Delay Type Finder and clicking the Field View button.

The hierarchies displayed on the page should exactly match the hierarchy displayed on the on-board display of the machine of the associated class. Delay Types and Delay Type Groups are presented in the same order as they are in the Delay Type Finder. A Delay Type is displayed in the tree for that machine class when that machine class is selected on the Associations tab for the Delay Type in the Delay Type Editor. Any groups that are empty are removed from the hierarchy before being sent to the field.


Page:35

Delay Type Finder

Delay Type Finder In Delay Type Finder, delay groups and delay types are sorted in the order you leave them in, they are not sorted alphabetically. When you close Delay Type Finder and reopen it, everything displays in the order in which you left it. Use Field Delay Type View to check the ordering before the new delay configuration is sent to the field.


Page:36

Delay Type Editor

Delay Type Editor The Delay Type Editor has been modified to •

allow the selecting or clearing of the Available From Field

•

use the list of Delay Categories from the database.

Selecting Available From Field indicates that when the list of delay types is sent out to the machines, that delay type is included in the list for all types of machine it is associated with. Selecting and clearing this check box will change the results shown in Delay Type trees for the associated machine classes on the Field Delay Type View page.


Page:37

Site Monitor

Site Monitor You are now able to right-click destinations and road segments and put them on delay.


Page:38


Destination Assistant You are now able to right-click a destination in Destination Assistant and put it on delay using Delay Editor.


Page:39


Delay Work Order References The concept of work order references has been added to Delays. This enables you to enter a work order ID, which is a reference number to the Asset Management and/or Maintenance systems. Work order references are not mandatory, so you can leave the field unpopulated. The work order references are visible in reports TH030 and TM020.

Delay Editor When creating or editing a delay from the Delay Monitor or Delay Type Assistant, the Work Reference field is on the Duration tab in the Delay Editor, as shown in the screenshot below. You can enter the work order reference number for the delay in this field. Saving the delay stores the work order reference against the delay under the historical database schema.

Delay Splitter When splitting a delay, the work order reference from the delay being split is populated into both work order fields. Each field is attached to one of the two delays that the original delay is to be split into. You can change either, both, or neither of these fields. The work order field does not have to be populated.


Page:40


Merging Delays When merging two or more delays in Delay Assistant the Delay Merger screen displays as shown below. The Work Order Reference field displays as a drop-down list, which is pre-populated with any work order reference that was set on any of the original delays.

Note: If none of the delays to be merged have a work order reference set, the Work Order field will not be displayed at all.


Page:41

Delay Work Order References If a number of delays are being merged into a single delay, you can only set a single work order reference. You can select one of the already attached work order references from the drop-down list or you can type an entirely new work order reference in the text box beside the drop-down list. Note: When you enter a new work order reference into the text box, the drop-down box is disabled. Clicking Save attaches either the selected work order reference from the drop-down list, or the new work order reference in the text box to the merged delay.


Page:42

Delay Activities

Delay Activities Delay activities, also known as Maintenance Bay activities have been added to the Delay functionality in release 4.0, Delay activities can be configured and stored in the system for reporting purposes. The main purpose for delay activities is for the determination of Mean Time Between Failure (MTBF). For example, a delay of type Scheduled Down Time may have a delay activity class of Minor Service. Minor Service may have a number of associated delay activity types, for example, Change Oil, Change Coolant, Clear Air Filter etc. When you create a delay you can add a number of delay activities to the delay. Delay activities can have delay activity types that are valid for the delay activity class attached to the delay type.

Delay Activity Types Note: This functionality is restricted to Controller and Builder roles. New delay activity types are created by going to Contents > Production > Delay Activity Type Finder.

Clicking New or Open displays the Delay Activity Type Editor, where you can enter a Name, Description and Code. This then displays in the Delay Activity Type Finder.

Delay Activity Classes Note: This functionality is restricted to Controller and Builder roles. New delay activity classes are created by going to Contents > Production > Delay Activity Class Finder.

Clicking New or Open displays the Delay Activity Class Editor. An example screenshot with some delay activity types already entered is shown below.


Page:43

Delay Activities

This displays a list of ALL delay activity types that have been created, and selecting the Selected check box attaches the delay activity type to the delay activity class.

Attaching a Delay Activity Class to a Delay Type Delay types can optionally have delay activity classes associated with them. Only one delay activity class can be associated to a delay type. Open a delay type, and select the delay activity class as shown in the screenshot below.

Creating a Delay with Delay Activities Delays may or may not have delay activities associated with them. To add delay activities to a delay, the delay needs to have a delay type that has a delay activity class associated with it. Note: This functionality is restricted to Controller, Builder and Maintenance Engineer roles. You can create and modify delay activities in the Delay Editor, from either the Delay Assistant or Delay Monitor. On the Delay Editor, the Delay Activities tab is disabled until a delay type with an associated delay activity class is selected. An example is shown below, in the first screenshot the delay type Wait for Space


Page:44

Delay Activities does not have an associated delay activity, in the second screenshot the delay type Wait for Labour has a delay type call Minor Service associated with it. Note: The tab changes its name to that of the delay activity associated with it.

To add a new delay activity, click New, then click in the Activity column. A drop-down list provides the activity options to choose from. Double-click the Duration field and set the length of the delay in the popup dialog that displays. If you set the duration of the activity to be longer than the delay duration you are given a warning and asked if you wish to continue or not. You are also able to add a Work Order Reference number and a Description of the activity if necessary.

Splitting Delays with Delay Activities When splitting a delay with associated delay activities, the delay is split initially into equal halves on the nearest whole minute boundary and delay activity durations are not adjusted. Delay activities are duplicated in each of the split delays and can be added, removed or modified on the Delay Splitter dialog.

Merging Delays When merging delays the merge takes each delay activity where the delay activity type is equal and add the duration. If there is a delay activity of the same activity type in each of the delays to be merged the work order reference defaults to the work order of the delay activity in the first delay. If the work orders on each of the delay activities in each of the delays is different, they will display in the Work Order field in a drop-down list. You are then able to select one of the work orders to use. The descriptions for each delay activity of the same delay activity type are concatenated. If the delay type is changed for the merged delay, only the delay activities of types that are present in the delay activity class for the delay type are active for merging. All other delay activities are grayed out to indicate they will not be included in the merged delay.


Page:45

Delay Activities database changes

Delay Activities database changes Tables The following tables have been added to the MODEL schema. •

DELAY_ACTIVITY_CLASS

•

DELAY_ACTIVITY_CLASS_TYPES

•

DELAY_ACTIVITY_TYPE

The following tables have been modified in the MODEL schema. DELAYCLASS

The following tables have been added to the HISTORICAL schema. DELAY_ACTIVITY The following tables have been modified in the HISTORICAL schema. DELAY

The following views have been added to the HISTORICAL schema; V_DELAY_ ACTIVITY_CLASS V_DELAYACTIVITYTYPE VM_DELAYDELAYACTIVITES


Page:46

Safety Checklist

Safety Checklist The following improvements have been made to Safety Checklist Finder and Safety Checklist Editor in release 4.0. •

The column heading on Safety Checklist Finder has changed from Machine Categories to Machine Classes.

•

The tab name on Safety Checklist Editor has changed from Machine Categories to Machine Classes.

•

Selecting a category and clicking Apply or Save creates entries for the safety check item against all machine classes in that category.

•

When on the Machine Classes tab, you can hold down the Ctrl key and click on all of the machine classes you wish to apply the safety check item to.


Page:47

Safety Check Record

Safety Check Record The Page Configuration drop-down list has changed in release 4.0. You can now select All, Bad or Unactioned.

•

All

Displays all records regardless of whether they have a status of Good or Bad. Good results are displayed in green, Bad in red. •

Bad

Displays all records that have a status of Bad regardless of whether or not they have been actioned. Results are displayed in red. •

Unactioned

Displays all records that have a status of Bad and have yet to be actioned. Results are displayed in red.


Page:48

Shift Change

Shift Change This section documents numerous improvement made to Shift Change in release 4.0.


Page:49

Shift Change Finder

Shift Change Finder When creating or editing a shift change in Shift Change Finder, the General tab now allows you to specify messages relating to the created shift change.

Select the type of error message you wish to view. Click Display Message Types to display all message types. •

The Error check box is selected by default. When creating a new shift change there should not be any Error messages.

•

Selecting Warning or Information will display messages of that type. Each group of errors relates to the table on a particular tab, for example Loading Tools.

•

Each error row identifies the row number and column on the table of the particular tab in which the error occurs.

In the screenshot below, the Operator column on the Loading Tools tab has an warnings on rows 1, 2, 3 and 4.

•

Error messages display in red text.

•

Warning messages display in orange text (as shown above).

•

Information messages display in gray text.


Page:50

Shift Change Editor

Shift Change Editor There have been several improvements to Shift Change Editor. •

Setting a tie-down location load state.

•

Creating shift change tie-downs with penalty durations.

•

Allow no further assignments until tie-down has ended.


Page:51

Setting a tie-down load state

Setting a tie-down load state The load state of the truck on arrival at the tie-down destination is now set using the Destination Editor. 1.

You can either open the Destination Finder and select a destination, or double-click the Destination in the Destination column on the Tie-down tab that you wish to change the load state for.

2.

Select either Full, Empty, or Full or Empty.

3.

Click Save.

When Assignment performs the evaluations to assign a truck it will consider any scheduled assignments that are within range. All locations on that scheduled assignment are considered where the destination load state matches the current load state. For a scheduled assignment to have a valid station to assign the truck to, the truck load state must match at least one of the destination load states for the scheduled assignment. An example of this is shown in the tables below.

Destination A (Full Only)

Destination B (Empty Only)

Destination C (Full or Empty)

Truck 1 (Loaded)

OK

Not OK

OK

Truck 2 (Empty)

Not OK

OK

OK

Destination A (Full Only)

Destination B (Empty Only)

Destination C (Full or Empty)

Scheduled Assignment 1

Truck 1

A, B and C

A and C


Truck 1

A and B

A


Truck 1

B

None


Truck 2

A, B and C

B and C


Truck 2

A and B

B


Truck 2

A

None


Page:52

Creating shift change tie-downs with penalty durations

Creating shift change tie-downs with penalty durations You are now able to configure a penalty duration against the shift change tie-down location On the Shift Change Editor, the Tie-Downs tab has a Penalty column in the tie-down table, which allows you to configure a penalty duration, given normal circumstances, for an operator to travel from the tiedown station to the line out or dry room. The value should be an average duration. Penalty durations for a station are not mandatory, and can be left at zero.

Creating a tie-down penalty duration 1.

Click the Tie-down tab.

2.

Double-click the Penalty column for the relevant tie-down destination. A dialog displays with day, hour and minute duration field settings.

3.

Set the required duration and click OK.

4.

Double-click the Trucks cell for the destination you have just set the penalty on.

5.

Select the Trucks to apply the tie-down penalty to. The penalty duration selected shows in the Penalty Column for the relevant destination. The Count column displays the number of vehicles the penalty applies to. An example is shown in the screenshot below.

The penalty duration in the example above now defines that when the selected trucks are to tie-down at station FUELINT0 at shift change, the assignment engine must consider a penalty duration of 20 minutes, which corresponds to the travel time between FUELINT0 and the line out area. 6.

Select the Auto create Tie Down Assignments check box.

7.

Click Save. Scheduled Assignments are created as per usual.


Page:53

Creating shift change tie-downs with penalty durations 8.

Open Scheduled Assignments Finder. The Destinations column shows the additional penalty duration.

Note: Double-clicking a row with a destination tie-down penalty displays the Scheduled Assignment Editor. If you click the Browsebutton beside the Stationfield, you will notice that the pop-up dialog also contains the Penaltycolumn. You can double-click the Penalty column to change the penalty duration.

9.

Click Save to save your changes and close the page.


Page:54

How penalty durations are evaluated

How penalty durations are evaluated On the Scheduled Assignment Editor there are the following fields •

Required At

•

Arrive After

•

Arrive Before

Note: It is important to note that the scheduled assignment period window is for the scheduled assignment as a whole. Penalty durations greater than zero may be different for each destination or location defined in the scheduled assignment, for example, Workshop may have no penalty duration and FUELINT may have a 15 minute penalty. Assignment applies the penalty duration to these times at runtime when the assignment engine is determining which tie-down location to assign the trucks to. The diagram below shows how the scheduled assignment window is adjusted.

Assignment looks at the scheduled assignment for the truck and for each location in that scheduled assignment it applies any penalty duration to effectively shift the scheduled assignment’s window of


Page:55

How penalty durations are evaluated activity forward in time. Assignment then uses this time period to calculate the best assignment for the truck.


Page:56

Tie-Down Assignments

Tie-Down Assignments When a truck has an active scheduled assignment to travel to its tie-down station at shift change it will not receive any further assignments until the tie-down has ended. If the truck goes off-course during its travel to the tie-down station, it will not receive any further assignments. When the scheduled assignment for the shift change tie-down allocation becomes active, the machine operator receives the following message: “Current assignment is scheduled tie down. No further assignments for shift” to which the operator must respond “OK” to acknowledge the message. This is captured in the OFFICEMESSAGE historical table for future reference.


Page:57

Shift Change Allocations Monitor

Shift Change Allocations Monitor The Shift Change Allocations Monitor now has an On Delay column. This column displays Yes with the cell colored red if a machine is on delay, and No with the cell colored green if the machine is not on delay. This is shown in the screenshot below.


Page:58

Sending operator messages to multiple machines

Sending operator messages to multiple machines When in Fleet Update Assistant, Machine Finder and Site Monitor, you are now able to send operator messages to multiple Trucks, Loading Tools and Auxiliary Equipment by selecting contiguous or non-contiguous machines, and choosing Send Message from the right-click menu.


Page:59

Outbound office message timeout

Outbound office message timeout In Supervisor, Options > System Options > Pit Link there is a new Option Set called Outgoing Messages. On this page, the outbound office message timeout and retry is now configurable, with the default timeout before resend being set at 10 seconds, and the number of retries for sending the message has the default setting of 5 retries. An example of the page is shown below.


Page:60


Travel Progress Monitor In Travel Progress Monitor, the default display is to show the Loading Tools and Processors in alphabetical order.

You are now able to add priority servers which display in the order you set them, before all other servers. The priority servers are saved with the page configuration.


Page:61


The machines will display in the order you set them. If you filter by another fleet and the machines you selected are not in that fleet they will not display. However, they will remain as priority servers in the fleet you selected them from.


Page:62

Travel Progress Manager drag and drop

Travel Progress Manager drag and drop You are able to reassign a truck to a particular loading tool in Travel Progress Monitor, using the drag and drop functionality.

To reassign a truck to a loading tool using drag and drop 1.

Open Travel Progress Monitor.

2.

Click the truck you wish to assign to a different loading tool, drag it to that loader, and release the mouse button. The Truck Assistant for the dragged truck opens displaying the Assign tab. The loading tool is preselected, and displays in its compatibility color. Loading tools are colored based on their suitability.

3.

Click Assign to assign the truck to the loading tool.

.


Page:63


Travel Progress Monitor configure options The following changes have been made to the Configure Options dialog on Travel Progress Monitor.

Empty trucks Two new check boxes have been added to the Empty Trucks Tab in Travel Progress Monitor. The Loading Tool Annotations panel now has the Coverage and Productivity check boxes. Selecting these check boxes will display the Coverage and Productivity statistics with the Loading Tools on Travel Progress Monitor.

Loaded trucks Two new check boxes have been added to the Loaded Trucks Tab in Travel Progress Monitor. The Processor Annotations panel now has the Productivity and Destination check boxes. Selecting these check boxes will display the Productivity and Destination statistics with the Processors on Travel Progress Monitor.


Page:64


Station trucks Station trucks is a new tab, displaying a reduced set of the same options as the other tabs as shown below.


Page:65

Personnel Editor

Personnel Editor On the Personnel Editor, the Licenses in the License drop-down box are now sorted alphabetically, and then alphabetically / numerically by class. For example, in the screenshot below, Truck comes after Shovel, and within Truck, the 793s are before 797s, and Cs are before Ds.


Page:66

Site Editor - Rollback option for Surface

Site Editor - Rollback option for Surface The office software now keeps track of the last ten changes to the Surface. This gives you the ability to quickly revert to an earlier version of the Surface file from within Site Editor. When the Upload all DXF files to the Surface option is run from the Actions > Background Files window, or by clicking on the toolbar, the current Surface is automatically backed up, and the backup file is timestamped with the current date and time, e.g. Surface_2012_11_21_095656_411.dxf - Wed Nov 21 09:56:36 EST 2012 Each additional change is appended to the list, up to a maximum of ten changes. When this limit is reached, the oldest file in the list is deleted when the next change is uploaded. To revert to an earlier version of the Surface, select the Load backup surface option from the Background Files window, then click OK.

A list of the available backups is displayed.


Page:67

Site Editor - Rollback option for Surface Select the backup you want to load, then click OK.

The current backgrounds in Site Editor are replaced by the selected file. To use this data as the new Surface, open the Background Files window again, select Upload all DXF files to the Surface and click OK. The previous Surface will be backed up, and the file you have loaded will be set as the new Surface.


Page:68

Sending Scheduled Assignments

Sending Scheduled Assignments When in Fleet Update Assistant and Site Monitor, you are now able to send scheduled assignments to multiple Trucks by selecting contiguous or non-contiguous machines, and choosing Schedule Assignment from the right-click menu.


Page:69

Deleting Scheduled Assignments

Deleting Scheduled Assignments You are now able to delete scheduled assignments from Scheduled Assignment Monitor, by selecting single, contiguous or non-contiguous assignments and clicking Delete.


Page:70

Dragline Operational Statistics

Dragline Operational Statistics In release 4.0 the following features have been added for Draglines. Cycles Dragline operational states, e.g. Walking, Digging and Power Off, are used to generate Dragline Cycles. Dragline Cycles can be viewed, merged, split and edited. Delays Draglines may be placed on delay. Dragline delays can be viewed, merged, split and edited.


Page:71

Machine Class Capabilities

Machine Class Capabilities On the Capabilities tab of Machine Editor pages, the Use Class Capabilities option has been added.

When you select this option, the capabilities of the machine's class are inherited by the machine, in this case the truck. Once you have selected the Use Class Capabilities check box, the Capabilities check box is grayed out so you cannot select specific capabilities for the machine. You can clear the check box to enable the different capabilities for the machine.


Page:72

Machine Class Editor

Machine Class Editor On the Machine Class Editor, for each machine class that displays the Machine Type tab , there is now a Machine Type drop-down list at the top of the page under the Description field, which allows you to select the type of machine. Once a machine type is selected the Operator Interface field on the Onboard tab will be populated. Note: This field was previously called the Category drop-down list on the General tab.


Page:73

Destination Chooser

Destination Chooser Clicking the Destination field on a Machine Assistant page, e.g. Loading Tool Assistant, or Machine Editor page, e.g. Loader Editor, now displays the Destination Chooser, which allows you to filter, search for, and select a destination.

Destinations are color-coded as follows. Blue - within 500m of the machine. See Supervisor, Options > System Options > Machine Tracking > Destinations to change the default distance. Green - compatible destination. Orange - have a material or destination type combustibility issue. Red - not connected to the network. If your site has a lot of destinations, you can click in the Type field and select a Filter to reduce the list.

Select one of •

Combined Source, Sink and Station

•

Combined Source and Sink

•

Combined Source and Station

•

Sources

•

Stations

depending on which Assistant or Editor you have open. Cat® Fleet / Cat® Health 4.0 Release Notes

Page:74

Destination Chooser You can also find a destination by starting to type the name of a destination in the Search field. The panel underneath the field dynamically updates as you type. The Destination Chooser can also be found on the Mining Block Editor when selecting a Stockpile or a Locked Destination. The Chooser is the same as for machines, except that the filter options are as follows •

Combined Source, Sink and Station.

•

Combined Source and Sink.

•

Sinks. This option does not apply to Stockpiles.


Page:75

Cycle Editor

Cycle Editor When viewing the Cycle Editor screen for an auxiliary or truck cycle, the office software now shows the truck activity, and that it is traveling on an unknown road if the machine loses the GPS signal, rather than leaving the columns blank. This makes it easier for you to correct the cycles. Also, the Start Waypoint and End Waypoint columns have been renamed Start Position and End Position.

Cycle Editor in release 4.0

Cycle Editor in previous releases


Page:76

Daylight Saving Timezones

Daylight Saving Timezones In Supervisor, when setting a time zone which has daylight savings time, colored boxes display beside any time fields in the office software, e.g. on Delay Assistant, Cycle Assistant, to indicate that the time is displaying in Daylight Savings Time.


Page:77


On-board hardware configuration From release 4.0, the way a machine’s on-board hardware is configured in the office software has changed. In earlier releases, on-board hardware was configured by choosing the corresponding on-board platform. These platforms could represent the application of the machine, software and hardware combination, software and version or related capability set. Furthermore, it was only the Detect-only based machines which could be configured to have camera and radars. From release 4.0, the machine's on-board system is selected by choosing from the list of relevant operator interfaces and add-ons, then specifying the custom configuration.

Operator interface An operator interface is the physical on-board hardware that is installed on the machine, including •

CMPD

•

Navigator

•

G610

•

Autonomous

•

PC

The operator interfaces available for a machine are based on the office software license, and machine category, e.g. Haul Truck, Scraper, Shovel, etc of the machine’s class.

Add-on and custom components Add-ons represent other physical components, for example •

Cameras

•

Radars

•

Proximity Awareness

that can work with a particular operator interface. The custom configuration and add-ons available are also based on the office software license and machine category of the machine’s class and the operator interface selected.

Example Office software which is licensed for Fleet and Detect, allows a Haul Truck to have No (None), or a CMPD operator interface. If CMPD is selected as the operator interface, then the available add-ons are Camera, Radars and Proximity. The custom configurations options are VIMS, TPMS, GPS or Detect.


Page:78


As part of the upgrade process from release 3.x to release 4.0, the office software migrates existing configurations to the new approach. Any configurations that could not be migrated are highlighted in the log files and in the Mine Model Query. Typically, machines that could not be migrated have inappropriate configurations or the machine category is not correct for the actual machine type, or the onboard is no longer supported.

Impact of the changes •

Machines with inappropriate configurations will no longer work. For example, a Haul Truck which was configured with a Scraper custom configuration will no longer work.

•

The version of the software that runs on an on-board system can no longer be specified. •

Terrain for Grading and Loading 4.0 is no longer supported and should be upgraded to the latest version of the software.

•

Fleet on CMPD2 is no longer supported and should be upgraded to the latest version of the software

•

Terrain Fuel and Lube is no longer supported

•

CD550 is no longer an available option and is not supported

•

It is expected that the on-board software should be the latest aligned version or the previous stable version.

•

Machines configured in the office software with the CMPD operator interface can only be (re-)flashed with the latest software.


Page:79

On-board hardware configuration On-board Software

Versions Supported

Tope

3.1, 3.1.1, 3.2

Terrain for Grading and Loading

4.1, 4.2, 5.0

Terrain for Drilling and Draglines

6.8, 6.9, 7.0

CD550

No longer supported

For step-by-step instructions for configuring a machine, refer to the Fleet User manual.


Page:80

Mining Blocks: Archive Page configuration

Mining Blocks: Archive Page configuration A new Page Configuration called Archive has been added to the Mining Block Finder page. To view the archive page configuration 1.

Open Mining Block Finder.

2.

Select the Page Configuration drop-down list and select Archive.

When this is selected the Mining Block Finder page shows all mining blocks that can be archived, i.e. they are inactive. Only inactive mining blocks can be archived. Inactive blocks display as a red icon. The columns on Mining Block Finder can be ordered in ascending or descending order, so you can see if the mining block is suitable for archiving. You are able to select multiple rows for archiving.


Page:81

Assignment Options U-Turn policy

Assignment Options U-Turn policy In Supervisor, Contents > Setup > Assignment Options, on the Assignment Behaviour tab, when selecting the Never turn-around policy you should be aware that if the truck goes off course, or encounters a Re-assign waypoint, iAssignment recalculates the assignment without considering the prior path traveled and concludes that the truck has turned around. You should limit the use of Re-assign waypoints to those areas where the trucks are able to turn around.


Page:82

Data Share

Data Share Data Share provides you with an open interface for integration with your other mining information systems. Closely integrated systems remove the need for duplicate data entry and allow business processes to span systems and provide greater value to your operations. The interface is built on open industry standard protocols (i.e. JSON data interchange, over REST web services), and integration can be achieved by using off-the-shelf components. As such there are no proprietary libraries or program files to integrate, reducing development costs and time to deploy. Using the Data Share, systems external to the office software can send and receive data about operators, machine location, machine activities and materials as well as share text messages. For example, business processes implemented in fleet management systems (FMS), enterprise resource planning (ERP) and corporate reporting systems can commonly benefit through integration with high precision guidance and control processes implemented by the office software. The new functionality added to this release includes: •

the ability to integrate your existing HR systems with Operator Management within the office software.

•

the ability to integrate third party fuel management systems with Fuel Management within the office software.

For more information on Data Share, contact your Cat Implementation and Deployment teams.


Page:83


Synchronizing Fleet and Terrain Data When running both Fleet and Terrain you are able to synchronize the following entities. •

Job Codes

•

Operators

•

Delay Codes

•

Machines

The tables below show which information will be synchronized for each of the entities as listed in the code.

Job Codes Fleet

Terrain

Name

Name

ID

ID

Job Code Group

JobCodeGroup

Operators Fleet

Terrain

Archived

Archived

MacPassword

Password

Name

Name

OID

ID

Delay Codes Fleet

Terrain

Archived

Archived

Duration

DefaultDuration

ID

ID

Name

Name


Page:84


Machines Currently only the four machines classes shown below are common between Fleet and Terrain, therefore these are the only ones you can synchronize. Fleet

Terrain

Loader Classes

Wheel Loader

Surface Miner Classes

Surface Miner

Dozer Unit

Wheel Dozer

Grader Unit

Motor Grader

You must enable synchronization on both Fleet and Terrain.

Data synchronization preparation While the synchronization functionality will update records between the systems, it is not intended to handle initial merging of data between the systems. Mine sites want to maintain consistent IDs between the Fleet and Terrain systems. To ensure that the synchronization process enforces this consistency with new records, a manual reconciliation between code, operator and machine IDs across the two systems should be performed before synchronization is enabled. If this is not performed, the synchronization process may merge the existing data in unexpected ways. By performing this manual step of ensuring the ids are correct in each system, the synchronization process will run smoother and more reliably.

Enabling data synchronization on Fleet You should not enable these check boxes unless you are running Terrrain v1.3 or later. Fleet has two check boxes in Supervisor which must be selected to enable or disable data synchronization, Initial Sync and Live Sync. To enable data synchronization, do the following. 1.

Navigate to Options > System Options > Platform > System.

2.

Click the Server tab, then click the Middleware button.

3.

Select Initial Sync and/or Live Sync.


Page:85


Selecting Initial Sync then starting the client will pass the information for the entities mentioned above from Fleet to Terrain, and Terrain will then pass its information to Fleet. This process will occur every time you start Fleet if data has not been synchronized before. If you select Live Sync, Fleet and Terrain automatically synchronize any changes you make to any of the four entities. Only the change made will be re-synched. Note: If you change either check box, e.g. you clear Live Sync, you must restart Fleet to activate the change.

Machine associations Both the Delay Type Editor and Job Code Editor have an Associations tab, associating machines with delay and job codes. Only the four machine classes mentioned earlier are able to have their delay and job code information synchronized.


Page:86

Platform

Platform This section provides information on new and changed platforms used in conjunction with release 4.0.


Page:87

Java

Java The office software operates with Java 1.6, and will install a copy for its own use. If you are installing another version of Java, it must be compatible with the office software requirements. Check the Java_ Home directory to see which version you are running. The office software, as currently configured, does not support Java 1.7, and it should not be installed, used or configured.


Page:88

Memory sizes

Memory sizes JVM heap size settings can now be set using Supervisor. The Available options are SMALL, MEDIUM and LARGE. •

SMALL is for demonstration or test systems only, and should not be used for production.

•

MEDIUM requires a machine with a minimum of 16 GB memory, and may be a suitable initial configuration for a medium mine site.

•

LARGE requires a machine with a minimum of 24 GB memory, and may be a suitable initial configuration for a large mine site. Note: As requirements and JVM needs vary considerably between sites, the Implementation and Deployment teams should review and adjust the JVM heap configuration according to their current best practices and knowledge. The Supervisor configuration is provided as a convenience to set an initial coarse configuration.

Any additional site-specific adjustments to the JVM heap sizes should be via editing the files in the MSTAR_CONFIG\catalogs directory.


Page:89

GeoServer

GeoServer From release 4.0, all capability sets make use of a GIS Server. A GIS Server allows users to share GIS resources and provide Google Maps style capability. The GIS Server distributed with the office software is GeoServer version 2.2.2 at the time of writing. GeoServer is installed and configured automatically as part of the office software install, and creates a service called “M*GeoServer”.


Page:90

Web Client

Web Client For release 4.0, a new client is available through the web browser.

The key features of the new client include: •

Pre-defined and custom Desktops.

•

Workflow-orientated tasks.

•

Save as Draft option.

•

Smart Search.

•

Notifications.

•

Zero install.

•

Improved user experience and styling.

•

Online Help.

The available functionality is based on the license you have. For further detail on the individual features please refer to the relevant User manual. For Fleet the new functionality includes: • The ability to install the Remote Foreman's Terminal. • Travel Progress Monitor. • Site Map. • Dashboards. For new Health functionality see the Health section.


Page:91

Web Client The web client can be accessed at http://:8080/minestar/ using Internet Explorer 8 or greater with Flash 11 or greater. To ensure there are no issues with Window security, it is recommended the web client is added to the safe web site list. You can do this by doing the following (based on Windows 7). 1.

Start > Control Panel.

2.

Click Internet Options.

3.

Select the Security tab.

4.

Click Local Intranet.

5.

Click Sites. •

If the option to add the website is not available then Click Advance.

6.

Type the web client address.

7.

Click Add.

8.

Click Close.


Page:92

BusinessObjects 4.0

BusinessObjects 4.0 Note: From release 4.0, only BusinessObjects 4.0 is supported. The following sections highlight the changes and new features in BusinessObjects 4.0. Refer to the Fleet Install manual for more detailed information. For SAP documentation, please refer to http://help.sap.com/bobip40


Page:93

Knowledge Network

Knowledge Network The Knowledge Network is a resource for sharing the following BusinessObjects-related topics between Caterpillar Employees and Dealers. We encourage you to subscribe to this site to receive updates. https://kn.cat.com/cat.cfm?id=15440 1.

PDFs of Standard Reports and report specification documents

2.

Custom reports which Customers/Dealers want to share

3.

Tips, tricks, tools, discussions

4.

Success stories

5.

Training materials (including AVI files)

6.

Report Review Committee presentations and meeting minutes


Page:94

Hardware Requirements

Hardware Requirements The BOXI 4.0 architecture is substantially different and requires more memory. In addition, the way that BusinessObjects and MineStar interact leads us to recommend the following server hardware requirements. •

Minimum Server Hardware Requirements (Updated) 4 x 2.0 GHz Core CPU 16 GB RAM minimum / recommended 32 GB. If you are a Dealer you may wish to add more RAM. Note: Sizing Companion for SAP BusinessObjects Business Intelligence (BI) 4.0 states: “In terms of typical hardware in an enterprise scale deployment of BI 4.0, a node in a BI 4.0 cluster would typically be an 8 core machine with 16GB minimum or equivalent.”

•

Minimum Client Hardware Requirements: 2.0 GHz Core CPU 2 GB RAM Note: Compiled binaries of SAP BusinessObjects BI software is supported on versions of the Windows operating system running on CPUs made by AMD or Intel

Recommended Disk Space Requirements SAP BusinessObjects BI (client installer): • 14 GB for default installation with all languages installed With the removal of Desktop Intelligence from the BusinessObjects 4.0 reporting suite, there is a greater reliance on Java plugins, which require a reasonable level of available RAM to operate with. Note: For full Fleet hardware requirements, please refer to the Fleet 4.0 Compatibility Matrix.


Page:95

KPISUM universe

KPISUM universe Please note that the KPISUM universe in the standard BIAR file is a reference implementation universe only. There are several changes in the following sections which you will want to update in your customized KPISUM_XXX universe.


Page:96

Universe split for VIMS

Universe split for VIMS Due to performance issues in BOXI 4.0, the objects required for VIMS reporting have been split out into a separate VIMS universe. This universe is available as a patch in Fleet 3.1 and Fleet 3.1.1. Custom reports should be repointed in 3.1.1 to the new VIMS universe prior to upgrading to BOXI 4.0 as there is a known issue in BOXI 4.0 which prevents this.


Page:97

Support SQL Server

Support SQL Server MineStar 4.0 and BusinessObjects XI 4.0 are soon to support SQL Server. Note that Oracle and SQL server work differently when it comes to Daylight Savings Time (DST). For example, the function displayLocalTime() in Oracle does not work in SQL Server. SQL Server has a function DisplayUTCTime() which can be used. Custom functions required a universe change where objects were prefixed with “dbo.” e.g. dbo.validDate and dbo.interpolatedSMU


Page:98

Coordinated Universal Time (UTC)

Coordinated Universal Time (UTC) UTC dates have been incorporated into the MineStar database and BusinessObjects. Time zones around the world are expressed as a positive or negative offset from UTC. UTC time does not change with the seasons e.g. for Daylight savings. It is recommended that you build reports using UTC time variables instead of local time. There are 405 new UTC objects in the MSTARGE3 universe and 20 in the KPISUM reference universe. The prompts have also been updated for UTC time, and all standard reports. Note: Your KPISUM_XXX universe will need to be updated as well as all your custom reports. For BO reporting to work, the query against the database should be based on UTC variables, while the data displayed in the report should reflect the local time equivalent. Below is an example of the one-off changes needed to the “where” clause of every query.

Remove these prompts

SQL of the prompt WHERE ( CYCLE_S_FACT_MAIN.ENDTIME > (select dbo.displayutctime(dbo.shift_OR_date(@Prompt('1) Shift Begin:','C','PromptsShifts\ShiftName',mono,free) ,'STARTTIME')) from v_dual) AND CYCLE_S_FACT_MAIN.ENDTIME <= (select dbo.displayutctime(dbo.shift_OR_date(@Prompt('2) Shift End:','C','PromptsShifts\ShiftName',mono,free) ,'ENDTIME')) from v_dual) )

Replace with the UTC equivalent object

SQL of the prompt WHERE


Page:99

Coordinated Universal Time (UTC) ( CYCLE_S_FACT_MAIN.ENDTIME_UTC > (select dbo.displayutctime(dbo.shift_OR_date(@Prompt ('1) Shift Begin:','C','PromptsShifts\ShiftName',mono,free) ,'STARTTIME')) from v_dual) AND CYCLE_S_FACT_MAIN.ENDTIME_UTC <= (select dbo.displayutctime(dbo.shift_OR_date(@Prompt ('2) Shift End:','C','PromptsShifts\ShiftName',mono,free) ,'ENDTIME')) from v_dual) ) Refer to Coordinated Time (UTC) in the BO XI 4.0 chapter of the Fleet Install manual for more information.


Page:100

Changed Reports

Changed Reports General changes affecting all reports The following changes affect all reports. •

All remaining Health reports have been converted from Deski to Webi.

•

All reports are now "translation ready", where the variable GetLocalised() is wrapped around strings so that they can be recognized by the translation tool as being a textual string to be translated. At the time of release no translations have been exported to the repository. This is phase two of the project.

•

Standard reports have been updated for UTC.

•

Reports with an "&" in their title have been renamed as they cause errors in BOXI 4.0.

•

Using MACHINE_N or PRIMARYMACHINE_N in the query condition of the report causes performance degradation. Therefore, you should replace the name object with MachineOID in your Custom reports to improve performance.

Specific report changes HE001p-Health Events Application improvements to “Worst Value” allows better reporting of this in BusinessObjects to match VIMS PC. In addition two objects were added; “Worst Value Unit” and “Worst Value Description”.

HE002p-All Events Application improvements to “Worst Value” allows better reporting of this in BusinessObjects to match VIMS PC. In addition two objects were added; “Worst Value Unit” and “Worst Value Description”.

HE003p-Health Events for Levels 2, 3 Application improvements to “Worst Value” allows better reporting of this in BusinessObjects to match VIMS PC. In addition two objects were added; “Worst Value Unit” and “Worst Value Description”.

HE009p-Trend Summary Report Context updates to include objects and so that data is not aggregated e.g. ValidSampleSum= Sum((If IsNull() Then ) In ( , , , , ,,))


Page:101

Changed Reports

HE010p-Trends-By Machine-Detail Context updates to include objects and so that data is not aggregated.

HE010d-TKPH Trends-By Machine-Detail Context updates to include objects and so that data is not aggregated. Wildcard query conditions based on legacy VIMS values. Equivalent IDs were obtained for VIMS 3G and added to the queries.

HE037d-Brake Trends, Truck-Detail Wildcard query conditions based on legacy VIMS values. Equivalent IDs were obtained for VIMS 3G and added to the queries.


Page:102

New Reports

New Reports Validation •

VD001_validateTruckCycles

•

VD002_validateShovelCycles

•

VD003_validateAuxCycles

System Health SH001p-GWM Duplicates Information Shift This report helps the proactive monitoring of average duplicate record message count and percentage for each shift.

SH002d-OnBoard Hardware File version Information This report helps the proactive monitoring of the On-board hardware file version information for each shift.

SH003d-Service Restart Information This report helps the proactive monitoring of service restart information for each shift.

Health •

HE004-VIMS Version and Port Numbers

Template Historical •

TH150-Shift Change Allocation


Page:103

Changed Objects comparison

Changed Objects comparison The following spreadsheets list the changed options between Fleet 3.1.1 and Fleet 4.0, and should be included with these release notes. If they are not, please contact your Caterpillar support representative. KPISUM 4.0 vs 3.1.1 MSTARGE 4.0 vs 3.1.1 VIMS 4.0 vs MSTARGE 3.1.1


Page:104

Real-time KPIs

Real-time KPIs Real-time KPIs provide functionality for you to define and capture KPI data to be monitored and analyzed in real time. They are defined in xml files in MineStar, which allows the data to be persisted to the database and used in BusinessObjects or other third party dashboards. The real-time KPIs are updated every few seconds, allowing you to monitor your mine in real time. Refer to the Fleet Install manual for more information.


Page:105

BORefresh end of life

BORefresh end of life The BORefresh tool is now end of life. Refer to Deprecated Features and Functionality for more information.


Page:106

Command for hauling Reference Implementation BIAR

Command for hauling Reference Implementation BIAR For Command for hauling sites, there is a Reference Implementation BIAR on the Knowledge Network which is available for downloading. While it splits out data by Manual and Autonomous categories, manned sites could still use these reports if they wish and they will only see the manned results. The BIAR contains the following reports. •

AHS-01-Availability and Utilisation

•

AHS-02-Daily Report

•

AHS-03-Delays by Category

•

AHS-04-Error Check

•

AHS-05-Loader Performance

•

AHS-06-Management Report - Weekly

•

AHS-07-Production Cycle Breakdown - detail and delays

•

AHS-08-Production Cycle Breakdown - detail

•

AHS-09-Production Cycle Breakdown

•

AHS-10-Tons by Destination

•

AHS-11-Rise and Fall

•

AHS-12-Cycle Performance Management

•

AHS-13-Shift Lead Delay Report

•

AHS-14-Shift Summary

•

AHS-15-Operator Summary

•

AHS-16-Obstacle Clear

•

AHS-17-Time Elapsed to first Dump


Page:107

Oracle RMAN

Oracle RMAN Oracle Recovery Manager allows you to backup and recover your Oracle databases, and has the ability to •

perform incremental backups.

•

back up the control file and the SPFILE.

•

enforce the retention policy for archive redo log files.

•

report the files needed for the backup

•

restart the failed backup from the point of failure, without starting from the beginning. This is much faster, when compared with other traditional backup strategies.

The process for implementing Oracle RMAN has been added into the Install manual as an appendix.


Page:108

Third Party tool changes

Third Party tool changes The following section describes third party tool changes in release 4.0.


Page:109

Windows Task Scheduler

Windows Task Scheduler Note: From release 4.0, Splinterware System Scheduler has been removed and replaced with Windows Task Scheduler. Windows Task Scheduler is used to control the scheduled tasks that help maintain Fleet functions, and perform routine housekeeping tasks. Windows Task Scheduler provides the same features as Splinterware System Scheduler to enable you to schedule tasks, and the ability to enable, disable and reschedule scheduled tasks. Refer to the Fleet Install manual for more information and details on configuring Windows Task Scheduler.


Page:110

FTP Server

FTP Server Transferring VIMS report files to the office software for new-generation VIMS units requires a local FTP server for the files to be transferred to. The transfer type is also optionally available on the latest HIM versions. See the Fleet install manual for detailed installation steps. Refer to the VIMS compatibility matrix for machines with VIMS 3G.


Page:111

Installing Microsoft SQL Server 2008 R2 on Windows Server 2008 R2

Installing Microsoft SQL Server 2008 R2 on Windows Server 2008 R2 Note: SQL server is for new installs only. You cannot upgrade from Oracle to SQL Server. Release 4.0 provides limited support for SQL Server 2008 R2 as the system database. The following limitations apply. •

The SQL Server cannot be set up remotely, that is, the mstarrun commands checkDataStores, createDataStores and makeDataStores must be run locally on the database server machine.

•

The matarrun commands for database import and export may require the installation of third-party tools.

•

The GeoServer feature of the office software (installed with the office software installer) only works with the office software’s coordinate system when in an SQL Server-only installation. You cannot use custom coordinate systems. The impact of this is that images imported into the office software need to be in the local coordinate system not in another coordinate system. Furthermore, any integration with third party systems should use the local coordinate system.

Other points to note •

The mstarFiles folder on the database server should be shared over the network, with read and write access to the network users.

•

The SQL Server windows service should be run using a domain account which has read and write access to the MineStar shared folder over the network and admin access in the database windows server.

The process for installing Microsoft SQL Server 2008 R2 on Windows Server 2008 R2 has been added into the Install manual as an appendix.


Page:112

Running Fleet on SQL Server

Running Fleet on SQL Server The process for setting up Fleet to run using SQL Server has been added as an Appendix to the Install manual.


Page:113

VM Snapshot - Known Issue

VM Snapshot - Known Issue If you are using VMs and running VM snapshots, there is a known issue with running the VM snapshots which may cause a lack of functionality within the system. You should disable the VM snapshot functionality.


Page:114

Installation

Installation The following sections describe changes to, and requirements for, the install process.


Page:115

Installation procedure

Installation procedure Caterpillar recommends backing up the data from your current model before upgrading. Refer to the Fleet Administration manual for backup instructions.

Upgrading from release 3.x to release 4.x Upgrading from release 3.x to release 4.x requires a full uninstall and install. This ensures all the services and dependencies are installed correctly 1.

Uninstall the existing version of the office software.

2.

Uninstall GeoServer if installed.

Note: Step 2 is only applicable for systems with a Detect license, or those running the pre-release version of the Remote Foreman's Terminal. 3.

Restart the Application Server

4.

Install the office software. See the Fleet Install manual.

5.

Open Supervisor as an Administrator.

6.

Select Contents> Setup> Setup Tools.

7.

Select makeDataStores.

8.

Click Advanced Options.

9.

On the Schema tab select Major Upgrade.

10. Click Run.

Note: This process may take more than ten minutes to complete. 11. To make use of GeoServer, you need to configure the following setting in Supervisor. See the Fleet Administration & Configuration manual for more information. •

Mine Boundaries. Options> System Options> Machine Tracking> Mine Boundaries.

Optionally, you can also configure the following setting. See the Fleet Administration & Configuration manual for more information. •

GPS Coordinate Transform. Options> System Options> Pit Link > GPS Coordinate Transform. Then select the Enable coordinate transformations check box, and select the appropriate CRS definition. This is set to UTM by default.

12. In Supervisor, select Content> Setup> Setup Tools> publishCoordinateSystem.


Page:116

Installation procedure 13. Click Run. 14. Once the process is complete, restart the M*GeoServer service. 15. Ensure the GeoServer service is running. 16. Select makeSpatialStores.

Systems migrating from release 3.1.1 with a Detect license or a pre-release version of Remote Foreman's Terminal, should select "Update existing spatial stores". 17. Click Run. 18. Restart the M*MineTracking Service.

Note: The mine model is synched with GeoServer when the M*MineTracking service starts.

Upgrade path for minor releases As of release 3.1.1, minor releases can be upgraded using the Zip Upgrade Process.

Exception running makeSpatialStores If you receive an error running makeSpatialStores, refer to Troubleshooting GeoServer.


Page:117

Zip upgrade installation

Zip upgrade installation If you are upgrading from MineStar 3.x to 4.0 you must follow the installation procedure for upgrading from the installer. The Zip Upgrade option is only applicable if you have already installed MineStar 4.0.

Zip upgrade release artifacts You need the following files to perform the upgrade. •

Zip upgrade file •

•

mstarx-xx-x.zip

Web deployment files •

minestar.war

•

minestar-rest.war

Zip upgrade steps This section describes how to perform the zip upgrade. 1.

Stop the MineStar services.

2.

Copy mstarx-.xx-x.zip into the directory mstarFiles\systems\main\updates\builds.

3.

Open Supervisor as an Administrator.

4.

Select Contents> Management> Software Updates.

5.

Select the Builds tab.

6.

Change the Current Build to match the release. The build should follow the format mstarx-xx-x. For example, the MineStar 4.0 M4-3 build will be 4.0-M4-3.

7.

Click Apply.

8.

Click Yes to confirm you want to update.

9.

If you have installed patches for the previous build, you will be asked to decide if you want to keep these patches when you install the new build. By default, patches are removed when a new build is installed. If you want to keep a particular patch, select it from the Uninstall list and use the arrows to move it to the Keep list, then click OK to confirm your selection.

10. After the task has run, click OK. Supervisor closes. 11. Open Supervisor again as Administrator.


Page:118

Zip upgrade installation 12. Select Contents > Management > Software Updates. 13. Click Make System. 14. After the task has run, click Close. 15. Select Contents > Setup > Setup Tools. 16. Select makeDataStores. 17. Click Run.

Note: This process may take more than ten minutes to complete. 18. Start the M*Geoserver service. 19. Select makeSpatialStores and click Update existing spatial stores. 20. Click Run. 21. When the process has finished, click Close. 22. Close Supervisor. 23. Copy the MineStar web deployment files to mstar\jetty\webapps. 24. Start the MineStar services. The software has now been updated to the latest version. Note: The desktop icons for MineStar and Supervisor do NOT get updated in this process. You need to update them from the new \mstarFiles folder.

Exception running makeSpatialStores If you receive an error running makeSpatialStores, refer to Troubleshooting GeoServer.


Page:119

Troubleshooting GeoServer

Troubleshooting GeoServer Users and office software administrators should NOT need to access GeoServer. For troubleshooting purposes, the office software instance of GeoServer can be accessed by doing the following. 1.

Open a web browser.

2.

Go to http://:7070/geoserver/

3.

Enter the username and password. i.

The default username is “admin”.

ii.

The default password is “m*geoserver”.

Note: For systems migrating from 3.1.1 with a Detect license or a pre-release version of the Remote Foreman's Terminal, the default password is “geoserver”. 4.

Once logged in, the MineStar Stores, Layers and Layer Groups can be accessed.

Exception error when running makeSpatialStores If you receive an exception error when running makeSpatialStores, follow the procedure below to resolve the issue. 1.

Log in to GeoServer as per the procedure above.

2.

Click the Work Space link.

3.

Click the MINESTAR work space link.

4.

Review the MINESTAR work space detail (Services WCS, WFS and WMS only).

5.

Go back to the Work Space link.

6.

Select the MINESTAR work space check box, and click Remove selected workspace(s). A dialog displays displaying the objects in the work space you are about to delete.

7.

Click Ok to delete the objects.

8.

Click Logout.

9.

Stop the GeoServer service in Task Manager.

10. Open Supervisor, if it is not already open.


Page:120

Troubleshooting GeoServer 11. Click Contents > Setup > Setup Tools. 12. Click publishCoordinateSystem, and click Run. 13. Start the GeoServer service in Task Manager. 14. In Supervisor, run makeSpatialStores. 15. Close Supervisor.


Page:121

Configuring Windows Auto Updates

Configuring Windows Auto Updates Having Windows download and install updates automatically can cause an unscheduled server restart. The MineStar Champion should discuss this with the local IT support team and negotiate a suitable outage window for updates (and restarts) to be scheduled in. This way the MineStar services can be stopped in a controlled manner before the server restart occurs.


Page:122

Oracle Database 11g Express Edition

Oracle Database 11g Express Edition The Oracle Database 11gExpress Edition (Oracle Database XE) installation option is now available for Health, Pit Link (Health install option), Detect and Fleet for Underground. See the respective Install manuals for detailed installation considerations. Note: Oracle Database XE is a free product that does not require licensing. However, it is constrained in performance and data size. Therefore, release 4.0 can only support installations with low performance requirements and small data quantity. Furthermore, the data storage of the database must be located on a high performance I/O device. Oracle strongly advises against network share drives, compressed or virtualized partitions for database storage. See the Compatibility Matrix document for more information on application sizing and performance guides.


Page:123

Health install and Licensing options

Health install and Licensing options To align Health with the other Cat® MineStar™ System capability sets, release 4.0 introduces new Install and Licensing options. These include the following, PitLink The PitLink install is aimed at remote customer sites, and facilitates download and on-forwarding of VIMS files. This install option leverages Oracle Express and Corporate Data Management Basic Health Basic Health is a low-end Health install for existing Terrain and Detect customers. It extends PitLink with the addition of the Health web -based user interface. Site Health Site Health is a high-end Health install for existing Fleet and Command customers. It extends Basic Health with the addition of Advanced Reporting and Alarms. MVRS MVRS is a high-end Health install for Dealers.


Page:124

Health configuration changes

Health configuration changes There have been some changes to the configuration steps for Health, and for configuring VIMS, VIMS 3G and TPI devices.

makeDataStoresHealth It is no longer necessary to run mstarrun makeDataStoresHealth after initial installation, or after receiving a VIMS definition update. Refer to the Initializing Health section of the Initial Fleet Configuration chapter of the Fleet Administration chapter for more information.


Page:125


Deprecated features and functionality The following sections detail features and functionality that has been deprecated from release 4.0.


Page:126

VIMS 3G Download Job

VIMS 3G Download Job From release 4.0 onwards, the VIMS 3G Download job has been deprecated. Early versions of VIMS 3G for 793F-series haul trucks, version 7.2. and below, contain a distinct download job that is separate to the standard VIMS file download job. A new release of VIMS 3G for 793Fseries haul trucks is available which no longer requires this separate VIMS file download job and therefore to avoid confusion the job has been deprecated. For more details on compatibility between VIMS versions and the office software see the compatibility matrix.


Page:127

BusinessObjects 3.x

BusinessObjects 3.x BusinessObjects 3.x is not supported with release 4.0. Release 4.0 will require BusinessObjects 4.0.


Page:128

Deski Reports

Deski Reports Deski is not supported by BusinessObjects 4.x, therefore the office software no longer provides support reports in Deski. All reports are now delivered in Webi.


Page:129

BORefresh

BORefresh The BORefresh tool is now end of life. This is because BORefresh only works with Deski, and as BusinessObjects 4.x does not support Deski, there is no longer any support for BORefresh. BusinessObjects Report Scheduling and Publications are the preferred tools you should use as a viable alternative. If these do not provide all the functionality that you require, please contact BusinessObjects customer support with details of your required enhancements.


Page:130

Oracle 10g

Oracle 10g Oracle 10 g functionality is not supported in release 40


Page:131


Fleet on-board system changes The following sections describe changes to Fleet on-board systems. New Feature - Fluid Transaction On-board Hardware Changes Startup Connectivity Check Display Deprecation Information Module Compatibility


Page:132

Fluid Transaction

Fluid Transaction New functionality has been added to allow a machine operator to record fluids dispensed to another machine. You can configure Tope to include a new fluid transaction window. You can select the category, specific type, and quantity of fluids being dispensed from this window, as well as the SMU at which the fluids were dispensed.

Pressing the ID field displays a list of machines, as shown below, from which you can select the machine receiving the fluid(s).


Page:133

On-board hardware changes

On-board hardware changes Several changes have been made to improve the robustness of on-board hardware: •

Cables previously utilizing RJ45 sockets have been replaced with 6-position Deutsch DT connectors. Harnesses with these connectors will make durable environmentally-sealed connections with other Caterpillar networking hardware utilizing compatible connectors. Adapters are available for making durable connections to RJ45 cables.

•

The coaxial cable for making the connection from the GPS receiver to the GPS antenna has been replaced with an improved armored two-piece design. One cable will connect to the GPS antenna at one end and has a bulkhead connector at the other. The bulkhead connector allows for locating a connection point near the antenna mount. The second cable will connect from the GPS receiver to the second cable. Providing a disconnect near the antenna mount will improve serviceability of the cables and machine.

•

New harnesses are available to improve installation on select machines utilizing VIMS 3G.

•

A new harness is available to support dual GPS receivers on rotational machines running Tope.

•

The need for a display adapter harness on machines running Fleet and Object Detection has been eliminated.


Page:134

Startup connectivity check

Startup connectivity check Tope now has the ability to check for connectivity to the MineStar server at startup before allowing login. This functionality can help prevent a number of problems from occurring if the Fleet onboard system starts before the machine’s connection to the network has been made.


Page:135

Display deprecation

Display deprecation The CD550 running Tope 1.X and CMPD 2 running Tope 2.X will not be supported for use with Fleet 4.0. Machines utilizing a CD550 or CMPD 2 should upgrade to Tope 3.X running on a CMPD 3.


Page:136


Health Information Module compatibility Tope 3.X will require the machine to have a Health Interface Module (HIM) running firmware version 2.0.2 or newer or a third generation Vital Information Management System (VIMS 3G) utilizing the new file format.


Page:137



Page:138

Resolved issues

Resolved issues The resolved issues below are those for build M8-2.

Issue Number

Service Ticket Number

Component

Description

PitLink: Machines & Fixed Plant

The exception caused by Loadout Unit Class when generating the machine type files has been resolved. Also added a guard to bypass some failures by machine classes (if there are any) so as to continue the processing of files.

MSTAR10065/ FLT-9

GIS

The layer groups in Geo-Server are now created with the dp-prefix and namespace in their name. eg MS_ MINESTAR_MODEL

FLT-27

GIS

A no such element exception on the iterator of a geoserver update is now handled correctly. Updates to be ignored now contain 'null' geometry

FLT-30

Infrastructure

Delays now synchronize successfully between Terrain and MineStar.

FLT-34

Assignment

Assignment events are now being displayed in Assignment Event Monitor.

FLT-39

Infrastructure

Data Share now works as expected.

FLT-43

Services

The observed NullPointerException error which has been occurring when deleting a Destination (in the Destination Assistant page) is fixed now. This fix also prevents LazyInitializationException and Arrayindexoutofbounds as well.

FLT-49

Infrastructure

The delete functionality has been improved for DBDataman.

FLT-53

Infrastructure

Data mismatch between Oracle and SQL server for the tables R_CALENDAR and R_PROPERTY_FACT is fixed. R_CALENDAR table was not getting dropped every time MDS is run which caused the mismatch depending upon the number of times MDS is run.

FLT-62

Services

The CycleGenerator was taking an extended amount of

MSTAR10564 / FLT-31

TSC10073-13


Page:139

Resolved issues

Issue Number


Component

Description time to start when no cycle state recovery files were present due to the execution of some inefficient database queries. This fix improves the execution time of the database queries and allows the CycleGenerator to start quickly when there are no cycle state recovery files.

FLT-63

Infrastructure

A change to the implemented of AbstractPersistentObject.hashCode() has been reverted to maintain existing functionality.

FLT-68

Infrastructure

makeDataStores now supports index columns that have a default value.

FLT-70

Infrastructure

makeDataStores (major) now removes duplicate rows from the MACHINE_CATEGORY_CAPABILITY table so that the MACHINE_CATEGORY_CAPABILITY_PK primary key can be created.

FLT-86

User Interface

Destination name is displaying twice in the scheduled Assignment Monitor when creating shift change. Made changes in the scheduled assignment pages to reflect this.

FLT-111

Infrastructure

Summary can now be run for STANDBY server and the delay and cycle data is moved to STANDBY server.

FLT-196

GIS

There are no longer errors when the sychronization of the grade blocks layer to GeoServer takes place.

HLT22

A file log record is created on import of payload and event files as per other VIMS report categories.

HLT-30

Fixed the problem with missing data due to identical channel name in critical trend reports (HE410Ad-CriticalTrends).

HLT-31

Corrects fuel consumption trend decoding for 777G. More over corrects decoding of data points with flow and pressure unit types

HLT-33

Fixed the problem with service hours not mapped correctly to data points when importing VIMS NFF files.

HLT-35


Air Filter and Parking Brake channel and trend data are now decoded correctly.

Page:140

Resolved issues The resolved issues below are those for build M9-1.

Issue Number


AHS-63

FLT-15

TSC0428112, TSC0766-13

FLT-106

FLT-131

TSC08775-12

Component

Description

Fleet

Corrected database primary key violation allowing the class of a truck to be correctly changed.

User Interface

Fixed the problem with scheduled jobs being stacked up when a job takes a long time to run e.g. VIMS Import Job. The job is now skipped if another instance is still running. Users can configure this feature in Supervisor.

User Interface

Corrected the coverage map generation job so that it does not throw NullPointerExceptions if there are no .gwm files to process.

Infrastructure

Preferred machines are now being saved with ordering details. The Personnel Editor is now correctly being updated when displaying new persons.

FLT-135

User Interface

In Personnel Finder, when trying to edit the records, and also when trying to open/preview the archived records they now display correctly on Quick view.

FLT-158

Infrastructure

Default dates are now based on the offset in the shift format pattern set in Supervisor for the selected shift type in the dropp-down list. {0} = start date {1} = finish date {2} = instant after finish date {3} = halfway between start and finish dates {4= 24 hours after start {5} = 24 hours before finish {6} = 7 days after start {7} means 7 days before finish Also for an offset of 1 against the 12 hour night shift or the 3rd 8 hour shift the Roster Editor will display based on the shift finish date, which for any given day, displays the night shift first i.e. the night shift finishing on that day.

FLT-155

User Interface

FLT-160

User Interface

FLT-167

TSC10080-13

TSC-


When editing a delay the delay duration is now retained and not overwritten by the selected delay type. Loading tools are now valid destinations for shift change and when enabled can be used as a tie down location for all machines. Saving the page config from the Onboard Files Assist-

Page:141

Resolved issues

Issue Number


Component

10736-13

FLT-174

Description ant now maintains the correct page config that was used to create it.

Infrastructure

Incrementing missed counts on waypoints no longer fails.

FLT-176

TSC10505-13

Services

Start time should be enabled when creating a delay with and unknown duration but should not be enabled when editing the delay.

FLT-179

TSC10473-13

Services

The Delay Type tree in the Delay Editor Page now opens up collapsed as per MineStar v3.1.

FLT-194

TSC10421-13

Services

When the KPI Summary engine was processing an update to a cycle (for example a Loader cycle may be updated when the truck that was loaded completes it's Truck cycle), the engine was not correctly removing the old KPI values before adding the new ones. This was resulting in some instances incorrect realtime KPI values.

FLT-197

TSC10794-13

User Interface

The Split Cycle Wizard now displays the Start/End Position Name instead of the XYZ coordinate.

FLT-202

TSC10423-13

Services

Zero fluid amounts will still display a warning but will allow the user to still save the values if required. Validation errors that prevent the saving of data are displayed as errors instead of warnings.

FLT-203

FLT-206

FLT-210

Architecture

TSC10703-13

FLT-223

FLT-226

When trucks are put on delay the icon in the site monitor now correctly turns grey to show the truck is on delay.

The infrastructure layer is for command and has been removed for fleet-health licenses.

Services

TSC10920-13


Fixed the issue while running exportDataStores for historical and summary DB from client machine.

User Interface

Error when opening the Safety Check Record prevented the page from showing any data. These have been fixed. With a Fleet license, the default Create item in Site Editor is a road, not a DXF poly line. When creating roads the default shapes are ignored and the user needs

Page:142

Resolved issues

Issue Number


Component

Description to free form click the road shape.

FLt-239

FLT-277

TSC0986313, TSC09309-13

FLT-286

Architecture

A migration script has been added to detect and correct invalid data in the DELAY_GROUP_SUBDIR table that would prevent database constraints from being created.

Assignment

Manual assignments are now considered active which means scheduled manual assignments are properly handled when determining if an assignment is locked. A truck's assignment is locked when the truck is in the same the lane/waypoint which requested the previous assignment. For example, if a truck's state changes at the same waypoint which prompts two assignment requests, then the truck's first assignment will not be overridden.

GIS

Fixed Hibernate LazyIntializationException when processing notifications of changed Grade Blocks. When exporting the Time Usage Model to XML the 'waitForSpotDuration' embedded variable is included to prevent validation errors.

FLT-289

FLT-306

A change to iPretend was made to improve interoperability with other simulation tools. Two new options were added: -include Only simulate the specified machines -exclude Do not simulate the specified machines (i.e .-ignore) Additional checks were added to prevent iPretend from issuing commands for ignored machines.

FLT-45

Exceptions no longer occur when editing the name of a machine category and then trying to edit a machine under the same category.

FLT-56

User Interface

A selection box has been added for Seconds in the DelayEditor page duration field.

FLt-72

User Interface

The errors when opening some of the Delay Monitor


Page:143

Resolved issues

Issue Number


Component

Description page configurations have been addressed. The maximun column widths in the Delay Monitor have all been removed and the page will now show a horizontal scroll bar to support wider columns.

FLT-85

User Interface

HLT-35

Now able to select the delay types while creating Manual or Automatic scheduled assignments when using Scheduled Assignment Editor. Air Filter and Parking Brake channel and trend data is correctly decoded.

HLT-53

Improved processing of HS3 VIMS reports containing undefined histograms

HLT-56

Supporthas been added for additional transmission trends available on F series Large Mining Trucks with VIMS 3G NFF .

HLT-58

The VIMS file download process now produces a single request at a time even after recieving an error from VIMS 3G NFF device.

HLT-59

Newer generation VIMS 3G units encourage a valid timezone to be set during VIMS configuration with CAT Electronic Technician. This change requires that MineStar Office communicates its timezone when attempting to synchronize the clock between device and MineStar office. The clock synchronization can be performed the following ways: 1) Through the Synchronize VIMS clock with office job 2) During VIMS file download if default Set VIMS clock supervisor option for VIMS file downloads 3) Between Fleet On-board (TOPE) and VIMS via iDesk 4) Between VIMS and GPS This improvement adds an option to methods 1 & 2 to optionally include the timezone information of the MineStar office installation.

UX-43

Server, User Interface

In the web client smart search can find a machine by its serial number and the Manage Machines page can be filtered by a serial number.

The resolved issues below are those for build M10-1.


Page:144

Resolved issues

Issue Number


CMD-115

Component

Description

User Interface (Web)

Added support in Machine Configuration for the Terrain Mobile product.

CMT-1436

Delay codes being synchronized with Terrain were not being applied to MineStar if only the duration was changed in Terrain. Neither would Delay Codes with only changes to the duration be sent to Terrain via the sync process. The code was updated to check for changes to the duration along with the other synchronized attributes for a Delay Code.

FLT-168

Infrastructure

The licence cache now reloads before checking for the licences. This allows operators to log in as soon as machine is created in MineStar.

FLT-178

The Scan button is no longer enabled while thn scan process is running in the Data Model validation page. The fix avoids the user interface error when the user tries to hit the Scan button multiple times while the scan process is not completed yet.

TSC-1074213

User Interface (Java)

FLT-192

TSC-1079713

Services

The cycle editor and wizard now listen for events where a cycle has been deleted so that users editing a deleted cycle can be notified that the record is no longer available.

FLT-204

TSC-1083613


Snapping a waypoint to the surface no longer looks for autonomy services that are not running.

FLT-230

Assignment

Errors no longer occur when modifying a scheduled assignment because of locations not being setup properly as Scheduled Assignment Locations.

FLT-257

Assignment

Removed logging statements which were causing errors.

FLT-263

Services

When a delay is deleted, but a corresponding cycle activity can not be found, a warning is logged and delay deletion is allowed.


Updated the kpi labels to be unit agnostic i.e. Bank Volume. Also updated units.xml so that imperial bank densities default to the correct units.

FLT-282

TSC-1137613


Page:145

Resolved issues

Issue Number


Component

Description

FLT-292

Services

When both the Personnel Finder and Machine Licence Finder are opened in the client, changes to the licences held by personnel are now available in both pages without requiring the page to be closed.

FLT-302

Infrastructure

The Machine License Adaptor is now an extension.

FLT-345

Services

Any objects fetched from Hibernate as a "HibernateProxy" are now converted into the correct domain object before being returned.

FLT-347

Architecture

The Audit History page has been removed from the client.

FLT-348


The properties files which defined the columns available to the Delay Monitor still referenced the deleted "category" column. These obsolete references have been removed.

Assignment

The handling of a material change on a truck is ignored for an empty truck preventing a dipper report without a loading state change from causing a reassignment of the truck.

FLT-349

TSC-1154313

FLT-351

FLT-357

Shift Change Allocation Monitor now correctly reflects what the Delay Monitor is showing in terms of delayed vehicles. TSC-1160313

PositionReports missing either State and/or Location were being received and processed by MineStar. MineStar now either ignores or warns when an incomplete event is processed rather than throwing exceptions that can pollute the logs.

Infrastructure

Operators can now be removed from machines in Machine Assistants.

FLT-375

Assignment

Updated the handling of trucks ignored for assignment.

FLT-378


Fix updates of the active status of grade blocks.

FLT-379

Services

Fix setting fluid details on a ServiceHours event.

Services

Improved performance of VIMS histogram imports.

FLT-368

FLT-380

TSC-1191113

Services

TSC-11726-


Page:146

Resolved issues

Issue Number


Component

Description

Infrastructure

The V_HEALTH_EVENT view will now be created on sql server.This will also fix the update issue in the MEASURE_DEF table on sqlserver.

13

FLT-381

FLT-387

TSC-0732112 TSC11540-13 TSC-1201713

FLT-391

Assignment

The assignment event logger will now not show unable to assign messages unless an assignment has been requested by the controller or the truck.

Infrastructure

A thread safety problem could lead to corruption of data packets. This is particularly a problem when using iPretend.

Infrastructure

The LicenceCache was being reloaded multiple times (once for every machine) whenever a machine was opened for editing in the Machine Finder. This resulted in unacceptable performance, particularly on large mines. The LicenceCache is now only reloaded when changes are made that affect licences.

FLT-402

Infrastructure, Services

If periods e.g. Day, Week, Month etc are set with the offset of 1 (finish date) then period selections will organise by shifts finishing in the selected period. This will allow the period selectors to work correctly where periods are specified by finish time rather than start time. Also the shift label in the shift change editor defines the start and finish times of the shift to avoid ambiguity where sites have the finish time offset (1).

FLT-413

Assignment

FLT-399


Assignment would not correctly determine the travel times between loading tools and processors for autonomous trucks. This caused over saturation of loading tools and/or processors, as well as made the production requirements and other features of Assignment not work as expected. This has been fixed and autonomous trucks using lane based assignment will now operate correctly with normal fleet allocation to all servers based upon actual travel time information.

Page:147

Resolved issues

Issue Number FLT-421

Service Ticket Number TSC-1189113

FLT-436

TSC-1189013

FLT-440

TSC-0813212, TSC11717-13

FLT-443

FLT-76

FLT-91

Component

Description

Infrastructure

Operators can now log on to Auxiliary machines.

Services

Nightly snapshots no longer fail.

Assignment

The model validator for ScheduledAssignments has been modified so that manual and asap ScheduledAssignments are considered valid and are not removed by the scan.

Infrastructure

The machine licence name was not properly compared with a person with that machine licence in Machine Licence Adaptor. This fixes issues for determination of the difference between licence names "licence" and "licenceShovel" in Machine Licence Adaptor.

TSC-0710912

Assignment

New option in Supervisor, on the Assignment Supervisor under Policies: Delayed trucks in a queue will resume queueing when taken off delay. This allows trucks to resume queueing when placed on a delay while queueing rather than getting a new assignment when taken off delay.

TSC-0780112


FUG-126

The selection of the destination has been changed from a combo-box, to a popup to allow searching and filtering for easier selection on all the machine assistant pages, and on the mining block editor. Fixed database unique constraint violation in Daily Service Schedule page.

FUG-133

After a file transfer to underground machines, MineStar will send a FileAction2 message to notify MineGem that files have been uploaded. If a file gets corrupted in the file transfer, it will attempt to upload the file again.

HLT-48

Update to VIMS master database version 13.0.0


•

New UIDs for APECS support (issue #350)

•

Added bitmap UIDs that are missed in the previous release

•

Expanded event description from 80 to 255 chars (issue #356)

Page:148

Resolved issues

Issue Number


Component

Description •

Fixed "Forward Time: Gear 2" unit issue (issue # 349)

•

773E: Added new Histograms (9970 - 9982)

•

777F: Correct Actuate values for Event 13286 (Body Up) and 13231 (Grnd Speed)

•

793D Mule: Added new event (13230- Trn Oil Temp)

•

773F & 775F: Added new Events (13232-Trn Out Spd and 13233- Grnd Spd)

•

773E: Added new Events (13234 - 13237 Eng Spd )

•

793D (High Altitude): Added new Altitude Derate event (13238)

•

Hitachi Shovels, Ex-6 series

•

Bucyrus Rope Shovels, 495

•

Bucyrus Hydraulic Shovels, RH340B, RH400

•

Liebherr Excavator

HLT-51

Early version VIMS cumulative data is now persisted during file import.

HLT-65

When MineStar receives a VimsTpmsCycle2 message from a TPI device it now repoonds immediately.

HLT-67

Improved handling of EC3 files with duplicate events.

HLT-73

VIMS Event files with CID/MID or FMI values can now be imported. Improved error handling of corrupted VIMS files. Certain corrupted files could cause VIMS import job to suspend until user closes the error dialogue. The error dialogue has been removed and replaced with a more userfriendly message in the progress dialogue.

HLT-74

MSTAR10095

TSC-0720512, TSC-1094713

UX-9


Assignment: Scheduled Assignments

On Arrival delay for Manual Scheduled Assignment is now working correctly.

Server

The Site Map within the Web Client is now available for

Page:149

Resolved issues

Issue Number


Component

Description use with a Command-only license to display Command features (e.g lanes).

UX-28


Simplified the use of the monitoring collection by having fully typed data and making the code more readable.

UX-42

RFT, User Interface

Site bounds are now shown using GeoServer.

UX-47


Finding AStop device ID's < 10 using smart search is now possible

UX-59

Server

Added cumulative hang time for machines on the KPI screen.

UX-150

Map

Modified the web client Map's road style to only show the name up to 1:1900 scale, removing some clutter when zoomed out.


Page:150

Enhancements

Enhancements The enhancements below are those for build M8-2.

Issue Number


Component

Description

Platform: System Admin

FTP file transfer will work on both Linux and windows directory listing. Also the current directory selection based on customer code is removed.

Production: Cycles

The cycle generator has been modified to store travel at source and sink in the cycle road segments.

MSTAR9885

Health: Health Data Mgmt

Option added to VIMS Import job which allows users to choose between concurrent processing of files and disabling concurrency. Processing concurrently will reduce the total time taken to import a large set of files but places more strain on the overall MineStar system.

MSTAR9828/ FLT-97

Production: Delays

Added the ability to store a work order reference against a delay instance. Refer to the feature note documentation for details.

FLT-29

Infrastructure

Updated MineStar and Terrain to ensure that common data for Machine definitions are synchronized successfully between the two systems (when the two systems are configured to synchronize data).

FLT-38

Infrastructure

Improved the fluid and SMU validation, so that error messages between the two are not shared. Instead, the validation messages are separated, telling the user what the error is and hence what to fix.

MSTAR10328/ FLT136 MSTAR9020

TSC03173-12

FLT-58

Infrastructure

Zip upgrade files now do not include a JDK environment, so systems can be easier to manage, because the JDK environment is defined and supported outside of the zip upgrade process.

FLT-136

Architecture

FTP file transfer will work on both Linux and windows directory listing. Also the current directory selection based on customer code is removed.

FLT-173

Assignment

The assignment context message produced during a


Page:151

Enhancements

Issue Number


Component

Description failed assignment for loaded truck was corrected changing the variable reference when the message was generated. This ensures the material name is displayed and not the date. For example "T00 at SH0 with Coal has no valid assignment" not "T00 at SH0 with 02:43:00 EST 31 March 2013 has no valid assignment"

UX-8

RFT

UX-49

Web Client

The KPI Dash-board screens for Utilization and Loading Times will only show loading tools that Cycles/KPI determine to have production numbers. GPS Accuracy is no longer displayed and is not being used for machine status.

Enhancements for builds up to M8-1.

Issue Number


Component

Description

MSTAR10512

Production: Delays

When saving a file, the extension defaults to .xls if no extension is given when exporting the time usage model to Excel.

MSTAR10518


A check box has been added in Supervisor, Options > System Options > Health > VIMS Import, to enable the backup of files prior to importing. This option is disabled by default. The same check box has also been added into the office software on the VIMS Data Import job page. When selecting the check box in Supervisor, it is also selected in the office software.

MSTAR10402

Health: Health Data Management

Store VIMS Hardware and Software version information during import.

MSTAR10377

Platform: Database Admin

RMAN is an optional tool for database backup. A Supervisor setting is provided to enable RMAN. Supervisor > System Options > Workgroup Extensions > RMAN configurations.

MSTAR10269

Health: Heath Data Mgmt

The message indicating files already uploaded to the same host has been updated to be more clear.


Page:152

Enhancements

Issue Number


MSTAR10241

TSC05994-12

Component

Description

Health: Heath Data Mgmt, Health: Wired Download, PitLink: Field Comms

Newer generation VIMS 3G units encourage a valid timezone to be set during VIMS configuration with CAT Electronic Technician. This change requires that the office software communicates its timezone when attempting to synchronize the clock between the device and the office. The clock synchronization can be performed the following ways: 1. Through the Synchronize VIMS clock with office job. 2. During VIMS file download if default Set VIMS clock supervisor option for VIMS file downloads. 3 Between TOPE and VIMS via iDesk. 4 Between VIMS and GPS This improvement adds an option to methods 1 & 2 which will optionally include the timezone information of the office software installation.

MSTAR10240


New Supervisor settings have been added to the also new RMAN functionality. In Supervisor, Options > System Options > Workgroup Extensions > RMAN configuration as follows. •

Enable RMAN on this system check box.

•

RMAN Base Directory path field.

•

Archive Log Destination field.

MSTAR10219

Platform: User Interface

For each Machine Class Editor that displays the Machine Type tab, there should now be a machine type drop-down list in the main page panel allowing selection of a machine type. In those editors where the onboard tab is displayed, the selection of the machine type should effect the population of the Operator Interface combo on the onboard tab.

MSTAR10215


Import VIMS files for new machines will now trigger a re-import of machine measure limits.

MSTAR10189

RFT, Web Client

The user name has been added into the About dialog.

MSTAR10119

RFT, Web Client


The RFT now uses the correct location for help files.

Page:153

Enhancements

Issue Number


Component

Description

MSTAR10069

Machine: Travel Network

The mining block tree now displays Layers dialog in the Site Monitor and Site Editor.

MSTAR10061

Production: Delays

When making changes to Delay Categories, the user interface now flags that the Time Usage Model needs to be revisited and the xml regenerated.

MSTAR10084

RFT, Web Client

A more specific icon is being displayed in the selection panel within the thin client's site map to represent a machine. The new icon will be a side view corresponding to the machine icon selected for the machine. In cases where no side view icon is available a generic machine icon will be displayed instead. The Travel Progress Monitor of the thin client will now also display the appropriate icon for loading tools to improve clarity to the user.

MSTAR10041

RFT, Web Client

On Travel Progress Monitor, the tooltip for a machine now shows the complete mining block path rather than just the block name.

MSTAR9976

Health: User Interface

Event lines in the Flex client are now ordered by machine name, then event names.

MSTAR9996

PitLink: Operator Messaging

The Message Group Editor now allows the same association list as is available in the Machine State Editor.

MSTAR9930

Health: Web Client

The rendering speed of Health Events has been improved.

MSTAR9908

PitLink: Operator Messaging

Outbound office message timeout and retry are now configurable in Supervisor, and the default timeout has been reduced from 180 seconds to 10 seconds.

MSTAR9898

Health: Health - Health Data Deletion job segments deletion in groups to Data Manavoid exceeding database rollback segment in cases agement where a very large quantity of data is to be deleted.

MSTAR9891

Production: Delays


A new tab has been added to the Delay Editor for managing delay activities. This tab is only available if the selected delay type has a delay activity class associated with it.

Page:154

Enhancements

Issue Number


MSTAR9718

Component

Description

Health: Web Client

The Server version number has been added to the About dialog. The Assignment Events Monitor received the following improvements:

MSTAR9626


Assignment: Decision Support

•

Publish Message Grade Block Warning No warning is published in the Assignment Event Monitor for mining block locking when the truck cannot go to the mining block destination. A warning is published in the Assignment Event Monitor for strict mining block locking when the truck cannot go to the mining block destination.

•

Publish Message when assignment cannot be sent A message "Unable to send assignment to truck" will appear in the Assignment Event Monitor if a message cannot be sent to a truck (e.g. radio contact failing.)

•

Publish Message when unknown truck state A message "Unable to assign truck {0} as the truck state is unknown" will appear in the Assignment Event Monitor when the truck state is unknown.

•

Publish Message when unknown material determination A message "Unable to assign truck {0} as the material determination is unknown" will appear in the Assignment Events Monitor when the material determination is unknown

•

Publish Message when Truck Out of Service A message "Unable to assign truck {0} as the truck state is out of service" will appear in the Assignment Events Monitor when the truck is out of service. However, preceding events which cause trucks to be out of service such as delays will take priority in the messages.

•

Fix to Message No Assignment Loaded A message "Truck X at Loading Tool Y with {3} has no valid assignment." appears in the Assignment Event Monitor. The {3} now includes the name of the material.

Page:155

Enhancements

Issue Number


MSTAR9555

Component

Description

Platform: Installation Platform: Configuration

The default Oracle 'Server' template has been updated to reflect common current production, and minimizes the usage of the recommended hardware.

MSTAR9504

Health: Health Data Management

UTC columns have bee added to V_OIL_SAMPLE for each timestamp field.

MSTAR9475


Updates and corrections to Supervisor text description and added unit selections where applicable.

MSTAR9474


Updates and corrections to Supervisor text description and added unit selections where applicable.

MSTAR9473

Production: KPIs & Summaries

Time Usage Model Editor now has the ability to export the visual representation of the Time Usage Model as an Excel spreadsheet file.

MSTAR9343

Health

MineStar Health and Pitlink only licence options are available which reduce the default started services and reduce the menu items and pages available to the required functionality provided by the respective license.

MSTAR8991

Health: Data Mgmt

Improved logging of timeout and missing interface errors in Health jobs.

MSTAR8960


Executing mstarrun generateKpiSummaries no longer needs MineTracking to be running.

MSTAR8929

Platform; Software Updates

The version number in the patch builder will be correctly populated when running Supervisor within a development environment.

MSTAR8717

Platform: Database Admin, Platform: Disaster Recovery

Provides functionality in MineStar 4.0 to improve handling of large databases.

MSTAR8683


Improved handling of VIMS PC definition data and loading into MineStar Schema.


Page:156

Enhancements

Issue Number


MSTAR8682

Component

Description

Platform: 3rd Party

The Oracle data type for timestamp storage has been changed from DATE to TIMESTAMP(3). A "makeDataStores all" should be run on existing databases to update the column definitions. Update VIMS definitions database to version 11.0.5.

MSTAR8634


•

Support for Seatbelt feature

•

Support for 797 Changes related to Hoist HD Pres and Hoist Rod Pres

•

Support for VIMS Guardian Events

•

Support for 789D Events

•

Support for VIMS 3G Diagnostics.

MSTAR8622

Health: Wireless Download

TPI version of VIMS 3G sends an accept (response) then success (message) on reset request. This causes download procedure to error. Now this has been fixed.

MSTAR8587


Support for the creation of VIMS long version header (VIMS version 10.5+) on download of file.

MSTAR8586

Platform: 3rd Party

Many third-party JARs used by MineStar are well behind the times. Do a global upgrade of JARs.

MSTAR8580

Proxy level support has been added for historical requests.

MSTAR8550


New application to build Time Usage Models and generate KPI Summaries XML.

MSTAR8514

Platform: Configuration

SSMA Migration tool need to be used to migrate the data from Oracle to SQL server.

MSTAR8508

Platform: Installation

Changed text in installer panels. Installation options have not changed, only the text describing them.

MSTAR8319

Platform: 3rd Party

The Sun proprietary code has been replaced by using the Base64 class from Apache Commons Codec.

MSTAR8313

Production: Cycles

The CPU performance of the CycleGenerator has been improved.


Page:157

Enhancements

Issue Number


MSTAR7081

Component

Description

Production: Delays

An email is now sent when a machine ends a delay, as well as when it starts a delay. Purging the Oracle Recycle bin to free up the space occupied by the deleted objects, as a part of initStandbyDbFromSnapshot,replaceDataStoresWithModel,replaceDataStoresWithXml and emptyDataStore has been implemented.

MSTAR4634

The task has been added to Scheduled Jobs in the office software. This is Expert Mode functionality in Supervisor, at Options > System Options > System > Workgroup Extensions > PurgeRecycleBin (Tab). MSTAR2906

Health: Real Time Events

The Event table in the web interface now displays the worst values and the first values if included in event messages.

MSTAR2261


Corporate data management has been added into Health.


Page:158

CAT Fleet

4.0 Release Notes

Known issues Service Ticket Number

Component

Description

MSTAR10568 / FLT28

CMD IL 3572

Platform: Security

When launching a client from anywhere other than the MineStar application server itself, the user does not get any notification that their MineStar license is going to expire. The only time any client notification occurs is if the MineStar client application is launched from the server which it is not supposed to be.

MSTAR10544

CMD IL 3556

PitLink: Machines & Fixed Plant

There is no icon tab for Machine Class Editor when running a Fleet/Detect License.

Issue Number

MSTAR10392

Perform analysis to determine performance bottlenecks and potential improvements.

MSTAR10439

Assignment: Assignment Controls

Compatibility confusion in Mine Model Query.

MSTAR10294

Platform: GIS

GeoServer producing errors.

MSTAR-9899


Health Import Job messages do not always show the correct count.

MSTAR-9858


Regression testing needed for views used in BO Reporting.

MSTAR-9555

Platform: Installation, Platform: Configuration

Oracle "Server" template needs to be updated to reflect common current production and maximize the use of recommended hardware.

MSTAR-9121

PitLink: Field Comms

Remove requirement for default Field Handlers to be resolved from Config.properties.

Caterpillar: Confidential Yellow Page 159 / 159

CAT FLEET & HEALTH V4.0.pdf

Recommend Documents