CAT FLEET & HEALTH V4.0.pdf

Cat Fleet 4.0Cat Health 4.0Release Notes

Contents

Table of ContentsChange 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

New and improved features 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 VIMSWireless Messaging Healthjob 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

CumulativeMaterial Moved 24

Cat Fleet / Cat Health Page:24.0 Release Notes

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

RunmakeDataStores 31

Review KPIGen.properties 31

Update the Customer's KPISummaries Universe 32

Create Dashboards or Reports that access real-time KPIs 32

Delays 33

Email notification of delays 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 46

Tables 46

Safety Checklist 47

Safety Check Record 48

Shift Change 49

Shift Change Finder 50


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

Travel Progress Monitor 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


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


Contents

Upgrade path for minor releases 117

Exception runningmakeSpatialStores 117

Zip upgrade installation 118

Zip upgrade release artifacts 118

Zip upgrade steps 118

Exception runningmakeSpatialStores 119

Troubleshooting GeoServer 120

Exception error when runningmakeSpatialStores 120

Configuring Windows Auto Updates 122

Oracle Database 11g Express Edition 123

Health install and Licensing options 124

Health configuration changes 125

makeDataStoresHealth 125

Deprecated features and functionality 126

VIMS 3G Download Job 127

BusinessObjects 3.x 128

Deski Reports 129

BORefresh 130

Oracle 10g 131

Fleet on-board system changes 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


Change History

Date Change EditedBy Version

7 December 2012 Draft K Wilson Draft

14 December 2012 Added Resolved Issues and Improvementsfor Build M6-1.

K Wilson Draft

22 January 2013 Added Resolved Issues and Improvementsfor Build M6-2. K Wilson Draft

11March 2013 Updated Resolved and Known Issues andEnhancements up to build M8-1. K Wilson Draft

8 April 2013 Updated Resolved Issues and Enhance-ments for build M8-2.

K Wilson Draft

23 April 2013 Updated BusinessObjects Reports withchanges in build 4.0M-9.

K Wilson Draft

29 April 2013 Updated Resolved Issues for build M9-1. K Wilson Draft

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

Changed BusinessObjects section.K Wilson Draft

Information in this document is subject to change without notice. While every effort has beenmade 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 arisingfrom, the use of this information.

This document and all related documentation are the property of Caterpillar andmay not be reproduced,transferred, sold, or otherwise disposed of, without the written permission of the owners.


Overview

OverviewWelcome to the release notes for Cat Fleet and Cat Health release 4.0 which delivers functionalityand other improvements over those delivered in Fleet 3.1 and 3.1.1.

These release notes have the following sections.

New and improved featuresThis section comprises new and improved features in Fleet 4.0, starting with themajor new featuressuch as the Health and Fleet web clients, andmoving into the improved and enhanced features such asSite Editor surface rollback andMachine Class capabilities.

PlatformThis section comprises new and updated platform information for Fleet 4.0, such as GeoServer and Busi-nessObjects 4.0.

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

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

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

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

EnhancementsThis section provides a list of enhancements in Fleet 4.0.

Known issuesThis section comprises the known issues in Fleet 4.0.


New and improved features

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


Health

HealthThe following sections describe the new features relating to Health.


Health web-based user interface

Health web-based user interfaceA new web-based Health user interface is available for monitoring real-time, or exploring historicallylogged, 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, cumu-lative and channel data from devices and the specific configuration stored and recalled by any other sys-tem user.

Timeline Viewer

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

Spatial Viewer

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

Event Monitor Viewer

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


Health web-based user interface

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


Measure Groups

Measure GroupsWith the introduction of the Health Monitor, a new concept of Measure Groups has been introduced tosimplify themanagement of health monitors.

You are able to define groups of trends, cumulative and channels, and provide the group with a customname.

Groups are visible to all users system-wide and can be used to simplify the creation of new health mon-itors around commonly targeted channels, trends and cumulative.


Corporate Data Share and VIMS File Upload

Corporate Data Share and VIMS File UploadA new job has been introduced which allows for on-forwarding VIMS files from office software install-ations tomultiple FTP and/or secure FTP locations.

Scheduled regularly, this job simplifies VIMS file management and processes required to send files toCaterpillar, Dealer or alternative customer sites.


Configuring VIMS or HIM to send events in real time

Configuring VIMS or HIM to send events in realtimeThere are three options for configuring VIMS or HIM to send events in real time. All of them involveinforming the device which Office IP Address to send events too.

The options available are:

1. Configure eachmachine by connecting to the web server (communicator) embedded in each deviceand setting the office IP address.

2. Run the Configure VIMSWireless Messaging Health job to send TMAC message tomachine toalter its configured IP address.

3. Run a system command to send TMAC message to themachine to alter its configured IP address.

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

Note: See your VIMS 3G or HIM setupmanual for more detailed instructions.

VIMS 3G and HIM 2.x comewith an embedded web server often referred to as communicator. You canconfigure the device to send events to the office via communicator by setting the Office IP address.

Do the following steps for eachmachine.

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 ConfigureVIMS Wireless Messaging Health jobYou can change the internally configured Office IP address of each device by running the ConfigureVIMSWireless Messaging job, which sends a TMAC message to eachmachine selected in the job withthe current office IP address.

1. Click Jobs > Health > Configure VIMSWireless Messaging.

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


