Вы находитесь на странице: 1из 165

Table of Contents

Chapter 1: An overview of MZone 4..........................................8

Welcome to MZone 4 ............................................................................. 8


Prerequisite software ............................................................................................ 8

1.2 How to access MZone 4 ..................................................................... 8


The landing page ................................................................................................... 9
The welcome screen .............................................................................................. 9

1.3 The MZone home page ..................................................................... 10


A. The navigation bar .......................................................................................... 11
B. MZone 4 logo ................................................................................................... 11
C. Global Search Tool .......................................................................................... 11
D. Settings ............................................................................................................ 12
E. Quick Short Cuts ............................................................................................. 13
F. Status Grid with Graph................................................................................... 13
G. Versions............................................................................................................ 14
H. UTC time setting ............................................................................................. 14
I. User Logged on ................................................................................................ 14

Chapter 2: Maintenance tasks .................................................. 15

Maintenance Introduction ................................................................. 15


Basic Navigation ........................................................................................ 15
A. Deactivating units ........................................................................................... 15
B. Link to Workspace/MRM ................................................................................ 16
C. Deleting ............................................................................................................ 16
D. Editing............................................................................................................... 16
E. Add new ............................................................................................................ 16
F. Find Option ....................................................................................................... 16

2.2 Data Structure ..................................................................................... 16


MZone User Group Structure Diagram ............................................................. 17

2.3 Groupings .............................................................................................. 18


2.3.1 How to add Groups on MZone 4 ............................................................. 18

Page 2 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
2.4 Vehicles .................................................................................................. 19
2.4.1 Adding a New Vehicle ............................................................................... 19
2.4.2 Editing a Vehicle ........................................................................................ 21
2.4.3 Adding a Vehicle Group ............................................................................ 23
2.4.4 Adding a Vehicle Type .............................................................................. 23
2.4.5 Adding a vehicle Time Profile .................................................................. 25
2.4.6 How to Share a Vehicle ............................................................................ 26
2.4.7 Using the Share Code ............................................................................... 29

2.5 Drivers .................................................................................................... 30


2.5.1 Adding a New Driver ................................................................................. 30
2.5.2 Adding a New Driver Profile..................................................................... 32

2.6 Users ....................................................................................................... 33


2.6.1 Adding a New User .................................................................................... 34
2.6.2 Adding a New User Group ........................................................................ 37

2.7 Places...................................................................................................... 40
2.7.1 Adding a New Place................................................................................... 41
2.7.2 Adding a New Place Group....................................................................... 42
2.7.3 Adding a New Geofence Action ............................................................... 43
2.7.4 Adding Geofence Type .............................................................................. 45
2.7.5 Assigning Geofence actions ..................................................................... 46
2.7.6 Downloading Geofences to MHub devices............................................. 48
2.7.7 How to view Geofence download statuses ............................................ 50

2.8 Fuel .......................................................................................................... 51


2.8.1 Adding a New Fuel Entry .......................................................................... 51
2.8.2 Adding a New Fuel Batch ......................................................................... 53

2.9 Events ..................................................................................................... 53


2.9.1 Adding a New Event Type Group ............................................................ 53
2.9.2 Editing an Event ........................................................................................ 54

2.10 Security Groups ................................................................................ 56


2.10.1 Adding a New Security Group ............................................................... 57

2.11 MRM ...................................................................................................... 58


2.11.1 Adding a New Customer ........................................................................ 59
2.11.2 Adding a Job ............................................................................................ 63

Page 3 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
2.11.3 Adding a new Job category ................................................................... 65
2.11.4 Adding a New Depot ............................................................................... 66

2.12 Roles & Rights .................................................................................. 69


2.12.1 Adding New Role & Rights ..................................................................... 70
2.12.2 Pre-defined System Roles...................................................................... 71

2.13 Miscellaneous .................................................................................... 72


2.13.1 Translations .............................................................................................. 72
2.13.2 Adding a New Generic Time Profile ...................................................... 74

Chapter 3: Workspace tasks ...................................................... 75

Workspace an Introduction .............................................................. 75


3.1 Data Grid (II) ................................................................................... 76
3.1.1 Vehicles Tab .......................................................................................... 76
I. Events ............................................................................................................ 79
II. Poll .............................................................................................................. 80
III. Trips ............................................................................................................ 80
IV. Unit Controller........................................................................................... 82
V. Dispatcher ..................................................................................................... 83
3.1.2 Drivers Tab ............................................................................................ 86
3.1.3 Places Tab .............................................................................................. 88
3.1.4 Geofence Entry/Exit Tab ..................................................................... 90
3.1.5 Fuel Tab ................................................................................................. 91
3.1.6 Alerts Tab............................................................................................... 92
3.1.7 Messaging Tab ...................................................................................... 95

3.2 Map Data Control (III).................................................................. 96


3.2.1 Selected Vehicles – Active Track ....................................................... 96
3.2.2 Plotted Entities ...................................................................................... 97
3.2.3 Map Settings ......................................................................................... 99

3.3 Mapping (IV) .................................................................................... 99


3.3.1 Map Control ................................................................................................ 99
3.3.2 Shape Draw Control .................................................................................. 99
3.3.3 Trip Control .............................................................................................. 100
3.3.4. Mapping icons ......................................................................................... 100

Page 4 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
Chapter 4: Mobile Resource Management (MRM) ........... 102

MRM an Introduction ........................................................................ 102


4.1 MRM Data Grid ............................................................................... 103
4.1.1 Jobs Tab ................................................................................................ 103
4.1.2 Resources Tab ..................................................................................... 104
4.1.3 Customers Tab .................................................................................... 112
4.1.4 Depot Tab ............................................................................................ 114
4.1.5 Gantt Chart Navigation ...................................................................... 115

4.2 Job Assignment Window ............................................................ 117


4.2.1 Auto-Scheduling ................................................................................. 119
4.2.2 Manual Job Assignments ................................................................... 123

4.3 Job Management ........................................................................... 124


4.3.1 Interpreting jobs on the Gantt ......................................................... 124
4.3.2 How Job details are populated ......................................................... 126
4.3.3 How to communicate to drivers ....................................................... 128

4.4 Additional Reading (Auto-Scheduling) ................................. 129


4.4.1 Shortest Distance – Load balanced ................................................. 130
4.4.2 Shortest Travel Duration – Load balanced ..................................... 130
4.4.3 Shortest Distance – Max resource utilization ................................ 130
4.4.4 Shortest Travel Duration – Max resource utilization .................... 131
4.4.5 Least Cost per Kilometre – Load balanced..................................... 131
4.4.6 Least Cost per Kilometre – Max resource utilization .................... 131

Chapter 5: Reports ...................................................................... 132

Reports an Introduction .................................................................. 132


5.1 Basic Navigation ............................................................................ 132
5.1.1 Selecting report criteria ..................................................................... 133
5.1.2 Report Bar ........................................................................................... 133
5.1.3 Static Report bar ................................................................................ 134
5.1.4 Report Scheduling .............................................................................. 134
5.1.5 Report Structure ................................................................................. 135

5.2 Vehicle Reports .............................................................................. 136

Page 5 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
5.1.1 Vehicle Event....................................................................................... 136
5.1.2 Vehicle Event Detail ........................................................................... 136
5.1.3 Vehicle Trip Detail .............................................................................. 137
5.1.4 Vehicle Trip Overview ........................................................................ 138
5.1.5 Daily Tachograph ................................................................................ 138
5.1.6 Vehicle Alert Detail ............................................................................. 139
5.1.7 Temperature Detail ............................................................................ 140
5.1.8 Fuel Entry Detail ................................................................................. 141
5.1.9 Daily Trip Event Detail ....................................................................... 141
5.1.10 POI Analysis per Vehicle ................................................................ 142
5.1.11 FMS Detail ........................................................................................ 142
5.1.12 Fuel Distance ................................................................................... 143
5.1.13 Vehicle Exception Detail ................................................................ 143
5.1.14 Accident Reconstruction Detail ..................................................... 144
5.1.15 Reckless Driving Detail .................................................................. 144
5.1.16 Reckless Driving Summary ........................................................... 145

5.3 Vehicle Group Reports ................................................................ 145


5.3.1 Vehicle List........................................................................................... 145
5.3.2 Vehicle Activity Summary ................................................................. 146
5.3.3 Vehicle Exception Summary ............................................................. 146
5.3.4 Vehicle Utilization (Simplified) ......................................................... 147
5.3.5 Daily Trip Event Summary ................................................................ 147
5.3.6 Vehicle Time utilization (Simplified) ................................................ 148
5.3.7 Fuel Entry Summary .......................................................................... 148
5.3.8 Fuel Consumption trends .................................................................. 149
5.3.9 POI Duration Summary ..................................................................... 149
5.3.10 Green band Summary.................................................................... 150
5.3.11 POI Activity ...................................................................................... 150
5.3.12 POI Analysis per Place ................................................................... 151
5.3.13 Temperature Summary ................................................................. 151
5.3.14 Distance Exception ......................................................................... 152
5.3.15 FMS Summary ................................................................................. 152
5.3.16 Temperature Exception ................................................................. 153
5.3.17 Fuel Consumption Summary ........................................................ 153
5.3.18 Vehicle Alert Summary .................................................................. 154

Page 6 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
5.3.19 Vehicle Communication ................................................................. 154
5.3.20 Vehicle Trip Summary.................................................................... 155

5.4 Driver Reports ................................................................................ 156


5.4.1 Driver List ............................................................................................ 156
5.4.2 Driver Activity Summary ................................................................... 156
5.4.3 Driver Event ........................................................................................ 157
5.4.4 Driver Trip Detail ................................................................................ 157
5.4.5 Driver Rating Summary ..................................................................... 158
5.4.6 Driver Rating (Simplified) ................................................................. 158
5.4.7 Driver Rating Trend ............................................................................ 159
5.4.8 POI Analysis Driver per Place ........................................................... 159
5.4.9 POI Analysis per Driver ..................................................................... 160
5.4.10 Driver Exception Detail .................................................................. 160
5.4.11 Driver Rating ................................................................................... 161

5.5 Depot Reports ................................................................................ 162


5.5.1 Vehicle Itinerary ................................................................................. 162
5.5.2 Job Analysis ......................................................................................... 162
5.5.3 Depot Activity ...................................................................................... 163
5.5.4 Driver Debriefing ................................................................................ 163
5.5.5 Depot Performance ............................................................................ 163
5.5.6 Task Analysis....................................................................................... 164
5.5.7 Task Detail ........................................................................................... 164
5.5.8 Task Summary .................................................................................... 165
5.5.9 Vehicle Task Job performance .......................................................... 165

Page 7 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
Chapter 1: An overv iew of MZone 4

Welcome to MZone 4

Thank you for choosing MZone, the comprehensive and user-friendly web-based
fleet management tool. You can now look forward to reduced costs, increased
fleet utilisation, and enhanced driver and asset safety.

Prerequisite software

Please note that you need to have Microsoft Silverlight installed on your
computer before you can use MZone 4.

You will automatically be prompted to download and install this application the
first time you attempt to log on to MZone. Silverlight is a small 4MB download
which should take no longer than 5 minutes to complete.

1.2 How to access MZone 4

MZone is a web-based application. This means that you can access it from any
internet-enabled workstation, anywhere, anytime.

To access MZone, simply type the following URL into your internet browser.
Clients hosting their own MZone 4 servers locally will have a different link
assigned, please consult your local administrator for further details.

http://us.MZoneweb.net/scope.MZone.web

Page 8 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
The landing page

This will take you to the landing page, and you can log in by using the username
and password that was supplied to you by your local administrator:

You can tick the “Remember Me” checkbox if you want the computer to save
your login details. However, this is not recommended if you share your
workstation with other users.

Enter your username and password and click on Login.

The welcome screen

Once you’ve clicked on Login you will be taken to the welcome screen, where
you have the option to launch the MZone application, switch to another
username if you have administrative rights, read the release notes or log out.

To launch MZone 4, click on Launch Client:

b b
This option will log you into the MZone 4 application.

This allows you to login as another user within your


assigned group, this is an administrator privilege.

This option allows you to view the new changes in


versions being updated on the MZone 4 application.

This option will log you out of MZone 4.

The application will take a moment to load. Note loading times do vary between
PC’s as certain factors such as new versions and frequency of usage on a PC will

Page 9 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
affect loading times. Some data is locally cached for better performance of the
application.

Once MZone has finished loading you’ll be presented with the home page. The
home page gives you a comprehensive overview of your fleet’s current status,
and provides you with shortcuts to the most commonly used functionality.

1.3 The MZone home page

A
B C D

G H I

Page 10 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
A. The navigation bar

This is the navigational bar that is always visible, no matter where you are in the
MZone application. This allows you to easily switch between different task
menus.

Maintenance
Here you can add, update and delete all entity types on MZone 4, such as
vehicles, users and drivers (see Chapter 2 for further details)
Workspace
This is your main working area; from where you can monitor the movements
of your entire fleet and perform all mapping related actions (see Chapter 3
for further details)
MRM (Mobile Resource Management)
This functionality allows you to manage your resources and automate
delivery scheduling. It is available as an optional add-on to MZone 4. (See
Chapter 4 for further details)
Reports
Here you can view detailed reports to assist you in managing your fleet. The
report groups include:

B. MZone 4 logo

This is the default logo of the MZone 4 application; this logo can be changed to
your own respective logos.
(Please view section 2.6.2 for an example on how to do this.)

C. Global Search Tool

Next to the task menu buttons is a handy search feature which you can use to
find specific entities within the MZone 4 application. This is a very quick and
easy way for new users to locate data on the MZone 4.

Page 11 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
1

1. Search results grouped by entities


2. Search results within a selected category
3. The option to edit the search entity

D. Settings

On the top right of the navigation bar you’ll see two buttons, namely Settings
and Logout. You can use the Logout button to log out of the application at any
time.

Page 12 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
1. This allows you to change your password
2. Option to disable which will prevent alerts from popping up/audible.
(Please view section 2.9.2 for more details)
3. This indicates how many lines of data that will be presented to you on any
grids displayed within the application as a default.
 The Global option reflects all the grids in the Maintenance, MRM
and Reports section
 The Workspace option only affects the grids within the workspace
section.

4. This indicates how often the Polling screen refreshes and displays the new
data received.
(See section 3.1.1 on the screen effected.)
5. The Primary refresh interval periodically updates information on the MZone
4 application on the following:
 Checking of new incoming alerts
 Updating Active Tracked Vehicle positions
 Updating of unscheduled jobs
6. The Gantt chart is specific to MRM in which it refreshes to indicate any new
updates to drivers job Tasks. This option sets the intervals.

E. Quick Short Cuts

The shortcuts menu is prominently displayed on the home page, and allows you
to access commonly used entities from each of the main task menus.

F. Status Grid with Graph

The status bar gives you a high level overview of your entire fleet at a glance,
such details include:

You can also make use of the dropdown to view different graph options which
include:

Page 13 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
An example of the “Favorite Vehicle Trip Summary for the Past 2 weeks” is displayed
below.

G. Versions

Versions are indicated on the bottom left corner. The color indicators indicate the
status of the MZone 4 application:

H. UTC time setting

The users UTC time adjustments are shown on the bottom of the window. The
UTC time that matches with the PC local time will be indicated in WHITE and
when it does not match the PC’s local time then the time is indicated in RED

This simply highlights to users if the UTC needs changing as all time adjustments
are done on MZone 4.

I. User Logged on

The bottom left of the screen indicates which user is logged on. Even using the
impersonate option. Multiple logins using the same username is allowed.

Page 14 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
Chapter 2: Mai ntenan ce task s

Maintenance Introduction

All entities, whether you are adding, editing or deleting are maintained in this
section. Typical entities include the following:

Basic Navigation

Editing entities

All entities on the MZone 4 application can be maintained quickly and