Configuring VIMS or HIM to send events in real time

3. Click Run.

To configure VIMS to send events to the office in real time1. 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.SendBroadcastSettmac://192.168.1.44:51889 172.30.44.34

4. Monitor the Field Communications Monitor for an outgoing CmnBroadcastSet2 request and acorresponding CmnBroadcastSet2Response response.

5. Monitor themachine for VIMS events, using Health Event Monitor.


Configuring Pollable Channels

Configuring Pollable ChannelsPollable channels are only configurable for VIMS 3G and TPI. The command for configuring pollable chan-nels is as follows.

mstarrun -b healthChannelSetup ,..

e.g.

mstarrun -b healthChannelSetup T01,T02


Support for larger fleet diversity

Support for larger fleet diversityPrior to release 4.0, Health supported amaximum number of different channels, trends and cumulativetypes. Newer versions of VIMS have increased the diversity of channel, trend and cumulative types, lim-iting 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 res-ult, the profile database storage size, performance of VIMS file import and BusinessObjects reporting dif-fer from prior versions of Health. The exact difference depends onmany factors and is dependant on thespecifics of the installation; in some cases improvements will be observed while in others a performancereduction will be observed.

See the Compatibility Matrix document for more information on application sizing and performanceguides.


Fleet web client

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

Opening the web clientTo open the web client, you need to open your Internet Browser, and enter the URLwhich will have beengiven 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 hasbeen given to you.

The web client opens displaying the Site Map as the default desktop. You are able to open otherdesktops such as Travel Progress Monitor and KPI Dasboards.

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


Remote Foreman's Terminal

Remote Foreman's TerminalThe Remote Formans Terminal (RFT) provides a low bandwidth view of the office software to a Fore-man, who is looking at it primarily while in the field, allowing them tomonitor the decisions made by theoffice software and theMine 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 clientare downloaded automatically on opening the client. For instructions on how to install and use theRemote Foremans Terminal, refer to the Fleet web client online help.

The Remote Formans Terminal comprises the following.

Site Map KPIDashboard Travel Progress Monitor

In addition the Remote Foremans Terminal

is read-only. will work on small screen laptops, for example, a Panasonic Toughbookwith 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.


SiteMap

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


Travel ProgressMonitor

Travel Progress MonitorThe Travel Progress monitor shows the relative position, and allocation, of trucks to loading tools and pro-cessors. The Travel Progress Monitor in Remote Forman's Terminal is designed differently to the exist-ing 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 10minutes and then 10minutes to the longest ETA. whenmachines are on delay they are organized by their last known location.


KPI Dashboards

KPI DashboardsThe KPI desktop displays dashboards showing different KPIs.

Production Utilization Loading

Thesemetrics are a consolidation of different mining requirements.


Production

ProductionOn the Production screen you can choose to view Material Moved or CumulativeMaterial Moved inform-ation. On both screens you can filter by Loading Tool andMaterial, or choose to display All Loaders andAll Materials.

Material MovedThis view displays information relating to the number of tonnes (or the appropriate unit of measurementfor your mine site) of material moved within the current shift. It indicates the following.

The actual amount of material that has beenmoved for the current shift. An estimate of how muchmaterial will bemoved 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 andmaterial by selecting the desired option from the filter buttonsabove the graph. These are shown below. Units may vary depending on the type of material selected. Ifmultiple materials are selected theMass unit is shown. For a single material, the unit is based on thetype of material selected. For example, if set up correctly, Waste could be shown as BCM (Bank CubicMeter).

Cumulative Material MovedClick the drop-down arrow by Material Moved and select CumulativeMaterial Moved. This view displaysthe cumulativematerial moved throughout the shift.



Production

The quantity of Prime and Rehandledmaterial is displayed on an hour- by-hour basis.

You can filter the data by machine andmaterial by selective the desired option from the filter buttonsabove the graph. These are shown below. Units may vary depending on the type of material selected.


Utilization

UtilizationThis screen displays the KPIs relating to the loading tool availability and utilization as a percentagewithin the current shift. The loading tool names are listed on the left of the graph, with the percentagesalong the bottom of the graph.

Average availability and utilization are displayed as a line dropping down to the average percentage.


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


Loading

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

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

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

Cumulative DurationThe total time the loading tool spent in each state for the shift.

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

An example screenshot of each is shown below.

Shift Average


Loading

Rolling Average

Cumulative Duration


KPI Configuration Tool (TimeUsageModel)

KPI Configuration Tool (Time Usage Model)

This feature is designed for creating a time usage model for NEW sites, not for updating themodel at existing sites. In the future the feature will be expanded to be available for the con-version of existing sites. As this feature has a direct impact on production recording itshould be configured by MineStar deployment or support personnel only.

From release 4.0, you are able to use the TimeUsageModel page in the office software to build themodel graphically and then export themodel as a generated piece of XML, rather than directly modifyingthe KPI Summaries definition file. This can then be incorporated into and used by the CyclesKpiSum-maries engine.

The TimeUsageModel page is anExpert Mode page, and once you are in Expert Mode can be found byclicking Contents > Platform > TimeUsageModel Finder.

The TimeUsageModel Finder allows you to create new models, view and open existingmodels, anddelete models.

An example of the opening screen of the TimeUsageModel Editor page is below.

The top left panel is theModel Hierarchy Editor, which shows themodel as a tree view. The top right panel is theModel Attributes Editor. The bottom panel shows a graphical representation of the structure of the time usagemodel. This only

updates when a node in the tree is selected.


KPI Configuration Tool (TimeUsageModel)

Formore information on the TimeUsageModel Finder and Editor, refer to the Fleet User manual.


Real-time KPI Persistence

Real-time KPI PersistenceRelease 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 inSupervisor. The data is presented through a view, and available to third party software such as Busi-nessObjects Dashboards. In future versions, this will be used within the office software user interface.

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

Run makeDataStoresmakeDataStores must be run after inserting or modifying KPISummaries.xml with the new KPI Sum-maries entries. RunningmakeDataStores creates the necessary database tables and views to allowthird party software to access real-time KPI's. Below is an example of a view that will allow access tothe 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.propertiesAfter makeDataStores is run, the KPIGen.properties file contains entries that can be used to update theKPI Summaries universe at the customer site to expose real-time KPI's for use in reports and


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 realtimeKPIs."; Show->Boolean(true)}

Class.Realtime\ Kpis.DrillKpis={Description->"Holes and feet drilled perhour and per shift"; Show->Boolean(true)}

Update the Customer's KPISummaries UniverseUsing amanual process, or tools such as ImportUniverse andMergeUniverse, the customer's KPI Sum-maries 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-timeKPIsAfter the KPI Summaries universe has been updated, reports and dashboards can now be implementedthat expose the Realtime KPI's.


Delays

DelaysThere are two new delay pages.

Delay Category Finder Field Delay Type View

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 Destination Assistant

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


DelayCategory Finder

Delay Category FinderThis page allows you to create,edit and delete delay categories. You can specify a name and color for thedelay, 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 yourMineStar support personnel beforemaking this type of change.


Field Delay Type View

Field Delay Type ViewUse Field Delay Type View to

preview which delay type hierarchies are being sent to whichmachine classes in the field. ensure that the delay types are being sent out to themachine in the correct order.

Note: The Field Delay Type View page presents a snapshot of the delay type hierarchy at the time it isopened. 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 dis-play of themachine of the associated class.

Delay Types and Delay TypeGroups are presented in the same order as they are in the Delay TypeFinder.

A Delay Type is displayed in the tree for that machine class when that machine class is selected on theAssociations 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.


Delay Type Finder

Delay Type FinderIn Delay Type Finder, delay groups and delay types are sorted in the order you leave them in, they are notsorted 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.


Delay Type Editor

Delay Type EditorThe Delay Type Editor has beenmodified 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 themachines,that delay type is included in the list for all types of machine it is associated with. Selecting and clearingthis check box will change the results shown in Delay Type trees for the associatedmachine classes onthe Field Delay Type View page.


SiteMonitor

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


Destination Assistant

Destination AssistantYou are now able to right-click a destination in Destination Assistant and put it on delay using DelayEditor.


DelayWorkOrder References

Delay Work Order ReferencesThe concept of work order references has been added to Delays. This enables you to enter a work orderID, 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 ref-erences are visible in reports TH030 and TM020.

Delay Editor

When creating or editing a delay from the Delay Monitor or Delay Type Assistant, theWork Referencefield is on the Duration tab in the Delay Editor, as shown in the screenshot below. You can enter the workorder reference number for the delay in this field. Saving the delay stores the work order referenceagainst 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 workorder fields. Each field is attached to one of the two delays that the original delay is to be split into. Youcan change either, both, or neither of these fields. The work order field does not have to be populated.



Merging Delays

Whenmerging two or more delays in Delay Assistant the Delay Merger screen displays as shown below.TheWork Order Reference field displays as a drop-down list, which is pre-populated with any work orderreference that was set on any of the original delays.

Note: If none of the delays to bemerged have a work order reference set, theWork Order field will notbe displayed at all.



If a number of delays are beingmerged into a single delay, you can only set a single work order ref-erence. You can select one of the already attached work order references from the drop-down list or youcan 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 workorder reference in the text box to themerged delay.


Delay Activities

Delay ActivitiesDelay activities, also known as Maintenance Bay activities have been added to the Delay functionality inrelease 4.0, Delay activities can be configured and stored in the system for reporting purposes. Themainpurpose for delay activities is for the determination of Mean Time Between Failure (MTBF).

For example, a delay of type Scheduled Down Timemay have a delay activity class of Minor Service.Minor Servicemay have a number of associated delay activity types, for example, ChangeOil, ChangeCoolant, Clear Air Filter etc. When you create a delay you can add a number of delay activities to thedelay.

Delay activities can have delay activity types that are valid for the delay activity class attached to thedelay 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, Descriptionand 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 delayactivity types already entered is shown below.


Delay Activities

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

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

Creating a Delay with Delay ActivitiesDelays may or may not have delay activities associated with them. To add delay activities to a delay, thedelay needs to have a delay type that has a delay activity class associated with it.

Note: This functionality is restricted to Controller, Builder andMaintenance Engineer roles.

You can create andmodify delay activities in the Delay Editor, from either the Delay Assistant or DelayMonitor.

On the Delay Editor, the Delay Activities tab is disabled until a delay type with an associated delay activ-ity class is selected. An example is shown below, in the first screenshot the delay typeWait for Space