easily and typically an editing window will look like this:

F E

A. Deactivating units

This option is only available/visible to a user if the User Group logged into contains the
original vehicle added. (i.e. vehicles that are not shared). If available, this option allows
the user to deactivate a particular vehicle unit device. The deactivation is necessary in
the event of an accident whereby the tracking device is removed and utilized in another
vehicle. MZone 4 only allows 1 unique MProfiler ID to be registered at any one time. By
deactivating the ID, it will allow the same ID to be added for another vehicle on the
system. The deactivated unit will still be available for historical referencing.

A confirmation code is required to deactivate a unit, simply fill it in and then click
validate to continue.

Page 15 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
(Note: Once deactivated, this process is irreversible)

B. Link to Workspace/MRM

Whenever available this option allows users to select the entity and go directly to
workspace, whereby avoiding the need to search for it when you are in the
Workspace or MRM sections.

C. Deleting

This option deletes the selected entity. Note this option is not reversible once
deleted it will not be retrievable.

D. Editing

Once an entity has been selected you can quickly edit by selecting the edit icon.
An editor will appear with its current details and you can simply change the
details as required.
(Please view the add new entity section for the entity concerned for further assistance on editors)

E. Add new

Selecting this icon will add the new entity concerned into the MZone 4
database.

F. Find Option

This option allows the users to find any selected entity quickly and easily. Simply
type in the text field what you are looking for and click on the Find button.

2.2 Data Structure

The data structure is setup in such a way that the user can be limited to certain
groups as well as restrictions on certain functionality on MZone 4. This is best
illustrated as follows:

A user group can contain multiple users which is then given access to the
entities they are responsible for by way of Security Groups. Once a user is
granted access entities then we further specify what type of features they can
access within the MZone system by way of Roles and Rights.

(Please view section 2.10.1 on Security Groups and section 2.12 on Roles and Rights)

Page 16 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
MZone User Group Structure Diagram

Page 17 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
2.3 Groupings

All entities must belong to their respective groups so that in conjunction with
Security Groups users can be given access on a group by group basis.

2.3.1 How to add Groups on MZone 4

To add a new group, access the maintenance section, the entity you
would like to add a group to, like drivers example and then click on the
add driver group button.

B C

A - A description given to this group can be entered here.


B - Available drivers that can be added to this group.
C - Identify which Drivers will belong to this Driver Group by simply
moving the Drivers from the left pane to the right pane, using the
arrow indicators as shown as B above.

Other groupings include:

Page 18 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
2.4 Vehicles

New Entity options are grouped on the top

General maintenance options are grouped below

2.4.1 Adding a New Vehicle

To add a new vehicle, access the maintenance section, vehicles and then
the Add Vehicle button.
A A A

C D

A A A

Page 19 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
A. Vehicle Information

I. Description
A user defined description of the vehicle being added.
II. Vehicle Type
The type indicates what vehicle category it belongs to such as “trucks” or
“passenger vehicles” etc. These types are pre-defined by the user.
(Please view section 2.4.4 for more details on how to define them)

III. Model Year


The year the vehicle was bought, 2009 etc.
IV. Home Depot
The default depot where the vehicle belongs, note this field is related to
MRM. And will only be utilized for task planning. If no Depot is selected,
the vehicle in question will not be available to MRM specifically on the
Gantt Chart.
(Please view section 4.1.5 for more details on the Gantt Chart)

V. Mileage Limit
A set amount of kilometers/miles can be set per vehicle. In the event of a
vehicle exceeding such thresholds a notification is automatically notified by
the MZone application to the user in the form of an event as well as in
reports. The report can be found is in section 5.3.14.
VI. Registration
The registration or number plate of the vehicle concerned can be entered
in this field.
VII. Vehicle Time Profile
A pre-defined time profile can be associated to a vehicle. Once defined the
user has the option to view utilization reports that are available to identify
when vehicles are being used outside the time profile assigned. This time
profile is also utilized for MRM task scheduling.
(Please view section 2.4.5 for more details on how to define time profiles)
VIII. Event Type Group
A pre-defined group of events can be assigned to a vehicle. This is to limit
the type of events being displayed on the MZone application. Limiting
events are predominately used when filtering data for end user clients in
differing user groups.
(Please view section 2.9.1 for more details on how to define event types)

IX. MProfiler Unit ID


A unique ID that has been assigned to the MHub device, the field is an
auto-fill field which needs to be identified. Once identified (MZone will
attempt to list the unit ID you have specified) only then will you be able to
successfully assign a MHub to a vehicle in MZone 4. If the unit ID you
have added is not listed, ensure the Unit is online and reporting to the
MProfiler server. Further assistance can be provided by contacting your
local administrator.

B. Dates

I. Purchase Date - The date the vehicle was bought


II. Start Date - The date where the vehicle will be active on MZone.

Page 20 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
III. COF Date - Certificate of fitness or its service intervals
IV. End Date - The anticipated date where the vehicle will be inactive on
MZone 4. This field can be left blank if the end date is not
known or not applicable.

C. Notes - A custom area where you can enter any information specific to this
vehicle.
D. Custom Image - A custom image can be loaded per vehicle for easy
identification, limited to 20kb upload image.
E. Use Share Code - If a share code has been assigned you can click on this
button insert it here like this below:
(Please view section 2.4.7 on how to share a Vehicle)

F. Vehicle Groups

Identify which Vehicle group this vehicle will belong to by simply moving the
groups from the left pane to the right pane, using the arrow indicators as shown
as G above. A vehicle must belong to at least one or more vehicle group/s.

F F

2.4.2 Editing a Vehicle

Note: when editing a vehicle, 2 additional tabs namely Events and


Accessories are available for further setup.

To edit a Vehicle, access the maintenance section, vehicles and then the
Vehicle Maintenance button.

Page 21 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
Every individual event can be
configured per vehicle.

Note: setting this section up


will override user group
settings under event types.

Simply rename the event if


desired, set an alert level and
an icon as indicated below.

Generic I/O can be renamed to the actual device connected


such as the Input 1 = Panic button as indicated.

Simply click on the Edit icon and rename as needed.

(Please view section 2.9.2 for more details)

Page 22 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
2.4.3 Adding a Vehicle Group

To add a new Vehicle group, access the maintenance section, vehicles and
then the Add Vehicle Group button.

A
F

A. Description
A description given to this group can be entered here.
B. Available Vehicles
Listed vehicles here can be added to this group by simply moving them from
the left pane to the right.
C. Selected Vehicles
Vehicles that has been selected to be a part of this group being created.
D. Pane Selection icons
Pane icons to move vehicles from left to right.

2.4.4 Adding a Vehicle Type

To add a new Vehicle Type, access the maintenance section, vehicles and
then the Add Vehicle Type button.

Page 23 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
A

A. Details

I. Description
A user defined description for the Vehicle Type being added.
II. Make
The make of the vehicle such as Volvo, MAN etc.
III. Model
The specific model of the particular vehicle such as the FH16 or TGS can
be added here.
IV. Cost Per Kilometre
A cost can be assigned to the vehicle, this cost refers to the cost of
running the vehicle per kilometre which can be an overall cost consisting
of wear and tear, fuel, driver costs etc.

B. Parameters

I. Travelling Consumption
Is the consumption of fuel used by the vehicle per distance covered in
L/100km or Miles/Gallon.
II. Idling Consumption
Is the consumption of fuel used by the vehicle while stationary also in
L/100km or Miles/Gallon.

Page 24 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
III. Green Band RPM High/LOW
Green band is defined as the vehicles optimal RPM range. A high and low
value is indicated for reporting purposes.
(Please view section 5.3.10 for the Green Band Report)

IV. Vehicle Not Reported Threshold


This field indicates the maximum time in seconds in which a vehicle must
report within. Exceeding this threshold will illuminate the Last Event
Timestamp in workspace that the threshold has been reached. So if a
value of 3600s was set, then in workspace vehicle reporting positions
within 1 hour will be displayed as per normal, thresholds exceeding 3600s
will be shown in RED.

V. Service Interval
A service interval can entered in KM or Miles. Once reached the MZone
application will notify the user via Alerts.
VI. Max Loading Unit
This sets the maximum number of objects that a particular vehicle can
load. The maximum capacity is entered here. As differing goods has
differing measurements or criteria, the field is generic and any unit
description can be entered here.
(Note: this field is used for the MRM module only)

2.4.5 Adding a vehicle Time Profile

To add a new Vehicle Time Profile, access the maintenance section,


vehicles and then the Add Vehicle Time Profile button.

Page 25 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
A. Description
A user defined description for the time profile can be inserted here.
B. Selected Operating Times (Specific Hours)
In the grids that are displayed, a user is able to specify exactly what hours
Hours can be set for a particular day, simply click and drag the sections as
required. Selected hours are highlighted in red and what is referred to as the
“inside hours”
. C. Operating Hours (Flexible Hours)
The other alternative is to have flexi hours by selecting the second radio
Radio option the grid becomes inactive and the Operating Hours portion
is now made available. Here a user can enter a set hour/s. In using this
option, referring to the example above, on Wednesdays vehicles assigned to this
Time Profile may not exceed 8 hours of total drive time.

2.4.6 How to Share a Vehicle

Vehicle sharing enables the use of vehicles to be shared across User


Groups. This sets the environment whereby the main User Group can be
setup with all vehicles concerned and then subdivided into their respective
subset of other Client User Groups. This can be best illustrated as follows:

(Please view section 2.6.2 for more details on how to create new User Groups)

Page 26 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
To Share a Vehicle, access the maintenance section, vehicles and then the
Vehicle Sharing button.

D
C

E
B A

A. Vehicle Sharing Tab


This tab will allow the user to create the share code needed for vehicle sharing.
B. Available Vehicles
This section lists the vehicles that are available for sharing; simply click on the
vehicle to select it.
C. Reuse Fields
Once a Vehicle is selected, the user will have the option to keep the existing set
of data currently on the vehicle in question or not. Simply use the check boxes as
needed.
D. Expiry Date
Every share code has an expiry date if not used; simply set a date for this. By
default expiry dates are set to one week.

Page 27 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
E. Create Share Code
Once all the selections are done, simply click on the to complete
the process. A confirmation will acknowledge the request as shown below.

(Note: Once a code is created you will need to log into the User Group which you want to share the
vehicle too. Please view the below sections on how to view and administrate this code.)

F. Pending Tab
This tab allows the user to view all the current unassigned share codes
together with its expiry date.
G. Vehicle Sharing Code
This code is the vehicle sharing code that will be needed in order for it to be
shared into another User Group.
H. Show Selected Share Code
Click on this button to view the full share code. Simply copy the code and use
it in another User Group.
(Please view section 2.4.1 on how to Add a new Vehicle)

(Note: Ensure you only copy the code as indicated above, i.e. df366093-c15e-4940-82c1-223ac03879f8)

Page 28 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
I

I. History
This section shows where the vehicles have been shared; it allows the user to
keep track of his/her fleet.

2.4.7 Using the Share Code

To add the new share code, log into the user group that you would like to add the
vehicle too and click on the Add New Vehicle option under maintenance Section.

In this editor click in the and enter the code as indicated J below.

Click on validate to complete and Mzone will validate the code. If successful
complete the Adding of the vehicle as per normal.
(Please view section 2.4.1 for more details on how to add a new vehicle)

If not successfully the following will be shown: Ensure the code is correct by
reviewing the pending tab as shown in 2.4.6 F.

Page 29 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
2.5 Drivers

New Entity options are grouped on the top

General maintenance options are grouped below

2.5.1 Adding a New Driver

To add a new Driver, access the maintenance section, drivers and then
the Add Driver button.

B D

A. General Tab
Allows the user to capture the drivers’ information onto the MZone 4 application
B. Personal Information
Details such as name and ID numbers can be entered here.

Page 30 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
C. Contact Information
Details such as Home number’s and Work number’s can be captured here.
D. Custom Image
An image of the driver can be uploaded here.

E. Dates
Drivers can be set to be active (Start date) and inactive (End Date) on the MZone
application by entering the dates where the drivers will be monitored. Leaving the
end date blank will allow the driver to be monitored indefinitely.
F. Identification
I. Driver Key Code – This key code will link the driver keys to a name. i.e.
2431 = John Doe
(Driver ID as configured on the Dallas key needs to be entered here)
II. Cost Per Hour - This field allows the user to assign a Cost per hour to the
driver.

G. Notes
Any driver specific details can be inserted here.

Page 31 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
G H

H. Driver Groups
Identify which Driver group this driver will belong to by simply moving the groups
from the left pane to the right pane, using the arrow indicators as shown as G
above. A Driver must belong to at least one or more driver group/s.

2.5.2 Adding a New Driver Profile

Driver Profiles allows a user to measure the performance of a driver as


well as a group of drivers according to the exception events they incur.
Our reports will utilize the Driver Profiles created to view such ratings.

(Please view section 5.4 for further details on how to view these reports)

To add a new Driver Profile, access the maintenance section, drivers and
then the Add Driver Profile button.

Page 32 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
C

A D

B E

A. Driver Rating Profile


A user defined description for the driver rating profile can be inserted here.
B. Event Type
We rate drivers according to 6 exception events as listed in the image.
C. Count
The count indicates the maximum number of exceptions allowed.
D. Weight
The weight indicates the severity that is assigned to the exception.
E. Percentage
After the Count and Weight has been configured, a final percentage is assigned
and is calculated as follows:

Using the Speed exception as the example, for every speeding violation that
occurred, the driver will lose 4.57%. The maximum a driver will lose on his/her
profile with speeding is 50.3%.

All drivers start with a 100% record.

2.6 Users

New Entity options are grouped on the top

General maintenance options are grouped below

Page 33 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
2.6.1 Adding a New User

To add a new User, access the maintenance section, Users and then the
Add User button.

A
E

A. General Tab
The general tab captures the entire user’s information as well its preferences.
B. Identification
Personal details are captured in this section.
C. Settings
The user’s preferences are selected here.
(Note: The language drop down can be modified to include your local language if desired, please view
section 2.13.1 for further details)

Page 34 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
D. Contact details
All contact details are entered in this section.

E. Time Zones
All timestamps are adjusted on the MZone application depending on the users
UTC offsets. To change the UTC setting, highlight the text bar and enter the
offset, the field will auto populate the options to you. Simply select the time zone
that is appropriate for you as indicated below.

F. Login Details
Every user on the system requires a unique login; this can be done in this
section.

Page 35 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
G

G 1

G. Roles
Identify which Role/s this user will belong to by simply moving the groups from
the left pane to the right pane, using the arrow indicators as shown as 1 above. A
User must belong to at least one or more Role/s.
(Please view section 2.12.1 for more details using Roles)

H H

H. Security Groups
Identify which Security Group this user will belong to by simply moving the
groups from the left pane to the right pane, using the arrow indicators as shown
as 1 above. A User must belong to at least one or more Security Groups.
(Please view section 2.10.1 for more details on Security Groups)

Page 36 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
I

I. Default Extent
The default extent allows the user to select his/her preferred view of the map so
that every time they login, the map area selected will always be shown as a
default in the workspace section. This can be achieved in 2 ways; one as
indicated in I above, you can enter Lats & Long to locate specific areas of the
map and 2 which is indicated in K above, you can use the map control to
manually move the map to its desired location.
J. Get Main Extent
Clicking on this option will retrieve the current Map Zoom Extent in workspace,
within the user current session.

2.6.2 Adding a New User Group

User Groups independent groups that are created for differing clients, this
ensures data is not shared across different User Groups.

To add a new User Group, access the maintenance section, Users and
then the Add User Group button.

Page 37 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
A

B C

A. Group Information
Details of the new group can be entered here.
B. MZone logo
A user is able to brand the MZone website according the clients they are
presenting to or simply offer a more customized experience. Simply uncheck the
default MZone logo option and click on the upload button to insert a logo of your
choice.
C. Report Logo
The same can be applied to all reports; this section brands the reporting section
of the MZone application.
(Note: Uploading logos is restricted to 20KB in size as indicated below.)

D. Exchange Configurations
An exchange account is not compulsory for every User Group created. An
exchange account is an account on the MProfiler server which the MZone
application uses to connect so that the correct client data is directed to the

Page 38 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
correct User Groups. No exchange account is required in the event the user is
making use of Vehicle Sharing.
(Please view section 2.4.6 for further details on Vehicle Sharing)

To add a new exchange account, simply click on the Add Configuration button and
complete the details as listed below:

(Note: Exchange account details will only be available to your local administrators, please consult
them for further details.)

1
E E

E. Modules
MZone is separated into 2 main sections:
I. Default – The core of MZone 4 for vehicle tracking access.
II. Distribution Management – Allows the MRM to be utilized by the
user group.

To setup simply identify which Module is required, move the modules from the
left pane to the right pane, using the arrow indicators as shown as 1 above. The
User Group must be assigned to at least one Module.

Page 39 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
F

F. User Group Administrator


Every new User Group creation will always have at least one administrator to
admin the new user group. Simply fill in the details of the new administrator as
indicated in G above.

2.7 Places

This section allows users to create various shapes onto the maps on the MZone
application. Once shapes are created, users will then be able to manage those
designated areas such as No-Go zones, POI and Boundary limits. Advanced
features such as Geofencing and Zone management can be setup to monitor
such areas.

New Entity options are grouped on the top

General maintenance options are grouped below

Page 40 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
2.7.1 Adding a New Place

To add a new Place, access the maintenance section, Places and then the
Add Place button.

A. Place Information
Details of the POI being created can be entered here. The place type dropdown
allows the user to categories the POI being created. Category options include:

I. POI
A place of interest, if vehicles are within or close proximity to these
POI’s, then it is included in the location descriptions within the
MZone application. A shape of the Scope offices was drawn and
categorized as POI will result as follows:

Page 41 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
II. Area
In much the same way POI this category is generally a much larger
shape geographically. Shapes categorized in this category will not
be listed in the locations. An example as listed below:

B. Maximize Icon
Simply click on this button to enlarge the map.
C. Map Controls
(Please view section 3.3.1 for more details)

D. Shape Controls
(Please view section 3.3.2 for more details)

E
E

E. Place Groups
Identify which Place Group this Place will belong to by simply moving the groups
from the left pane to the right pane, using the arrow indicators as shown as 1
above. A Place must belong to at least one or more Place Groups.

2.7.2 Adding a New Place Group

To add a new Place Group, access the maintenance section, Places and
then the Add Place Group button.

Page 42 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
A

1
C C

A. Description
The description for the Place Group can be entered here.
B. List Places
The list place drop down can be used as a filter to list the available places as
indicated in C above.
C. Select places
Identify which Places this Place Group will contain by simply moving the Places
from the left pane to the right pane, using the arrow indicators as shown as 1
above. A new Place Creation without any places is permitted.

2.7.3 Adding a New Geofence Action

Geofence Actions allows a user to alter the behavior of vehicles (MHub


devices) while they are in or out of predefined places on MZone 4
governed by the Geofence actions. These are a set of software rules that
can be utilized on all places created in MZone.
(Note: Geofence Actions are simply to define the rules, where the rules actually apply is setup in
section 2.7.5)

To add new Geofence Actions, access the maintenance section, Places and
then the Geofence Actions button.

Page 43 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
A

B
D

A. Descriptions
A user defined description for this Geofence option can be entered here.
B. Active Recovery
A rule can be created that when a vehicle enters/exits a POI it will set the
Recovery mode on/off. Recovery mode will override all settings on the MHub
device and force the MHub to report every 30 seconds for 2 hours unless
manually turned off again. When a unit goes out of Recovery mode, the unit will
revert back to it normal operations.
To set this up simply use the drop down and select the action either ON or OFF.
C. Alert level
Alerts in Geofence actions operate the same way as normal alerts in MZone.
When a vehicle enters/exits a POI, MZone will again override all current settings
and all subsequent events that comes through to MZone it will flagged as an
alert.
To set this up simply use the drop down and select either Low or High alert.
(Please view section 2.9.2 for further details on Alerts)

D. Output Controls
Outputs can be controlled by Geofence actions; this allows the MZone application
to automatically turn ON/OFF the outputs while a vehicle is entering/exiting a
particular POI.
A typical instance where this is used is when a vehicle enters a No-Go Zone the
central locking will be activated automatically.
To set this up, simply use the desired output dropdown and select the options
available to the outputs.
E. E-mail
Email notification can be sent to recipients when the transgression occurs. Simply
use the checkbox and fill in the details as indicated below.

Page 44 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
I

II

III

IV

I. E-mail details
Emails can be sent it to multiple recipients, a subject and message
can also be setup in this section. Email can be further customized
in such a way that vehicles in violation of such rules are identified
in the email itself. This is done using templates and described
below.
II. Templates
Templates can be added from the drop down as indicated. The
following templates can be added: Vehicle, Place and Timestamp. If
inserted into the email as shown above, what the MZone
application will do is insert the actual vehicle description, actual
place description and its actual timestamp of the transgression.
III. Help
Clicking on these options will give an explanation on how templates
are utilized online for your convenience.
IV. Insert Template
Clicking on this button will add the selected template into the
email.

2.7.4 Adding Geofence Type

A Geofence type categorizes the Geofences into convenient groupings in


order to set further specific hardware rules based on the Geofence type.
Hardware rules are on the MHub device itself; please consult your local
administrator for further details on hardware rules setup.

To add new Geofence Type, access the maintenance section, Places and
then the Add Geofence Type button.

Page 45 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
A

A. Type
On the MHub device, Geofence groupings are numbered from 1 – 10, therefore
groupings of 10 types are permitted as a maximum.
Simply insert a value from 1 – 10 in this field to set a particular type.
B. Description
From an MZone perspective a description allows a user to set a description for the
type assigned.
So as an example Type 1 = No-Go Zones, Type 2 = Government Buildings etc.

2.7.5 Assigning Geofence actions

Once Geofence actions have been created we are now ready to assign
these rules from either the Place or Vehicle Groups.

A. Editing Place Groups

To enforce Geofence Actions edit the Place\Vehicle Group where the rules
are to be applied. An example in indicated in A below.

Page 46 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
B

B. Selected Places
By editing the Place Group in question, the selected places are the places where
the rules will be applied.

C E

C. Geofence Details
I. Vehicle Group
Here we specify which groups of vehicles are to be monitored
against the rules selected.

Page 47 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
II. Entry Action
Here we select the action MZone will take when the specified
vehicles enter the places.
III. Exit Action
Here we select the action MZone will take when the specified
vehicles exits the places.
IV. Geofence state
Geofences can be set as hardware, Software or both.
(Please the next section 2.7.6 for further details)
V. Event Type overrides
Clicking on this button will direct you to the Event type editor. This
enables a user to override existing settings for a particular event
while the vehicle is in a monitored POI. The override is not
permanent and will revert back to normal when the vehicle exits
the monitored POI.
(Please view section 2.9.2 on how to configure an event type.)

D. Dates
Geofence Actions can be confined to dates; this means that the actions will only
be enforced during the dates specified in these fields.
E. Time Profile
With time profiles, a user has the ability to enforce these rules to only apply in
certain times during the day/night as dictated by the time profile.
(Note: you can click on the add new icon next to the field to add new time profiles)
F. Assign option
Once all the fields have been configured, click on the assign button to confirm the
Geofence enforcements. This will then insert the rules into the rules action
window in G above. Now simply click save to complete the process.

2.7.6 Downloading Geofences to MHub devices

With reference to 2.7.5 C IV above, Geofences can be sent down to


Geofence enabled MHub devices as hardware Geofences.

Page 48 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
A A

Using the Geofence state drop down as indicated in A above the following
options are available:

Rules are enforced by using POI’s From MZone only, nothing is sent
down to the MHub devices

Rules are enforced by MZone as well as hardware rules as governed


by types. The physical shape is sent down to the MHub devices as
co-ordinates.

Rules are enforced by MZone as well as hardware rules as governed


by types. The physical shape is sent down to the MHub devices as
co-ordinates.

The Debounce indicates how long the unit should wait before sending the
Entry or Exit event.

This option allows you to add new Geofence types quickly.

If the Geofence State was selected as Hardware only or Both, this


option will become available. Here we classify what the Geofence type
will be based on the Place Group selected.

(Please view section 2.7.4 for further details on how to add Geofence Types)

Page 49 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
2.7.7 How to view Geofence download statuses

To view Geofence download statuses, access the maintenance section,


Places and then the Add Place Group button.

B C D E

A. Search bar
The search bar allows a user filter by any vehicle or place group. It also allows a
user to view the status of a specific vehicle.
B. Vehicle
It lists the vehicles that currently have Geofences to be downloaded.
C. Timestamps
Shows various timestamps of Geofence download status.
D. Status
Shows the statuses of the Geofence downloads
Geofence downloaded successfully

Geofence download still pending

Geofence download failed

E. History
Select the history icon of the vehicle to view its entire Geofence download history.
MZone will bring a new popup window as indicated below.

Page 50 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
2.8 Fuel

New Entity options are grouped on the top

General maintenance options are grouped below

2.8.1 Adding a New Fuel Entry

To add a new Fuel Entry, access the maintenance section, Fuel and then
the Add Fuel Entry button.

Page 51 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
A

A. Fuel Batch Entry Editor


I. Fuel Batch
This is an auto-fill field; simply enter the fuel batch where this fuel
entry will belong. You can also use the add icon to create a new
fuel batch.
II. Vehicle
This is again an auto-fill field; here we select the corresponding
vehicle for the fuel entry.
III. Date
The date where the fuel entry occurred can be inserted here. You
can make use of the calendar icon for reference.
IV. Unit of Measurement
This can be entered in metric or imperial units; this is normally
defined in the user’s editor of the person adding the fuel entry. If
the default unit displayed is not correct you can go to the user
editor and make amendments, however you can use the dropdown
and select the UOM of your choice.
V. Total Fuel
The total fuel entered can be entered here.
VI. Currency
A default currency is displayed this is not correct; you can make
amendments in the user group editor. You can however use the
dropdown to select the currency used for the payment of the fuel.
VII. Total Cost
The actual cost of the fuel can be entered here.
VIII. Reference
A user defined reference can be entered here.
IX. Odometer
If the odometer was recorded at the time of the fuel instance, it
can be entered here.

Page 52 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
X. Description
A custom user defined description can be entered here.

2.8.2 Adding a New Fuel Batch

To add a new Fuel Batch, access the maintenance section, Fuel and then
the Add Fuel Batch button.

A. Descriptions
Fuel batches are like groups that contain multiple fuel entries. Batches can be
created for per month, quarter etc. A user defined description for the batch can
be entered here.

2.9 Events

All events in MZone can be grouped and allows the user the ability to customize
any event that gets received. The user also has the ability to rename events as
well assigning specific icons for easy identification on maps.

New Entity options are grouped on the top

General maintenance options are grouped below

2.9.1 Adding a New Event Type Group

To add a new Event Type, access the maintenance section, Events and
then the Add Event Type Group button.

Page 53 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
A

B
1

A. Description
A user defined description for the event group can be entered here.
B. Available Event Types
A listed of available events are shown which a user has the option to define which of
those events will be selected as part of this event group. Simply use the arrow icons
as shown in 1 above to move the identified events from the left pane to the right.
C. Selected Event Types
Once the events have been selected and saved, the user then has the ability to use
the new event group to filter events to show only what is listed in the event group
selected. Typical areas when the event type groups are used are in workspace and
reports.

2.9.2 Editing an Event

To edit an Event Type, access the maintenance section, Events and then
the Event Type Maintenance button.

Page 54 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
A

A. Editing an Event
Under the event type maintenance section, an event can be customized by clinking
on the edit icon. An editor will appear as a popup as indicated below.

B. Description
The default event description can be changed to a user defined description; events
that get commonly renamed are generic I/O and third party events.
E.g. Input 1 = Panic Button
C. Alert Level
Each and every event that comes through to MZone can be setup as an alert. 2 main
types of alerts can be set as indicated below.

Page 55 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
Low = Events set as a low alert will still constitute as an alert and be listed in the
alerts table. It will however not have a popup.
High = Events set as a high alert will be populated in the alerts table as well as an
Audible popup that appears on the bottom left of the browser. This popup will
not disappear until such time the operator has processed the alert.

(Please view section 3.1.6 for more details)

D. Map Markers
A custom map icon can be assigned individual events as a means of easy
identification on maps. Simply select the desired icon and click Save to complete the
event editing process.

E.g. Trip Shutdown event

2.10 Security Groups

Security Groups are controls that determine which user/s will have access to
which vehicles in their respective User Groups. In summary Security Groups
control what users can and cannot see.

Security Group forms the basic level access to entities, once identified MZone
will then utilize Roles & Rights for specific feature access.
(Please view section 2.12.1 on Roles & Rights)

Page 56 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
2.10.1 Adding a New Security Group

To add a new Security Group, access the maintenance section, Security


Group and then Add Security Group button.

B
D

I. Description
A user defined description for the security group can be entered here.
II. Selecting the user
Identify which user is to be included in this security group by simply moving it from
the left pane to the right pane, using the arrow indicators as shown as 1 above.
III. Groups
Security Groups can set basic level access to 4 entity groups namely:
I. Vehicle Groups
II. Driver Groups
III. Customer Groups
IV. Depot Groups
These groups, if selected will determine what the user can access. An example is
illustrated below:

Page 57 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
Any users identified for this
security group will NOT be able Any users identified in this
to have access to vehicles in this security group WILL BE able to
group. have access to these vehicles
contained in these groups

The same will apply to Driver/Customer and Depot Groups.

2.11 MRM

Mobile Resource Management, a fleet management tool that effectively captures


and schedules tasks for resources. To make use of this module ensure that you
are subscribed to this first. For subscription details please consult your local
administrator for more information.

3 fundamental entities are required for the usage of MRM:


I. Resources
For resources to one made available under the MRM section you need to
ensure the MHub device in the vehicle is subscribed to the MRM service,
without this subscription no resources will show in the MRM section. Again
please consult your local administrator.
II. Customers
The MZone database requires a list of existing customers in order to
process jobs for them. Each and every customer has a POI Shape assigned
to it indicating the customer’s physical location. With this identified MRM is
able to determine arrival times, departure times etc.
III. Depots
The MZone database requires a list of depots from which to operate from.
These are normally starting points of drivers to their respective customers.
Each and every depot has a POI shape assigned to determine its physical
location as well as an additional servicing POI shape. This servicing POI
shape indicates the depots geographical range in which the depot can
make the deliveries to. This means that MRM will endeavor to identify the
Customer and select a Depot in which its servicing area is covered. This is
one of many optimization aspects that MRM caters for.

Page 58 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
New Entity options are grouped on the top

General maintenance options are grouped below

2.11.1 Adding a New Customer

To add a new Customer, access the maintenance section, MRM and then
the Add Customer button.

Page 59 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
I. General Tab

A
E
B

A. Description
A user defined description of the customer can be entered here.
B. Reference
An account number/Customer reference number of the customer can be entered
here.
C. POI options
When assigning a POI shape to a customer you can either select an existing POI in
the MZone application or opt to draw a new one by making use of the map interface
on the right. Simply use the radio buttons to make the selection.
D. Image
A custom image of the customer can be uploaded for easy identification.
E. Map Control
Please view section 3.3.1 on how to navigate using the map controls.
F. Shape Control
Please view section 3.2.2 on how to navigate using the shape controls.

II. Contacts Addresses Tab

Using the Add contact/Add Address buttons as indicated in G & H