Delay Activities

does not have an associated delay activity, in the second screenshot the delay typeWait for Labour hasa 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 theactivity options to choose from. Double-click the Duration field and set the length of the delay in thepopup dialog that displays. If you set the duration of the activity to be longer than the delay duration youare given a warning and asked if you wish to continue or not.

You are also able to add aWork Order Reference number and a Description of the activity if necessary.

Splitting Delays with Delay ActivitiesWhen splitting a delay with associated delay activities, the delay is split initially into equal halves on thenearest wholeminute boundary and delay activity durations are not adjusted. Delay activities are duplic-ated in each of the split delays and can be added, removed or modified on the Delay Splitter dialog.

Merging DelaysWhenmerging delays themerge takes each delay activity where the delay activity type is equal and addthe duration. If there is a delay activity of the same activity type in each of the delays to bemerged thework order reference defaults to the work order of the delay activity in the first delay. If the work orders oneach of the delay activities in each of the delays is different, they will display in theWork Order field in adrop-down list. You are then able to select one of the work orders to use. The descriptions for each delayactivity of the same delay activity type are concatenated. If the delay type is changed for themergeddelay, only the delay activities of types that are present in the delay activity class for the delay type areactive for merging.

All other delay activities are grayed out to indicate they will not be included in themerged delay.


Delay Activities database changes

Delay Activities database changesTablesThe following tables have been added to theMODELschema.

DELAY_ACTIVITY_CLASS DELAY_ACTIVITY_CLASS_TYPES DELAY_ACTIVITY_TYPE

The following tables have beenmodified in theMODEL schema.

DELAYCLASS

The following tables have been added to the HISTORICAL schema.

DELAY_ACTIVITY

The following tables have beenmodified in the HISTORICAL schema.

DELAY

The following views have been added to the HISTORICAL schema;

V_DELAY_ ACTIVITY_CLASS

V_DELAYACTIVITYTYPE

VM_DELAYDELAYACTIVITES


Safety Checklist

Safety ChecklistThe following improvements have beenmade to Safety Checklist Finder and Safety Checklist Editor inrelease 4.0.

The column heading on Safety Checklist Finder has changed fromMachine Categories toMachineClasses.

The tab name on Safety Checklist Editor has changed fromMachine Categories toMachine Classes.

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

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


Safety CheckRecord

Safety Check RecordThe Page Configuration drop-down list has changed in release 4.0. You can now select All, Bad or Unac-tioned.

All

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

Bad

Displays all records that have a status of Bad regardless of whether or not they have been actioned. Res-ults 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.


Shift Change

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


Shift Change Finder

Shift Change FinderWhen creating or editing a shift change in Shift Change Finder, theGeneral tab now allows you to spe-cify messages relating to the created shift change.

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

TheError check box is selected by default. When creating a new shift change there should not beany Error messages.

SelectingWarning or Informationwill display messages of that type. Each group of errors relates tothe 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 theerror occurs.

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

Errormessages display in red text. Warningmessages display in orange text(as shown above). Informationmessages display in gray text.


Shift Change Editor

Shift Change EditorThere 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.


Setting a tie-down load state

Setting a tie-down load stateThe 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 Destinationin theDestination 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 assignmentsthat are within range. All locations on that scheduled assignment are considered where the destinationload statematches the current load state.

For a scheduled assignment to have a valid station to assign the truck to, the truck load statemustmatch at least one of the destination load states for the scheduled assignment. An example of this isshown 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)

ScheduledAssignment 1

Truck 1 A, B and C A and C


Truck 1 A and B A

ScheduledAssignment 3 Truck 1 B None

ScheduledAssignment 1 Truck 2 A, B and C B and C


Truck 2 A and B B


Truck 2 A None


Creating shift change tie-downswith penalty durations

Creating shift change tie-downs with penaltydurationsYou 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 allowsyou to configure a penalty duration, given normal circumstances, for an operator to travel from the tie-down station to the line out or dry room. The value should be an average duration. Penalty durations for astation are not mandatory, and can be left at zero.

Creating a tie-down penalty duration

1. Click the Tie-down tab.

2. Double-click thePenalty column for the relevant tie-down destination. A dialog displays with day,hour andminute 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 thePenalty Column for the relevant destination. TheCount column displays the number of vehiclesthe 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 atstation FUELINT0 at shift change, the assignment enginemust consider a penalty duration of 20minutes, which corresponds to the travel time between FUELINT0 and the line out area.

6. Select theAuto create Tie Down Assignments check box.

7. Click Save. Scheduled Assignments are created as per usual.


Creating shift change tie-downswith penalty durations

8. OpenScheduled Assignments Finder. The Destinations column shows the additional penaltyduration.

Note: Double-clicking a row with a destination tie-down penalty displays the Scheduled AssignmentEditor. If you click theBrowsebutton beside theStationfield, you will notice that the pop-up dialogalso contains thePenaltycolumn. You can double-click the Penalty column to change the penalty dur-ation.

9. Click Save to save your changes and close the page.


How penalty durations are evaluated

How penalty durations are evaluatedOn 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 assign-ment as a whole.

Penalty durations greater than zeromay be different for each destination or location defined in the sched-uled assignment, for example, Workshopmay have no penalty duration and FUELINT may have a 15minute penalty. Assignment applies the penalty duration to these times at runtime when the assignmentengine is determining which tie-down location to assign the trucks to. The diagram below shows how thescheduled assignment window is adjusted.

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