respectively, allows the user to capture customer’s details which will
be reflected on the PDA as an additional Scope accessory.

Page 60 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
G
D

H
D

III. Notes Tab

Under this tab any additional customer specific notes can be entered
here. Simply click on the Add Note button as indicated in I below.

I
J

Page 61 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
IV. Hours and Settings Tab

J. Customer Operating Hours


A time profile is assigned to a customer to identify when it is appropriate for
MRM to schedule selected jobs for the customer concerned.
K. Off-load Rate
The off-load rate refers to the time it takes on average to remove the goods from
the vehicle to the customer site.

L. Setup Time
This time refers to the time it takes the driver to arrange for the goods to be
dropped off once he/she arrives. Considerations include, going to reception and
locating the person to accept the goods, signing off etc.

V. Customer Groups

Identify which Customer Group which this customer will belong by simply moving
the Customer Groups from the left pane to the right pane, using the arrow
indicators as shown as M below.

Page 62 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
M

2.11.2 Adding a Job

To add a new Job, access the maintenance section, MRM and then the Add
Job button.

This window will show any duplicate


jobs on the system if the details
entered on the left are similar to the
jobs already on the system. From here
a user is able to either delete the
duplicate job, edit it etc.

The Include History check box option


will also display all historical jobs
associated with the client if checked.

Page 63 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
I. Customer
An auto-fill field, simply identify the customer to whom the job is requested for.
The option to add a new customer can be selected by using the add icon.
II. Job Description
Here we describe the job details; this should some thing simple to interpret as
drivers will be viewing this line of information if a PDA is available in the vehicle.
III. Reference
Here we enter the waybill number/customer account number etc into this field for
tracking purposes.
IV. Job Category
This is a type of distribution, whereby assigning a job category to this job will
enable MRM to assign the correct type of vehicle to perform this job.
E.g. A job to deliver frozen prawns will require a refrigerated delivery vehicle.
(Note: the vehicle will need to be assigned a category first before MRM is able to identify such
scenarios. Please view section 2.11.3 on how to do this.)

V. Priority
A priority can be assigned to a job by utilizing the dropdown box. The options
available are Low, Medium and High. Each and every job is color coded depending
on the priority selected. This enables the operator to handle the job accordingly.

Low = BLUE
Medium = ORANGE
High = RED
VI. Available Depots
This dropdown allows the user to identify the depot that will be assigned to the
job. The dropdown assists the operator to select the correct Depot by listing it in
ascending kilometer. Therefore the closest depot will always be listed first. In
addition to this customers that fall within servicing areas of the depots will have
preference as indicated below.

E.g. in the image below a depot servicing area is highlighted in blue with 2
customers falling within its distribution area.

Page 64 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
VII. Loading units
This indicates how many quantities of goods are to be delivered. So using the
example with the prawns, we need to know how many boxes of Prawns the client
has requested. E.g. 30
So we inset the loading units here.
VIII. Job Duration
This field will auto populate once the loading units have been filled in. Once we
have the number of units along with the off-load rate assigned to the customer,
plus the setup time, MRM will then be able to determine a duration time.

Therefore: (number of units x off-load rate) + setup time = duration time


(Please view section 2.11.1 IV for more details on off-load rates and setup times)

IX. Job window


Once a customer has been selected the job window options are as follows:

None = If no job window is selected the MRM will assign the job firstly
based on the date then its priority.
Custom = A custom date allows the operator to set a specific date and time
for the delivery. E.g. 2009/10/08 @ 14:22PM
Date = The date option allows the operator to specify a delivery date
only, then MRM will schedule the job on that date at the first
available time slot.

2.11.3 Adding a new Job category

To add a new Job Category, access the maintenance section, MRM and
then the Add Job Category button.

Job category creations are simply categories that segregate vehicles and
jobs according to its category description. MRM will then only assign Jobs
to resources based on its job category matching.

Page 65 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
2.11.4 Adding a New Depot

To add a new Depot, access the maintenance section, MRM and then the
Add Depot button.

I. General Tab

D
A

A. Description
A user defined description of the depot can be entered here.
B. Reference
An account number/Depot reference number of the customer can be entered here.
C. POI options
When assigning a POI shape to a depot you can either select an existing POI in the
MZone application or opt to draw a new one by making use of the map interface on
the right. Simply use the radio buttons to make the selection.
D. Map Control
Please view section 3.3.1 on how to navigate using the map controls.

Page 66 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
II. Depot Areas

E. Depot Areas
When this tab is selected, use the Shape Controls to draw the servicing area for the
Depot. Once the shape is drawn, the new listing will be shown as indicated in F
above. To rename the servicing area, simply click on the new entry.

III. Contacts Addresses Tab


Using the Add contact/Add Address buttons as indicated in F & G
respectively, allows the user to capture customer’s details which will be
reflected on the PDA as an additional Scope accessory.

Page 67 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
G

VI. Notes Tab

Under this tab any additional customer specific notes can be entered
here. Simply click on the Add Note button as indicated in H below.

Page 68 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
VII. Hours and Settings Tab

I. Depot Operating Hours


A time profile is assigned to every depot to identify its operating hours. MRM will
then ensure the selection of depots applied only to the available depots.

VIII. Customer Groups

Identify which Depot Group which this Depot will belong by simply moving the
Depot Groups from the left pane to the right pane, using the arrow indicators as
shown as J below.

2.12 Roles & Rights

Roles & Rights is our second access level after Security Groups, which controls
all features within the MZone application.

Page 69 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
2.12.1 Adding New Role & Rights

To add new Role, access the maintenance section, Roles & Rights and
then the Add Role button.

A user defined description for the role can be inserted in A above.

Under this editor every feature of MZone is conveniently categorized and


optioned. A user simply checks the features the user is able to access.

In B on the left the users assigned to this role will have access to:

I. Active Tracking
B II. Poll Vehicle Group

Options not selected will not be available.

When features are not available


the options will be greyed out as
illustrated in C above.

Page 70 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
D

D. User Selection
Identify which Users will belong to this Role by simply moving them from the left
pane to the right pane, using the arrow indicators as shown as 1 above.

2.12.2 Pre-defined System Roles

A. System Roles
I. Maintenance User
A maintenance user administers the MZone database and controls all
entities on the system. Full access is granted to the Maintenance and
workspace functions.
II. Mapping User
Primarily a workspace user only the mapping functions in workspace is
granted.

Page 71 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
III. Operator
This role is primarily assigned to MRM users as full MRM functions are
granted. Certain Workspace functions are allowed as related features work
hand in hand with MRM such as Active Tracking.
IV. Reporting User
Full accesses to the reporting functions are granted. Users assigned to this
role normally are data analyzers.
V. User Group Administrator
As the name states this role is grants complete access to all features on
the MZone application. At least one administrator must be assigned to a
User Group.

B. Deleting
Deleting system roles is not permitted; custom roles created however are permitted
to be removed.
C. Editing
To assign users to system roles, simply edit the role and assign the users as
required.
(Please view section 2.12.2 on how to do this)

2.13 Miscellaneous

New Entity options are grouped on the top

This option is only available to System


Administrators

2.13.1 Translations

The MZone application is fully translatable to any language of your choice.


If a particular language is not available, a user may opt to translate. Our
translation facility draws all possible terms on our MZone site for you to
do your translations online. Granting of translation access can only be
done by System Administrators. For more information or to get access to
translate, please contact your local administrator.

To access the translations, access the maintenance section first,


Miscellaneous and then the Translation button.

Page 72 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
A

G
C

A. Selecting your language


The TO and FROM dropdowns can be selected based on the users preference. If a
language has been translated already you are able to translate from say Spanish to
Chinese. Using English as the primary language to translate is not compulsory. If a
set of language has already been translated it will be listed in these dropdowns
automatically.
B. Get Translation
Once the options have been selected you need to retrieve the languages so that you
are able to translate, simply click on this button to retrieve.
C. Search Option
To look for a specific phrase to translate simply insert it here and click on Find and
check box for match exact if required.
D. Translation Sections
The translations are conveniently sectioned for the users so that they are aware of
where the phrases are located within the MZone application.
E. Translation subcategories
These subcategories are color coded to indicate if all the translations are complete
within any given category.
Subcategories indicated RED indicates incomplete translations and GREEN indicates
complete.
F. Actual Translating
To perform any translating actions simply click next to the phrase from which you are
translating to as indicated in F above.

Page 73 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
G. Save
Ensure all your hard work is saved by clicking on the save button. No auto save
feature is available, so we suggest you save every 10 – 15 minutes. Once saved the
translations will never be lost, this enables users to pace himself/herself and not
needing to complete the translations all is one session.

2.13.2 Adding a New Generic Time Profile

To add a new Time Profile, access the maintenance section, Miscellaneous


and then the Add Time Profile button.

A. Description
A user defined description of the time profile can be entered here.
B. Grids
To use the grids simply click and drag on the grids to select the times which will be
indicated in RED
C. Clear option
Clicking on this button will reset grid.

Page 74 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
Chapter 3: Wo rkspa ce task s

Workspace an Introduction
MZone is a comprehensive, powerful Mobile Resource Management platform
designed for logistics companies and fleet operators. The platform encompasses
management tools to reduce operational and maintenance costs, increase mobile
resource utilization, efficiently plan and schedule delivery and service
assignment and overall enhance mobile resource safety. MZone is browser
based, presenting the operator with user friendly access to complex activities
such as planning and scheduling. The platform boasts incorporation of the latest
technology tools, providing a robust, versatile and sophisticated application.

To access the workspace section, click on the workspace button as indicated in I


below.

II

III

IV

Page 75 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
3.1 Data Grid (II)

3.1.1 Vehicles Tab

A
B

C D E

A. Vehicle Groups

This grid lists all Vehicle Groups that a user is permitted to access. A
favourite vehicle group is a default group for every user on the system.
This group allows a user to custom list his/her favourite vehicles into
this list.

The star option when selected (highlighted yellow) will re-order your
I
groups first by favourite then alphabetically. This is done in I as
II
indicated.

II as indicated can be used to determine how many groups to list.

III allows you to search for your Vehicle Groups.

III

B. Vehicle details
IV V VI VII

III

II

Page 76 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
I. Add to favorites
Any vehicles can be added to favorites by selecting this icon; upon
selecting it will automatically add the vehicle into the favorites Vehicle
Group for easy administration.
II. Alerts summary
This indicator shows the number of alerts that the vehicle has generated.
Clicking the indicator will allow the user to action and process the alerts.
(Please view section 3.1.6 on how to do this)
III. Active POI
This indicator shows the current POI that the vehicle is currently in.
Clicking the indicator will automatically plot active POI on the map as
shown below.

IV. Ignition
If the ignition indicator is lit (shown in orange), this informs the user that
the vehicle is currently driving (ignition state ON)
V. Status
The status icon allows the user to gain access to the vehicle by having
control over the outputs and various other actions as indicated below.

c
a

Page 77 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
a. Vehicle Description
The current status of the vehicle will be listed are listed here.
b. Output controls
Here a user is able to manually turn Outputs ON and OFF etc.
(Please view section 3.1.1 IV for more details)
c. Vehicle Enablement
A user is able to manually disable a vehicle by simply clicking on the disable
button and confirming it. Depending on how it is physically connected,
disabling a vehicle could entail disconnecting the fuel pump or ignition relay.
Contact your local administrator for more details.
d. Vehicle Recovery
This option allows a user to set recovery mode ON of OFF. Vehicle recovery
simply means if turned ON, it forces the MHub device to report to MZone
every 30 seconds for up to 2 hours, unless manually turned OFF.
(Note: normal operations of the MHub device will be restored once the action has been turned off)
e. View Geofence Download
Clicking on this button will direct you to the viewing of Geofence Download
History of the vehicle selected.
(Please view section 2.7.7 for Geofence Downloads)
f. Last Known I/O
This view gives you a current status of your current I/O, lit indicates that the
I/O is currently ON or Enabled.

g. Commands sent
This window shows you the current commands that a user has sent to the
device. This will also indicate whether the command was sent successfully of
not.

VI. Event Type


This column indicates the latest event received from the vehicle.
VII. Last event Timestamp
This time stamp indicates the time the last event was received. Note, the
time stamps can be configured to thresholds. These thresholds indicate
whether the timestamps are displayed in RED or not.
(Please view section 2.4.4 on how to set this up)

C. Action buttons
I. Plot
The plot button allows any selectable entity/data to be placed onto the
map for viewing. Simply select the entity/data first, (you can hold down
the ctrl key to select multiple entity/data to plot at once) then click on the
plot button.
II. Active track
This option allows you to active track vehicles on the map; this means that
this action will place the vehicles in the active track window and auto-
update positions automatically in real-time.

Page 78 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
D. Mapping buttons
When a mapping function is selected, it will overlap the entity selected, to
unselect the mapping function again simply click on the map function button
concerned again.

I. Events

The events option allows a user view a list of vehicle/s events over a
specified time. The user also has the option to filter the event data as
required.

b
a
c
6 step process:

a. Vehicle identified for the event search


b. Select an event group filter if required
c. Select your date range
d. Click on search to complete the search process.
e. Select the event/s you want to plot
f. Click on plot to view in map.

f e

Page 79 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
II. Poll

Polling a vehicle allows a user to update any vehicle position in real-time.


Once actioned, MZone will send a request via the MProfiler to the MHub
device for a new position. This process will normally take around 40
seconds to complete.

a 4 step process

a. Select the vehicle to be polled


b. Confirm the polling action
c. Process will be begin with status indication
Status indication explained in E below.
d. Once action is complete, click on plot to view
the poll location on the map.

III. Trips

The trip function allows a user to analyze all historical trip information
from vehicles and the option to replay trips on the map.

3 step process
b
a. Identify the vehicle to view trip history.
b. Select the date range to view
c. Click search to execute.

The list of trips results will be listed as indicated in d below.

Page 80 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
Click on this icon to view d
specific details of a particular
trip as indicated in e below.

To place a trip onto the map simply


select the trips you want plotted and
click on the Plot button.

To select multiple trips simply hold


down the CTRL key.

A trip plotted will be shown as


indicated in f below.

Page 81 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
f

(Please view section 3.3.3 on how to use the Trip Controller)

IV. Unit Controller

This option allows a user to activate outputs of the MHub device. These
generic outputs controls can be connected to various accessories on a
vehicle to be activated remotely. Such accessories can include central
locking, Boot lock etc.

Page 82 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
V. Dispatcher

This option allows a user to locate any vehicles within a specified Location,
POI, Address, latitude & longitude and positions on a map.

Step 1 – select your options

Select an option by using one of the radio buttons as


indicated. Depending on the selection the relevant
options will appear.

Step 2 – Search by Point of Interest or Place

B
B

A. POI Search Bar


Enter an existing POI as the point in which to search for your closest vehicles, then
click on the search button to confirm.
B. Search Results
The results of your POI search will be listed here, simply select your POI in which you
would to do a search on.
C. Search Range
Enter the search range you would like to do a search around the location you hae
identified. Then click on find to complete the search. Please proceed to step 3 below.

Page 83 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
Step 2 – Search by Location Finder

D. Location bar
Enter the address of the location you want to locate your nearest vehicle.
E. Mapset selection
In the event a user group has more then one mapset, simply make your mapset
selections here.
F. Results
Upon selecting the search button the results of your search will be diaplayed here,
simply select the option that you are looking for by highlighting with your mouse.
G. Search Range
Enter the search range you would like to do a search around the location you hae
identified. Then click on find to complete the search. Please proceed to step 3 below.

Step 2 – Search by Latitude & Longitude

H. Co-ordinates
Enter the co-ordinate of the location you would like to do a search on.
I. Search Range
Enter the search range you would like to do a search around the location you hae
identified. Then click on find to complete the search. Please proceed to step 3 below.

Page 84 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
Step 2 – Search by Position on the Map

J. Location on Map
Selecting on this button allows a user to use the mouse and manually select a
location on the map and retrieve a co-ordinate.
K. Search Range
Enter the search range you would like to do a search around the location you hae
identified. Then click on find to complete the search. Please proceed to step 3 below.

Step 3– Search Results

L. Dispatcher vehicles
The Vehicles within the specified search range will be listed here in order of distance
from the identified location.
M. Plot Button
A user has the option to plot the results of the dispatched vehicles onto the map by
clicking on the plot button. Multiple vehicles can be selected by holding down the
CRTL key. Plotted vehicles will be displayed as indicated below.

Page 85 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
From here the user/operator is able to use the registration and driver details to
contact the person and direct them to the location as needed. Al dispatcher
vehicles are indicated with a blue truck for easy identification.

Dispatcher Vehicle

E. Maintenance buttons
The maintenance buttons is an extension to the maintenance section of
MZone. This allows quick access to editing the entity tab selected.

Depending on the entity tab selected the Add, Edit and Delete options will
take you to their respective editors.
(Please view section 2.4 for more details)

3.1.2 Drivers Tab

A
B

D
C

Page 86 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
A. Driver Groups

This grid lists all Driver Groups that a user is permitted to access. The
favourite driver group is a default group for every user on the system.
This group allows a user to custom list his/her favourite drivers into
I this list.

The star option, when selected (highlighted yellow) will re-order your
groups first by favourite then alphabetically. This is done in I as
II indicated.

II as indicated can be used to determine how many groups to list.

III allows you to search for your Driver Groups.

III

B. Drivers

II III II IV

I. Add to Favorites
Any drivers can be added to favorites by selecting this icon; upon selecting
it will automatically add the driver into the favorites Driver Group for easy
administration.
II. Registered to vehicle
When a driver is identified to a vehicle i.e. driver key tag was detected on
to a vehicle then the icon as well as the description of the vehicle is listed.
If a driver is registered to multiple vehicles then the drivers will be listed
multiple times.
III. Driver Key Code
MZone will map the key code detected to a drivers name by using this key
code as inserted by a user.
(Please view section 2.5.1 for more details on how to add and setup key codes)
IV. Registered to Timestamp
The time at which the driver key tag was detected will be shown here.

Page 87 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
C. Plot Button
The plot button allows any driver to be placed onto the map for viewing.
Simply select the driver first, (you can hold down the ctrl key to select
multiple drivers to plot at once) then click on the plot button.
(Note: Only drivers who have been registered to vehicles may be plotted)

D. Maintenance Buttons
The maintenance buttons is an extension to the maintenance section of
MZone. This allows quick access to editing the entity tab selected.

Depending on the entity tab selected the Add, Edit and Delete options will
take you to their respective editors.
(Please view section 2.5 for more details)

3.1.3 Places Tab

B
A

D
A. Place Groups

I as indicated is a grid that lists all Place Groups that a user can view
POI’s from.
I
II II as indicated can be used to determine how many groups to list.

III allows you to search for your Place Groups.

III

Page 88 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
B. Places
Depending on the place group selected, the relevant Places will be listed in
this section. A user is then able to place these POI’s onto the map for
viewing. Multiple places can be selected by using holding down the CTRL key
as shown below.

C. Plot Button
The plot button allows any POI to be placed onto the map for viewing. Simply
select the POI first then click on the plot button. The will be displayed as
shown below.

D. Maintenance Buttons
The maintenance buttons is an extension to the maintenance section of
MZone. This allows quick access to editing the entity tab selected.

Depending on the entity tab selected the Add, Edit and Delete options will
take you to their respective editors.
(Please view section 2.7 for more details)

Page 89 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
3.1.4 Geofence Entry/Exit Tab

A. Vehicle Groups

I as indicated, is a grid that lists all Vehicle Groups that a user is


permitted to access. If Geofence actions have been setup for these
vehicle groups then selecting them will display all entry and exits of
those vehicles within a group.
I
II II as indicated can be used to determine how many groups to list.

III allows you to search for your Place Groups.

III
(Please view section 2.7.5 on how to assign Geofence actions to them)

B. Geofence Detected Entry/Exit

A list of entry and exits will be displayed for the Vehicle group selected.

I II III IV V

Page 90 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
I. Vehicle
The vehicle being monitored will be displayed here; you can use the columns
to sort alphabetically.
II. Geofence Description
The POI where the vehicle is entering will be listed in this column. You can
use the columns to sort alphabetically.
III. Time Entered
The event detected entering the POI will be indicated as well as the
timestamp.
IV. Time Exited
The event detected exiting the POI will be indicated as well as the
timestamp.
V. Duration
The total duration the vehicle was within the POI will be displayed here.

C. Plot button
The plot button allows any Geofence Entry/Exit to be placed onto the map for
viewing. Simply select the vehicle entry/exit detail first then click on the plot
button. The map will indicate the first event detected inside and the first
event detected outside the POI as displayed below.

POI

Entry

Exit

3.1.5 Fuel Tab

C
Page 91 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
A. Fuel batches

I as indicated, is a grid that lists all the Fuel batches currently on the
MZone system.

II as indicated can be used to determine how many Batches to list.


I
III allows you to search for your specific fuel batches.
II

IV

III

IV Clicking on the ellipses dot button allows a user to perform


an advanced search using the date selector as indicated.
(Note: fuel entries are then used in reports to determine L/100KM, Fuel trends etc please view some the
reports related for this in sections 5.3.8 & 5.3.17)

B. Fuel Entries
Listings of fuel entries based on Fuel batch selected are indicated here.
(Please view section 2.8.1 on how to add fuel entries)

C. Maintenance buttons
The maintenance buttons is an extension to the maintenance section of
MZone. This allows quick access to editing the entity tab selected.

Depending on the entity tab selected the Add, Edit and Delete options will
take you to their respective editors.
(Please view 2.8 for more details)

3.1.6 Alerts Tab

D B C

Page 92 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
A. Alert Search Bar

I II III IV V

I. Search Period

The search period allows a user to isolate a search according


the options as indicated. Simply click on the desired option.

Complete the rest of the options that follow if needed and


click on find button to complete the search

II. Alert Level

Alert levels can be utilised by a user to list only LOW of High alerts
to be displayed in the alerts tab. Simply select the desired option
as indicated.

Complete the rest of the options that follow if needed and click on
find button to complete the search

III. Vehicle

An auto-fill field, this option allows a user to


list only alerts for a particular vehicle.

Complete the rest of the options that follow


if needed and click on find button to
complete the search

IV. Status

The status of alerts can also be filtered as either processed or


not. Processed alerts are alerts that have already been
actioned/addressed by a user/operator. Unprocessed alerts are
alerts that still need to be actioned/addressed, such as adding a
note.
Complete the rest of the options that follow if needed and click on
find button to complete the search

(Please view section 3.1.6 for more details)

Page 93 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
V. Search

The search field allows a user to view specific alerts.

B. Alert Listings
The alert grid shows all the alerts as specified in the Alert Search Bar,
indicating all details of the alert such as alert levels, processed by,
Timestamps etc.

C. Alert Maintenance Button

I II III

I = Selecting this button will bring up this editor and processes


all alerts on the MZone system as indicated above. Ensure a
description is entered in the note section before processing.

II = Selecting this button will bring up this editor and processes


only alerts searched as indicated above. Ensure a description is
entered in the note section before processing.

Page 94 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
1

2 3 4 5

III = Editing is only allowed for unprocessed alerts. Once selected, the details of the selected alerts are
indicated.

1. Notes = Details can be entered here as to what was done to the alert.
2. Save = Will save and process the alert as Processed.
3. Cancel = Cancel all notes entered and alert will remain unprocessed.
4. Plot Alert = Places the alert onto the map in workspace for viewing.
5. Vehicle details = Opens up the vehicle information editor to activate vehicle controls.

(Please view section 3.1.1 V for more details)

D. Plot button
The plot button allows an Alert to be placed onto the map for viewing. Simply
select the Alert, and then click on the plot button. Multiple alerts can be
selected by holding down the CTRL key.

3.1.7 Messaging Tab

The messaging tab allows a user to communicate through the MHub device with
a compatible MDT Messaging PDA.

SECTION STILL UNDER CONSTRUCTION

Page 95 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
3.2 Map Data Control (III)

The Map data control allows a user to control and manage data entries onto the
maps. 3 main tabs are categorised as follows:

3.2.1 Selected Vehicles – Active Track

A
C D
B

A. Active Track Window


This window shows all vehicles that are currently being active tracked, this
means that the location of vehicles are plotted onto the map and MZone
automatically refreshes its position every 30, 60 seconds etc. the list of
vehicles can be seen displayed in I below.
(Please view section 1.3 D on how to set the primary refresh intervals)

II = Ignition state
III = last reported time stamp
IV = Keep history
I
Checked = ON
Unchecked = OFF
V = remove vehicle from Active Track list

II III IV V

B. Make all favorite vehicles selected


Selecting this option will place all your vehicles from the Favorite Vehicles
Group into the Active Track window in A above.

Page 96 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
C. Toggle active track history ON or OFF
This option automatically selects all the active track vehicles to keep history
(checked). Keeping history keeps previous positions of a vehicle on the map
and MZone will automatically join all previous positions with a color coded trip
line. This enables a user to view real-time trips of vehicles. History ON and
OFF are differentiated below.

History ON

History OFF

D. Deleting Active track vehicles


A user is able to delete vehicles from the active track window, simply click on
the delete icon and confirm.
(Note: deleing vehicles from the active track window will only remove them from the active track list and
NOT deleted off the MZone system.)

3.2.2 Plotted Entities

Under the plotted entities section a user is able to control how and where the data is
viewed. This section ensures locating the data on the maps is quick and easy.

Page 97 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
I

II

I. Data type Listing


Each data type currently on the map is conveniently categorized which
indicates total data and of those data which have been made
visible/invisible.

To remove plotted
All events plotted events, simply click
will be categorized Use this icon to the delete button to
here. make all events confirm.
visible/Invisible.

II. Specific Data type control

To manually administer specific events, simply click on the category to


expand.

Clicking on this icon


will zoom to the
event on the map.

This icon makes


events on the
visible/invisible.

To remove data
entries on the map,
simply click the
delete button to
confirm.

Page 98 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
3.2.3 Map Settings

Map settings allow users to set his/her preferences of MZone behaviors when
actions are instructed to MZone. Current options are listed below:

These settings once selected will be saved onto the local machine. All settings
are locally cached.

3.3 Mapping (IV)

3.3.1 Map Control

Pans left, right, up, down and back

Manual Scroll to zoom in/out

Zooms out to extent Set manual zoom level

Set pan mode Use the location finder

Option to use Google maps

3.3.2 Shape Draw Control

Select Mode Draw Circle

Draw Rectangle Draw Polygon

Draw Corridor Delete Shape

Page 99 of 165
MZone 4 Product Manual, v 4.3.13 21-Jul-09
3.3.3 Trip Control

Total Trip Duration Indicator


Trip Replay Speed Control

Replay trips in chronological order Stop

Replay trips all at once

Pause

3.3.4. Mapping icons

Map icons plotted can be customized so that they are easily identified.
(Please view section 2.9.2 on how to set this up)

Ignition state and


Event Identifier direction indicator

Active Track
Identifier

Event Identifier

Ignition state and


direction indicator

Any data entity plotted onto the map can further be identified in 2 ways:

Mouse over

Using the mouse over option will display the vehicle’s description of
which the data entity belongs.

Page 100 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
Clicking on the data entity

Clicking on the data entity will give specific details such as location,
date, time etc.

Page 101 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
Chapter 4: Mob ile Resou rce Mana gement (MRM)

MRM an Introduction

MZone is a comprehensive, powerful Mobile Resource Management platform


designed for logistics companies and fleet operators. The platform encompasses
management tools to reduce operational and maintenance costs, increase mobile
resource utilization, efficiently plan and schedule delivery and service
assignment and overall enhance mobile resource safety. MZone is browser
based, presenting the operator with user friendly access to complex activities
such as planning and scheduling. The platform boasts incorporation of the latest
technology tools, providing a robust, versatile and sophisticated application.

To access the MRM section, click on the MRM button.

MRM Data Grid

Job Assignment Window

Page 102 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
4.1 MRM Data Grid

4.1.1 Jobs Tab

Jobs are captured onto the MZone system by utilizing the Jobs editor. Once Jobs
are captured, they can then be assigned to resources to perform those tasks.
A

C D

A. Job Search Options

Filter by date range Filter by Depot Filter jobs by Priority Search by job description Detailed search
as shown below.

This detailed search allows a user to locate a specific job on the MZone 4 system by utilising this
advanced search option as listed below.

B. Captured Job details


Once jobs has been created and captured on the MZone system it will be displayed in
this section all details will be displayed here.
(Please view section 2.11.2 for more details.)

Page 103 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
C. Plot Button
The plot button allows any job/s to be placed onto the map for viewing.
Simply select the job first and click on the plot button. You can hold down the
CTRL key to select multiple jobs to plot at once.
D. Maintenance Buttons
The maintenance buttons is an extension to the maintenance section of
MZone. This allows quick access to editing the entity tab selected.

Depending on the entity tab selected the Add and Edit options will take you
to their respective editors.
(Please view section 2.11 for more details)

4.1.2 Resources Tab

A
B

C D E

A. Vehicle Groups

This grid lists all Vehicle Groups that a user is permitted to access. A
favourite vehicle group is a default group for every user on the system.
This group allows a user to custom list his/her favourite vehicles into
this list.

The star option when selected (highlighted yellow) will re-order your
groups first by favourite then alphabetically. This is done in I as
I II indicated.

II as indicated can be used to determine how many groups to list.

III allows you to search for your Vehicle Groups.

III

Page 104 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
B. Vehicle details

IV V VI VII

III

II

I. Add to favorites
Any vehicles can be added to favorites by selecting this icon; upon
selecting it will automatically add the vehicle into the favorites Vehicle
Group for easy administration.

II. Alerts summary


This indicator shows the number of alerts that the vehicle has generated.
Clicking the indicator will allow the user to action and process the alerts.
(Please view section 3.1.6 on how to do this)
III. Active POI
This indicator shows the current POI that the vehicle is currently in.
Clicking the indicator will automatically plot active POI on the map as
shown below.

IV. Ignition
If the ignition indicator is lit (shown in orange), this informs the user that
the vehicle is currently driving (ignition state ON)
V. Status
The status icon allows the user to gain access to the vehicle by having
control over the outputs and various other actions as indicated below.

Page 105 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
c
a

I. Vehicle Description
The current status of the vehicle will be listed are listed here.
II. Output controls
Here a user is able to manually turn Outputs ON and OFF etc.
(Please view section 3.1 IV for more details)
III. Vehicle Enablement
A user is able to manually disable a vehicle by simply clicking on
the disable button and confirming it. Depending on how it is
physically connected, disabling a vehicle could entail disconnecting
the fuel pump or ignition relay. Contact your local administrator for
more details.
IV. Vehicle Recovery
This option allows a user to set recovery mode ON of OFF. Vehicle
recovery simply means if turned ON, it forces the MHub device to
report to MZone every 30 seconds for up to 2 hours, unless
manually turned OFF.
(Note: normal operations of the MHub device will be restored once the action has
been turned off)
V. View Geofence Download
Clicking on this button will direct you to the viewing of Geofence
Download History of the vehicle selected.
(Please view section 2.7.7 for Geofence Downloads)

Page 106 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
VI. Last Known I/O
This view gives you a current status of your current I/O, lit
indicates that the I/O is currently ON or Enabled.

VII. Commands sent


This window shows you the current commands that a user has sent
to the device. This will also indicate whether the command was
sent successfully of not.