How penalty durations are evaluated

activity forward in time. Assignment then uses this time period to calculate the best assignment for thetruck.


Tie-Down Assignments

Tie-Down AssignmentsWhen a truck has an active scheduled assignment to travel to its tie-down station at shift change it willnot receive any further assignments until the tie-down has ended. If the truck goes off-course during itstravel 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, themachineoperator receives the followingmessage: Current assignment is scheduled tie down. No further assign-ments for shift to which the operator must respond OK to acknowledge themessage. This is capturedin the OFFICEMESSAGE historical table for future reference.


Shift Change AllocationsMonitor

Shift Change Allocations MonitorThe Shift Change Allocations Monitor now has anOn Delay column.

This column displays Yes with the cell colored red if a machine is on delay, and Nowith the cell coloredgreen if themachine is not on delay. This is shown in the screenshot below.


Sending operator messages tomultiple machines

Sending operator messages to multiplemachinesWhen in Fleet Update Assistant, Machine Finder and Site Monitor, you are now able to send operatormessages tomultiple Trucks, Loading Tools and Auxiliary Equipment by selecting contiguous or non-con-tiguous machines, and choosing SendMessage from the right-click menu.


Outbound officemessage timeout

Outbound office message timeoutIn Supervisor, Options > System Options > Pit Link there is a new Option Set called OutgoingMes-sages.

On this page, the outbound officemessage timeout and retry is now configurable, with the defaulttimeout before resend being set at 10 seconds, and the number of retries for sending themessage hasthe default setting of 5 retries.

An example of the page is shown below.



Travel Progress MonitorIn Travel Progress Monitor, the default display is to show the Loading Tools and Processors in alpha-betical 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.



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


Travel ProgressManager drag and drop

Travel Progress Manager drag and dropYou are able to reassign a truck to a particular loading tool in Travel Progress Monitor, using the drag anddrop 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 themouse 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 coloredbased on their suitability.

3. Click Assign to assign the truck to the loading tool.

.


Travel ProgressMonitor configure options

Travel Progress Monitor configure optionsThe following changes have beenmade to the Configure Options dialog on Travel Progress Monitor.

Empty trucksTwo new check boxes have been added to the Empty Trucks Tab in Travel Progress Monitor. The Load-ing 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 Toolson Travel Progress Monitor.

Loaded trucksTwo new check boxes have been added to the Loaded Trucks Tab in Travel Progress Monitor. The Pro-cessor Annotations panel now has the Productivity and Destination check boxes.

Selecting these check boxes will display the Productivity and Destination statistics with the Processorson Travel Progress Monitor.


Travel ProgressMonitor configure options

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


Personnel Editor

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


Site Editor - Rollback option for Surface

Site Editor - Rollback option for SurfaceThe office software now keeps track of the last ten changes to the Surface. This gives you the ability toquickly revert to an earlier version of the Surface file from within Site Editor.

When theUpload all DXF files to the Surface option is run from the Actions > Background Files win-dow, 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 -WedNov 21 09:56:36 EST 2012

Each additional change is appended to the list, up to amaximum of ten changes. When this limit isreached, 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 BackgroundFiles window, then click OK.

A list of the available backups is displayed.


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 Sur-face, 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.


Sending Scheduled Assignments

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


Deleting Scheduled Assignments

Deleting Scheduled AssignmentsYou are now able to delete scheduled assignments from Scheduled Assignment Monitor, by selectingsingle, contiguous or non-contiguous assignments and clicking Delete.


Dragline Operational Statistics

Dragline Operational StatisticsIn 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.


Machine ClassCapabilities

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

When you select this option, the capabilities of themachine's class are inherited by themachine, in thiscase the truck.

Once you have selected the Use Class Capabilities check box, the Capabilities check box is grayed outso you cannot select specific capabilities for themachine.

You can clear the check box to enable the different capabilities for themachine.


Machine Class Editor

Machine Class EditorOn theMachine Class Editor, for eachmachine class that displays theMachine Type tab , there is now aMachine Type drop-down list at the top of the page under the Description field, which allows you to selectthe type of machine.

Once amachine type is selected the Operator Interface field on the Onboard tab will be populated.

Note: This field was previously called theCategory drop-down list on theGeneral tab.


Destination Chooser

Destination ChooserClicking the Destination field on aMachine Assistant page, e.g. Loading Tool Assistant, or MachineEditor page, e.g. Loader Editor, now displays the Destination Chooser, which allows you to filter, searchfor, and select a destination.

Destinations are color-coded as follows.

Blue - within 500m of themachine. See Supervisor, Options > System Options > Machine Tracking >Destinations to change the default distance.

Green - compatible destination.

Orange - have amaterial 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.


Destination Chooser

You can also find a destination by starting to type the name of a destination in the Search field. The panelunderneath the field dynamically updates as you type.

The Destination Chooser can also be found on theMining Block Editor when selecting a Stockpile or aLocked Destination. The Chooser is the same as for machines, except that the filter options are as fol-lows

Combined Source, Sink and Station. Combined Source and Sink. Sinks. This option does not apply to Stockpiles.


Cycle Editor