I. Event Type
This column indicates the latest event received from the vehicle.
II. Last event Timestamp
This time stamp indicates the time the last event was received. Note, the
time stamps can be configured to thresholds. These thresholds indicate
whether the timestamps are displayed in RED or not.
(Please view section 2.4.4 on how to set this up)

C. Action buttons
I. Plot
The plot button allows any selectable entity/data to be placed onto the
map for viewing. Simply select the entity/data first, (you can hold down
the ctrl key to select multiple entity/data to plot at once) then click on the
plot button.
II. Active track
This option allows you to active track vehicles on the map; this means that
this action will place the vehicles in the active track window and auto-
update positions automatically in real-time.

D. Mapping buttons
When a mapping function is selected, it will overlap the entity selected, to
unselect the mapping function again simply click on the map function button
concerned again.

I. Events
The events option allows a user view a list of vehicle/s events over a
specified time. The user also has the option to filter the event data as
required.

Page 107 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
b
a
c
6 step process:

a. Vehicle identified for the event search


b. Select an event group filter if required
c. Select your date range
d. Click on search to complete the search process.
e. Select the event/s you want to plot
f. Click on plot to view in map.
d

f
e

II. Poll
Polling a vehicle allows a user to update any vehicle position in real-time.
Once actioned, MZone will send a request via the MProfiler to the MHub
device for a new position. This process will normally take around 40
seconds to complete.

Page 108 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
a 4 step process c
a. Select the vehicle to be polled
b. Confirm the polling action
c. Process will be begin with status indication
Status indication explained in E below.
d. Once action is complete, click on plot to view
the poll location on the map.

III. Trips

The trip function allows a user to analyze all historical trip information
from vehicles and the option to replay trips on the map.

3 step process a
b
a. Identify the vehicle to view trip history.
b. Select the date range to view
c. Click search to execute.

The list of trips results will be listed as indicated in d below.

Page 109 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
Click on this icon to view
specific details of a particular d
trip as indicated in e below.

To place a trip onto the map simply


select the trips you want plotted and
click on the Plot button.

To select multiple trips simply hold


down the CTRL key.

A trip plotted will be shown as


indicated in f below.

Page 110 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
f

(Please view section 3.3.3 on how to use the Trip Controller)

IV. Unit Controller


This option allows a user to activate outputs of the MHub device. These
generic outputs controls can be connected to various accessories on a
vehicle to be activated remotely. Such accessories can include central
locking, Boot lock etc.

V. Dispatcher
This option allows a user to locate any vehicles within a specified Location,
POI, Address and latitude & longitude.

(Please view section 3.1.1 V on how to utilize the dispatcher feature)

Page 111 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
F. Maintenance buttons
The maintenance buttons is an extension to the maintenance section of
MZone. This allows quick access to editing the entity tab selected.

Depending on the entity tab selected the Add, Edit and Delete options will
take you to their respective editors.
(Please view section 2.11 for more details)

4.1.3 Customers Tab

D
C

A. Customer Groups

This grid lists all Customer Groups that a user is permitted to access. A
favourite customer group is a default group for every user on the
system. This group allows a user to custom list his/her most active
customers into this list.
I
The star option when selected (highlighted yellow) will re-order your
groups first by favourite then alphabetically. This is done in I as
II
indicated.

II as indicated can be used to determine how many groups to list.

III allows you to search for your Customer Groups.

III

Page 112 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
B. Customers

II
I

I. Favorites
Any vehicles can be added to favorites by selecting this icon; upon selecting it
will automatically add the vehicle into the favorites Vehicle Group for easy
administration.
II. Customer details
All customer details are displayed in the customers tab.
(Please view section 2.11.1 for more details)

C. Plot Button
The plot button allows any customer to be placed onto the map for viewing. Simply
select the customer first and then click on the plot button. You can hold down the
CTRL key to select multiple customers to plot at once.

D. Maintenance Button

The maintenance buttons is an extension to the maintenance section of


MZone. This allows quick access to editing the entity tab selected.

Depending on the entity tab selected the Add, Edit and Delete options will
take you to their respective editors.
(Please view section 2.11 for more details)

Page 113 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
4.1.4 Depot Tab

B
A

C D

A. Depot Groups

This grid lists all Depot Groups that a user is permitted to access. A
favourite customer group is a default group for every user on the
system. This group allows a user to custom list his/her most active
depot into this list.
I
The star option when selected (highlighted yellow) will re-order your
II
groups first by favourite then alphabetically. This is done in I as
indicated.

II as indicated can be used to determine how many groups to list.

III allows you to search for your Depot Groups.

III
I

B. Depots

I II

Page 114 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
I. Favorites
Any vehicles can be added to favorites by selecting this icon; upon selecting it
will automatically add the vehicle into the favorites Vehicle Group for easy
administration.
II. Depot Details
All depot details are displayed in the depots tab.
(Please view section 2.11.4 for more details)

C. Plot Button
The plot button allows any depot with their servicing areas to be placed onto the map
for viewing. Simply select the depot first and then click on the plot button. You can
hold down the CTRL key to select multiple depots to plot at once.
D. Maintenance Buttons
The maintenance buttons is an extension to the maintenance section of MZone. This
allows quick access to adding/editing the entity tab selected.

Depending on the entity tab selected the Add and Edit options will take you to their
respective editors.
(Please view section 2.11 for more details)

4.1.5 Gantt Chart Navigation

The Gantt Chart is a graphical representation of the tasks that is assigned for the
selected resource. The Gant chart displays a snapshot of all the tasks and its
current updates.

A B C D E

F G H J I G F

Page 115 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
A. Search Options

The search option allows the user to locate their resources or jobs by completing the
auto-fill fields.

Automatically the searched


entity will be highlight to the
user by way of a small
animation as indicated.

B. Refresh Gantt
By default the Gantt is refreshed every 5 minutes or as custom defined by the user
under settings (section 1.3 D). This refresh icon allows the user the manually refresh
the Gantt Chart.
C. Current Time Indicator
The yellow line indicates current time of the day which takes the users UTC time
setting into account. Ensure your Local UTC time is correctly set.
(Please view section 2.6.1 for more details on how to setup a user UTC time)

D. Timeline
The time line indicates the times jobs are scheduled represented in a 24hour format.
You can click on the timeline to decrease intervals and zoom out again using the
icons as indicated in E above.
E. Zoom options
Zoom option can be done by using these icons, simply zoom in and zoom out as
needed.
F. Toggle between days
Clicking on the panes as indicated will toggle between days to be displayed on the
Gantt.
G. Toggle between timeline
Mouse over these panes to scroll the timeline within the day selected.
H. Resources.

= Plot resource last known position

Resource Capacity = Place resource in the active track list

= Vehicle information editor


Ignition status
= Job assignment option
= ON
= OFF = Plot resource route/tasks on the map

= Optimise a single resource tasks

Page 116 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
I. Tasks

Resource Time Profile Resource Not Available

Resource Time Profile


The darker shade of grey on the Gantt shows the resources available
times of operation. All jobs will fall within this section for job
assignments.
(Please view section 2.4.1 on how to assign these time profiles to resources or section
2.4.5 on how to create new Time Profiles)

Resource Not Available


The lighter shade of grey indicates the resources non-operational
times. No jobs will be scheduled in the lighter areas of the Gantt.

J. Sort By

Sort Alphabetically

Sort by ignition states

4.2 Job Assignment Window

D E

Page 117 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
A. Job Window Control
Once the MRM section is selected, the Job Window Control tab will available to view
and assign jobs to its resources. Upon selecting this tab will also default the user to
view the Gantt Chart.
B. Job List
In this section a list of unassigned jobs will be listed in this window for assignment.
Simply click on the Assign icon to assign it to a resource.

C. Job Filter
The job filters can be used to filter the job window by type of category or related
depot.
D. Auto assignments buttons

Auto-Scheduling option, this option allows a user to allow MRM to


assign all unscheduled jobs to its available resources automatically.

(Please view section 4.2.1 below for more information on how to utilize this)

This icon plots all the unassigned jobs onto the maps along with the depot for
which it is assigned. Please image A below for an example.

(Image A)
E. Job Buttons
Job assignment button, simply identify the job that needs to be
assigned and then click on this icon to bring up an editor which you
then specify a resource to subscribe.
d

(Please view section 4.2.2 below for more information)

Selecting this icon will create a new job onto the MZone 4 system.

(Please view section 2.11.2 on how to add new jobs)

Page 118 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
4.2.1 Auto-Scheduling

The Auto-scheduling feature allows MRM to optimize all the Jobs against
Resources effectively and quickly. This allows MRM to assist an operator to
manage and automatically produce a list of schedules to be completed for the
day, week etc.
(Please view Additional Reading Section for Auto-Scheduling.)

To utilize this feature click on the auto schedule icon as indicated:

= This icon can be located in the Job Assignment Window

Once selected an editor will appear with 5 steps to complete:

Step 1 – Job and Resource Selection

A. Selecting Jobs
In this section the user/operator identifies which Jobs will be considered for MRM to
optimize. Simply use the check box to the select. You can make use of the check all
option on the first checkbox listed in this section.
B. Selecting Resources
In this section the user/operator identifies which Resources will be considered for
MRM to optimize. You can make use of the check all option on the first checkbox
listed in this section.

Once the selections are made click to proceed

Page 119 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
Step 2 – Optimization Parameters

C D

If a resource selected in step 1 already contains jobs for the selected date, then an additional
option will appear as indicated.

Simply instruct MRM how it will handle the existing jobs by selecting one of the options as indicated
in E above.

C. Optimization Options

I. Best Scheduled Time


The best scheduled time is a combination of all the options in this section.
Using this option to instruct MRM to schedule jobs will be done in the
following order:
Cost per kilometer
Closest depot
Shortest duration
Shortest distance
II. Shortest Distance (load Balance)
Using this option to schedule will result in MRM scheduling the jobs to
resources by shortest distance possible and MRM ensures that all the
resources selected will have the jobs spread evenly among them as well as
the distance traveled by these resources.
E.g. 100 Jobs and 4 Resources, MRM will endeavor that each resource will
be assigned 25 Jobs.

Page 120 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
III. Shortest Distance (Max Resource Utilization)
Using this option to schedule will result in MRM scheduling the jobs to
resources by shortest distance possible and MRM will ensure that the first
resource selected will perform as much of the jobs as it can handle before
MRM identifies another resource.
E.g. 100 Jobs and 4 Resources, MRM may only require 3 Resources to
complete these 100 jobs.
IV. Shortest Duration (Load Balance)
Using this option to schedule will result in MRM scheduling the jobs to
resources by shortest duration possible and MRM ensures that all the
resources selected will have the jobs spread evenly among them.
E.g. 100 Jobs and 4 Resources, MRM will endeavor that each resource will
be assigned 25 Jobs.
V. Shortest Duration (Max Resource Utilization)
Using this option to schedule will result in MRM scheduling the jobs to
resources by shortest duration possible and MRM will ensure that the first
resource selected will perform as much of the jobs as it can handle before
MRM identifies another resource.
E.g. 100 Jobs and 4 Resources, MRM may only require 3 Resources to
complete these 100 jobs.
VI. Least Cost per Kilometer (Load Balance)
Using this option to schedule will result in MRM scheduling the jobs by
utilizing the cost per kilometer field that is pre-assigned to a resource. Each
resource has a cost per kilometre attached to it, which is used in this
combination, where each resource’s travelling cost will result in roughly the
same amount.
(Please view section 2.4.4 on how to assign vehicles to a cost per kilometer value via Vehicle
Types)
VII. Least Cost per Kilometer (Max Resource Utilization)
Using this option to schedule will result in MRM scheduling the jobs by
utilizing the cost per kilometer field that is pre-assigned to a resource. MRM
will then select the most cost effective resource to run before selecting
higher costs resources.
(Please view section 2.4.4 on how to assign vehicles to a cost per kilometer value via Vehicle
Types)

(Please view Additional Reading Section for Auto-Scheduling.)

D. Execution Options

VIII. Optimization Cut-off


MRM uses a series of generations to compute the best optimal tasks for
resources. Here the user has to option to limit how many generations MRM
will perform until it comes up with its optimal set of tasks. By default 100
generations are done, simply increase or decrease as needed.
IX. Resource Overtime Minutes
When scheduling, MRM will take the resources time profile into consideration
when optimizing, here a user has the option to increase its operating hours
to cater for that last important job if required.
X. Optimization Date
A user defined start date for the schedules to begin can be entered here.

Page 121 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
Click to proceed

Step 3 – Pre-Optimization Procedures

In this section MRM will compute the details as captured in Step 2, once
optimizing procedures are done as indicated in E below, a user can then proceed
to the next step.

E
Step 4 - Optimization

In step 4 MRM will start placing the generations onto the maps as well as the
information window to indicate MRM’s optimization progress. The user has the
option stop/resume the optimization process by clicking on the Stop button as
indicated in F below. This ensures the user has control over how long the
process he/she is willing to take.

Page 122 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
F
Step 5 - Confirmation

In the final step the results of the optimization will be presented on the Gantt
chart for review. The user has the option here to make any final adjustments to
the tasks scheduled. Simply click on save to complete the process.
(To learn how to use the Gantt please view section 4.3.1 for more details)

4.2.2 Manual Job Assignments

Manual job assignments allow a user to assign jobs to resources when


optimization is not required. This allows the flexibility for users to assign random
jobs to resources. To access the manual job editor screen, you can click on the
assign icon where available.

= Manual assignment of jobs

Page 123 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
Specify a date for which
this job will assigned for.

The list of jobs selected will


be displayed here.

An auto-fill field, simply list


a resource to be assigned
here.

Once the job has been assigned as confirmation will be presented as follows:

4.3 Job Management

Once job has been assigned to resources a user will monitor the Gantt for the
drivers progress to the jobs assigned.

4.3.1 Interpreting jobs on the Gantt

Once a job has been placed on the Gantt the following information and details
can be obtained.

A Planned Time

Priority

Travel Duration B

Page 124 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
A. Drop down option
Upon selecting the drop down for a particular job, it will give specific details
about customer and the option for a user/operator to manually override job
statuses.

All scheduled and actual


dates will be populated here
as they become available.
You can also use the Jobs
Tab to view this data.

II

I. Statuses

II. Job maintenance buttons

Edit option
Remove job from Gant chart and set job as unassigned
PDA communication, please view section 4.3.3 for more details

B. Actual Times
Once real life data starts to populate the Gantt Chart, the initial blue indicator
will start to shift according the to the time resources arrive at their various
destinations. A shift will be represented by a series of color coded tabs as
follows:

A blue indicator represents the job


has yet to begin. The resource has
not arrived at the current job.

Page 125 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
A yellow indicator represents the job
is currently in progress and also
indicates at what time the resource
arrived.

A red indicator represents the job has


been visited and is late. Note the red
indicator only shows once the
resource and left.

A green indicator represents the job


has been visited and was early. Note
the green indicator only shows once
the resource has left.

4.3.2 How Job details are populated

Data can be populated as follows:

A. Automatic population
By default MRM populates actual data by automatically identifying if resources are
within the destination points assigned to them by the use of various POI’s. If
resources have been detected, then MRM will set the jobs as arrived or departed. As
indicated below.

First event detected within the destination will be set as arrived, and the first event
detected outside the POI will be set as departed.

The first detected


event within the
destination will be
identified as arrival
and MRM will set
job status to - in
progress.

B. Operator population
A user/operator can manually set actual arrival and departure times by
editing the jobs from the Gantt Chart.

To access the Jobs Editor to manually set arrival and departure dates, simply
use the dropdown on the job you would like to set dates and click on the Edit
icon as indicated below.

Page 126 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
Editing an assigned Job

Simply click on the set button to insert Actual Arrival or Actual Departure times as needed. A popup will
assist you in selecting a date and time as indicated below.

C. PDA population

The PDA option will allow drivers to update Actual arrivals and Departures
with the use of a Windows CE enabled device. Software needs to be
preloaded onto the PDA which then connects via USB to a MHub device.
Please consult your local administrator for more details.

Page 127 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
As an example the PDA interface will allow drivers to view all the information
that is sent from MRM.

Driver selecting this option will


send a departure notification to
MRM as an Incomplete
Departure.

Driver selecting this option will


send a departure notification to
MRM as a Complete Departure.

4.3.3 How to communicate to drivers

MRM can maintain communication to drivers by making use of the PDA


option. A user/operator can send messages to the PDA and drivers can
respond with various updates.

To access the Notes Editor to communicate simply use the dropdown on the
job you would like to send a message to and click on the PDA icon as
indicated below.

Messaging access

Page 128 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
All Notes about the jobs are
displayed here for referencing at a
This window displays all historical and current later stage.
communications between the driver and operator. The option to filter
messages by using You can access quickly to
a date range can be other vehicles to
done here. communicate by using this
option.

Click the add button to


To enter messages, simply insert text in insert a note.
the text box provided and click the send
button to communicate.

4.4 Additional Reading (Auto-Scheduling)

When using the Automatic Resource Scheduler, the user has the option to
schedule his/her Resources using 3 (three) different types of techniques. These
3 (three) techniques include the following:

A. Shortest Distance
Distance is used as a measure to determine the next closest Job. When selecting a
job from the pool of unassigned jobs the next closest job is selected according to a
calculated distance.
B. Shortest Travel Duration
An average Travel Duration is calculated from a Time and Distance Matrix. This
matrix is periodically updated from completed jobs, and these actual values are used
to determine travel duration.
C. Least Cost per Kilometre
Similar to Shortest Distance, but an extra factor is added to determine the closest
next job for any resource. The Cost per Kilometre (which is attached to a Vehicle
Type) is factored into the calculation for the next closest job for any resource.

Once the user has determined what technique he/she will use, further
customization is possible. This customization exists to aid the user in
determining the best possible schedule according to the needs of the situation.
To further customize how optimization is performed the user has the ability to
choose any of the following:

Page 129 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
 Maximum Resource Utilization
 Load balancing

Also, another 7th option exists that does not quite fit the combinations mentioned
above which is Best Schedule Time. This option allows the user to Schedule the
unassigned jobs as quickly as possible. This means that each job will be
assigned to a resource so that each job gets completed as quickly as possible.
This type of optimization is a combination of Shortest Distance, Shortest Travel
Duration and Load Balancing, and for this reason separated from the rest of the
combinations.

Below are detailed explanations of each combination mention above, excluding


Best Schedule Time.

4.4.1 Shortest Distance – Load balanced

When selecting this option the user would want all of his/her resources to do the
same amount of work. In particular, each resource roughly travels the same
amount of kilometres or miles, depending on the users Unit of Measure. For
example if there are 2 resources and 4 jobs, where one of the jobs is 100 km
away from each resource and the other 3 only 25 km away, the optimization
process will try and schedule the first resource to do the 3 jobs that are 25km
away and the last resource to complete the job that is 100 km away. The result
would be that the first resource travel 75 km and the second 100 km, balancing
the distance travelled among the resources.

4.4.2 Shortest Travel Duration – Load balanced

This is very similar to the combination mentioned already, Shorted Distance –


Load Balanced, but, instead of travel distance, takes travel duration into
account. This option looks at the average travel duration determined from actual
values** and makes sure that each resources is on the road the same amount of
time. In the example mentioned above, the outcome could be slightly different,
if, for example, the travel duration for the job that is 100 km away is 60
minutes, the travel duration for one of the jobs that is 25 km is also 60 minutes,
and the remaining jobs each have a travel duration of 20 minutes (keeping in
mind the distance between the points are the same). The optimization process
will schedule each resource to do 2 jobs, where each resource would be used for
a total of 80 minutes. This combination is useful if the user requires his
resources to be busy for the same amount of time, resulting in all resources
completing their scheduled route at roughly the same time.

4.4.3 Shortest Distance – Max resource utilization

Unlike Loaded Balanced, Max Resource Utilization uses a resource fully before
selected another resource from the available resources, resulting in as few
resources being used as possible. To continue using the example mentioned
before, if 2 resources are available and 4 jobs, where one job is 100km away
and the other three jobs are all 25 km away, the optimization process here
would try and assign all 4 jobs to one resource, provided the resource can be

Page 130 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
used and the job schedule times do not conflict with the operating hours of the
Customer.

4.4.4 Shortest Travel Duration – Max resource utilization

This combination functions the same way as Shortest Distance – Max Resource
Utilization, where travel duration between each job is considered rather than
travel distance. The two combinations (Shortest Travel Duration and Shortest
Distance for Max Resource Utilization) could yield different results if actual data
is present to determine average distance and duration from the Time and
Distance Matrix.

4.4.5 Least Cost per Kilometre – Load balanced

Each resource has a cost per kilometre attached to it, which is used in this
combination, where each resource’s travelling cost will result in roughly the
same amount. To use the example mentioned earlier; there are 2 resources and
4 jobs, where the first job is 100 km away from each resource and the remaining
3 jobs are 25 km away. If the first resource has a Cost per Kilometre of 5 and
the second resource a cost per kilometre of 10, the result of the optimization
process would be that the first resource would have to complete 2 jobs, namely
one that is 100 km way and the other that is 25 km away. The second resource
would complete the remaining jobs that are 25 km away. The first resources’
cost per kilometre would be 625 units and the second resources would be 500
units. The result is that each resource’s attached cost to complete the assigned
jobs would be the same, resulting in a balanced and shared cost.

4.4.6 Least Cost per Kilometre – Max resource utilization

This combination optimizes all unassigned jobs to be done by available resources


where the cost per kilometre is minimized. The resource with the lowest cost per
kilometre is considered first and subsequent resources are considered with the
next lowest cost per kilometre.

Page 131 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
Chapter 5: Repo rts

Reports an Introduction

MZone reports give the user the proper management tools to reduce operational
and maintenance costs, as well as improve operational efficiencies. A suite of 56
reports is available.
To access the reports section the user will have to select the following tab.

5.1 Basic Navigation

The reports are categorized into 4 subsections that allow a user to navigate to
their reports quickly and easily. Simply click on the category then select the
desired report.

Step 1

Select the category


by simply clicking on
the button.

Step 2

Select the specific


report as needed

Page 132 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
5.1.1 Selecting report criteria

Once a report has been selected, various options will be available depending
on the type of report.

Generally reports require 3 basic options in order for a report to be drawn.

Let’s view an example below:

The entity for which the report will be


based on needs to be identified, this is
normally in the first field of any report.

A timeline for the report to be drawn for


the entity selected can be entered here.

Where certain reports apply a filter can


be used to display only the data
needed such as “Speeding Events”
only etc.

The option to schedule a report


directly to a mailbox can be
View the report within the done here. View section 5.1.4
MZone application. View the report in a for more details.
new separate tab.

5.1.2 Report Bar

Every report once drawn will a report bar from which to further administer
the report in the following ways:

Allows a user to switch Search for a particular Formats available to export the Print
between report pages. Page width options allow a text within the report can report to are as follows:
user to change the report to be done here.
the desired zoom level.

Page 133 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
5.1.3 Static Report bar

The static report bar is a supplementary to the report bar when reports are
viewed within the MZone application. This bar remains on the top of the
report page at all times.

Click to redraw the report into a


new tab
Back

Allows a user to switch Print


between report pages.
Refresh the report

5.1.4 Report Scheduling

When the scheduling option is selected, a user is able to schedule and email
reports directly to recipients mailboxes without having the need to log into
MZone.

A. Selecting a schedule
The options allows a user to specify how frequent the report is to be mailed. Simply
select the options by selecting the radio icon corresponding to your choice.

Page 134 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
B. Recipients
Emailing of reports can be done to multiple recipients by simply entering their email
addresses in this field. By default the user logged into MZone will havehis/her email
address already entered.
C. Sending format
Various report formats can be selected for the recipients, simply use the dropdown
and select one of the following options.

D. Email Message
As with any email a user has the option to enter any additional information to the
recipient receiving the report.
E. Schedule confirmation
Once all details have been entered into editor simply click on the Schedule button to
confirm and the schedule will be listed in the Schedules tab for further refereance as
indicated below.

5.1.5 Report Structure

All MZone reports will contain the following basic information:

Report Header Entity details utilized in the report

Report data display

Page 135 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
5.2 Vehicle Reports

Vehicle specific reports, giving the user detailed information


pertaining to individual vehicles, line by line events are displayed.

5.1.1 Vehicle Event

This report details a chronological record of events for a specific vehicle over time
including the location, driver description, odometer, speed and coordinates grouped by
day. Optionally the report can be filtered to show only a specific group of events thereby
enabling specialized event reports.

Pre-requisites:

All MHub units can make use of this report as any events received by MZone will be
displayed in this event.

5.1.2 Vehicle Event Detail

This report is an extension of the Vehicle Event report. It lists all the events in
chronological order grouped by day and includes specific details of events such as driver
faults, green band percentage, trip duration, trip distance, trip ID, Ignition delays and
RPM.

Pre-requisites:

All MHub units can make use of this report as any events received by MZone will be
displayed in this event. Note: the detail extent of the report depends on the type of
events being received.

For example, without a Trip Shutdown event being received then no trip durations can
be displayed etc.

Page 136 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
5.1.3 Vehicle Trip Detail

This report details all events that have been recorded within a trip for a specific vehicle.
For each trip, the Start Time, End Time, Distance, Duration and Driver Registered is
listed per trip recorded. Chronological logs of events that occurred within a Trip as well
as the location of each event are listed.

Pre-requisites:

A MHub device reporting Trip Startup and Shutdown events are at least required.

Page 137 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
5.1.4 Vehicle Trip Overview

This report gives an overview of all trips for the specified vehicle over the selected date
range. For each trip, the Start & End time, Location, Distance, Speed (Max & Avg), RPM
(Max & Avg) and vehicles dwell times (idle times) are indicated.

Pre-requisites:

A MHub device reporting Trip Startup and Shutdown events are at least required.

5.1.5 Daily Tachograph

This report contains a summary listing of trips the vehicle performed on a particular day
with details that include Driver key code, Driver description, Trip distance, Maximum &
Averages for Speed and RPM. Two graphical representations of Speed and RPM are also
displayed for the selected vehicle.

Pre-requisites:

This report requires the Tacho Graph Event to be generated by the MHub device. If you
are not receiving any data for this report ensure this is setup on the MHub device itself
for drawing this report again. Please consult your local administrator for further details

Page 138 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
5.1.6 Vehicle Alert Detail

This report details every alert individually for the selected vehicle. This allows a user to
identify how the alerts the handled by operators as well the operators response time to
alerts. Optionally the report can be filtered by the user that actioned alerts for the
specified vehicle.

Pre-requisites:

Alerts can be setup for any events received on MZone. Ensure at least one alert has been
setup and generated before drawing this report.
Note: this report only lists Processed Alerts only.

(Please view section 2.9.2 to setup an alert and section 3.1.6 to process an alert)

Page 139 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
5.1.7 Temperature Detail

This report lists temperature events for the specified vehicle. It’s Location, Input
statuses; Sensor Description, Temperature Reading, Thresholds and Duration are listed
for each temperature event. All events are grouped per day in the reports which also
includes a graph indicating various readings of all sensors.

Pre-requisites:

Temperature sensors must be installed onto the MHub device with its Temperature
Events High/Low setup.

Page 140 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
5.1.8 Fuel Entry Detail

This report lists all fuel entries entered into MZone for the selected vehicle over a
specified date range. It includes entry information such as total cost of fuel, total
quantity of fuel and cost per litre/gallon. Data obtained can be manually entered into the
MZone database or via electronic fuel cards.

Pre-requisites:

Entries must exist on the MZone database.


(Please view section 2.8 on how to set this up.)

5.1.9 Daily Trip Event Detail

This report shows the trip summary of the selected vehicle with trips details that include
trips done during the day or night. The details of Geofence types entered include total
time spent and total distance travelled can be identified.

Pre-requisites:

2 events are required for this report to populate: Daily Trip Summary and the Daily
Geofences Summary events. Geofence types must also be setup on the MHub device as
well as drive slot times. Please contact your local administrator for more details.

Page 141 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
5.1.10 POI Analysis per Vehicle

This report lists an analysis of places of interest visited by the selected vehicle. Details of
POI visited include: number of visits, total duration and average duration.

Pre-requisites:

POI’s must be created on the MZone application for this report to populate.
(Please view section 2.7.1 for more details.)

5.1.11 FMS Detail

The FMS Detail Report gives a summary of Trips, Driving Time, and Fuel Usage for the
selected vehicle over a certain date range. It also gives a summary of each Trip a vehicle
has performed with trip summary information that includes Trip Info, Driving Time Info,
Fuel Usage Info, Speed Info and RPM Info. A Speed and RPM Histogram is depicted for
analysis.

Pre-requisites:

This is can CANBus report and will only be available if the MHub device is connected via
CANBus on the J1939 standard.

Page 142 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
5.1.12 Fuel Distance

The Fuel Distance Report shows the fuel level in relation to the odometer reading in a
graphical representation for the selected vehicle over a given time period.

Pre-requisites:

This is can CANBus report and will only be available if the MHub device is connected via
CANBus on the J1939 standard.

5.1.13 Vehicle Exception Detail

This report contains all the exceptions for the selected vehicle in the selected date period
including the details on each exception. Exception events include: Speeding, Harsh
Barking, Excessive Acceleration, Excessive RPM and Freewheeling.

Pre-requisites:

None, as long as the vehicle is reporting such exceptions as listed in the report
description above.

Page 143 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
5.1.14 Accident Reconstruction Detail

This report shows the accident reconstruction log events for the selected vehicle over a
specified time period. This log contains a predefined set of accident logs for viewing. You
are able to export the logs to a KML file for display in Google Earth.

Pre-requisites:

The Accident Log Event will need to be configuration the MHub device in order for this
report to populate. Please contact your local administrator for more details.

5.1.15 Reckless Driving Detail

This report shows the details of all Reckless Driving Events for the selected vehicle over
a date period. Details such as Driver Accountability, The Trip incurred and Accelerometer
Details are included.

Pre-requisites:

The Reckless Driving Event is detected by means of an accelerometer device component


within the MHub device. Not all devices include the accelerometer options; please consult
your local administrator for more details.

Page 144 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
5.1.16 Reckless Driving Summary

This report summarises the occurrence of Reckless Driving Events for the selected
vehicle group over the selected date range. The report shows the trips each vehicle has
made along with details such as Total Trip Distance, Total Trip Duration, and the Number
of Reckless Driving events included.

Pre-requisites:

The Reckless Driving Event is detected by means of an accelerometer device component


within the MHub device. Not all devices include the accelerometer options; please consult
your local administrator for more details.

5.3 Vehicle Group Reports

Vehicle Group reports are summary information reports designed


to provide a user with an overview of his /her fleet.

5.3.1 Vehicle List

This report lists all selected vehicles belonging to the specified vehicle group. In addition,
The Registration, COF due date, Home Location, Last Known Odometer Reading,
Purchase Date and The Age of the Vehicle are listed fro referencing.

Pre-requisites:

None, as long as Vehicles are added the MZone database this report can be utilized.
(Please view section 2.4.1 on how to add vehicles.)

Page 145 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
5.3.2 Vehicle Activity Summary

This report ranks all vehicles in the selected vehicle group based on the amount of time
and distance it has been in operation. In addition, Total Trip Distance, Duration,
maximum and minimum Speed/RPM are listed for referencing.

Pre-requisites:

This report requires the device to be configured with the Tacho Graph Event for full
population of this report. Please contact your local administrator for further details.

5.3.3 Vehicle Exception Summary