Cycle EditorWhen viewing the Cycle Editor screen for an auxiliary or truck cycle, the office software now shows thetruck activity, and that it is traveling on an unknown road if themachine loses the GPS signal, rather thanleaving the columns blank. This makes it easier for you to correct the cycles.

Also, the Start Waypoint and EndWaypoint columns have been renamed Start Position and End Pos-ition.

Cycle Editor in release 4.0

Cycle Editor in previous releases


Daylight Saving Timezones

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


On-board hardware configuration

On-board hardware configurationFrom release 4.0, the way amachines on-board hardware is configured in the office software haschanged.

In earlier releases, on-board hardware was configured by choosing the corresponding on-board platform.These platforms could represent the application of themachine, software and hardware combination,software and version or related capability set. Furthermore, it was only the Detect-only basedmachineswhich could be configured to have camera and radars.

From release 4.0, themachine's on-board system is selected by choosing from the list of relevant oper-ator interfaces and add-ons, then specifying the custom configuration.

Operator interface

An operator interface is the physical on-board hardware that is installed on themachine, including

CMPD Navigator G610 Autonomous PC

The operator interfaces available for amachine are based on the office software license, andmachinecategory, e.g. Haul Truck, Scraper, Shovel, etc of themachines 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 andmachine category of themachines 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 aCMPD operator interface. If CMPD is selected as the operator interface, then the available add-ons areCamera, Radars and Proximity. The custom configurations options are VIMS, TPMS, GPS or Detect.



As part of the upgrade process from release 3.x to release 4.0, the office softwaremigrates existing con-figurations to the new approach. Any configurations that could not bemigrated are highlighted in the logfiles and in theMineModel Query. Typically, machines that could not bemigrated have inappropriate con-figurations or themachine category is not correct for the actual machine type, or the onboard is no longersupported.

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 latestversion of the software.

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

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.



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 amachine, refer to the Fleet User manual.


Mining Blocks: Archive Page configuration

Mining Blocks: Archive Page configurationAnew Page Configuration called Archive has been added to theMining Block Finder page.

To view the archive page configuration

1. OpenMining Block Finder.

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

When this is selected theMining Block Finder page shows all mining blocks that can be archived, i.e.they are inactive. Only inactivemining blocks can be archived.

Inactive blocks display as a red icon.

The columns onMining Block Finder can be ordered in ascending or descending order, so you can see ifthemining block is suitable for archiving.

You are able to select multiple rows for archiving.


Assignment OptionsU-Turn policy

Assignment Options U-Turn policyIn Supervisor, Contents >Setup > Assignment Options, on the Assignment Behaviour tab, when select-ing theNever turn-around policy you should be aware that if the truck goes off course, or encounters aRe-assign waypoint, iAssignment recalculates the assignment without considering the prior pathtraveled and concludes that the truck has turned around. You should limit the use of Re-assign way-points to those areas where the trucks are able to turn around.


Data Share

Data ShareData Share provides you with an open interface for integration with your other mining information sys-tems. Closely integrated systems remove the need for duplicate data entry and allow business pro-cesses 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 webservices), and integration can be achieved by using off-the-shelf components. As such there are no pro-prietary 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 oper-ators, machine location, machine activities andmaterials as well as share text messages.

For example, business processes implemented in fleet management systems (FMS), enterpriseresource planning (ERP) and corporate reporting systems can commonly benefit through integration withhigh 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 officesoftware.

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

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


Synchronizing Fleet and Terrain Data

Synchronizing Fleet and Terrain DataWhen 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 thecode.

Job Codes

Fleet Terrain

Name Name

ID ID

Job CodeGroup JobCodeGroup

Operators

Fleet Terrain

Archived Archived

MacPassword Password

Name Name

OID ID

Delay Codes

Fleet Terrain

Archived Archived

Duration DefaultDuration

ID ID

Name Name



Machines

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

Fleet Terrain

Loader Classes Wheel Loader

SurfaceMiner Classes SurfaceMiner

Dozer Unit Wheel Dozer

Grader Unit Motor Grader

Youmust enable synchronization on both Fleet and Terrain.

Data synchronization preparationWhile the synchronization functionality will update records between the systems, it is not intended tohandle initial merging of data between the systems. Mine sites want to maintain consistent IDs betweenthe Fleet and Terrain systems. To ensure that the synchronization process enforces this consistencywith new records, amanual reconciliation between code, operator andmachine IDs across the two sys-tems should be performed before synchronization is enabled. If this is not performed, the synchronizationprocess may merge the existing data in unexpected ways. By performing this manual step of ensuringthe ids are correct in each system, the synchronization process will run smoother andmore 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 whichmust be selected to enable or disable data syn-chronization, 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 theMiddleware button.

3. Select Initial Sync and/or Live Sync.



Selecting Initial Sync then starting the client will pass the information for the entities mentioned abovefrom Fleet to Terrain, and Terrain will then pass its information to Fleet. This process will occur everytime you start Fleet if data has not been synchronized before.

If you select Live Sync, Fleet and Terrain automatically synchronize any changes youmake to any of thefour entities. Only the changemade will be re-synched.

Note: If you change either check box, e.g. you clear Live Sync, youmust restart Fleet to activate thechange.

Machine associationsBoth the DelayType Editor and Job Code Editor have an Associations tab, associatingmachines withdelay and job codes. Only the four machine classes mentioned earlier are able to have their delay and jobcode information synchronized.


Platform

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


Java

JavaThe office software operates with Java 1.6, and will install a copy for its own use. If you are installinganother 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 beinstalled, used or configured.


Memory sizes

Memory sizesJVM 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 amachine with aminimum of 16GB memory, andmay be a suitable initial

configuration for amediummine site. LARGE requires amachine with aminimum of 24GB memory, andmay be a suitable initial

configuration for a largemine site.

Note: As requirements and JVM needs vary considerably between sites, the Implementation andDeployment teams should review and adjust the JVM heap configuration according to their currentbest practices and knowledge. The Supervisor configuration is provided as a convenience to set an ini-tial coarse configuration.

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


GeoServer

GeoServerFrom release 4.0, all capability sets make use of a GIS Server. AGIS Server allows users to share GISresources and provide GoogleMaps style capability.

TheGIS 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 aservice called M*GeoServer.


WebClient

Web ClientFor 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 featuresplease 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.


WebClient

The web client can be accessed at http://:8080/minestar/ using InternetExplorer 8 or greater with Flash 11 or greater.

To ensure there are no issues withWindow security, it is recommended the web client is added to thesafe web site list.

You can do this by doing the following (based onWindows 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.


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 FleetInstall manual for more detailed information.

For SAPdocumentation, please refer to http://help.sap.com/bobip40


Knowledge Network

Knowledge NetworkThe Knowledge Network is a resource for sharing the following BusinessObjects-related topics betweenCaterpillar 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. Trainingmaterials (including AVI files)

6. Report Review Committee presentations andmeetingminutes


Hardware Requirements

Hardware RequirementsThe BOXI 4.0 architecture is substantially different and requires morememory. In addition, the way thatBusinessObjects andMineStar interact leads us to recommend the following server hardware require-ments.

Minimum Server Hardware Requirements (Updated) 4 x 2.0 GHz Core CPU 16GB RAMminimum /recommended 32GB. If you are a Dealer youmay wish to addmore RAM.

Note: Sizing Companion for SAP BusinessObjects Business Intelligence (BI) 4.0 states: In terms oftypical hardware in an enterprise scale deployment of BI 4.0, a node in a BI 4.0 cluster would typicallybe an 8 coremachine with 16GB minimum or equivalent.

Minimum Client Hardware Requirements: 2.0 GHz Core CPU 2GB RAM

Note: Compiled binaries of SAP BusinessObjects BI software is supported on versions of theWin-dows 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 greaterreliance 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.


KPISUMuniverse

KPISUM universePlease note that the KPISUM universe in the standard BIAR file is a reference implementation universeonly. There are several changes in the following sections which you will want to update in your cus-tomized KPISUM_XXX universe.


Universe split for VIMS

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


Support SQL Server

Support SQL ServerMineStar 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). Forexample, the function displayLocalTime() in Oracle does not work in SQL Server. SQL Server has a func-tion DisplayUTCTime() which can be used.

Custom functions required a universe change where objects were prefixed with dbo. e.g. dbo.validDateand dbo.interpolatedSMU


Coordinated Universal Time (UTC)

Coordinated Universal Time (UTC)UTC dates have been incorporated into theMineStar database and BusinessObjects. Time zonesaround the world are expressed as a positive or negative offset from UTC. UTC time does not changewith the seasons e.g. for Daylight savings. It is recommended that you build reports using UTC time vari-ables instead of local time.

There are 405 new UTC objects in theMSTARGE3 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 thedata 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) ShiftBegin:','C','PromptsShifts\ShiftName',mono,free) ,'STARTTIME')) from v_dual)

AND

CYCLE_S_FACT_MAIN.ENDTIME

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

Changed Reports

Changed ReportsGeneral changes affecting all reportsThe following changes affect all reports.

All remaining Health reports have been converted from Deski toWebi. 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 thetime 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. UsingMACHINE_N or PRIMARYMACHINE_N in the query condition of the report causes

performance degradation. Therefore, you should replace the name object with MachineOID in yourCustom reports to improve performance.

Specific report changesHE001p-Health Events

Application improvements to Worst Value allows better reporting of this in BusinessObjects to matchVIMS PC. In addition two objects were added; Worst Value Unit and Worst Value Description.

HE002p-All Events


HE003p-Health Events for Levels 2, 3


HE009p-Trend Summary Report

Context updates to include objects and so that data is not aggreg-ated e.g.

ValidSampleSum= Sum((If IsNull() Then ) In ( , , , , ,,))


Changed Reports

HE010p-Trends-By Machine-Detail

Context updates to include objects and so that data is not aggreg-ated.

HE010d-TKPH Trends-By Machine-Detail

Context updates to include objects and so that data is not aggreg-ated. Wildcard query conditions based on legacy VIMS values. Equivalent IDs were obtained for VIMS3G 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 andadded to the queries.


New Reports

New ReportsValidation VD001_validateTruckCycles VD002_validateShovelCycles VD003_validateAuxCycles

System HealthSH001p-GWM Duplicates Information Shift

This report helps the proactivemonitoring of average duplicate recordmessage count and percentage foreach shift.

SH002d-OnBoard Hardware File version Information

This report helps the proactivemonitoring of the On-board hardware file version information for each shift.

SH003d-Service Restart Information

This report helps the proactivemonitoring of service restart information for each shift.