This report all vehicles in the selected vehicle group with a summary of all exceptions
occurred. Included in the report is the No. of Speed, Excessive RPM, Harsh Braking,
Excessive idling, Freewheeling and Temperature Exceptions. In addition the Total
Duration of Utilisation and Unauthorised Usage are shown.

Pre-requisites:

Various exception events are to be setup on the MHub device for the vehicles concerned
before any meaningful data can be concluded by this report. Please contact your local
administrator for further assistance.

Page 146 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
5.3.4 Vehicle Utilization (Simplified)

This report lists all vehicles within the selected vehicle group with their Total Trip
Durations. This is shown graphically and ranks the vehicles in order of the durations in
descending order within the selected vehicle group.

Pre-requisites:

Vehicles generating the Trip Start up Event and the Trip Shutdown Event will be able to
utilise this report.

5.3.5 Daily Trip Event Summary

This report lists all vehicles within the selected vehicle group for any selected date range
and provides basic trip summary information. Included in the report are indications of
Trips done during the Day or Night and Total Duration/Distance within a Geofence Type.

Pre-requisites:

2 events are required for this report to populate: Daily Trip Summary and the Daily
Geofences Summary events. Full report utilization can be achieved by ensuring
Geofences are setup within your MZone user group.
(Please view section 2.7 for more details on how to set this up.)

Page 147 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
5.3.6 Vehicle Time utilization (Simplified)

This report specifically details the Time Utilization for all vehicles within the selected
vehicle group. Report indicates whether vehicles utilization are increasing or decreasing
compared to the previous report date range selected. Additional information such as the
Inside and Outside Times can be identified by making use of Time Profiles.

Pre-requisites:

Vehicle Time Profiles are required per vehicle or a selected vehicle time profile when the
report is drawn.
(Please view section 2.4.5 for more details on how to create profiles.)

5.3.7 Fuel Entry Summary

This report lists a summary of fuel entries for all vehicles in the selected vehicle group,
calculating the Total Amount of Fuel Entries, Total Quantity, Total Costs and The Average
Quantity per Vehicle.

Pre-requisites:

Fuel Entries are required to be in the MZone database for this report.
(Please view section 2.8.1 on how to add Fuel Entries. Note: this report does not include details on any CANBus
fuel data.)

Page 148 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
5.3.8 Fuel Consumption trends

This report lists the Fuel Consumption Values and the Resulting Trends of the selected
vehicle group. The report indicates whether the Fuel Consumption Trends are either
increasing or decreasing compared back three consecutive periods the report date range
was initially selected.

Pre-requisites:

Fuel Entries are required to be in the MZone database for this report.
(Please view section 2.8.1 on how to add Fuel Entries. Note: this report does not include details on any CANBus
fuel data.)

5.3.9 POI Duration Summary

This report summarises the Total Time each vehicle spent within an individual/group of
Poi’s’.

Pre-requisites:

This report only works if the entity groups are setup for Software Geofence.
(Please view section 2.7 for more details on Geofence.)

Page 149 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
5.3.10 Green band Summary

This report ranks all vehicles in the selected vehicle group based on the amount of time
the vehicle has been operated at an RPM value within the Green Band range defined. In
addition, Total Trip Distance, Duration and Average RPM are listed for referencing.
Optionally the report content can be further filtered on the Green Band Percentage.

Pre-requisites:

A Vehicle Type needs to be defined to a vehicle. The MHub device need will need to be
configured with the Tacho Graph Event. Please contact your local administrator for more
details.
(To define Vehicle Types to a vehicle please view section 2.4.1 and 2.4.5.)

5.3.11 POI Activity

This report lists all vehicles along with their registration in the selected vehicle group. It
identifies to the user when the First Entry and Last Entry, Total Duration and No. of Visits
for a particular POI queried.

Pre-requisites:

POI’s need to be added into the MZone database before the report is able to identify
these times of entry or exits etc.
(Please view section 2.7.1 for details on how to add places.)

Page 150 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
5.3.12 POI Analysis per Place

This report lists all vehicles within the selected vehicle group that has visited a particular
POI (Place of Interest) identified by a user. Details for the selected POI that can be
obtained by this report include: No. of Visits, Total Duration and Average Duration.

Pre-requisites:

POI’s need to be added into the MZone database before the report is able to identify
these times of entry etc.
(Please view section 2.7.1 for details on how to add places.)

5.3.13 Temperature Summary

This report lists all vehicles within the selected vehicle group along with their registration
details. Each vehicles Temperature High and Low values are indicated with the No. of
occurrences and Total Duration.

Pre-requisites:

The temperature sensors are required to be installed on the MHub device and setup in
order for the report to generate such details. Please contact your local administrator for
more details.

Page 151 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
5.3.14 Distance Exception

This report contains all the vehicles within the selected vehicle group that exceeded the
Distance Threshold within a certain time period (normally a month). The Distance
Threshold can be taken from each vehicle’s preset distance thresholds or can be
overridden by a user defined threshold within the report criteria.

Pre-requisites:

Not compulsory, however if the “use vehicle default” checkbox is used, then the Mileage
Limit field in the vehicle editor needs to be set.
(Please view section 2.4.1 for more details on how to set this.)

5.3.15 FMS Summary

The FMS Summary report gives a summary of Trips, Driving Time, Fuel Usage, and
Harsh Braking per vehicle within the selected vehicle group. The report obtains this
information from the vehicles CANBus normally on the J1939 Protocol.

Pre-requisites:

This is a CANBus only report and only MHub devices connected via CANBus may utilize
this report. In addition the following event needs to be setup, FMS Brake Clutch and Trip
Analysis Event. Please contact your local administrator for further details.

Page 152 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
5.3.16 Temperature Exception

This report details all the Temperature Exceptions generated by the vehicles within the
selected vehicle group.

Pre-requisites:

The temperature sensors are required to be installed on the MHub device and setup in
order for the report to generate such details. Please contact your local administrator for
more details.

5.3.17 Fuel Consumption Summary

The fuel consumption report is used to determine the differences in fuel consumption
with a specific type of vehicle compared to other vehicles of the same type. In addition
the report is able to identify any deviations within the fuel consumptions for a specific
vehicle on a per vehicle basis.

Pre-requisites:

Fuel Entries are required to be in the MZone database for this report.
(Please view section 2.8.1 on how to add Fuel Entries. Note: this report does not include details on any CANBus
fuel data.)

Page 153 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
5.3.18 Vehicle Alert Summary

This report lists each alert that has occurred for the selected vehicle group. Optionally
the report can be further filtered by the user that processed the alert. Details in this
report include: Action Time, Response Time, Driver description and Alert Event.

Pre-requisites:

Alert needs to be setup on the MZone application before any alert information is
displayed in reports.
(Please view section 2.9.2 on how to setup alerts.)

5.3.19 Vehicle Communication

This report is typically used as a diagnostic tool to determine whether vehicles are
communicating properly. The report lists each vehicle within the selected vehicle group
and provides the following information: No of events recorded, The Last Known Event
and Last Known Driver. Optionally the report can be further filtered to show only a
specific group of events as well as limiting the list of vehicles shown based on a range for
the number of events recorded.

Pre-requisites:

None, as long as vehicles are present on the MZone database.


(Please view section 2.4.1 on how to add vehicles.)

Page 154 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
5.3.20 Vehicle Trip Summary

This report lists all vehicles within the selected vehicle group and shows their summary
trip information. Included in the summary are the: Vehicle Registration, No. of trips,
Total and Average Distance Travelled, Total and Average Duration Travelled, No. of
drivers and the Last Known Odometer Reading.

Pre-requisites:

None, as long as vehicles are present on the MZone database and trip information is
received such as Trip Start up Event and Trip Shutdown Event. Further information
please contact you local administrator.
(Please view section 2.4.1 on how to add vehicles)

Page 155 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
5.4 Driver Reports

All driver related reports are contained in this section. Various


driver rating and performance reports are also included.

5.4.1 Driver List

This report lists all drivers within the selected driver group. In addition the Key Code and
Identity Number are listed to for referencing.

Pre-requisites:

Driver needs to be added to the MZone database for the report to be drawn correctly. In
addition but not mandatory for this, driver key should ideally be setup for each driver as
well as on the MHub devices.
(Please view section 2.5.1 on how to add new drivers.)

5.4.2 Driver Activity Summary

This report ranks all drivers within the selected driver group based on the total amount
of time the driver has been driving which includes the No. of Trips completed and the
total No. of days that vehicles where utilised. In addition, the Total Trip Distance, No. of
Exceptions and the Total No. of Unique Vehicles used are listed for referencing.

Pre-requisites:

Driver needs to be added to the MZone database. Driver keys need to be setup for each
driver as well as on the MHub devices. Contact your local administrator for further
details.
(Please view section 2.5.1 on how to add new drivers.)

Page 156 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
5.4.3 Driver Event

This report details a chronological record of events for the selected driver over the date
range selected. Information in this report includes the Event Description, Event Location,
Vehicle Description and Registration with co-ordinates grouped by day. Optionally the
report can be further filtered to show only a specific group of events.

Pre-requisites:

Driver needs to be added to the MZone database. Driver keys need to be setup for each
driver as well as on the MHub devices. Contact your local administrator for further
details.
(Please view section 2.5.1 on how to add new drivers.)

5.4.4 Driver Trip Detail

This report details all events that have been recorded within a trip for the selected
driver. For each trip the Start-up and Shutdown Times, Distance, Duration and Vehicle is
listed.

A chronological log of events that occurred within the trip as well as the location of each
event is listed.

Pre-requisites:

Driver needs to be added to the MZone database. Driver keys need to be setup for each
driver as well as on the MHub devices. Contact your local administrator for further
details.
(Please view section 2.5.1 on how to add new drivers.)

Page 157 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
5.4.5 Driver Rating Summary

This report contains the driver rating score for all drivers within the selected driver
group. Additional information such as the No. of trips, Total Trip distance and Total
Duration are indicated.

Pre-requisites:

Driver Rating profiles are needed for the rating.


(Please view section 2.5.2 for more details on how to add Driver Rating Profiles.)

5.4.6 Driver Rating (Simplified)

This report rates all drivers within the selected driver group according to Total Trip
Exceptions and Distance. In addition, the rating of the driver and the driver group scores
are given which indicates if the driver is above or below the average Group Rating.

Pre-requisites:

Driver Rating profiles are needed for the rating.


(Please view section 2.5.2 for more details on how to add Driver Rating Profiles.)

Page 158 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
5.4.7 Driver Rating Trend

This report contains the ratings for all drivers within the selected driver group over
three consecutive periods. The report is indicates if driver ratings are improving or
deteriorating when comparing the information with the previous periods generated.
Trends indicating up are down quickly identifies improving or deteriorating performances
by drivers.

Pre-requisites:

Driver Rating profiles are needed for the rating.


(Please view section 2.5.2 for more details on how to add Driver Rating Profiles.)

5.4.8 POI Analysis Driver per Place

This report lists all drivers within the selected driver group along with its Driver Key
Code. The report identifies the Total No. of visits and Total Duration by a driver against a
particular POI (Place of Interest).

Pre-requisites:

POI’s need to be added into the MZone database before the report is able to identify No.
of Visits and Total Durations.
(Please view section 2.7.1 for details on how to add places.)

Page 159 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
5.4.9 POI Analysis per Driver

This report lists all POI’s within the selected place group. The report identifies the Total
No. of visits, Total Duration and Average Duration visited by the selected driver.

Pre-requisites:

Driver’s and Place’s need to be added to the MZone database.


(Please view section 2.7.1 on how to add places and section 2.5.1 on how to add new drivers.)

5.4.10 Driver Exception Detail

The report lists the selected driver’s exceptions events along with details that included:
Location of Events, Max Duration and Limit for Speed and RPM, Idling Durations and
Temperature Durations.

Pre-requisites:

Driver needs to be added to the MZone database. For this report to be meaningful make
sure there are exception events against the drivers you are reporting on.
(Please view section 2.5.1 on how to add new drivers.)

Page 160 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
5.4.11 Driver Rating

This report calculates the performance of particular driver based on the exception events
that he/she has generated. The report contains a summary of violations rated against
his/her selected Driver Rating Profile to obtain a final score.

Pre-requisites:

Driver Rating profiles are needed for the rating.


(Please view section 2.5.2 for more details on how to add Driver Rating Profiles.)

Page 161 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
5.5 Depot Reports
Depot reports are MRM exclusive reports which are designed to
provide fleet managers with fleet performances, identification of
client mismanagement in jobs performed as well as fleet
utilization.

5.5.1 Vehicle Itinerary

An itinerary print out for all vehicles within the selected vehicle group is listed. Each
resource Itinerary is conveniently separated on each page for easy hand out. Drivers not
making use of the PDA will require this report.

Pre-requisites:

At least one Job must be assigned to a resource for this report to populate.
(Please view section 4.2 on how to assign Jobs.)

5.5.2 Job Analysis

This report lists all customers within the selected customer group which indicates
performances to the selected clients. This report may indicate potential issues that arise
with customers by identifying jobs that have their stop times exceeded consistently.
Additional information such as Best and Worst stop times are also indicated.

Pre-requisites:

Customers need to be on the MZone system with Jobs assigned to them.


(Please view section 2.11.1 to add new customers and section 4.2.2 to assign jobs.)

Page 162 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
5.5.3 Depot Activity

This report displays all Depot Activity for the selected vehicle/driver over the selected
date range. This report can identify to ensure that resources are departing the depots as
scheduled and that all resources are utilized. In addition the total time spent at the
depot is also reported by means of the Dwell Time field within the report.

Pre-requisites:

A depot needs to be created on the MZone system with active resources.


(Please view section 2.11.4 on how to create depots.)

5.5.4 Driver Debriefing

An analysis of the performance of the selected driver over a user defined date range.
This report indicates driver performances to the assigned tasks.

Pre-requisites:

Drivers must be on the MZone system along to jobs assigned.


(Please section 2.5.1 on how to add drivers and section 4.2.1 on how to assign jobs.)

5.5.5 Depot Performance

An analysis of the performance of all depots within the selected driver group which can
identify depot resources that are either departing on schedule or not. The total time
spent for a resource on top of the scheduled stop time within the depot can be identified
by the Total Excess Dwell Time.

Pre-requisites:

A depot needs to be created on the MZone system with active resources.


(Please view section 2.11.4 on how to create depots.)

Page 163 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
5.5.6 Task Analysis

This report gives a user the ability to analyze tasks for the selected date range on Job
Duration VS Trip Duration. Essentially this report identifies actual VS planned in a report
format for referencing. Other information in this report include: Differences in actual and
planned times, Vehicle details and Registration.

Pre-requisites:

Population of actual data is required for this analysis.


(Please view section 4.3 on how to manage jobs.)

5.5.7 Task Detail

This report displays the full details of the selected tasks. Information such as Planned
Arrival and Departure Times, Actual Arrival and Departure Times and its Total Travel
Distance are indicated.

Pre-requisites:

Jobs must be least be assigned to a resource.


(Please view section 4.2 for more details on Job assignment options)

Page 164 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09
5.5.8 Task Summary

A summary of tasks information for the selected criteria are indicated in this report.
Details on the percentage of jobs planned and achieved are calculated. Additional
information includes Duration Times and Total Stop Times are indicated in the reports.

Pre-requisites:

Tasks must have jobs assigned with actuals being populated.


(Please view section 4.2 on how to Job assignment options.)

5.5.9 Vehicle Task Job performance

This report provides an analysis of the performance of the selected vehicles against the
jobs assigned. Details such as Total Planned, Total Executed and No. of Late Arrivals can
be determined.

Pre-requisites:

Tasks must have jobs assigned with actuals being populated.


(Please view section 4.2 on how to Job assignment options.)

Page 165 of 165


MZone 4 Product Manual, v 4.3.13 21-Jul-09