Health HE004-VIMS Version and Port Numbers

Template Historical TH150-Shift Change Allocation


ChangedObjects comparison

Changed Objects comparisonThe following spreadsheets list the changed options between Fleet 3.1.1 and Fleet 4.0, and should beincluded 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


Real-time KPIs

Real-time KPIsReal-time KPIs provide functionality for you to define and capture KPI data to bemonitored and analyzedin real time. They are defined in xml files in MineStar, which allows the data to be persisted to the data-base and used in BusinessObjects or other third party dashboards. The real-time KPIs are updated everyfew seconds, allowing you tomonitor your mine in real time.

Refer to the Fleet Install manual for more information.


BORefresh end of life

BORefresh end of lifeThe BORefresh tool is now end of life. Refer to Deprecated Features and Functionality for more inform-ation.


Command for hauling Reference Implementation BIAR

Command for hauling ReferenceImplementation BIARFor Command for hauling sites, there is a Reference Implementation BIAR on the Knowledge Networkwhich 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 themanned results. TheBIAR 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 PerformanceManagement 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


Oracle RMAN

Oracle RMANOracle Recovery Manager allows you to backup and recover your Oracle databases, and has the abilityto

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.


Third Party tool changes

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


Windows Task Scheduler

Windows Task Scheduler

Note: From release 4.0, Splinterware System Scheduler has been removed and replaced withWin-dows Task Scheduler.

Windows Task Scheduler is used to control the scheduled tasks that help maintain Fleet functions, andperform routine housekeeping tasks. Windows Task Scheduler provides the same features as Splin-terware System Scheduler to enable you to schedule tasks, and the ability to enable, disable and res-chedule scheduled tasks.

Refer to the Fleet Install manual for more information and details on configuringWindows Task Sched-uler.


FTP Server

FTP ServerTransferring VIMS report files to the office software for new-generation VIMS units requires a local FTPserver for the files to be transferred to. The transfer type is also optionally available on the latest HIM ver-sions.

See the Fleet install manual for detailed installation steps.

Refer to the VIMS compatibility matrix for machines with VIMS 3G.


InstallingMicrosoft SQL Server 2008 R2 onWindowsServer 2008 R2

Installing Microsoft SQL Server 2008 R2 onWindows Server 2008 R2

Note: SQLserver 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 lim-itations apply.

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

Thematarrun commands for database import and export may require the installation of third-partytools.

TheGeoServer feature of the office software (installed with the office software installer) only workswith the office softwares coordinate system when in an SQL Server-only installation. You cannot usecustom coordinate systems. The impact of this is that images imported into the office software needto be in the local coordinate system not in another coordinate system. Furthermore, any integrationwith third party systems should use the local coordinate system.

Other points to note

ThemstarFiles folder on the database server should be shared over the network, with read and writeaccess to the network users.

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

The process for installingMicrosoft SQLServer 2008 R2 onWindows Server 2008 R2 has been addedinto the Install manual as an appendix.


Running Fleet on SQL Server

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


VMSnapshot - Known Issue

VM Snapshot - Known IssueIf you are using VMs and running VM snapshots, there is a known issue with running the VM snapshotswhichmay cause a lack of functionality within the system.

You should disable the VM snapshot functionality.


Installation

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


Installation procedure

Installation procedureCaterpillar recommends backing up the data from your current model before upgrading. Refer to the FleetAdministrationmanual for backup instructions.

Upgrading from release 3.x to release 4.xUpgrading from release 3.x to release 4.x requires a full uninstall and install. This ensures all the servicesand 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 ver-sion 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. SelectmakeDataStores.

8. Click Advanced Options.

9. On theSchema tab selectMajor Upgrade.

10. Click Run.

Note: This process may takemore than tenminutes to complete.

11. Tomake use of GeoServer, you need to configure the following setting in Supervisor. See the FleetAdministration & Configurationmanual for more information.

Mine Boundaries. Options> System Options>Machine Tracking>Mine Boundaries.Optionally, you can also configure the following setting. See the Fleet Administration &Configurationmanual for more information. GPS Coordinate Transform. Options> System Options> Pit Link > GPS Coordinate

Transform. Then select theEnable coordinate transformations check box, and select theappropriate CRS definition. This is set to UTM by default.

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


Installation procedure

13. Click Run.

14. Once the process is complete, restart theM*GeoServer service.

15. Ensure the GeoServer service is running.

16. SelectmakeSpatialStores.

Systems migrating from release 3.1.1 with a Detect license or a pre-release version ofRemote Foreman's Terminal, should select "Update existing spatial stores".

17. Click Run.

18. Restart theM*MineTracking Service.

Note: Theminemodel is synched with GeoServer when theM*MineTracking service starts.

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

Exception running makeSpatialStoresIf you receive an error runningmakeSpatialStores, refer to Troubleshooting GeoServer.


Zip upgrade installation

Zip upgrade installationIf you are upgrading fromMineStar 3.x to 4.0 youmust follow the installation procedure for upgradingfrom the installer.

The Zip Upgrade option is only applicable if you have already installedMineStar 4.0.

Zip upgrade release artifactsYou need the following files to perform the upgrade.

Zip upgrade file mstarx-xx-x.zip

Web deployment

Documents

CAT FLEET & HEALTH V4.0.pdf