RTS350OperationsGuide 85

version 3.
50
Operations Guide
Roadnet, RouteNet, Territory Planner, FleetLoader, and MobileCast are registered trademarks of
Roadnet Technologies, Inc.
Roadnet Technologies, Inc. assumes no liability for any real or consequential damages related to
the use or misuse of the Roadnet Transportation Suite software or documentation.
2011 Roadnet Technologies Inc., All rights reserved.
Computer Program Code and Screen Displays Copyright 2011 Roadnet Technologies, Inc. All
Rights Reserved. The contents of this material are confidential and proprietary to Roadnet
Technologies, Inc. Unauthorized use, disclosure, or reproduction is strictly prohibited. Rights to
use are governed and limited by license agreement.
This manual is the property of Roadnet Technologies, Inc. It may not be reproduced by any
method, in whole or in part, without written permission of the publisher.
Microsoft Access is a registered trademark or trademarks of Microsoft Corporation in the
United States and/or other countries.
Crystal Reports is a registered trademark of Seagate Software Company.
Geographic Data Technology, Inc.
This product contains proprietary and confidential information of Geographic Data Technology,
Inc. Unauthorized use, including copying for other than testing and standard backup procedures,
of this product is expressly prohibited.
Table of Contents
Table of Contents
Getting Started with the Roadnet Transportation Suite . . . . . . . . . . . . . . . . . . . . . . . . 1
About this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Conventions Used in this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Navigating through the Roadnet Transportation Suite . . . . . . . . . . . . . . . . . . . . . . . . 7
Window Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Managing Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Starting the Roadnet Transportation Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Changing your Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Adding an ODBC Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Roadnet Transportation Suite Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Administration
Setting Up the Administration Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Setting the Administration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Setting the Options for RIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Entering Database User Information for User Defined Data . . . . . . . . . . . . . . . 15
Working with the Authentication Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Locking out All Non-Super Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Setting Additional Security Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Working with Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Working with User Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Working with Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Enabling a Locked Out User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Working with Notification Recipients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Working with Regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Working with Organization Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Setting the Alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Maintaining the Roadnet Transportation Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Working with Maintenance Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Setting the Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Setting the Mobile Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Working with Statuses and Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Adding a Status or Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Working with Bay Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Working with Compartment Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Working with Equipment Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Sharing Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Working with Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Working with Equipment Overrides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Working with Warehouse Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Working with SKU Brands
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Working with Package Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Working with Product Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Working with SKUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Operations Guide
i
2011 Roadnet Technologies, Inc. All rights reserved.
Table of Contents
Working with Planned Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Working with Stack Rules Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Mix Rules Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Warehouse Zone Pick Order Methods . . . . . . . . . . . . . . . . . . . . . . .
Establishing Mix Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Establishing Stack Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Pallet Loading Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Pallet Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Skill Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Employee Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Employees . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tracking Productivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with the Distance Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Travel Time Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Onboard Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Account Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Service Time Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Time Window Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Service Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Service Pattern Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Planning Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Reason Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Cancel Stop Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Undeliverable Stop Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Stop Signature Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Order Financial Detail Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Order Status Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Driver Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Surveys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding a Survey . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating the Survey Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Assigning Questions to the Surveys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.Working with Canned Text Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Container Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Containers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Wireless Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Route Exception Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Location Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the Location Notebook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Location Overrides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ii
151
159
160
162
163
165
167
168
170
172
174
175
179
183
185
186
188
189
191
193
194
195
198
200
202
205
209
211
212
213
214
216
217
218
218
219
220
222
223
225
227
229
235
237
240
259
Roadnet Transportation Suite

Table of Contents
Working with Location Substitutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Working with Void Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Loading Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with User Defined Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Rush Hour Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating the Rush Hour Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Choosing the Rush Hour Map Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding a Rush Hour Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding Rush Hour Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Time of Day Restriction Models . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Barriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding Barriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying Barriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting Barriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding Cell Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Editing Cell Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Switching Cell Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting Cell Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Splitting Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Editing Cell Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Actual vs. Planned Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Entering Actual Route/Stop Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Drivers Duty Period History . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Area Distances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Combining Routing Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Updating Service Times Using Service Time Maintenance . . . . . . . . . . . . . . . . . .
Setting Update Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Service Time Maintenance Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Updating Service Times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the Interactive Graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Maintaining the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Transporting Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Delivery Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Order Classifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Delivery Waves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating Delivery Wave and Delivery Window Template . . . . . . . . . . . . . . . .
Adding Filters to Delivery Waves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding Skill Sets to Delivery Waves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Delivery Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding Delivery Windows Individually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with the Business Calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operations Guide
261
262
263
265
266
267
269
270
274
277
287
287
288
289
290
290
291
292
293
293
294
295
295
297
298
300
305
308
310
312
312
314
316
316
321
327
330
332
333
338
339
340
341
341
345
iii
Table of Contents
Import
Importing into the Roadnet Transportation Suite . . . . . . . . . . . . . . . . . . . . . . . . . .
Importing Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Importing Location Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Importing Daily Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Importing Daily Route Information for MobileCast . . . . . . . . . . . . . . . . . . . . . . . .
Importing Daily Container Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Importing Static Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Importing a Routed Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Importing Maintenance Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
lmporting OnBoard Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Combine from Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the Batch Import Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Import Layouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating Import Layout Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting the Import File Layouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printing a Layout Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Switching Between Import Layout Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Location Import File Available Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Location Extensions Import File Available Fields . . . . . . . . . . . . . . . . . . . . . .
Daily Orders Import File Available Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Routed Solution Import File Available Fields . . . . . . . . . . . . . . . . . . . . . . . . . .
OnBoard Import File Available Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Send Orders Export File Available Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Export Routes File Available Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User Upload File Available Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exporting Loaded Routes Available Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Import Route Available Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Stop Available Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Product Order Table Available Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Line Item Table Available Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Route Driver Table Available Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Order Container Assignments Table Available Fields . . . . . . . . . . . . . . . . . . .
Line Item Container Assignments Table Available Fields . . . . . . . . . . . . . . . .
Order Financial Details Table Available Fields . . . . . . . . . . . . . . . . . . . . . . .
Order Activities Table Available Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Route Equipment Table Available Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Employee Available Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Driver Available Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Container Available Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Equipment Available Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Package Type Available Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SKU Available Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SKU Brand Available Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Depot SKUs Available Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Equipment Types Available Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv
347
350
354
357
362
364
367
368
372
374
376
378
383
383
384
386
387
387
393
397
400
405
406
409
412
414
415
417
419
420
421
421
422
423
424
424
425
426
429
430
431
432
434
434
435

Table of Contents
Skill Set Available Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Activities Available Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Skill Set - Activities Available Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Bay Type Capacity Available Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Pallet Type Capacity Available Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
438
439
439
439
440
Roadnet-Routing Editor
Creating Routes in the Routing Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
Entering the Routing Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
Maintaining Items in the Routing Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
Using Maps in the Routing Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
Viewing Routes in the Routing Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453
Using the Toolbars in the Routing Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
Setting the Routing Editor Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458
Working with Standard Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
Creating Standard Route Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
Creating Standard Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
Creating Standard Routes and Standard Route Overrides from Existing Routes 478
Adding Standard Routes to a Standard Route Set . . . . . . . . . . . . . . . . . . . . . . . 479
Adding Stops to a Standard Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
Adding Breaks and Layovers to Standard Routes . . . . . . . . . . . . . . . . . . . . . . . 484
Adding Mid-Route Depots to Standard Routes . . . . . . . . . . . . . . . . . . . . . . . . . 485
Sequencing Standard Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
Saving the Standard Routes in the Routing Editor . . . . . . . . . . . . . . . . . . . . . . 487
Creating Daily Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
Using the Routing Pass Options Notebook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
Creating Routing Passes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
Locking and Unlocking Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
Evaluating the Routes in the Routing Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
Balancing the Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513
Combining Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
Time Window Swap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
Adjust Mid-Route Sourcing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
Finding Paired Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
Listing Duplicate Geocodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
Regeocoding A Stop in the Routing Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
Working With Route Reloads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
Routing Unassigned Stops or Transferring Stops . . . . . . . . . . . . . . . . . . . . . . . . . . 522
Adding Not Considered, Void, or Future Orders to a Route . . . . . . . . . . . . . . . . . . 527
Sequencing Stops in the Routing Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
Unassigning Stops on a Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
Finding a Route, Stop, or Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
Changing a Routes Properties in the Routing Editor . . . . . . . . . . . . . . . . . . . . . . . 533
Adding a Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
Working with Preferred Route Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
Assigning Drivers and Equipment to Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Operations Guide
v
Table of Contents
Assigning Sequential Route IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Assigning Start Times to the Routes in the Routing Editor . . . . . . . . . . . . . . . . . .
Splitting an Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Saving the Routes Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Saving the Routes in the Routing Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Uploading Selectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding Breaks to a Route in the Routing Editor . . . . . . . . . . . . . . . . . . . . . . . . . .
Inserting a Depot onto a Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Mid-Route Sourcing Depots on a Route . . . . . . . . . . . . . . . . . . . . .
Adjusting the Service Time for a Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Assigning the Load Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Updating the Locations Preferred Route ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printing Reports in the Routing Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printing Driver Directions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Building the Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sending Orders from the Routing Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Removing Orders from the Routing Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sending the Routes to MobileCast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Archiving the Routing Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Combining Routing Sessions in the Routing Editor . . . . . . . . . . . . . . . . . . . . . . . .
Exporting Routes from the Routing Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a New Routing Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Rolling Routes and Orders to a New Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Merchandisers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
545
546
547
549
552
553
554
556
558
559
560
561
563
564
566
567
570
571
572
573
575
577
581
582
Territory Planner - Planning Editor

Creating Strategic Routes in the Planning Editor. . . . . . . . . . . . . . . . . . . . . . . . . . .
Entering the Planning Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Maintaining Items in the Planning Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting the Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using Maps in the Planning Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing Territories and Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the Toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating the Territories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the Make Territories Options Notebook . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Evaluating the Territories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Editing the Territories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Assigning Drivers, Equipment, and Other Items to a Territory . . . . . . . . . . . . . . .
Viewing Account Type Distribution Information . . . . . . . . . . . . . . . . . . . . . . . . .
Adding a Territory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Assigning IDs to Several Territories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the Assign Days Options Notebook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Evaluating the Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Editing Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Letting the Planning Editor Suggest the Territory or Routes . . . . . . . . . . . . . . . . .
587
588
589
590
596
604
606
610
611
616
620
622
624
625
628
629
630
637
640
645
vi

Table of Contents
Saving the Territories and Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Finding Territories, Weeks, Routes, Stops, or Location Extensions . . . . . . . . . . .
Changing a Routes Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Assigning Start Times to Several Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Assigning Sequential Route IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Assigning Breaks and Waits to Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Inserting a Depot onto a Route in the Planning Editor . . . . . . . . . . . . . . . . . . . . . .
Assigning New Service Pattern Sets to Location Extensions . . . . . . . . . . . . . . . . .
Assigning Service Time Overrides to Location Extensions . . . . . . . . . . . . . . . . . .
Anchoring Location Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting the Previous Days and Weeks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Geocoding a Location on the Map in the Planning Editor . . . . . . . . . . . . . . . . . . .
Printing Driver Directions in the Planning Editor . . . . . . . . . . . . . . . . . . . . . . . . . .
Shifting the Delivery Days . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printing Reports in the Planning Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printing Maps in the Planning Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Transferring Data to a New Planning Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Saving a Copy of the Current Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Archiving the Planning Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Uploading the Planning Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Updating the Delivery Days in Roadnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sending the Routes to Roadnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sending the Planning Routes to MobileCast . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Send Routes to netScheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Depot Planner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting Depot Planner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding a Depot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Geocoding a Depot in Depot Planner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Assigning Location Extensions to the Depots . . . . . . . . . . . . . . . . . . . . . . . . . .
Evaluating the Depot Planner Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Loading Trucks in the FleetLoader Loading Editor . . . . . . . . . . . . . . . . . . . . . . . .
Setting Up to Load Bay Trucks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Up to Load Bulk Trucks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Entering the Loading Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Loading Trucks in the Loading Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the Loading Options Notebook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preparing to Edit Trucks in the Loading Editor . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting the Loading Editor Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using Loading Editor Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Editing Trucks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Analyzing the Loaded Truck . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Editing the Status of a Convertible Bay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reloading an Individual Bay/Pallet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Moving SKUs on the Loaded Truck . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Saving Your Work in the Loading Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operations Guide
649
650
652
653
654
655
657
659
660
661
664
665
666
668
670
671
672
674
676
677
680
682
684
686
688
688
688
689
689
690
693
694
700
705
706
708
720
721
721
727
737
738
739
740
741
746
vii
Table of Contents
Deleting Pre-Built Loading Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Exporting the Loaded Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printing Reports in the Loading Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exiting the Loading Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
747
748
750
751
MobileCast - Dispatcher
Dispatching in MobileCast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using Windows in the Dispatcher Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reading the Data Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting a Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting Routes, Step 1: Display the Route . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting Routes, Step 2: Assign Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting Routes, Step 3: Tell MobileCast to Start the Route . . . . . . . . . . . . . . .
Completing Stops on a Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Completing a Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting a Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Finding a Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tracking Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tracking Equipment with the Equipment Map . . . . . . . . . . . . . . . . . . . . . . . . . . .
Following Equipment and Using Route Position History . . . . . . . . . . . . . . . . . . .
Using the Position History Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Following Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Following a Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Evaluating Cancelled Stops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Re-geocode and/or Adjust the Radii for Cancelled Stop Locations . . . . . . . . .
Working with Route Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing Route Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using Route Watch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the Route Watch Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing Route Exceptions on the Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing Diagnostic Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checking the Route Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Container Statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scan Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with the Route Properties Notebook . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding, Changing, Deleting, or Unassigning Stops on a Route . . . . . . . . . . . . . . .
Adding a Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing a Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting a Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unassigning a Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Entering Order or Line Item Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding a New Order or Line Item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing or Deleting an Order or Line Item . . . . . . . . . . . . . . . . . . . . . . . . . .
Processing an Order or Line Item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding Breaks, Waits, or Layovers to a Route
.........................
753
754
756
762
762
763
769
772
775
777
778
780
782
784
784
788
790
792
794
797
797
798
800
800
803
807
808
809
810
811
813
813
815
817
817
819
819
822
823
825
viii

Table of Contents
Inserting a Mid-Route Depot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Working with Unassigned Stops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Assigning Unassigned Stops to a Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Letting MobileCast Determine the Best Route . . . . . . . . . . . . . . . . . . . . . . . . .
Combining Unassigned Stops to Existing Stops in MobileCast . . . . . . . . . . . .
Locating Unassigned Stops on a Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding and Editing Unassigned Stops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting Unassigned Stops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing the Order of Stops on a Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Transferring Stops between Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cancelling a Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a Static Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating Route and Item Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing and Reporting Route and Item Notes . . . . . . . . . . . . . . . . . . . . . . . . .
Creating and Viewing Users Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Completing User-Defined Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Wireless Communication with MobileCast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Wireless Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing Event Receipts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with the Message Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Disabling Wireless Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sending Messages to the Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printing Driver Directions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checking for Space on a Piece of Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Swapping Equipment at a Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Assigning Equipment to Be Swapped . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Handling the Swap at the Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing Item Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing My Routes Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing Distance by Jurisdiction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing User Defined Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with OnTrack Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Generating Stops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Accounting for a Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Refreshing the Windows in Dispatcher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
828
830
830
832
836
837
838
842
844
846
848
849
850
850
852
855
858
860
860
863
864
866
867
868
870
872
872
873
875
876
877
880
881
882
883
885
MobileCast - Loads
Using MobileCast to Manage Loads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Load Key Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Up for Loads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting the Load Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding or Changing Load Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Load Customers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Load Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
887
887
889
890
892
892
893
895
Operations Guide
ix
Table of Contents
Working with Customer Commodities, STCC Codes, Freight Classes, Common Carriers,
and Load Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 897
Managing Loads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 898
Creating the Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 900
Adding Load Stops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 903
Claiming a Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 905
Assigning the Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 906
Assigning the Load to an Existing Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 906
Assigning the Load to a New Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 907
Assigning the Load to a Common Carrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 909
Completing a Load Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 911
Relaying the Load to Another Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 914
Transferring the Load to a Common Carrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 916
Transferring the Load to Another Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 918
Editing a Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 920
Searching for Loads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 922
Searching for Completed Loads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 922
Searching for Loads on Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 922
Canceling a Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 924
Returning a Load to the Available List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 925
Working with Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 927
Reports
Printing Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Previewing Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Grouping Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printing Report Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Report View Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with the AVP Route Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . .
AVP Stop Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Actual vs. Planned Route Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Actual vs. Planned Stop Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with the Carbon Emissions Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Compartment Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Compartment Detail Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Consolidated Off-Day Delivery and Less Than Minimum Stops Report . . . . . . .
Days Serviced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Delivery Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Distance by Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Distance by Jurisdiction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Draft Daily . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Driver Check Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Driver Itinerary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Driver Manifest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Roadnet Driver Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
x
929
930
932
933
935
936
938
939
940
941
943
945
946
947
949
950
952
953
954
955
956
958
960

Table of Contents
MobileCast Driver Performance Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 962

Driver Productivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 963
Driver Returns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 964
Driver Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 965
Driver Service Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 966
Driver Survey . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 967
Driver Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 969
Employee Hours Worked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 970
Employee Hours Worked Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 972
Equipment Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 974
Equipment Utilization Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 975
Global Cost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977
Global Itinerary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 978
Global Manifest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 979
Global Time/Distance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 981
Key Performance Indicators Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 982
Key Performance Indicators Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983
Less Than Minimum Orders
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 984
Less Than Minimum Stops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 986
Load Truck Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 988
Load Productivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 990
Load Validation Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 991
Location Delivery Cost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 993
Location Returns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 996
Location Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997
Multiple Pallet Pick Sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 998
Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1000
Off-Day Delivery Exception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1001
Open/Close Exception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1002
Order Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004
Pallet Pick Sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1006
Pick Sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1008
Prebuild Orders Customer Invoice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1009
Prebuilt Pallet Pick Sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1011
Prebuilt Pick Sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1013
Re-Route Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1015
Resource Route by Day . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1017
Resource Stop List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1018
Resource Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1019
Route Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1020
Route Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1021
Route Pallet Pick Sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1022
Route Pick Sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1024
Route Summary Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1026
Route Variance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1029
Selection Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1030
Operations Guide
xi
Table of Contents
Session Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Session Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SKU by Package Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SKU Summary Sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Standard Route Driver Survey . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Standard Route Stop List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Roadnet Stop List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FleetLoader Stop List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Territory Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Territory Stop List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Territory Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Time Window Exception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Time Window Override . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All Loads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Week Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1044
1045
1046
Report Samples
Report Samples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AVP Route Summary Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AVP Stop Detail Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Actual vs. Projected Route Summary Report Sample . . . . . . . . . . . . . . . . . . . . . .
Actual vs. Projected Stop Detail Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . .
Carbon Emissions Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Compartment Detail Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Compartment Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Consolidated Off-Day Delivery and Less Than Minimum Stops Report . . . . . . .
Days Serviced Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Delivery Detail Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Distance by Area Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Distance by Jurisdiction Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Draft Daily Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Driver Checkout Sheet Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Driver Itinerary Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Driver Manifest Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Driver Performance Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Driver Productivity Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Driver Service Log Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Driver Returns Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Driver Statistics Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Driver Survey Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Driver Utilization Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Employee Hours Worked Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Employee Hours Worked Summary Report Sample . . . . . . . . . . . . . . . . . . . . . . .
Equipment Utilization Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Equipment Utilization Metrics Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . .
Global Cost Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1047
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
xii

Table of Contents
Global Itinerary Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Global Manifest Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Global Time/Distance Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Key Performance Indicators Detail Report Sample . . . . . . . . . . . . . . . . . . . . . . .
Key Performance Indicators Summary Report Sample . . . . . . . . . . . . . . . . . . . . .
Less Than Minimum Orders Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Less Than Minimum Stops Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Load Truck Diagram Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Load Productivity Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Load Validation Diagram Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Location Delivery Cost Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Location Delivery Cost Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Location Returns Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Location Statistics Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MobileCast Driver Performance Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . .
Multiple Pallet Pick Sheet Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Notes Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Off-Day Delivery Exception Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Open/Close Exception Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Order Summary Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Pallet Pick Sheet Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Pick Sheet Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prebuild Orders Customer Invoice Report Sample . . . . . . . . . . . . . . . . . . . . . . . .
Prebuilt Pallet Pick Sheet Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prebuilt Pick Sheet Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Route Pallet Pick Sheet Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Route Pick Sheet Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Re-Route Analysis Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Resource Route By Day Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Resource Stop List Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Resource Utilization Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Route Exceptions Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Route Metrics Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Roadnet Route Summary Statistics Report Sample . . . . . . . . . . . . . . . . . . . . . . .
MobileCast Route Summary Statistics Report Sample . . . . . . . . . . . . . . . . . . . . .
Route Variance Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Selection Summary Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Session Analysis Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Session Summary Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SKU by Package Type Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SKU Summary Sheet Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Standard Route Driver Survey Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . .
Standard Route Stop List Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Roadnet Stop List Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FleetLoader Stop List Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Territory Location Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operations Guide
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
xiii
Table of Contents
Territory Stop List Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Territory Summary Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MobileCast Time Window Exception Report Sample . . . . . . . . . . . . . . . . . . . . .
Roadnet Time Window Exception Report Sample . . . . . . . . . . . . . . . . . . . . . . . .
Time Window Override Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All Loads Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Week Summary Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1123
1124
1125
1126
1127
1128
1129
Using Windows
Using Roadnet Transportation Suite Maps and Windows . . . . . . . . . . . . . . . . . . .
Using List Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using Maintenance Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Searching the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Arranging List and Maintenance Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the Search Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Up the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Map Properties Notebook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Map Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Map Navigation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Map Hotkey Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Finding a Location on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Landmarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Editing the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding Street Segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Editing Street Segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Impasses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Penalty Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting the Global Penalties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Updating by Road Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Evaluating the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Explaining Stop Type Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1131
1132
1134
1134
1136
1141
1147
1148
1157
1159
1161
1162
1164
1165
1165
1166
1170
1172
1173
1174
1176
1178
Menu Options
Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Maintenance Module Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Import Module Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Territory Planner Planning Editor Menu Options . . . . . . . . . . . . . . . . . . . . . .
Roadnet Routing Editor Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FleetLoader Loading Editor Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . .
MobileCast Dispatcher Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Administration Module Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reports Module Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1179
1179
1182
1183
1186
1190
1192
1196
1197
Route History
Using Route History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1199
Retrieving Information from Route History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1201
xiv

Table of Contents
Route Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Stop Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Route History Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Route History Entity Relationship Diagrams (ERD) . . . . . . . . . . . . . . . . . . . . . .
Introducing netScheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Day Commander . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing the Delivery Date or Customer in Day Commander . . . . . . . . . . . .
Viewing an Order, Delivery Wave, or Delivery Window . . . . . . . . . . . . . . . .
Using the Order Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding, Deleting, or Closing a Delivery Window in Day Commander . . . . .
Changing Properties for a Wave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing Skill Set Properties for a Wave . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Review Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Locking and Unlocking Orders in Day Commander . . . . . . . . . . . . . . . . . . . .
Columns for the Delivery Windows Window . . . . . . . . . . . . . . . . . . . . . . . . .
Columns for the Routes Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Columns for the All Deliveries Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with the Cost Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Entering Orders Individually in Cost Analyzer . . . . . . . . . . . . . . . . . . . . . . . .
Columns in the Cost Analyzer Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Importing Individual Orders into Cost Analyzer . . . . . . . . . . . . . . . . . . . . . . .
Importing Batches of Orders into netScheduler . . . . . . . . . . . . . . . . . . . . . . .
Columns in the Import Orders Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1203
1227
1236
1250
1255
1256
1256
1257
1259
1260
1260
1263
1264
1266
1267
1268
1270
1272
1272
1274
1275
1278
1281
Glossary and Index

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1283
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1299
Operations Guide
xv
Table of Contents
xvi

Getting Started with the Roadnet Transportation Suite

Used with: Roadnet, Territory Planner, FleetLoader, MobileCast
We all know how efficiently the Roadnet Transportation Suite can handle your everyday
routing, planning, and loading needs. But, do you know how easy it is to start using and
maintaining your companys information? Each section below contains a set of basic
instructions about the Roadnet Transportation Suite. Simply follow the hyperlinks for
instructions on how to perform your most common tasks for routing, strategic planning,
and loading your trucks. Its that easy! In no time youll be ready to create your routes,
analyze their efficiency, and manage your loading capacity.
Roadnet
Used with: Roadnet
Roadnet, part of the Roadnet Transportation Suite, is a comprehensive routing program

that effectively schedules and routes your equipment. For instance, you can use Roadnet
to create standard routes or standard route overrides, which can be added to the set and
used as a basis for future routing. Once you have created your new routes, you can use the
many tools and reports included in Roadnet to analyze and change your new routes as
needed.
The first step to using Roadnet is to set up and maintain your data. The Maintenance
module allows you to enter all of your customers essential information, which is then
used to create your routes. There are eleven key steps you need to complete before you
can begin creating your routes. These steps are: adding regions, adding equipment types,
adding equipment, adding employee types, adding employees, adding drivers, adding
scenarios, adding service time types, adding time window types, adding location types,
and setting the options.
Next, youll want to keep your locations and orders up to date. This task may seem
difficult, but Roadnet allows you to quickly import your companys locations and orders.
After your location and orders have been imported into Roadnet, you can use the Routing
Editor to create your standard routes. Once this is done, you can create your daily routes,
add stops, sequence stops, and assign drivers and equipment.
Now that youve successfully created your routes, you can use the map in the Routing
Editor to view and evaluate the routes. Then, once your finished reviewing your routing
sessions, Roadnet gives you the option to send your orders elsewhere for storage or
additional use. Furthermore, you are able to generate and print any number of informative
reports.
Roadnet has many additional features not described above; refer to the complete Roadnet
Transportation Suite Operations Guide or the complete help system for information on
all of Roadnets powerful features.
Operations Guide
1
Territory Planner
Used with: Territory Planner
Territory Planner, part of the Roadnet Transportation Suite, is a strategic planning tool
that lets you easily perform reroutes, changing some of the parameters without losing your
existing routes. For instance, you can use Territory Planner to determine the consequences
of adding or eliminating trucks on the road, or to determine the effects of a large, new
contract. Once you have created your new routes, you can use the many tools and reports
included in Territory Planner to analyze and change your new routes as needed.
The first step to using Territory Planner is to set up and maintain your data. The
Maintenance module allows you to enter all of your customers essential information,
which is then used to create your routes. There are fourteen key steps you need to
complete before you can begin creating your territories. These steps are: adding regions,
adding equipment types, adding equipment, adding employee types, adding employees,
adding drivers, adding scenarios, adding service time types, adding time window types,
adding service patterns, adding service pattern sets, adding planning sessions, adding
location types, and setting the options.
Next, youll want to keep your locations and location extensions up to date. This task may
seem difficult, but Territory Planner allows you to quickly import your companys
locations and location extensions.
After your location and location extensions have been imported into Territory Planner,
you can use the Planning Editor to create and edit your routes, and to create and edit
your territories. Then, once your routes and territories are created you can transfer data to
a planning session, selecting the location extensions and/or any other supporting
information you may want to transfer.
Now that youve successfully created your routes, territories, and planning sessions, you
can use the map in the Planning Editor to view and evaluate the territories and routes.
Then, once your finished reviewing your territories and planning sessions, Territory
Planner can upload the routing information to your network, mainframe, or another
computer, and you can upload any of the fields that can be imported from the location or
location extension file. Furthermore, you are able to generate and print any number of
informative reports, and print maps directly from the Planning Editor.
Territory Planner has many features not described above; refer to the complete Roadnet
Transportation Suite Operations Guide or help system for information on these features.
FleetLoader
Used with: FleetLoader
FleetLoader, part of the Roadnet Transportation Suite, lets you quickly and easily load
your beverage trucks. When using FleetLoader, you can choose to load your trucks in a
manner that is easier for the warehouse workers (warehouse friendly) or so that it is easier
for the driver to unload (driver friendly) or a combination of both. Once you have loaded
2

your trucks, you can use the tools and reports included with FleetLoader to analyze and
change the trucks as needed.
The first step to using FleetLoader is to set up and maintain your data. The Maintenance
used to load your trucks. There are nine key steps you need to complete before you can
begin creating your routes. These steps are: adding regions, adding bay types, adding
equipment types, adding equipment, adding SKU brands, adding package types, adding
SKUs, adding loading preferences, setting the stack and mix rules, and setting the options.
Next, youll want to keep your routes up to date. You can do this by simply using
FleetLoaders import feature to import the routes that will be loaded onto your trucks.
Prior to loading your trucks, you need to define the load truck options. The Load Truck
Options allow you to set how the Loading Editor functions, such as when warnings are
displayed for violations of certain loading rules and how information is displayed in the
windows.
After youve entered all of the necessary information into the Maintenance module, and
established your preferences, you can load your trucks from within the Loading Editor,
which gives you easy access for editing your trucks and viewing the products in each bay.
Now that youve successfully loaded your truck(s), you can use FleetLoader to analyze
the loaded truck and move SKUs as necessary to fine-tune the load. You can use the
different windows to move products between bays, or move it around within a bay.
When editing routes and loading trucks, you should save your work periodically in the
Loading Editor. However, once the routes have been saved or locked, you may need to
change its status.You can lock, unlock, or clear the status of a route easily from within the
Routes window. Furthermore, you are able to generate and print any number of
informative reports.
FleetLoader has many features not described above; refer to the complete Roadnet
Transportation Suite Operations Guide or help system for information on these features.
Getting Started with MobileCast
Used with: MobileCast
MobileCast, part of the Roadnet Transportation Suite, is a comprehensive routing

program that effectively schedules, routes, and keeps track of your deliveries. When using
MobileCast, you can easily handle your most common tasks such as creating routes,
starting routes, completing stops and routes, tracking efficiency, and monitoring your
drivers performance.
The first step in using MobileCast is to set up and maintain your data. The Maintenance
used to create your routes. There are twelve key steps you need to complete before you
can begin creating your routes. These steps are: adding regions, setting the options, adding
statuses and types, adding employees, adding drivers, adding equipment, adding
Operations Guide
3
locations, adding travel models, adding reason codes, adding cancel stop codes, adding
container types, and adding containers.
If you are using wireless communication, then youll need to learn how to work with
driver alerts, undeliverable stop codes, text messaging, wireless events, the message
center, and how to send messages to the drivers.
Next, youll want to keep your information up to date. This task may seem tedious, but
MobileCast allows you to quickly import information about containers, drivers,
employees, equipment, routes, static routes, and your customers locations and orders.
After your locations and orders have been imported into MobileCast, you can use the
Dispatcher to create your routes. Once this is done, you can add stops, transfer stops,
assign drivers and equipment, assign and unassign stops, create static routes, plus start and
complete your routes.
Now that youve successfully created your routes and become more comfortable with the
functions of MobileCast, you can use the windows and maps in the Dispatcher to view
your routes, track drivers, track equipment, view route and equipment position history,
and look at any route exceptions. Furthermore, you can generate and print both driver
directions and any number of informative reports.
MobileCast has many additional features not described above; refer to the complete
Roadnet Transportation Suite Operations Guide or help system for information on these
features.

About this Manual
About this Manual

This Operations Guide explains how you can use the Roadnet Transportation Suite to
effectively route and load your equipment. The Roadnet Transportation Suite is composed
of three major programs: the Roadnet Routing Editor, the Territory Planner Planning
Editor, the MobileCast Dispatcher, and the FleetLoader Loading Editor. Although you
may only be using a portion of the overall suite, this Operations Guide contains
instructions on using the entire suite.
The manual is divided into several sections:
Introducing the Roadnet Transportation Suitedescribes basic program operations

and navigation common to all portions of the Roadnet Transportation Suite.
Maintaining the Roadnet Transportation Suitea section of detailed steps for

entering and maintaining your data for all portions of the Roadnet Transportation
Suite.
Importing into the Roadnet Transportation Suitea section that explains the import
process and outlines import criteria for all portions of the Roadnet Transportation
Suite.
Creating Routes in the Routing Editorextensive instructions for performing the

tasks that are critical to creating daily routes using the Roadnet Routing Editor.
Creating Routes in the Planning Editorextensive instructions for performing the

tasks that are critical to creating planning routes using the Territory Planner Planning
Editor.
Loading in the Loading Editorextensive instructions for performing the tasks that
are critical to loading your trucks using the FleetLoader Loading Editor.
Dispatching in MobileCastextensive instructions for performing day-to-day

routing tasks using the MobileCast Dispatcher.
Reporting in the Roadnet Transportation Suitedescribes all the reports you can
print in the Roadnet Transportation Suite.
Route Historydescribes how the Route History database is accessed and set up.
The Route History database was designed to allow you to keep historical routing data
longer, and make it easier to query against it to extract data, such as for reports.
Glossarya glossary to help with any unfamiliar terms used in the Roadnet
Transportation Suite.
In addition, an index is included to help you locate information in the manual.

Conventions Used in this Manual
All references to keyboard keys are bracketed; for example:

Press [Enter] to confirm.
All references to buttons on the screen are bracketed; for example:
Operations Guide
5
Click on the [OK] button when all information is complete.
The word press refers to keyboard keys; click refers to the mouse.
Menu paths are displayed in bold italics beneath the task to provide a quick reminder
of how to access a particular function; for example:
List Product Package Types
The term click refers to using the primary mouse button; right-click refers to clicking
the secondary mouse button; and double-click refers to clicking on the primary
mouse button twice.

Navigating through the Roadnet Transportation Suite

The Roadnet Transportation Suite has an intuitive, graphical interface that makes the
program easy to learn and use. It is based on menus, icons, and windows that are chosen
and managed with the mouse. For more information on navigating through the suite, see
Managing Windows and Window Types.
Window Types
Several types of windows are used in the Roadnet Transportation Suite to display and
manage routing information. The types of windows used are:
List windowused to present information, such as routes, stops, orders, etc. You
can change the way the data is presented in the window, but the data itself cannot
be altered.
Maintenance windowused to present and edit information. You can alter the
data, as well as the way it is presented in the window.
Mapsused in the Routing Editor, Planning Editor, and Maintenance modules to
view and update routes and to geocode locations. The maps themselves can be
updated and edited.
The maps in the Roadnet Transportation Suite have some functions that are specific to the
software, or even the module being used. For instance, you can add barriers or cells to the
map in Maintenance, Routing Editor, or Planning Editor; see Working With Barriers and
Working With Cells in the Maintenance section of this manual for more information. In
the Routing Editor you can display the routes on the map, and edit the routes from the
map; see Using the Map in the Routing Editor for more information. In the Planning
Editor you can use the map to evaluate and edit the territories and routes; see Using the
Map in the Planning Editor for more information. In the Dispatcher you can display and
edit the routes from the map; see Using the Map in the Dispatcher for more information.
Managing Windows
To select a particular menu item or icon, point to it and click the mouse button. In
windows that list columns of editable data, double-click (click it twice in a row) to begin
the process of editing a particular line of data.
The windows in will stay open until you close them by doing one of the following:
Click the Close box (the X) in the upper-right corner of the window.
Click the Control box in the upper-left corner of the window and select Close from
the menu.
Double-click the Control box.
Click on the File menu and then click on Exit (modules only).
Press [Ctrl]+[F4].
Operations Guide
7
Choose Window Close All

Throughout the Roadnet Transportation Suite, especially in the Routing and Planning
Editors, and when working with maps, there are several hot keys that you can use to
perform certain actions. Where appropriate, the hot key combination is listed on the menu
next to the option.
Within each module, such as Maintenance, you dont need to close one window before
working on another; you can have several windows open at the same time. To make the
desired window active, click its title bar. However, you must close each module before
entering the next.
You can have several windows open simultaneously in any module; the window
with the brightly colored bar, usually blue, is the active window.

Starting the Roadnet Transportation Suite

The first step in using the Roadnet Transportation Suite is to open the program and log in.
Once you have logged in, the application toolbar is visible, and you can simply click on
a module to open it.
Important: When you log in, you may be forced to change your password. The login
credentials that you enter may be checked against an authentication policy. For
more information on authentication policy, see Working with Authentication
Policy.
Step 1: Double-click on the Roadnet Transportation Suite icon. The Login: window
opens.
Step 2: Enter your username in the User ID field.
Step 3: Enter your password in the Password field. Remember, the password is case
sensitive, so check if [Caps Lock] is on or not.
The database field may or may not

be visible on your Login window,
depending on the environment
variables you have set.
Note: If you enter a password that no longer meets the current authentication policy, the
Change Password window will automatically open. For more information, see
Changing your Password.
Step 4: Click the [Login] button. The application toolbar appears; simply click on the
icon to open the module you want to work with.
Changing your Password
Each user created in the Admin module is assigned a password. You can change your
password any time you are logging into the Roadnet Transportation Suite. There may also
be times when you are forced to change your password. In either case, when you change
your password, the new password may be checked against the current authentication
policy. For instance, the policy may check to see if the password is the correct length. For
more information on authentication policy, see Working with the Authentication Policy.
Operations Guide
9
Note: If the new password will not be checked against the current authentication policy,
the password can be whatever you want it to be.
Step 1: On the Login: window, click the [Change Password] button. The Login: window
that allows you to change your password opens.
Step 2: In the Old Password field, enter your current password.
Step 3: In the New Password field, enter your new password. Type the new password
again in the Confirm New Password field.
Note: You cannot use the @ or " symbols as part of the password.
Step 4: Click the [Change & Login] button. If your new login credentials pass the
current authentication policy, then you will be logged in; the application toolbar
appears. If your new password fails the authentication policy, then you will need
to create a valid password.
Note: The [Show Policy] button will appear if you create a password that no longer
meets the current authentication policy. When clicked, the [Show Policy] button
displays the current authentication policy, which you can use as a reminder to help
you create a valid password.
Adding an ODBC Connection
ODBC connections tell the Roadnet Transportation Suite which database you want to use.
You can have many different ODBC connections, each to a separate database. For
instance, if you use different databases for your different regions, you could create an
ODBC connection for each regions database. You can create new ODBC connections
from the Login window, or add an existing ODBC connection to the list of possible
choices when you log in.
You must be on the Login window to perform this procedure.
Step 1: On the Login window, click the [Configure] button. The Data Source
Configuration window opens.
Step 2: To add an ODBC connection, click the [Add] button. The Create New
Datasource window opens. Follow the steps in this and the following windows to
create you new ODBC connection.
To add an existing ODBC connection to the list you can choose from when
logging in to the Roadnet Transportation Suite, check the box in the Include
column for the connection. A check appears in the Include column when a
connection is available to log into.
Step 3: Click the [OK] button. The Login window appears, with the newly selected
connection displayed as the Database.
10

Roadnet Transportation Suite Modules

The Roadnet Transportation Suite is organized into several modules; the actual number
of modules and which modules are available depends on which modules you purchased.
Below is a summary of each of the modules. For detailed instructions on how to use each
module, see the corresponding sections of this manual.
Maintenanceused to set up, maintain, and update all of the information about your
business, such as locations, employees, equipment, etc.
Importused to import location data, daily order information, and other information into
Roadnet Transportation Suite. The Import module is also used to import data from
onboard computer systems.
Routingused to create standard and dynamic routes based on parameters you establish.
The Roadnet Routing Editor also allows you to analyze and modify routes as needed, as
well as maintain items and print reports.
Planningused to create strategic routes based on parameters you establish. The
Territory Planner Planning Editor module also allows you to analyze and modify routes
as needed, as well as maintain items, export routes, and print reports.
Loadingused to load the trucks based on parameters you define once the routes have
been created. FleetLoader also allows you to analyze and change the loaded trucks as
needed.
Dispatchingused to track your routes as they are run throughout the day. In the
MobileCast Dispatcher module, you can change the routes as needed, create new routes,
as well as monitoring your equipment and drivers.
Reportsused to set report options and view and print different reports.
Administrationused to set up the parameters for who is allowed to use which portions
of the Roadnet Transportation Suite by creating the users, user groups, privileges, and
regions.
In addition to the modules you can access from the toolbar, you may also have installed
the Route History feature. Route History establishes a separate database you can use to
access past routing information, such as for writing reports.
Operations Guide
11
12

Administration
Setting Up the Administration Module
Setting Up the Administration Module

Used with: Roadnet, netScheduler, Territory Planner, FleetLoader, MobileCast
The Administration module allows you to set up the people who will use the Roadnet
Transportation Suite, and how they will be able to use the Roadnet Transportation Suite.
For instance, you may have a router who should be able to create routes in the Routing
Editor, but not be able to change the routes in the Dispatcher. On the other hand, your
dispatcher should be able to change the routes in the Dispatcher, but not be able to create
routes in the Routing Editor. Or, there may be an administrator who should be able to not
only work in both the Routing Editor and Dispatcher, but also be able to oversee multiple
regions, while the routers and dispatchers can only see information for their own region.
The many options in the Administration module allows you to control not only who can
use the system, but what portions of the suite they can use and which regions of your
business they can see.
In order to set the users, regions, and access rights for the regions there are several things
you need to create, including the users themselves, groups of users, the regions, the
organization units, and the privileges. Privileges are rights the user has within the Roadnet
Transportation Suite; you can create different sets of privileges which are then assigned
to the users/user groups for each region. Users are the people who will be using the
Roadnet Transportation Suite, and you can collect users who will use the Roadnet
Transportation Suite in the same way together in user groups. The final piece of the puzzle
is regions. Regions are the geographic areas you serve; often a region is equivalent to a
depot. When creating the regions, you specify the users and user groups who have access
to the region, as well as the privileges each user/user group has in that region. Once you
have your regions established you can also setup organization units which allow you to
summarize and filter data based on a group of regions.
Operations Guide
13
Setting the Administration Options

Used with: Roadnet, RIC, Territory Planner, FleetLoader, MobileCast
The Administration Options notebook lets you set up some of the options used with RIC,
as well as entering database user information that a database user can create user-defined
tables in the Roadnet Transportation Suite database.
Step 1: Click on the Administration icon to open the Administration module. The
Administration window opens.
Step 2: Click on the Tools menu and select Options. The Administration Options
notebook opens.
Setting the Options for RIC
Used with: RIC
.The RIC page of the Options notebook lets you specify some of the options used for
setting up users, user groups, and privileges with RIC. If you have users who will be using
RIC, you may want to let new users be added directly from RIC, instead of all users being
added through the Administration module. When you add a user, they will be added to the
user group selected here.
Admininstration window opens.
Step 2: Click on the Tools menu and select Options. The Administration Options
notebook opens.
If Allow adding new RIC user at

client-side login is selected, users
can be added from the RIC login
screen.
Step 3: Click on the RIC tab. The RIC page opens.

Step 4: To allow new users to be added through RIC, check Allow adding new RIC
user at client-side login. Click the Automatically assign new user to user group
arrow and select the user group the new user will be part of.
Notes: New users added through RIC will be added to this user group. Once the user has
been added, the group can only be changed in the Administration module.
For information on user groups, see Working with User Groups.
Step 5: Click the [OK] button.
14

Entering Database User Information for User Defined Data

.The User Defined Data page of the Administration Options notebook lets you enter
existing database user information so that the database user can create user-defined tables
in the Roadnet Transportation Suite database. Once this page is completed, Roadnet Web
Services will have the privileges to create/maintain user-defined tables. For more
information on Web Services, see Roadnet Transportation Suite Web Services Overview;
on creating route exception rules using data from the user-defined tables, see Working
with Route Exception Rules; on user-defined data, see Viewing User-Defined Data.
Notes: The database user must have the appropriate privileges.
For security purposes, it is recommended that you remove the Database User
Name and Database Password information once you are done maintaining userdefined tables.
Step 2: Select the Tools menu and then Options. The Options window opens.
You must enter a username

and password.
Step 3: Click on the User Defined Data tab.

Step 4: Enter the Database User Name and Database Password. You must complete
both fields.
Note: It is recommended that you use tsdba as the Database User Name.
Step 5: Click the [OK] button to save the information.
Operations Guide
15
Working with the Authentication Policy

Used with: Roadnet, Territory Planner, FleetLoader, MobileCast, Roadnet Performance
Dashboard, Roadnet Info Center
There may be times when you need a higher level of security for your organization in
order to protect customer and employee information. For instance, you may need to verify
that the user who is logging into Roadnet Transportation Suite is really that user. You can
create an authentication policy, which is a set of rules to improve the security of Roadnet
Transportation Suite. For example, you can set an authentication policy that requires a
strong password to be at least 6 characters that has a combination of 1 alpha and 1 numeric
character. A strong password will make it difficult for an unauthorized user to access
Roadnet Transportation Suite.
You can create username and password policies that can be checked when any user tries
to login or change a password in Roadnet Transportation Suite. If the login credentials fail
any of the options that are set for the authentication policy, then the user may be able to
correct the password.
Note: You have the option to set selected users to bypass the authentication policy. This
option is set in the User window
Step 1: .Click on the Administration icon to open the Administration module. The
Step 2: Click on the Tools menu, and click on Security, then click Authentication
Policy, and finally Edit. The Authentication Policy window opens.
You can use the Authentication

Policy window to define the
username and password
policies.
Step 3: To define the username and login policies, click on the appropriate option in the
Username and Login Policies section. Click on the arrow open a list of options,
then click on the option to select it, or if necessary, enter the number manually or
use the arrows to scroll to the number. For instance, if you want to specify 3
minutes as the length of time a super user is locked out for when the number of
allowed password attempts has been reached, then click on the Super User
Lockout Period (Minutes) arrow, then click on 3 to select it.
16

Invalid Logins Before Lockoutthe number of times that a user is allowed to

enter an incorrect password before the user is locked out of Roadnet
Transportation Suite. The user will have a locked status, at which point a super
user must unlock the user so that the user is able to log in again.
Super User Lockout Period (Minutes)the amount of time a super user is
locked out of Roadnet Transportation Suite if the number of invalid logins is
reached. Once this time passes, the super user can try to log in again. This must be
at least 3 minutes.
Minimum Username Lengththe minimum length of characters required for
the username; length must be at least 1 character.
Step 4: To define the password policies, click on the appropriate option in the Password
Policies section. Click on the arrow open a list of options, then click on the
option to select it, or if necessary, enter the number manually or use the small
arrows to scroll to the number. For instance, if you want the password to be at
least 6 characters long, enter 6 in the Minimum Password Length field or scroll to
the number 6.
Minimum Password Lengththe minimum length of characters required for the
password; length must be at least 3 characters.
Required Alpha Charactersthe minimum number of alpha characters
required in a password.
Required Numeric Charactersthe minimum number of numeric characters
required in a password.
Passwords Rememberedthe number of consecutive passwords that must be
used before a user can repeat the password. Let say that this is set to 3. When a
user creates a new password, the new password may not match the last 3
passwords used.
Password Expiration Period (Days)the number of days from the time the
password was created until the password expires. When the number of days are
met, and the user tries to log into Roadnet Transportation Suite, they will have to
change their password at that time; the window that allows the user to change their
password will open. If the user does not change their password, then they will not
be allowed to access the Roadnet Transportation Suite.
Expiration Notification Period (Days)the time period for when a user should
be notified that their password is approaching expiration. If the user is
approaching their password expiration, then the user will be notified and has the
option to either change their password before it expires or continue to use Roadnet
Transportation Suite. This must be at least 7 days.
Allow Password to Match Usernameallows users to create a password that is
the same as their username.
Step 5: Click the [OK] button to save the policies.
Operations Guide
17
Once this authentication policy has been created, you can edit the policy, as necessary.
Whenever you make a change to the authentication policy, you can choose whether or not
to use the recently updated policy the next time a user logs in.
18

Locking out All Non-Super Users
Locking out All Non-Super Users

There may be times when you need to perform certain tasks where no users should be
logged in the Roadnet Transportation Suite. For instance, you may need to upgrade a
maintenance patch. For a task like this, you can prevent all non-super users from being
able to access the Roadnet Transportation Suite.
Important: This process does not log out users who are already in the Roadnet
Transportation Suite. You may want to take additional measures to ensure that all
users are logged out.
Step 2: Click on the Tools menu, and select Security, then Non-Super User Lockout and
finally, Enabled. A pop up message appears asking if you wish to continue.
Step 3: Click the [Yes] button. Non-super users will not be able to access the Roadnet
When you are finished with your task, make sure you uncheck the option so users can
have access to the Roadnet Transportation Suite.
Note: A non-super user who tries to login the Roadnet Transportation Suite during this
time period will get a message letting them know that they do not have access.
Operations Guide
19
Setting Additional Security Options
Setting Additional Security Options

In addition to being able to create an authentication policy, you can quickly set other
security options that apply to all users, not just selected users. You can make all users
change their password or have all users login credentials checked the next time they log
in. Lets say that there may be a possible security breach at your organization. As a
security measure, you can set either option. This means that if you have five hundred
users, then all five hundred users, including any super users, will have their login
credentials checked against the current authentication policy. However, on the other hand,
if there are 10 users out of the five hundred users that you do not want the feature to apply
to, then you can manually reverse the feature and disable just those 10 users.
Important: The Require All Users to Change Password and Re-Validate All Users at
Next Login options are not commonly used and are recommended for emergency
situations only, such as if you feel that there may be a possible security breach at
your organization.
To require all users to change their password the next time they log in:
Step 1: Click on the Tools menu, and select Security, then Authentication Policy, and
finally, Require All Users to Change Password. A pop up message appears asking
if you wish to continue.
Step 2: Click the [Yes] button. All users will have to change their password the next
time they log in.
To have all users login credentials checked the next time they log in:
Step 1: Click on the Tools menu, and select Security, then Authentication Policy, and
finally, Re-Validate All Users on Next Login. A pop up message appears asking
if you wish to continue.
Step 2: Click the [Yes] button. Every users login credentials will be checked to make
sure the credentials meet the current authentication policy.
20

Working with Privileges

Privileges are the groups of rights that users have within the Roadnet Transportation
Suite. You can create different privileges, each of which have access to different parts of
the Roadnet Transportation Suite. For instance, you can create a privilege called Router,
which has rights to the Routing Editor but not the Loading Editor, and another privilege
called Loader which has rights to the Loading Editor but not the Routing Editor. Once the
privileges have been created, you can assign them to the users or the user groups for each
region.
Step 2: Click on the List menu and select Privileges. The Privileges window opens,
listing any privileges that exist.
Step 3: On the Privileges window, click on the Add icon or press [Insert]. The Add
Privilege window opens.
The permissions established for each

privilege define which portions of the
Roadnet Transportation Suite a user can
use.
Hint: To add an entry that is similar to an existing one, right-click on the existing entry
and select Clone from the menu that pops up. The Add Privilege window opens
with some information already completed; change the information as necessary
for the new entry.
Step 4: Enter the Name and Description for the privilege. You must enter a name.
Step 5: In the Permissions area, select the permissions the privilege will have. You can
choose from the following permissions:
Operations Guide
21
Has full access to the regionthe user can access the entire Roadnet
Transportation Suite in the selected region(s).
Can perform maintenancethe user can access the Maintenance module, and
can add, change, and delete maintenance items in the Maintenance module and in
the Routing and Planning editors. Any users not granted this permission cannot
enter the Maintenance module.
To allow the user to change the Maintenance Options, check Can change
maintenance options.
To allow the user to be able to set up the parameters to delete routes in Roadnet,
Can control routing deletions must be checked. If this option is not selected, the
user can still delete routes when importing daily orders if another user set the
option.
To allow users to create or edit rush hour and/or time of day restriction models,
check Can edit rush hour and time of day restriction models. The user must have
access to the Maintenance module in order to create rush hour and/or time of day
restriction models. A user who does not have access to edit rush hour and/or time
of day restriction models can still view the rush hour and /or time of day restriction
models and select the rush hour or time of day restriction model that will be used.
To allow users to create, edit, and delete travel time models, and edit the distance
model, check Can edit travel time/distance models. A user who does not have
access to edit travel time models can still select the model that will be used for the
routes.
To allow the user to run the transport script wizard, check Can run transport script
wizard.
To allow users to activate and deactivate the device diagnostics tool for drivers
handheld devices, check Can activate device diagnostics. This permission also
allows users to change the settings associated with device diagnostics. A user who
does not have access to activate device diagnostics can still view device diagnostic
information in MobileCast.
Can configure layoutsthe user can create and change import layouts. If this
option is not selected, the user can view the import layouts, but cannot make any
changes to them.
Can view employees confidential informationthe user can add, change, and
see confidential information on the Driver and employee windows. The affected
information on the Driver window is: license information, date of last physical and
drug test and pay rates. The affected information on the Employee window is:
ADP file number, date of birth, date of hire, and date of termination. If this option
is not selected the user will not be able to see this information, use the Search
Manager on these columns, print or export these columns.
22

Can import datathe user can use the Import module to import information into
the Roadnet Transportation Suite. If this option is not selected, the user will not be
able to import information into the Roadnet Transportation Suite.
Can change import/export optionsthe user can change the options selected
when importing and exporting. If this option is not selected, the user will not be
able to change the options selected when performing an import or export.
Can execute reportsthe user can preview and print reports in the Roadnet
Transportation Suite, from the Reports module or other editor the user has access
to.
To allow the user to be able to view and change the report options, check Can
access report options.
To allow the user to view or change report groups, check Can configure report
groups. Users who do not have permission to access the report options or the
report groups will be able to use the options/groups other users have created. In
order to be able to view the Report Viewer applet in RIC, a user must be granted
this privilege.
Can print mapsthe user can print maps from the Reports module, Planning
Editor, and driver directions. The user must have access to the module as well to
print maps from it. If the user does not have access to print maps, any reports that
include maps cannot be printed.
Can edit mapsthe user can make changes to the streets and nodes on the map.
If this option is not selected, the user can still change the map options that affect
the map display.
Can access Routing Editorthe user can use the Route Editor to create, view,
and edit routes. To allow the user to open the Routing Pass Options notebook and
change the options used to create the routes, check Can access Routing Pass
Options. To allow the user to be able to send the routes from the Route Editor to
MobileCast, check Can update MobileCast.
Can access Planning Editorthe user can use the Planning Editor to create,
view, and edit territories and routes.
To allow the user to open the Make Territories Options notebook and/or Assign
Days Options notebook, check Can access Make Territory/Assign Days Options.
To allow the user to send the routes from the Planning Editor to MobileCast, check
Can update MobileCast.
To allow the user to use Depot Planner, check Can access Depot Planner.
To allow you to send routes from the Planning Editor to netScheduler, check Can
seed netScheduler.
Operations Guide
23
Can access Loading Editorthe user can use the Loading Editor to load, view,
and edit trucks. To allow the user to open the Loading Options notebook, check
Can access Loading Options.
Can view other Dispatcher routesthe user can view another dispatchers route
information within a region. This permission must be enabled in order for the
dispatcher to access routes other than their own within a region. If this option is
not selected, dispatchers will only be able to see those routes assigned to them.
Can access Dispatcherthe user can use the Dispatch module to track routes
throughout the day.
To allow the user to sequence or make other changes to the routes, check Can
make changes. To allow the user to disable the route on the wireless device, check
Can Disable Wireless Communication. To allow the user to delete routes, check
Can delete routes and route details. This permission affects all routes including
routes that have already been started.
To allow the user to make changes to an orders financial information, check Can
edit order financial details.
To allow the user to add new accounting items for the route, check Can insert
accounting items.
In order for the user to work with loads, Is a load user, or Is a load
administrator must be selected. See User Rights in Working with Loads for more
information on using these options.
Can perform accountingthe user can access the Accounting module, as well
as access track types and the Dispatch-Accounting page of the Maintenance
Options notebook, if the user has access to Maintenance. If the user has access to
the Dispatcher, accounting can also be done for the routes in the Dispatcher.
Can manage static routesthe user can access the Static Routes module, as well
as create static routes in the Dispatcher, if the user has access to the Dispatcher.
Can access Roadnet Information Center (RIC)the user can access RIC.
Select the specific applets within RIC the user can access.
Can access Day Commanderthe user can access the Day Commander module
portion of netScheduler to evaluate the days routes. To allow the user to make
changes in Day Commander, check Can make changes.
Can access Cost Analyzerthe user can access the Cost Analyzer portion of
netScheduler to analyze the costs associated with doing business.
Notes: Not all permissions may be available; the permissions that are available will
depend upon the portions of the Roadnet Transportation Suite you purchased.
If you select Can access Roadnet Information Center (RIC) as one of the
permissions, you may want to set the RIC options allow the user to add new RIC
users. See Setting the Administration Options for more information.
Step 6: Click the Save icon, or press [Ctrl]+[S] to save the privilege.
Step 7: Repeat Steps 4 6 to add any other privileges.
24

Step 8: When you are finished adding privileges, click the Close box to close the Add
Privilege window.
Administration icon List Privileges Add icon ([Insert]) Save icon
([Ctrl]+[S])
Existing privileges can be edited or deleted as necessary. See Editing Items and Deleting
Items for more information.
Operations Guide
25
Working with User Groups

Dashboard
A user group is a collection of users who have the same privileges in a region(s). Although
you do not need to use user groups, they can make it easier to change the access rights for
users. For instance, you can create user groups for managers who have access to multiple
regions, such as an East Coast Manager who can see the Maryland, Pennsylvania, New
Jersey, and New York regions and a West Coast Manager who can see the California,
Oregon, and Washington regions. Then, you can simply assign the appropriate user(s) to
each group. And, if you need to change the user in the group, you only need to change the
group, not change the access rights for the user for each affected region.
Hint: You can add users before creating the user groups and then add them to the group
while creating the group, or you can add the users after creating the user groups
and add the user to the group while creating the user.
Step 2: Click on the List menu and select User Groups. The User Groups window
opens, listing all existing user groups.
Step 3: On the User Groups window, click the Add icon or press [Insert]. The Add User
Group window opens.
and select Clone from the menu that pops up. The Add User Group window opens
for the new entry.
Step 4: Enter the User Group ID and Description; the ID is required.
26

Step 5: To add users to the user group, click the [Add] button; the Lookup - Users
window opens.
User groups let you collect users

who use the same portions of the
Roadnet Transportation Suite in
the same regions.
Step 6: Select the user(s) to include in the group, then click the Process icon. To select
multiple users, hold down the [Ctrl] key while clicking on the users. The Lookup
- Users window closes, and the users are listed in the Members list for the group.
Step 7: If the user group will be using the Roadnet Performance Dashboard, click on
the Roadnet Performance Dashboard tab.
To allow the user group to view Roadnet Performance Dashboard, but not create
or change dashboards, check Allow Access.
To allow the user group to create and change dashboards, as well as view them,
check Allow Access, then Allow Setup.
Note: The Roadnet Performance Dashboard tab will only appear if your organization has
purchased Roadnet Performance Dashboard.
Step 8: Click the Save icon, or press [Ctrl] + [S] to save the user groups.
Step 9: Repeat Steps 4 - 8 to add any additional user groups.
Step 10: When all the users groups have been added, click the Close box to close the
Add User Groups window.
Existing user groups can be edited or deleted as necessary. See Editing Items and Deleting
Administration icon List User Groups Add icon ([Insert]) Save icon
([Ctrl]+[S])
Operations Guide
27
Working with Users
Working with Users

Users are the dispatchers, routers, and others in your organization who use the Roadnet
Transportation Suite. Each user can be granted access to different parts of the suite,
different regions, or even have different rights in different regions. Because each user can
have different rights, a unique ID and password must be created when the user is
established. Each time the Roadnet Transportation Suite is started, the ID and password
must be entered. You can group users together in user groups, making it easier to change
the rights for multiple users simultaneously. Once the users have been created, you can
give them privileges for each region.
Step 2: Click on the List menu and select Users. The Users window opens, listing any
users that exist.
Step 3: On the Users window, click on the Add icon or press [Insert]. The Add User
window opens.
and select Clone from the menu that pops up. The Add window opens with some
information already completed; change the information as necessary for the new
entry.
Step 4: Enter the users ID and Name.
The password is case-sensitive, so

make sure to notice if the [Caps
Lock] is on or not.
28

Working with Users
Note: When users are created, the ID and password may be checked against the
authentication policy.
Step 5: Enter the Password. Type the password again in the Verified Password field to
confirm it.
Notes: The password is case-sensitive, so be sure to notice whether the [Caps Lock] is
on or off.
You cannot use the @ or symbols as part of the password.
Step 6: If you want the user to change their password the next time they login, check
Require Password Change on Next Login. For instance, you may enter a default
password, such as 123abc for all users, but have the users change it to something
unique to each user.
Step 7: If you do not want to validate this users login information against the
authentication policy, check Ignores All Authentication Policy. Every time the
user logs in, their login credentials will be not be checked.
Step 8: To prevent a user from being able to login, check Disabled. For example, you
may have an employee whose last day of work is today. You can disable their
login so that they will still exist as a user, but they will not be able to access the
Roadnet Transportation Suite.
Note: The Locked checkbox will be checked if a user exceeded the allowed number of
attempts to enter the correct password. For more information, see Enabling a
Locked Out User.
Step 9: Click the Time Zone arrow and select the time zone that will be used to display
all times not specifically designated to use another time zone. Normally, this will
be the time zone the user works in.
Operations Guide
29
Working with Users
Step 10: Click on the Membership tab to add the user to the appropriate user groups.
You can add users to user groups

from the Add Users window or the
Add User Group window.
Step 11: On the Membership page, click the [Add] button. The Lookup - User Groups
window opens.
Step 12: Select the group(s) the user is part of, then click the Process icon. To select
multiple groups, hold down the [Ctrl] key while clicking on the groups.
To remove a user from a user group, click on the user group then click the
[Remove] button. Click [Yes] to confirm you want to remove the user from the
user group.
Note: You can add users to the user groups when creating the user groups as well.
Step 13: If the user is an administrator or other person who should have access to all
modules in all regions, check This user is a super user (full access to all regions).
Only super users have access to the Administration module.
Step 14: If the user will be using the Roadnet Performance Dashboard, click on the
Roadnet Performance Dashboard tab.
30

Working with Users
To allow the user to view Roadnet Performance Dashboard, but not create or
change dashboards, check Allow Access.
To allow the user to create and change dashboards, as well as view them, check
Allow Access, then Allow Setup.
Notes: Any users that are super users will automatically have full access to view and
change the Roadnet Performance Dashboard.
The Roadnet Performance Dashboard tab will only appear if your organization has
purchased Roadnet Performance Dashboard.
Step 15: Click on the Save icon, or press [Ctrl]+[S] to save the information for the new
user.
Step 16: Repeat Steps 4 through 12 for any other users.
Step 17: Click the Close box to close the Add User window.
Administration icon List Users Add icon ([Insert]) Save icon ([Ctrl]+[S])
Existing users can be edited or deleted as necessary. See Editing Items and Deleting Items
in for more information.
Enabling a Locked Out User
If a user exceeds the allowed number of attempts to enter the correct password, the user
will be locked out of the Roadnet Transporation Suite. You can enable a user if the user
is locked out of the Roadnet Transportation Suite. The user must be unlocked in order to
be able to log in again.
Step 2: Click on the List menu, then select Users. The Users window opens.
Step 3: Double-click on the appropriate user(s). The window that allows you to edit
information opens.
Step 4: Uncheck Locked. The user will now be able to log into the Roadnet
Step 5: Click the Save icon, or press [Ctrl]+[S] to save the user.
Operations Guide
31
Working with Notification Recipients

Notification recipients are external programs that gather information about events that
occur in the Roadnet Transportation Suite. As events for this recipient occur, the Roadnet
Transportation Suite gathers them, and when the program polls the Roadnet
Transportation Suite, the information is transferred to the program. For instance, you may
have a software program called Up To Date that wants to know when drivers arrive and
depart stops on their wireless devices so that your organizations internal system can be
up to date; to have this information transferred you set up a notification recipient for Up
to Date and select Stop Arrive - Device and Stop Depart - Device from the Subscription
list. Notification recipients are intended to be used with the Roadnet Web Services.
Step 2: Click on the List menu and select Notification Recipients. The Notification
Recipients window opens, listing any notification recipients that exist.
Note: The built-in recipient, WMX, is a default notification recipient for MobileCast
Smartphone. It cannot be removed or changed.
Step 3: On the Notification Recipients window, click on the Add icon, or press [Insert].
The Add Notification Recipient window opens.
Step 4: Enter the Recipients ID and Description. You must enter an ID.
You can choose which events, or

subscriptions, the recipient receives
information about.
Step 5: If the recipient should only receive notifications about routes loaded onto a
wireless device, check Loaded Routes Only. If this option is not selected,
32

notifications will be sent for both routes that are loaded and routes that are not
loaded.
Step 6: If a specific wireless provider should receive notifications, check Selected
Wireless Provider Only and select the wireless provider from the list. If this
option is not checked, notifications will be sent to all wireless providers.
Step 7: In the Subsections list, check the events that the recipient should receive
notifications about. The options are explained below.
Route Startoccurs when the route is started.
Route Departureoccurs when the driver leaves the depot.
Route Arrivaloccurs when the driver returns to the depot after the stops are
delivered.
Route Completeoccurs when the route is finished.
Route Changeoccurs when a change has been made to the route.
GPSoccurs when a GPS ping is received from the wireless device.
Stop Sequenceoccurs when the order of stops on the route is changed.
Stop Arriveoccurs when the driver arrives at the stop.
Stop Departarrives when the driver leaves the stop.
Stop Canceloccurs when the driver cancels the stop. If a stop is canceled it
means the driver will not be returning to the stop.
Delivery Detailoccurs when the actual delivery/pickup quantities are entered.
Text Messagethe event was created when a message was sent by the driver to
the dispatcher, sent by the dispatcher to the driver, or sent by web services.
Route Exceptionsoccurs when one the tracked route exceptions is triggered.
Select the specific exceptions you want tracked from the list.
Routing Sessionoccurs when orders are uploaded from the Routing Editor to
your host system using the send orders feature.
Scheduleroccurs when a successful optimization occurs, you update the
delivery wave which causes orders to be taken off the route due to constraints, or
you cancel an order.
Remember, you must also select which method generates the events you want to
receive. The options are:
Devicethe event was created on a device, either by the driver or a GPS ping.
Transportation Suite Client Softwarethe event was created within the Roadnet
Transportation Suite, usually by a dispatcher.
External Hostthe event was created by an external program and transmitted to
the Roadnet Transportation Suite using the SOAP API.
Operations Guide
33
Step 8: Click the Save icon, or press [Ctrl]+[S] to save the notification recipient.
Step 9: Repeat Steps 3 through 7 to add more notification recipients.
Step 10: Click the Close box to close the Add Notification Recipient window when all
recipients have been added.
34

Working with Regions

Each area or organization for which you create routes is referred to as a region; you could
set up separate regions for each depot. Regions have resources available to them, such as
drivers and equipment. When setting up the regions you need to specify which privileges
each user or user group has in the region; you can grant users different privileges in
different regions.
Adding a Region
If you need to set up a new region in which you need to recreate maintenance items that
exist in a current region, such as employee types, equipment types, and service time types,
you can clone the region. This means that maintenance items that are common across the
business are automatically copied to the new region, saving you the step of manually
adding them to the new region.
Before you can start using the Roadnet Transportation Suite, you must add at least one
region.
Step 2: Click on the List menu and select Regions. The Regions window opens with all
existing regions displayed.
Step 3: On the Regions window, click on the Add icon, or press [Insert]. The Add
Region window opens.
and select Clone from the menu that pops up. The Add Region window opens with
some information already completed; change the information as necessary for the
new entry.
Operations Guide
35
Step 4: Enter the ID and Name for the region. The ID must be completed.
Each region must

have a unique ID.
Step 5: If you are using organization units to group your regions, click the Organization
Unit arrow. The Lookup - Organization Unit window opens. Double-click on the
organization unit, or click on the organization unit and then the Process icon, to
select it.
Step 6: Enter the phone and fax numbers for the region.
Step 7: In the Address section, enter the address information in the appropriate fields.
Step 8: In the Limits section, review the route and territory information.
RN Routes/Sessionenter the number of routes per session in the Assigned field,
up to the amount available, you want to assign to this region.
TP Territories/Sessionthe number is equal to the System Total and Available
fields. Territory Planner territories are the same for each region and cannot be
changed.
Assignedthe number of routes that are currently alloted for this region.
System Totalthe total number of routes allowed as specified in your Roadnet
Transportation Suite contract.
Availablethe number of routes that remain unassigned
36

Note: When you add a region, the RN Routes/Session Assigned limit defaults to zero.
You cannot route in the region until you assign a number to the field. If you enter
a number in the Assigned column that causes the sum of assigned routes to exceed
the System Total, you will be unable to save the region.
Step 9: If you are using MobileCast and tracking payroll for ADP, enter the Company
Code and Temp Dept for the region. See your ADP software for more
information.
Step 10: In the User Defined Fields section, if you have any information, enter the userdefined information in the appropriate fields.
Step 11: Click the Security tab to define the users and user groups, and their privileges
for the region.
Step 12: On the Security page, click [Add User] or [Add User Group] to open the
appropriate Lookup window. Click on the user(s)/user group(s) that will have
access to the region, then click on the Process icon. To select multiple users/user
groups, hold down the [Ctrl] key while clicking the users/user groups.
You can give individual

users, as well as user
groups, different
privileges within the
region.
To remove a user/user group, select the user/user group and click the [Remove]
button. Click [Yes] to confirm you want to remove the user/user group from the
region.
Step 13: For each user/user group, check the privileges that user/user group will have in
this region.
Step 14: If you are using RIC and MobileCast, click the RIC tab to define where
planned data will come from.
Operations Guide
37
Note: If a configuration key is applied with MobileCast as a purchased product, the Use
MobileCast planned data starting option will automatically be checked and the
date field populated with the date on which the configuration key is applied.
If MobileCast is installed, the Sales/Service History applet in RIC uses data from
MobileCast. If your organization did not purchase MobileCast, Roadnet data is
used. If MobileCast is purchased later, the RIC tab lets you define when planned
data starts coming from MobileCast. Prior to that date, Roadnet data is used.
Step 15: Check Use MobileCast planned data starting. Enter the date to begin pulling
data from MobileCast; typically this would be the date MobileCast is installed. If
this date is blank, and the Use MobileCast planned data starting option is
checked, all planned data will come from Dispatcher and there will be no planned
data before MobileCast was installed.
You can define when RIC

data will begin coming from
MobileCast.
When entering date information, you can type in the date, or you can click on the
arrow to display the calendar. If entering the dates manually, use the arrow keys
to move from the month to day to year field. If using the calendar, to change the
month use the arrows on the top of the calendar to scroll through the month or
click on the month and select from the menu that pops up. To change the year,
click on the year and use the arrows to scroll to the correct year. Click on a date to
select it.
Step 16: Click the Save icon, or press [Ctrl]+[S] to save the information.
Step 17: Repeat Steps 4 - 16 for each region you want to add.
38

Step 18: When all regions have been added, click the Close box to close the Add
Region window.
Administration icon List Regions Add icon ([Insert]) Save icon ([Ctrl]+[S])
Existing regions can be edited or deleted as necessary. See Editing Items and Deleting a
Region for more information.
If you have more than one region, you can choose one as the default region, or you can
switch the region you are viewing within a module.
Cloning a Region
Setting up a new region is a time-consuming task and for the most part, the information
and data records that you enter for a new region are identical to the original region. By
cloning a region, you will save a substantial amount of time and effort if you do not have
to enter maintenance items that are common across the business, such as equipment types,
and location types. Even though settings in the various Options notebooks are copied to
the new region, some corresponding maintenance items may not be copied. For instance,
in the Routing Pass Options notebook the resources assigned to a depot are copied to the
new region, but the new depot may not exist in the new region. So before using the new
region, you should review all of the option settings and change them as necessary.
Important: The maintenance items are independent, so changing an item in the original
region will not change it in the new region. Because of this, you should spend a
good deal of time setting up and verifying your template region before cloning
new regions.
Step 2: Click on the List menu and select Regions. The Regions window opens with
existing regions displayed.
Step 3: On the Regions window, right-click on the region you want to clone and select
Clone from the menu that pops up. The Add Region window opens with some
region.
Step 4: Click the Security tab to define the users and user groups, and their privileges
for the new region.
Step 5: Click the [Add User] or [Add User Group] button to open the appropriate
Lookup window. Click on the user(s)/user group(s) that will have access to the
Operations Guide
39
region, then click on the Process icon. To select the multiple users/user groups,
hold down the [Ctrl] key while clicking the user/user group.
You can select the users/user groups for

the new region as well as assign their
privileges.
Step 6: To remove a user/user group, select the user/user group and click the [Remove]
button. Click [Yes] to confirm you want to remove the user/user group from the
region.
Step 7: For each user/user group, check the privileges that user/user group will have in
the region.
Step 9: When you have finished cloning the new region, click the Close box to close
the Add Region window.
Important: Once you have cloned the new region, you will need to access the new region
and set up other administration items as well as locations, drivers, and other region
specific maintenance items.
Note: Once the clone process completes successfully, you will be prompted to enter the
configuration key. You will need to apply the configuration key in order to work
with the new region.
Deleting a Region
If you delete this region, all data associated with the region including routes, maintenance
items and historical routing information, will no longer be available and cannot be
restored. You should do the following prior to the deletion:
40

Back up your database.
Review your databases transactions log. If the log is too large, delete any
unnecessary entries from the log file.
Delete regions only during non-operational periods.
Note: The delete region process may take a long time to complete.
Step 1: Click on the Administration icon to open the Administration module The
Step 2: Click on the List menu and select Regions, then Regions. The Regions window
opens with all existing regions displayed.
Step 3: On the Regions window, click on the Region that you want to delete, then click
the Delete icon. The Confirm Deleting Region window opens.
In order to delete a region, you must confirm the deletion by entering

a verification code.
Step 4: Enter the Region ID in the field. This can be found on the Regions window.
Step 5: Enter the Verification Code shown on the Confirm Deleting Region window.
Step 6: Click [OK] when you done.
Selecting Rush Hour and Time of Day Restriction Models to Use with the Regions
If your organization serves a large geographic region, such as the United States, and you
have a lot of rush hour and time of day restriction models, you may find that it takes a
long time for the SuperMatrix to build. One way to reduce the time needed to build the
SuperMatrix is to limit the rush hour and time of day restriction models being built to
only those models used with that region.
Step 2: Click on the List menu, then Regions, then Rush Hour and Time of Day
Restrction Models. The Rush Hour Models to Use window opens.
Operations Guide
41
Step 3: The Rush Hour and Time of Day Restriction Models to Use window contains
three lists. The Select Region area lists all your regions; the contents of the
remaining two lists reflect the region you select here. The Models to Use with
Region area contains all the rush hour and time of day restriction models
assigned to the selected region, while the Select Models to Use with Region area
lists all rush hour and time of day restriction models available to assign to the
selected region.
In this example, the CLNREGTST region uses the Dallas and Fort worth models.
To select the rush hour and time of day restriction models to use with a
region, click on the region in the Select Region list. Then, select the rush hour and
time of day restriction model(s) you want to use with the region in the Select
Models to Use with Region and click on the [<] button; the selected rush hour and
time of day restriction model(s) move to the Models to Use with Region list.
To move all the rush hour and time of day restriction models from the Select
Models to Use with Region list to the Models to Use with Region list, click the
[<<] button.
To remove a rush hour or time of day restriction model from a region, select
the model(s) in the Models to Use with Region list and click on the [>] button; the
selected rush hour model(s) move to the Select Models to Use with Region list.
To move all the rush hourand time of day restriction models from the Models
to Use with Region list to the Select Models to Use with Region list, click the
[<<] button.
Step 4: To have new rush hour and time of day restrictionmodels automatically set
to use with all regions, check New Models Apply to All Regions.
42

Step 5: To have all rush hour and time of day restrictionmodels automatically set to
use any new regions, check New Regions Use All Models.
Note: The rush hour and time of day restriction model will automatically be linked to
the region selected in the Maintenance module when the rush hour or time of day
restriction model is created.
Step 6: Click the Save icon, or press [Ctrl]+[S] to save the rush hour and time of day
restriction model region links.
Administration icon List Regions Rush Hour and Time of Day Restriction Models
Save icon ([Ctrl]+[S])
Selecting a Default Region
If you have more than one region, you may find that there is one region you use more
frequently than others. You can specify this as your default region; whenever you enter a
new module, such as the Routing Editor, you will automatically see the information for
the default region. You can change the region you are viewing in each module, as
necessary.
Note: The region selected as the default is the default for the user currently logged into
the module.
You can select a default region from any module except the Admin module.
To select a default region, right-click on the region name at the bottom right of the module
window and select Make Default.
Switching Regions
Sometimes it may be necessary to switch from one region to another; the Roadnet
Transportation Suite allows you to easily switch between regions in most areas of the
program. Because you may work with one regions information more frequently than
others, you can make one region the default.
Note: Only regions you have access to in that module will appear in the list.
Step 1: Open the appropriate module.
Step 2: On the bottom right side of the windows status bar is a field with the name of
the current region. Click the arrow and a list of regions appears.
Step 3: Click on the region you want to work with. The list of regions closes and a
confirmation window appears.
Step 4: Click [Yes] to change to the new regions data, or [No] to remain working with
the current region.
Operations Guide
43
Working with Organization Units

Organization units are a set of regions that define your companys organizational
structure. Organization units let you group your regions so that you can gather executivelevel details about your companys routing. Similar to regions, organization units are
defined at the Roadnet Transportation Suite level. You can also give the organization unit
a different name, or alias. For instance, if your company combines regions into districts,
you can call the organization unit districts and that would appear in the Roadnet
Transportation Suite. The organization unit feature gives you the flexibility to assign a list
of your companys existing regions to a specific organization unit.
Adding the Organization Units
Before you can begin assigning specific regions to an organization unit, you must first add
the organization units.
Step 2: Click on the List menu and select organization units. The Organization Units
window opens with all existing organization units displayed.
Note: This menu is an alias so it may read something other than Organization Units
depending on your companys structure, such as districts.
Step 3: On the Organization Units window, click on the Add icon or press [Insert]. The
Add Organization Unit window opens.
The ID field must be

completed.
and select Clone from the menu that pops up. The Add Organization Unit window
opens with some information already completed; change the information as
necessary for the new entry.
Step 4: Enter the ID and Name for the organization unit. The ID must be completed.
Step 6: Repeat Steps 1 - 5 for each organization unit you want to add.
Step 7: When all organization units have been added, click the Close box to close the
Add Organization Unit window.
44

Existing organization units can be edited or deleted as necessary. See Editing Items and
Deleting Items for more information.
Administration icon List Organization Unit Add icon ([Insert]) Save icon
([Ctrl]+[S])
Operations Guide
45
Setting the Alias
Setting the Alias

The Administration module allows you to track up to three user-defined fields containing
information for each region. The headers for these fields, or the aliases, are common to
all regions, but each region can have unique information in the fields. Likewise, you can
also give the organization unit a different name, or alias. For instance, if your company
combines regions into districts, you can call the organization unit districts and that would
appear in the Roadnet Transportation Suite.
Step 1: Click the Administration icon to open the Administration module. The
Step 2: Click on the List menu and select Aliases. The Aliases window opens.
Step 3: In the Region Aliases area, enter the desired user-defined field names in the
appropriate fields. The headers will appear on the Regions window.
You can enter a unique name for a

user-defined field.
Step 4: If you are using organization units, and want to create an alias, enter the desired
user-defined name in the Organization Unit field.
Administration icon List Aliases OK
46

Maintaining the Roadnet Transportation Suite
Maintaining the Roadnet Transportation Suite

Note: If you have not been granted permission to perform maintenance in the
Administration module, you will not be able to open this module.
The Maintenance module comprises all of the information about your business
locations (depots, locations or delivery customers, etc.), employees, equipment (tractors,
trailers, straight trucks, etc.) and how that information will be used when planning,
creating, loading, and ultimately tracking your routes. You will use the Maintenance
module initially to set up that information, and then regularly to keep the information in
your system current. For example, if you acquire a new type of delivery equipment and
are using it to deliver a product, you must enter information about the new piece of
equipment so that you have accurate data in the computer system.
The Maintenance module in the Roadnet Transportation Suite allows you to set up and
maintain the data in the system. Using the Maintenance module you can:
Enter and maintain information about the locations, deliveries, drivers, equipment,
and other areas of your operation.
Adjust travel time according to equipment type and size.
Set up the options that will define how the Roadnet Transportation Suite runs.
Record the actual time spent making deliveries to help Roadnet produce more
accurate service times and routing solutions.
Edit the drivers duty period history to record the amount of time each driver has
worked and prevent the drivers from violating safety and labor regulations.
Update locations service times with actual information so you can create more
accurate routes.
Create rush hour models that reflect traffic patterns that change throughout the day.
Run database maintenance to keep the Roadnet Transportation Suite running

smoothly.
Transport data to Roadnet Technologies for troubleshooting assistance.
Set up the schedule to determine the delivery options presented to the locations when
orders are placed.
Important: The Roadnet Transportation Suite is only as accurate as the information you
enter into it. Be sure to promptly enter new data and changes to existing data.
Note: You can also access and update many maintenance resource items in the Routing
Editor and the Planning Editor.
Operations Guide
47
Working with Maintenance Items

All items in the Roadnet Transportation Suite use maintenance windows to add, edit, and
delete items. This means that the same basic process can be used to maintain all items.
Additionally, you can set and change default values for many maintenance items
according to your regions preferences.
Click on the Maintenance icon to open the Maintenance module. You can then choose to
add or update information within the system.
Adding Items
Each maintenance item in the Roadnet Transportation Suite, such as equipment,

employees, or locations, will contain specific step-by-step instructions on adding
information since the required data is different for each item. For example, when you look
up instructions for adding equipment, you will see the main Equipment section, which
describes the concepts associated with equipment, followed by the step-by-step
instructions for adding equipment.
If you are adding an item that is similar to an existing item, you can clone the existing
item, reducing the amount of text you need to enter.
Step 1: Click the List menu and select the menu option for the item you want to add.
Step 2: To add an item, click on the Add icon or press [Insert]. The Add window opens.
Step 3: Enter all the necessary information.
Step 4: When the window is complete, click the Save icon or press [Ctrl]+[S] to save
the new item.
Step 5: Click the Close box when all items have been added.
Cloning Items
You can clone existing maintenance items. When you clone an item, most of the
necessary information is completed when the Add window opens, reducing the amount of
text you need to enter. You can change any of the existing information as needed.
To add an entry that is similar to an existing one, right-click on the existing entry and
select Clone from the menu that pops up. The Add window opens with some information
already completed; change the information as necessary for the new entry.
Editing Items
Once items have been added in the Maintenance module, you can change the items as
needed.
Step 1: In the item window (for example Equipment), double-click on the entry to be
modified. The Edit window opens.
48

OR
In the item window, select the entries to be edited. Right-click on a selected type
and choose Edit from the menu that pops up. The Edit window opens.
To select a single entry, click on the entry.
To select multiple entries, click on the first entry. Then press and hold the [Ctrl]
button on the keyboard and click the remaining entries to be edited.
To select multiple entries in a row, click on the first entry. Then press and hold
the [Shift] key on the keyboard and click the last entry to be edited. All entries
between those two entries will be selected.
Step 2: Change the information in the window as necessary. Click on the Save icon, or
press [Ctrl]+[S] to save the changes.
If editing multiple entries, use the arrows at the top of the window to scroll through
the selected entries, and save the changes for each one.
Note: The key field(s) (typically the ID or name field) cannot be changed; it will be
grayed out in the window and you will not be able to select the field. To edit the key
field for an entry, delete the entry and add it again, or clone the entry then delete the
original.
Deleting Items
Existing maintenance items can be deleted.

Some entries should not be deleted until all related items using that entry are deleted or
modified. For example, an equipment type should not be deleted until all equipment using
that type is deleted.
Step 1: In the item window (for example Equipment Types), click on the entry(s) to be
deleted.
To select a single entry, click on the entry.
To select multiple entries, click on the first entry. Then press and hold the [Ctrl]
button on the keyboard and click the remaining entries to be deleted.
To select multiple entries in a row, click on the first entry. Then press and hold
the [Shift] key on the keyboard and click the last entry to be deleted. All entries
between those two entries will be selected.
Step 2: Click on the Delete icon, or press [Delete]. Click the [OK] button to confirm the
deletion.
OR
Operations Guide
49
Right-click on a selected entry and select Delete from the menu that pops up. Click
on the [OK] button to confirm the deletion.
Note: If you delete several items, you may want to compress the database to completely
remove the items and reduce its size. To compress the database, select Compact
Database from the Tools menu.
Selecting Defaults
You can easily select defaults for many maintenance items, which will be used throughout
the Roadnet Transportation Suite unless an alternative is specified. For example, the
driver selected as the default will be the driver used to calculate the routes cost when
routes are created in the Routing Editor unless another driver is specified for that route.
Step 1: In the item window (for example Equipment Types), right-click on the entry you
want to be the default.
Step 2: Select Make Default from the menu that pops up.
To select default values, right-click on the entry and select Make Default.
Notes: The current default entry is indicated by a check next to Make Default.
Many defaults can also be selected in the Options notebook. See Setting the
Options for more information.
50

Setting the Options
Setting the Options

Note: If you have not been granted permission to change maintenance options in the
Administration module, you will not be able to open this notebook.
The Roadnet Transportation Suite allows you to set up default options related to many
items, such as routing, sessions, dispatching, locations, and wireless devices. You can set
up what level of detail the system should use in displaying service time, the aliases for
your quantity information, the size aliases used to measure capacity, service time, cost and
other factors. If you are using MobileCast, you can set up additional defaults, such as for
reason codes and the onboard computer.
The options you choose in the Options notebook will be used for the routing sessions,
planning sessions, routes, location, and dispatching unless you specify an alternative.
Some of the items that you set in the Options notebook can also be set as the default by
right-clicking on it in the list window and selecting Make Default from the menu that pops
up. See Selecting Defaults for more information.
Note: These options cannot be set up until other Maintenance items have been added.
Step 1: Click on the Maintenance icon to open the Maintenance module. The
Maintenance window opens.
Step 2: Click on the Tools menu and select Options. The Options notebook opens.
Tools Options
For more information see the General Defaults Page, Route History Page, Routing
General Defaults Page, Planning General Page, Location Defaults Page, Alias Defaults
Page, Unit Reference Defaults Page, Duty Period Monitor Page, Dispatch - General Page,
Dispatch - Detail Level, Dispatch - Device Diagnostics, Dispatch - Load Page, Dispatch
- Accounting Page, Dispatch - Continuous Optimization, and the Historical Travel Speeds
Page.
Setting the General Defaults
Used with: Roadnet, Territory Planner, MobileCast
The General page of the Options notebook lets you choose the default country for your
locations and the time zones that will be available throughout the Roadnet Transportation
Suite. There is also an option that allows you to track orders that have been picked up and
then delivered on the same route and options to adjust how a routes time will be
calculated when there are consecutive stops at the same physical location. If you want to
restrict vehicles from being routed on roads with certain height and weight limits, you
must enter height and weight thresholds that determine which roads will be restricted on
this page. If you want to reduce the amount your driver needs to cross traffic to enter and
Operations Guide
51
Setting the Options
exit customer locations, you can enter the information in the Same Side of Street Routing
area. And, you can specify how the delivery cost for a location will be calculated.
The General page of the Options notebook lets you select some options that will be used
throughout the Roadnet Transportation Suite.
Step 3: To select the default country, click the arrow to open a list of options and click
on a country to select it. The country you select will be pre-entered on the
Attributes page of the Locations Notebook when you add a new location.
Step 4: To be able to select from all time zones, not just North American time zones,
check Display International Time Zones.
Step 5: To have the Roadnet Transportation Suite consider two orders with the
same order number but different order types (one a pickup and one a
delivery) as a pair when creating and evaluating routes, check Enable Order
Sourcing.
Step 6: In the Consecutive Stops With Same Latitude-Longitude box, check the options
you want to use for calculating fixed service time and fixed travel time when
delivering to consecutive stops with the same latitude and longitude.
To disregard the fixed service time for any daily stop that is at the same
latitude and longitude as the stop before it, check Apply Fixed Service Time To
First Stop Only. When this option is selected, if there is a group of consecutive
52

Setting the Options
stops on a route with the same latitude and longitude, fixed service time will only
be applied for the first stop in that group of stops. Using this option can result in
more accurate route times when there are multiple stops at the same physical
location (for example, multiple stops in the same building).
To disregard the fixed travel time for any daily stop that is at the same
latitude and longitude as the stop before it, check Apply Fixed Travel Time To
First Stop Only. When this option is selected, if there is a group of consecutive
stops on a route with the same latitude and longitude, fixed travel time will only
be applied for the first stop in that group of stops. Using this option can result in
more accurate route times when there are multiple stops at the same physical
location (for example, multiple stops in the same building).
Note: This setting does not affect breaks, waits, and layovers; these stop types always
have a fixed travel time of 0.
Step 7: In the Road Restrictions area, enter a Height Restriction and/or Weight
Restriction if you want to prevent specified equipment types from being routed
on roads that have certain height or weight limits. You can select whether each
equipment type is able to use roads that are restricted due to height or weight
limits when working with equipment types.
To restrict roads based on their weight limit, enter a weight in the Weight
Restriction field. If a street segments weight limit is less than the Weight
Restriction, the street segment will be restricted. For example, if a street segments
weight limit is 6,000 lbs and the Weight Restriction is 9,000 lbs, the street segment
will be restricted. If the Weight Restriction is set to zero, weight limits on roads
will be ignored.
To restrict roads based on their height limit, enter a height in the Height
Restriction field. If a street segments height limit is less than the Height
Restriction, the street segment will be restricted. For example, if a street segments
height limit is 14 ft and the Height Restriction is 18 ft, the street segment will be
restricted. If the Height Restriction is set to zero, height limits on roads will be
ignored.
Step 8: In the Same Side Of Street Routing area, enter the penalty to be associated with
turning into or out of the delivery locations. This penalty will associate an
additional amount of time with crossing traffic to enter and exit the customer
locations, making it more likely the driver will deliver one side of the street, then
turn once and deliver the other side of the street. This kind of routing can be
helpful in busy commercial areas. Normally, if you are in the United States you
would enter a left turn penalty, while Europeans would enter a right turn penalty.
Enter the penalty in the format H:MM:SS; studies have indicated that a 1 minute
penalty is appropriate in many suburban settings.
Note: If you choose to use same side of street routing and you used versions of the
Roadnet Transportation Suite prior to 3.30, you will need to re-geocode the
customers in areas that may benefit from not crossing traffic.
Operations Guide
53
Setting the Options
Step 9: To select the Location Delivery Cost Method, click the arrow to select the
appropriate option. This determines how the delivery cost for a location is
calculated.
Nonedelivery costs are not calculated. If the Location Delivery Cost report is
run, it will be blank.
Sharedshows the direct effect of the stop on the routes cost.
Percent of Totalmore accurately reflects each stops effect on the total route
cost because each stops shared cost is adjusted to reflect the relationship between
the routes total shared cost and the actual total cost.
Step 10: Click the [OK] button to save the information, or continue to another tab.
Page.
Setting the Routing - General Defaults
Used with: Roadnet, FleetLoader, Territory Planner
The Routing - General page of the Options notebook allows you to set the defaults used
when creating routing sessions and routes for the Routing Editor. You can select the
Time/Distance Calculation method you want to use, whether to combine orders, whether
to use barriers (if you are using the XY method), whether to restrict your trucks to travel
on select roads, use user-created rush hour models, or the historical travel speed for your
routing sessions. The options you select will be the defaults for any new routing session
and route created; however, these options can be changed in the Routing Editor.
54

Setting the Options
In addition to setting the defaults for the routing sessions, you can set the defaults that will
be used when routes are created. You can set the default start time, any pre- and post-route
times, as well as select the default driver, travel model, depot, and equipment type.
The Routing Sessions tab contains default items used for sessions in the Routing
Editor.
Step 1: In the Default Session Properties area, click the appropriate circles/boxes to
select the Time/Distance Calculation options and other session options.
XYa routing method that uses a straight line to measure the distance between
two points; it relies on the distance and travel time models to account for curves
and turns in the road as well as varying speeds. Compared with RouteNet, the XY
method is quicker to use but less accurate.
Use Barrierscan be selected only when the XY method is being used. This
option accounts for actual barriers between two points, such as a body of water, a
mountain, etc. Barriers must be created in the Barrier mode on the map.
RouteNeta calculation method that uses maps to replicate the actual road
conditions, accounting for everything from stop signs and traffic lights to speed
limits and road changes. Compared with XY, RouteNet takes longer to process but
is more accurate.
Notes: Using RouteNet may cause a significant delay when entering the Routing or
Planning Editor as the times and distances are calculated. The length of this delay
is based on several factors, including:
the number of locations with orders
Operations Guide
55
Setting the Options
the number of depots
the number of roads in the geographic area
the processing power of the computer
If you want to avoid this delay, you can use the SuperMatrix.
If there are more than 4000 unique locations that have orders in a routing session
or if the memory required for the build exceeds 2 GB, times and distances will be
calculated using XY.
SuperMatrixanother calculation method that uses the street network to
replicate actual road conditions, accounting for everything from stop signs and
traffic lights to speed limits and road changes. You can schedule the SuperMatrix
to be built overnight so that you do not have to wait for the travel times and
distances to be calculated when entering the editors. If you are using the
SuperMatrix, you need to specify how you want the Routing Editor to handle
locations that have been added since the SuperMatrix was last built. In the
Realtime Updating area, select whether you want to use XY or RouteNet to
calculate the distances to these locations.
Note: In order to use the SuperMatrix, you must have write permission to the map data
directory.
To improve loading time of a routing session when using the SuperMatrix, check
Load SMX files for session valid delivery dates only. The information that is
loaded is limited to just valid delivery days.
Apply Commercial Vehicle Restrictionsprevents specified equipment types
from being routed on street segments that are considered commercially restricted
roads. If it is impossible to reach a stop without traveling on a street segment that
is restricted as well as the equipment type being restricted, the stop will be routed
using the XY method.
Apply Road Restrictionsprevents specified equipment types from being
routed on street segments with a height limit that is less than the Height Restriction
or a weight limit that is less than the Weight Restriction. To use this feature, a
Height Restriction and Weight Restriction must be entered on the General page of
the Maintenance Options notebook. If you want road restrictions to be enabled by
default for routing sessions, check Apply Road Restrictions. When the road
restrictions feature is enabled, equipment types that are prohibited from traveling
on height and weight restricted roads will only be routed on street segments that
are not restricted. If it is impossible to reach a stop without traveling on a street
segment that is restricted, the stop will be routed using the XY method and no
driver directions will be generated. If you need to enable or disable the road
56

Setting the Options
restrictions feature for an individual routing session, you can do so by opening the
list of routing sessions, right-clicking a routing session, and selecting Properties.
Note: The commercial road restrictions and the road restrictions feature can only be used
with RouteNet or Supermatrix; it cannot be used with the XY method.
No Rush Hourdoes not use rush hour models or historical travel speeds when
creating routes in the routing session.
Use Rush Hour Modelsuses user-created rush hour models when creating
routes in the routing session. Select the rush hour model that the session should
use from the Rush Hour Model field.
Rush Hour Modelallows you to choose a rush hour model to designate
times during which rush hour activity occurs. To choose a rush hour model,
click on the Rush Hour Model arrow; the Lookup - Rush Hour Model window
opens. Double-click on a model to select it, or click on the model and then on
the Process icon. If you are using RouteNet or the SuperMatrix and want to
use advanced rush hour features, such as paths, check Advanced Rush Hour
(consider alternate streets).
Advanced Rush Hour (consider alternate streets)uses rush hour paths
and areas to determine the actual streets the routes will take. If using advanced
rush hour features, you can still use simple areas as well as advanced areas and
paths. If you want to change the road direction during a rush hour period, you
must check Advanced Rush Hour. Using advanced rush hour may require
additional time when entering the Routing Editor.
Note: Using advanced rush hour may cause a significant delay when entering the
Routing or Planning Editor as the times and distances are calculated. This is in
addition to the delay cause by using RouteNet. The length of this delay is based
on several factors, including:
the number of rush hour time periods in the model
whether equipment restrictions were created for the time periods
the number of rush hour areas and paths in the model
Use Historical Travel Speedsuses historical travel speeds to determine the

actual streets the routes will take. This option is only available if you purchased
historical travel speeds.
Time of Day Restriction Modelallows you to choose a time of day restriction
model to designate periods in/during the day in which restricted equipment types
cannot travel in restricted areas or paths. This prevents some vehicles, such as
large trucks, from being routed on restricted roads while allowing other vehicles,
such as small trucks or vans, to use those roads. To choose a time of day restriction
model, click on the Time of Day Restriction Model arrow; the Time of Day
Operations Guide
57
Setting the Options
Restriction Models window opens. Double-click on a model to select it, or click

on the model and then on the Process icon.
Combine Orderscombines multiple orders for a single location during a
session so they will be placed on the same route. The orders will only be combined
if they meet the criteria specified on the Combine Orders Window, which is
accessed from the Routing - General page of the Maintenance Options notebook.
If Enable Mid-Route Sourcing is checked, Combine Orders will not be available.
Enable Mid-Route Sourcingadds mid-route sourcing depots to a route to
allow the driver to pick up or drop off product in order to be able to service the
next stop. It is recommended that you do not use Combine Orders in conjunction
with Mid-Route Sourcing. If Combine Orders is checked, Enable Mid-Route
Sourcing will not be available.
Update Duty Period Historyupdates drivers planned work time history based
on the routes you create and edit in Roadnet. When this option is selected, drivers'
work time history will be updated based on both active and built routes every time
you save the session. The drivers' work time history, also known as the Duty
Period History, is used by the Roadnet Transportation Suite when determining if
duty period rules have been violated. Duty period rules regulate the length of time
that drivers can work and are used to help your organization comply with safety
and labor laws. This option is only available when you have duty period rules
enabled on the Duty Period Monitor page of the Maintenance Options notebook.
You may not want to use this option when you are experimenting with different
route possibilities.
Note: Once actual duty period data has been collected for a route through MobileCast or
from an onboard computer, the duty period information for that route will not be
updated if changes are made to the route in Roadnet. Similarly, if duty period
information was manually entered for a route in the Duty Period History window,
the duty period information for that route will not be updated if changes are made
to the route in Roadnet.
Save Route Historyincludes the sessions built routes when Route History is
run to archive the data in the Route History database. If the routes were completed
in MobileCast, that information will be stored. This option is only available if
Enable Roadnet as a data source is selected on the Route History page.
Step 2: In the Defaults area, select the default driver, travel time model, equipment
type, and depot; the importance of each depot is explained below. To select a
default, click on the appropriate arrow to open a Lookup window. Double-click
on an item, or click on the item and then on the Process icon, to select it.
Driverrefers to the driver whose costs will be used to calculate the route costs
if no other driver is assigned to the route.
Equipment Typerefers to the kind of equipment automatically chosen for a
route in the Editor if another equipment type is not assigned. Equipment types
58

Setting the Options
determine the capacity of the equipment assigned to the route and are used to
calculate the costs when routes are created.
Depotrefers to the depot automatically chosen for a route in the Routing Editor
if another depot is not assigned.
Travel Time Modelrefers to the method of calculating travel time for routes in
the Editor. The default travel time model will be used unless another travel time
model is selected in the Routing Editor, or unless you select RouteNet as your
travel time calculator.
Step 3: In the Order Options area, you can select how you want your orders to be
calculated and combined.
If you will be using line items to determine order sizes in the Orders
notebook, check Line Items Calculate Order Sizes. If this box is not checked, the
overall order quantity will be used.
If you will be combining orders from a single location into a single stop, click
the [Combine Orders] button to open the Combine Orders Options window, where
you can define the guidelines you want to use when determining if the orders
should be combined or not. In order for two orders to be considered for combining,
the orders must be for the same location ID and either have the same preferred
route ID or at least one must not have a preferred route ID. The options are
explained below.
Selectorsif your orders have selectors, you can choose to disregard selectors
when combining orders (Combine All), or to not combine orders if the selectors
dont match (Separate All). Or, you can create groups of selectors and specify that
orders with these selectors can be combined (Combine By Group). Enter the
selectors for each group in the Selector Groups fields.
Combine Pickups and Deliveriescheck to allow pickups and deliveries to be
combined. If this option is not selected, pickup and delivery orders will not be
combined.
Combine Orders with Non-matching Time Window Overridescheck to
allow orders whose time windows do not match to be combined. If this option is
selected, click the Time Window Override Selection Preference arrow and choose
the time window you want all the combined orders to use.
Consider Skill Setscheck to allow orders with order activities that are in the
same skill set to be combined. If this option is not selected, and the orders include
activities that are not in the same skill set, the orders will not be combined.
Step 4: In the Default Route Properties area, enter the defaults that will be used when
routes are created, such as the times and starting quantity.
Operations Guide
59
Setting the Options
Start Timerefers to the time the route departs from the depot.
Reg. Timerefers to the maximum amount of time the driver can work before
being paid overtime.
Pre-Route Timerefers to the amount of time needed between when the driver
arrives at the origin and leaving the origin. This time may be used for meetings or
checking the load. The driver is paid for pre-route time, so it is included when the
route time is calculated.
Note: The pre-route time entered here is calculated for every route in the territory or the
week. For example, if the territory contains three stops and the pre-route time is
20 minutes, 60 minutes will be added to the total route time for the territory.
Pref. Timerefers to the preferred amount of runtime for a route. Preferred
runtimes are used in dynamic routing, and in the Editor when adding stops to
routes. A route may exceed the preferred runtime.
Post-Route Timerefers to the amount of time needed between when the driver
arrives at the routes destination and clocks out for the day. This time may be used
to complete paperwork or unload the truck. The driver is paid for post-route time,
so it is included when the route time is calculated.
Max. Timerefers to the maximum amount of runtime for a route. Maximum
runtimes are used in dynamic routing, and in the Editor when adding stops to
routes. Dynamic routing will not exceed the maximum runtime when creating
routes.
Reload Timethe amount of time needed to reload the truck if it is being sent out
for a second route. To set, select either Specify Time or Use Reload Depot Service
Time. If you selected Specify Time, enter the exact time using the format
HH:MM.
Starting Quantityrefers to how much is loaded on the piece of equipment at
the beginning of the route.
For most industries: if the truck leaves the depot with just enough product
for that route, choose As Needed; this is the most common choice.
For the fuel industry: if a fuel truck is typically refilled at the last stop, then
enter Full. If a fuel truck is typically refilled at the first stop, then enter
Empty. Finally, if a fuel truck starts the route with just enough fuel for that
route, then enter As Needed.
For the waste industry: If a bulk carrier truck always leaves the depot
without an empty container enter Empty. If a bulk carrier truck leaves the
depot with an empty container and if the first customer stop requires
delivery of an empty container enter As Needed.
Note: Full is not available as a Starting Quantity when using Mid-Route Sourcing.
Step 5: Check Pre-build travel network to make the map draw faster.
60

Setting the Options
Step 6: Check Load SMX files for session valid delivery days only to improve loading
time of a routing session using the SuperMatrix. The information loaded is
limited to valid delivery days.
Step 7: Check the appropriate days for your organizations business week. The business
week refers to the days that your business routes are for. This information is used
when determining which day to create a session for.
Page.
Setting the Planning Session Defaults
The Planning - General page of the Options notebook lets you set the defaults that will be
used when creating planning sessions for the Planning Editor. For a new planning session
you can select the method you want to use to calculate travel times and distances, as well
as the amount of time the planning session covers. These items can be changed for an
individual planning session when you are adding the session.
Operations Guide
61
Setting the Options
To open the Options notebook, select Options from the Tools menu in the Maintenance
module. Click on the Planning - General tab.
The Planning General tab contains default items used for sessions in the Planning Editor.
Step 1: Click in the appropriate circles/boxes to select the Time/Distance Calculation

options.
limits and road changes. Compared with XY, RouteNet takes a little longer to
process but is more accurate.
Include Reload Depotscheck to include all of the regions depots for every
territory when calculating RouteNet travel times and distances. If this option
is not checked, only the depot within the territory will be included when times
62

Setting the Options
and distances are calculated for that territory. If you are using reload depots,
you should check this option.
If there are more than 4000 unique location extensions in a planning session or if
the memory required for the build exceeds 2 GB, times and distances will be
SuperMatrix, you need to specify how you want to the Planning Editor handle
directory.
the Maintenance Options notebook. If you want road restrictions to be enabled by
default for planning sessions, check Apply Road Restrictions. When the road
restrictions feature is enabled, equipment types that are prohibited from traveling
on height and weight restricted roads will only be routed on street segments that
are not restricted. If it is impossible to reach a stop without traveling on a street
segment that is restricted, the stop will be routed using the XY method. If you need
to enable or disable the road restrictions feature for an individual planning session,
Operations Guide
63
Setting the Options
you can do so by opening the list of planning sessions, right-clicking a planning

session, and selecting Properties.
with RouteNet or Supermatrix; it cannot be used with the XY method.
creating routes in the planning session.
Use Rush Hour Modeluses user-created rush hour models when creating
routes in the planning session. Select the rush hour model that the session should
(consider alternative streets).
Advanced Rush Hour (consider alternative streets)uses rush hour paths
must check Advanced Rush Hour (consider alternative streets). Using
advanced rush hour may require additional time when entering the Planning
Editor.
Use Historical Travel Speedsuses historical traffic data when creating routes
in the Planning Editor. This option is only available if you purchased historical
travel speeds.
64

Setting the Options

Step 2: Enter a number between 1 and 24 to indicate the number of Cycle Weeks for the
planning session. When determining the number of cycle weeks, make sure the
cycle is long enough that every location extension is delivered at least once.
Dispatch - SmartPhone, Dispatch - Detail Level, Dispatch - Device Diagnostics, Dispatch
- Load Page, Dispatch - Java Phone Page, Dispatch - Accounting Page, Dispatch Continuous Optimization, and the Historical Travel Speeds Page.
Setting the Location Defaults
The Location page of the Options notebook allows you to select service time type, zone,
state, time window type, time window factor, and bulk threshold defaults for new
locations. These defaults are automatically entered based on the information in the
Options notebook; however, they can be changed when adding a new location; for more
information, see Location Notebook.
Step 1: Click on the arrows next to the items described below to choose the default
information.
Service Time Typeused to determine the service times for a new location
unless you enter a service time override.
Time Window Typeused to determine the time windows for a new location
unless you enter a time window override.
Time Window Factorused to determine the importance of delivering to a
location within the time window(s) stated.
Zonepre-fills the zone for a new location. You can change the zone when
adding a location.
Account Typeused to establish the account type for the location. You can
change the account type when you add a new location.
Statepre-fills the state for a new location. You can change the state when
adding a location.
Location Typepre-fills the type for a new location. You can change the type
when adding a location.
Operations Guide
65
Setting the Options
Time Zonethe time zone most locations use. For instance, if a locations open
time is 8:00 and the time zone is Eastern Time , the locations open time is 8AM
Eastern Time.
You can choose the service time type and time window type that will be assigned
to a new location.
Step 2: In the Delivery Radius field, enter the distance surrounding a location that the
driver must travel into for MobileCast to automatically consider that the driver
has arrived at the stop. The drivers equipment must not move within this circle
for the amount of time specified in the RTS.Telematics.Adapter.exe.config file or
either of the minimum stop time fields on the Dispatch - Java Phone page for the
stop to be auto-arrived in MobileCast. When the equipment leaves this area,
MobileCast considers that the driver has departed the stop. Enter the distance in
miles. The radius you enter here is the default for locations; you can change it for
individual locations as needed.
Note: The Delivery Radius is used with the Roadnet Telematics Adapter, On Track, and
auto-arrive/depart.
Step 3: In the Bulk Threshold section, enter the amounts for each of your order quantity
measurements to qualify as a bulk order (Size 1, Size 2, and Size 3). When you
add a new location, you can change these numbers.
Step 4: To add or edit locations with the same ID but different types (ex. ID 12345,
types frozen, dry, produce) simultaneously, check Synchronize same IDs in the
When Performing Maintenance section. Click the [Fields to Sync] button to
choose the fields that will be synchronized. In the Pre-Selected box, [Ctrl]+click
66

Setting the Options
the types that will be pre-selected when adding a location; you can change the
actual types when adding the location.
Setting the Default Aliases
The Alias page of the Options notebook allows you to set up size and category aliases and
user fields for locations. This is the only place you can establish or change these defaults
in the Roadnet Transportation Suite.
Step 1: Enter the names for each of your units (Size 1, Size 2, and Size 3) and for each
category (Category 1, Category 2, and Category 3). These names will appear
throughout the Roadnet Transportation Suite as column headers and on reports
whenever this data appears.
Note: Categories are only used in Roadnet.
Step 2: If needed, assign names or headers to one or more of the user-defined fields
(User Defined 1, 2, and 3). These are user-defined fields that can be used to enter
additional location, stop, order, or line item information. Location user-defined
fields are used throughout the Roadnet Transportation Suite. Order and line item
Operations Guide
67
Setting the Options
user-defined fields are used with Roadnet and MobileCast; route and stop userdefined fields are only used in MobileCast.
The size aliases you choose here will appear throughout the Roadnet Transportation Suite
whenever sizes are displayed.
Notes: The names you assign to the User Defined - Location will appear as headers on
the Extended Attributes page of the Location notebook and in all location
windows. You can enter user-defined field information for the location in the
Locations notebook, or you can import it. See Entering Extended Attributes or
Importing Locations for more information.
The names you assign to the User Defined - Route and User Defined - Stop fields
will appear in the Dispatcher. You can enter information in these fields in the
Properties notebook in the Dispatcher, or they can be imported. See Completing
the User Defined Fields or Importing Daily Routes for MobileCast for more
information.
The names you assign to the User Defined - Order and User Defined - Line Item
fields will appear in the Dispatcher and the Routing Editor. You can enter
information in these fields Maintenance (when manually entering an order), in the
Properties notebook in the Dispatcher, or import the information. See Working
with Planned Orders, Completing the User Defined Fields or Importing Daily
Orders for more information.
Step 3: If you are using containers with MobileCast, enter the name you want
associated with the containers in the Container field. This name will appear on
the menus and other places where containers are referenced.
68

Setting the Options
Step 4: If you want to use reference numbers to track your routes in the MobileCast
Dispatcher, enter the alias in the Route Reference Alias field.
Setting the Unit Reference Defaults
The Unit Reference Page of the Options notebook allows you to select your unit of
measure, cost, service, distance, and variable service time. This is the only place you can
establish or change these defaults in the Roadnet Transportation Suite.
The Unit Reference tab lets you determine which of your sizes will be used
to calculate equipment capacity, cost, service time, and bulk service time
for the routes.
Operations Guide
69
Setting the Options
Step 1: Click in the appropriate circles to choose the Unit of Measure, Unit of Cost, Unit
of Service, Unit of Loading, Unit of Bulk Service, and Unit System as described.
Unit of Measuredetermine which quantity is used when calculating minimum
capacities for routes.
Unit of Costdetermines which quantity (Size 1, 2, or 3) will be used when
calculating the cost per unit delivered. It is used to calculate the driver cost, if the
driver is paid for the number of pieces delivered. Plus, the cost per unit delivered
is multiplied by the variable fee, then added to the fixed fee to determine the total
fee for a location.
Unit of Servicedetermines which quantity (Size 1, 2, or 3) will be used when
calculating variable service time.
Unit of Bulk Servicedetermines which quantity (Size 1, 2, or 3) will be used
when calculating variable service time on bulk orders.
Unit of Loadingdetermines which size will be shown as the quantity in
FleetLoader.
Unit Systemdetermines whether metric units or non-metric (English) units will
be used to express distance, speed, height, and weight throughout the Roadnet
Transportation Suite. This option does not control what units are used for
measurements associated with the map; the units of measure for map features are
determined by your map provider and cannot be changed.
Step 2: Click on the arrow to choose how detailed the variable service time will be for
your locations. You may enter variable service time in tenths, hundredths,
thousandths up to millionths of a minute.
Step 3: If you are importing line items with your orders and do not want SKU service
times used for bulk orders, check Ignore SKU Service Time for Bulk Service. If
this option is not selected, the SKU service time will be added to the bulk service
time for the order.
Step 4: In the Size Precision field, enter the number of digits you want to display to the
right of the decimal point in the quantity fields. For example, if you want to enter
a quantity of 9.0025, enter 4 in the Size Precision field. You can enter the number
manually, or use the small arrows to scroll to the number. The default is 0, but
you can have as many as 6 digits after the decimal point.
Step 5: If you are tracking the carbon emissions for your routes, enter the information
in the Carbon Emissions Units area. Click the CO2 Computation Method arrow
and choose the proper measurement method: Pounds per Gallon (US) or Grams
per Kilometer (Europe). Click the Carbon Output Display arrow and choose how
the results should be displayed on the report: as pounds, kilograms, or tonnes.
70

Setting the Options

Setting the Duty Period Monitor Options
Used with: Roadnet, MobileCast
The Duty Period Monitor page of the Options notebook allows you to set up duty period
rules, which regulate the amount of time that drivers can work and how much rest they
must get. You can use these rules to help your organization comply with safety and labor
regulations. On this page you can also select whether activities such as breaks, waits, and
layovers count toward the time drivers are considered to be working.
When setting up the duty period rules, you can use either Hours of Service rules or
Working Time Directive rules. Hours of Service rules are designed for organizations
operating in North America, while Working Time Directive rules are designed for
organizations in the European Union.
Once you set up the duty period rules that drivers must follow, you can use exceptions
that will notify you when a duty period rule is violated. You can enable a route exception
in Roadnet that allows you to consider potential duty period violations when planning
routes. You can also enable a route exception for MobileCast that will alert you of duty
period violations that occurred on routes run MobileCast. You can view and edit the work
time history for each driver in the Duty Period History window.
Important: The Duty Period Monitoring feature in the Roadnet Transportation Suite is
not a replacement for any records that you are required to keep by law, such as
DOT logs.
Step 1: Click the Rule set arrow and select either Hours of Service (North America) or
Working Time Directives (European Union), depending on where you are located.
Operations Guide
71
Setting the Options
If No duty period monitoring is selected, drivers work time will not be monitored
by the Roadnet Transportation Suite.
The Duty Period Monitor page lets you select whether time that drivers spend on
activities such as breaks, waits, and layovers will be considered on duty or off duty.
72

Setting the Options
Step 2: Click [Configure]. Depending on which option you selected in Step 1, either the
Hours of Service rules or the Working Time Directive rules window opens.
If you are in North America, you will use Hours of Service rules. If you are in the European
Union, you will use Working Time Directive rules.
Step 3: Change the rules as necessary. For more information about each of the rules,
refer to the tables at the end of this section.
Note: If you want to set all of the Hours of Service or Working Time Directive rules to
their default setting, click [Set Defaults].
Step 4: Click the [OK] button. You will return to the Duty Period Monitor page.
Step 5: In the On-duty selection area, check the box for each activity where drivers
should be considered to be working.
The options you select here are used when the Roadnet Transportation Suite
calculates how long drivers have been working (on duty time). However, time
spent doing these activities will not be considered driving time. For example, if
you select Paid breaks are on-duty, any time that a driver spends on paid breaks
will count toward that drivers working time, but not their driving time. Any time
spent doing activities that are not checked will count toward drivers off duty time.
The options you select can affect when certain duty period violations will occur.
Operations Guide
73
Setting the Options
Hours of Service Rules (North America)

Rule
Default
Description
Maximum hours of drive

time in a Tour of Duty
11 hours
The maximum number of hours drivers are

allowed to drive in a shift. Time that a driver is
working, but not driving, does not count
toward this limit. For example, time spent
servicing a stop or time on a break, wait, or
layover will not count toward this limit.
May not drive after this

many hours since Tour of
Duty start
14 hours
A driver is no longer allowed to drive if this

many hours passes from when their current
shift was started. All time after a drivers shift
began counts toward this limit, including any
time spent off duty. This rule does not prohibit
drivers from working after this limit is reached
as long as they are doing non-driving activities.
Minimum consecutive hours

off duty to reset a Tour of
Duty
10 hours
The minimum number of consecutive hours

drivers must be off work for a new shift to
begin. You can select whether or not time spent
on activities such as breaks, waits, and
layovers is considered off work on the Duty
Period Monitor page of the Maintenance
Options notebook.
Number of days in a Cycle
7 days
The number of days in a work week. This is

a rolling period of time where the current day
is considered the last day of the cycle until the
cycle is reset. Once a drivers cycle is reset, the
driver will be on the first day of a cycle. The
number of days in a cycle is usually either 7 or
8.
May not drive after this

many hours on duty in a
Cycle
60 hours
The maximum number of hours drivers can

have worked in their current cycle and still be
allowed to drive. This is usually either 60 hours
(with a 7 day cycle) or 70 hours (with an 8 day
cycle). Time spent servicing stops will count
toward this limit. However, you can select
whether or not time spent on activities such as
breaks, waits, and layovers will count toward
this limit on the Duty Period Monitor page of
the Maintenance Options notebook. This rule
does not prohibit drivers from working after
this limit is reached as long as they are doing
non-driving activities.
74

Setting the Options
Rule
Default
Description

off duty to reset a Cycle
34 hours
The number of consecutive hours drivers must

be off work for a new cycle to begin. Once a
driver has been off duty the number of hours
specified here, the driver will begin a new
cycle regardless of how many days has passed
in the previous cycle. You can select whether
or not time spent on activities such as breaks,
waits, and layovers is considered off work on
the Duty Period Monitor page of the
Maintenance Options notebook.
Working Time Directives

Rule
Default
Description

time in a driver shift
9 hours
The maximum number of hours a driver is

allowed to drive in a shift. Time that a driver is
working, but not driving, does not count
toward this limit. For example, time spent
servicing a stop or time on a break, wait, or
layover will not count toward this limit.
Except for __ maximum

hours on __ driver shifts per
week
10 hours;
An exception to the Maximum hours of drive

time in a driver shift rule. This exception
allows drivers to drive an extended number of
hours a specified number of times each week.
Maximum hours of on duty

time in a driver shift
13 hours

work in a single shift. All driving time and
service time will count toward this limit.
However, you can select whether or not time
spent on activities such as breaks, waits, and
layovers will count toward this limit on the
Duty Period Monitor page of the Maintenance
Options notebook.

off duty required between
driver shift
11 hours
The minimum number of hours drivers must be

off work between shifts. You can select
breaks, waits, and layovers is considered off
work on the Duty Period Monitor page of the
Maximum driver shifts per

week
6 driver
shifts
The maximum number of shifts drivers can

work in any consecutive 7 day period of time.
2 driver
shifts
Operations Guide
75
Setting the Options
Rule
Default
Description
Maximum hours of on duty

time per week
60 hours

work in any consecutive 7 day period of time.
All driving time and service time will count
toward this limit. However, you can select
breaks, waits, and layovers will count toward
this limit on the Duty Period Monitor page of
the Maintenance Options notebook.

off duty required per week
45 hours
The minimum number of consecutive hours

that drivers must be off work beginning
midnight Monday through 11:59 PM Sunday.
You can select whether or not time spent on
activities such as breaks, waits, and layovers is
considered off work on the Duty Period
Monitor page of the Maintenance Options
notebook.

time in a Fortnight
90 hours

drive in any consecutive 14 day period of time.
Time that a driver is working, but not driving,
does not count toward this limit. For example,
time spent servicing a stop or time on a break,
wait, or layover will not count toward this
limit.
Period duration in number of

weeks
17 weeks
The number of weeks in a period; usually

either 17 or 26. The number of weeks in a
period is used when determining the average
number of hours per week a driver has worked.
Maximum average hours on

duty per week over a Period
48 hours
The maximum average number of hours

drivers can work over the number of weeks
specified for a period. All driving time and
service time will count toward this limit.
However, you can select whether or not time
spent on activities such as breaks, waits, and
layovers will count toward this limit on the
Duty Period Monitor page of the Maintenance
Options notebook.
Setting the General Dispatching Options
76

Setting the Options
The Dispatch - General page of the Options notebook allows you to set up a variety of
options pertaining to MobileCast. From this page, you can set up the time/distance
calculator, your wireless and onboard integration, reason codes, event processing, and
more.
The Dispatch - General page provides a wide variety of dispatching

options.
The Miscellaneous section allows you to establish several default options used with
MobileCast.
Step 1: In the Miscellaneous section, check any of the following default options:
Auto Generate Route IDtells MobileCast to pre-fill the ID field when a route
is created. You can change the route ID when adding the route if desired.
Auto Generate Unique DTR Numberscan be turned on when you first set up
a region to have MobileCast keep track of DTR numbers (route numbers) for you.
If it is turned on, the fields for entering route numbers will be grayed out in the
Import module.
Quantities Are A Ratio Of Size 1toggles whether or not the size aliases are
ratios. If they are ratios, MobileCast will calculate the quantities for size 2 and size
3 based on the quantity for size 1.
Note: You must have this option checked if you want the handheld device to display an
Order Summary.
Operations Guide
77
Setting the Options
Driver Assignment Requiredallows you to specify whether a driver must be

assigned to a route before it is started. This is the default setting; you can change
it for an individual route in the Assignment for Routes notebook.
Equipment Assignment Requiredallows you to specify whether equipment
must be assigned to a route before it is started. This is the default setting; you can
change it for an individual route in the Assignment for Routes notebook.
Allow Additional Stop Typesallows you to add a break, wait, layover, or midroute depot to a route.
Note: You must have this option checked if you want to add breaks, waits, layovers, or
mid-route depots in the Dispatcher. For more information, see Adding Breaks,
Waits, or Layovers to a Route, or Inserting a Mid-Route Depot.
Designate Unplanned Stops As Paidcheck to set all breaks, waits, and
layovers as paid when added on the fly by the driver.
Allow Override of Actuals During Routecheck if you want to be able to
change the actual times and quantities of a stop after that stop is completed, but
before the route is completed.
Note: This option will also allow you to edit the arrival and departure times of completed
breaks, waits, and layovers during the route.
Important: It is recommended that you do not adjust actual times for a stop until the next
stop is completed. Also, you should not change actual times for completed stops
to a future time. For example, if a stop was completed at 1:00 pm and the current
time is 1:30 pm, you should not change the actual time to indicate the stop was
completed at 2:00 pm. Doing so may cause errors or disruptions to the route
sequence.
Calculate Service Timescheck to have the stops service times automatically
recalculated whenever a change is made to a route, stop, order, or line item. For
instance, if additional items are added to an order, the stops service time would
be updated.
Calculate Distance by Jurisdictioncheck to have the distance the route
traveled in each state/province/jurisdiction automatically calculated when the
route is completed. Distances are calculated by measuring the straight line
distance between GPS pings. If this option is selected, reports can be generated
from within the Dispatcher about the distances traveled.
Allow Asynchronous Arrivalscheck to allow drivers to deliver two stops out
of the expected order. For instance, if the route has a driver and a helper, and both
people have wireless devices, they may split up to deliver two nearby stops. In that
case, the expected stop may not be delivered first. This option is only valid if you
are using the Roadnet Transportation Suite Web Services to push information into
78

Setting the Options
the MobileCast Dispatcher. This option cannot be used with Roadnet

Technologies devices.
Stop Critical Minutesenter the number of minutes late the stop must be before
it is considered critical.
Step 2: In the Time/Distance Calculation area, click in the appropriate circles/boxes to
select the Time/Distance Calculation options and other session options.
limits and road changes. Compared with XY, RouteNet takes longer to process but
is more accurate. The default setting is RouteNet.
Notes: If the memory required for the build exceeds 2 GB, times and distances will be
SuperMatrix, you need to specify how you want the Dispatcher to handle locations
that have been added since the SuperMatrix was last built. In the Realtime
Updating area, select whether you want to use XY or Street Network to calculate
the distances to these locations.
directory.
the Maintenance Options notebook. If you want road restrictions to be enabled in
MobileCast, check Apply Road Restrictions. When the road restrictions feature is
enabled, equipment types that are prohibited from traveling on height and weight
Operations Guide
79
Setting the Options
restricted roads will only be routed on street segments that are not restricted when
routes are created or edited. If it is impossible to reach a stop without traveling on
a street segment that is restricted, the stop will be routed using the XY method.
with RouteNet or SuperMatrix; it cannot be used with the XY method.
creating routes.
routes. Select the rush hour model that the session should use from the Rush Hour
Model field.
advanced rush hour may require additional time when entering the Routing
Editor.
Use Historical Travel Speedsuses historical travel data when creating routes.
This option is only available if you purchased historical travel speeds.
Time Modellets you choose the travel time model that will be used if you
selected XY as the Time/Distance Calculator. The time model also supplies the
fixed travel time used for the stops.
The Event Processing section allows you to establish several default options used with
MobileCast.
Step 3: In the Event Processing section, check any of the following default options:
80

Setting the Options
Automatically Relocate Equipmentallows you to specify whether equipment

should automatically be moved to the necessary location when assigned to a route.
For instance, if the equipment is located at Depot 2, but the route starts from Depot
1, the equipment will automatically be switched to Depot 1 and assigned to a
route. If used, this feature overrides the built-in equipment tracking feature in
MobileCast, and could hide poor equipment tracking within the organization. The
Automatically Relocate Equipment option is checked as the default setting.
Automatically Fixup Wireless Eventsallows you to specify whether wireless
events should be automatically fixed when a stop departs before it arrives, a stop
completes before the previous stop departs, or a route tries to start when the
equipments status is In Use. If this option is not selected, you can attempt to fix
the event manually using the Attempt to Fix Error button on the Edit Event
window. Departure times will be fixed using the projected depart time. The
equipment status will be changed to Ready and the equipment will be moved to
the appropriate location. When an event is fixed successfully, a route note is
created.
Use Cross Street Position Textallows you to receive specific address
information about where the equipment is located. For instance, if the equipment
is located five miles north of Baltimore, near the corner of Maple Avenue and
Division Street, the message sent to the dispatcher will provide this information.
If this option is not selected, the message will show the equipment is five miles
north of Baltimore, but not provide address information.
Warning: Enabling cross street positioning could cause the performance of your program
to slow down significantly.
The Reason Codes section allows you to specify any reason code requirements when a
stop is completed. For example, if you select Pickup, the driver will be required to enter
a reason code if the actual pickup quantity is different from the planned quantity.
Step 4: In the Reason Codes section, check the situations in which a reason code would
be required for any discrepancy.
Deliveryrequires a reason code for any quantity variance for a delivery.
Overrequires a reason code if the actual amount you are over is different from
the planned amount over.
Damagedrequires a reason code for any damaged product.
Pickuprequires a reason codes for any quantity variance for a pickup.
Shortrequires a reason code if actual shortage is different from your planned
shortage.
Validate Quantitiesrequires MobileCast to check whether one of the following
circumstances applies if the actual quantity varies from the planned quantity:
The pickup quantities are the same as the planned quantities.
The sum of the Delivery, Short, and Damaged quantities are the same as
the planned Delivery quantities.
Operations Guide
81
Setting the Options
Note: If the Enable Edit Quantities Screen or Enable Quantities On Device option on the
Dispatch - SmartPhone page is not checked, but Validate Quantities is checked,
MobileCast SmartPhone will not enforce validation of quantities when the driver
departs a stop.
The Allow Updates to Planned Times/Distances section lets you specify when planned
information, such as the planned arrival and departure times, are updated in the
Dispatcher.
Step 5: Click the Allow Updates to Planned Times/Distances and choose when planned
times and distances can be updated in the Dispatcher. The choices are Never or
Until the route is loaded or started. If you choose Until the route is loaded or
started once the route is loaded onto the device, or started manually, the planned
times and distances will be updated when the route changes.
Step 6: In the Route Capacity Checking area, check the appropriate size alias(es) for
MobileCast to monitor the equipments available capacity while sequencing,
time windowing, or performing other route actions.
This option is particularly helpful if your routes contain both pickups and
deliveries, and you want to monitor the available capacity during the route.
Setting the Default Detail Level
The Dispatch - Detail Level page of the Options notebook allows you to establish the level
of detail that will be tracked for the routes in MobileCast. You can choose to track just
stops, orders, or even line items for the orders on the routes. If you are using containers,
82

Setting the Options
you can also establish the parameters you will use on this page. The detail level should be
set when a region is first set up and should not be changed.
The Dispatch - Detail Level page is used if you are tracking stops, orders, containers,
or line items.
Step 1: In the Detail Level Support section, click on the appropriate circle to choose a
detail level. The detail level selected here determines the level that you can track
throughout MobileCast. The default setting is Order.
Step 2: If you will be using containers, check Use Containers. If this option is checked,
you will be able to associate containers with orders in the Dispatcher module.
Note: If you are tracking routes at the stop level, you will not be able to track containers,
and the Use Containers options will be disabled.
Step 3: In the Container Options section, click the appropriate box(es) to choose your
container option(s).
Use Container ID As Barcodecheck to use the container's ID as its barcode
number.
Require Verification Of Containers Before Trip Startscheck to require
drivers to scan and verify the containers before the trip can be started on the
wireless device.
Require Verification Of Containers At Each Stopcheck to require the drivers
to scan and verify the containers at each stop before the stop can be departed on
the wireless device.
Operations Guide
83
Setting the Options
Require Verification Of Containers Before Route Completescheck to

require the drivers to scan and verify the containers before the route can be
completed on the wireless device.
Group Unloadingcheck if the driver may be delivering several stops at the
same time. This may happen if the stops are located in an office building, mall, or
a similar location where the driver parks once for several stops. If this option is
selected, the driver can choose the stops that will be delivered together. Enter the
maximum distance between the stops in the Grouping Candidate Tolerance field.
Grouping Candidate Toleranceif you checked Group Unloading, then enter
the maximum distance apart, in miles or kilometers, the stops can be before they
can be delivered at the same time. For example, if you enter 0.10, and Stop 3 is
0.10 miles away from Stop 4, then the driver will be notified that these stops can
be unloaded and delivered simultaneously.
Step 4: If you are scanning any quantity (containers, line items, etc.), check Verify By
Exception in the Quantity Options section. If this option is checked, and the
driver does not scan the quantities for delivery, the actual amount will be
completed with the planned amount. If this option is not checked, then the driver
will need to scan every quantity delivered. The Verify By Exception is checked
as the default setting.
Setting the Device Diagnostics Options
The Dispatch - Device Diagnostics page of the Options notebook contains settings that
affect what information will be available when using the device diagnostics feature to
monitor drivers handheld devices. You can set how much diagnostic information the
wireless devices will report and how often the devices will report periodically sent
information back to the server.
Important: To receive diagnostic information from a drivers handheld device, the
Device Diagnostics option must be checked on the Dispatch page of the Edit
Driver window for that driver. If this option is not checked, no diagnostic
information will be available for the drivers handheld device.
You must set the device diagnostics options before routes are loaded onto the
wireless devices. If you change the options after routes have been loaded on any
84

Setting the Options
of the drivers devices, the changes you make wont take effect for those driver
devices until the next time routes are loaded.
The Dispatch - Device Diagnostics page lets you select whether dispatchers will
have access to advanced diagnostic information for the drivers handheld devices.
Step 1: To receive diagnostic information, check Process Device Diagnostics. When

this box is checked, dispatchers will have access to basic diagnostic information
from the server such as Route Start, Route Depart, Stop Arrive, Stop Complete,
Route Arrive, Route Complete, GPS, battery power, signal strength, and Event
Receipts. If you do not check Process Device Diagnostics, device diagnostics
information will be unavailable.
To receive all diagnostic information generated by the wireless devices, check
Enable Advanced Diagnostics. When this box is checked, the devices will send
additional information back to the server that dispatchers can view. This includes
information regarding communication problems that have occurred, logging
information, and error messages. This information may be helpful when
troubleshooting problems with the wireless devices. If you do not check Process
Device Diagnostics, device diagnostics information will be unavailable.
Step 2: Enter how often you want the wireless devices to report periodic diagnostics
back to the server in the Periodic rate (in minutes) field. The default setting is 15
minutes.
Step 3: Click the [OK] button to save the options or continue to another tab.
Operations Guide
85
Setting the Options
Setting the Route History Options
The Route History page of the Maintenance Options notebook allows you to specify the
data that will be archived in the Route History database and the time of day the data will
be saved. Route History is a separate database where you can store historical data about
routes that have been completed; since the Route History database does not store all the
details associated with the daily routes it is much smaller and the data can be stored for a
longer time. It is also easier to write reports against the Route History database. If
selected, you will need to enable Route History for each session you want included; you
can set it so that Route History is enabled by default for your routing sessions.
Notes: You must set up the tsroutehistoryservice.cfg file for the update to run as expected.
Normally this is done during the installation process.
Routes will not be added to Route History until the planned route completion time
has passed.
You are able to specify the data to be archived as well as the time of day the data
will be saved.
86

Setting the Options
Step 1: Select the data you want added to Route History.

To have built routes in Roadnet added to Route History, check Enable Roadnet as
a data source.
To have completed routes in MobileCast added to Route History, check Enable
MobileCast as a data source.
Note: If both Roadnet and MobileCast data are being saved, the completed route from
MobileCast will be saved instead of the built route from Roadnet.
Step 2: Enter the time of day the data will be saved to the Route History database.
When entering the time, use a 24-hour clock, so enter 1:00 PM as 13:00.
Hint: Roadnet Technologies recommends that the data be saved during the night or some
other time when fewer people will be using the Roadnet Transportation Suite.
Step 3: Click the [OK] button to save the options or continue to another tab.
Page.
Setting the SuperMatrix Options
Used with: Roadnet, netScheduler, Territory Planner, MobileCast
The SuperMatrix Update page of the Maintenance Options notebook allows you to
schedule the time each day when the SuperMatrix will be updated. When the SuperMatrix
is updated, any locations that have been added or regeocoded will be added to the
SuperMatrix. Because the update can take a long time to complete, it is recommended that
you schedule the update to run when routing will not be occurring. You will only need to
schedule the SuperMatrix update if you are using the SuperMatrix as your time/distance
calculator in the Routing Editor, Planning Editor, or Dispatcher.
Notes: In order to use the SuperMatrix, you must have write permission to the map data
directory.
In order to update the SuperMatrix using this method, the SuperMatrix service
needs to be installed and configured. This can be done using InstallShield. The
Operations Guide
87
Setting the Options
service configuration parameters are stored in the tsSuperMtxServer.cfg, usually

found in the ts_services_home environment variable.
You are able to schedule the time of day when the SuperMatrix will be updated.
Step 1: To schedule the SuperMatrix to be updated daily, check the Enable SuperMatrix
Update box.
Step 2: In the Update SuperMatrix each day at time field, enter the time you want the
SuperMatrix update to run. This field uses a 24-hour clock, so enter 1:00 PM as
13:00.
Hint: Roadnet Technologies recommends that the update be run during the night or
some other time when fewer people will be using the Roadnet Transportation
Suite.
Step 3: Check the Build Historical Travel Speeds SuperMatrices box if you are using
the historical travel speeds feature and want to have these times and distances
available.
Note: If the map does not support historical travel speeds, the checkbox is grayed out.
Page.
88

Setting the Options
Setting the Historical Travel Speeds

Note: The Historical Travel Speeds tab will only appear if you have purchased Historical
Travel Speeds.
The Historical Travel Speeds page of the Options notebook allows you to simulate a rush
hour for street segments that do not have historical travel speeds. This can reduce the
possibility that a route will take roads that do not have supplied historical travel speeds,
such as local roads.
For example, you want the local roads that do not have historical travel speeds of 55 mph
to be reduced by 40 percent for the Mon - Thurs 6 am - 9 am time period. To accomplish
this, you select Slower in the 6 am - 9 am slot and type in 40. This will cause all streets
without a historical travel speed reduced by 40% or to 33 mph.
You are able to simulate a rush hour for street segments that do not have historical
travel data.
Step 1: For a time period, enter the percentage that you want to either travel faster or
slower.
Step 2: Select Faster or Slower to indicate the speed.
Step 3: Complete each of the remaining fields as necessary.
Operations Guide
89
Setting the Options
Page.
Setting the MobileCast Continuous Optimization Options
The Dispatch - Continuous Optimization page of the Options notebook allows you to set
up the criteria for MobileCast to constantly and dynamically assign unasigneds to routes
and reassign stops to other routes throughout the day. By using Continuous Optimization,
your dispatcher does not need to take the time during the day as orders are coming in to
place them on routes; instead MobileCast will automatically place them on the route that
best meets the criteria set up.
When using the Continuous Optimization feature:
You can specify the parameters that are used to determine which route to add the stop
to.
If using skill sets, you can have them considered when stops are assigned.
You can have MobileCast report which stops were assigned and which were not in
the Message Center.
You can have stops transferred to another route if their current route exceeds the
specified guidelines.
You can place stops on routes that are currently in transit, before the driver arrives at
the next stop or depot.
Note: To prevent MobileCast from over-capacitizing a route by when running continuous

optimization, make sure Route Capacity Checking is selected for the appropriate
size(s) on the Dispatch - General page. If this option is selected, MobileCast will
not add or transfer a stop or unassigned to a route where its addition would cause
the equipment to be over-capacitized.
Step 1: Check Enable Automatic Assignment if you want MobileCast to constantly and
dynamically place unassigned stops on routes throughout the day.
Step 2: Check Generate Route Notes On Success to have MobileCast generate
messages when an unassigned is assigned to a route. The messages can be
viewed in the Message Center.
Step 3: Check Generate Route Notes On Failure to have MobileCast generate messages
when an unassigned cannot be assigned to a route.
Note: MobileCast will not generate duplicate notes for stops that failed to be assigned. If
you acknowledge a message concerning a failure, it is removed from the Message
Center. MobileCast will continue to try and assign the stop to a route, but if there
are anymore failures, a new message will not appear.
90

Setting the Options
Step 4: Check Enable Automatic Reassignment if you want MobileCast to take an

existing stop and reassign it to another route.
Step 5: In the Time Window Threshold ___ minutes late field, enter the minimum
number of minutes the route can miss the time windows to be considered for
reassignment. This number represents the sum of the amount the driver is late for
all the time windows on the route. For example, your route has 25 stops on it and
the criteria set up for your time window threshold is 10 minutes. So if your
second stop arrives 4 minutes late according to the time window, the fifth stop
time window is projected to be late by 3 minutes and the sixth stop time window
is projected to be late by 4 minutes, then the remaining stops on your route would
be eligible for reassignment to other routes.
If you select any of the criteria in the Dispatch - Continuous Optimization tab, you
allow the system to constantly and dynamically assign and unassign stops
throughout the day based on the selected criteria.
Step 6: Check Must Meet TW Limit To Reassign to only remove stop(s) from a route if
removing the stop allows the route to meet the defined Time Window Limit.
Enter the minimum number of minutes the route cannot miss all of the stops
time windows in the Time Window Limit __ missed minutes field.
Step 7: Check Generate Route Notes On Success to have MobileCast generate
messages when a stop is transferred to another route.
Step 8: Check Generate Route Notes On Failure to have MobileCast generate messages
when a stop cannot be transferred to another route.
Operations Guide
91
Setting the Options
Note: MobileCast will not generate duplicate notes for stops that failed to be assigned. If
you acknowledge a message concerning a failure, it is removed from the Message
Center. MobileCast will continue to try and assign the stop to a route, but if there
are anymore failures, a new message will not appear.
Step 9: In the Include Only Routes That Are section, select one of the following:
Not Completed only routes that have not been completed will be considered.
Not Startedonly routes that have not begun will be considered.
Not Departedonly routes that have not departed from the origin will be
considered.
To consider only routes that have the current date as the planned start date,
check Todays Routes.
Step 10: In the Prioritize Changes By section, select one of the following:
Best DistanceMobileCast will add the stop to the route that will cause the least
increase in distance.
Best TimeMobileCast will add the stop to the route that will cause the least
increase in runtime.
Best Time WindowMobileCast will add the stop to the route where it will
cause the least disruption to meeting time windows.
Step 11: Check Consider Skill Sets to only consider routes where the driver has the
necessary skill sets to complete the activities. If this option is selected, only
routes with a preferred skill set that includes the order activities will be
considered.
Step 12: Check Enforce Equipment Type Restrictions to only consider routes that are
assigned an equipment type not restricted by the stop or unassigned.
Step 13: Check Maximum Runtime to only consider routes whose maximum runtime will
not be exceeded if a stop is added. Enter the maximum amount of time that the
route can last. Any route whose runtime would be exceeded by adding a stop will
not be considered.
Step 14: Check Maximum Stops per Route to only consider routes that do not exceed a
specified number of stops. Enter the maximum number of stops allowed per route
below. Only routes that will not exceed this number if this unassigned or stop is
added will be considered.
Step 15: Check Must Meet TW Limit To Assign to prevent routes missing the Time
Window Limit when stops are added. Enter the minimum number of minutes the
route cannot miss all of the stops time windows in the Time Window Limit __
missed minutes field.
Step 16: In the Time Window Limit __ missed minutes field, enter the minimum number
of minutes the new route cannot miss all of the stops time windows by or the stop
will not be assigned/transferred. This time includes being early or late. For
example, The Time Window Limit is set to 10 minutes. You have a route and
92

Setting the Options
MobileCast added a stop to the current route that causes the route to miss the time
windows by 15 minutes. The stop would not be added to the route.
Note: This option is only available if Must Meet TW Limit To Reassign or Must Meet
TW Limit To Assign field is checked.
Step 17: Check Consider Before Next Arrival to place unassigned and existing stops as
the next stop on a route that is currently in transit. In Minutes Before Next, enter
the minimum number of minutes before the projected arrival at the next stop for
this placement to be considered. Positions on routes that are currently in transit
and have at least this much time before the next scheduled stop or the depot will
be analyzed.
Notes: If the next stop on a current route is not eligible, the remainder of that route will
still be analyzed according to the other options selected on the Continuous
Optimization page.
This function only applies to current routes that are Not Completed. If either Not
Started or Not Departed is selected under Include Only Routes That Are, Consider
Before Next Arrival is not available.
If Minutes Before Next is set to 0, the unassigned or reassigned stop will be placed
before the next stop on the route, regardless of the next stops projected arrival
time.
Page.
Setting the Schedule Options
Used with: netScheduler
The Schedule page of the Options notebook is used with netScheduler. The information
on this page tells Cost Analyzer where the Roadnet Web Service is running so that it can
communicate with the server.
Step 1: In the URL field, enter the url of the machine where the services are located. For
example, http://localhost.
Step 2: In the Port field, enter the port number on the server through which the service
communicates. For example, 80.
Note: These fields are only available if you have purchased netScheduler.
Operations Guide
93
Setting the Options
Page.
94

Setting the Mobile Options

Note: If you have not been granted permission to change maintenance options in the
Administration module, you will not be able to open this notebook.
The Roadnet Transportation Suite allows you to set up default options related the mobile
devices that your drivers use. Some of the settings, depending on what mobile devices and
features you use, change how the software acts or responds, limit what the driver is
allowed to do on a route, as well change how order details display. When setting mobile
options, the General page affects all devices. The Auto Arrrive/Depart page is for both
SmartPhone and the Java-enabled phone, while the other pages are specific to the types
of devices for which the page is named.
Step 2: Click on the Tools menu and select Mobile Options. The Mobile Options
notebook opens.
Tools Mobile Options
For more information see the General Page, SmartPhone Page, Java Phone Page, Auto
Arrive/Depart Page, Handheld Page, and the Telematics Page.
Setting the General Mobile Options
The General page of the Mobile Options notebook allows you to set up a variety of
options pertaining to MobileCast running on all types of mobile devices. From this page,
you can set up how often the mobile device contacts the Dispatcher as well as what general functions the driver is allowed to perform. Click on the General tab.
Step 1: The General Mobile Options area contains options that affect how MobileCast
will operate on the mobile device. Set the options as desired.
Message Polling Timeoutallows you to adjust how often messages are sent to
Dispatcher. Enter the polling rate in the format H:MM:SS. A lower polling rate
means messages are received more quickly, but causes more processing by the
server. A higher polling rate reduces the number of times messages are sent/
received, lowering the processing burden, but increasing the wait between receipt
of messages. The default is 120 seconds.
GPS Intervalallows you to adjust how frequently GPS data is collected. Enter
the frequency in the format H:MM:SS. A lower interval (30 seconds) will ensure
more GPS data, but requires more network space. A higher interval (15 minutes)
Operations Guide
95
decreases the data network space needed, but the GPS can suffer. The default is
30 seconds.
Note: If the GPS Interval option is set and Send GPS By Distance is checked on the Java
Phone page, the position data will be gathered when either condition is met.
Show Confirmation Dialogsallows you to control whether or not the drivers
need to confirm their actions on the mobile device. If you want the drivers to
confirm actions before they can be performed, then this option must be checked.
The Show Confirmation Dialogs option is checked as the default setting.
Note: If this option is not checked, the drivers will still need to confirm Pick New Stop,
Redeliver, and Add a Break, Wait, or Layover actions.
Step 2: In the Allow Driver To area, select the options to which you want the driver to
have access.
Geocode Locationsallows drivers to geocode the stops location on the mobile
device. If you want the driver to be able to send the latitude and longitude of your
customer locations to MobileCast, so they can be used to create more accurate
routes, then this option must be checked.
SendText While Drivingallows you to set whether or not the driver can send a
text message on a Proceeding to screen on the mobile device. If you want the
96

driver to be able to send text messages while on the Proceeding to screen, then
this option must be checked.
Redeliver Completed Stopsallows the driver to return to a completed stop to
correct a delivery on the mobile device. If you want the driver to be able to
redeliver a completed stop, then this option must be checked.
Setting the MobileCast SmartPhone Options
The SmartPhone page of the Mobile Options notebook allows you to define how the
drivers interact with the MobileCast SmartPhone application.
Click on the SmartPhone tab.
Step 1: Place a check in the box for each Administrative option you want to use.
Administrative options affect how MobileCast SmartPhone acts or responds.
Accumulate Distance Only While In Transitif you do not want the
application to collect GPS data while a stop is being serviced, check this
option. GPS data is only collected before arriving and after departing a stop.
Allow Application Exitif you want to allow the driver to be able to exit the
MobileCast application while on the route, check this option. Even if this
option is not selected, the driver will still be able to call the customer or get
directions using the navigation feature, if it was purchased.
Auto Navigate On Departif you want the navigation application, CoPilot,
to automatically start when the driver leaves the depot or stop, check this
option. CoPilot must be installed and configured to work with MobileCast
SmartPhone for this option to work.
Automatically Log Off Driver on Route Completionif you want the
driver to automatically be logged out of the MobileCast application when the
route is completed, check this option.
Display Notifications While In Backgroundif you want the wireless
device to return to MobileCast SmartPhone when a notification is received
when another application, such as navigating, is in use, check this option.
MobileCast SmartPhone must be running in the background for this option to
work.
Call Dispatcher Reminderif you want the driver to be reminded to contact
the dispatcher before returning to the depot, check this option. If selected and
Operations Guide
97
the Show Confirmation Boxes option is checked, the driver will not be able to
arrive at the depot without confirming the dispatcher was contacted.
Consignee Requiredif the driver must enter a consignee before the stop can
be completed, check this option.
The SmartPhone page contains several options that affect how MobileCast
will operate when SmartPhone devices are being used.
Enable Verbose Stop Updatesif you want the driver to receive a message
each time a change is made to a stop, order, or line item, check this option.
Enabling this option may result in a large number of notifications being sent
to MobileCast SmartPhone, causing the wireless device to slow down or lock
up. If unchecked, the driver will receive messages concerning additions and
modifications of a stop, but no order or line item messages.
Signature Capture Requiredif the driver must have the customer sign for
the delivery before the stop can be completed, check this option.
Show Column Headersif you want the driver to see column headers when
on the Orders or Line Item screen, check this option. If unchecked, column
headers will not display, allowing for more information to show on the screen.
98

This option is not available when Show Orders With Line Items is enabled. If
Show Rolled-Up Quantities is selected, this option will not be available.
Show Consignee Historyif you want the driver to be able to choose from a
list of five names, which consists of the last five people who signed for a
delivery or pick-up at the location, check this option.
Show Break Typeif you want the driver to see if the break, wait, or layover
is Paid or Unpaid, check this option. If this option is not selected, the driver
will see a general Type description of Break, Wait, or Layover,
Show Location Information At Stopif you want the driver to be able to see
the Location ID, Name, and address under Location information on the At
Stop screen, check this option. If unchecked, only Location ID and Name will
display, saving screen space for other information.
Show Orders With Line Itemsif you want the driver to see a combined list
of all orders and line items on a single screen, check this option. This setting
has no visible effect unless the Detail Level Support is set to Line Item. The
first item in the list is a rolled-up total of all orders in the list. Each order is
then displayed with a rolled-up total and its line items beneath it. Uncheck this
option to view orders and line items on separate screens.
Step 2: Allow Driver To options limit what features are available to the driver. Place a
check in the box for each option that you want the driver to be able to use.
Access Device Diagnosticsif you want the driver to be able to see the
diagnostic information on the phone to help troubleshoot any problems that
arise, check this option.
Add Breaks And Layoversif you want the driver to be able to add breaks
and layovers to their route, check this option. Allow Additional Stop Types on
the Dispatch-General page must also be enabled. Planned breaks/layovers are
not affected by this option.
Add Notes To Stops, Orders And Line Itemsif you want the driver to be
able to send notes concerning a specific stop, order or line items, check this
option. If unchecked, the driver will only be able to send text messages at the
route level. If this option is not selected, Add Pictures To Notes will not be
available.
Add Orders and Line Itemsif you want the driver to be able to add orders
to a stop or line items to an order, check this option.
Add Pictures To Notesif you want the driver to be able to attach a picture
to a note for a stop, order, or line item, check this option. This option is only
available if Allow Driver To Add Notes To Stops, Orders, And Line Items is
Operations Guide
99
checked. Depending on the mobile devices you use, you may not be able to
take pictures.
Add Pictures To Text Messagesif you want the driver to be able to attach
a picture to a text message at the route level, check this option. Depending on
the mobile devices you use, you may not be able to take pictures.
Arrive And Waitif you want the driver to be able to arrive at a stop and
wait, check this option. Allow Additional Stop Types on the Dispatch-General
page must also be enabled. Planned waits are not affected by this option.
Call Locationif you want the driver to be able to call a location on the route,
from within MobileCast SmartPhone, check this option. A valid phone
number must be available for the location. If necessary, the driver can still
leave MobileCast SmartPhone, make a call, then return to the application.
Cancel Stopsif you want the driver to be able to cancel stops, check this
option. If this option is not selected, Cancel Remaining Stops will not be
available.
Cancel Remaining Stopsif you want the driver to be able to cancel all
unvisited stops at one time, check this option. If unchecked, stops must be
canceled one at a time. The Cancel Stops option must be enabled for this
option to be available. If Cancel Stops is not selected, this option will not be
available.
Preview Routeif you want the driver to be able to see the days stops before
starting the route, check this option. If unchecked, the driver will not be able
to view the route until it is started.
Resequence Stopsif you want the driver to be able to change the order of
stops, check this option.
Step 3: Place a check in the box for each Quantity option you want to use. Quantity
options control how order details are displayed.
Enable Quantities On Deviceif you want the driver to be able to see the
quantities on a stop, order, or line item, check this option. These quantities
display in the Size 1, Size 2, and Size 3 fields. If unchecked, the driver will not
see the quantities. If Validate Quantities on the Dispatch - General page is
checked and Enable Quantities On Device is unchecked, MobileCast
SmartPhone will not enforce validation of quantities when the driver departs
a stop. If this option is not selected, no other options in the Quantities group
will be available.
Enable Edit Quantities Screenif you want the driver to be able to edit
quantities on a stop, order, or line item while on the Edit Quantities screen,
check this option. If Validate Quantities on the Dispatch - General page is
checked and Enable Edit Quantities Screen is unchecked, MobileCast
SmartPhone will not enforce validation of quantities when the driver departs
a stop. If this option is not selected, Enable Over, Short and Damaged
100

Quantities will not be available. If Enable Quantities On Device is not

selected, this option will not be available.
Enable Over, Short, and Damaged Quantitiesif you want the driver to be
able to edit Over, Short, and Damaged quantities on a stop, order, or line item
on the Edit Quantities screen, check this option. If unchecked, the driver will
not see the Over, Short, and Damaged rows. If Enable Quantities On Device
and Enable Edit Quantities Screen are not selected, this option will not be
available.
Allow OSD By Manual Check-Offif you want the driver to be able to
manually check the reconciled checkbox at the detail level, automatically
reconciling the item, check this option. This sets the Actual quantity equal to
the Planned and the Over, Short, and Damaged to zero. Checking the
reconciled box overwrites any previous entries made for the item for all three
sizes. Unchecking the reconciled box after it has been checked clears the
assigned reason codes and sets the Actual, Over, Short, and Damaged to zero
for all three sizes. If this option is selected and detail level is set to Order,
Allow Check-Off At Stop Level will be available. If this option is selected and
detail level is set to Line Item, Allow Check-Off At Stop Level and Allow
Check-Off At Order Level will be available. If this option is not selected,
Allow Check-Off At Stop Level and Allow Check-Off At Order Level will not
be available. If Enable Quantities On Device is not selected, this option will
not be available.
Allow Check-Off At Stop Levelif you want the driver to be able to
manually check the reconciled checkbox at the stop level when the Detail
Level Support is set to Order, check this option. Checking the reconciled box
for a rolled-up total on the device reconciles the stop while unchecking the
reconciled box clears the assigned reason codes and sets the stop quantities to
zero. Checking and unchecking the reconciled box at the stop level has the
same effect as checking or unchecking all the orders below it. This option is
only available if detail level is set to Line Item or Order and Allow OSD By
Manual Check-Off is selected.
Allow Check-Off At Order Levelif you want the driver to be able to
manually check the reconciled checkbox at the order level when the Detail
Level Support is set to Line Item, check this option. Checking the box
reconciles the order while unchecking the box clears the assigned reason codes
and sets the order to zero. Checking and unchecking the reconciled box at the
order level has the same effect as checking or unchecking all the line items
below it. This option is only avaliable if detail level is set to Line Item and
Allow OSD By Manual Check-Off is selected.
Allow Increment Scanningif you want the quantity in the Actual Size 1
field to increment by one when the order or item is scanned, check this option.
Sizes 2 and 3 are incremented based on the planned ratio, even if ratio mode
is off. When the item or order being scanned is reconciled, it is automatically
checked. If an item or order is scanned more times than the Planned Size 1
Operations Guide
101
quantity, the device will beep and the Actual Size 1 will increment, causing an
overage. If Allow Check-Off Scanning is selected, then this option will not be
available. If Enable Quantities On Device is not selected, this option will not
be available.
Allow Check-Off Scanningif you want the Actual quantity to be set to the
Planned quantity and the order or item to be automatically reconciled when an
order or line item is scanned, check this option. Quantities for Over, Short, and
Damaged are set to zero. If an order is scanned that has already been
reconciled, the device will beep, but no changes will be made to the quantities.
There is no way to uncheck an order or line item by scanning; it must be done
manually. When an item is unchecked, the assigned reason codes are cleared
and the quantity is set to zero. If Allow Increment Scanning is selected, then
this option will not be available. If Enable Quantities On Device is not
selected, this option will not be available.
Show Rolled Up Quantitiesif you want the driver to be able to go directly
to the list of line items from the At Stop screen, bypassing the orders screen,
check this option. This option is used when the detail level is set to line item.
If unchecked, depending on detail level, the driver will be able to see lists of
orders and line items, and the combined items list. If Show Column Headers
is selected, this option will not be available. If Enable Quantities On Device is
not selected, this option will not be available.
Step 4: Place a check in the box for each user defined field you want to use. Display
User Defined Fields options allow the driver to see user defined field names and
information on the mobile device.
Note: The user-defined fields are named on the Alias tab of the Maintenance Options
notebook.
Routeif you want the driver to see all available route user defined field
names and information on the mobile device, check this option. If you do not
want the driver to see all of the route fields, they can be checked and
unchecked individually.
Stopif you want the driver to see all available stop user defined field names
and information on the mobile device, check this option. If you do not want
the driver to see all of the stop fields, they can be checked and unchecked
individually.
Orderif you want the driver to see all available order user defined field
names and information on the mobile device, check this option. If you do not
want the driver to see all of the order fields, they can be checked and
Line Itemif you want the driver to see all available line item user defined
field names and information on the mobile device, check this option. If you do
102

not want the driver to see all of the line item fields, they can be checked and
Locationif you want the driver to see all available location user defined
field names and information on the mobile device, check this option. If you do
not want the driver to see all of the location fields, they can be checked and
Setting the Java Phone Options
The Java Phone page allows you to establish several default options when you are using
Java-enabled phones with MobileCast. Click on the Java Phone tab.
Step 1: The MobileCast area of the Java Phone page contains various options that affect
how the application will operate. Each option is described below. Set the options
as desired.
Send GPS by Distanceallows you to specify how frequently the Java-enabled
phone sends position data to the server. Enter the frequency in miles. The lowest
possible frequency is 0.5 miles. The default setting is 1.
Note: If this option is checked and GPS Interval on the General page is set, the position
data will be gathered when either condition is met.
Display Delivery and Pickup Detailsallows you to set whether or not to show
a stops delivery and pickup details on the Java-enabled phone. If you are tracking
over, short, and damaged items, then this option must be checked. The Display
Delivery and Pickup Details option is not checked as the default setting.
Show Planned Times On Previewallows you to control whether or not to
display planned arrival times on the Java-enabled phone. If you want the planned
arrival times displayed on the phone, then this option must be checked.
Step 2: The On Track area of the Java Phone page contains various options that affect
how the application will operate. These options are set if you are using On Track
routing to track your drivers. For more information about using On Track
routing, refer to Working with OnTrack Routes.
Passive Modeallows MobileCast to automatically add stops to a route as
position data is sent from the phone to MobileCast. Passive Mode is used if
you are using unplanned or passive routing, which is convenient for those
employees, such as a salesperson, who want very little interaction with the
Operations Guide
103
Java-enabled phone. The Passive Mode option is checked as the default

setting.
Enter the minimum stop time in the Minimum Stopped Time field.
The Java Phone page contains several options that affect how MobileCast
will operate when Java-enabled phones are being used.
Send Locations to Phoneif you want the employees location information

loaded onto the phone, check this option. If a large number of locations are
assigned to the employee, the phone may not operate properly if the locations
are sent to the phone. If this option is not selected, the employee will not be
able to view the locations on the phone. Roadnet Technologies recommends
you do not check this option. This option is only available if Passive Mode is
selected. The Send Locations to Phone option is not checked as the default
setting.
Minimum Stopped Timeif you checked Passive Mode, then enter the time,
in minutes, that the Java-enabled phone can be stationary before MobileCast
will consider the current GPS as an official stop on a route. For example, if you
entered 10 minutes, and a salesperson is at a customers office for 10 minutes
or more, then the Java-enabled phone will send the current position data to
MobileCast and a stop for this salespersons route will automatically be added.
Step 3: Check the Allow Driver to add breaks, waits, and layovers if you want the
driver to be able to add these stops to their route. Allow Additional Stop Types
104

on the Dispatch-General page must also be enabled. Planned breaks/layovers are

not affected by this option.
Setting the Auto Arrive/Depart Mobile Options
The Auto Arrive/Depart page allows you to establish default options when you are using
auto arrive/depart with MobileCast and Telematics. Auto arrive and depart settings should
be enabled and defined so that the Roadnet Transportation Suite knows how to handle the
position information it receives. Click on the Auto Arrive/Depart tab.
Note: If setting up the telematics feature, you will also need to set options on the
Telematics tab.
Step 1: On the Auto Arrive/Depart page, select whether or not you will use the Auto
Arrive/Depart feature. This feature allows the mobile device and telematics
adapter to automatically detect when a driver is at a stop so that drivers don't have
to press any buttons when arriving and departing. There are several additional
Operations Guide
105
options related to the Auto Arrive/Depart Mode that you must set when the Auto
Arrive/Depart feature is enabled.
Auto Arrive/Depart Enabled (Telematics/Java Phone Only)allows the
mobile device or telematics adapter to automatically arrive and depart stops
without the drivers having to push any buttons. When using this feature with a
mobile device, drivers can still manually press the Arrive and Depart buttons to
arrive and depart stops if needed. The mobile device must be on the In Transit
screen for an automatic arrival to occur and on the At Stop screen for an automatic
departure to occur. If the driver is on any other screen, such as when looking at a
stop's details, no automatic arrivals or departures will occur.
Note: It is essential that your locations are accurately geocoded before using the Auto
Arrive and Depart feature. It is also recommended that Auto Arrive/Depart only
be used by organizations with stops that are physically distant from each other and
that have lengthy service times.
Minimum Stop Timeallows you to specify the length of time a drivers truck
must be stationary while within a stops delivery radius for an automatic arrival to
occur. Enter the length of time in hours and minutes. The default setting is 3
minutes. The maximum time you can enter is 1 hour.
Note: Use Minimum Stop Time For Destination Arrival must be checked for the
Minimum Stop Time to be used for automatic arrival at destination.
Minimum Route Durationallows you to specify the routes minimum run time
after it has started, before entering the destinations delivery radius, for the route
to auto arrive. If the routes planned run time is shorter in length than the
Minimum Route Duration value, the routes planned run time will be used. The
Minimum Route Duration must be met before the driver can arrive at a
destination. Enter the length of time in hours and minutes. This option is only used
with the Roadnet Telematics Adapter.
Minimum Transit Speedallows you to specify the speed in MPH at which a
truck is considered stationary. When both the Minimum Transit Speed and the
Minimum Stop Time are met, a stop is considered arrived. The default setting is 7
MPH. This option is only used with the Roadnet Telematics Adapter.
Auto Departure Of Originallows drivers to be automatically departed from
their origin when beginning their route. This must be enabled for the Roadnet
Telematics Adapter to work.
Auto Arrival At Destinationallows drivers to be automatically arrived at their
destination when completing their route. This must be enabled for the Roadnet
Telematics Adapter to work.
Note: When using mobile devices, if Last Stop is Destination is checked for a route in the
Dispatcher Route Properties notebook, the route arrival will automatically occur
106

even if Auto Arrival at Destination is not selected. For more information, see
Creating a Route in MobileCast Dispatcher.
Auto Cancel Remaining Stopsallows planned stops that were not serviced and
any breaks/layovers that were not taken to be automatically cancelled when the
driver arrives at the destination. When using a mobile device, if Auto Cancel
Remaining Stops is not selected, a driver must resolve any scheduled stops that
were not serviced and any breaks not taken before they will be automatically
arrived at their destination. The Auto Cancel Remaining Stops option can only be
used when Auto Arrival At Destination is selected.
Use Minimum Stop Time For Destination Arrivaltriggers an automatic
arrival when the Minimum Stop Time is satisfied at the route destination.
Checking this reduces the number of false arrivals at the destination.
Auto Sequencingallows stops that are not being delivered in the planned
sequence to automatically arrive and depart. If this box is not checked, routes are
expected to be run in exact planned order. Only stops that are being delivered in
their planned sequence will be automatically arrived and departed. If Auto
Sequencing is enabled, you must choose a Resequence Method.
Resequence Methodchoose how to handle stops when they are skipped on the
route. If you are using Auto Sequencing, you must choose a Resequence Method
for MobileCast to use when stops are skipped on the route. If auto arrive/depart is
enabled, and the driver does not stop at the next scheduled stop on the route, you
must choose how the skipped stop will be handled. Auto Sequencing must be
enabled for a Resequence Method to be defined. Select one of the following
options to occur after the next stop on the route auto arrives.
Move Nextthe missed stops will be moved to the next stop on the
route
Move Lastthe missed stops will be moved to the last stop on the route
Cancel Stopsthe missed stops will be canceled
Push Breaks/Layoverscheck to have breaks and layovers automatically
moved on the route if the driver chooses to take them later. If this option is
checked and the driver chooses to service the next stop instead of taking the
scheduled break, the break will automatically be moved until after that stop. For
example, if the driver is scheduled to take a lunch break after Stop 3 but instead
chooses to service Stop 4 before breaking for lunch, the break will be moved to
after Stop 4. If this option is selected, the driver will need to manually arrive and
depart all breaks and layovers; if this option is not selected, breaks and layovers
will be automatically arrived and departed. This option is only used with mobile
devices.
Break/Layover Departurechoose how breaks and layovers will be departed
on the route. If auto arrive/depart is enabled, and the driver has finished a break or
Operations Guide
107
layover, you must choose how the route will know to begin again. This option is
only used with mobile devices. Select one of the following options.
Manual Onlythe driver will manually choose depart when the break/
layover is over
By Projected Timethe break/layover will auto depart when the
projected departure time is passed
By GPSthe break/layover will automatically end when the drivers
equipment moves the distance away from where the break occurred that
is defined in the Delivery Radius field.
Important: When using mobile devices, after you enable the Auto Arrive/Depart feature
and select the options you want to use, you must select which drivers will use the
feature. For each driver that needs to use Auto Arrive/Depart, you must open the
Dispatch page of the Driver window and select the Auto Arrive/Depart option.
Setting the Handheld Mobile Options
The Handheld page of the Mobile Options notebook allows you to set up tracking of
wireless events and transfering of data between MobileCast and an onboard computer.
Click on the Handheld tab
Step 1: Check Generate Event Receipts to track all events that are sent between the
MobileCast server and a wireless device. If checked, the dispatcher will be able to
view when the event was received on the wireless device, when it was viewed by
the driver, when the driver acknowledged it, and, if applicable, when and why the
event was discarded.
The Onboard Integration section lets you specify how you want to transfer data between
MobileCast and the onboard computer. If you are using MobileCast with the Tripmaster
onboard computer, you have several ways of transferring data between the systems. One
108

of these options is to have the handheld device transfer data. If you use this option, you
must tell MobileCast the IP address and port of the computer where the server is running.
Step 2: In the Onboard Integration section, check Use Handheld For Load/Unload.
Then, enter the IP address and port of the server.
Setting the Telematics Mobile Options
The Telematics feature lets the Roadnet Transportation Suite receive information from a
supported GPS provider and send it to the MobileCast Server. Before you can start using
the Roadnet Telematics Adapter you must tell MobileCast when to start and stop looking
for data as well as who will be providing it.
The Telematics page of the Mobile Options notebook allows you to define settings for the
Roadnet Telematics Adapter. Click on the Telematics tab.
Note: You will also need to set options on the Auto Arrive/Depart tab.
Step 1: The General Settings area of the Telematics page lets you tell MobileCast when
to start and stop looking for data and define proxy settings, if you are using a proxy
server. Set the options as desired.
Operations Guide
109
Ignore Routes Older Thanallows you to specify the maximum number of days
that the adapter will continue looking for a route, after its planned start date. The
maximum number of days you can enter is 14.
Begin GPS Pollingallows you to specify the maximum length of time before
the planned start time that the adapter will start polling for GPS data. Enter the
time in hours and minutes.
Use Proxycheck if the information will need to go through a proxy server. Then
enter the appropriate information for each field.
Proxy URLEnter the proxy URL.
UsernameEnter the proxy authentication username.
PasswordEnter the proxy authentication password.
The Provider Settings area of the Telematics page allows you to define provider settings
that tell where the information is coming from and security settings that allow the adapter
and provider to interact.
Important: Some information within the Provider Settings area may not be required by
your service provider. A Roadnet Technologies consultant can help you determine
110

what information is necessary, based on your Provider Type. This information

should not be changed, once established, unless your GPS Provider changes.
Provider Typechoose the name of your GPS Provider from the list.
Cache Position Datacheck to have GPS data temporarily stored before it is
proccessed. It is recommended that this only be used if your GPS provider does
not allow you to retrieve data more than once or if your server is responding
slowly. Data is saved for two days.
Server URLEnter the GPS Providers server URL.
Note: Use the appropriate internet address for the Server URL setting:
Geotab: roadnettelematics.geotab.com
SkyPatrol: URL should be left blank.
PeopleNet: open.peoplenetonline.com
Vehicle Tracking Solution(VTS): URL should be left blank.
Database NameEnter the GPS Providers database name. This information is
given to you by your GPS provider.
UsernameEnter the username to use for authenticating on the GPS Providers
server. This information is given to you by your GPS provider.
PasswordEnter the password to use for authenticating on the GPS Providers
server. This information is given to you by your GPS provider.
API KeyEnter the API Key, if required by your GPS Provider. This information
is given to you by your GPS provider.
Operations Guide
111
Working with Statuses and Types

Used with: Roadnet, Territory Planner, FleetLoader, and MobileCast
The Maintenance module contains several different types and statuses that can be used to
follow and classify information about the routes that you are tracking. These types and
statuses set up the choices that you will be able to pick from when entering information
about employees, equipment, locations, stops, and routes. All statuses and types you
create are available to be used with all regions. See Adding Statuses and Types for
information on adding these items.
Note: Not all options will be available to all users; the available options depend on the
parts of the Roadnet Transportation Suite you have installed, as well as the user
permissions. You must have accounting permissions to work with driver types and
track types.
Account Types
Account types help you to group your locations by a common trait, such as a chain of fastfood restaurants or those locations that require COD payment. Account types are also a
method of grouping locations for reporting purposes, such as producing a Location
Delivery Cost report. In other words, account types are a flexible tool that can be used for
almost any purpose. When you add a location, you must assign an account type. See
Working with Account Types for more information.
Maintenance List Account Types
Bay Types
Bay types are used in the beverage industry to define the types of bays available on
equipment. FleetLoader uses bay type information when determining the amount of
product that can fit into a given bay. Because bay types are used only for determining the
amount of a package type that can be loaded into the bay, it is necessary to create types
only for bays with different capacities, although several bays of one type may have
slightly different dimensions. Bay types must be added before the equipment types can be
added. This options is only available if FleetLoader is loaded. See Working with Bay
Types for more information.
Maintenance List Equipment Bay Types
Compartment Types
Compartment types are used to define the types of compartments on a truck. Examples
of compartment types could be freezer or refrigerator. You can specify what product
types can be loaded into each compartment type and how many of each compartment
type are on each equipment type. If your compartments are sizable (have a movable
bulkhead), you can allow the Roadnet Transportation Suite to size the compartments for
optimal use of cargo space. You should only create compartments if you intend to use
compartment routing when creating routes.
Maintenance List Equipment Compartment Types
112

Delay Types
Delay types explain why a planned stop time was not met. Some examples of delay types
could be traffic, mechanical problems, or customer-related situations. You can assign
delay types in the Dispatcher when a route starts, when a route arrives at a stop, departs
from a stop, or when the route is completed. Any delay types you create are available for
all regions. Delay types, which are used for reporting purposes only, are only available if
MobileCast is loaded.
Maintenance List Dispatch Delay Types
Employee Status
Employee statuses allow you to classify employees according to criteria you define. You
can use the status to help determine which employees are available to assign to a route in
the Dispatcher. Some examples of employee statuses may include training or illness/
disability. Any employee statuses you create are available to all your regions. The
Transportation Suite comes with two pre-filled employee statuses: RDY (Ready) and
USE (In Use).
Maintenance List Employees Employee Statuses
Employee Types
Employee types allow you to classify the types of employees in your organization. Some
examples of employee types are driver, dispatcher, merchandiser, or helper. See Working
with Employee Types for more information. Employees can be associated with types
when they are added.
Maintenance List Employees Employee Types
Equipment Status
Equipment statuses allow you to specify the status of pieces of equipment, and search on
it when choosing equipment to view. Some examples of equipment status could be down
or ready. All equipment statuses you create are available for all regions. The Roadnet
Transportation Suite comes with two pre-filled equipment statuses: RDY (Ready) and
USE (In Use).
Maintenance List Equipment Equipment Statuses
Equipment Types
Equipment types define the types of equipment you use, such as whether you use straight
trucks or trailers, and the number of bays on a specific type of truck. You can define the
dimensions of a type of equipment, including weight, and specify its capacity. You can
also flag commercial vehicles to prevent them from being routed on restricted roads. In
addition, you can associate equipment types with locations, so that type will be used when
that location is routed. In the beverage industry, bay types must be entered before
equipment types can be entered if you are using FleetLoader. After equipment types are
completed, the individual pieces of equipment can be entered. See Working with
Equipment Types for more information.
Maintenance List Equipment Equipment Types
Operations Guide
113
Location Types
Location types allow you to specify the kinds of locations you have. Normally, the
location type is simply an ID and a description, and you can assign the types to your
locations to distinguish depots from customers from vendors, to separate departments in
a grocery store any number of uses. If you are using location types to differentiate
between various departments in a single store, such as a grocery store, you can have the
Roadnet Transportation Suite automatically synchronize selected fields for each type
when you add or edit a location; see the Location page of Setting the Defaults for more
information. If you are using the accounting portion of MobileCast, you can assign a track
type to a location type to differentiate between the cost of delivering to different types of
locations. The Roadnet Transportation Suite comes with two default location types:
depots (DPT) and sites (SIT), but you can add as many as needed.
Maintenance List Locations Location Types
Package Types
Package types define the various types of packages loaded on your equipment, such as 12ounce cans or 2-liter bottles. Package types are used to define the capacity of a pallet/bay,
or a layer on a pallet. Once package types and SKU brands have been entered, the SKUs
can be added. If you purchased FleetLoader, you must enter package types to determine
how your equipment will be loaded. You will use package types only if you have
purchased FleetLoader or if you intend to import SKU level detail in your order file. See
Working with Package Types for more information.
Maintenance List Product Package Types
Pallet Types
Pallet types are used in the beverage industry to define types of pallets available to use
when loading the equipment. Pallet types will only be used if you are using FleetLoader.
For each pallet type, you can specify loading details by defining the quantity of a package
type that can fit on a pallet layer and how many layers of the package can fit on the pallet
type. You can exclude certain pallet types from being loading into specific bay types and
equipment types. Pallet types must be created before you can use them to load your
beverage equipment. You can create as many pallet types as needed. See Working with
Pallet Types for more information.
Maintenance List Equipment Package Types
Product Types
Product types are assigned to SKUs and classify SKUs based on what compartment type
they can be loaded into. Some examples of product types could be frozen or refrigerated.
You will use product types only if you use compartment routing.
Maintenance List Product Product Types
Route Types
Route types give you a way to classify different types of loads the trucks carry. Some
examples of route types could be flammable or refrigerated. Any route types you create
are available for all regions. This option is only available if MobileCast is loaded.
114

Maintenance List Routes Route Types
Route Status
Route statuses can be used to classify routes according to urgency, stage of completion,
or some other criteria. Some examples of route statuses could include delayed or no status.
Route statuses are assigned to routes in the Dispatcher. All route statuses you create are
available to all regions. This option is only available if MobileCast is loaded.
Maintenance List Routes Route Status
Driver Types
Driver types allow you to categorize drivers and track pay rates by those categories. For
instance, you could have a driver type for senior drivers and another for new drivers, and
assign a pay rate to each type. Driver types are maintained in Maintenance, but since they
involve payroll information, you must have accounting permissions to work with driver
types.
Maintenance List Employees Driver Types
Track Types
Track types are used to hold accounting and operational information that can be combined
with data from specific routes to produce detailed accounting reports. Track types are
maintained in the Maintenance module, but since financial information is involved, you
must have accounting permissions to work with track types. This option is only available
if MobileCast is loaded and you have accounting permissions.
Maintenance List Dispatch Track Types
Operations Guide
115
Adding a Status or Type
Below are basic instructions for adding a status or type; some statuses and types have
additional fields which need to be entered. See the instructions for working with that
individual type for more information.
Step 2: Click on the List menu and select the desired type/status. The type/status
window opens listing the current types/statuses.
Note: To see an updated list of types/statuses click on the Refresh icon; the window will
be updated with all changed information from the database.
Step 3: To add a status or type, click the Add icon or press the [Insert] key. The Add
window opens.
Step 4: Complete the fields, as needed. The Type or Status field is required; the
Description is optional.
The Add Driver Type window is
a typical window used to add
statuses or types. Simply enter
a type and a description, then
click the Save icon.
Step 5: If the status/type has a color used to identify it, click on the arrow to open a
color palette and choose the desired color.
Step 6: Click on the Save icon, or press [Ctrl]+[S] to save the type or status.
Step 7: Click the Close box to close the window.
Maintenance List Status/Type Add ([Insert]) Save icon ([Ctrl]+[S])
Existing statuses and types can be edited or deleted as necessary. See Editing Items and
116

Working with Bay Types

Bay types are used in the beverage industry to define the types of bays available on
equipment. FleetLoader uses bay type information when determining the amount of
product that can fit into a given bay. Because bay types are used only for determining the
amount of a package type that can be loaded into the bay, it is necessary to create types
only for bays with different capacities, although several bays of one type may have
slightly different dimensions. Bay types must be added before the equipment types can be
added.
Note: Bay Type IDs Default 1, Default 2, Default 3, and Default 4 are reserved by the
Roadnet Transportation Suite and cannot be modified.
Step 1: Click on the Maintenance icon to open the Maintenance module.The
Step 2: Click on the List menu and select Equipment, then Bay Types. The Bay Types
window opens, listing any bay types that exist.
Note: To see an updated list of bay types, click on the Refresh icon; the window will be
updated with the most recent information from the database.
Step 3: In the Bay Types window, click on the Add icon or press [Insert]. The Add Bay
Type window opens.
entry.
Step 4: Enter up to 15 characters as the Bay Type ID. This field must be completed.
The bay type dimensions can

be in inches, feet, or
centimeters.
Step 5: Enter up to 30 characters as the Description.

Step 6: Enter the Height, Width, and Depth dimensions. These fields must be
completed.
Important: The dimensions must be entered in the same measurement as the package
type dimensions. For instance, both types must use either inches or feet or
centimeters.
Operations Guide
117
Step 7: To define the maximum number of each package type that can fit in the bay
type, click on the [Bay Capacities] button. The Bay Type Capacity Maintenance
window opens.
Using the Bay Type Capacity

Maintenance window, you can
enter the number of each package
type that can fit in the bay type, or
you can have the system calculate
the capacity for you. The default for
the Percent Utilized field is 85%.
To have the capacity automatically calculated, enter, in the Percent Utilized

field, the percent of the bay to be filled, and click on the [Calculate] button. The
default is 85 percent.
To manually enter the capacities, click on the Package Type ID to select it, and,
in the Units field, enter the maximum number of that package type that will fit in
the bay type. Click on the [Update] button. Continue until all capacities are
entered.
To specify the maximum number of different SKUs that can be loaded in that
type of bay, check Define Max and enter the number of SKUs allowed in the bay.
Note: The package types must be added before the bay type capacity can be entered.
Warning: Clicking the [Calculate] button will cause any existing capacities to be
overwritten with the calculated capacity.
Hint: To keep a specific package type from being loaded into a bay, make its capacity
0. Bays of that type will be skipped when loading that package type.
Step 8: Click the [OK] button to save the bay capacity information.
Step 9: To exclude specific pallet types from being loaded into this bay, click on the
[Pallet Types Allowed] button. The Pallet Types Allowed window opens.
To restrict the pallet type(s) from being loaded into the specific bay type, uncheck
the appropriate pallet type(s).
Note: By default, all pallet types are allowed.
118

Pallet types must already have been added to select this information.
Certain pallet types can be

restricted from loading into a
particular bay type. Pallet
types that are not checked are
not allowed to be loaded into
this particular bay type.
Step 10: Click the [OK] button to save the pallet types allowed information.
Step 11: Repeat Steps 4 10 to add any other bay types.
Step 12: Click the Save icon, or press [Ctrl]+[S] to save the new bay type.
Step 13: When you are finished adding bay types, click the Close box to close the Add
Bay Types window.
Maintenance icon List Equipment Bay TypesAdd icon ([Insert]) Save
icon ([Ctrl]+[S])
Existing bay types can be edited or deleted as necessary. See Editing Items and Deleting
Important: Deleting bay types affects other items in Maintenance. Before you delete bay
types, you should edit or delete equipment and equipment types with that bay type.
Operations Guide
119
Working with Compartment Types

Used with: Roadnet
If you are going to use compartment routing, you need to create compartment types and
specify which product type(s) can be loaded in each compartment type. You are able to
select whether SKUs of different product types can be mixed in a compartment type and
whether or not a compartment type is sizable (has a movable bulkhead).
Once you have created compartment types, you must add compartments to equipment
types to indicate what compartments each equipment type contains. When adding
compartments to equipment types you will be able to specify the size, or range of possible
sizes (if the compartment is sizable), of each compartment.
Step 2: Click on the List menu and select Equipment, then Compartment Types. The
Compartment Types window opens.
Step 3: In the Compartment Types window, click the Add icon or press [Insert]. The
Add Compartment Type window opens.
Step 4: Enter up to 15 characters as the Type.
You select whether or not
multiple product types can
be mixed in the
compartment type. If you
do not select Mixable, only
SKUs of one of the allowed
product types will be
loaded into that
compartment type.

Step 6: If different product types can occupy the compartment simultaneously, check
Mixable. If this box is not checked, only SKUs of the same product type will be
allowed to be loaded into the compartment.
Note: If you have compartments that are sizable (have a movable bulkhead), you can set
the minimum and maximum size that each compartment can be sized to when
adding compartments to an equipment type.
Step 7: To specify which product type(s) can be loaded into the compartment, click the
Add icon or press [Insert] in the Product Types box. The Lookup - Product Type
window opens. Double-click on an item to select it, or click on the item and then
on the Process icon.
120

Step 8: Repeat Step 7 to add any other product types.

Step 9: Click the Save icon, or press [Ctrl]+[S] to save the new compartment type.
Step 10: When you are finished adding compartment types, click the Close box to close
the Add Compartment Type window.
Maintenance icon List Equipment Compartment TypesAdd icon ([Insert]) Save
icon ([Ctrl]+[S])
Existing compartment types can be edited or deleted as necessary. See Editing Items and
Operations Guide
121
Working with Equipment Types

Equipment types define the types of equipment you use, such as whether you use straight
trucks or trailers, and the number of bays on a specific type of truck. You can define the
dimensions of a type of equipment, including weight, and specify its capacity. You can
designate for each equipment type whether or not they are considered a commercial
vehicle restricted from certain attributes of a street. In addition, you can associate
equipment types with locations, so that type will be used when that location is routed. If
you use compartment routing, you will specify how many of each compartment type are
on each equipment type. In Territory Planner, you have the option of creating territories
proportional to the equipment type you will be using. In the beverage industry, bay types
must be entered before equipment types can be entered if you are using FleetLoader. After
equipment types are completed, the individual pieces of equipment can be entered.
You can add equipment types individually or import them; see Importing Maintenance
Items for more information on importing equipment types.
Step 2: Click on the List menu and select Equipment, then Equipment Types. The
Equipment Types window opens. The current list of equipment types will not
appear. This makes the system run much faster than if the complete list were
loaded every time. To see the current list of equipment types, or just specific
equipment types, use the Search feature.
Note: To see an updated list of equipment types, click on the Refresh icon; the window
will be updated with the most recent information from the database.
Step 3: In the Equipment Types window, click on the Add icon or press [Insert]. The
Add Equipment Type window opens.
entry.
Step 4: Enter up to 15 characters as the Equipment Type ID. This field must be
completed.
Step 6: Enter the Weight and Height information, if desired.
Step 7: If you want to track the carbon emissions for your routes, enter the Carbon
Factor and Avg Fuel Consumption. Enter the Avg Fuel Consumption in miles per
gallon (MPG).
Notes: If you are going to calculate your carbon emissions using Grams per Kilometer,
you do not need to enter the fuel consumption. If you are using Pounds per Gallon,
both pieces of information must be entered. The CO2 Computation Method is
selected on the Unit Reference page of the Maintenance Options notebook.
122

The Average Fuel Consumption must always be entered in miles per gallon
(MPG), regardless of the Unit System selected on the Unit Reference page of the
Step 8: If the type is a trailer or other cargo unit, enter your total truck capacity as Size
1, Size 2, or Size 3 in the Size fields.
If you are using Roadnet, you can enter the capacity for the categories for each size
as well.
Step 9: If you are using MobileCast, check Carries a load to indicate that the capacity
of the equipment should be tracked as the route is run. If this type of equipment
contains a motor (ex. a tractor), check Power Unit. If equipment must be assigned
to a route before it can be started, it means that a type designated as a power unit
must be assigned to the route.
Step 10: Enter cost information if desired (fixed, variable). This information is needed
to accurately calculate route costs.
Fixed costsaccrue independently of miles driven, such as lease or purchase
price, insurance, depreciation, license fees, and highway use tax.
Variable costsare affected by the distance driven, such as fuel, oil, tires and
tubes, and repairs and replacement parts.
This example shows a 45-foot

trailer added as equipment
type 126. The trucks capacity
for three size measurements is
added in the box at the bottom
right.
Step 11: Check Prohibited from Time of Day Restricted Areas and Paths to prevent this
type of equipment from traveling on selected roads during specified times of the
day. If this option is selected, equipment of this type will not be routed on any
street segment that has a time of day restriction.
Operations Guide
123
Step 12: To prevent this type of equipment from being routed on height and weight
restricted roads, check Prohibited from Height-Weight Restricted Roads. If this
option is selected, equipment of this type will not be routed on any street segment
that has a height limit that is less than the Height Restriction or a weight limit that
is less than the Weight Restriction. The Height Restriction and Weight
Restriction are specified on the General page of the Maintenance Options
notebook.
Note: This option is only applied when routing with SuperMatrix and RouteNet; it does
not apply to shortest route or XY.
Step 13: To prevent this type of equipment from being routed on commercial roads,
check Prohibited from Commercially Restricted Roads. If this option is selected,
equipment of this type will not be routed on any street segment that is marked as
commercially restricted. The Commercial Restriction is marked on the Edit
Street Attributes window; see Editing the Network for more information.
Step 14: Check the Adjust Equipment Types Travel Time By box if the travel time will
be longer or shorter than normal when the assigned equipment type is used.
Indicate whether you will be traveling longer or shorter and enter the percentage
difference. For example, smaller vehicles often have greater maneuverability and
fewer restrictions than larger ones, so you would select Longer if you were using
that equipment type.
Step 15: If you are using compartment routing, see Adding Compartments to an
Equipment Type.
If you have purchased FleetLoader, see Equipment Types and FleetLoader.
If you are finished entering information for the equipment type, click the Save
icon or press [Ctrl]+[S] to save the equipment type.
Step 16: Repeat Steps 4 15 to add any other equipment types.
Step 17: When you are finished adding equipment types, click the Close box to close
the Add Equipment Type window.
Maintenance icon List Equipment Equipment TypeAdd icon ([Insert])
Existing equipment types can be edited or deleted as necessary. See Editing Items and
Important: Deleting equipment types affects other maintenance items. Before you delete
equipment types, you should delete equipment with that equipment type.
Adding Compartments to an Equipment Type
The Compartments page lets you specify information about the compartments that are
present on the equipment type. You only need to use this page if you intend to use
compartment routing when creating your routes.
124

Click on the Compartments tab to begin entering compartment information. You must
have created compartment types and entered the equipment type before starting this procedure.
Step 1: On the Compartments page, click on the Add icon or press [Insert]. The Add
Compartment window opens.
Step 2: To select the compartment type of the compartment you are adding, click on the
Compartment Type arrow to open the Lookup - Compartment Type window.
Double-click on an item to select it, or click on the item and then on the Process
icon.
Step 3: Enter up to 15 characters as the Compartment ID.
Step 4: Click on the Color arrow and select a color for the compartment. Once you
build routes, graphs that use the color code selected here will show how full each
compartment is.
Step 5: In the Minimum % of Equipment Type field, enter the smallest size the
compartment can be, measured as a percent of the equipment types total
capacity.
Step 6: In the Maximum % of Equipment Type field, enter the largest size the
compartment can be, measured as a percent of the equipment types total
capacity.
For each compartment that you

add to an equipment type, you
enter the minimum and maximum
percent of the equipment types
total capacity the compartment
can consume.
Note: If the compartment is not sizable (does not have a movable bulkhead), the
Minimum % of Equipment Type and Maximum % of Equipment Type should be
the same.
Step 7: In the Number of Bulkhead Positions field, enter the number of different places
the bulkhead can be set to. If the compartment is not sizable, enter 0 or 1.
Note: Roadnet only allows resizeable compartments to be sized in equal increments. For
example, if a compartment can consume from 20 to 65 percent of the equipment
types capacity and it has 4 possible bulkhead positions, the compartment will be
allowed to be sized in increments of 15 percent of the equipment types capacity;
it will be allowed to consume 20, 35, 50, or 65 percent of the equipments
capacity.
Operations Guide
125
Step 8: Click the Save icon, or press [Ctrl]+[S] to save the information about the
compartment.
Step 9: Repeat Steps 2 8 to add any other compartments.
Step 10: Click on the Close box when you have added all compartments. The Add
Compartment window closes.
Step 11: If you have purchased FleetLoader and need to enter bay information for the
equipment type, see Equipment Types and FleetLoader. If you are finished
entering information for the equipment type, click the Save icon or press
[Ctrl]+[S] to save the new equipment type.
Equipment Types and FleetLoader
The FleetLoader tab, which will only appear if you have purchased FleetLoader, lets you
specify information about the location and number of bays on the equipment.
If you are using FleetLoader to load your trucks, you can specify information about the
equipment type, such as bay information, by clicking on the FleetLoader tab. You must
have entered the equipment type before starting this procedure.
Step 1: Click the FleetLoader tab on the Add Equipment Type window.
126

Step 2: Select whether the equipment is a side loader or a bulk truck. If the equipment
uses a trailer, verify that a check is present in the Trailer box. Enter the number of
rear axles in the Rear Axles field.
The FleetLoader tab on the Add Equipment Type window lets users who have
purchased FleetLoader specify the truck body type (side loader or bulk) and number
of axles, and to specify where the bays are located on the truck.
Step 3: To exclude certain pallet types from specific equipment types, click on the
[Pallet Types Allowed] button. The Pallet Types Allowed window opens.
To restrict the pallet type(s) from being loaded into the specific equipment type,
uncheck the appropriate pallet type(s).
Note: By default, all pallet types are allowed.
Step 4: Click the [OK] button to save the information.
Step 5: If the equipment is a side loader, select Side Loader and enter the number of
bays in each category in the Driver Side Bay Info area. If the equipment includes
a rear bay that can be accessed only from the rear of the truck, verify that a check
is present in the Rear Bay box.
Step 6: If the equipment is a bulk truck, select Bulk.
To specify the dimensions of the bulk equipment type, enter the Width and the
Depth. The width is measured from the driver side to the passenger side and the
depth is measured from the front of the truck to the back of the truck.
To specify the minimum free space within rows when the equipment is
loaded, enter the Minimum total empty width within row.
Operations Guide
127
To specify the minimum free space between rows when the equipment is
loaded, enter the Fixed empty depth between rows of pallets.
Important: The dimensions must be entered in the same measurement as the pallet type
dimensions. For instance, both types must use feet.
Note: If the truck is a bulk truck, the Driver Side Bay Info is not applicable, although it
may appear in the Equipment Types list.
Step 7: To specify the bay types for each bay, click on the [Define Bays] button. The
Define Bays window opens.
To split a bay, right-click on the bay and select Split from the menu that pops up.
A horizontal line appears across the bay; use the mouse to move the line to the
correct position to split the bay. Click to anchor the line.
To assign a type to a bay, double click on the bay; the Define Attributes window
opens. If the bay has a shelf that can be engaged to form an upper and lower bay
when needed, check Convertible Bay. Edit the Bay Number and Description if
desired, and select the proper bay type for the bay; if the bay is a convertible bay,
you can make these changes for each part of the bay. Click on the [OK] button
when all the information is correct.
To change the ID or Description for the bay, type the new information in the
field.
You can define each bay on a side loader by double-clicking on it,

specify the bay number, type, and description for each bay, and use
the Define Bays screen to split bays.
Step 8: Click on the [OK] button when all the bays are defined. The Define Bays
window closes.
Step 9: If you are using compartment routing and need to add compartments, see
Adding Compartments to an Equipment Type. If you are finished entering
information for the equipment type, click the Save icon or press [Ctrl]+[S] to
save the new equipment type.
128

Sharing Resources
Sharing Resources
Some resources within the Roadnet Transportation Suite can be shared among your
regions. Employees (drivers) and equipment that are added for one region can be assigned
to routes in other regions if they are created as shared resources in the Maintenance
module. You can even determine which regions will be allowed to use the shared
resource(s). This feature allows you to draw from a larger pool when assigning resources
to routes.
Employees and equipment can be shared among your regions

within the Roadnet Transportation Suite, which greatly increases
your available resources. At the bottom of the Add window, simply
choose the region(s) you will share the resource with.
When viewing lists of employees or equipment, those resources that were created in
another region and shared to your region will be displayed in red. You can review the
resources information, but can not update it.
To make a resource available to a region, click on that region in the Shared by Regions
list to highlight it. You can select more than one region by holding down the [Ctrl] key as
you click.
To make a resource no longer available to a specific region(s), simply hold down the
[Ctrl] key and click on the highlighted region(s) in the Shared by Regions list to deselect
it. The resource will still be available to the other highlighted regions.
For more information on how to share employees and equipment, see Working with
Employees or Working with Equipment for more information.
Operations Guide
129
Working with Equipment

Equipment generally refers to the trucks used to deliver product; however, a piece of
equipment can be anything used in a delivery. Before equipment can be added, the
equipment types must be added. You can add equipment individually or import it; see
Importing Maintenance Items for more information on importing equipment.
Step 2: Click on the List menu and select Equipment, then Equipment. The current list
of equipment will not appear. This makes the system run much faster than if the
complete list were loaded every time. To see the current list of equipment, or just
specific pieces of equipment, use the Search feature.
Notes: To see an updated list of equipment, click on the Refresh icon; the window will be
Equipment displayed in red are shared by another region; you can assign them to
routes and view their information but you cannot modify their information.
Step 3: In the Equipment window, click on the Add icon or press [Insert]. The Add
Equipment window opens.
entry.
You could assign a preferred

driver to this straight truck,
which could be automatically
assigned to the route with the
equipment in the Routing Editor.
Step 4: Enter up to 20 characters as the Equipment ID. This field must be completed.
130


Step 6: Click on the Equipment Type ID arrow to open the Lookup - Equipment Type
window. Double-click on an item to select it, or click on the item and then on the
Process icon. You must select an equipment type.
Step 7: If you are using Roadnet, assign a preferred driver, and buddy equipment if
desired. Click on the appropriate arrow to open the Lookup window. Doubleclick on an item to select it, or click once and then click on the Process icon. If
selecting buddy equipment, use the Search feature to find the equipment you are
looking for. Once the equipment appears in the list, double-click on it, or click on
a piece of equipment and then on the Process icon, to select it.
Note: If you select a preferred driver and then choose to assign a piece of equipment to
a route in the Routing Editor, the preferred driver may be assigned to the route
automatically (but can be changed).
Step 8: Enter a status for the equipment. If you are using MobileCast this field must be
completed.
Step 9: Enter the date the equipment needs to be inspected in the Inspection Date field.
Step 10: If the equipment can be used by another region, select the region(s) in the
Shared by Regions box. To select more than one region, select the first region and
then press and hold the [Ctrl] key while selecting the others.
Note: To make equipment no longer available to a specific region(s), simply hold down
the [Ctrl] key and click on the highlighted region(s) in the Shared by Regions list
to deselect it. The equipment will still be available to the other highlighted regions.
Step 11: Select an ownership status for the equipment. If the equipment is owned by the
region, select Dedicated. If the equipment is a substitute for another piece of
equipment, select Substitute. If the equipment is rented, select Rental.
Step 12: Click the Save icon, or press [Ctrl]+[S] to save the information about the
equipment.
If you are using FleetLoader, see Equipment Preferences and FleetLoader.
If you are using MobileCast, see Equipment and MobileCast.
Step 13: Repeat Steps 4 11 to add any other equipment.
Step 14: When you are finished adding equipment, click the Close box to close the Add
Equipment window.
Maintenance icon List Equipment Equipment Add icon ([Insert]) Save
icon ([Ctrl]+[S])
Existing equipment can be edited or deleted as necessary. See Editing Items and Deleting
Important: Deleting equipment affects other maintenance items. Before you delete
equipment, you should edit or delete drivers with that preferred equipment.
Operations Guide
131
Equipment Preferences and FleetLoader
If you have purchased FleetLoader and would like to define the equipment preferences
(how product is loaded in the bays) for the piece of equipment, click [Define Bay
Preferences] on the Add or Edit Equipment window. The Define Bay Preferences window
opens.
Step 1: Double-click on a bay to specify the preferences for that bay; the Bay Preference
Maintenance notebook opens.
Step 2: Click the Global tab. The Global page opens. .
You can establish the

loading preferences for
the individual bays in
the Bay Preference
Maintenance notebook.
To keep any product from being loaded into the bay, such as to reserve the bay
for pickups, click on the Disable Bay box.
To have only SKUs with small quantities loaded into the bay, click on the
Small SKU bay box.
To choose the strategy that should be used when the bay is loaded in the
Loading Editor, click the Loading Strategy arrow. The bay will only be
considered for loading when this strategy is being used. For instance, if the truck
is being loaded Warehouse Friendly but the bays loading strategy is Driver
Friendly Only, the bay will not be loaded.
Step 3: If you want to set up package type preferences, click on the Package Types tab
to open the Package Types page. The Package Type page contains a list of
Available Package Types.
To make a package type preferred, click on the type and drag it to the Preferred
Package Types list. Drag the types within the list until they are in the proper order.
Note: Package types are assigned preference according to their order in the Preferred
Package Types list. The package type that appears first in the list will be loaded
132

first. To change the order of the package types, click and drag the package type you
want to move and drop it on the package type you want it to appear after. If you
want the package type to be first on the list, drop it on the column header labeled
Package Type ID.
Package types LX52, LX53,

LX54, LX56, and LX58 are the
preferred types for this bay, and
FleetLoader will load them into
this bay before other bays.
Step 4: If you want to set up SKU preferences, click on the SKUs tab to open the SKUs
page. The SKUs page of the Bay Preference Maintenance notebook contains a
list of Available SKU IDs.
Operations Guide
133
To make a SKU preferred, click on the ID and drag it to the Preferred SKUs list.
Drag the SKUs within the list until they are in the proper order.
SKUs L2594, L2694, and L3202

are the preferred SKUs for this
bay, and FleetLoader will load
them into this bay before other
bays.
Note: SKUs are assigned preference according to their order in the Preferred SKUs list.
The SKU ID that appears first in the list will be loaded first. To change the order
of the SKUs, click and drag the SKU ID you want to move and drop it on the SKU
ID you want it to appear after. If you want the SKU ID to be first on the list, drop
it on the column header labeled SKU ID.
Step 5: When you have finished setting your bay preferences, click [OK] to apply your
selections and close the Bay Preference Maintenance notebook.
Step 6: Continue defining the preferences for each bay. When all the bay preferences
have been defined, click on the [OK] button to close the Define Bay Preferences
window.
Step 7: Click on the Save icon, or press [Ctrl]+[S] to save the information about the
equipment.
Step 8: When you are finished adding equipment, click the Close box to close the Add
Equipment window.
Equipment and MobileCast
If you are using MobileCast to track your routes as they are run, there is additional
information about the equipment you should complete, such as any wireless devices or
onboard computers associated with the equipment.
134

Step 1: If you are using MobileCast, click on the Dispatch tab on the Equipment window.
You can add additional information about the equipment, such as wireless
devices.
Step 2: If you are using an external GPS device, enter the GPS Unit ID. MobileCast
uses this ID to associate the piece of equipment with a specific route.
Step 3: If the equipment carries an onboard computer, check the On Board Computer
box.
Step 4: If a wireless device is assigned to the equipment, select the provider and the ID.
Note: If you are using newer versions of the mobile application, where the driver logs
into the device, you do not need to assign a wireless device to the equipment.
Step 5: Enter the location where the equipment will start routes from, such as the depot.
Click on the arrow next to the Type field to choose a type and enter the ID or
search for the location. To add a new location, click on the [New] button. This
field must be completed.
Note: If you use MobileCast Dispatcher, it is recommended that you specify your
Location ID and Location Type.
Step 6: To manually reposition equipment at a drop off location, enter the drop off date
and time in the Dropped Off fields.
Operations Guide
135
Working with Equipment Overrides

Equipment is normally assigned to the route before the truck is loaded, but there may be
times when you need to make a last minute change to the assigned equipment. If this
happens, you can create an equipment override for that trucks route. The override
equipment will be used for all instances of the route in FleetLoader until it is deleted.
Step 2: Click on the List menu and select Equipment, then Equipment Overrides. The
Equipment Overrides window opens, listing any existing overrides.
Note: To see an updated list of equipment overrides, click on the Refresh icon; the
window will be updated with the most recent information from the database.
Step 3: In the Equipment Overrides window, click the Add icon or press [Insert]. The
Add Equipment Override window opens.
entry.
Step 4: Enter the Route ID. This field must be completed.
You can give the route a new

description when you enter an
equipment override.
Step 5: Click on the Equipment Type : Equipment : Description arrow to choose the
equipment that you want to use for the entered route ID; the Lookup-Equipment
window opens. Use the Search feature to find the equipment you are looking for.
Once the equipment appears in the list, double-click on it, or click on a piece of
equipment and then on the Process icon, to select it.
Step 6: If desired, enter a new description for the route in the Route Description field.
Step 7: Click on the Save icon, or press [Ctrl]+[S] to save the equipment override.
Step 8: Click the Close box to close the Add Equipment Override window when all
overrides have been entered.
Maintenance icon List Equipment Equipment OverrideAdd icon ([Insert])
136

Existing equipment overrides can be edited or deleted as necessary. See Editing Items and
Operations Guide
137
Working with Warehouse Zones

Warehouse zones let you organize your SKUs into different areas in your warehouse, and
then specify the order in which the zones should be loaded onto the pallets. For instance,
you could create a warehouse zone, A, for cases of 12 ounce cans of RN Cola, and another
zone, B, that contains single bottles of less popular items. Then, you could specify that the
items in zone A are loaded on the pallet before items from zone B. Once the warehouse
zones have been established, you can specify which zone each SKU is in. Before you can
set up your warehouse zone you need to create the warehouse zone pick order methods.
Step 2: Click on the List menu and select Product, then Warehouse Zones. The
Warehouse Zones window opens, listing all established warehouse zones.
Note: To see an updated list of warehouse zones, click on the Refresh icon; the window
Step 3: In the Warehouse Zone window, click on the Add icon or press [Insert]. The
Add Warehouse Zone window opens.
The Add Warehouse Zone window is a

typical window used to add warehouse
zones. Simply enter an ID and a
description, then click the Save icon.
entry.
Step 4: Enter the Warehouse Zone ID and Description; the ID is required.
Step 6: Repeat Steps 4 through 6 to add any other warehouse zones.
Step 7: When you are finished adding warehouse zones, click the Close box to close the
Add Warehouse Zones window.
Once the warehouse zones have been added, you can choose the order that they should be
picked.
138

Step 8: On the Warehouse zones window, click the Change the Pick Order icon. The
Edit Warehouse Zone Pick Order window opens.
The order the warehouse zones are

listed in the window is the order they
will be picked in the Loading Editor.
Step 9: Click the Pick Order Method arrow and select the method you are creating the
pick order for.
Step 10: In the Pick Order list, drag and drop the zones until they are in the proper
order.
Step 11: Click the Save icon, or press [Ctrl]+[S] to save the warehouse zone pick order.
Step 12: When you are done, click the Close box to close the Edit Warehouse Zone
Pick Order window.
Existing warehouse zones can be edited or deleted as necessary. See Editing Items and
Hint: If you want to use the Pick Order selected here when loading in FleetLoader, you
must select Warehouse Zones as the Loading Order.
Maintenance icon List Product Warehouse ZoneAdd icon ([Insert]) Save icon
([Ctrl]+[S])
Operations Guide
139

Used with: Roadnet, FleetLoader
SKU brands are the brand names of the various products delivered, such as RN Cola or
RN Lite. You will use SKU brands only if you have purchased FleetLoader or if you
intend to import SKU level detail in your order file. See Importing Orders for more
information. You can add SKU brands individually or import them; see Importing
Maintenance Items for more information on importing SKU brands.
Step 2: Click on the List menu and select Product, then SKU Brands. The SKU Brands
window opens, listing all established SKU brands.
Note: To see an updated list of SKU brands, click on the Refresh icon; the window will
be updated with the most recent information from the database.
Step 3: In the SKU Brands window, click the Add icon or press [Insert]. The Add SKU
Brand window opens.
entry.
The ID must be completed

for each SKU brand.
Step 4: Enter up to 15 characters as the ID. This field must be completed.

Step 6: Click on the Save icon, or press [Ctrl]+[S] to save the SKU brand.
Step 7: Repeat Steps 4 6 to add any other SKU brands.
Step 8: When you are finished adding SKU brands, click the Close box to close the
Add SKU Brand window.
Maintenance icon List Product SKU BrandsAdd icon ([Insert]) Save
icon ([Ctrl]+[S])
Existing SKU brands can be edited or deleted as necessary. See Editing Items and
Important: Deleting a SKU brand affects other maintenance items. Before you delete a
SKU brand, you should delete SKUs with that SKU brand.
140

Working with Package Types

Package types define the various types of packages loaded on your equipment, such as 12ounce cans or 2-liter bottles. Package types are used to define the capacity of a pallet, or
a layer on a pallet. Once package types and SKU brands have been entered, the SKUs can
be added. If you purchased FleetLoader, you must enter package types to determine how
your equipment will be loaded. You will use package types only if you have purchased
FleetLoader or if you intend to import SKU level detail in your order file. Package types
can be added individually or imported; see Importing Maintenance Items for more
information on importing package types.
Step 2: Click on the List menu and select Product, then Package Types. The Package
Types window opens, listing all established package types.
Notes: To select which pallet loading information is displayed in the Package Types
window, click the Pallet Loading Method for Display arrow at the bottom of the
window and choose a loading method. Then click the Pallet Type for Display
arrow and choose the pallet type. The Quantity Per Layer, Layers Per Pallet, and
Quantity Per Pallet columns will show the information for the selected method.
To see an updated list of package types, click on the Refresh icon; the window will
Step 3: In the Package Type window, click on the Add icon or press [Insert]. The Add
Package Type window opens.
entry.
Step 6: If you want to have a picture of the package type associated with it in
FleetLoader, enter the path where the image is located in the Bitmap field. If no
image is specified here, the default image will be used in the editor.
Note: The image must be a.bmp file that is 28x28 pixels and 256 colors or fewer.
Step 7: In the Package Type Properties area, enter the height, width, and depth of the
type.
Note: The dimensions must be entered in the same measurement as the equipment type
dimensions. For instance, both types must use feet.
Step 8: If you are using equivalencies to relate different types of package types to each
other, enter the equivalency factor for this type in the Equivalency field.
Operations Guide
141
Hint: You can use equivalencies to level the field when calculating service time,
capacity, or cost, between different package types. For instance, if a pallet takes
up six times as much space in the truck as a case, you could enter the equivalency
for the case as 1 and the equivalency for the pallet as 6. Then, when the Routing
Editor is determining how much product can be loaded on the truck, it will
consider the difference in the sizes.
For each package type, you can

define the capacities for a pallet
and a bay.
Important: The dimensions must be entered in the same measurement as the bay type
dimensions. For instance, both types must use either inches or feet or centimeters.
When the equipment is loaded, these dimensions are used to calculate the volume
of each SKU.
Step 9: To define the loading details for each combination of loading and pallet type,
click on the [Pallet Capacities] button. To enter the information, select the
loading method and pallet type from the list below. After you have entered the
loading detail, click the [Update] button to update the loading information for the
method.
Quantity Per Layerthe amount of the package type needed to create a full
pallet layer.
Layers Per Palletthe number of layers of this package type that can be stacked
on a pallet.
Quantity Per Palletthe total quantity of package types that can fit on this pallet
type.
To specify how many package types can fit on each pallet type, enter the
Quantity Per Layer, Layers Per Pallet, and Quantity Per Pallet.
OR
To specify just the amount of package type needed to create a full pallet layer
and the number of layers of this package type that can be stacked on a pallet,
enter the Quantity Per Layer and Layers Per Pallet. Click the [Calculate] button to
have the Quantity Per Pallet automatically calculated.
142

OR
To specify only the total quantity of packages that can fit on this pallet type,
enter the Quantity Per Pallet.
The Edit Loading Details window allows you to specify

the pallet capacities.
Note: You must have created the Pallet Loading methods before this information can be
completed.
Step 10: To define the amount of each package type that can fit into a bay type, click on
the [Bay Capacities] button. The Bay Type Capacity Maintenance window opens.
Note: The bay types must be added before the bay type capacities can be entered.
Operations Guide
143
To have the capacity automatically calculated, enter the percent of the bay to
be filled and click on the [Calculate] button. Click on the [OK] button to accept
the calculated capacities.
In this window you can
specify how many of a
particular package type
will fit in the bays of your
truck. You can also ask the
system to calculate the
capacity for you, but you
must enter the dimensions
for your bay types and
package types first.
To manually enter the capacities, click on the Bay Type ID to select it, and enter
the maximum number of the package type that will fit in that bay type. Click on
the [Update] button. Continue until all capacities are entered. Click on the [OK]
button.
This information is only used if you are using FleetLoader and loading bay trucks.
Warning: Clicking the [Calculate] button will cause any existing capacities to be
overwritten with the calculated capacity.
Hint: To prevent a specific package type from being loaded into a bay type, make its
capacity 0. FleetLoader will skip all bays of that type when loading that package
type.
Step 11: Click the [OK] button. Then click on the Save icon, or press [Ctrl]+[S] to save
the new package type.
Step 12: Repeat Steps 4 11 to add any other package types.
Step 13: When you are finished adding package types, click the Close box to close the
Add Package Type window.
Maintenance icon List Product Package TypeAdd icon ([Insert]) Save
icon ([Ctrl]+[S])
Existing package types can be edited or deleted as necessary. See Editing Items and
144

Important: Deleting a package type affects other maintenance items. Before you delete
a package type, you should do the following:
delete SKUs with that package type.
verify the accuracy of bay type capacities.
verify the accuracy of equipment preferences.
Operations Guide
145
Working with Product Types
Working with Product Types

Used with: Roadnet
If you are going to use compartment routing, you need to create product types. Product
types are assigned to SKUs and determine what compartment type(s) a SKU is allowed
to be loaded into. When you create compartment types you will be able to select which
product types can be loaded into each compartment type. You can add product types
individually or import them; see Importing Maintenance Items for more information on
importing product types.
Step 2: Click on the List menu and select Product, then Product Types. The Product
Types window opens.
Step 3: In the Product Types window, click the Add icon or press [Insert]. The Add
Product Type window opens.
Product types allow you to
categorize SKUs based on
what compartment(s) they
can be loaded into.
Step 4: Enter up to 3 characters as the Type.

Step 6: Click on the Save icon, or press [Ctrl]+[S] to save the new product type.
Step 7: Repeat Steps 3 6 to add any other product types.
Step 8: When you are finished adding equipment types, click the Close box to close the
Add Product Type window.
Maintenance icon List Product Product TypesAdd icon ([Insert]) Save icon
([Ctrl]+[S])
Existing product types can be edited or deleted as necessary. See Editing Items and
146

Working with SKUs
Working with SKUs

SKUs are the most specific way to define your products. A SKU is composed of a SKU
brand and a package type, such as 12-ounce cans of RN Lite or 2-liter bottles of RN Cola.
SKU brands and package types must be entered before SKUs can be added. You will use
SKUs only if you have purchased FleetLoader or if you intend to import SKU level detail
in your order file. You can add SKUs individually or import them; see Importing
Maintenance Items for more information on importing SKUs.
If your orders contain line items, you can establish service times for each SKU, giving
you more accurate service times when routing. For instance, you can specify that it takes
longer to deliver a keg than a case of 12 ounce cans, and the service time calculated for
the order will reflect this difference, instead of basing all of the variable service time on
one size. Some additional things to consider if you are using SKU service time:
Any service time for the SKU will be added to the service time established for the
stop.
If you only want to use SKU service time to calculate the variable service time, make
sure the locations variable service time is set to 0.
Fixed service time will be the locations fixed service time.
If you do not want to include the SKU service time for bulk orders, check Ignore
SKU Service Time for Bulk on the Unit Reference page of the Options notebook. If
this option is not checked, the SKU service time will be added to the bulk service
time.
Step 2: Click on the List menu and select Product, then SKUs. The SKUs window
opens, listing all established SKUs.
Note: To see an updated list of SKUs, click on the Refresh icon; the window will be
Step 3: In the SKUs window, click the Add icon or press [Insert]. The Add SKU
window opens.
entry.
Step 6: Assign a package type and brand ID to the SKU. Click on the appropriate arrow
to open the Lookup window. Double-click on the proper ID to select it, or click
once and then click the Process icon. Both fields are required.
Operations Guide
147
Working with SKUs
Step 7: To assign a product type to the SKU, click on the Product Type arrow to open
the Lookup - Product Type window. Double-click on an item to select it, or click
on the item and then on the Process icon. You only need to assign a product type
to your SKUs if you are going to use compartment routing.
Step 8: If the SKU is delivered to the warehouse on a specific pallet, and then stored on
that pallet, you can specify that as the manufacturer pallet type for the SKU. To
specify a manufacturer pallet type for the SKU, click on the Manufacturer Pallet
Type arrow and select the appropriate pallet type. In the Minimum Percent of
Manufacturer Pallet field, enter the minimum amount the manufacturer pallet
type must be filled with that SKU in order for that particular pallet type to be
used. If you specify a manufacturer pallet type and a location will accept
manufacturer pallet types and receives an order that fills a manufacturer pallet
type, then FleetLoader will use the manufacturer pallet type when loading the
equipment if the equipment will accept it.
Step 9: To display an image of the SKU in FleetLoader, enter the path to the image. If a
path is not entered here, the icon associated with the package type will be
displayed in the Loading Editor.
Important: The image must be a.bmp file that is 28x28 pixels and 256 colors or fewer.
Step 10: Check Unload First if the item must be handled first, such as waste that needs
to be removed from a container before anything else is done with the container.
Step 11: In the Warehouse Properties area, complete the information as desired to
indicate where product is stored in the warehouse. This information is optional.
Click the Warehouse Zone arrow; the Lookup - Warehouse Zone window opens.
Double-click on a zone, or click on a zone and then the process icon, to select it.
The warehouse zone can dictate how the SKU is loaded on a pallet; this
information appears on the Pallet Pick Sheet and Pick List.
148

Working with SKUs
Enter the warehouse information in the Primary Zone and Secondary Zone fields.
This optional information will appear on the Pick List.
Before you add SKUs you

must add the package
type and SKU brand.
Step 12: To set up service times for the SKU, enter the times in the Variable Service
Time Properties area. You can enter separate times for each size alias, and the
service time will be calculated based on the quantity for each size entered for the
line item on the order. In other words, if you specify a quantity for each size in
the line item, the times for each size will be calculated and then added together to
determine the total service time for the line item.
Step 13: Click on the Save icon, or press [Ctrl]+[S] to save the new SKU.
Step 14: Repeat Steps 4 12 to add any other SKUs.
Step 15: When you are finished adding SKUs, click the Close box to close the Add
SKU window.
Maintenance icon List Product SKUsAdd icon ([Insert]) Save icon
([Ctrl]+[S])
Existing SKUs can be edited or deleted as necessary. See Editing Items and Deleting
Operations Guide
149
Working with SKUs
Note: To quickly change the service time or warehouse zone for a group of SKUs, use
the Replace feature. To replace information, simply select the SKUs you want to
change, right-click on a selected SKU and choose Replace from the menu that
pops up. Check Manufacturer Pallet Type (to change pallet type information) or
Warehouse Properties (to change warehouse location information) or Variable
Service Time Properties (to change service times) or Mid-Route Sourcing (to
change Unload First information). Enter the new information and click the
[Replace] button. The new information replaces the existing information for all
selected SKUs. For instance, if you need to change the service time for all SKUs
in a package type, select all the SKUs having that package type. In the Replace
SKU Properties window, check Variable Service Time Properties and enter the
new service times for each size.
To change these properties for all SKUs, right-click on an SKU and choose
Replace All from the menu that pops up.
150

Working with Planned Orders

The Roadnet Transportation Suite gives you the option to manually enter orders at
anytime and to modify previously entered orders. Additionally, you can enter time
window and service time overrides as well as special instructions for any order.
Step 2: Click on the List menu and select Product, then Planned Orders. The Orders
window opens, listing all orders for the most recent session. The title bar of the
Orders window lists the routing session you are viewing and will be working
with.
To view the orders for a different routing session, click the Change Displayed
Session icon. The Lookup - Routing Sessions window opens. Double-click on the
session you want to work with, or click on a session and then on the Process icon.
To add a new routing session to add orders to, click on the Create a New
Session icon; the Add Routing Session window opens. Complete the information
for the new routing session; see Creating a New Routing Session for more
information.
To add a future order, click on the Change Displayed Session icon. The LookupRouting Sessions window opens. Double-click on the Future session or click on
the Future session and then on the Process icon; the Future session is the first one
in the list.
Notes: To see an updated list of orders, click on the Refresh icon; the window will be
When you open a future order, you may receive a warning stating that another
user is working with that future order. If this happens, then you can only open the
future order for viewing. You will not be able to make any changes to it until the
other user has saved and closed out of the future order. Once this has happened,
you can make any changes it after you refresh the window (either click the Refresh
icon or close and re-open the window).
Operations Guide
151
Step 3: In the Orders window, click on the Add icon or press [Insert]. The Add Order
window opens.
Orders entered using

the Add Order for
Session window will
be added to the
routing session
displayed on the top
of the window.
Step 4: Enter the Order Number.

Note: This field is only required if you have MobileCast installed; however. if you do not
have MobileCast, it is strongly recommended that you include this field.
Step 5: Click on the Order Type arrow and choose whether the order is a delivery or
pickup.
Step 6: Enter the Location ID and Location Type. The Location ID and Location Type
fields must be completed; when you enter information in these fields, the name
and address of the location appears in the display box below.
Note: If you enter a location ID and type for a location that does not exist, a message
will appear asking if you want to add the location. Click [Yes] to add the location;
the Location notebook opens. See Working with Locations for more information.
If you do not geocode the location, it will appear in the Not Considered list for the
session in the Routing Editor, from which it can be routed.
Step 7: If appropriate, enter an order selector in the Selector field. You can use selectors
to filter orders when creating routes in the Routing Editor.
Step 8: To have the order originate from a specific depot, click the Preferred Depot
arrow and select the depot from the list. Unless the order is routed using Standard
152

Route Sequencing, it will be placed on a route originating from this depot. If

there are no routes originating from this depot, the order will be unasssigned.
Step 9: To have an order routed to a specific depot when using Mid-Route Sourcing,
click the Preferred MRS Depot arrow and select the depot from the list.
Step 10: If necessary, enter the Dependency between 0 and 100 for a paired order. The
dependency indicates what priority this order has over others. For paired orders
with a dependency greater than zero, the order with the lower dependency value
(1) will be picked up or delivered before orders with higher dependency value
(100). Dependency is only used with Mid-Route Sourcing.
Note: A dependency of zero allows Roadnet to determine the best order for paired
deliveries and pick-ups. If a stop has two orders with the same order number and
the same dependency, greater than zero, the container will be returned to the stop
immediately after removal of its contents.
Step 11: Click the Taken By arrow and select the employee who took the order from the
list that appears.
Step 12: Enter the appropriate quantities in the Sizes box.
Note: If you are viewing an existing order that has been routed, the quantities shown are
the quantities if the order is delivered on the Date shown.
You can only enter size quantities here if the Line Items Calculate Order Sizes box
is not checked on the Routing - General page in the Maintenance Options
notebook.
Step 13: Enter the Urgency between 1 and 100 for the order. The urgency indicates how
important it is to deliver the order, with 100 indicating the order must be
delivered. If you choose to consider urgency when creating routes in the Routing
Editor, orders with a higher urgency will be routed first.
If you are using weekly routing, enter the Daily Urgency Increase in the Weekly
Routing area.
Step 14: If you are doing weekly routing, enter the information in the Weekly Routing
area.
Daily Increaseenter the amount the quantity for each size increases each day
the order is not delivered.
Daily Urgency Increaseenter the amount the urgency should increase each day
until the End Date. An urgency of 100 indicates the order must be routed on that
date.
Note: If you are viewing an existing order that has been routed, the urgency reflects the
urgency for the delivery date. Changing this urgency will change the beginning
dates urgency.
Begin Dateenter the first date the order can be delivered. When entering date
information, you can type in the date, or you can click on the arrow to display a
calendar. If entering the date manually, check the box before typing the date. If
Operations Guide
153
using the calendar to change the month, either use the arrows on the top of the
calendar to scroll through the months, or click on the month and select from the
menu that pops up. To change the year, click on the year and use the arrows to
scroll to the correct year. Click on a date to select it.
End Dateenter the date the order must be delivered by. You can enter the date
manually, or click on the arrow to open a calendar. If entering the date manually,
check the box before typing the date. If using the calendar to change the month,
either use the arrows on the top of the calendar to scroll through the months, or
select it.
Step 15: If you want to enter a void order, check the Mark As A Void Order box at the
bottom of the window.
Step 16: If you want the order to use bulk service times, even if the quantity does not
meet the established Bulk Threshold, check Force Bulk Service Time.
Step 17: Enter the user-defined field information for the order in the appropriate fields.
The names of the user-defined fields are established on the Alias page of the
Options notebook.
Step 18: If you want to enter time window overrides, service time overrides, or special
instructions, see Orders and Overrides.
Note: Any missing values will be replaced with the location's time window's type's
corresponding value for the session's scenario. If this would cause the time
windows to fall outside the order's open and close times, the time windows will be
adjusted to within the order's open and close times.
If you want to enter line items or order activities for the order, see Entering Line
Items and Order Activities.
Step 19: Once you have entered all the appropriate information, click the Save icon or
press [Ctrl]+[S] to enter your new order.
Note: If orders are being combined in the routing session, and all other orders for the
location are on built routes, a message will appear asking if you want to add the
new order to a built route or leave it unassigned. Click on the appropriate option.
Maintenance icon List Product Planned OrdersAdd icon ([Insert]) Save icon
([Ctrl]+[S])
To add time window, service time information or instructions for the order use the
Override tab on the Orders notebook.
To add line items or activities to the order, use the Line Item/Activities tab on the Orders
notebook.
Existing orders can be edited or deleted as necessary. See Editing Items and Deleting
154

Adding Overrides to Planned Orders
The Orders notebook lets you add and edit your planned orders that will be routed in the
Routing Editor. Although the notebook contains three pages, all mandatory information
is located on the first page; you can create order overrides on the second page, and enter
line items/order activities through the third page.
The second page of the Orders notebook is the Override page. From there you can enter
time window overrides, additional service time, and special instructions to a new order or
an existing order. You must be in the Add Orders or Edit Orders window to start this
procedure.
Step 1: From the Orders window, click the Add icon to add a new order, or double-click
on an order you want to edit.
Step 2: Once the information on the Order page is accurate, click the Override tab of
the Orders notebook.
Step 3: If you want to override a locations time windows for the current order, check
the Override Location Time Windows box. The Delivery Windows box displays.
Enter the open/close and time window override information in the appropriate
fields.
Use the Override page to

add service time for an
order, such as if the order
will require more time
than normal to unload.
Step 4: Enter any applicable service time, preferred route ID, or special instructions
overrides in the appropriate fields. If a preferred route ID or special instructions
are entered they will be used instead of the information provided for the location
Operations Guide
155
when routes are created in the Routing Editor. If additional service time is
entered, it will be added to the locations service time for the stop in the Routing
Editor.
Step 5: Click the Save icon, or press [Ctrl]+[S] to save your order and override
information.
To add line items or activities to the order, use the Line Item/Activities tab on the Orders
notebook.
Entering Line Items and Order Activities for Planned Orders
The third page of the Orders notebook lets you add line items and order activities for your
planned orders. Before adding the line items or order activities, the SKUs or activities
must have been added. You must be in the Add Orders or Edit Orders window to start this
procedure.
Note: If you want to calculate the quantity for each order size using line items, be sure the
Line Items Calculate Order Sizes box is checked on the Routing - General page of
the Maintenance Options notebook.
Step 1: From the Orders window, click the Add icon to add a new order, or double-click
on an order you want to edit.
156

Step 2: Once the information on the Order page is accurate, click the Line Items/
Activities tab of the Orders notebook. The Line Items/Activities page opens.
The third page of the

Orders notebook allows
you to add line items and
order activities to your
orders.
Step 3: To add a line item to the order, click the Add icon in the Line Items section of
the window. The Add Line Item window opens. Click the SKU arrow and select
the SKU you want to add. In the Sizes area, enter the total amount of the SKU as
each size you are using. If you are using line item user defined fields, enter the
information in the User Defined Fields area. Click the Save icon, or press
[Ctrl]+[S] to save the information.
If you know the SKUs ID,

you can type it in the SKU
field, instead of clicking on
the arrow and finding it in
the list.
Operations Guide
157
To add an activity to the order, click the Add icon in the Activities section of
the window. The Add Activity window opens. Click the Activity arrow and select
the activity you want to add. The description and service time for the activity are
automatically entered in the fields below. Click the Save icon, or press [Ctrl]+[S]
to save the information.
Once you choose an activity, the

Description and Service Time for
that activity are displayed.
Step 4: Click the Save icon, or press [Ctrl]+[S] to save your order.
To add time window, service time information or instructions for the order use the
Override tab on the Orders notebook.
158

Working with Stack Rules Methods
Working with Stack Rules Methods

Stack rules methods let you create different sets of rules for how your product is stacked
when your truck is loaded in the Loading Editor. In other words, you can create different
sets of stack rules to use when loading your trucks Warehouse Friendly than you use when
loading your trucks Driver Friendly. Once the stack rules methods have been created, you
can create the stack rules.
The Roadnet Transportation Suite ships with a default stack rules method, called Standard
(STD). This method cannot be deleted, but can be changed. You can add as many stack
rules methods as you need.
Step 2: Click on the List menu and select Loading Rules, then Stack Rules, and Stack
Rules Methods. The Stack Rules Methods window opens.
This is the Stack Rules Methods window, where you can add, delete, and clone your Stack
Rules Methods.
Step 3: In the Stack Rules Methods window, click the Add icon or press [Insert] to add
a new method.
Hint: To add a method that is similar to an existing one, right-click on the existing
method and select Clone from the menu that pops up. The Add window opens with
new entry.
Step 4: Enter the ID for the method. This field must be completed.
Step 5: Enter the Description for the method.
Step 6: Click the Save icon, or press [Ctrl]+[S] to save the stack rules method.
Step 7: Repeat Steps 3 through 6 to continue adding stack rules methods.
Step 8: Click the Close box when all stack rules methods have been added. The Stack
Rules Methods window closes.
Existing stack rules methods can be edited or deleted as necessary. See Editing Items and
List Loading Rules Stack Rules Stack Rules Methods Add icon ([Insert]) Save
icon ([Ctrl]+[S]
Operations Guide
159
Working with Mix Rules Methods

Mix rules methods let you create different sets of layer and pallet mix rules that can be
used when you are loading a bay or building a pallet. For example, if you are loading your
beer by product, you may decide to set up rules that state you can load 12 oz cans and 16
oz cans together, but cannot put any 12 oz or 20 oz bottles with these cans. Once the mix
rules methods have been created, you can create the mix rules.
The Roadnet Transportation Suite ships with a default mix rules method, called Standard
(STD). This method can not be deleted, but can be changed. You can add as many mix
rules methods as you need.
Step 2: Click on the List menu and select Loading Rules, then Layer Mix Rules, and
Layer Mix Rules Methods. The Layer Mix Rules Methods window opens
OR
Click on the List menu and select Loading Rules, then Pallet Mix Rules, and Pallet
Mix Rules Methods. The Pallet Mix Rules Methods window opens.
This is the Layer Mix Rules Methods window, where you can add, delete, and clone your
Layer Mix Rules Methods.
Step 3: In the Layer Mix Rules Methods window or Pallet Mix Rules Methods window,
click the Add icon or press [Insert] to add a new method. The appropriate add
window opens.
new entry.
Step 6: Click the Save icon, or press [Ctrl]+[S] to save the mix rules method.
Step 7: Repeat Steps 3 through 6 to continue adding mix rules methods.
Step 8: Click the Close box to close the Layer Mix Rules Methods window.
160

Existing mix rules methods can be edited or deleted as necessary. See Editing Items and
List Loading Rules Layer Mix Rules/Pallet Mix Rules Layer Mix Rules Methods/
Pallet Mix Rules Methods Add icon ([Insert]) Save icon ([Ctrl]+[S]
Operations Guide
161
Working with Warehouse Zone Pick Order Methods
Working with Warehouse Zone Pick Order Methods

Warehouse Zone Pick Order Methods let you create sets of rules to establish in what order
to pick the warehouse zones when loading equipment. For instance, you could decide in
one order to pick side loader trucks to be loaded by product; and in a second picking order
for the by stop orders to go on bulk trucks.
The Roadnet Transportation Suite ships with a default warehouse zone pick order method,
called Standard (STD). This method cannot be deleted, but can be changed. You can add
as many warehouse zone pick order methods as you need.
Maintenance window opens
Step 2: Click on the List menu and select Loading Rules, then Warehouse Zone Pick
Order Methods.The Warehouse Zone Pick Order Methods window opens.
This is the Warehouse Zone Pick Order Methods window, where you can add, delete,
and clone your Warehouse Zone Pick Order Methods.
Step 3: In the Warehouse Zone Pick Order Methods window, click the Add icon or
press [Insert] to add a new method.
new entry.
Step 6: Click the Save icon, or press [Ctrl]+[S] to save the new method.
Step 7: Repeat Steps 3 through 6 to continue adding methods.
Step 8: Click the Close box when all Warehouse Zone Pick Order Methods have been
added. The Warehouse Zone Pick Order Methods window closes
Existing warehouse zones can be edited or deleted as necessary. See Editing Items and
List Loading Rules Warehouse Zone Pick Order Methods Add icon ([Insert]) Save
icon ([Ctrl]+[S]
162

Establishing Mix Rules

Mix rules allow you to define what products can be placed together on a pallet layer or in
a bay/on a pallet. You can define mix rules for warehouse zones (product from different
zones cannot be mixed), package types, and SKU brands. If all options are used, there are
six different sets of mix rules you can create:
Pallet mix rules by SKU brand
Pallet mix rules by package type
Pallet mix rules by warehouse zone
Layer mix rules by SKU brand
Layer mix rules by package type
Layer mix rules by warehouse zone
In order for two SKUs to be loaded together on a layer or pallet, there must be no mix
rules at any level (warehouse zone, package type or SKU brand). For instance, in order
for two SKUs to be loaded on the same pallet layer, there must be no package type,
warehouse zone, or SKU brand mix rules prohibiting them from being on the same layer.
Before you can set up your mix rules you need to create the mix rules methods.
Step 2: Click on the List menu and select Loading Rules, then Layer/Pallet Mix Rules,
and select the type of rule you want to create. The appropriate Mix Rules window
opens.
The same type of window is used for creating all six types of mix rules.
Step 3: Click the Mix Rules Method for Display arrow to select the method you are
creating mix rules for.
Operations Guide
163
Step 4: In the Target item for rule list, select the warehouse zone/SKU brand/package
type you are creating the rule for. The Items not used yet in this rule list is filled
with the remaining warehouse zones/SKU brands/package types.
Step 5: In the Items not yet used in this rule list, select the items that should not mix
with the target item. To select multiple items, hold down the [Ctrl] key while
selecting the items. Click the [<] button to move the items to the Should not mix
with list.
To move all items from the Items not yet used in this rule list, click the [<<]
button.
Step 6: Repeat Steps 4 and 5 until you have created all the necessary mix rules.
Step 7: Click the Save icon, or press [Ctrl]+[S] to save the mix rules.
Step 8: Click the Close box to close the Mix Rules window.
List Loading Rules Pallet Mix Rules/Layer Mix Rules By Warehouse Zone/By
Package Type/By SKU Brand Save icon ([Ctrl]+[S])
To delete or change an existing mix rule, simply move the package type/SKU brand/
warehouse zone from the Should not mix with and Items not yet used in this rule as
needed.
164

Establishing Stack Rules

Stack rules prohibit a specific package type from being stacked on another package type
when the equipment is loaded in FleetLoader. For instance, you may want to establish a
rule that prohibits cans from being stacked on bottles. Unlike mix rules, stack rules are
one-way; a stack rule preventing cans from being stacked on bottles does not prevent
bottles from being stacked on cans. Before you can set up your stack rules you need to
create the stack rules methods.
Note: Do not use stack rules to prevent SKUs from being loaded together in the same
bay/on the same layer; use mix rules to prevent this mixing.
Step 2: Click on the List menu and select Loading Rules, then Stack Rules. The Stack
Rules window opens.
Step 3: Click the Mix Rules Method for Display arrow to select the method you are
creating stack rules for.
Step 4: In the first column, find the package type that cannot be stacked on the second,
then scroll across the row to find the package type it cannot be stacked on top of.
Click in the box to place a check there.
You can create stack rules to prevent one package type from being
loaded on top of another, such as do not stack kegs on top of bottles.
Step 5: Continue until all stack rules have been created.

Step 6: Click the Save icon, or press [Ctrl]+[S] to save the stack rules.
Step 7: Click the Close box to close the Stack Rules window.
Operations Guide
165
List Loading Rules Stack Rules Save icon ([Ctrl]+[S])
166

Working with Pallet Loading Methods
Working with Pallet Loading Methods

Pallet loading methods let you create multiple ways package types can be built on a pallet.
For instance, you may build your pallets differently for holiday weekends in order to put
more product on each pallet. To allow for these situations, create a separate holiday
method, which would only be used in those special circumstances. When trucks are
loaded in the Loading Editor, a pallet loading method must be specified; if a method is
not specified the default loading method will be used.
Once the loading methods have been added, you can define the quantity of a package type
that can fit on a layer, the number of layers that can fit on a pallet, and the total quantity
for the package type. See Working with Package Types for more information.
The Roadnet Transportation Suite ships with a default pallet loading method, called
Standard (STD). This method cannot be deleted, but can be changed. You can add as
many pallet loading methods as you need.
Step 2: Click on the List menu and select Loading Rules, then Pallet Loading Methods.
The Pallet Loading Methods window opens, listing all established pallet loading
methods.
Note: To see an updated list of pallet loading methods, click on the Refresh icon; the
Step 3: In the Pallet Loading Methods window, click the Add icon or press [Insert]. The
Add Pallet Loading Method window opens.
entry. All package types will be pre-filled with the quantity per layer and layers
per pallet from the type being cloned.
Step 4: Enter up to 3 characters as the Loading Method ID. This field is required.
Step 6: Click the Save icon, or press [Ctrl]+[S] to save the loading method.
Step 7: Repeat Steps 4 through 6 to continue adding pallet loading methods.
Step 8: Click the Close box when all pallet loading methods have been added. The Add
Pallet Loading Method window closes.
List Service Rules Pallet Loading Methods Add icon ([Insert]) Save icon
([Ctrl]+[S])
Once the pallet loading methods have been added, the building information needs to be
added for each package type. See Working with Package Types for more information.
Operations Guide
167
Working with Pallet Types

Pallet types are used in the beverage industry to define types of pallets available for use
when loading the equipment. For each pallet type, can specify the pallet loading details
by defining the quantity of each package type that can fit on a pallet layer and how many
layers of the package type can fit on the pallet type. You can exclude certain pallet types
from being loaded into specific bay types and equipment types. Pallet types must be
created before you can use them to load your equipment. If you do not have multiple pallet
types, FleetLoader will load your equipment using the default standard pallet type. For
more information on adding items, see Adding Items.
Note: The Roadnet Transportation Suite ships with a default pallet type, called Standard
(STD). This pallet type cannot be deleted, but can be changed. You can add as
many pallet types as you need.
Step 2: Click List, then click Equipment, and then Pallet Types. The Pallet Types
window opens.
Step 3: Click on the Add icon to add a pallet type. The Add Pallet Type window opens.
of the information already completed; enter a new ID and change the information
as necessary for the new entry.
Step 4: Enter up to 3 characters for the ID. This field must be completed.
Step 5: Enter up to 30 characters for the Description.
You can add multiple pallet

types using the Add Pallet
Type window.
Step 6: Enter the Width and Depth. These fields must be completed.
Important: The dimensions must be entered in the same measurement as the equipment
type dimensions. For instance, both types must use feet.
Step 7: Click the Save icon, or press [Ctrl]+[S] to save the pallet type.
Step 8: Repeat Steps 4-7 to add other pallet types.
168

Step 9: When you are finished adding pallet types, click the Close box to close the Add
Pallet Type window.
Once the pallet type has been added, it can be edited or deleted as necessary. See Editing
Items and Deleting Items for more information.
Operations Guide
169
Working with Activities

In some organizations the specific tasks or activities an employee can perform need to be
considered when routes are created. For instance, if an air conditioner needs to be
installed, you want to make sure that someone qualified to install air conditioners is
assigned to that order. The Roadnet Transportation Suite allows you to create activities
that need to be performed, such as install air conditioner, and then group similar activities
together in groups called skill sets. Skill sets are then assigned to employees who can
perform those activities, and only these employees will be placed on routes containing
orders that need these activities.
Before you can create the skill sets, you need to create the activities that will be included
in the skill sets.
Step 2: Click on the List menu and select Activities. The Activities window opens,
listing all established activities.
Note: To see an updated list of activities, click on the Refresh icon; the window will be
Step 3: In the Activities window, click the Add icon or press [Insert]. The Add Activity
window opens.
entry.
Step 4: Enter up to 32 characters as the Activity ID. This field must be completed.
Enter the amount of time
needed to complete the
activity in the Service Time
field.

Step 6: Enter the amount of time needed to perform this activity in the Service Time
field. Enter the time in the format HH:MM.
170

Note: When creating the skill sets, you can associate a service time factor with the set.
When routes are created, the combination of the service time factor and the service
time will be used to determine how long an employee needs to complete a task.
Step 7: Click the Save icon, or press [Ctrl]+[S] to save the activity.
Step 8: Repeat Steps 4 - 7 to continue adding activities.
Step 9: When all activities have been added, click the Close box. The Add Activity
window closes.
Existing activities can be edited or deleted as necessary. See Editing Items and Deleting
Once the activities have been added, you can group them together as skill sets. See
Working with Skill Sets for more information.
List Activities Add icon ([Insert]) Save icon ([Ctrl]+[S])
Operations Guide
171
Working with Skill Sets

Skill sets are a group of activities that an employee is able to perform. For instance, a
plumber may be able to perform the following activities: install a washing machine, install
a dishwasher, and install a garbage disposal. Then, when the routes are created, you can
specify that only employees with the skill set needed to fulfill an order can be assigned to
the route.
Before you can create the skill sets, the activities should have been added. Once the skill
sets have been created, you can assign a skill set to an employee.
Step 2: Click on the List menu and select Employees, then Skill Sets. The Skill Sets
window opens, listing all established skill sets.
Note: To see an updated list of skill sets, click on the Refresh icon; the window will be
Step 3: In the Skill Sets window, click the Add icon or press [Insert]. The Add Skill Set
window opens.
When routes are created, employees will

not be assigned to routes that include
activities that are not included in the
skill sets Assigned Activities list.
entry.
172

Step 4: Enter up to 15 characters as the Skill set ID. This field must be completed.
Step 6: Enter the Service Time Factor for the skill set. The service time factor will be
multiplied by all the activities needed for a particular order when routes are
created.
Hint: The service time factor can be used to compensate for employees who have
different skill levels. For instance, a novice plumber may need more time to
perform activities than a senior plumber; simply give the novice plumber a higher
service time factor and more time will be allotted for completion of the task when
the routes are created.
Step 7: In the Available Activities list, select the activities employees with this skill set
can perform. Drag the activities from the Available Activities list to the Assigned
Activities list. Employees with this skill set will not be assigned to routes that
need an activity that is not included in their Assigned Activities list.
Step 8: Click the Save icon, or press [Ctrl]+[S] to save the skill set.
Step 9: Repeat Steps 4 - 8 to continue adding skill sets.
Step 10: When all activities have been added, click the Close box. The Add Skill Set
window closes.
Existing skill sets can be edited or deleted as necessary. See Editing Items and Deleting
List Employees Skill Sets Add icon ([Insert]) Save icon ([Ctrl]+[S])
Operations Guide
173
Working with Employee Types
Working with Employee Types

Employee types allow you to classify the types of employees in your organization. Some
examples of employee types are driver, dispatcher, merchandiser, or helper. Employees
can be associated with types when they are added.
Step 2: Click on the List menu and select Employees, then Employee Types. The
Employee Types window opens, listing all established employee types.
Note: To see an updated list of employee types, click on the Refresh icon; the window
Step 3: In the Employee Types window, click the Add icon or press [Insert]. The Add
Employee Type window opens.
entry.
You can add employee types,
such as drivers and helpers,
in this window.
Step 4: Enter up to 3 characters as the Employee Type. This field must be completed.
Step 6: Click the Save icon, or press [Ctrl]+[S] to save the new employee type.
Step 7: Repeat Steps 4 6 to add any other employee types.
Step 8: When you are finished adding employee types, click the Close box to close the
Add Employee Type window.
Maintenance icon List Employees Employee TypeAdd icon ([Insert])
Existing employee types can be edited or deleted as necessary. See Editing Items and
Important: Deleting an employee type affects other maintenance items. Before you
delete an employee type, you should delete employees with that employee type.
174

Working with Employees

Employees are those workers who are tracked through the Roadnet Transportation Suite,
such as the drivers, dispatchers, sales people, and helpers. The employee records store
such information as name and address, phone numbers, and various dates (birth, hire, last
physical, etc.). Before the employees are added, the employee type must be added. You
can add employees individually or import them; see Importing Maintenance Items for
more information on importing employees. You can also assign locations to the
employee, such as a salesperson or a merchandiser.
Note: If you were not granted permission to view employees confidential information
in the Administration module, you will not be able to see or enter the employees
birth, hire, and termination dates, or any ADP information.
Step 2: Click on the List menu, then Employees. The Employees window opens, listing
all current employees.
Notes: To see an updated list of employees, click on the Refresh icon; the window will
Employees displayed in red are shared by another region; you can assign them to
routes and view their information but you cannot modify their information.
Step 3: In the Employees window, click the Add icon or press [Insert]. The Add
Employee notebook opens.
Step 4: Click the General tab to open the General page.
entry.
Step 5: Enter up to 15 characters as the ID (for example, Social Security number). This
field must be completed.
Step 6: If using MobileCast, click the arrow in the Status box and select the employees
status. If the employee is available to work, check Active.
Step 7: Click on the Type arrow to open the Lookup Employee Type window.
Double-click on the proper employee type to select it, or click once and then
click the Process icon.
Step 8: Click on the Skill Set arrow to open the Lookup - Skill Set window. Doubleclick on a skill set to select it, or click once and then on the Process icon. Skill
sets are used with Roadnet and MobileCast only.
Step 9: Enter up to 35 characters each as the Last, First, and Middle Names.
Operations Guide
175
Step 10: Enter the employees address and phone number. You can also enter hire,
birth, and termination dates.
The employees ID must be

unique, such as the social
security number.
arrow to display the calendar. If entering the dates manually, use the arrow keys
to move from the month to day to year field. If using the calendar, to change the
select it.
Step 11: Enter the employees password. You can use letters, numbers, or punctuation
marks. This field does not need to be completed unless the employee is using
wireless communications.
Step 12: If you plan to export payroll data from MobileCast to ADP, you must fill in the
ADP File Number with a valid employee code. To find these codes, check your
ADP software or contact ADP.
Step 13: If the employee can be used by another region, select the region(s) in the
Shared by Regions box. To select more than one region, select the first region,
then press and hold the [Ctrl] key while selecting the others.
Note: To make an employee no longer available to a specific region(s), simply hold down
the [Ctrl] key and click on the highlighted region(s) in the Shared by Regions list
to deselect it. The employee will still be available to the other highlighted regions.
176

Step 14: If you want to assign a location to this employee, click the Locations tab.
Search for locations by entering the location type, ID, or description, and then
click the [Query] button. The locations appear in the Available Locations List.
Check Assign ALL Locations to

assign all present and future
locations in the region to the
employee.
Step 15: To assign all locations to this employee automatically, check Assign ALL
Employees. All current locations for this region will be assigned to the employee,
as well as any locations that may be added to this region in the future.
To assign a selected location to this employee, click on the location, and then
drag and drop it in the Assigned Locations list. This location is now assigned to
the employee. To select more than one location from the Available Locations list,
press [Ctrl] and then click on the locations. You can then drag all of the selected
locations into the Assigned Locations list.
Hint: You will need to assign locations to employees if you are using the MobileCast
OnTrack feature or if you want to assign a salesperson to a location. If you are
using OnTrack in the passive mode, you may want to assign a location with a type
DPD to each OnTrack user. This location should be the depot where the OnTrack
user will start the day; when the driver logs into the phone the route will
immediately start at this location, instead of waiting for the first GPS ping.
Operations Guide
177
Notes: To see a complete list of your locations, leave all of the fields empty, and then click
the [Query] button.
If you dont know the ID, enter as much as you know followed by an asterisk (*),
such as 12*.
To unassign a location from this employee, click on the location in the Assigned
Locations list, and then drag and drop it in the Available Locations list.
Step 16: Click the Save icon, or press [Ctrl]+[S] to save the new employee.
Step 17: Repeat Steps 4 15 to add any other employees.
Step 18: When you are finished adding employees, click the Close box to close the Add
Employee window.
Maintenance icon List Employees EmployeesAdd icon ([Insert]) Save icon
([Ctrl]+[S])
Once the employees have been added, the drivers can be added.
Existing employees can be edited or deleted as necessary. See Editing Items and Deleting
Items for more information. If there is a driver with the same ID as an employee being
deleted, the driver will be deleted as well.
178

Working with Drivers

Drivers are those employees who are tracked through the Roadnet Transportation Suite
on a daily basis. You can specify how each driver is paid; this pay information is used to
help determine the total cost of a route. When adding a driver, you can also assign the
equipment that driver normally uses, specify physical and drug test dates, and enter
license information for the Roadnet Transportation Suite to track. You can add drivers
only after they have been entered as employees. You can add driver individually or import
them; see Importing Maintenance Items for more information on importing drivers.
Notes: If you were not granted permission to view drivers confidential information in the
Administration module, you will not be able to see or enter the drivers pay
information, license information, date of last physical, and date of last drug test.
If the driver was created in another region, you will not be able to make any
changes to the drivers information.
Step 2: Click on the List menu and select Employees, then Drivers. The Drivers
window opens, listing all current drivers.
Note: To see an updated list of drivers, click on the Refresh icon; the window will be
Step 3: In the Drivers window, click the Add icon or press [Insert]. The Add Driver
window opens.
entry.
Step 4: Click on the ID arrow to open the Lookup Employees window. Double-click
on the correct employee in the list to insert that employee in the ID field, or click
once and then click the Process icon. The ID must be entered; everything else is
optional. This equipment be automatically assigned to a route with the driver in
the Routing Editor if desired.
Step 5: Click on the Equipment arrow to open the Lookup - Equipment window. Use
the Search feature to find the equipment you are looking for. Once the equipment
appears in the list, double-click on it, or click on a piece of equipment and then
on the Process icon, to select it. You can have the equipment automatically
assigned to the drivers route when using Speed Assign in the Routing Editor.
Step 6: Click on the Depot arrow to open the Lookup - Depot window. Double-click on
the correct depot to insert it in the Depot fields, or click once and then click the
Process icon.
Operations Guide
179
Step 7: Enter the Route ID the driver normally drives, if appropriate. You can have the
route ID automatically assigned to the route when you assign a driver using
Speed Assign in the Routing Editor.
Step 8: If you are using MobileCast, click the Type arrow and choose the driver type.
Step 9: Complete License and medical information, as needed.
When entering date information, click on the arrow to display the calendar. You
can enter the dates manually, or click the arrow to open a calendar. To change the
select it.
You can specify how much

a driver is paid in many
different ways, such as
per hour, per stop, or per
quantity delivered. This
information is used when
the route cost is
calculated.
Step 10: Determine how the driver will be paid and enter the rate of pay according to
the Driver Cost Fields table.
Item
Description
Non-Help Cost
Cost for driver only (no helper)
180

Item
Description
Helper Cost
Cost for driver and helper combined (driver alone earns $2

and helper earns $1, then helper cost = $3)
Regular Rate (per

minute)
Cost per minute, including travel and service time (driver

earns $10/hour, then regular rate = 0.1666 per minute)
Overtime Rate (per

minute)
Cost per minute for overtime work, if driver is paid at a

higher rate, including travel and service time
Minimum Time
Guaranteed minimum number of hours the driver is paid for,

whether driver works the hours or not
Overtime Hrs Begin
Number of hours after which overtime rate would apply
Per Stop Rate
Amount paid to driver per stop
Minimum Stops
Guaranteed minimum number of stops the driver is paid for,

whether driver completes that number of stops or not
Per Distance Rate
Amount paid to driver per distance (mile or kilometer)
Minimum Distance
Guaranteed minimum number of miles or kilometers the

driver is paid for, whether driver drives the miles or not
Per Piece Over Min
Amount paid to driver per piece delivered exceeding a

specified minimum number of pieces
Minimum Piece Count
Guaranteed minimum number of pieces driver is paid for,

whether driver delivers that number of pieces or not
Minimum Piece Cost
Total amount paid to driver for delivering the minimum

number of pieces (driver guaranteed to be paid $50 for
delivering 100 pieces, enter $50)
Fixed Route Cost
Fixed cost per route for a driver, such as flat rate payment.
Step 11: If you are using MobileCast to track your drivers, click on the Dispatch tab. If
not, skip to Step 13.
Step 12: If you are using MobileCast, complete the following items on the Dispatcher
tab.
If you are using newer versions of the mobile application, where the driver logs
into the device, you do not need to assign a wireless device to the driver.
Check the Pre-load Driver Directions box if you want driver directions
automatically sent to the drivers mobile device when the route is loaded.
Check Auto Arrive/Depart if you the want the drivers phone to automatically
arrive and depart stops based on GPS information. This prevents the driver from
having to press a button each time they arrive or depart a stop. This option is only
available for drivers that use Java-enabled phones with MobileCast. You must
Operations Guide
181
have Auto Arrive/Depart Mode enabled on the Dispatch - Java Phone page of the
Maintenance Options notebook to use this feature.
Check the Device Diagnostics box to have the drivers wireless device report
diagnostic information back to the server. Selecting this option allows dispatchers
to view information regarding the status of the drivers device, such as battery
power, signal strength, and error messages.
Note: If you uncheck the Auto Arrive/Depart Mode option in the Maintenance Options
notebook, the Auto Arrive/Depart option will be automatically deselected for
every driver.
Step 13: Click the Save icon, or press [Ctrl]+[S] to save the new driver.
Step 14: Repeat Steps 4 13 to add any other drivers.
Step 15: When you are finished adding drivers, click the Close box to close the Add
Driver window.
Maintenance icon List Employees DriversAdd icon ([Insert]) Save icon
([Ctrl]+[S])
Existing drivers can be edited or deleted as necessary. See Editing Items and Deleting
182

Tracking Productivity
FleetLoader allows you to track the productivity of your loaders and drivers. Productivity
information is entered in the Maintenance module, but the reports are generated in the
Reports module or the Loading Editor.
Step 2: Click on the Actual Data Entry menu and select Driver Productivity or Load
Productivity. The Productivity window opens, displaying the routes for the
current session.
Step 3: If necessary, change the session you are working with. To change the session,
click on the Change Displayed Session icon to open a list of sessions; doubleclick on a session to select it.
Step 4: Select the routes you want to add productivity information for. Right-click on a
selected route and select Edit from the menu that pops up. The Productivity
window opens.
Step 5: In the Productivity window, click on the route you want to enter productivity
information for. The route number will appear in the windows title bar.
Step 6: If entering Driver Productivity information, click on the arrow to open the
Lookup - Driver window. Double-click on the driver you want to enter
information for, or click on the driver and then on the Process icon. Enter the
service time in the format HH:MM.
You can track how long it takes each driver to deliver product. Do
not include the travel time in this amount.
If entering Load Productivity information, click on the appropriate arrow to

open a list of employees, bay types, or equipment types. Double-click on an item
to select it, or click on the item and then on the Process icon. Enter the service time
Operations Guide
183
in the format HH:MM. Click on the [Add] button. Continue until all load
productivity information for the route has been entered.
There may be more than one person loading the truck for a route, so
FleetLoader lets you enter information for multiple loaders.
To change a load productivity entry, click on it in the list, make the necessary
changes, and click on the [Update] button.
To delete a load productivity entry, click on it in the list, then click the [Remove]
button.
Step 7: Click the Save icon, or press [Ctrl]+[S] to save the information. If multiple
routes were selected, the next route will automatically be selected in the route
list.
Step 8: Continue to enter productivity information. When all productivity information
has been entered, click the Close box to close the Productivity window.
Maintenance icon Actual Data Entry Driver Productivity/Load
ProductivitySave icon ([Ctrl]+[S])
To remove one employees load productivity information for a route, while keeping the
rest of the information for the route, select that employees information and click on the
[Remove] button. To change an employees load productivity information, select that
employees information in the list, make the necessary changes, and click the [Update]
button.
184

Working with the Distance Model
Working with the Distance Model

Once the Roadnet Transportation Suite knows where your locations are, it can calculate
the distance between them. One of the distance calculation methods the Roadnet
Transportation Suite uses is the RouteNet street network; the other method is the distance
model. The distance model multiplies the straight-line distance between two points by a
factor you specify to account for turns and curves in the roads. For example, the closer
two locations are to each other, the more likely it is that they are in an urban area and have
more turns between two points because of the increased number of streets, so the factor
would be higher. In contrast, the farther apart two locations are from each other, the more
likely it is that a driver would use major roads (such as highways) to get from point to
point. Major roads mean fewer turns, so the factor would be smaller as distance increases.
The Roadnet Transportation Suite uses only one distance model; you cannot add or delete
the model, but you can edit it.
Note: If you were not granted permission to edit travel time/distance models in the
Administration module, you will not be able to edit the distance model.
Step 2: Click on the List menu, then Travel Models, then select Distance Model. The
Distance Model window opens.
Step 3: Change the information in the window as necessary. The model indicates that
the Distance (left column) between two locations will be multiplied by the Factor
(right column).
The first line in the distance model
indicates that if two points are not more
than 10 miles apart, the straight line
distance will be multiplied by 1.37
Step 4: Click the [OK] button to save the changes, or [Cancel] to abort. Clicking either
button closes the Distance Model window.
Maintenance icon List Travel Models Distance ModelOK
Note: Roadnet Technologies recommends editing the default distance model only if you
notice a significant discrepancy from the drivers actual mileage as reported by an
odometer. If the discrepancy is in travel time, edit or add a travel time model
instead. See Working With Travel Time Models for more information.
Operations Guide
185
Working with Travel Time Models

Once the Roadnet Transportation Suite knows where your locations are and the distance
between them, it can calculate travel time. One of the methods the suite can use to
calculate this time is travel time models.
The Roadnet Transportation Suite uses travel time models to calculate the speed traveled
between two points based on the distance traveled. For example, the closer two locations
are to each other, the more likely it is that the driver would use local roads and therefore
travel at a slower rate of speed. Conversely, the farther apart two locations are from each
other, the more likely it is that the driver would use larger roads (such as highways) and
therefore travel at a faster rate of speed.
You can add a number of models to fit almost any driving situation; the system contains
three default models. To compensate for traffic patterns throughout the day, use a rush
hour model.
Note: If you were not granted permission to edit travel time/distance models in the
Administration module, you will not be able to add or edit travel time models.
Step 2: Click on the List menu, then Travel Models, then select Travel Time Models.
The Travel Time Models window opens, listing all current travel time models.
Note: To see an updated list of models, click on the Refresh icon; the window will be
Step 3: In the Travel Time Models window, click on the Add icon or press [Insert]. The
Add Model window opens.
entry.
186

Step 6: Enter any fixed time (HH:MM) that you determine should be added to actual
travel time for pre- and post-delivery tasks such as starting the truck, entering or
leaving the parking lot, etc.
Read the Speed and Distance columns

like this: if two stops are 20 miles apart,
the driver will travel the first 2 miles at
21 mph, the next 3 miles (5 total) at 30
mph, the next 7 miles (10 total) at 37
mph, and the final 10 miles (20 total) at
43 mph.
Step 7: In the first space under the Distance and Speed columns, enter the first tier of
miles or kilometers and MPH or KPH.
Step 8: Repeat for the remaining tiers of Distance and Speed.
Step 9: Click on the Save icon, or press [Ctrl]+[S] to save the new travel time model.
Step 10: Repeat Steps 4 9 to add any other travel time models.
Step 11: When you are finished adding travel time models, click the Close box to close
the Add Model window.
Maintenance icon List Travel Models Travel Time ModelAdd icon
([Insert]) Save icon ([Ctrl]+[S])
Existing travel time models can be edited or deleted as necessary. See Editing Items and
Operations Guide
187
Working with Areas
Working with Areas

Used with: Roadnet
Areas in the Roadnet Transportation Suite are simply the regions states, provinces, etc.
through which your equipment travels. Their purpose in Roadnet is to allow you to
track and report the miles your equipment travels in each area. See Working with Area
Distances for more information.
Step 2: Click on the Actual Data Entry menu, then Areas. The Areas window opens.
Note: To see an updated list of areas, click on the Refresh icon; the window will be
Step 3: In the Areas window, click on the Add icon or press [Insert]. The Add Area
window opens.
entry.
Step 4: Enter up to 3 characters as the Area. This field must be completed.
Once the areas have been
added you can enter the
distance a route travels in
the area.

Step 6: Click on the Save icon, or press [Ctrl]+[S] to save the new area entry.
Step 7: Repeat Steps 4 6 to add any other areas.
Step 8: When you are finished adding, click the Close box to close the Add Area
window.
Maintenance icon Actual Data Entry AreasAdd icon ([Insert]) Save icon
([Ctrl]+[S])
Existing areas can be edited or deleted as necessary. See Editing Items and Deleting Items
for more information.
Important: Deleting areas affects other maintenance items. Before you delete areas, you
should verify the accuracy of area distances.
188

Working with Zones
Working with Zones

Used with: Roadnet, Territory Planner
Zones are used in Roadnet to group similar delivery locations together in dynamic routing
so that they fall on the same route. Zones are set up and then assigned to your locations if
necessary. In dynamic routing, you can apply a filter to only route stops in a particular
zone(s).
Although the name zone implies that the customers must be grouped together
geographically, zones are actually much more flexible than that. Of course, zones can be
used geographically. For instance, you may decide that all locations in a particular postal
code should be routed together. But you could also use zones to route, for example, all
locations of a high volume chain store that warrants their own equipment.
Step 2: Click on the List menu, then Zones. The Zones window opens.
Step 3: In the Zones window, click on the Add icon or press [Insert]. The Add Zones
window opens.
entry.
Step 4: Enter up to 15 characters as the Zone. This field must be completed.
You can add zones to group
locations together by area,
or by any other common
factors.
Step 5: Enter up to 30 characters as a Description for the zone.

Step 6: Click on the Save icon, or press [Ctrl]+[S] to save the zone.
Step 7: Repeat Steps 4 6 to add any other zones.
Step 8: When you are finished adding, click the Close box to close the Add Zones
window.
Maintenance icon List ZonesAdd icon ([Insert]) Save icon ([Ctrl]+[S])
Existing zones can be edited or deleted as necessary. See Editing Items and Deleting
Operations Guide
189
Working with Zones
Important: Deleting zones affects other maintenance items. Before you delete zones, you
should edit locations with that zone.
190

Working with Onboard Codes

Used with: Roadnet
Roadnet lets you import actual route information the driver collects during the day on an
onboard computer. Once imported into the Roadnet system, this actual information can
be used when running some reports or when using service time maintenance to update the
service times. Some of these onboard systems allow the driver to enter codes that indicate
breaks, waits, or layovers. In order for Roadnet to recognize these breaks as such, you
need to tell it the codes the driver will be entering, and whether the code indicates a paid
or unpaid break, wait, or layover. Onboard codes let you provide this information to
Roadnet.
During the import process, if Roadnet encounters one of these onboard codes, it searches
the route for the next occurrence of a break/wait/layover and enters the actual information
for that break. For instance, if there is an onboard code of PHONE and it is set as a paid
break, when Roadnet encounters a PHONE entry during the onboard import, it will
associate it with the next paid break on the route. If there is no paid break planned for the
route, it will note the actual break in the import error log but will not add it to the route.
Step 2: Click on the List menu, then Onboard Codes. The Onboard Codes window
opens.
Step 3: In the Onboard Codes window, click on the Add icon or press [Insert]. The Add
Onboard Code window opens.
entry.
Step 4: Enter the code and description. A code is required and must match the code the
drivers will be entering
The code the driver enters
on the onboard computer
must match the code
entered here or Roadnet
will not recognize it.
Operations Guide
191
Step 5: In the Stop Type area, select whether the code indicates a break, wait, or
layover. If the code indicates a paid break/wait/layover, check the Paid box.
Step 6: Click on the Save icon, or press [Ctrl]+[S] to save the onboard code.
Step 7: Repeat Steps 4 6 to add any other onboard codes.
Step 8: When you are finished adding, click the Close box to close the Add Onboard
Code window.
Maintenance icon List Onboard CodeAdd icon ([Insert]) Save icon
([Ctrl]+[S])
Existing onboard codes can be edited or deleted as necessary. See Editing Items and
192

Working with Account Types
Working with Account Types

Account types help you to group your locations by a common trait, such as a chain of fastfood restaurants or those locations that require COD payment. Account types are also a
method of grouping locations for reporting purposes, such as producing a Location
Delivery Cost report. In other words, account types are a flexible tool that can be used for
almost any purpose. When you add a location, you must assign an account type.
Step 2: Click on the List menu, then select Account Types. The Account Types window
opens, listing all current account types.
Step 3: In the Account Types window, click on the Add icon or press [Insert]. The Add
Account Type window opens.
entry.
Step 4: Enter up to 5 characters as the type and up to 30 characters as the description.
The type must be entered; everything else is optional.
The Add Account Type
window allows you to
specify a type, color, and
description for account
type.
Step 5: Click on the arrow next to the color to open a color palette. Click on a color to
select it.
Step 6: Click on the Save icon, or press [Ctrl]+[S] to save the new account type.
Step 7: Repeat Steps 4 6 to add any other account types.
Step 8: When you are finished adding account types, click the Close box to close the
Add Account Type window.
Maintenance icon List Account TypesAdd icon ([Insert]) Save icon
([Ctrl]+[S])
Existing account types can be edited or deleted as necessary. See Editing Items and
Operations Guide
193
Working with Scenarios
Working with Scenarios

Scenarios are an easy way to apply changes to time windows, service times, and even
service pattern sets on a global level. Scenarios can be used for routing in the Dispatcher,
for routing sessions in the routing editor, or for planning sessions in the planning editor.
The Roadnet Transportation Suite comes with one default scenario, which you can use for
general purposes. If you use only this scenario, you dont have to do anything. But if you
need a means to globally alter service times, time windows, or service pattern sets within
a route or session, then scenarios will help you. For instance, if you need to update the
service times for a session to account for snow for instance you can create a new
scenario to instantly update the service times for every customer in that session. The
scenario will be there for you to use when you need it, but the update will occur for that
days routes only; subsequent sessions will revert to your default scenario. Another way
scenarios are commonly used is to account for merchandisers, who often follow different
service times and time windows.
Step 2: Click on the List menu, and select Service Rules, then Scenarios. The Scenarios
window opens.
Step 3: In the Scenarios window, click on the Add icon or press [Insert]. The Add
Scenario window opens.
and select Clone from the menu that pops up. The Add Scenario window opens
for the new entry.
Step 4: Enter up to 15 characters as the scenario name and up to 256 characters as the
description. The scenario name must be entered.
Step 5: Click on the Save icon, or press [Ctrl]+[S] to save the new scenario.
Step 6: Repeat Steps 4 and 5 to add any other scenarios.
Step 7: When you are finished adding scenarios, click the Close box to close the Add
Scenario window.
Maintenance icon List Service Rules ScenariosAdd icon ([Insert]) Save
icon ([Ctrl]+[S])
Existing scenarios can be edited or deleted as necessary. See Editing Items and Deleting
194

Working with Service Time Types

Service time types help you group your locations by a common trait, which is strictly
service time. Service time types allow you to specify that a group of locations has the
same fixed and variable service times because the delivery environment is the same, such
as a chain of fast-food restaurants or a group of grocery stores that allows a pallet drop at
a loading dock. Service time types may be, but don't have to be, correlated directly with
account types.
The service time types that you add can be assigned to your locations. Service time types
are also created for each scenario, so an individual location may have multiple service
times depending on the number of existing scenarios. Your scenarios must be created
before you can add service time types.
Step 2: Click on the List menu and select Service Rules, then Service Time Types. The
Service Time Types window opens, listing all current types.
Note: To see an updated list of service time types, click on the Refresh icon; the window
Step 3: In the Service Time Types window, click on the Add icon or press [Insert]. The
Add Service Time Type window opens.
and select Clone from the menu that pops up. The Add Service Time Type
window opens with some information already completed; change the information
as necessary for the new entry.
Step 4: Enter up to 5 characters as the ID and up to 30 characters as the name. The ID
must be entered.
Step 5: Click on the color arrow to open a color palette. Click on a color to select it.
Step 6: If more than one scenario appears in the list window at the bottom of the Add
Service Time Type window, verify that the scenario you want to enter service
times for is highlighted.
Operations Guide
195
Step 7: Enter the service times and bulk service times for non-helper and helper
deliveries.
The Add Service Time Type window
allows you to create types for all of
your scenarios. You can specify
regular and bulk service times,
helper and non-helper, for every
scenario.
Service timesare total time spent delivering product to a location.

Bulk service timesare times spent delivering product on pallets or quantities
that meet the bulk threshold for that location or orders forced to use bulk service
time.
Fixed service timeis the amount of time, independent of the quantity of product
delivered, that it takes to service a location. Fixed service time includes parking
the truck, filling out paperwork, obtaining payment on COD orders, etc.
Variable service timeis the amount of time it takes to move one unit of product
from the equipment into the location receiving the delivery. The size selected as
the Unit of Service or Bulk Unit of Service (if a bulk order) in the Options
notebook is used to calculate the variable service time.
Step 8: Click on the [Update] button to store the service times in the list window at the
bottom of the Add Service Time Type window.
Hint: If there is more than one scenario and the times for the other scenarios are similar,
click on the updated scenario and drag it to the other listed scenario(s). The times
will be copied into the new scenario(s), where they can be edited.
Step 9: Click on the Save icon, or press [Ctrl]+[S] to save the new service time type.
Step 10: Repeat Steps 4 9 to add any other service time types.
Step 11: When you are finished adding service time types, click the Close box to close
the Add Service Time Type window.
Maintenance icon List Service Rules Service Time TypesAdd icon ([Insert])
196

Existing service time types can be edited or deleted as necessary. See Editing Items and
Operations Guide
197
Working with Time Window Types

Time window types help you to group your locations by a common trait, but that common
trait is strictly time windows. Time window types allow you to specify that a group of
locations has the same time windows, such as a chain of fast-food restaurants.
The time window types that you add can be assigned to your locations. Time window
types are also created for each scenario, so an individual location may have multiple time
windows depending on the number of existing scenarios. Your scenarios must be created
before you can add the time window types.
Note: Roadnet Technologies advises that make the time windows as wide as possible.
Narrow and unnecessary time windows restrict the system and make it more
difficult to achieve cost savings on your routes.
Step 2: Click on the List menu, and select Service Rules, then select Time Window
Types. The Time Window Types window opens, listing all current types.
Note: To see an updated list of time window types, click on the Refresh icon; the window
Step 3: In the Time Window Types window, click on the Add icon or press [Insert]. The
Add Time Window Type window opens.
entry.
Step 4: Enter up to 5 characters as the ID and up to 30 characters as the name. The ID
must be entered.
Step 5: Click on the arrow next to the color to open a color palette. Click on a color to
select it.
Step 6: If more than one scenario appears in the list window at the bottom of the Add
Time Window Type window, verify that the scenario you want to enter time
windows for is highlighted.
Step 7: Enter the open and close times and preferred delivery times for the time
window type. To enter a time, click in the box to enter a check for the field, then
198

either type the time or use the arrows to scroll to the time. Make sure the correct
part of the time (hours or minutes) is selected when you are entering the time.
Using time window types, you

can have different time
windows for each scenario.
When you choose a scenario
in the Route or Planning
Editor, that time window
information will be used.
Open/Close Timesare the earliest and latest possible times the location can
receive a delivery, not when they open and close for business. Enter a start (open)
and end (close) time.
Time Windows 1 and 2are the times that location prefers to receive deliveries.
Enter a start (earlier time) and stop (later time) for each time window if necessary.
Step 8: Click the [Update] button to store the times in the list window at the bottom of
the Add window.
Hint: If there is more than one scenario and the times for the other scenarios are similar,
click on the updated scenario and drag it to the other listed scenario(s). The times
will be copied into the new scenario(s). You can then edit the times for the
subsequent scenario(s).
Step 9: Click on the Save icon, or press [Ctrl]+[S] to save the new time window type.
Step 10: Repeat Steps 4 9 to add any other time window types.
Step 11: When you are finished adding time window types, click the Close box to close
the Add Time Window Type window.
Maintenance icon List Service Rules Time Window TypesAdd icon
Existing time window types can be edited or deleted as necessary. See Editing Items and
Operations Guide
199
Working with Service Patterns

Service patterns describe the percentage of delivery on each day of the week as well as
the number of weeks between deliveries. Once all service patterns have been entered, they
can be grouped into service pattern sets, which are used to define location delivery options
in Territory Planner.
Step 2: Click on the List menu and select Service Rules, then Service Patterns. The
Service Patterns window opens, listing all existing patterns.
Note: To see an updated list of service patterns, click on the Refresh icon; the window
Step 3: In the Service Patterns window, click on the Add icon or press [Insert]. The
Add Service Pattern window opens.
and select Clone from the menu that pops up. The Add Service Pattern window
This example of a
service pattern displays
a weekly delivery
schedule for Monday,
Wednesday, and
Friday. Notice the total
weekly delivery equals
100%.
Step 4: Enter up to 3 characters as the Pattern ID and up to 30 characters for the

Description. The Pattern ID must be entered.
Step 5: Enter the percentage of the total quantity to be delivered on each day of the
week. The total of each service pattern must equal 100 percent of the total
delivery.
Step 6: Select the number of weeks between deliveries. A selection of 2 would indicate
the delivery is to be made every other week. If you have multiple deliveries in the
same week enter 1 in this field.
200

Step 7: Click on the Save icon, or press [Ctrl]+[S] to save the new service pattern.
Step 8: Repeat Steps 4 -7 to add any other service patterns.
Step 9: When you are finished adding service patterns, click the Close box to close the
Add Service Pattern window.
Maintenance icon List Service Rules Service PatternsAdd icon ([Insert])
Existing service patterns can be edited or deleted as necessary. See Editing Items and
Operations Guide
201
Working with Service Pattern Sets

A service pattern set is a group of service patterns used to define delivery options for the
location extensions in Territory Planner. Each location extension is associated with a
service pattern set which defines its possible delivery options that Assign Days can
choose from when creating routes. Because the delivery frequencies defined in these sets
are based on quantity delivered, location extensions with the same service pattern set may
have different delivery days in different planning sessions. For example, a set may contain
one service pattern that delivers 100% on Monday with a quantity level of 0-50 cases and
another service pattern that delivers 50% on Wednesday and 50% on Friday with a
quantity level of 51-100 cases. The delivery quantity for the individual session will
determine which service pattern is used in that session.
You can have an unlimited number of patterns for each level as well as an unlimited
number of levels for each set. You must add the service patterns before adding the service
pattern sets.
Step 2: Click on the List menu and select Service Rules, then select Service Pattern
Sets. The Service Pattern Sets window opens, listing all current pattern sets.
Note: To see an updated list of service pattern sets, click on the Refresh icon; the window
Step 3: In the Service Pattern Sets window, click on the Add icon or press [Insert]. The
Add Service Pattern Set window opens.
and select Clone from the menu that pops up. The Add Service Pattern Set window
Step 4: Enter up to 3 characters as the Set ID and up to 30 characters for the
Description. The Set ID must be entered.
Step 5: Click the Current Scenario arrow to open a list of scenarios and select the
scenario you are adding a service pattern set information for.
Step 6: Click on the Color arrow to open a color palette. Click on a color to select it.
This is the color that will be used to represent the service pattern set on the map if
that option is selected in the Planning Editor.
202

Step 7: Click the [New Level] button and enter the maximum quantity for the level for
which you want to enter service patterns.
Remember to tab beyond the last

field of entry before saving.
Step 8: Select service pattern(s) by clicking on the arrow to open a list of available
service patterns and clicking on a service pattern to select it. You can select as
many service patterns as necessary for each quantity level.
Hint: Make sure to tab past the last service pattern you select.
Step 9: Repeat Steps 6 and 7 for every quantity level for which you want separate
service patterns. The maximum quantity for the final level must be 9,999,999.
Step 10: Choose the next scenario you want to enter service pattern set information for.
Step 11: When you have entered level information for each scenario, click on the Save
icon or press [Ctrl]+[S] to save the new service pattern set.
Note: If you have more than one scenario, and have not entered service pattern set
information for all scenarios, the Service Pattern Set Data Options window opens
when you save. The Service Pattern Set Data Options window lists the scenarios
that do not have service pattern sets assigned to them, and gives you several
options. You can choose to copy the service pattern set information to all the other
scenarios (Fill these Scenarios with Data from:), leave the scenarios without
service pattern sets (Save Only the Data I Entered) or return to the Service Pattern
Set window to assign service pattern sets to the scenarios ([Cancel]).
Step 12: Repeat Steps 4 - 10 to add any other service pattern sets.
Step 13: When you are finished adding service pattern sets, click the Close box to close
the Add Service Pattern Set window.
Maintenance icon List Service Rules Service Pattern SetsAdd icon
Operations Guide
203
Existing service pattern sets can be edited or deleted as necessary. See Editing Items and
204

Working with Planning Sessions

Planning sessions are a way of grouping information necessary to solve routing problems
in Territory Planner. They also enable you to change parameters and try different what
if scenarios without losing existing routes. When you enter the Planning Editor, you
must select a specific session with which to work. Planning sessions can be added using
this window by importing location extensions, or choosing Transfer Session when in the
Planning Editor.
Step 2: Click on the List menu and select Planning Sessions.
Note: To see an updated list of planning sessions, click on the Refresh icon; the window
Step 3: In the Sessions window, click on the Add icon, or press [Insert]. The Add
Session window opens.
entry.
Cycle weeks denotes the length of the planning session.
Step 4: Click on the arrow to open the Lookup - Scenario window. To select a scenario,
either double-click on it, or click on it and then on the Process icon, to select it.
Operations Guide
205
Step 5: Enter a Description for the planning session. The combination of Description
and Scenario must be unique for each planning session.
Hint: Make the session description something easily identifiable so you can select the
proper session when entering the Planning Editor.
Step 6: Select the type of Time/Distance Calculation to be used for the planning
session.
XYis a routing method that uses a straight line to measure the distance between
RouteNetis a calculation method that uses maps to replicate the actual road
limits and road changes. Compared with XY, RouteNet takes a little longer to
process but is more accurate.
Include Reload Depotscheck to include all of the regions depots for every
territory when calculating RouteNet travel times and distances. If this option
is not checked, only the depot within the territory will be included when times
and distances are calculated for that territory. If you are using reload depots,
you should check this option.
If there are more than 4000 unique location extensions in a planning session or if
the memory required for the build exceeds 2 GB, times and distances will be
SuperMatrixis another calculation method that uses the street network to
SuperMatrix, you need to specify how you want to the Planning Editor handle
206


directory.
the Maintenance Options notebook. If you want road restrictions to be enabled for
the planning session, check Apply Road Restrictions. When the road restrictions
feature is enabled, equipment types that are prohibited from traveling on height
and weight restricted roads will only be routed on street segments that are not
restricted. If it is impossible to reach a stop without traveling on a street segment
that is restricted, the stop will be routed using the XY method.
Note: The commercial road restriction and the road restriction features can only be used
routes in the planning session. Select the rush hour model that the session should
opens.Double-click on a model to select it, or click on the model and then on
Advanced Rush Houruses rush hour paths and areas to determine the
actual streets the routes will take. If using advanced rush hour features, you
can still use simple areas as well as advanced areas and paths. If you want to
change the road direction during a rush hour period, you must check Advanced
rush hour. Using advanced rush hour may require additional time when
entering the Planning Editor.
Operations Guide
207
Use Historical Travel Speedsuses historical traffic data when creating routes
in the Planning Session. This option os only available if you purchased historical
travel speeds.
Step 7: Click the Time of Day Restriction Model arrow to select the model to use for
the planning session. This allows you to choose a time of day restriction model to
choose a time of day restriction model to designate periods in/during the day in
which restricted equipment types cannot travel in restricted areas or paths. This
prevents some vehicles, such as large trucks, from being routed on restricted
roads while allowing other vehicles, such as small trucks or vans, to use those
roads.
Step 8: Enter a number between 1 and 24 to indicate the number of Cycle Weeks for the
planning session. When determining the number of cycle weeks, make sure the
cycle is long enough that every location extension is delivered at least once.
Step 9: Click on the Save icon, or press [Ctrl]+[S] to save the new planning session.
Step 10: Repeat Steps 4 - 9 to add any other planning sessions.
Step 11: When you are finished adding planning sessions, click the Close box to close
the Add Session window.
Maintenance icon List Planning SessionsAdd icon ([Insert]) Save icon
([Ctrl]+[S])
Existing planning sessions can be edited or deleted as necessary. See Editing Items and
Note: If you delete a planning session you may want to compress the database to reduce
its size. To compress the database, choose Compact Database from the Tools
menu.
208

Working with Reason Codes

MobileCast allows you to set up reason codes that give information about why an actual
delivery quantity does not match the planned quantities. For example, if some of the
merchandise is damaged and therefore refused, the driver can select a reason code
explaining why the delivery quantity is less than planned. In the Options notebook, you
can choose to make reason codes mandatory for any variance between actual quantity and
planned quantity. See Setting the Reason Codes for more information.
Step 2: Click on the List menu and select Dispatch, then Reason Codes. The Reason
Codes window opens, listing the existing reason codes.
Note: To see an updated list of reason codes click on the Refresh icon; the window will
Step 3: In the Reason Codes window, click on the Add icon or press the [Insert] key.
The Add Reason Code window opens.
and select Clone from the menu that pops up. The Add Reason Code window
opens with some information completed; change the information as necessary for
the new reason code.
Step 4: Enter up to three characters as the Code. This field must be completed.
When adding a reason
code, you can select
whether it applies to
discrepancies in the
Delivery, Over, Pickup,
or other quantity.
Step 6: In the Code Applies To section, click to place checkmarks next to the situations
you want the code to apply to: Delivery, Over, Short, Damaged, and/or Pickup.
Step 7: Click on the Save icon, or press [Ctrl]+[S] to save information.
Step 8: When all reason codes have been added, click the Close box to close the Add
Reason Code window.
Operations Guide
209
Maintenance icon List Dispatch Reason Codes Add icon ([Insert]) Save icon
([Ctrl]+[S])
Existing reason codes can be edited or deleted as necessary. See Editing Items and
210

Working with Cancel Stop Codes
Working with Cancel Stop Codes

There may be times when the driver needs to cancel a stop that for some reason cannot be
delivered at its scheduled time. A canceled stop remains part of the planned route. You
can set up codes that can be used to indicate why a stop is canceled or unassigned; when
the driver or dispatcher cancels the stop they choose the appropriate code. The dispatcher
can review why a stop was canceled and update the code if necessary. Canceled stop
codes can also be used when unassigning a stop in the Dispatcher.
Step 2: Click on the List menu and select Dispatch, then Canceled Stop Codes. The
Cancel Stop Codes window opens, listing the existing codes.
Note: To see an updated list of cancel stop codes click on the Refresh icon; the window
will be updated with all changed information from the database.
Step 3: In the Cancel Stop Codes window, click on the Add icon or press the [Insert]
key. The Add Cancel Stop Codes window opens.
Hint: To add an entry that is similar to an existing entry, right-click on the existing entry
and select Clone from the menu that pops up. The Add Cancel Stop Code window
the new cancel stop code.
You can set up cancel stop codes that
the driver can use to indicate why a
stop is canceled.
Step 7: When all cancel stop codes have been added, click the Close box to close the
Add Cancel Stop Code window.
Maintenance icon List Dispatch Cancel Stop Codes Add icon ([Insert]) Save
icon ([Ctrl]+[S])
Existing cancel stop codes can be edited or deleted as necessary. See Editing Items and
Operations Guide
211
Working with Undeliverable Stop Codes
Working with Undeliverable Stop Codes

If you are using wireless communication, you can set up undeliverable stop codes that the
driver can apply to situations in which a stop cannot be delivered. For instance, if an order
is refused, damaged, incorrect, etc., the driver can select the appropriate undeliverable
stop code to send to the dispatcher. The dispatcher can review why a stop was
undeliverable, and change the code if necessary.
Step 2: Click on the List menu and select Dispatch, then Undeliverable Stop Codes.
The Undeliverable Stop Codes window opens, listing the existing stop codes.
Note: To see an updated list of undeliverable stop codes click on the Refresh icon; the
window will be updated with all changed information from the database.
Step 3: In the Undeliverable Stop Codes window, click on the Add icon or press the
[Insert] key. The Add Undeliverable Stop Codes window opens.
You are able to indicate why you

are unable to deliver to a stop.
and select Clone from the menu that pops up. The Add Undeliverable Stop Codes
window opens with some information completed; change the information as
necessary for the new stop code.
Step 7: When all stop codes have been added, click the Close box to close the Add
Undeliverable Stop Codes window.
Maintenance icon List Dispatch Undeliverable Stop Codes Add icon ([Insert])
Existing undeliverable stop codes can be edited or deleted as necessary. See Editing Items
and Deleting Items for more information.
212

Working with Stop Signature Codes
Working with Stop Signature Codes

If you are using wireless communication, you can set up stop signature codes that the
driver can apply to situations when a signature or proof of delivery is required. These
codes can be used in place of or in addition to a signature. Once applied to the delivery,
the code and signature are sent back to the Dispatcher module, where they are stored as
proof of delivery.
Step 2: Click on the List menu and select Dispatch, then Stop Signature Codes. The
Stop Signature Codes window opens, listing the existing signature codes.
Note: To see an updated list of stop signature codes, click on the Refresh icon; the
Step 3: In the Stop Signature Codes window, click on the Add icon or press the [Insert]
key. The Add Stop Signature Codes window opens.
You can have the driver get a
signature as proof of delivery.
and select Clone from the menu that pops up. The Add Stop Signature Codes
necessary for the new signature code.
Step 7: When all signature codes have been added, click the Close box to close the Add
Stop Signature Codes window.
Maintenance icon List Dispatch Stop Signature Codes Add icon ([Insert]) Save
icon ([Ctrl]+[S])
Existing stop signature codes can be edited or deleted as necessary. See Editing Items and
Operations Guide
213
Working with Order Financial Detail Codes

If you are tracking financial information about your orders, then you can set up financial
codes that the dispatcher can apply to any order. The dispatcher can add, edit, or delete
any financial detail associated with an order, including these financial codes. Orders
associated with these codes can also be seen on a handheld device, giving the driver the
ability to verify the customers financial information pertaining to that particular delivery.
Step 2: Click on the List menu and select Dispatch, then Order Financial Detail Codes.
The Order Financial Detail Codes window opens, listing any existing financial
codes.
Note: To see an updated list of financial types click on the Refresh icon; the window will
Step 3: In the Order Financial Detail Codes window, click on the Add icon or press the
[Insert] key. The Add Order Financial Detail Code window opens.
When adding a financial

code, you can select
whether it is for items that
are credit, debit, or
adjustments.
and select Clone from the menu that pops up. The Add Order Financial Detail
Code window opens with some information completed; change the information as
necessary for the new financial code.
Step 6: Check Aggregate if you want the hand-held application to combine all orders
for each order financial detail code and display each code as one total sum. If this
option is not checked, the driver will see all the financial details for the selected
order.
Step 7: Select the financial type:
ChargeItems that a customer is responsible for, usually in the form of a
payment (i.e. credit card, money order, check).
214

AdjustmentItems that will affect the original cost of the order, usually in the
form of a coupon or discount.
DebitThe original cost of the order, plus an other item(s) that will affect the
cost, such as a tax or shipping fee.
Step 9: When all codes have been added, click the Close box to close the Add Order
Financial Detail Types window.
Maintenance icon List Dispatch Order Financial Detail Types Add icon ([Insert])
Existing financial codes can be edited or deleted as necessary. See Editing Items and
Operations Guide
215
Working with Order Status Codes
Working with Order Status Codes

If you are using handheld devices, and you want to assign the same code to all of the
orders on a stop, then you can create order status codes that the driver can apply to many
situations. For example, you can set up codes that the driver can apply when an order is
damaged, undeliverable, refused, when a stop is canceled, when the time window was
missed, when the stop requires a signature, and so on. These codes are very similar to
reason codes, cancel stop codes, undeliverable stop codes, and signature codes; the only
difference is that they are applied to every order on a stop.
Step 2: Click on the List menu and select Dispatch, then Order Status Codes. The Order
Status Codes window opens, listing any existing status codes.
You can apply a code to every

order on a stop.
Note: To see an updated list of status codes, click on the Refresh icon; the window will
Step 3: In the Order Status Codes window, click on the Add icon or press the [Insert]
key. The Add Order Status Codes window opens.
and select Clone from the menu that pops up. The Add Order Status Codes
necessary for the new status code.
Step 7: When all status codes have been added, click the Close box to close the Add
Order Status Codes window.
Maintenance icon List Dispatch Order Status Codes Add icon ([Insert]) Save
icon ([Ctrl]+[S])
Existing order status codes can be edited or deleted as necessary. See Editing Items and
216

Working with Driver Alerts
Working with Driver Alerts

If you are using wireless communication, you can set up driver alerts to remind drivers of
a task that is associated with a stop. For instance, if the stop is a COD account, you could
set up a COD driver alert, and associate it with the stop. You can also set up driver alerts
for specific items on an order, such as alcohol, where the driver needs to check ID when
delivering. When the driver arrives at the stop, the alert flashes on the wireless devices
screen for the driver to see. Driver alerts are associated with the stop in the Dispatcher
module.
Step 2: Click on the List menu and select Dispatch, then Driver Alerts. The Driver
Alerts window opens, listing the existing driver alerts.
Note: To see an updated list of driver alerts click on the Refresh icon; the window will
Step 3: In the Driver Alerts window, click on the Add icon or press the [Insert] key. The
Add Driver Alert window opens.
Hint: To add an entry that is similar to an existing one, right-click on the existing driver
entry and select Clone from the menu that pops up. The Add Driver Alert window
the new driver alert.
Step 4: Enter up to three characters as the ID. This field must be completed.
Step 5: Enter up to 255 characters as the message that the driver will see. This field
must be completed. Try to make the message as concise as possible.
Step 6: Click on the Save icon, or press [Ctrl]+[S] to save the driver alert.
This driver alert will
remind the driver to
collect cash from the
customer when
making a delivery.
Step 7: When all driver alerts have been added, click the Close box to close the Add
Driver Alert window.
Maintenance icon List Dispatch Driver Alerts Add icon ([Insert]) Save icon
([Ctrl]+[S])
Existing driver alerts can be edited or deleted as necessary. See Editing Items and
Operations Guide
217
Working with Surveys

Surveys can be used to gather different kinds of information from your customers or
drivers as they proceed through their routes. You can create marketing surveys to find out
more information about your customers, such as their shopping preferences, as well as
operational surveys to find out more about how your drivers operate throughout the day.
Surveys are associated with routes or stops in the Dispatcher, or you can import the
surveys with your MobileCast routes.
Step 2: Click on the List menu and select Dispatch, then Survey Setup. The Survey
Setup window opens, listing the existing surveys and survey questions.
Step 3: There are several parts to creating a survey; you need to add the survey, create
the survey questions, and then assign the questions to the survey.
Adding a Survey
The first step in creating a survey is to add the survey itself.

Step 1: In the Survey area of the Survey Setup window, click on the Add icon. The Add
Survey window opens.
and select Clone from the menu that pops up. The Add Survey window opens with
some information completed; change the information as necessary for the new
survey.
Step 2: Enter up to 3 characters as the surveys unique Code. This field must be
completed.
Step 3: Enter a Description.
Step 4: To have this survey automatically assigned to a route or stop, click the Default
Survey For arrow. Choose whether the survey will be taken Pre-Route, PostRoute, or At Stop. You can change or unassign a survey for any individual route
or stop.
Note: You are limited to one default Pre-Route, Post-Route, or At Stop survey.
Step 5: Click on the Save icon, or press [Ctrl]+[S] to save the survey
This survey is being
created to use at each
stop.
218

Step 6: When all surveys have been added, click the Close box to close the Add Survey
window.
Maintenance icon List Dispatch Survey Setup Surveys area Add icon Save
icon ([Ctrl]+[S])
Existing surveys can be edited or deleted as necessary. See Editing Items and Deleting
Once you have created the survey, you need to assign the questions to the survey. See
Assigning Questions to the Surveys for more information.
Creating the Survey Questions
You need to create the questions that will be included in the surveys. The questions you
create here will appear on the wireless device for the driver to answer. You can create
several types of questions, such as where the driver chooses yes or no, chooses an answer
from a list, or simply types an answer. You can use the same question on as many surveys
as you like.
Step 1: In the Available Questions area of the Survey Setup window, click on the Add
icon. The Add Survey Question window opens.
Step 2: Enter a unique ID for the question in the Descriptor field. This field must be
completed.
Step 3: Enter the question as you want it to appear on the wireless device in the
Question Text field.
When entering the possible

answers for a pick list
question, press the [Enter]
key between each option to
form a list.
Step 4: Click the Answer Type arrow and choose the type for the question. The options
are described below.
Textthe driver types an answer to the question on the wireless device. An
example of an open ended question is What can we do to better meet your
needs?
Operations Guide
219
Yes/Nothe driver selects Yes or No on the wireless device as the answer to the
question. An example of a Yes/No question is Were you happy with the service
you received today?
Pick Listthe driver selects the answer from a list you provide. Enter the possible
answers in the Answer Data field below. When typing the answers press the
[Enter] key between each option; you will be creating a list of answers. An
example of a pick list question is How often do you purchase groceries?
More than once a week
Once a week
Every other week
Once a month
Numericthe driver types a number on the wireless device to answer the
question. an example of a Numeric question is How many times did you visit this
location this week?
Step 5: Click on the Save icon, or press [Ctrl]+[S] to save the question
Step 6: When all surveys have been added, click the Close box to close the Add
Question window.
Maintenance icon List Dispatch Survey Setup Available Questions area Add
icon Save icon ([Ctrl]+[S])
Existing survey questions can be edited or deleted as necessary. See Editing Items and
Assigning Questions to the Surveys
Once you have created the survey and the questions, you need to select which questions
will appear on the survey and the order in which they will appear.
220

Step 1: In the Surveys are of the Survey Setup window, select the survey you are adding
questions to.
You can change the column widths and positions to display the information as you want.
Step 2: In the Available Questions area, select the questions you want to add to the
survey. Drag the selected questions from the Available Questions area to the
Survey Questions area. When asked if answers should be required for the
questions, select [Yes] or [No].
Notes: If you say a question is required, the driver will not be able to proceed beyond the
question without answering it.
If you want to change whether a question is required or not, click on the Required?
column in the Survey Questions area.
Step 3: Verify the questions are listed in the order you want them to appear on the
wireless device. To move a question to a different place in the order, click on it
and drag it to where you want it to appear.
Operations Guide
221
.Working with Canned Text Messages
.Working with Canned Text Messages

If you are using wireless communication, you can set up canned text messages to be sent
to or from the drivers mobile device. For example, in the instance of a traffic jam or any
other situation, the driver can quickly select from a list of messages to send to the
dispatcher, rather than typing out the message. Similarly, the dispatcher can choose from
a list of messages to send to the driver at any time.
Step 2: Click on the List menu and select Dispatch, then Canned Text Messages. The
Canned Text Messages window opens, listing the existing messages.
Note: To see an updated list of canned text messages click on the Refresh icon; the
Step 3: From the Canned Text Messages window, click on the Add icon or press the
[Insert] key. The Add Canned Text Message window opens.
Your drivers can select a message to
send from a derived list.
and select Clone from the menu that pops up. The Add Canned Text Message
necessary for the new canned text message.
Step 4: Enter up to 255 characters as the message the driver will see. Try to keep your
message as concise as possible.; the driver or dispatcher can add to the message
when sending it if necessary.
Step 5: Click on the Save icon, or press [Ctrl]+[S] to save the information.
Step 6: When you are finished adding canned text messages, press the Close box to
close the Add Canned Text Message window.
Maintenance icon List Dispatch Canned Text Messages Add icon ([Insert])
Existing canned text messages can be edited or deleted as necessary. See Editing Items
222

Working with Container Types

MobileCast gives you the capability to use containers as a way to track the orders
associated with your routes. To help organize the containers, you can set up different
container types, each with a cost associated with it. For instance, you might set up
container types according to material, such as totes, pallets, bags, etc., or according to
size. Each container type you create is available to all your regions.
Hint: Unlike other items in the Maintenance module, you can add containers without
adding container types.
Step 2: Click on the List menu and select Dispatch, then Container Types. The
Container Type window opens, listing the existing container types.
Notes: Your menu will reflect whatever container alias you have entered on the Aliases
page of the Options notebook. Therefore, your menu might display something
other than container.
To see an updated list of container types click on the Refresh icon; the window
will be updated with all changed information from the database.
Step 3: In the Container Types window, click on the Add icon or press the [Insert] key.
The Add Container Type window opens.
Hint: To add an entry that is similar to an existing entry, right-click on the existing one
and select Clone from the menu that pops up. The Add Container Type window
the new container type.
You can create
container types to
organize your
containers.
Step 4: Enter up to 3 characters as the Type ID. This field must be completed.
Step 6: To associate a color with your container type, click the Color arrow and click on
a color to select it.
Step 7: Enter the cost, weight, and capacity of your container type.
Operations Guide
223
Step 8: In the Dimensions section, enter the length, height, and width of your container
type.
Step 10: When all the container types have been added, click the Close box to close the
Add Container Type window.
Maintenance icon List Dispatch Container Types Add icon ([Insert]) Save icon
([Ctrl]+[S])
Existing service pattern sets can be edited or deleted as necessary. See Editing Items and
224

Working with Containers

MobileCast gives you the capability to use containers to track orders for your routes.
Containers can be anything you use to package your orders, such as totes, pallets, bags,
etc. To help you organize your containers, you can use container types. Or, you can simply
add your containers without using types. You can track reusable containers from delivery
to pickup, and you can also use the Import module to import disposable containers on a
daily basis. You can add containers individually or import them; see Importing
Maintenance Items for more information on importing containers.
Step 2: Click on the List menu and select Dispatch, then Containers. The Containers
window opens. The current list of containers will not appear; to see the current
list of containers, or selected containers, use the Search feature at the bottom of
the window.
Notes: Your menu will reflect whatever container alias you have entered on the Aliases
page of the Options notebook. Therefore, your menu might display something
other than container.
To see an updated list of containers click on the Refresh icon; the window will be
updated with all changed information from the database.
Step 3: In the Containers window, click on the Add icon or press the [Insert] key. The
Add Container window opens.
Hint: To add an entry that is similar to an existing entry, right-click on the existing one
and select Clone from the menu that pops up. The Add Container window opens
with some information completed; change the information as necessary for the
new container.
Step 5: Click on the arrow next to the Type field and click on the correct container type.
If you do not want to associate a type with the container, select None.
You can choose to
associate a container
with any location.
Step 6: Click on the arrow next to the Location Type field, and select the type of the
location associated with the container. This field must be completed.
Operations Guide
225
Step 7: In the Location ID field, enter the ID of the where the container is located. If
you dont know the ID, click the [Query] button to search for the correct location.
This field must be completed.
Step 9: When all the containers have been added, click the Close box to close the Add
Container window.
Maintenance icon List Dispatch Container Add icon ([Insert]) Save icon
([Ctrl]+[S])
Existing containers can be edited or deleted as necessary. See Editing Items and Deleting
226

Working with Wireless Devices

Wireless devices allow the driver to communicate directly with the MobileCast system,
without going through the dispatcher. To use the wireless system, the driver keys the
message into the wireless device and the message is automatically transmitted to the
MobileCast server. There it is read and processed, and MobileCast automatically
performs the function, such as completing the stop, and the updated information can be
seen on the dispatchers computer screen. If MobileCast sees a problem with the function
being completed as sent from the driver, an error message is listed in the wireless events
so that the dispatcher can review the event and edit it as necessary before MobileCast
updates the system. See Working with Wireless Events for more information.
If your drivers are downloading routes using RN Mobile devices or WAP-enabled
phones, you do not need to add wireless devices to MobileCast. If the mobile device you
are using is an earlier model that you assign to routes, you will need to add the wireless
devices to MobileCast as described below.
Step 2: Click on the List menu and select Dispatch, then Wireless Devices. The
Wireless Devices window opens listing all current devices.
Note: To see an updated list of wireless devices click on the Refresh icon; the window
Step 3: In the Wireless Devices window, click on the Add icon or press the [Insert] key.
The Add Wireless Device window opens.
Hint: To add an entry that is similar to an existing one, right-click on the existing one
and select Clone from the menu that pops up. The Add Wireless Device window
the new wireless device.
The Add Wireless Device window
allows you to enter information
about your devices.
Step 4: Enter the ID of the wireless device.

Step 5: Click on the arrow next to the Provider field and click on the proper provider.
Step 6: Enter a Description for the device, if desired.
Step 7: Verify that a check is present in the Enabled box if the device is functioning.
Operations Guide
227
Step 9: Repeat Steps 3 - 8 to add more wireless devices as necessary. When all devices
have been added, click the Close box to close the Add Wireless Device window.
Note: Once a wireless device is added, it can be assigned to a driver or a piece of
equipment. It can also be changed or deleted as necessary.
Maintenance icon List Dispatch Wireless Devices Add icon ([Insert]) Save
icon ([Ctrl]+[S])
Existing wireless devices can be edited or deleted as necessary. See Editing Items and
228

Working with Route Exception Rules

You can create your own route exception rule for a situation that you want to keep track
of. For instance, you can create a rule for when a driver goes off a planned route for a
specified period of time. An exception rules wizard guides you through a step-by-step
process to easily create your route exception rules. You can define conditions that will
cause an exception to occur. When a route satisfies the conditions that you define, an
exception displays in Dispatcher. You have the option to indicate whether or not an
exception needs to be acknowledged, as well as have route exception alerts emailed to
you, as the exception occurs. As you create an exception rule, the bottom panel of the
wizard maintains a running display of the options you selected.
Step 2: Click on the List menu and select Dispatch, then Exception Rules. The Route
Exception Rules window opens, listing any exception rules that exist.
Note: Pre-existing route exception rules with the letters MC are for MobileCast routes
and OT are for OnTrack routes, for instance LATEGPS-MC indicates a
MobileCast exception. You cannot delete these route exception rules, but you can
clone them to make new route exception rules, as desired.
Step 3: Click the Add icon to create an exception rule. The Route Exception Rule Setup
window opens.
Step 4: Enter up to 15 characters for the Rule ID. This field must be completed.
Step 5: Enter up to 64 characters for the Description, if desired.
Step 6: Enter the email address(es) of the person that will receive an email that an
exception has generated, then choose either Short or Long in the Email Format
section.
Note: If you enter multiple email addresses, separate each one with a semicolon. A Short
email format provides minimal information for the route exception, while a Long
email format provides a detailed description. If you wish to receive the alerts on
your cell phone, choose Short, while office users may want to choose Long.
Step 7: If the route exception needs to be acknowledged when it occurs, check Requires
Acknowledgement. Exceptions that do not require an acknowledgement will not
show up in Route Watch.
Step 8: To have exceptions generated based on the route exception rule, check Enabled.
Operations Guide
229
Important: You must enable route exception rules in order for MobileCast to generate
route exceptions.
The Route Exception Rule Setup

window allows you to set the
options for route exception rules,
such as whether or not the
exception requires an
acknowledgement.
Step 9: Enter the character you want to appear for the exception as the Map Display
Character.
Note: Multiple exceptions occurring at the same location, or overlapping on the map, will
be indicated by three exclamation points (!!!), no matter what character you chose
to represent each individual exception.
Step 10: Click the [Next] button. The Application window opens.
Step 11: Select the application(s) to which the route exception rules will apply.
If you want the exception rules to apply to routes that are typically used for
delivery or pickup by drivers, select MobileCast.
If you want the exception rules to apply to routes that are typically used by
sales and merchandising teams, select OnTrack.
If you want the exception rules to apply to MobileCast and OnTrack, select
Both MobileCast and OnTrack.
Note: The options available throughout the wizard can be limited by the application for
which the rule is being created, when it is being processed, and the parameters that
are being tracked. For more information on which parameters can be combined
within the same exception, contact Roadnet Technologies Customer Support.
230

Step 12: Click the [Next] button. The Processing Trigger window opens.
If you choose Event Based, the

choices you see in the Events
section will depend on what you
selected on the previous
Application page (MobileCast or
OnTrack or both). For example,
if you choose Both MobileCast
and OnTrack, only events that
are common to preplanned and
unplanned routes are shown.
Step 13: Specify when you want the route exceptions to be processed. On the following
pages, you will be able to define the conditions that will cause an exception to
occur.
Continuallyexceptions are created as they occur.
Time of Dayexceptions are generated once per day at the specified time. Enter
the time manually or use the small arrows to scroll to the time, and then click on
the arrow to select the appropriate time zone.
Note: Time of Day will process based on a 24-hour clock, so enter 1:00 PM as 13:00.
Event Basedexceptions will be generated when an event(s) occurs. In the
Events section, select the appropriate event(s).
Note: The options available in the following windows will depend on the processing
trigger selected.
Step 14: Click the [Next] button. The Parameter Group Selection window opens
displaying the list of parameter groups.
Operations Guide
231
Step 15: Select the parameter group that you are interested in tracking. For example, to
set the parameters for triggering line item exceptions, select Line Item
Parameters.
As you move through each page,

the bottom panel of the window
will display a description of the
options in the order in which you
select them. To quickly return to
the option that you want to edit,
simply double-click the
appropriate option or right-click
and select Edit from the menu
that pops up.
Step 16: Click the [Next] button. The Parameters window opens.
Note: The parameters that will be available for you choose will depend on the options that
you selected on the previous pages; therefore, all the parameters for that parameter
group may not be available.
Step 17: The left panel displays a list of parameters for the parameter group, that when
selected, displays the condition(s) in the right panel, if applicable. Check the
appropriate parameter in the view and specify the settings for the parameter.
Repeat this step for additional parameters.
To set the parameters that require comparing values, such as when a device is
out of contact for a certain amount of time, you must enter at least one value. If
you need to specify a time, such as the amount of time you missed the departure
by, manually enter the time or use the arrows to scroll to the correct time. When
entering the time, use a 24-hour clock, so enter 1:00 PM as 13:00.
To set the parameters that require you to add one or more maintenance
items, such as an employee type, click the [Add] button. The Lookup window
opens. Double-click on an item, or click on the item and then on the Process icon
to select it.
232

Note: Click the [Add] button for each maintenance item you want to add. For example,
to add 3 employee types, you would click the [Add] button 3 times.
In the Parameters window, you

can specify the settings for the
parameters that will make them
exceptions.
To set the parameters that require you to complete a field, enter the
appropriate information. If necessary, you can use wildcards (* and ?) for
parameters that require you to enter text. For example, you can enter BALT100*
in the Route ID field, for all route IDs that begin with BALT100. You cannot use
wildcards for parameters that only accept numeric values, such as the amount of
time you missed the departure by.
To set the parameters for a quantity, such as the size for a planned delivery,
click the arrow and select the appropriate size alias, then provide the value(s) for
comparison.
To set the parameters for user-defined data, choose the User Defined Data
Parameters in the Parameter Group Selection window, and click the [Next] button.
The User Defined Data Parameter Setup window opens. Select the user-defined
table that has the data you are interested in tracking, then the user-defined date/
time column for that table, which has the exception time that you entered for when
the exception occurred.
Note: In order to see the user-defined tables and user-defined date/time columns in the
lists, you must first create them in the Roadnet Transportation Suite database; see
the Roadnet Transportation Suite Web Services for more information.
Operations Guide
233
Important: It is recommended that you select a custom date/time column that has the
time when the data was recorded, and not the default **Date Modified** column
because the custom date/time column has the time of when your exception
occurred. The time of the exception will appear in the Exception Time column of
Route Watch and in the Route Exceptions list window for the particular route.
Click the [Next] button. The Parameters window for the user defined data opens.
Check the appropriate parameters, then specify the conditions, as necessary.
Note: In Transit means that the exception occurs when the route is in between scheduled
locations (stop or depot). In Transit includes breaks, waits, and layovers. If you
check In Transit, then it is recommended that you check at least one user-defined
column parameter so that you can define a condition while the route is in transit.
For instance, if you want to know if the vehicle door is open while the driver is in
between stops, you would select In Transit and the appropriate column for an open
door. You can select a column(s) without having to check In Transit.
Step 18: Click the [Next] button. The Finished? window opens.
Step 19: If you want to specify more parameters that you are interested in tracking
for this rule, click the [Next] button. Repeat Steps 14-16.
OR
If you are finished selecting the parameter(s), click the [Finish] button to save
the rule.
Once the route exception rules have been created, they can be edited, deleted, or cloned,
as necessary. See Editing Items, Deleting Items, and Cloning Items for more information.
234

Working with Location Types

Location types allow you to specify the kinds of locations you have. Normally, the
location type is simply an ID and a description, but you can assign the types to your
locations to distinguish depots from customers from vendors, to separate departments in
a grocery store any number of uses. If you are using location types to differentiate
between various departments in a single store, such as a grocery store, you can have the
Roadnet Transportation Suite automatically synchronize selected fields for each type
when you add or edit a location; see the Location page of Setting the Options for more
information. If you are using the accounting portion of MobileCast, you can associate a
track type with each location type to help determine the cost of delivering to that type of
location.
The Roadnet Transportation Suite comes with two default location types: depots (DPT)
and sites (SIT), but you can add as many as needed. If you are using OnTrack in the
passive mode, you will want to add a location type of DPD.
Note: Do not add a location type of LD; that location type is reserved for load
functionality in MobileCast.
Step 2: Click on the List menu, then Locations, then select Location Types. The
Location Types window opens, listing all current types.
Note: To see an updated list of location types, click on the Refresh icon; the window will
Step 3: In the Location Types window, click on the Add icon or press [Insert]. The Add
Location Types window opens.
entry.
Step 4: Enter up to 3 characters as the type and up to 30 characters as the description.
The type must be entered.
The Add Location Type window
allows you to specify a type and
description for each location type
you add.
Step 5: If you using track types to track accounting costs in MobileCast, click the Track
Type arrow and select a track type to associate with the location type.
Operations Guide
235
Step 6: Click on the Save icon, or press [Ctrl]+[S] to save the new location type.
Step 7: Repeat Steps 4 - 6 to add any other location types.
Step 8: When you are finished adding location types, click the Close box to close the
Add Location Type window.
Maintenance icon List Locations Location TypeAdd icon ([Insert]) Save
icon ([Ctrl]+[S])
Existing location types can be edited or deleted as necessary. See Editing Items and
Important: Deleting location types affects other maintenance items. Before you delete
location types, you should delete locations with that location type.
236

Working with Locations

Locations are the customers you deliver to, the depots you use, the vendors from whom
you purchase product anywhere you might send a piece of equipment. The Roadnet
Transportation Suite places the locations on a map according to their geocodes (latitude
and longitude). You can associate many features with a location, including the address,
phone, and fax number; account, time window, and service time types; and time window
and service time overrides. Locations can be imported through the Import Module or
added individually. See Importing Locations for more information on using the Import
module to import locations. Location types must be added before locations can be added.
Step 2: Click on the List menu, then Locations, then Locations. The Locations window
opens, listing all current locations. The current list of locations will not appear.
This makes the system run much faster than if the complete list were loaded
every time. To see the current list of locations, or just specific locations, use the
Search feature.
Note: To see an updated list of locations, click on the Refresh icon; the window will be
Step 3: In the Locations window, click on the Add icon or press [Insert]. The Add
Location window opens. The left side of the Locations window displays the ID
and type for the location currently being worked with. The right side of the
window is a notebook with several pages:
Attributescontains name, address, and phone information for the location. All
required information is on this page.
Extended Attributescontains additional information for the location, such as
instructions, fee, zone, and priority details, as well as other information.
Equipment Typeslets you assign specific equipment types to the location.
When the location is routed, it will be placed on a route with this type of
equipment, unless it is part of a standard route.
SKUsonly available when Current Type is set to DPT, this page lets you assign
specific products to mid-route source depots.
Time Window Overrides contains information about the locations time
windows on specific days.
Service Time Overrides contains information about the locations service
times on specific days.
Dispatchcontains information specific to MobileCast.
Location Extensionscontains information that is used by Territory Planner
when creating strategic routes.
Operations Guide
237
FleetLoaderlets you choose the options that will be used when FleetLoader
loads your equipment.
Mapcan be used to geocode the location or simply see where it is geocoded.
entry.
Step 4: Enter the ID for the location. This field must be completed.
Only the first page of the Location notebook needs to be completed, the
remaining pages contain optional information.
Step 5: Click on the Current Type arrow to open a list of location types. Click on a
location type to select it. This field must be completed.
Note: If Synchronize Maintenance Items is checked on the Locations page of the Options
notebook, several location types may be selected in the Location Types list; these
are the types selected in the Options notebook to be synchronized. As you enter
information for the current type, any synchronized fields will be completed for all
selected types.
238

Step 6: Enter the location information in the notebook. See Using the Location
Notebook for more information. The Attributes page must be completed but all
other information is optional.
If you are synchronizing maintenance items to add different types for the same ID
simultaneously:
When you are finished with the first location type, click the Current Type arrow
and choose the next location type to work with. All the information in the fields
selected for synchronization will already be completed, you will only need to enter
information for the unsynchronized fields.
Step 8: When all locations have been entered, click the Close box to close the Add
Location window.
Maintenance icon List Locations LocationsAdd icon ([Insert]) Save
icon ([Ctrl]+[S])
Notes: If you want to replace specific information for multiple locations, such as
changing the service time type, select the locations in the Locations window.
Right-click on a selected location and select Replace from the menu that pops up.
Check the item to be replaced (Service Time Type), enter the new information,
and click the [OK] button, then click [Yes] to confirm you want to want to make
the change. The new information is entered for all the selected locations.
If you want to delete the service time overrides or time window overrides for
multiple locations, select the locations in the Locations window. Right-click on
a selected location and select Delete Overrides from the menu that pops up. Verify
the proper box is checked (Service Time and/or Time Window) for the type of
override you want to delete, and select the scenarios you want to delete overrides
from. Click the [Delete] button. A message appears telling you how many
overrides will be deleted; click [OK] to proceed.
If you are editing locations with types that are synchronized, and you do not
want the other types to be updated with the new information, make sure
Synchronize same IDs is not checked.
Existing locations can be edited or deleted as necessary. See Editing Items and
Deleting Items for more information.When you delete a location it will be
removed from any standard routes it is on; in addition the corresponding location
extension will also be deleted.
Operations Guide
239
Using the Location Notebook

The Location notebook lets you enter information about your delivery locations. You can
open the Location notebook to add a new location or edit an existing location. To add a
new location, click the Add icon on the Locations window. To open the Location
notebook and edit an existing location, double-click on the location in the Locations
window. The Attributes page of the notebook contains all the required information,
although you may want to use the Map page to see where the location is geocoded. If you
are using Territory Planner for strategic routing, you need to complete the Location
Extension tab as well. If you are using MobileCast to track your routes throughout the
day, you may need to complete information on the Dispatch page.
Entering Location Attributes
The Attributes page of the Location notebook allows you to enter or modify the address
information for a location. This information can be used to geocode the location. You
must also select a service time type, time window type, time window factor, and account
type for the location.
Step 2: Enter the address information for the location. Click on the Cross Street button
to add a cross street if necessary. The more complete and correct address
information you provide, the easier it will be to geocode the location.
Note: Use the actual street address. Do not use P.O. Box numbers, route numbers, RR
numbers, or intersections as these formats may not geocode automatically.
Step 3: Click on the arrows and select the time window type, service time type, time
window factor, and account type from the respective Lookup windows, if
necessary.
Hint: The maximum Time Window Factor of 5 should be used sparingly only when it
is absolutely essential that the time window(s) be met.
240

Step 4: Enter the phone and fax numbers, if appropriate. Do not type the parentheses or
dash; they will be entered automatically.
The address you enter on the Attributes page will be used to geocode the location.
Step 5: Remove the checks from the Delivery Days boxes for the days the customer
does not receive deliveries. If the customer receives deliveries on Monday,
Wednesday, and Friday, remove the checks from T, R, S, and U. This information
is used to determine if a scheduled delivery is an off-day delivery.
Step 6: Select the time zone for this location. All of the locations times will be
displayed using this time zone.
Step 7: If the Current Type is set to DPT, click on the Depot Color arrow to open a
color palette. Click on a color to select it. This is the color that will be used to
represent the depot on the map.
Step 8: Click the Save icon, or press [Ctrl]+[S] to save the information, or click on
another tab to enter additional information about the location.
Operations Guide
241
Entering Extended Attributes
The Extended Attributes page of the Locations notebook allows you to enter or modify
additional information about a location, such as the instructions, fees, zone, and priority
details, as well as other information. All of the information on this page is optional.
You can enter additional information about the location on the Extended Attributes page.
Step 1: Enter any Standard Instructions. These instructions will apply to all deliveries
and will appear on the drivers manifest.
Step 2: Enter any fees associated with the location. A fee is a charge applied every time
the location (usually a depot or terminal) is visited. The fixed fee is the fee for
servicing (delivering, reloading, or emptying) the location. The variable fee is
based on cost per unit delivered and is used by the location to control cost. For
example, if the variable fee is $10, then quantity measured as the unit of cost for
that location is multiplied by $10 and added to the fixed fee to equal the
location's total fee. The total fee will be applied to the route cost every time the
location is visited.
Step 3: If necessary, use the arrows in the Priority field to assign a number from 1 to 9,
which indicates the importance of delivering to that location first. The default
number is 0. The highest priority is 9.
242

Step 4: Click on the Zone arrow to open the Lookup windows and select a zone for the
location. You can group locations by zone when creating routes in the Routing
Editor.
Step 5: In the Pref. Rte. ID field, enter the ID of the route the location should be placed
on when routes are created in the Routing Editor. If you are using Preferred
Route ID routing, orders for this location will be placed on this route. If you are
not using Preferred Route ID routing, you can leave this field blank.
Step 6: Enter the store number, if appropriate.
Step 7: In the Building Delivery Sequence field, enter a number indicating the
sequence the location should be delivered in a large building that contains
multiple locations. When routes are created or sequenced, if this location is on a
route with other locations that have the same latitude and longitude, it will be
sequenced according to the number entered in the Building Delivery Sequence
field. The locations are sequenced so that the lowest building delivery sequence
number is delivered first.
Hint: When assigning building delivery sequence numbers for a given building, you may
want to leave spaces between numbers to insert new customers as they are added.
For instance, instead of giving three locations in a building delivery sequence
numbers of 100, 101, and 102, give them numbers like 100, 105, and 110, leaving
room to add new customers who should fall between them when being delivered.
Step 8: In the Delivery Radius field, enter the distance surrounding a location that the
driver must travel into for MobileCast to automatically consider that the driver
has arrived at the stop. The drivers equipment must not move within this circle
for the amount of time specified in the RTS.Telematics.Adapter.exe.config file or
either of the minimum stop time fields on the Dispatch - Java Phone page for the
stop to be auto-arrived in MobileCast. When the equipment leaves this area,
MobileCast considers that the driver has departed the stop. Enter the distance in
miles.
Note: The Delivery Radius is used with the Roadnet Telematics Adapter, On Track, and
auto-arrive/depart.
Step 9: In the Bulk Threshold area, enter the quantity an order must contain to be
considered a bulk delivery.
Step 10: In the When Importing Orders section, you can void all further orders for a
location, or you can have orders for different locations routed together using the
address of a single location.
To void all orders for the current location, check the Mark Any Orders For This
Location as Void box.
To substitute the current location to receive orders originally assigned to a
different location, click the [Add] button and enter the Location ID and Location
Type of the location you wish to transfer. The Location will appear in the
Operations Guide
243
Substitute This Location For Original Orders From box. Click the [Remove]
button to cancel the transfer and remove the location from the window.
Step 11: In User Defined Fields 1, 2, and 3, enter any additional information or
instructions associated with the location.
Note: The names of these fields will vary depending on the settings in Options notebook.
For more information, see the Alias defaults page.
Assigning Equipment Types to Locations
The Equipment Types page of the Locations notebook allows you to assign one or more
equipment types to a location. Equipment types can be taken into account when routing
stops in the Routing Editor or when assigning locations to territories in the Planning
Editor.
When routing a stop or assigning a location, it will be placed on a route or in a territory
with one of the assigned equipment types. If no equipment types are assigned to the
location, it will be placed on a route or in a territory without regard to the equipment type.
If none of the equipment types are available, a stop will not be routed and a stop exception
will occur in the Routing Editor, as well, a location will not be assigned to a territory. If
the stop is part of a standard route, the equipment type assigned to the standard route will
be used instead of the one assigned to the location.
244

Step 1: In the Available list, select the equipment types to be assigned. To select multiple
types, hold down the [Ctrl] key while clicking the types.
When creating routes in the Routing Editor, you can have the location only
assigned to routes using one of the specified kinds of equipment.
Step 2: Drag the selected equipment types to the Assigned list.

Entering Depot SKUs
Note: The SKUs page only displays when the Current Type is DPT.
If Mid-Route Sourcing is enabled and you do not assign SKUs to a depot, that
depot will be ignored during routing.
The SKUs page of the Locations notebook allows you to define which SKUs are accepted
and distributed at the location, as well as the fee for accepting an item. In the waste
industry, a mid-route source depot may charge a fee depending on the type of waste or
container they are accepting or distributing. In addition, they may be limited in what they
handle, recyclable materials, general waste, large or small containers, etc. Not only can
you specify what they accept, you can include the cost or profit for each item accepted.
Operations Guide
245
Step 1: In the SKUs list, select the item to be assigned to the location.
When creating mid-route sourcing depots in the Routing Editor, you can
specify if a location accepts or distributes a specific SKU.
Step 2: If this location accepts the item, check Accepts. The cost fields become
available. Enter the costs associated with the item for each size alias.
Notes: The names of your Sizes are established on the on the Alias page of the Options
notebook.
Costs can have a positive or negative value. For example, a positive value, or
charge, could be assigned if the depot accepts liquid waste, where as a negative
value, or payment, could be assigned for something like a recyclable material.
Profit is entered by placing a negative sign in front of the number in the cost field.
Step 3: If this location distributes the item, check Distributes.
Step 4: Click the [Update] button.
Step 5: Continue with other SKUs, as necessary.
246

Entering Time Window Overrides
The Time Window Overrides page of the Location notebook allows you to enter time
windows for specific days and scenarios. If a location has a different time window for
Monday than it has for the rest of the week, you can enter the times for Monday on this
page and not affect the time windows for the rest of the week. All of the information on
this page is optional. If entered, the overrides will be used in place of any time windows
set up in the locations time window types.
Step 1: Enter the open and close times and preferred delivery times for the time window
override. To enter a time, click in the box to enter a check for the field, then either
type the time or use the small arrows to scroll to the time. Make sure the correct
part of the time (hours or minutes) is selected when you are entering the time.
You can use the Time Window Overrides page if the location has different time
windows on one day of the week.
Operations Guide
247
Open/Close Timesare the earliest and latest possible times the location can
receive a delivery, not when it opens and closes for business. Enter a start (open)
and end (close) time.
Time Windows 1 and 2are the times that location prefers to receive a delivery.
Enter a start (earlier time) and stop (later time) for each time window if necessary.
Note: In order for the times to be accepted into the system, the complete time, including
minutes, must be entered.
Step 2: Click in the Days boxes to select the day(s) on which the time windows apply.
If the time windows apply for Monday, Wednesday, and Friday, click the boxes
under M, W, and F. If no boxes are checked, the override will be in effect for all
days of the week.
Step 3: Click the Scenario arrow and scroll to select the scenario in which the time
window(s) will be used.
Step 4: Click the [Add] button to insert the time window override in the list.
To change the times for an existing time window override, highlight that row
in the list and change the information as needed. Then click the [Update] button.
The information will be changed in the list.
To delete a row in an existing time window override, highlight that row in the
list and click the [Remove] button. The row will be deleted from the list.
Entering Service Time Overrides
The Service Time Overrides page of the Location notebook allows you to enter service
time overrides for specific days and scenarios. If a location has a different service time for
Monday than it has for the rest of the week, you can enter the times for Monday on this
page and not affect the service times for the rest of the week. All of the information on
this page is optional. If entered, the overrides will be used in place of any service times
established in the locations service time type.
Note: If you are using SKU service time, and you only want the SKU variable service
time to be considered, make sure the locations variable service time is set to 0.
Step 1: Enter the service times and bulk service times for non-helper and helper
deliveries.
Service timesare times spent delivering product to a location.
Bulk service timesare times spent delivering product on pallets. Bulk
quantities for the location are specified on the Attributes page. The bulk service
times will be used if the order is over the locations bulk threshold or if the order
is forced to use bulk service times.
248

Fixed service timeis the amount of time, independent of quantity of product

delivered, that it takes to service a location. Fixed service time includes parking
the truck, filling out paperwork, obtaining payment on COD orders, etc.
Variable service timeis the amount of time it takes to move one unit of product
from the equipment into the location receiving the delivery.
Note: In order for the times to be accepted the complete time, including minutes, must
be entered.
Enter service time overrides for particular days in the Service Time Overrides page of the
Location notebook.
Step 2: Click in the Days box(es) to select day(s) on which the service time overrides
apply. If the service time overrides apply for Monday, Wednesday, and Friday,
click the boxes under M, W, and F.
Note: If you do not select days, all days will be checked by default.
Step 3: Click the Scenario arrow to see a list of scenarios and scroll to select the
scenario in which the service times will be used.
Step 4: Click the [Add] button to accept the service time override.
Operations Guide
249
To change the times for an existing service time override, highlight that row in
the list and change the information as needed. Then click the [Update] button. The
information will be changed in the list.
To delete a row in an existing service time override, highlight that row in the
list and click the [Remove] button. The row will be deleted from the list.
Entering Location Extension Information
The Location Extension page of the Location notebook allows you to enter the
information that will be used by Territory Planner to create strategic routes. Location
extension information is specific to the planning session in Territory Planner, so you can
enter different location extension information for the different sessions that exist. For
each location extension, you must choose a territory, service pattern set, session, and
quantity for size 1. The remaining information is optional.
250

Step 1: In the Location notebook, click on the Location Extension tab.
When adding location extension information, you can select the planning sessions you
want it to be added to.
Step 2: Remove the check from the Do Not Use Extension With This Location box.
Note: When editing location extension information, make sure the Current Session is the
one you want to change. If not, change the current session to the one you want to
alter.
Step 3: Select the Territory and Service Pattern Set to assign to the location extension.
To open a list of territories/service pattern sets, click on the appropriate arrow,
then click on an entry to select it. If the territory you want to assign the extension
to does not exist, enter the name in the field.
Step 4: Enter the total quantity for the cycle in the appropriate size fields. The names on
the size fields will reflect the aliases entered in the Options notebook. Size 1
information is required, the remaining sizes are optional.
Step 5: Choose the planning sessions you want the extension information to be added
to. It will automatically be added to the Session Displayed; to add it to additional
sessions select them in the Sessions to Modify area.
Step 6: To assign the location extension to a territory in the selected planning
session(s). Click the Territory arrow and select the territory you want the
Operations Guide
251
extension assigned to. If this territory is not listed, type it in the field; it will be
automatically added.
Step 7: If the extension should use a different service time type in the selected planning
session(s), click on the Svc Time Type arrow to open the Lookup-Service Time
Type window. Double-click on the type you want the extension to use in the
planning session. If no service time type is selected, the service time associated
with the location will be used in the planning session.
Step 8: Enter any previous information you want included with the extension.
Step 9: Enter the number of days you want the extension moved when Day Shift is run
in the Day Shift area.
Note: Day Shift is a tool in Territory Planner that allows you to easily shift the delivery
days for a group of location extensions by a specified amount of time. This can be
very handy to route drivers to follow salespeople to the stops.
Step 10: To prevent the location extensions delivery days from moving more than a
certain number of days, click Select Day Range. In the box, enter the maximum
number of days from the Previous Days the location extension can receive its
deliveries when a re-route is done. For example, if the location extensions
Previous Day is Wednesday and you enter 1, the location extension could be
scheduled for delivery on Tuesday, Wednesday, or Thursday when a re-route is
done (as long as these days are allowed by the service pattern set). If you enter 0,
the location extension must be scheduled for delivery on Wednesday. To let the
range of allowed delivery days wrap across non-delivery days, check Allow
Wrap.
Note: If Any Day is selected, no day anchoring will be used. This will allow the location
extension to be scheduled for delivery on any day allowed by its service pattern
set when a re-route is done.
Step 11: To prevent the location extensions delivery weeks from moving more than a
certain number of weeks, click Select Week Range. In the box, enter the
maximum number of weeks from the Previous Weeks the location extension can
receive its deliveries when a re-route is done. For example, if the location
extensions Previous Week is week 7 of an 8 week delivery cycle and you enter 1,
the location extension could be scheduled to receive its delivery in week 6, week
7, or week 8 when a re-route is done (as long as these weeks are allowed by the
service pattern set). If you enter 0, the location extension must be scheduled for
delivery in week 7. To let the range of allowed delivery weeks continue through
the first and last week in the cycle, check Allow Wrap.
Note: If Any Week is selected, no week anchoring will be used. This will allow the
location extension to be scheduled for delivery on any week allowed by its service
pattern set when a re-route is done.
Step 12: To have the location extension routed using Assign Days, check Consider for
Assign Days. If this option is not selected, the extension will not be routed
automatically; you will need to route is manually.
252

Step 13: Enter the user-defined field information for the extension. To enter the
information, click on the field in the list; the header for the user-defined field
appears above the entry field to the right. Enter the text for the user-defined field
and click the [Set Value] button.
Note: The headers for the user-defined fields established in the User Defined Fields
window will be reflected here.
Step 14: Click the Save icon, or press [Ctrl]+[S] to save the location, or click on
Note: To enter location extension information for another planning session, double-click
on the location in the Locations window, then click on the Location Extension tab.
Enter the extension information for the new planning session.
Entering the FleetLoader Information
The FleetLoader page of the Location notebook allows you to choose the options that will
be used when FleetLoader loads your equipment. For instance, you can specify the
preferred pallet type that should be used for deliveries to the location. All of the
information on this page is optional.
Step 1: In the Location notebook, click on the FleetLoader tab to open that page.
Step 2: Click the Loading Preference arrow to choose a possible position the location's
order should be loaded on the equipment.
Step 3: Click the Preferred Delivery Pallet Type arrow to choose the pallet type that
should be used for deliveries to the location.
Note: The preferred delivery pallet type is the pallet type that is preferred by a particular
delivery location.
In FleetLoader, when stops are loaded for this location, they will be loaded on this
pallet type. When a location has a delivery of a single SKU that has enough to use
a manufacturer pallet type, then the manufacturer pallet type will be used instead
of the preferred delivery pallet type. Otherwise, if the order is not large enough for
Operations Guide
253
a manufacturer pallet type and the location does not have a preferred pallet type,
the default pallet type will be used to load the SKU.
Step 4: If this location accepts a delivery on a manufacturer pallet type, check Accepts
Manufacturer Pallet Types, which is the pallet type used to deliver the SKU to
your warehouse.
In the FleetLoader tab, you can specify the loading preference, the preferred
delivery pallet type and whether the location accepts a delivery on a
manufacturer pallet type.
Note: If the order is large enough, the manufacturer pallet type will be used to deliver.
Step 5: Click the Save icon, or press [Ctrl]+[S+] to save the information, or click on
Entering Dispatch Information
The Dispatch page of the Location notebook, opened when you add or edit a location,
allows you to enter advanced information about the location, including contact and
service failure information. All of the information on this page is optional.
254

Step 1: If the location wants to be notified of a delay in delivery, complete the Service
Failure Notification box.
Verify that a check is present in the Notify box. Click on the arrow to select a
service failure type; the options are sending an e-mail or sending a message to the
dispatcher. If e-mail is selected, enter the exact e-mail address of the person to be
contacted in the Contact field. Enter the minimum number of minutes the delivery
should be delayed before the customer is contacted.
Enter service failure and contact information in the Dispatch page of the location notebook.
Note: A notification will only be sent the first time the stop meets one of the following
criteria:
A stops projected arrival or departure time is outside both Time Window 1 and 2,
or outside the stops Open/Close time.
The stops projected arrival time is going to be more than the time allows in
Minutes to Notify.
The stop is canceled.
Step 2: Enter the names of the primary and alternate contacts, if necessary.
Step 3: To add a name to the list of consignees that drivers will have to choose from
on their handheld device, click the Add icon. The Add Consignee window
opens. Enter the consignees name and click the Save icon. You can then enter
more consignee names or close the Add Consignee window. Once there are five
consignee names in the list, you must delete a name before you can add a new
one.
Operations Guide
255
To delete a consignee name, click the name in the Consignee History area and
click the Delete icon. Press [OK] to confirm that you want to delete that name.
Step 4: Click the Save icon, or press [Ctrl]+[S] to save the information or click on
Geocoding the Location
The Map page of the Location notebook allows you to geocode the location. The geocode
assigns a latitude and longitude to the location, which is used when determining travel
time for your routes. When the page opens, the location is shown as a red bulls eye. The
geocode is based on the address information given on the Attributes page.
The location's address that you supplied is displayed in the Address box. The Roadnet
Transportation Suite automatically tries to geocode the location based on this address.
The Geocode Quality indicates the degree of accuracy with which the location has been
geocoded. You can change the location's address by clicking the [Edit] button. After
changing the address, you have the option to make the Roadnet Transportation Suite
attempt to re-geocode the location.
The Nearest Street Segment box displays the street segment the location is actually
geocoded to, based on the Roadnet Transportation Suite's map data. If the location is not
geocoded on a street, the Nearest Street Segment will be the street segment closest to
where the location is geocoded.
If the location does not geocode automatically, you can search the database to find a close
match for your location, or you can move the map to find the correct geocode for the
location. Complete the following steps to manually geocode the location.
256

Step 1: Click the [Display Candidates] button to search the database for street segments
and look for possible matches. The results of the search appear in the window.
By clicking [Display Candidates], you can search the database of street segments to find
a match for the location.
Step 2: Review the street segment candidates in the list. To view a candidate on the
map, right-click on the candidate and select Fit or Center. The map is redrawn
showing the candidate.
Step 3: To geocode the location to a street segment candidate, right-click on the
candidate and select Geocode. The location is assigned the same geocode as the
candidate.
Note: When you geocode a location by its street segment, the location will be geocoded
to the mid point of that street segment. This can result in inaccuracy, as the
location may not actually rest on the mid point of the street segment. You can use
the Center icon to manually change the geocode position on the map.
Step 4: Click the Save icon, or press [Ctrl]+[S] to save the information or click on
In addition to using the candidates, you can geocode directly on the map. Click the cross
hair cursor at the place where you want to geocode the location. You can use the Zoom
and Center icons to move around the map as needed, and then revert to the geocode mode.
Operations Guide
257
Notes: If you select Show listed locations, all existing geocoded locations currently listed
in the location view window will be plotted on the map. This can be useful if you
know that the location you are trying to geocode is close to an existing location.
When you geocode the location, the latitude and longitude are automatically
entered. If you are entering the latitude and longitude manually, click the [Edit]
button in the location area and enter them in some form of decimal degrees, up to
decimal degrees times million, including the decimal point and negative as
necessary (for example, -76.5982).
Hint: You can also geocode locations by right-clicking on the location(s) you want to
geocode to open the popup menu. Select Interactive Geocode to open the
Attributes and Map pages of the Location Notebook and geocode each location
individually. Select Batch Geocode to automatically geocode several locations at
once.
258

Working with Location Overrides

Location overrides allow you to temporarily override time windows and/or special
instructions for a location. This feature will nullify time window parameters and special
instructions established in the Location notebook; however, it will be bypassed when time
window information and/or special instructions are imported with the order(s). Once you
add location overrides, they will be applied until you delete them.
Step 2: Click on the List menu, select Locations, then select Location Overrides. The
Location Overrides window opens, listing all current location overrides.
Note: To see an updated list of location overrides, click on the Refresh icon; the window
Step 3: In the Location Overrides window, click on the Add icon or press [Insert]. The
Add Location Override window opens.
entry.
Step 4: Click on the ID arrow to see a list of locations. Double-click on the correct
location to insert that location into the ID field, or click once and then click the
Process icon.
When overriding a locations

time window information, all
fields need to be completed, not
just those that are changing.
Step 5: To add time window overrides, check the Override Location Time Windows
box. Enter your time window overrides in the Delivery Windows section.
Note: You must enter all applicable times, even if you are changing only one time
window.
Operations Guide
259
Step 6: To override existing special instructions or to add new ones, enter them in the
Special Instructions field.
Step 7: Click the Save icon, or press [Ctrl]+[S] to save the location override.
Step 8: When you are finished adding location overrides, click the Close box to close
the Add Location Override window.
Maintenance icon List Locations Location OverridesAdd icon ([Insert])
Important: Once you have added location overrides, they will be applied indefinitely. If
you are entering the overrides for a pre-determined duration of time (a day, week,
etc.), you must remember to edit or delete the override(s) as appropriate.
Existing location overrides can be edited or deleted as necessary. See Editing Items and
260

Working with Location Substitutions
Working with Location Substitutions

Used with: Roadnet
Location substitution allows you to assign one location address to two or more locations.
For example, if you have several stops within one building different floors, departments,
etc. you may choose to group them so that they are represented by one address in order
to avoid having them routed separately. Additionally, one location may be temporarily
unable to receive orders and may wish to have its orders delivered to a neighboring
location. Location substitutions can also be entered using the Location notebook.
Step 2: Click on the List menu and select Locations, then Location Substitutions. The
Location Substitutions window opens.
Note: To see an updated list of location substitutions, click on the Refresh icon; the
Step 3: In the Location Substitutions window, click the Add icon or press [Insert]. The
Add Location Substitution window opens.
entry.
Step 4: Enter the Original Location ID and the Original Location Type for the location
you want to change.
Step 5: Enter the New Location ID and the New Location Type of the location address
that you want to substitute for the original location address.
Step 6: Click the Save icon, or press [Ctrl]+[S] to save the location substitution.
Step 7: When you are finished adding location substitutions, click the Close box to
close the Add Location Substitution window.
Maintenance icon List Locations Location SubstitutionsAdd icon ([Insert])
Existing location substitutions can be edited or deleted as necessary. See Editing Items
Operations Guide
261
Working with Void Locations
Working with Void Locations

Used with: Roadnet
Void locations allow you to prevent a specified location from receiving orders; the
location, however, is not removed from the database. You might choose to use this option
if a customer hasnt paid a bill or if the customer no longer wants to be serviced but you
want to keep the location for reporting purposes. Void locations can also be entered using
the Location notebook.
Step 2: Click on the List menu, select Locations, then Void Locations.
Note: To see an updated list of void locations, click on the Refresh icon; the window will
Step 3: In the Void Locations window, click the Add icon or press [Insert]. The Add
Void Locations window opens.
entry.
Step 4: Enter the Location ID and Location Type, and click the Save icon or press
[Ctrl]+[S] to save the void location.
Step 5: When you are finished adding void locations, click the Close box to close the
Add Void Location window.
Maintenance icon List Locations Void LocationsAdd icon ([Insert]) Save
icon ([Ctrl]+[S])
Existing void locations can be deleted as necessary. See Deleting Items for more
information.
Hint: Void locations can also be added and deleted on the Extended Attributes page of
the Location Notebook.
262

Working with Loading Preferences

Loading preferences allow you to restrict the area of a truck where a particular locations
orders will be loaded. This is helpful if an area of the truck is inaccessible at the stop, such
as if the dock is located in a narrow alley. This information is used when loading trucks
if the Driver Friendly or one of the Hybrid methods is selected in FleetLoader. You can
also add Loading Preferences on the FleetLoader page of the Location notebook.
Step 2: Click on the List menu and select Locations, then Loading Preferences. The
Loading Preferences window opens.
Note: To see an updated list of loading preferences, click on the Refresh icon; the
Step 3: In the Loading Preferences window, click the Add icon or press [Insert]. The
Add Loading Preference window opens.
entry.
Step 4: Enter the Location ID and Location Type in the correct fields. These fields must
be completed.
If you are using Driver Friendly or

one of the hybrid methods to load
your trucks in FleetLoader, you can
specify where in the truck you want
a locations orders loaded.
Step 5: Click the Quadrant arrow and select the area of the truck you want that
locations product loaded into. That locations orders will be loaded in the
selected quadrant.
Step 7: Continue adding loading preferences as needed. When all have been added,
click the Close box to close the Add Loading Preference window.
Maintenance icon List Locations Loading PreferencesAdd icon ([Insert])
Operations Guide
263
Existing loading preferences can be edited or deleted as necessary. See Editing Items and
264

Working with User Defined Fields
Working with User Defined Fields

User-defined fields let you store additional information about your location extensions
that is not provided by Territory Planner. For instance, if you deal with chains and each
store has a number, you could enter the store number as a user-defined field. The
information stored in the user-defined fields is not used by Territory Planner, but is
displayed with the location extensions and can be imported and exported. User-defined
fields can be alphanumeric or numeric only; if a field is designated as numeric, the totals
for the column will appear in the Location Extensions window, the Stop List, and any
other windows the columns appear in.
Below are instructions for creating the column headers, or names, for the user-defined
fields. The user-defined field information for each individual location extension is entered
in the Location Extension page of the Location notebook.
Step 2: Click on the List menu and select User Defined Fields. The User Defined Fields
window opens, displaying all existing user-defined field.
Note: To see an updated list of user-defined fields, click on the Refresh icon; the window
Step 3: In the User Defined Fields window, click the Add icon or press [Insert]. The
Add User Defined Field window opens.
entry.
Step 4: Enter the Description for the user-defined field. The description will appear in
the column headers and in the Location Extensions notebook.
Step 5: If the field will only contain numeric information, check the Numeric box.
Numeric columns will be totaled in the Location Extensions window.
Step 7: Repeat Steps 4-6 until all user-defined fields are added. Click the Close box to
close the Add User Defined Fields window.
Maintenance icon List User Defined FieldsAdd icon ([Insert]) Save icon
([Ctrl]+[S])
Existing user-defined fields can be edited or deleted as necessary. See Editing Items and
Operations Guide
265
Working with Rush Hour Model

Used with: Roadnet, Territory Planner, MobileCast, netScheduler
In many areas, traffic patterns change throughout the course of the day due to the
increased or reduced amount of traffic on the roads. For instance, on a 3 mile stretch of
road where you normally drive 60 MPH you may only be able to drive 30 MPH during
certain times of day. The Roadnet Transportation Suite allows you to create a rush hour
model that compensates for traffic patterns that vary during the day. You can even create
separate models for different times of year. For instance, you may be routing in a resort
area where summer traffic is much heavier than winter traffic, so you could create a
summer model and a winter model with different speed variations. When routing you can
choose the appropriate rush hour model for the session you are working with.
Rush hour models can range from very basic to very complex. You can create a rush hour
model that simply changes the speed for all roads during specified time periods, or create
areas where the speeds are altered, or even change the speed or direction on individual
streets during the rush hour time.
Each rush hour model can have up to three time periods, not including the normal time
period, so you could have a morning, lunch, and then evening time period, as well as
normal traffic. To create areas or rush hour information for specific streets, use the map
to draw the areas and street paths and specify their rush hour attributes.
Setting up a rush hour model is a one-time process. Once you have created the model, you
can assign it to be used for netScheduler, Dispatcher, and for different routing and
planning sessions. The rush hour model can be used with XY, RouteNet, or the
SuperMatrix as the time distance calculator. If a session uses XY, you can use a rush hour
model with rush hour areas, where the speeds are altered by the specified amount during
the defined times of day. If the session uses RouteNet or the SuperMatrix, you can use a
model that specifies rush hour information for areas or individual streets, including
directional changes. In addition, you can choose to have the rush hour information
considered when the route paths are created or only considered when the travel times are
calculated for the route. See Setting the Options and Working with Planning Sessions for
more information.
The first step in working with rush hour models is to create the models. Once the model
has been created, you can create the rush hour areas and paths for the model.
266

Creating the Rush Hour Model
The first step in setting up rush hour information is to create the rush hour model. For each
rush hour model you can define up to three distinct time periods, each of which can have
separate speed variations and other attributes assigned. For instance, you can define a
morning and evening time period where speeds are reduced, and then a midnight time
period where speeds are increased.
You can create rush hour models only in the Maintenance module, although you can edit
an existing model in the Dispatcher, Planning Editor, or Routing Editor.
Note: If you were not granted permission to edit rush hour models in the Administration
module, you will not be able to add a rush hour model.
Step 2: Click on the File menu and select Map. The map opens.
Step 3: Click on the Map Options icon and select Properties from the menu. The Map
Properties notebook opens.
Step 4: Click on the Rush Hour tab. The Rush Hour page opens.
Step 5: To add a new rush hour model, click the Current Rush Hour Model arrow. The
Rush Hour Models window opens.
Step 6: Click the Add icon. The Add Rush Hour Model window opens.
The time periods defined

cannot change for
different areas and paths.
The speed variations for
the paths and areas can be
different however.
Step 7: Enter a Name and Description for the rush hour model. You must enter a name.
Step 8: Check the Enable box for Time Period 1.
Step 9: Enter a name or leave the default, then enter a starting and ending time for the
rush hour period.
Operations Guide
267
Step 10: Choose whether to increase the speed (Faster) or decrease the speed (Slower).
The new speed will be used when the travel time is calculated.
If you increase speed by 25%, 60 MPH becomes 75 MPH.
If you decrease speed by 25%, 60 MPH becomes 45 MPH.
Important: Any speed variations entered here will be used for all streets that are not
included in other rush hour areas or paths.
Step 11: Continue for the remaining time periods as necessary. Some things to
remember when adding a rush hour model:
The ending time for each time period must occur after the starting time.
The time periods cannot overlap. However, a new time period can start at the
same time a previous time period ended.
You can enter the time manually, or use the arrows to scroll to the correct
time. If entering the time manually, use the arrow keys to move from the hour to
minute field. If using the scroll arrows, click on the correct field (hour to minute)
before scrolling. Use a 24-hour clock when entering the time. For example, enter
1:00 PM as 13:00.
Step 12: Click the Save icon, or press [Ctrl]+[S] to save the rush hour model.
Step 13: Repeat Steps 6-12 to add additional rush hour models. When all necessary
rush hour models have been added, click the Close box to close the Add Rush
Hour Model window.
Maintenance File Map Map Options icon Add icon Save icon
Existing rush hour models can be edited or deleted as necessary. See Editing Items and
Deleting Items for more information. To create a new model with the same areas and
paths, you can clone the existing model. See Cloning Items for more information.
Once you have added your rush hour models, you can create rush hour areas and paths on
the map. Before you can work with the rush hour model on the map, you must select it as
the Current Rush Hour for the map. To select a rush hour area, click on it in the Rush Hour
Models window and then click on the Process icon.
268

Choosing the Rush Hour Map Display
The rush hour areas and paths are drawn on a map in Rush Hour mode. Before you can
enter Rush Hour mode, you need to select the rush hour model that you want to work with.
Any areas and paths that exist for the model will appear on the map while you are in rush
hour mode. You can specify how the paths and areas are displayed on the map.
You can only choose a current rush hour model in the Maintenance module, but you can
change the display options in the Maintenance module, Routing Editor, Planning Editor,
or Dispatcher module. These steps assume you are working in the Maintenance module.
Step 4: Click on the Rush Hour tab. The Rush Hour page opens.
The rush hour areas and

paths will be displayed on
the map when you are in
Rush Hour mode. To have
them displayed at all times,
check Display Rush Hour
Areas and Paths.
Step 5: Click on the Current Rush Hour Model arrow; the Rush Hour Models window
opens.
Step 6: Double-click on the rush hour model you want displayed on the map, or click
on the model and then on the Process icon. If you do not want to use a rush hour
model, check the None box.
Step 7: To change the color used to display the Rush Hour Areas, click on the color
arrow to open a color palette; click on a color to select it.
Step 8: To change the width of the areas border, enter the new width, in pixels, in the
Width field.
Step 9: To change the color used to display the Rush Hour Paths, click on the color
palette; click on a color to select it.
Operations Guide
269
Step 10: To change the width of the paths border, enter the new width, in pixels, in the
Width field.
Step 11: To have the rush hour areas and paths always displayed on the map, even
when you are not in Rush Hour mode, check Display Rush Hour Areas and
Paths. The areas and paths will be displayed when you are in Rush Hour mode
even if this box is not checked.
Step 12: Click the [Save] button to save the options.
Maintenance File Map Map Options icon [OK]
Adding a Rush Hour Area
Once you have created a rush hour model, you can create rush hour areas and define speed
variations unique to that area. Rush hour areas are simply geographic regions you create
and assign specific attributes to. You can have as many rush hour areas as needed for each
model; the areas can even overlap. If you want to define speed variations or direction
changes on individual streets, you need to create rush hour paths.
When creating rush hour areas, you need to choose whether you are creating Simple areas
or Advanced areas. Advanced areas let you specify speed variations by road class; Simple
areas let you define a speed variation for all roads in the area. If the rush hour model will
be used with a routing or planning session that uses XY as the time/distance calculator, or
uses RouteNet/SuperMatrix but not the Advanced Rush Hour features, create only Simple
areas. If the routing or planning session uses RouteNet with the Advanced Rush Hour
features, you can create Simple or Advanced areas.
Rush hour areas are added on the map in the Maintenance module, netScheduler,
MobileCast, or Routing or Planning Editor. These steps assume you are working in the
Maintenance module.
Note: In order to enter Rush Hour mode, you must have selected a Current Rush Hour
Model in the Map Options notebook.
Step 3: Click on the Edit Rush Hour Model icon. The map enters Rush Hour mode and
the cursor changes to a clock. The map title displays the current rush hour model.
Step 4: Right-click on the map and select Add Area from the menu that pops up. The
Add Rush Hour Area window opens.
Step 5: Click on the map where you want the rush hour area to start; a square appears
on the map. Continue clicking to create the outline of the rush hour area, the lines
connecting the squares will automatically be drawn, so you only need to click
where the outline will turn or curve. When you have completed the area, click the
270

[Finish/Close Area] button; you do not need to draw the last segment. The Edit
Rush Hour Area Attributes window opens.
When creating a rush hour area, you do not need to draw the last segment; simply click
the [Finish/Close Area] button and the last segment will be drawn.
Note: While you are in Rush Hour mode, you can use the zoom and center options to
move around the map as needed.
Step 6: Enter a Name and Description for the rush hour area. You must enter a name.
Step 7: Select whether you want to enter Simple area information or Advanced area
information. If using Advanced, skip to Step 10.
Hint: To define speed variations by road class, select Advanced. Advanced areas can
only be used with dispatcher, routing and planning sessions that use RouteNet and
have Advanced Rush Hour selected.
Operations Guide
271
Step 8: If the area may overlap another rush hour area, enter the priority for this area.
The attributes for the rush hour area with the higher priority will be used if areas
overlap. Priorities can range from a low of 0 to a high of 99.
When you first open the Rush Hour Area Attributes window the speed
variations are pre-filled with the models variations. You can change these
for the area.
Step 9: If you are using Simple mode, enter speed information that will pertain to all
roads in the area on the Speed Variation page. Any speed variations entered here
will be used instead of the speed variations entered for the model.
For each time period you want to adjust the speed for all roads in the area, check
the box and enter the percentage change. Choose whether to adjust the speed faster
or slower. The new speed will be used when the travel time is calculated.
Any time period where the Speed Variation box is not checked will use the
models speed variation.
Skip to Step 11.
Step 10: If you are using Advanced mode, click on the Advanced Speed Variation
page. For each road class and time period you want to specify a speed variation
for, check the box and enter the appropriate speed variation. The new speed will
be used when the travel time is calculated.
272


Any time period where the Speed Variation box is not checked will use the
models speed variation.
The Advanced Speed Variation page is only used if the session uses Advanced
Rush Hour; it lets you specify different rules for each road class.
Step 11: Click the [OK] button. The rush hour area attributes are saved.
Maintenance File Map Rush Hour Model icon Add Rush Hour Area [Finish/
Close Area] [OK]
Changing a Rush Hour Area
Once you have created your rush hour areas, you can change the attributes or shape of the
area.
To change the shape of the rush hour area, right-click inside the area and select Edit
Area Shape from the menu that pops up. Click on the outline where you want to change
the shape and drag to the new shape. Continue changing the shape of the rush hour area
as needed. When finished, click the [Finish] button.
To change the speed or other attribute of the area, right-click inside the area and select
Edit Area Attributes from the menu that pops up. The Edit Rush Hour Area Attributes
window opens. Make the necessary changes and click the [OK] button.
To delete a rush hour area, right-click inside the area and select Delete Area from the
menu that pops up. Click the [Yes] button to confirm you want to delete the area.
Operations Guide
273
Adding Rush Hour Path
If you are using RouteNet or the SuperMatrix to calculate travel times and distances, you
can define rush hour attributes for individual streets. Typically, when defining rush area
attributes at the street level, you would define the attributes for an entire path, such as a
stretch of an interstate, rather than for each individual street segment. The Roadnet
Transportation Suite allows you to choose individual street segments, or select a path that
will have the same attributes. If a rush hour path travels through a rush hour area, the path
attributes will be used on those streets; if an attribute is not specified for a path then the
area attributes will be used. If you are creating paths, the rush hour model must be used
with a routing or planning session using RouteNet or the SuperMatrix as the time/distance
calculator and is also using Advanced Rush Hour. Before creating the rush hour path, you
must create the rush hour model.
You can add rush hour paths from the Maintenance module, netScheduler, MobileCast,
or the Routing or Planning Editor. These instructions assume you are in the Maintenance
module.
Maintenance module opens.
Step 3: Click on the Edit Rush Hour Model icon. The cursor changes to a clock and the
models name is displayed in the maps title bar.
Step 4: Right-click on the map and select Add Path from the menu that pops up. The
Add Rush Hour Path window opens.
Step 5: Choose whether you want to use Select Street Mode or Multi-Shortest Path
Mode.
If you are using Multi-Shortest Path Mode, click on the beginning point of the
path; a box with the letter A appears. Click on the first end point for the path; a
box with the letter B appears and the shortest path between the two points is
drawn. To extend the path, continue clicking where you want the path to turn; the
box with the letter B moves to the latest end point and the shortest path from the
previous end point to the new end point is displayed. If you make a mistake, click
the [Undo] button ([Shift]+[U]) to remove the most recent segment drawn.
If you are using Select Street Mode, click on the street segments to include in
the path. Click on a street segment; the segment is highlighted and a box with the
letter A appears at one end of the segment and a box with the letter B appears at
the opposite end of the segment. Click the next segment you want included; the
A or B box moves to the end of the new segment. Continue clicking until all
desired segments are selected.
274

Notes: All street segments in the path must be connected; you will not be allowed to
select an unconnected segment.
While you are in Rush Hour mode, you can use the zoom and center options to
move around the map as needed.
Step 6: When the path is complete, click the [Finish] button. The Edit Rush Hour Path
Attributes window opens.
When drawing a rush hour path, all the segments must be connected.
Step 7: Enter a Name and Description for the path. You must enter a name.
Step 8: For each time period you want a speed variation, check the box and enter the
percentage change. Choose whether to increase the speed (Faster) or decrease the
speed (Slower). The new speed will be used when the travel time is calculated.
When establishing the
attributes for a rush hour
path, you can specify the
direction traffic travels if
it is different than during
normal times of day.
Operations Guide
275
Step 9: For each time period choose the road direction, if it is different than during the
normal time of day.
Step 10: Click the [OK] button when all attributes are entered.
Step 11: To add another rush hour path, repeat Steps 4-10.
Maintenance File Map Rush Hour Model icon Add Rush Hour Path
[Finish] [OK]
Changing a Rush Hour Path
Once you have created a rush hour path, you can change it as needed. When changing a
rush hour path, you can only select individual street segments and any segments you add
to the path need to be connected to the path.
To change the speed variation, or other attribute for the path, right-click on the path
and select Edit Path Attributes from the menu that pops up. In the Edit Rush Hour Path
Attributes window, make the necessary changes and click the [OK] button.
To shorten or lengthen the path, right-click on the path and select Edit Path from the
menu that pops up. To add to the path, click on the segment next to the end of the current
path. To remove segments from the path, click on the segment at the end of the path. The
A or B box moves to indicate the new end of the path.
To delete a rush hour path, right-click on the path and select Delete Path from the menu
that pops up. Click [OK] to confirm the deletion.
276

Working with Time of Day Restriction Models

In some metropolitan areas, there are roads where particular types of equipment are
restricted from traveling during different times of the day; for example, downtown areas
where delivery vehicles are not allowed during certain times of the day. So when your
routes are created, you either need to avoid those roads or make sure an equipment type
that can travel on the road is assigned to the route. The Roadnet Transportation Suite
allows you to create a time of day restriction model that compensates for traffic patterns
that vary during the day. This means you can define a time period during which certain
equipment types are restricted in defined areas/paths. This allows you to prevent some
vehicles, such as large trucks, from being routed on restricted roads while allowing other
vehicles, such as small trucks or vans, to use those roads. The Roadnet Transportation
Suite allows deliveries to destinations in restricted areas using a restricted vehicle if the
destinations can be serviced during the time when the restrictions are not in effect. You
can restrict the equipment types that are permitted to travel through areas or on specific
streets during the time of day restrictions.
Each time of day restriction model can have up to three time periods, not including the
normal time period, so you could have a morning, lunch, and evening time period, as well
as normal traffic. To create areas or time of day restriction information for specific streets,
use the map to draw the areas and street paths and specify their time of day restriction
attributes.
Setting up a time of day restriction model is a one-time process. Once you have created
the model, you can assign it to be used for netScheduler, MobileCast, and for different
routing and planning sessions. The time of day restriction model can be used with
RouteNet and SuperMatrix as the time distance calculator. If the session uses RouteNet
or SuperMatrix, you can use a model that specifies time of day restriction information for
areas or individual streets, including equipment type restrictions. In addition, you can
choose to have the time of day restriction information considered when the route paths are
created or only considered when the travel times are calculated for the route. See Setting
the Options and Working with Planning Sessions for more information.
The first step in working with time of day restriction models is to create the models. Once
the model has been created, you can create the time of day restriction areas and paths for
the model.
Creating the Time of Day Restriction Model
Setting up a time of day restriction model is a one-time process. Once you have created
the model, you can assign it to be used for netScheduler or for different routing and
planning sessions. The time of day restriction model can be used with RouteNet and
SuperMatrix as the time distance calculator. If the session uses RouteNet or SuperMatrix,
you can use a model that specifies time of day restriction information for areas and
individual streets, including equipment type restrictions. In addition, you can choose to
have the time of day restriction information considered when the route paths are created
or only considered when the travel times are calculated for the route.
Operations Guide
277
The first step in setting up time of day restriction information is to create the time of day
restriction model. For each time of day restriction model, you can define up to three
distinct time periods.
You can create time of day restriction models in the Maintenance module, although you
can edit an existing model in the Planning Editor, Routing Editor, or netScheduler.
Note: If you were not granted permission to edit the time of day restriction models in the
Administration module, you will not be able to add a time of day restriction model.
Maintenance module window opens.
Step 4: Click on the Time of Day Restriction tab. The Time of Day Restriction page
opens.
Step 5: To add a new time of day restriction model, click the Current Time of Day
Restriction Model arrow. The Time of Day Restriction Models window opens.
The time periods defined cannot change

for different areas and paths.
Step 6: Click the Add icon. The Add Time of Day Restriction Model window opens.
Step 7: Enter a Name and Description for the time of day restriction model. You must
enter a name.
Step 8: Check the Enable box for Time Period 1.
Step 9: Enter a new name or leave the default, then enter the starting and ending times
for the time of day restriction period.
Step 10: Continue for the remaining time periods as necessary. Some things to
remember when adding a time of day restriction model:
278

The ending time for each time period must occur after the starting time.
The time periods cannot overlap. However, a new time period can start at the
same time a previous time period ends.
You can enter the time manually, or use the arrows to scroll to the correct time.
If entering the time manually, use the arrow keys to move from the hour to
minute field. If using the scroll arrows, click on the correct field (hour to minute)
before scrolling. Use a 24-hour clock when entering the time. For example, enter
1:00 PM as 13:00.
Step 11: Click the Save icon, or press [Ctrl]+[S] to save the time of day restriction
model.
Step 12: Repeat Steps 7 - 11 to add any additional time of day restriction models. When
all necessary time of day restriction models have been added, click the Close box
to close the Add Time of Day Restriction Model window.
Note: In order to use the Time of Day Restriction Model you just created, you must create
a valid area or path. See Adding a Time of Day Restriction Area or Adding a Time
of Day Restriction Path for more information.
Maintenance File Map Map Options icon Add icon Save icon
Existing time of day restriction models can be edited or deleted as necessary. See Editing
Items and Deleting Items for more information. To create a new model with the same
areas and paths, you can clone the existing model. See Cloning Items for more
information.
Once you have added your time of day restriction models, you can create time of day
restriction areas and paths on the map. Before you can work with the time of day
restriction model on the map, you must select it as the Current Time of Day Restriction
for the map. To select a time of day restriction area, click on it in the Time of Day
Restriction Models window and then click on the Process icon.
Select the Time of Day Restriction Map Display
The time of day restriction areas and paths are drawn on a map in Time of Day Restriction
mode. Before you can enter the Time of Day Restriction mode, you need to select the time
of day model that you want to work with. Any areas and paths that exist for the model will
appear on the map while you are in time of day restriction mode.You can specify how the
paths and areas are displayed on the map.
You can only choose a current time of day restriction model in the Maintenance module,
but you can change the display options in the Maintenance module, Routing Editor,
Planning Editor, Dispatcher, or netScheduler. These steps assume you are working in the
Maintenance module.
Operations Guide
279
Step 4: Click on the Time of Day Restriction tab. The Time of Day Restriction page
opens.
The time of day restriction areas and paths

will be displayed on the map when you are
in Time of Day Restriction mode. To have
them displayed at all times, check Display
Time of Day Restriction Areas and Paths.
Step 5: Click on the Current Time of Day Restriction Model arrow. The Time of Day
Restriction Models window opens.
Step 6: Double-click on the time of day restriction model you want displayed on the
map, or click on the model and then on the Process icon. If you do not want to
use a time of day restriction model, check the None box.
Step 7: To change the color used to display the Time of Day Restriction Areas, click on
the color arrow to open the color palette; click on a color to select it.
Step 8: To change the width of the areas border, enter the new width, in pixels, in the
Width field.
Step 9: To change the color used to display the Time of Day Restriction Paths, click on
the color palette; click on a color to select it.
Step 10: To change the width of the paths border, enter the new width, in pixels, in the
Width field.
Step 11: To have the time of day restriction areas and paths always displayed on the
map, even when you are not in Time of Day Restriction mode, check Display
Time of Day Restriction Areas and Paths. The areas and paths will be displayed
when you are in Time of Day Restriction mode even if this box is not checked.
Step 12: Click the [Save] button to save the options.
Maintenance FileMapMap Options icon[Save]
280

Adding a Time of Day Restriction Area
Once you have created a time of day restriction model, you can create the time of day
restriction areas and travel restrictions unique to that area. Time of day restriction areas
are simply geographic regions you can create and assign specific attributes to. You can
have as many time of day restriction areas as needed for each model; the areas can even
overlap. If you want to define travel restrictions on individual streets, you need to create
time of day restriction paths.
Time of day restriction areas are added on the map in the Maintenance module,
netScheduler, Dispatcher, or Planning Editor. These steps assume you are working in the
Maintenance module.
Note: In order to enter the Time of Day Restriction mode, you must have selected a time
of day restriction model in the Map Options notebook.
Step 3: Click on the Edit Time of Day Restriction Model icon. The map enters the Time
of Day Restriction mode and the cursor changes to a slashed circle. The map title
displays the current time of day restriction model.
Step 4: Right-click on the map and select Add Area from the menu that pops up.The
Add Area window opens.
Step 5: Click on the map where you want the time of day restriction area to start; a
square appears on the map. Continue clicking to create the outline of the time of
day restriction area, the lines connecting the squares will automatically be drawn,
so you only need to click where the outline will turn or curve. When you have
completed the area, click the [Finish/Close Area] button; you do not need to draw
Operations Guide
281
the last segment. The Edit Time of Day Restriction Area Attributes window
opens.
When creating a time of day restriction area, you do not need to draw the last segment; simply
click the [Finish/Close Area] button and the last segment will be drawn.
Note: While you are in the Time of Day Restriction mode, you can use the zoom and
center options to move around the map as needed.
Step 6: Enter a Name and Description for the time of day restriction area. You must
enter a name.
The Edit Time of Day

Restriction Area
Attributes window
allows you to specify
different rules for each
road class.
282

Step 7: For each road class and time period you want to restrict equipment on, check
the Restricted box. To restrict all roads classes for a time period, click the [All]
button.
Note: If all the road classes in an area are restricted, and a stop is located in the restricted
area, it will not be placed on a route with a restricted equipment type. If some road
classes are not restricted, the stop can be routed and will display a dotted path
between locations.
Step 8: Click the [OK] button. The time of day restriction area attributes are saved.
Maintenance File Map Time of Day Restriction icon Add Area
[Finish/Close Area] [OK]
Changing a Time of Day Restriction Area
Once you have created time of day restriction areas, you can change the attributes or shape
of the area.
To change the shape of the time of day restriction area, right-click inside the area and
select Edit Areas Shape from the menu that pops up. Click on the outline where you want
to change the shape and drag to the new shape. Continue changing the shape of the time
of day restriction area as needed. When finished, click the [Finish] button.
To change the equipment restrictions, right-click inside the areas and select Edit Area
Attributes from the menu that pops up. The Edit Time of Day Restriction Area Attributes
window opens. Make the necessary changes and click the [OK] button.
To delete a time of day restriction area, right-click inside the area and select Delete
Area from the menu that pops up. Click the [Yes] button to confirm that you want to delete
the area.
Adding a Time of Day Restriction Path
If you are using RouteNet or SuperMatrix to calculate travel times and distances, you can
define the time of day restriction attributes for individual streets. Typically, when defining
time of day attributes at the street level, you would define the attributes for an entire path,
such as a stretch of an interstate, rather than for each individual street segment. The
Roadnet Transportation Suite allows you to choose individual street segments or select a
path that will have the same attributes. If a time of day restriction path travels through a
time of day restriction area, the path attributes will be used on those streets; if an attribute
is not specified for a path, then the area attributes will be used. If you are creating paths,
the time of day restriction model must be used with a routing or planning session using
RouteNet or SuperMatrix as the time/distance calculator. Before creating time of day
restriction path, you must create the time of day restriction model.
You can add time of day restriction paths from the Maintenance module, netScheduler,
Routing Editor, Dispatcher, or Planning Editor. These instructions assume you are in the
Maintenance module.
Operations Guide
283
Step 3: Click on the Edit Time of Day Restriction Model icon. The cursor changes to a
slashed circle and the models name is displayed in the maps title bar.
Step 4: Right-click on the map and select Add Path from the menu that pops up. The
Add Time of Day Restriction Path window opens.
Step 5: Choose whether you want to use Multi-Shortest Path Mode or Select Street
Mode.
If you are using Multi-Shortest Path Mode, click on the beginning point of the
path; a box with a letter A. Click on the first end point for the path; a box with the
letter B appears and the shortest path between the two points is drawn. To extend
the path, continue clicking where you want the path to turn; the box with the letter
B moves to the latest end point and the shortest path from the previous end point
to the new end point is displayed. If you make a mistake, click the [Undo] button
([Shift]+[U]) to remove the most recent segment drawn.
If you are using Select Street Mode, click on the street segments to include in
the path. Click on a street segment; the segment is highlighted and a box with the
letter A appears at one end of the segment and a box with a letter B appears at the
opposite end of the segment. Click the next segment you want included; the A
or B box moves to the end of the new segment. Continue clicking until all
desired segments are selected.
Notes: All street segments in the path must be connected; you will not be able to select
an unconnected segment.
While you are in the Time of Day Restriction mode, you can use the zoom and
center options to move around the map as needed.
284

Step 6: When the path is complete, click the [Finish] button. The Edit Time of Day Path
Attributes window opens.
When drawing a time of day restriction path, all the segments must be connected.
Step 7: Enter a Name and Description for the path. You must enter a name.
You can specify the time period that

equipment is restricted.
Step 8: To have unique travel restrictions for the path, check the Restricted box for the
correct time period. If a check appears in the box the path is restricted during the
period, if the check is gray or faded and the path is in a time of day restriction
area, then the restriction specified for the area is used; if there is no check, then
there is no equipment restriction for the path.
Step 9: Click the [OK] button when all attributes are entered.
Step 10: To add another time of day restriction path, repeat Steps 4 - 9.
Maintenance File Map Time of Day Restriction icon Add Path [Finish] [OK]
Changing a Time of Day Restriction Path
Once you have created a time of day restriction path, you can change it as needed. When
changing a time of day restriction path, you can only select individual street segments and
any segments you add to the path needed to be connected to the path.
Operations Guide
285
To change the travel restriction for the path, right-click on the path and select Edit Path
Attributes from the menu that pops up. In the Edit Time of Day Restriction Path Attributes
window, make the necessary changes and click the [OK] button.
To shorten or lengthen the path, right-click on the path and select Edit Path from the
menu that pops up. To add to the path, click on the segment next to the end of the current
path. To remove segments from the path, click on the segment at the end of the path. The
A or B box move to indicate the new end of the path.
To delete a time of day restriction path, right-click on the path and select Delete Path
from the menu that pops up. Click [OK] to confirm the deletion.
286

Working with Barriers

If you are using the XY method to calculate travel times and distances, you can create
barriers that compensate for rivers, lakes and other waterways, as well as mountains or
other natural barriers to travel. When routes are created, these barriers are considered, and
the Roadnet Transportation Suite will route around the barrier. Because Roadnet will not
cross a barrier, it is necessary to use only a single line to create a barrier, rather than
following the contours of the natural barrier, such as the coastline of a lake.
To have barriers appear on the map, click on the Map Options icon in a map window. In
the Map Properties notebook select the Barriers/Cells tab to open the Barriers/Cells page;
check the Display box in the Barriers area. You can also choose the color of the barriers
from here by clicking on the color box arrow.
You can create barriers on any map in the Roadnet Transportation Suite. For the purpose
of this guide the map in the Maintenance module will be used.
For more information see Adding Barriers, Modifying Barriers, or Deleting Barriers.
Adding Barriers
When adding a barrier, draw a single line through the area, rather than trying to follow the
contours of the waterway or other obstacle. The Roadnet Transportation Suite will not
cross a barrier when creating routes.
Step 2: Click on the File menu and select Map. The Map window opens.
Step 3: On a map, click on the Edit Barriers icon. The cursor changes to a barrier with
a plus sign next to the pointer to indicate Add Barrier mode.
Step 4: Click where you want the barrier to start. A square appears, marking the
beginning point of the barrier.
Operations Guide
287
Step 5: Click where you want the barrier to turn or end. Another square appears at this
point, with a line connecting the two points. This line is the barrier; the squares
are nodes.
The white line down the center of the water marks a barrier. Roadnet will not cross the
barrier line when using the XY method to calculate the travel time between stops.
Step 6: Continue clicking to add points and segments to the barrier. When the barrier is
complete, right-click on the map and select Finish Current Barrier from the menu
that pops up.
Step 7: To save the barrier(s) and exit the add mode, right-click and select Cancel/Exit
Add Mode; then right-click again and select Save/Exit from the menu that pops
up.
File Map Barrier icon Finish Current Barrier Cancel/Exit Add Mode
Once a barrier has been added you can change it or delete it as necessary.
Modifying Barriers
Once you have created a barrier, you can add a curve or otherwise change its shape, or
extend it, if necessary.
Step 1: Click on the Maintenance icon to open the Maintenance module.The
288

Step 3: Click on the Edit Barriers icon. The cursor changes to a barrier with a plus sign
next to the pointer to indicate add barrier mode.
Step 4: Right-click on the map and select Cancel/Exit Add Mode from the menu that
pops up.
Step 5: Right-click on the barrier and select Modify Barrier from the menu that pops
up. Click on any point of the barrier and drag to modify. For instance, to extend a
barrier, click on the end point and drag it to the new end point. If you are happy
with your change(s), right-click and select Finish Modifying Barrier from the
menu that pops up. Then, right-click again and select Save/Exit from the menu
that pops up.
Step 6: Repeat Steps 4 and 5 to continue editing the barrier if needed.
File Map Barrier icon Cancel/Exit Add Mode Modify Barrier Finish Modifying
Barrier Save/Exit
Deleting Barriers
If you have created a barrier that is no longer needed, you can delete it. Or, if your barrier
is too long, you can shorten it.
File Map
Step 3: Click on the Edit Barriers icon. The cursor changes to a barrier with a plus sign
next to the pointer to indicate add barrier mode.
Step 4: Right-click on the map and select Cancel/Exit Add Mode.
Step 5: Right-click on the barrier to be deleted and select Delete Barrier from the menu
that pops up. Click the [Yes] button to confirm the deletion.
Note: If you click on an end node, only that segment of the barrier will be deleted. For
instance, if you created a barrier that has several segments, and the barrier is too
long, you can shorten it by clicking on the end node to delete only the last segment.
File Map Barrier icon Cancel/Exit Add Mode Delete Barrier [Yes]
Operations Guide
289
Working with Cells
Working with Cells

Used with: Roadnet
Cells work with dynamic routing to help divide your delivery area into smaller segments.
If you ask dynamic routing to use cells that you have created, Roadnet will create routes
within the cells but will not cross the cell boundaries. This means you can use cells to keep
the stops on your routes clustered together in a more compact geographic area.
Additionally, you can assign the cells attributes to the route.
A collection of cells is called a cell pattern. You must create cell patterns before you can
draw cells on the map. You can specify a cell pattern to group cells together based on how
you would like your routes created. For instance, you may create a cell pattern for every
day of the week. Mondays cell pattern may have cells drawn in a town that you visit only
on Mondays. Tuesdays cell pattern may concentrate stops together in a congested city
area.
In other words, you create cell patterns to solve certain routing problems. If you need five
routes created in a town, you may create a cell pattern for that town with five individual
cells. Then, in dynamic routing, you can use any number of cell patterns for individual
routing passes.
To have cells appear on the map, click on the Map Options icon and select Properties in
a map window. In the Map Properties notebook select the Barriers/Cells tab to open the
Barriers/Cells page and check the Display box in the Cells area. You can also choose the
color of the cells from here by clicking on the color box arrow.
To select a default cell pattern, the cell pattern that will appear when you enter the map,
click on the Options icon and select Properties, then the Barriers/Cells tab. Click on the
Default Cell Pattern arrow to open the Change Cell Pattern window; click on the pattern
you would like to set as your default, and click the Process icon to save the default cell
pattern. If no default cell pattern is selected, the Cell Pattern window will open before any
work on cells can be done.
You can create cells on any map in the Roadnet Transportation Suite. For the purpose of
this guide, the map in the Maintenance module will be used.
Adding Cell Patterns
A collection of cells is called a cell pattern. You can create a cell pattern to group cells
together based on how you would like your routes created. For instance, you may create
a cell pattern for every day of the week or for different parts of town. You must create a
cell pattern before drawing cells on the map. The cell pattern is chosen for the dynamic
routing pass.
Step 3: Click on the Edit Cells icon. The cursor changes to a cell with a plus sign next
to it to indicate Add Cell mode.
290

Working with Cells
Note: If you havent yet created cell patterns, the Add Cell Pattern window will open
automatically when you click on the Cell icon. Proceed to Step 4 if this happens.
pops up to abandon Add Cell mode (the default).
Step 5: Right-click and select Cell Patterns from the menu that pops up. The Cell
Pattern window opens.
Step 6: Click on the Add icon or press [Insert] to add a new cell pattern. The Add Cell
Pattern window opens.
Add cell patterns to group cells based on how you want the routes to be created.
Step 7: Enter a title for the pattern and a description as appropriate. You must enter a
pattern name.
Step 8: Click on the Save icon, or press [Ctrl]+[S] to add the new cell pattern.
Step 9: When you are finished adding cell patterns, click the Close box to close the Add
Cell Pattern window.
File Map Edit Cell icon Cancel/Exit Add Mode Cell Patterns Add icon ([Insert])
Editing Cell Patterns
You can change the description of an existing cell pattern, but not the ID. If you want to
change the ID you need to delete the existing pattern and re-add it.
Operations Guide
291
Working with Cells
Step 5: Right-click on the map and select Cell Patterns from the menu that pops up. The
Cell Pattern window opens.
Step 6: From the Cell Pattern window, right-click on the cell pattern(s) you want to
edit.
Step 7: Select Edit from the menu that pops up. The Edit Cell Pattern window opens.
Step 8: Change the information as necessary.
Step 9: Click on the Save icon, or press [Ctrl]+[S] to save the changes.
Step 10: When you are finished, click the Close box to close the Edit Cell Pattern
window.
File Map Edit Cell icon Cancel/Exit Add Mode Cell Patterns Edit Save icon
([Ctrl]+[S])
Switching Cell Patterns
You can establish one cell pattern as the default that automatically opens when you enter
Cell Mode on the map. However, if you want to work with a different cell pattern, you
need to change to that pattern.
Step 3: Click on the Edit Cells icon. The Cell Pattern window opens.
Step 4: Click on a cell pattern in the window, then right-click on the pattern to display
the menu that pops up.
Right-click on the cell pattern
for which you want to draw a
cell and choose Change Cell
Pattern.
292

Working with Cells
Step 5: To switch to a cell pattern other than the one displayed, right-click on the
pattern and select Change Cell Pattern from the menu that pops up. The cell
pattern you selected will be displayed on the map.
File Map Edit Cell icon Cancel/Exit Add Mode Cell Patterns Change Cell
Pattern
Deleting Cell Patterns
If you find that you have a cell pattern that you no longer use, you can delete it. Before
deleting the cell pattern, make sure you do not need the cells contained in the pattern.
Step 5: Right-click on the map and select Cell Patterns from the menu that pops up. The
Cell Pattern window opens.
Step 6: From the Cell Pattern window, right-click on the cell pattern you want to delete.
Step 7: Select Delete from the menu that pops up. You can also delete cell patterns by
selecting the cell pattern you want to delete and clicking on the Delete icon.
Step 8: Click on [OK] to confirm the deletion.
File Map Edit Cell icon Cancel/Exit Add Mode Cell Patterns Delete([Delete])
[OK]
Adding Cells
Once you have added a cell pattern, you can draw any number of individual cells for that
pattern. You can also add additional cells to existing patterns. The cells can conform to
any geographic area you want, follow roads, water boundaries, zip/postal codes, etc.
to it to indicate Add Cell mode. Your default cell pattern will appear on the map.
Note: If you want to add a cell to a cell pattern that is not displayed as your default, change
to the appropriate cell pattern.
Step 4: Click where you want the cell to start. A node appears, marking the beginning
point of the cell.
Operations Guide
293
Working with Cells
Step 5: Click where you want the cell to turn. Another node appears at this point, with
a line connecting the two points; this line is the cell boundary. Continue clicking
until you are ready to close the cell.
Note: You do not need to close the cell when you are creating it; once you select Finish
Current Cell from the popup menu, Roadnet will automatically close the cell for
you.
Step 6: Right-click on the map and select Save Current Cell from the menu that pops
up. The Cell Attributes window opens. Enter the necessary information and click
[OK]. See Editing Cell Attributes for more information.
Hint: If you want two cells next to each other to share a common boundary, draw one
big cell that comprises the entire area of the two cells and then split the cell. See
Splitting Cells for more information.
Step 7: To save the cell(s) and exit the add mode, right-click on the map and select
Cancel/Exit Add Mode; then right-click again and select Save/Exit from the
menu that pops up.
File Map Edit Cell icon Finish Current Cell Save Current Cell Cancel/Exit
Mode Save/Exit
Splitting Cells
Existing cells can be broken, or split, to create two or more new cells. When you split a
cell, you can create new attributes for the new cell.
Note: If you want to add a cell to a cell pattern that is not displayed as your default,
change to the appropriate cell pattern.
Step 4: Right-click anywhere in the cell and select Split from the menu that pops up.
Step 5: Click where you want to start splitting the cell. You must click on a cell
boundary. A node appears, marking the beginning of the split.
Step 6: Click where you want the split boundary to turn or end. Another node appears
at this point, with a line connecting the two points.
Step 7: Continue clicking until you reach the cell boundary where you want the split to
end.
Note: When splitting a cell, you must start and end on an existing cell boundary.
Step 8: Right-click on the map and select Finish Cell Split from the menu that pops up.
You can then edit the cell(s) attributes. See Editing Cell Attributes for more
information.
294

Working with Cells
File Map Edit Cell icon Split Finish Cell Split

Modifying Cells
You can change the shape or size of an existing cell by moving the cell boundary. You
must have a map open to work with cells and cell patterns.
Step 4: Right click anywhere in the cell you want to modify, and select Modify Cell
from the menu that pops up. The cursor changes to a Work Zone.
Step 5: Click anywhere on the cell boundary and drag to modify the cells shape and
size.
Step 6: Once you have finished modifying your cell, right-click in the cell to open the
pop-up menu, and select Finish Modifying Cell. Then right-click again and select
Save/Exit to save your changes. If you do not want to save your changes, rightclick in the cell and select Cancel/Edit Modify Mode from the menu that pops up.
File Map Edit Cell icon Modify Cell Finish Modifying Cell Save/Exit
Editing Cell Attributes
If you choose, you can assign attributes to any cell so that the attributes are applied to any
routes created using that cell. The cell attributes are described below.
Step 4: Right-click anywhere in the cell to edit that cells attributes, and select Edit
Attributes from the menu that pops up. The Edit Attributes window opens.
Note: If you have split cells, each split cell will have its own attributes.
Operations Guide
295
Working with Cells
Step 5: Enter the appropriate information based on the Cell Attribute Descriptions
chart. For items in the Route Attributes section, click the arrow to open the
Lookup window and double-click the appropriate selection.
The Edit Attributes window
contains information you
can specify about the
route(s) created within the
cell.
Note: Attribute information is optional. However, if you enter attribute information,

those attributes will be applied to any route(s) created within that cell if Use Cell
Attributes is selected in the Routing Pass Options notebook, unless there is an
overriding attribute. For instance, if you select a preferred depot for the cell, but
an order within that cell has a different preferred depot, the orders depot will be
used for that order. Likewise, if the order is routed using standard route
sequencing, it will use the standard routes depot.
Step 6: Click [OK] to save the attributes for the cell.
Cell Attribute Descriptions
Attribute
Description
Name
Name of the cell. Name is also assigned to the route in the Routing
Editor if specified.
Priority
Up to a 3-digit number used to determine which cell to use if a

location falls within two overlapping cells. Higher number = higher
priority.
Driver
Driver used to calculate driver costs when routes are created. Also
assigned to the route in the Routing Editor if specified.
Depot
Depot used to calculate distance and cost when routes are created.
Also assigned to the route in the Routing Editor if specified.
Travel Model
Travel time model used to calculate travel time when routes are
created. Also assigned to the route in the Routing Editor if specified.
Equipment
Type
Equipment type used to calculate vehicle capacity and cost when

routes are created. Also assigned to the route in the Routing Editor if
specified.
Equipment
Equipment associated with the cell.
296

Working with Cells
Route ID
Route ID for the cell. ID is also assigned to the route in the Routing
Editor if specified.
Start Time
Time the route leaves the depot.
Preferred Time
Preferred runtime (travel and service time) for the route.
Max Time
Maximum runtime (travel and service time) for the route.
File Map Edit Cell icon Edit Attributes [OK]

Deleting Cells
Over time you may find that you have cells you no longer use. These cells should be
deleted so that they are not considered when routing using that pattern.
Step 4: Right-click in the cell you would like to delete and select Delete Cell from the
menu that pops up.
Step 5: Click [Yes] to confirm the deletion.
File Map Edit Cell icon Delete [Yes]
Operations Guide
297
Working with Actual vs. Planned Comments

Used with: Roadnet
Actual vs. planned comments enable the Roadnet Transportation Suite to report the
reason for differences between planned and actual service times based on data from driver
feedback or an onboard computer. Actual vs. planned comments also allow you to
determine whether deliveries with a particular comment should be used to update the
delivery history for a location. Roadnet can use this historical information to calculate
more accurate service times. See Update Service Times for more information on this
feature. For example, a driver takes much longer than usual delivering to a location
because his hand truck breaks. Because this delivery does not represent normal delivery
conditions, you wouldnt want that delivery to be used in calculating a more accurate
service time. The driver could enter an actual vs. planned comment code on his manifest
or in his onboard computer to indicate that this delivery should not update delivery
history. When the information is entered, the comment code tells the system not to store
this time in delivery history.
Step 2: Click on the Actual Data Entry menu, then Actual vs. Planned Comments. The
Actual vs. Planned window opens.
Note: To see an updated list of actual vs. planned comments, click on the Refresh icon;
the window will be updated with the most recent information from the database.
Step 3: In the Actual vs. Planned Comments window, click on the Add icon or press
[Insert]. The Add Actual vs. Planned Comments window opens.
and select Clone from the menu that pops up. The Add Actual vs. Planned
Comments window opens with some information already completed; change the
information as necessary for the new entry.
Step 4: Enter 3 characters as the Comment Code. This field must be completed.
You can specify whether
deliveries with an actual vs.
planned comment will be used to
update delivery history.

Step 6: If you want deliveries with this comment code to update delivery history, verify
that a check is present in the Update History box (the check is present by default;
click in the box to disable Update History).
298

Step 7: Click on the Save icon, or press [Ctrl]+[S] to save the new actual vs. planned
comment.
Step 8: Repeat Steps 2 7 to add any other comments.
Step 9: When you are finished adding comments, click the Close box to close the Add
Actual vs. Planned Comments window.
Maintenance icon Actual Data Entry Actual vs. Planned Comments Add icon
Existing actual vs. planned comments can be edited or deleted as necessary. See Editing
Operations Guide
299
Entering Actual Route/Stop Information

Used with: Roadnet
One very important responsibility a driver has is to gather actual route and stop
information throughout the day. The Roadnet Transportation Suites Actual Route/Stop
feature allows you to enter and store this information so that it can be accessed later and
computed when running Service Time Maintenance. Actual route/stop information is
crucial when updating service times and is a powerful way to monitor and refine costs.
Note: Entering actual route/stop information will not update the drivers duty period
history, which tracks the amount of time drivers have worked to help your
organization comply with safety and labor regulations. You must use the Duty
Period History window to manually enter duty period information for the drivers.
You can enter actual route/stop data according to route or stop. When you enter
information for each stop, the route information is automatically updated.
Entering Actual Route Information
When you enter actual route information, you can include overall summary information
about the service and travel times, the amount of product delivered, as well as any
comments you think are important.
If you have stop specific information, then you want to enter actual stop information,
rather than actual route information. See Entering Actual Stop Information for more
information.
Step 2: Click on the Actual Data Entry menu, then Actual Route/Stop. The Actual
Routes: Session window opens.
Step 3: In the Actual Routes: Session window, double-click on the route for which you
want to enter actual data. The Route window will automatically open for the
selected route. You can also right-click and select Edit to open the Route window.
OR
Click on the Change Displayed Sessions icon to view a list of all routing sessions
and double-click on the session for which you want to enter actual data. The
session you selected will appear in the Actual Routes: Session window. Doubleclick to open the Route window. You can also right-click and select Edit to open
the Route window.
Notes: The Actual Routes: Session window defaults to the most recent routing session.
If you want to enter actual data for more than one route (all the routes for a session,
for example) select the routes you want to edit, and right click and select Edit to
open the Route window. To edit all routes, right click on a route and select Edit
All. Use the arrows at the top of the Route window to move between routes.
300

Step 4: Click the Time Zone for Entry/Display arrow and select the time zone the times
you are entering are in. For instance, if you are entering times from Maryland,
choose Eastern Time.
Note: Any times that are currently displayed will change to reflect the new time zone.
The database stores them using the correct time zone, however.
Step 5: Enter the appropriate dates and times in the Route Start and Route Complete
fields.
Step 6: Enter the amount of time the driver spends at the origin before leaving the
origin in the Pre-Route Time field. This time may be for meetings or checking the
load. Pre-route time is included when the total route time is calculated.
Enter the amount of time the driver spends at the destination before clocking out
for the day in the Post-Route Time field. This time may be to complete paperwork
or unload the truck. Post-route time is included when the total route time is
calculated.
Step 7: Enter the appropriate mileage information in the Odom Start and Odom Finish
fields.
The Actual Route/Stop
window lets you enter
important actual
information about
routes and associated
stops. Entering this
information is crucial
when updating service
times.
Note: In order to track the distance from the last stop back to the depot, the Odom Start
and Finish fields need to be completed.
Step 8: Enter any necessary comments in the Comments field. If the driver had a
helper, check the Helper box.
Step 9: Select Route from the Edit Data section of the window. The window changes to
allow the Route Summary fields to become available.
Step 10: Fill in the Times, Quantities, and Totals columns as necessary. Remember,
these are the total times and quantities for the route.
Step 11: Once you have finished entering actual route information, click the Save icon
to save your changes.
Operations Guide
301
Step 12: If you have selected multiple routes to edit, use the arrows at the top of the
window to move to the next route, and repeat Steps 4-10 to enter actual data.
Step 13: When you are finished entering actual data, click the Close box to close the
Route window.
Maintenance icon Actual Data Entry Actual Route/Stop Sessions
iconRoute Save icon ([Ctrl]+[S])
Entering Actual Stop Information
You can enter actual route/stop data according to route or stop. When you enter
information for each stop, the corresponding route information, such as service time,
travel time, and quantity delivered is calculated.
If you do not have actual information for the individual stops, you can enter actual
information for the route. See Entering Actual Route Information for more information.
Step 2: Click on the Actual Data Entry menu, then Actual Route/Stop. The Actual
Routes: Routing Session window opens.
Step 3: In the Actual Routes: Routing Session window, double-click on the route for
which you want to enter actual data. The Route window automatically opens for
the selected route. You can also right-click and select Edit to open the Route
window.
OR
Click on the Change Displayed Sessions icon to view a list of all routing sessions
and double-click on the session for which you want to enter actual data. The
session you selected will appear in the Actual Routes: Routing Session window.
Double-click to open the Route window. You can also right-click and select Edit
to open the Route window.
Notes: The Actual Routes: Routing Session window defaults to the most recent routing
session.
If you want to enter actual data for more than one route (all the routes for a session,
for example) select the routes you want to edit, right-click on a selected route and
choose Edit to open the Route window. To edit all routes, right-click on a route
and select Edit All. Use the arrows at the top of the Route window to move
between routes.
Step 4: Verify that Stop is selected in the Edit Data section of the Route window.
Step 5: In the list at the bottom of the window, click to select the stop for which you
would like to enter actual information. The first stop is already selected by
default.
302

Step 6: Click the Time Zone for Entry/Display arrow and select the time zone the times
you are entering are in. For instance, if you are entering times from Maryland,
choose Eastern Time.
Note: Any times that are currently displayed will change to reflect the new time zone.
The database stores them using the correct time zone, however.
Step 7: Depending on whether or not your driver has an onboard computer, various stop
information may be imported. Enter any necessary information that is not already
present in the Stop, Dist, Size, In, Out, and Comment fields (the Comment field
is a drop-down list of the Actual vs. planned Comment codes). Location ID and
type are always imported and will therefore be displayed.
When you enter time, distance, and quantity information for the stop, the route
information is automatically updated.
Step 8: When you have finished entering actual information for the current stop, click
the [Enter] button on the Route window to automatically move to the next stop.
Note: If you need to add an additional stop, click the [Insert Stop] button, and enter all
the stop information, including the Location ID. Inserted stops can be deleted by
clicking the [Delete Stop] button. Stops that were previously imported cannot be
deleted.
Step 9: Once you have finished entering all the actual stop information for your
route(s), click the Save icon or press [Ctrl]+[S] to save your changes.
Step 10: Click the Close box to close the Route window.
Operations Guide
303
Maintenance icon Actual Data Entry Actual Route/Stop Sessions

iconRoute Save icon ([Ctrl]+[S])
304

Working with Drivers Duty Period History

The Duty Period History saves information about how long drivers worked during their
routes. This information is used to determine when drivers violate duty period rules. Duty
period rules regulate how long drivers can work and are used to help your organization
comply with safety and labor laws. You can set up duty period rules on the Duty Period
Monitor page of the Maintenance Options notebook.
When creating routes in Roadnet, you can select to update the drivers Duty Period
History based on the routes you create. If you use MobileCast, the drivers Duty Period
History will always be updated based on the information collected by MobileCast. If a
route is created in Roadnet and then run in MobileCast, the actual work time information
collected by MobileCast will overwrite the planned work time information generated by
Roadnet. You can view and edit the Duty Period History for each driver in the Duty Period
History window.
The Duty Period History window organizes the drivers work time history by duty
periods. A duty period is a block of work time that is not interrupted by any time where
the driver is off duty. When a driver goes off duty for any reason, the duty period ends
and a new duty period will begin when they go back to work. There can be multiple duty
periods for each route or shift. For example, if a driver takes a lunch break that is
considered to be off duty, the driver will have one duty period for the time worked before
lunch and a separate duty period for the time worked after lunch. You can specify whether
or not time spent on activities such as breaks, waits, and layovers is considered off duty
on the Duty Period Monitor page of the Maintenance Options notebook.
If you want to view or edit the work time information for a particular duty period, you can
search the Duty Period History by driver ID and/or by the duty period start date. You can
also add and delete duty periods.
Important: The Duty Period Monitoring feature in the Roadnet Transportation Suite is
not a replacement for any records that you are required to keep by law, such as
DOT logs.
Step 2: Click on the Actual Data Entry menu and select Duty Period History. The Duty
Period History window opens. The list of duty periods will not appear. This
makes the system run much faster than if the complete list were loaded every
time. To see the current list of locations, or just specific locations, use the Search
feature.
Note: To see an updated list of duty periods, click the Refresh icon; the window will be
Operations Guide
305
Step 3: In the Duty Period History window, click the Add icon or press [Insert]. The
Add Duty Period Entry window opens.
For each duty period that a driver

works, you can manually edit how
long the driver worked and how much
of that time was spent driving.
Step 4: In the Employee field, click the arrow to open the Lookup - Employee window.
Double-click on a driver to select the driver, or click on the driver then on the
Process icon.
Step 5: Enter the Route ID for the route the driver worked on during that duty period.
Step 6: In the Route Date field, enter the date the route worked on during this duty
period was started. You can enter the dates manually, or click on the arrow to
open a calendar. If you are using the calendar to change the month, either use the
arrows on the top of the calendar to scroll through the months, or click on the
month and select from the menu that pops up. To change the year, click on the
year and use the arrows to scroll to the correct year. Click on a date to select it.
Step 7: In the Duty Period Start Time field, enter the date and time the duty period
started. You can also select the date from the calendar by clicking the arrow. This
field uses a 24-hour clock, so 1:00 PM would be entered as 13:00. Click the time
zone arrow and select the time zone the duty period start time is in.
Step 8: In the Duty Period End Time field, enter the date and time the duty period
ended. You can also select the date from the calendar by clicking the arrow. If
using the calendar to change the month use the arrows on the top of the calendar
to scroll through the month or click on the month and select from the menu that
pops up. To change the year, click on the year and use the small arrows to scroll
to the correct year. Click on a date to select it. This field uses a 24-hour clock, so
1:00 PM would be entered as 13:00. Click the time zone arrow and select the
time zone the duty period start time is in.
Step 9: In the Duty Period Travel Time field, enter the amount of time the driver spent
driving during the duty period.
Step 11: When all duty periods have been entered, click the Close box to close the Add
Duty Period Entry window.
306

Notes: Once the duty period information for a route has been edited manually, it will not
be overwritten if you edit that route in Roadnet. However, the duty period
information for the route will be overwritten if that route is run in MobileCast or
if actual route information is imported from an onboard computer. Entering actual
route information through the Actual Route/Stop feature in Maintenance will not
update duty period information.
Existing duty periods can be edited or deleted as necessary. See Editing Items and
Maintenance icon Actual Data Entry Duty Period History Add icon ([Insert]) Save
icon ([Ctrl]+[S]
Operations Guide
307
Working with Area Distances

Used with: Roadnet
Area distances work with areas in the Roadnet Transportation Suite to allow you to track
the miles driven in each area (state, province, etc.). If you enter area distances on a regular
basis you can generate printouts of each area individually, for each piece of equipment,
by date, or for all areas and equipment together. You must add the areas and equipment
before you can enter area distances.
Step 2: Click on the Actual Data Entry menu, then Area Distances. The Area Distance
window opens.
Note: To see an updated list of area distances locations, click on the Refresh icon; the
Step 3: In the Area Distance window, click on the Add icon or press [Insert]. The Add
Area window opens.
entry.
Step 4: Choose the Delivery Date. To enter a date, check the box. You can type the
date, or click on the arrow to open a calendar. If you are using the calendar to
change the month, either use the arrows on the top of the calendar to scroll
through the months, or click on the month and select it from the menu that pops
up. To change the year, click on the year and use the arrows to scroll to the
correct year. Click on a date to select it. Make sure the correct part of the date
(months or days) is selected when you are entering the date.
You can enter the distance an individual

piece of equipment travelled in a area on
a specific date.
Step 5: Click on the area arrow to open the Lookup Area window. Double-click the
correct area to select it, or click once and then click the Process icon.
Step 6: Click on the Equipment arrow to open the Lookup Equipment window. Use
the Search feature to find the equipment you are looking for. Once the equipment
308

appears in the list, double-click on it, or click on a piece of equipment and then
on the Process icon, to select it.
Step 7: Enter the distance traveled for that piece of equipment in that area (in miles or
kilometers).
Step 8: Click on the Save icon, or press [Ctrl]+[S] to save the new area distance entry.
Step 9: Repeat Steps 2 8 to add any other area distances.
Step 10: When you are finished adding, click the Close box to close the Add Area
Distance window.
Maintenance icon Actual Data Entry Area Distances Add icon ([Insert])
Existing area distances can be edited or deleted as necessary. See Editing Items and
Operations Guide
309
Combining Routing Sessions

Used with: Roadnet
If you have more than one router creating routes for the same region, you may want to
combine all those routes into a single session so you can evaluate the picture for the
complete day, as well as printing reports. When combining sessions, the routes from the
selected source session are added to the existing destination session. The destination
session must be in the database you are currently working with. The source session can
come from two different places: it can be another session in the current database, or, if
you are using an Access database, it can be an archive database that you created.
In order for the sessions to be combined, the following conditions must exist:
the region you are importing routes for must exist in the database you are importing
into.
all maintenance items (locations, drivers, equipment, etc.) used on the routes must
exist in the database you are importing into.
if you select Import file, the archive must have been created in the same version of
Roadnet as you are importing into.
You can combine the routes into a single session in either the Maintenance module or the
Routing Editor.
Note: If you have multiple regions, verify that the appropriate one is displayed at the
bottom of your screen. To change the region, simply click on the arrow and make
your selection from the drop-down menu that appears.
Step 2: Click on the Tools menu and select Combine Routing Sessions. The Combine
Routing Sessions window opens.
Step 3: In the Source area, select the database where the source session exists.
If you selected Import file, click the [...] icon and browse to the database
containing the source session.
Note: If you are not using an Access database, Current database is the only option
available.
310

Step 4: In the Source Sessions list, select the session containing the routes you want to
add to the destination session.
If both the source session and destination session exist in the same database,
you can not select the same session for both the Source and Destination.
Step 5: In the Destination Sessions list, select the session the routes should be added to.
Step 6: To only move orders into the destination session that do not already exist there,
check Combine orders from Source that do not exist in Destination.
Step 7: Click [Start] to begin the import process.
Step 8: When the import is complete, click the Close box.
Notes: If a routing session is open, it will be closed before the import process begins. If
there are any unsaved changes in the session, you will be asked if you want to save
the changes before it closes.
Only built routes from the source session will be transferred as routes to the
destination session. Orders on active routes will appear in the destination session
as unassigned.
Maintenance icon Tools Combine Routing Sessions [Start]
Operations Guide
311
Updating Service Times Using Service Time Maintenance

Used with: Roadnet
Service time is the amount of time a driver spends at a location and is an integral part of
routing and scheduling in the Roadnet Transportation Suite. Accurate service times are
essential. If the service times for your locations are incorrect, the runtimes for your routes
also may be incorrect. Route costs also are affected by service times. If Roadnet believes
that it will take 3 hours to deliver to an account when it actually takes only 45 minutes,
the system will pay the driver for 3 hours. And if you use dynamic routing, a location with
incorrect service times may not be routed correctly because the system thinks it will take
3 hours to deliver to that location, which may exceed the preferred runtime for the route.
The Roadnet Transportation Suite includes the Service Time Maintenance program, a
powerful tool that makes it easy for you to update the service times for your locations.
Service Time Maintenance uses actual times from delivery history to compute more
accurate service times. If youre using MobileCast, the service times will be based on the
completed time; if not, the service time will be based on actual times entered from
Roadnet. With Service Time Maintenance you can:
enter actual service times for your daily stops quickly and easily.
calculate new service times based on real delivery history.
produce a report to view what updates will be processed before they happen.
update service times by location or service time type.
Before using Service Time Maintenance you need to determine if you want to update the
service times for a location or for a service time type.
By Locationupdates each location for which data exists, using deliveries for
that location only. Each locations service time is updated individually.
By Service Time Typegroups locations together by their service time type and
uses all deliveries for all locations with that service time type to calculate a new
service time (for example, all convenience stores, all restaurants, etc.). The new
service time is applied to all locations with that service time type.
Setting Update Criteria
Roadnets Service Time Maintenance feature allows you to update locations service
times based on completed time if youre using MobileCast, or on actual route data you
enter manually from Roadnet. The Update Criteria box in the Service Time Maintenance
window contains the settings that determine what data will be used to calculate new
service times. You can specify how far the actual service times can be from the planned
to be considered, as well as how many actual entries you must have to update the service
times.
312

Step 2: Click on the Tools menu and select Update Service Times, then select by
Location or by Service Time Type. The Service Time Maintenance window
opens.
Step 3: If you only use fixed service times and do not want variable service times
considered when service times are calculated, check Calculate Fixed Service
Time Only.
Step 4: Enter the allowed time variance for fixed service times and percentage for
variable service times. The variance setting establishes a range of acceptable
values above and below your actual service times. The default setting is 10
minutes for fixed time and 0% for variable time.
Notes: If both the Fixed and Variable Allowed Variances are left blank, all service time
information will be considered to be within the limits and the calculated fixed and
variable times will be used to update the service times. If one of the Allowed
Variances is left blank, all calculated service times for that service type will be
considered within the limits and updated.
Both delivery and pickup quantities will be used to calculate variable service time.
Step 5: Check Update If Outside Variance if you want to consider service times that fall
outside of the established variance. Check Set To Limit if Outside Variance if you
want the service times to be updated to the time defined by the allowed variance
when the newly calculated times are outside the allowed variance.
The Service Time Maintenance

window lets you tailor the settings for
updating service times. Accurate
service times are essential in Roadnet
for run time, cost, and other routing
calculations.
Step 6: Enter the Min Number of Accepted Deliveries and Min Percent of Accepted
Deliveries. Min Number of Accepted Deliveries works with the allowable time
variance setting in Step 1. Roadnet must have the number of deliveries specified,
and those deliveries must fall in the acceptable range, to be used for the
calculation. If the minimum number of deliveries is not met, that locations
service time will not be updated. The default setting is 10 deliveries.
Operations Guide
313
Similar to Min Number of Accepted Deliveries, Min Percent of Accepted

Deliveries specifies the minimum percentage of deliveries that must fall within the
allowable variance in order to be eligible for calculation. If the minimum
percentage is not met, that locations service time will not be updated. The default
setting is 50 percent.
Hint: The greater the number of deliveries used, the more accurate the calculation can
be. If the number of deliveries is too small, any variance in the service time history
will have a greater impact and may result in less accurate computed times.
Step 7: Enter the starting and ending dates to consider in the Date Range area.
arrow to open the calendar. If you are using the calendar to change the month, use
the arrows on the top of the calendar to scroll through the month, or click on the
month and select it from the menu that pops up. To change the year, click on the
Tools Update Service Times By Location/By Service Time Type
Once the update criteria has been established you can print a Service Time Maintenance
report or update the service times. Roadnet Technologies recommends printing and
reviewing the Service Time Maintenance report before updating the service times.
Service Time Maintenance Report
Roadnets Service Time Maintenance feature allows you to update locations service
times based on completed time if youre using MobileCast, or on actual route data you
enter manually from Roadnet. When you run the Service Time Maintenance report you
see exactly how Service Time Maintenance will update the service times for your
locations. The report details which locations times will be updated and which will not,
based on the update criteria you select. You can also see the previous and newly computed
service times for each location and what percentage change will occur. Running the report
does not actually update the service times; it simply shows what will happen when the
update is run.
Warning: Do not run a service time update without running a report first. Once the update
is run the service times are changed and cannot be restored.
opens.
Step 3: Change the update criteria if necessary. See Setting Update Criteria for more
information.
Step 4: On the Service Time Maintenance window, click the [Report] button to
generate the report. The service times are calculated but not updated and
the Service Time Maintenance Report window opens. The information at the top
314

of the report window details the number of pages in the report, as well as the
number of entries (locations).
The report lists each locations name and ID, the previous and computed (new)
service times, the percentage change in service time, and statistics on the number
of deliveries accepted and rejected based on the update criteria. See the Service
Time Maintenance Report Data table for information on the items contained in the
report.
Service Time Maintenance Report Data
Column
Description
Description
Location ID and name
Helper
Indicates whether a helper was used
Update Status
Indicates whether service time will be updated

(ACPT) or not (RJCT) for this location
Prev. Fixed
Locations previous fixed service time
Prev. Var.
Locations previous variable service time
Comp. Fixed
Computed fixed service time using delivery history
Comp. Var.
Computed variable service time using delivery

history
Pct. Changed Fixed
Percentage difference between previous and

computed fixed service time
Pct. Changed Var.
Percentage difference between previous and

computed variable service time
Deliveries Accpt.
Total number of deliveries that fell into the

acceptable range based on the variances you set
Deliveries Reject.
Total number of deliveries that fell outside of the

acceptable range
Deliveries Pct. Used
Deliveries accepted total number of deliveries for

that location
Step 5: You can view the report on the screen, print the report, or export the data in
another format (text file, Crystal Reports, Excel, Lotus, etc.).
To print the report, click the Printer icon. The Print window opens. Click [OK]
to print or [Cancel] to abort.
To export the report data, click the Export Report icon. The Export window
opens. Select the format and destination for the data and click [OK] to export or
[Cancel] to abort.
Tools Update Service Times By Location/By Service Time Type [Report]
Operations Guide
315
Updating Service Times
The Service Time Maintenance tool allows you to easily update your service times based
on actual data. You can update the service times for individual locations or for service
time types. Before updating your service times, you should view the actual data on the
report or the graph.
Warning: Do not run a service time update without running a report first. Once the update
is run the service times are changed and cannot be restored. If, after running the
Service Time Maintenance Report, you agree with the updates to the service
times, you can proceed with the actual service time update.
opens.
Step 3: Change the update criteria if necessary, and run a report to view the projected
data. See Setting Update Criteria and Service Time Maintenance Report for more
information.
Step 4: On the Service Time Maintenance window, click the [Update] button to proceed
or the [Cancel] button to abort. The service times for the current scenario are
updated.
Step 5: After the update is complete, the Service Time Maintenance Report window
opens. You can view the report on the screen, print the report, or export the data
in another format (text file, Crystal Reports, Excel, Lotus, etc.).
To print the report, click the Printer icon. The Print window opens. Click [OK]
to print or [Cancel] to abort.
To export the report data, click the Export Report icon. The Export window
opens. Select the format and destination for the data and click [OK] to export or
[Cancel] to abort.
Step 6: Click the Close box when finished to exit Service Time Maintenance.
Tools Update Service Times By Location/By Service Time Type [Update]
Using the Interactive Graph
In addition to generating Service Time Maintenance reports, the Roadnet Transportation

Suite uses a graph layout as another way to view and update data within Service Time
Maintenance. By using Interactive Graph Options, you can visually access, manipulate,
and update your data on an easy-to-read chart.
Using Graph Options to run Service Time Maintenance provides other options not
available when you update service times by location or service time type. For instance,
you can choose to update locations and service time types according to delivery and
316

quantity type. You can also change the actual service time for any stop, as well as the
newly computed service times. In addition to these service time maintenance features, the
graph also allows you to view all your service times for all your locations and service time
types simultaneously.
Step 2: Click on the Tools menu and select Update Service Times, then Interactive
Graph. The Service Time Maintenance - Graph Options window opens.
Tools Update Service Times Interactive Graph
Step 3: In the Graph By section, decide whether you want to calculate according to a
specific location or service time type, or if you want to calculate all locations and
service time types.
To graph by location, click to select the Location option, and use the arrow to
open the Locations list window and select the location you want to graph.
To graph by service time type, click to select the Service Time Type option, and
use the arrow to open the Service Time Types list window and select the service
time type you want to graph.
To graph by all locations and service time types, click to select the All option.
Step 4: If you only use fixed service times and do not want variable service times
considered when service times are calculated, check Calculate Fixed Service
Time Only.
Step 5: Enter the allowed time variance for fixed service times and percentage for
variable service times. The variance setting establishes a range of acceptable
values above and below your actual service times. The default setting is 10
minutes of fixed time and 0% of variable time.
Notes: If both the Fixed and Variable Allowed Variances are left blank, all service time
information will be considered to be within the limits and the calculated fixed and
variable times will be used to update the service times. If one of the Allowed
Variances is left blank, all calculated service times for that service type will be
considered within the limits and updated.
Both delivery and pickup quantities will be used to calculate variable service time.
Step 6: Check Update If Outside Variance if you want to consider service times that fall
outside of the established variance. Check Set To Limit if Outside Variance if you
want the service times to be updated to the time defined by the allowed variance
when the newly calculated times are outside the allowed variance.
Step 7: When entering date information, you can type in the date, or you can click on
the arrow to open the calendar. If you are using the calendar to change the month,
either use the arrows on the top of the calendar to scroll through the months, or
click on the month and select it from the menu that pops up. To change the year,
select it.
Operations Guide
317
Step 8: Enter the Min # Deliveries and Min% Accept to indicate the minimum number
of data points needed to generate the graph.
Step 9: In the Delivery Type section, select whether you want stops without helpers
(Non Helper) or stops including helpers (Helper) to be computed.
Step 10: In the Quantity Type section, select whether you want Bulk or Non Bulk stops
to be computed.
Step 11: Click [OK] to open the graph or [Cancel] to abort.
For more information on working with the graph, see Using the Graph.
Using The Graph
The Service Time Maintenance feature of the Maintenance module includes a graph that
allows you to view the actual service times for locations or types, and update them as
needed. To open the graph, click on the Tools menu in Maintenance and select Update
Service Times, then Interactive Graph. Once the criteria is selected, the graph will open
showing all existing data. For more information on how to use the features of the graph,
see Data Boxes, Working within the Graph, and Action Buttons.
The Service Time

Maintenance graph
gives you a visual
presentation of your
actual service time
data, and allows you
to alter and update
your service times.
318

Data Boxes
On the left and right of the graph are various data boxes that you can use to view, change,
and update information. Following are descriptions of each of the data boxes and how
they function.
Variance
The Variance data box displays the fixed service time and the variable
service time percentage variance information set up on the Graph
Options window. See Setting Update Criteria for more information.
To edit the variance, right-click on the Variance box to open the
Variance window. Enter the new variance(s) and click the [OK]
button to set. The Variance bounds in the graph will adjust to reflect
your edit.
Previous
The Previous data box displays your current fixed and variable service
times for a location or service time type. This is simply a reflection of
your current settings and is, therefore, not editable.
Computed
The Computed data box displays the newly computed service times
that Roadnet suggests for updating service times.
To edit the computed service times, right-click on the Computed
box to open the Computed Service Times window. Enter the new
service time(s) and click the [OK] button to set. The Computed line in
the graph will adjust to reflect your edit.
Deliveries
The Deliveries data box displays the number of accepted and rejected
deliveries. Accept represents all deliveries that were within the set
variance and were calculated as a result. Reject refers to any deliveries
that exceeded the variance and were therefore not calculated.
Working Within the Graph
In addition to manipulating the data boxes beside the graph, you can also alter information
from within the graph itself. The following bulleted items explain the various ways you
can access these data elements.
To change the actual service time for a stop, right-click on the stop you want to edit; the
Actual Stop Entry window will open. Edit the service time and quantity amounts as
necessary and click the [OK] button to apply. You can also change the service time for a
stop by clicking and dragging the stop to a new point on the graph.
Notes: Hold your mouse over any stop to see a tool tip that displays stop, route, and date
information as well as service time and quantity amount.
Service times collected using MobileCast cannot be updated through the graph.
Hint: See the key at the bottom of the graph to identify the various graph elements.
To change the service time variance, click on either end of one of the variance bounds and
drag it to a different point on the graph. Information in the Variance data box will be
updated accordingly.
Operations Guide
319
To change the computed service time, click on either end of the Computed line and drag
it to a different point on the graph. The Computed data box will be updated accordingly.
Action Buttons
Once you are satisfied with the Service Time Maintenance graph and any changes you
may have made, you can use the action buttons on the left of the graph to apply changes
and/or update service times. The following list explains the function of each item.
ReCompute Svc Times
If you have made changes to the service time variance, your newly
projected service time will need to be recomputed.
To recompute your service times, click on the [ReCompute Svc
Times] button. Your new service times will automatically be
generated.
Save Actual Stops
If you have made any changes to one or more stops service time(s)
and you want these changes applied permanently in Roadnet you will
need to save your changes.
To save actual stop service time changes, click on the [Save Actual
Stops] button. Click [Yes] in the Maintenance window that appears to
save your changes.
Update Svc Times
If you are satisfied with the current computed service times and would
like to apply them to your location or service time type, you are ready
to update your service times.
To update your service times, click the [Update Svc Times] button.
Check the Maintenance window that appears to verify that your
service times are correct, and click [Yes] to complete the update.
If the data results in a negative service fixed or variable service time,
that service time will not be updated.
If the Computed times have a rejected status, the Update Svc Times
button will not be available.
Important: Once you save actual stops or update service times, the service times are changed
and cannot be restored.
320

Maintaining the Database

Used with: Roadnet, Territory Planner, FleetLoader
Because the Roadnet Transportation Suite stores historical routing data, its database can
grow quite large. Database Maintenance helps you to control the size of the database by
archiving or even eliminating unnecessary data. You can easily choose a single session or
a range of dates to archive or delete.
Database Maintenance also performs another helpful task: it compacts the database to
remove all records marked for deletion. When you delete an item (location, driver,
equipment, etc.) from the Transportation Suite, that record is marked for deletion in the
database. When you run Database Maintenance, the program searches the entire database
and removes all of the specified records.
Before starting database maintenance, determine which option will best serve your
current needs. Detailed instructions for using each option are in the sections that follow.
Click on an option for detailed instructions on using that option.
Tools/Database Maintenance/Archive Routing Sessionstakes a snapshot
of your database from a specified session or date(s). The archive function is used
typically when you experience a problem on a particular routing day and need to
send that information to Roadnet Technologies. All information needed to view
routing for the specified session or date(s) is included in the archive. This option
is only available if you are using Microsoft Access.
Tools/Database Maintenance/Delete Routesremoves all records from the
database that occurred during a specified number of days, weeks, or months before
the current routing session, or between a specified date range.
Tools/Database Maintenance/Auto-Delete Configallows you to specify that
the delete should occur automatically during the order import process, and to
control what functions occur automatically.
Tools/Compact Databaselets you reduce the size of the database. When you
run Compact Database items that were marked for deletion are permanently
removed from the database.
Archiving the Database
The archive function of Database Maintenance takes a snapshot of your database from
a specified session or date(s). This snapshot contains all information needed to view the
routes created in the session, such as locations, drivers, etc. This option is only available
if you are using Microsoft Access.
If you want to delete information from the database, see Deleting Historical Database
information or Configuring Automatic Database Maintenance.
Operations Guide
321
Step 2: Click on the Tools menu and select Archive Routing Session. The Database
Maintenance-Archive Routing Sessions window opens.
Step 3: In the Database MaintenanceArchive Routing Sessions window, determine
whether you want to archive by date(s) or for an individual session.
The Database Maintenance Archive window lets you archive

historical data by date range or
for a single routing session. The
archive includes all the data
needed to view the routes for the
archived period.
Archive by Date Rangewill store all data necessary to view routing for all
sessions that occurred between the start and end dates.
Archive by Sessionwill store all data necessary to view routing for a single
session.
Step 4: Click [OK] to start the archive. A Save As window will appear to allow you to
save the archive to a file. You can either accept the default file name and location
or specify a new name and/or location.
To accept the default file name and locationin the format
RoadnetArchiveOnMonthDDYYYY (such as RoadnetArchiveOnJune121999)
in the directory where your Roadnet database is stored click on the [Save]
button.
To change the archives file name, type the new file name in the File name: box.
Then click on the [Save] button.
To change the location where the archive is stored, click the arrow in the Save
in: box and browse your computer for the new location. Then click on the [Save]
button.
Note: Once an archive has been created, you can import that archive into another routing
session to combine the sessions. See Combine from Archive or Combining
Routing Sessions in the Maintenance Module for more information.
Tools Database Maintenance Archive Routing Session [OK]
[Save]
322

Deleting Historical Database Information

Used with: Roadnet, FleetLoader, MobileCast
Note: If you have not been granted permission to control routing session deletions in the
Administration module, you will not be able to use this option.
The Roadnet Transportation Suite database contains a lot of information and can become
large, using a lot of disk space. To help control its size, you can delete historical
information from the database. However, be sure you are finished with the data before you
delete it; once data is deleted, it will not be considered when running reports or service
time maintenance.
Database Maintenance performs another helpful task: it compacts the database to remove
all records marked for deletion. When you delete an item (location, driver, equipment,
etc.) from the Roadnet Transportation Suite, that record is marked for deletion in the
database. When you run Database Maintenance, the program searches the entire database
and removes all of the specified records.
If you want to store a portion of the directory in a separate file, such as a single session,
you can archive that information. If you want old information to be deleted from the
database on a regular basis, you can set up Roadnet to automatically delete data when
orders are imported. See Configuring Automatic Database Maintenance for more
information.
Step 2: Click on the Tools menu and select Database Maintenance, then select Delete
Routes. The Database Maintenance Delete Routing Sessions window opens.
Step 3: On the Database Maintenance Delete Routing Sessions window, determine
whether you want to delete data before a specified number of days, weeks, or
months, between a specified date range, or for a single session.
Note: The Delete data older than and Delete data by date range options can be used when
purging both Roadnet and MobileCast data. The Delete by Session option purges
only Roadnet data.
Operations Guide
323
Step 4: Determine what data you want to delete and whether you want to compress the
database.
Deleting data can help keep
your database from growing
too large, but be sure you are
finished with the data before
you delete it. Any data that is
deleted will not be available for
reports, service time
maintenance, or other options.
Planned Informationdeletes order, route, and stop data for all sessions that
occurred during the specified time period.
Actual Informationdeletes imported onboard computer data or manually
entered actual stop data for all sessions that occurred during the specified time
period.
Dispatch Informationdeletes completed routes in MobileCast that occurred
within the specified time period. This option can only be used with the Delete data
older than and Delete data by date range options.
Driver Duty Periodsdeletes duty period history that occurred during the
specified time period.
Compact Databasesearches the database for and removes any records that
have been marked for deletion (recommended). This option is only available if
you are using Microsoft Access.
Warnings: Deleted data cannot be recovered once the database has been compacted.
If you delete actual information, you will not be able to use that data to calculate
more accurate service times with the Service Time Maintenance program.
Step 5: Click on the [OK] button to delete the data. Delete selected routes one at a time
from the route editor using the [X] button. This button is grayed out if the
necessary privilege to delete is not granted.
Tools Database Maintenance Delete Routes [OK]
324

Configuring Automatic Database Maintenance

Note: If you have not been granted permission to control routing session deletions in the
Administration module, you will not be able to use this option.
By deleting historical information from the database, you can help control the size of the
database. When you run the deletion, you can choose to have the database compacted,
which removes all items marked for deletion, or to have actual routing information
removed. You can delete data manually, or configure the Roadnet Transportation Suite to
delete data when orders are imported.This section provides instructions for setting up the
Roadnet Transportation Suite to delete old data when importing orders.
Step 2: Click on the Tools menu and select Database Maintenance, then Auto-Delete
Config. The Database Maintenance-Auto Delete Configuration window opens.
Warnings: Using the Auto Deletion function will cause Roadnet to delete the data you
select automatically during the order import process.
Deleted data cannot be recovered once the database has been compacted.
If you delete actual information, you will not be able to use that data to calculate
more accurate service times with the Service Time Maintenance program.
Step 3: On the Database Maintenance - Auto Delete Configuration window, determine
that the Roadnet Transportation Suite should delete data older than the specified
length of time before the current routing session (or, the number of days, weeks,
or months worth of data you want to keep in the database) in the Delete Data box.
The Database Maintenance Auto Delete Configuration
window lets you specify certain
data that will be deleted
automatically during the order
import process.
Step 4: Determine which deletion options you want to occur automatically during the
order import process.
Operations Guide
325
Planned Informationdeletes previous order, route, and stop data for all
sessions that occurred during the specified time period.
Actual Informationdeletes imported onboard computer data or manually
entered actual stop data for all sessions that occurred during the specified time
period.
Compact Databasesearches the database and removes any records that have
been marked for deletion (recommended). This option is available only if you are
using Microsoft Access.
Step 5: Click on the [Save] button to save the auto deletion options, or click [Cancel] to
abort.
Tools Database Maintenance Auto-Delete Config
Compacting the Database
Used with: Roadnet, Territory Planner, FleetLoader
To ensure that the Roadnet Transportation Suite is running at peak performance, you
should periodically compact the database, removing extraneous data and shrinking the
overall size of the database. When you run Compact Database, all records you deleted are
permanently removed from the database.
Step 2: Click on the Tools menu and select Database Maintenance, then Compact
Database. The database is compacted.
Tools Database Maintenance Compact Database
326

Transporting Data
Transporting Data
The Roadnet Transportation Suite contains a tool that makes it easy to transport large
amounts of data to Roadnet Technologies Customer Support for troubleshooting
assistance. The Data Transport Tool allows you to create export files containing only the
data needed to troubleshoot a problem, so that a Roadnet Technologies support technician
can work with the data. This feature is only available if you are using an Oracle or SQL
Server database; it can not be used with an Access database.
Step 2: Click on the Tools menu and select Data Transport. The Data Transport Script
Wizard opens.
Step 3: After reading the disclaimer, click [Next].
Step 4: If you wish to transport Territory Planner data, make sure Include planning data
is checked. Select the Planning Sessions you want to include in the export. Click
[Next].
You can select which

sessions you want to export
Territory Planner data for.
Notes: If you did not purchase Territory Planner, this window will not appear.
If you wish to transport RIC data for troubleshooting assistance, select the
planning sessions containing the data you need help with.
Step 5: If you wish to transport Roadnet and/or FleetLoader data, make sure Include
routing session data is checked. Click the Begin Date arrow to open a calendar
and choose the correct starting date. Click on the End Date arrow to open a
calendar and choose the correct ending date. You can enter the dates manually, or
click the arrow to open a calendar. If entering the dates manually, use the arrow
keys to move from the month to day to year field. If using the calendar, to change
Operations Guide
327
Transporting Data
the month use the arrows on the top of the calendar to scroll through the month or
click on the year and use the small arrows to scroll to the correct year. Click on a
date to select it. Routing sessions within those dates appear in the Routing
Sessions list. [Ctrl]+click each session you want to include and click [Next].
You can select which sessions you

want to export Roadnet and
FleetLoader data for.
Notes: If you did not purchase Roadnet or FleetLoader, this window will not appear.
If you wish to transport RIC data for troubleshooting assistance, select the routing
sessions containing the data you need help with.
Step 6: If you wish to transport MobileCast data, make sure Include dispatch data is
checked. Click the Begin Date arrow and choose the starting date for routes to
include in the export. Click the End Date arrow and choose the final date for
routes to include in the export. Click [Next].
You can enter the dates that you

want to export the data for.
328

Transporting Data
Notes: If you did not purchase MobileCast, this window will not appear.
If you wish to transport RIC data for troubleshooting assistance, select the date
range of dispatch data that contains the data you need help with.
Step 7: The Edit window opens. From the Edit window you can change any of the
export options you chose. To change the export option for a products data, click
the [Edit X Options] button for that product and make the changes.
The Edit window shows a

summary of the data you
have chosen to export. If
needed, you can change
your selections from this
window.
Note: All selected data as well as supporting data from the items selected will be
exported.
Step 8: In the Transport script destination folder field, enter where the script and export
files should be stored. You can type the path to the directory, or click the [...]
button and browse to the correct directory. Click [Finish].
Step 9: Several new files are created in the specified directory. These files allow you to
export the selected data from your database so that it can be transported to
Roadnet Technologies Customer Support. The procedure that you should follow
for exporting the data depends on whether you use Oracle or SQL Server.
Contact Roadnet Technologies Customer Support for assistance with exporting
and transporting the data.
Tools Data Transport
Operations Guide
329
Working with Delivery Areas

Note: If you have not been granted permission to perform maintenance in the
Delivery areas are geographic zones you can create for each region. For instance, you
could have a region that covers the Baltimore area, and then delivery areas for each zip
code in the Baltimore area. When orders are scheduled for delivery, orders in different
delivery areas cannot be scheduled for delivery together; in other words they will not be
on the same route. You must have at least one delivery area per region. Delivery areas
must be added before delivery waves and delivery windows can be added.
Step 2: Click on the List menu and select Schedule, then Delivery Areas. The Delivery
Areas window opens, listing all existing delivery areas.
Step 3: In the Delivery Areas window, click on the Add icon. The Add Delivery Areas
window opens
Step 4: Enter a unique identifier to add a delivery areas in the Area field. The Area field
must be completed.
Step 5: Enter a Description for the area.
If the Use XY for Realtime Updates box is

not checked and new locations are not
included in the SuperMatrix, then
RouteNet will be used to calculate the
times and distances for the delivery area.
Step 6: Enter the amount of time, in minutes, that an order can be reserved before being
canceled in the Abandoned Minutes field. If a reserved order exceeds this time, it
will be canceled.
Step 7: Check the Use XY for Realtime Updates box to use the XY calculation method
for new locations that are not included in the SuperMatrix. To use the RouteNet
calculation method, leave the Use XY for Realtime Updates box unchecked.
Hint: It is recommended that you keep the Use XY for Realtime Updates box checked.
The XY calculation method is quicker than the RouteNet calculation method.
Step 8: Click the Save icon, or press [Ctrl]+[S] to save the delivery area.
Step 9: When all delivery areas have been added, click the Close box to close the Add
Delivery Areas window.
330

Maintenance icon List Schedule Delivery Area Add icon ([Insert]) Save
icon ([Ctrl]+[S])
Existing delivery areas can be edited or deleted as necessary. See Editing Items and
Operations Guide
331
Working with Order Classifications
Working with Order Classifications

netScheduler allows you to establish categories that you can use to classify your orders.
For instance, you could create an order classification for large orders called GOLD. Order
classifications can help group orders for filtering and help determine whether to accept an
order or not.
Step 2: Click on the List menu and select Schedule, then Order Classifications. The
Order Classifications window opens, listing any classifications that exist.
Step 3: Click on the Add icon. The Add Order Classifications window opens.
You can use order classifications to
help filter available delivery windows
for orders.
Step 4: Enter a name for the classification in the Class field. The Class field must be
completed.
Step 5: Enter a Description for the order classification.
Step 6: Click on the Close box to close the Add Order Classifications window when all
classifications have been added.
Maintenance icon List Schedule Order Classifications Add iconInsert]Save
icon ([Ctrl]+[S])
Existing delivery areas can be edited or deleted as necessary. See Editing Items and
332

Working with Delivery Waves

You can set up more than one delivery wave, or work shift when deliveries can occur, for
each delivery area and region. Each wave has a delivery day, start time, preferred and
maximum runtimes, and a number of vehicles. You can set up your delivery waves to have
a code so that it can be associated with a particular delivery window that has the same
assigned code. You can choose whether each delivery wave can have reloads. Also, you
can create multiple delivery waves with the same region, delivery area, day, and start
time. This means you can have several depots that all have the same delivery start time.
There are also costs associated with the driver for the wave; this information is used to
calculate how much adding an order to a delivery window costs. You can also create
filters for each delivery wave, which allows open delivery windows to be closed based on
a graduated set of criteria. See Adding Filters to Delivery Waves for more information.
Delivery areas must be created before the delivery waves can be created. You must have
at least one delivery wave for each delivery area.
Step 2: Click on the List menu and select Schedule, then Delivery Waves. The Delivery
Waves window opens.
Operations Guide
333
Step 3: Click on the Add icon. The Add Delivery Waves window opens.
You can create multiple delivery waves with the same region, delivery areas, day, and time.
Step 4: Click on the Area arrow to open a list of delivery areas and click on an area to
select it.
Step 5: Enter the time the delivery wave begins in the Start Time field. You can enter
the time manually, or use arrows to scroll to the correct time. If entering the time
manually, use the arrow keys to move from the hour to minute field. If using the
scroll arrows, click on the correct field (hour or minute) before scrolling. Use a
24-hour clock when entering the time. For example, enter 1:00 PM as 13:00.
Step 6: Enter a code if you want to be able to associate a delivery wave with a delivery
window in the Code field. For example, you have three delivery windows and
two delivery waves. Delivery Window A has a code of AM, Delivery Window B
has a code of PM, and Delivery Window C has no code assigned to it. Delivery
Wave A has a code of AM and Delivery Wave B has a code of PM. You analyze
an order and three possible delivery windows come back. If you choose Delivery
Window B, a route from Delivery Wave B will be used.
334

Step 7: Click on the Color arrow to open the color palette. Select the color that will be
used to identify the orders in this delivery wave. The color is used in Day
Commander if you select to color the orders by delivery wave.
Step 8: In the Delivery Window Metrics section, enter the Outbound Stem Time and the
Inbound Stem Time. You can enter the time manually. Click on the correct field
(hour to minute) before entering the time. Enter as HH:MM. For example, enter
if you want the outbound time to be 13 minutes, enter 00:13.
Step 9: In the Delivery Day section, select the delivery day this wave is for:
If the delivery wave is for a specific date, click on Date and enter the date in the
field. You can type in the date, or click on the arrow to open a calendar. If you are
using the calendar to change the month, either use the arrows on top of the
calendar to scroll through the months, or click on the month and select it from the
scroll to the correct year. Click on a date to select it. This option is only available
if Date is selected.
If the delivery wave is for a day of the week, click Day. Click the arrow to open
a list of the weekdays and select the day for the delivery wave. This option is only
available if Day is selected.
If this is your default delivery wave, which will be used if the delivery date does
not match the date, or day specified for the delivery wave, click Default.
Note: See Creating Delivery Wave and Delivery Window Templates for more
information on the importance of selecting the appropriate delivery day.
Step 10: In the Depot section, choose the depot for the route by selecting the location
Type and entering the ID. If you dont know the ID, enter as much as you know
followed by an asterisk (*) such as 12*, and click the [Query] button. Doubleclick the desired location from the Locations list that appears.
Note: If you need to add a depot, you can click the [New] button. The Add Location
window opens. See Working with Locations for more information.
Step 11: In the Reloads section, check the Enable box if the routes on the delivery wave
can have reloads. If this option is not checked, the delivery wave will not support
reloads.
Step 12: Enter the time necessary to reload the equipment in the Fixed Reload Time
field in the Reloads section. Enter the time manually, or use the arrow to scroll to
the correct time. If entering the time manually, use the arrow keys to move from
the hour to minute field. If using the arrows, click on the correct field (hour or
minute) before scrolling. For example, if it takes 15 minutes to reload, enter
00:15.
Step 13: In the Constraints area, check Capacity if a reload should be created when the
route reaches the equipment type capacity.
Step 14: Check Trip Max Runtime if a reload should be created when the route reaches
a time constraint. Enter the maximum amount of time for a trip before it needs to
Operations Guide
335
be reloaded in the Time field. Enter the time manually, or use the arrows to scroll
to the correct time. If entering the time manually, use the arrow keys to move
from the hour to minute field. If using the scroll arrows, click on the correct field
(hour or minute) before scrolling. For example, if you want the time constraint to
be 4 hours, enter 4:00.
Step 15: In the Cut Off section, check the Same Day box if the cutoff time is for the
same day as the deliveries. If this option is not checked, no orders will be
accepted after the specified time on the previous day.
Step 16: Enter the cutoff time in the Time field in the Cut Off section. Enter the time
manually, or use the arrows to scroll to the correct time. If entering the time
scroll arrows, click on the correct field (hour or minute) before scrolling. Use a
24-hour clock when entering the time. For example, enter 1:00 PM as 13:00. No
orders will be analyzed once the cutoff time has passed.
Step 17: Enter the costs associated with the wave. These costs are used to calculate the
effects of adding orders to a delivery window.
Hourly Wage Durationthe amount of time the driver is paid the hourly wage.
If the route extends beyond this time, any additional time, the driver will be paid
at the overtime wage.
Hourly Wagethe amount the driver is paid per hour.
OT Wagethe amount the driver is paid when working overtime. Once the
routes total runtime exceeds the hourly wage duration, the driver costs will be
calculated using this wage.
Step 18: Click on the Equipment Type arrow to open the Lookup - Equipment Type
window in the Resources section. Double-click on an item to select it or click on
an item and then click the Process icon.
Note: If you need to add an equipment type, you can do so within the Maintenance
module by opening the Equipment Types window and clicking the Add icon.
Step 19: Enter the number of vehicles available for the delivery wave in the Vehicles
field in the Resources section. The number of available vehicles is also the
maximum number of routes that be created for the delivery wave.
Step 20: Click the Time of Day Restriction arrow to open the Time of Day Restriction
Models window in the Resources section. Double-click on a model to select it, or
click on a model and then click on the Process icon. This allows you to choose a
time of day restriction model to designate periods in/during the day in which
restricted equipment types cannot travel in restricted areas or paths. This prevents
some vehicles, such as large trucks, from being routed on restricted roads while
allowing other vehicles, such as small trucks or vans, to use those roads.
Step 21: In the Equipment Capacity Restrictions section, check the appropriate size
alias to have netScheduler check for an equipments available capacity as that
size.
336

Step 22: To compensate for traffic patterns, select one of the following rush hour
options.
No Rush Hourif you do not want to use rush hour models or historical travel
speeds when creating routes.
Use Rush Hour Modelsif you want to use user-created rush hour models when
creating routes. Select the rush hour model that the session should use from the
Rush Hour Model field.
click on the arrow to open the Lookup - Rush Hour Model window. Doubleclick on a model to select it, or click on the model and then on the Process icon.
If you are using RouteNet or SuperMatrix and want to use advanced rush hour
features, such as paths, check Advanced Rush Hour (consider alternative
streets).
advanced rush hour may require additional time when entering the Planning
Editor.
Note: If you need to add a rush hour model, you can do so within the Maintenance
module by opening the Rush Hour page of the Map Properties notebook. Click
Current Rush Hour Model to open the Rush Hour window and click the Add icon.
Use Historical Travel Speedsif you want to use historical traffic data when
creating routes
Step 23: Enter the preferred length of time that you would like the route to last in the
Preferred field of the Runtime section. A route may be longer than the preferred
runtime. Enter the time in the format HH:MM.
Step 24: Enter the maximum amount of time that the route can last in the Maximum
field of the Runtime section.
Step 25: Set up the filters for the wave. See Adding Filters to Delivery Waves for more
information.
Step 26: Set up the skill sets for the wave. See Adding Skill Sets to Delivery Waves for
more information.
Step 27: Click on the Save icon, or press [Ctrl]+[S] to save the delivery wave.
Step 28: When all delivery waves have been added, click the Close box to close the
Add Delivery Wave window.
Maintenance icon List ScheduleDelivery WavesAdd icon ([Insert] Save icon
([Ctrl]+[S])
Operations Guide
337
Creating Delivery Wave and Delivery Window Template

When you are creating the delivery waves and delivery windows, you are actually
creating templates that provide a way to easily have different delivery scenarios available
for different occasions. For instance, if you have extra resources available for Friday
deliveries, you could set up a Friday delivery wave template with more vehicles and
longer runtimes than those limits used for the rest of the week. The template used for any
given day is based on the delivery day information. If an order is placed Monday,
December 11th, netScheduler first looks to see if there is specific delivery day
information for that date; if there is no template for that date, it then looks to see if there
is a template for Monday; if there is no template for Monday, it uses the default template.
338

Adding Filters to Delivery Waves
Adding Filters to Delivery Waves

Filters allow you to close delivery windows based on a specified set of criteria, such as
the order classification and the existing capacity of the wave. For instance, you can create
a filter that prevents a new vehicle from being added to the wave at the end of the day to
fulfill an order. Simply set a filter with an order classification of DEF that will exclude
orders that cost more than $10.00 when 80% of capacity is reached. Alternatively, you
could have a separate filter that allows you to go out of your way to fulfill large or special
orders (Gold orders that cost more that $15.00 when 80% capacity is reached).
You can use the Cost analyzer to determine the parameters of the filters you want to create
as well as testing existing filters. Filters are created from the Delivery Waves window. To
open the Delivery Waves window, click on the List menu and select Schedule, then
Delivery Waves to open a list of delivery waves; double-click on the wave to add the filter
to. Order classifications must be created before filters can be added. You can view
existing filters by selecting Filters from the List - Schedule menu.
Step 1: In the Filters section of the Delivery Waves window, click the Add icon. The
Add Filters window opens.
Step 2: Click the arrow to open the list to select an Order Classification.
You can create filters that give

customers with large orders
more delivery options than
customers with smaller orders.
Step 3: Enter the threshold cost for which the filter takes effect in the Order Stop Cost
field.
Step 4: Enter the percentage of the selected capacity value in the Start At (percentage)
field.
Step 5: Click on the arrow and select whether the filter will be based on the total wave
capacity (Capacity), or on the number of wave vehicles used (Vehicles).
Step 6: Click on the Save icon, or press [Ctrl]+[S] to save the filter.
Step 7: Click the Close box to close the Add Filters window when all filters have been
added.
Existing filters can be edited or deleted as necessary. See Editing Items and Deleting
Operations Guide
339
Adding Skill Sets to Delivery Waves
Adding Skill Sets to Delivery Waves

Skill sets area group of activities that an employee is able to perform. For instance, a
plumber may be able to perform the following activities: install a washing machine, install
a dishwasher, and install a garbage disposal. Then when the routes are created, you can
specify that only employees with the skill set needed to fulfill an order can be assigned to
the route.
Step 1: In the Skill Sets section of the Delivery Waves window, click the Add icon. The
Add Skill Sets window opens.
Step 2: Click the arrow to open a list of Skill Sets and click on a set to select it.
You can enter the number of vehicles
associated with a particular skill set
that represents the number of drivers
who are able to perform the skill sets.
Step 3: Enter the number of Vehicles that has a driver with the selected skill set.
Step 4: Click on the Save icon, or press [Ctrl]+[S] to save the skill set.
Step 5: Click the Close box to close the Add Skill Sets window when all skill sets have
been added.
Existing filters can be edited or deleted as necessary. See Editing Items and Deleting
340

Working with Delivery Windows

Delivery windows are the time spans in which deliveries can occur. You can set up
different delivery windows for each delivery area, and even for each day of the week. You
can set up your delivery windows to have a code so that it can be associated with a
particular delivery wave. You must establish at least one delivery window for each
delivery area for each region. You can create each delivery window individually, or add
several delivery windows for a delivery area simultaneously.
Adding Delivery Windows Individually
can set up your delivery windows to have a code so that it can be associated with a
particular delivery wave. You must establish at least one delivery window for each
delivery area for each region. You can create each delivery window individually, or add
several delivery windows for a delivery area simultaneously.
Step 2: Click on the List menu and select Schedule, then Delivery Windows. The
Delivery Windows window opens, listing all existing delivery windows.
Step 3: Click on the Add icon to open the Add Delivery Window window.
Delivery windows define the time of

day your customers can choose to
receive their deliveries.
Step 4: Click the Area arrow to open a list of delivery areas; click on a delivery area to
select it.
Step 5: In the Delivery Day section, select the proper delivery day for the windows.
If the delivery window is for a specific date, click on Date and enter the date in
the field. You can type in the date, or click on the arrow to open a calendar. If you
are using the calendar to change the month, either use the arrows on top of the
Operations Guide
341
If the delivery window is for a day of the week, click Day. Click the arrow to
open a list of weekdays and select the day for the delivery window. This option is
only available if Day is selected.
If this is your default delivery window, which will be used if the delivery date
does not match the date or day specified for the delivery window, click Default.
Step 6: To change the color that will be used to indicate which orders are being
delivered during that window in Day Commander, click on the arrow and select a
Color from the palette that opens.
Step 7: Enter the code that matches the associated delivery wave in the Code field. For
example, you have Delivery Window 1 with a code of Morning and Delivery
Window 2 with a code of Afternoon. There are two delivery waves; Delivery
Wave 1 with a code of Morning and Delivery Wave 2 with a code of Afternoon.
When yo analyze an order, two possible delivery windows come back. If you
choose Delivery Window 1, a route from Delivery Wave 1 will be used.
Step 8: Enter the time the delivery window begins in the Start Time field. You can enter
the time manually, or use the arrows to scroll to the correct time. If entering the
time manually, use the arrow keys to move from the hour to minute field. If using
the scroll arrows, click on the correct time (hour or minute) before scrolling. Use
a 24-hour clock when entering the time. For example, enter 1:00 PM as 13:00.
Step 9: Enter the time the delivery window ends in the End Time field. You can enter
time manually, use the arrows to move from the hour to minute field. If using the
scroll arrows, click on the correct time (hour or minute) before scrolling. Use a
Step 10: Click the Save icon, or press [Ctrl]+[S] to save the delivery window.
Step 11: When all delivery windows have been added, click on the Close box to close
the Add Delivery Window window.
Maintenance icon ListScheduler Delivery WindowsAdd icon [([Insert]) Save icon
([Ctrl]+[S])
Existing delivery windows can be edited or deleted as necessary. See Editing Items and
Adding Several Delivery Windows Simultaneously
342

must establish at least one delivery window for each delivery area for each region. You
can create each delivery window individually, or add several delivery windows for a
delivery area simultaneously.
Step 2: Click on the List menu and select Schedule, then Delivery Windows. The
Delivery Windows window opens.
Step 3: Click on the Add Multiple Records icon. The Delivery Windows Quick Setup
window opens.
If your delivery windows are evenly

spaced throughout the day, you can use
the Quick Setup window to easily set up
all your windows for the day.
Step 4: Click on the Area arrow to open a list of delivery areas; click on a delivery area
to select it.
Step 5: In the Delivery Day section, select the delivery day you are creating windows
for.
If the delivery window is for a specific date, click on Date and enter the date in
the field. You can type in the date, or click on the arrow to open a calendar. If you
are using the calendar to change the month, either use the arrows on top of the
If the delivery window is for a day of the week, click Day. Click the arrow to
open a list of weekdays and select the day for the delivery window. This option is
only available if Day is selected.
If this is your default delivery window, which will be used if the delivery date
does not match the date or day specified for the delivery window, click Default.
Step 6: Enter the time the delivery window begins in the Start Time field. You can enter
Operations Guide
343
the scroll arrows, click on the correct field (hour to minute) before scrolling. Use
Step 7: Enter the time the delivery window ends in the End Time field. You can enter
the scroll arrows, click on the correct field (hour to minute) before scrolling. Use
Step 8: Enter the length of each delivery window, in minutes, in the Increment
(minutes) field.
Step 9: If a break for a driver, such as lunch, needs to be incorporated into the delivery
window, check the Break box.
Step 10: Enter the start time in the From field. You can enter the time manually, or use
the arrows to scroll to the correct time. If entering the time manually, use the
arrow keys to move from the hour to minute field. If using the scroll arrows, click
on the correct field (hour to minute) before scrolling. Use a 24-hour clock when
entering the time. For example, enter 1:00 PM as 13:00.
Step 11: Enter the end time in the To field. You can enter the time manually, or use the
arrows to scroll to the correct time. If entering the time manually, use the arrow
keys to move from the hour to minute field. If using the scroll arrows, click on
the correct field (hour or minute) before scrolling. Use a 24-hour clock when
Step 12: Click the [OK] button. The Delivery Windows Quick Setup window opens.
Step 13: Click the Save icon, or press [Ctrl]+[S] to save the delivery window.
Step 14: Click the Close box to close the Delivery Windows window when all delivery
windows have been added.
Maintenance icon List Schedule Delivery WindowsAdd Multiple icon
[OK]
Existing delivery windows can be edited or deleted as necessary. See Editing Items and
344

Working with the Business Calendar

netScheduler provides the capability for you to restrict the days on which you deliver
using the business calendar. This means you can restrict specific days of the week from
delivery, as well as unique or one-time holidays. For instance, you could set up a
restriction on Christmas Day deliveries which would occur on the same day every year
(December 25), or you could set up a one time restriction for Thanksgiving, which occurs
on different dates. If you dont deliver on Sundays, you could also set up a restriction for
Sundays. The restrictions you enter here will affect the delivery days offered to your
customers.
Step 2: Click on the List menu and select Schedule, then Business Calendar. The
Business Calendar Non-Working Days window opens, listing all restricted
delivery days.
Step 3: Click on the Add icon. The Add Business Calendar - Non -Working ... window
opens.
You can use the Business Calendar to

block days from being options your
customers can select as delivery days.
You can block a day of the week, or
individual dates, such as holidays.
Step 4: Click on the Area arrow to open a list of delivery areas. Scroll to the correct
delivery area, and click to select it.
Step 5: Enter the delivery day restriction in the Non-Working Day by section.
To exclude a particular date from delivery, such as November 23, 2000, click
on Date and enter the date in the field. You can type in the date, or click on the
arrow to open a calendar. If you are using the calendar to change the month, either
use the arrows on top of the calendar to scroll through the months, or click on the
Operations Guide
345
This option is only available if Date is selected.
To exclude a recurring date from delivery, such as December 25 of all years,
click on Date, then place a check in the Recurring box. Enter the date in the field
below.
To exclude a particular weekday from delivery, such as Sunday, check Day of
Week, then click on the arrow to open a list of days. Select the day you are
restricting. This option is only available if Day of Week is selected.
Step 6: Click the Save icon, or press [Ctrl]+[S] to save the business calendar.
Step 7: When all nonworking days have been entered, click the Close box to close the
Add Business Calendar - Non -Working ... window.
Maintenance icon List Schedule Business Calendar Add icon ([Insert])
Existing business calendar information can be edited or deleted as necessary. See Editing
346

Import
Importing into the Roadnet Transportation Suite
Importing into the Roadnet Transportation Suite

Note: If you were not granted permission to import data in the Administration module,
you will not be able to open this module.
The Import module lets you to import information into the Roadnet Transportation Suite.
You can import locations, location extensions, orders, equipment, drivers, and other
maintenance items, data from an onboard computer, and even routes created in other
software packages. You can even set up a process to automatically import information at
a specified time of day, eliminating the need to import it manual. The information that you
will want to import depends upon the portions of the Roadnet Transportation Suite you
are using. The table below summarizes the items that can be imported when you are using
the various components of the Roadnet Transportation Suite.
Roadnet
Territory Planner
FleetLoader
MobileCast
Locations
Locations
Routed Solution
Locations
Orders
Location
Extensions
Equipment
Equipment
Routed Solution
Equipment
SKUs
Employees
Onboard
Employees
Package Types
Drivers
Combine from
Archive
Drivers
SKU Brands
Containers
Equipment
User Upload
(Export)
Equipment Types
Full Daily
Employees
Equipment Types
Exporting Loaded
Routes
Daily Container
Assignments
Drivers
Pallet Type
Capacities
Static Routes
Send Orders
(Export)
Bay Type
Capacities
Equipment Types
Export Routes
(Export)
Skill Sets
SKUs
Activities
SKU Brands
Skill Set Activities
Depot SKUs
Package Types
Equipment Types
Operations Guide
347
Roadnet
Territory Planner
FleetLoader
MobileCast
Skill Sets
Activities
Skill Set Activities
You can import location data into the Roadnet Transportation Suite, eliminating the need
to enter it manually. This can ensure that the locations in your organizations host
computer match the locations in the PC by creating daily import files that add, change, or
delete locations in the Roadnet Transportation Suite database. See Importing Locations
In addition, you can import the daily order information that you will be routing in
Roadnet. Along with the orders for a location, you can also download any special
instructions that pertain to that order, as well as overrides for location-specific
information, such as service time and time windows. See Importing Daily Orders for more
information.
If you are using MobileCast to track your routes, but not Roadnet or Territory Planner to
create your routes, you can import your daily routes, or simply your container
assignments. See Importing Daily Route Information for more information.
You can also import data from onboard computer systems. Roadnet stores this
information to use when generating a series of actual vs. projected reports, and when
calculating accurate service times based on the imported delivery history. See Importing
OnBoard Data for more information.
If you are using another routing package but want to use FleetLoader to load your trucks,
you can import these routes. See Importing a Routed Solution for more information.
If you are using Territory Planner to create strategic routes, you can import the location
extension information that is used when creating the routes. The location extension
information is specific to a planning session, so you can have different routing
information for the same location in different sessions. See Importing Location
Extensions for more information.
To save you from having to enter the information manually, you can import several
maintenance items, including employees, drivers, SKUs, package types, and equipment.
See Importing Maintenance Items for more information.
You can set up a batch import to run unattended imports of routes, containers, container
assignments, drivers, employees, and almost anything else that can be imported through
the Roadnet Transportation Suite Import Module. See Using the Batch Import Process for
more information.
In addition to importing the information, you can set up the layouts for the various export
functions, such as Send Orders, Export Routes, and User Upload in the Import module.
The difference is that you actually export the data from within the appropriate module,
not the Import module.
348

In order for the Roadnet Transportation Suite to know where information is located in the
import file, or where you want it located in the export file, you need to create layouts for
each type of import/export. The layouts you create for the various imports and exports are
grouped together in layout sets. You can create separate layout sets for different importing
situations, and then simply choose the layout set you want when importing.
Click on the Import icon to open the Import module. You can then choose to import
locations, location extensions, onboard data, a routed solution, orders, maintenance items,
daily routes, or to set up import layouts.
Operations Guide
349
Importing Locations
Importing Locations
Keeping your location information up to date is one of the most important tasks in the
Roadnet Transportation Suite . If the location information, such as service time, geocode,
and time windows, is not correct, it can affect how the location is routed. For instance, if
Roadnet receives an order for a location that does not exist, the order is not routed and is
treated as a not considered order. The program doesnt know where the order should be
delivered and therefore cannot deliver it. Roadnet cannot calculate accurate costs or run
time for locations that do not exist, nor can dynamic routing include that order. If the
location does not exist in Territory Planner, you cannot add or import the location
extension.
Keeping track of all of your locations may seem difficult, especially if your organization
adds a significant number of new locations (customers) on a regular basis. But the
Roadnet Transportation Suite allows you to import a file of new locations at any time, in
addition to allowing you to enter each location manually. You can also use this file to
update or delete information for existing locations.
When you import locations, you can choose to have the Roadnet Transportation Suite
geocode the locations, or you can supply latitude and longitude information in the file. If
you want your locations to be geocoded (which occurs automatically unless you indicate
Do NOT Geocode), the process will start immediately after the locations have been
imported. The import status bar will indicate that geocoding is in process.
Once locations have been imported, you can display the locations in the Maintenance,
Routing Editor, Dispatcher, or Planning Editor modules to determine the method of
geocoding for any location(s). If you are not satisfied with the geocode for a location, you
may edit that location and geocode it manually. See Geocoding the Location for more
information.
Note: When you import new locations, they will all be assigned the time zone selected
on the Locations page of the Maintenance Options notebook. If you are updating
an existing location, the locations time zone will not change.
Step 1: Click on the Import icon to open the Import module. The Import window opens.
Note: If you have multiple regions or scenarios, verify that the appropriate ones are
displayed at the bottom of your screen. To change the region or scenario, simply
click the arrow and select the proper one from the list that opens.
Step 2: Click on the Import menu and select Locations. The Import Locations window
opens.
Notes: The name of the current layout set is displayed in the status bar at the bottom of
the Import module. If this is not the correct set, change it before importing. See
Switching between Layout Sets or more information.
To review or change the layout of the import file, click the [File Layout] arrow
and select Edit from the menu that pops up. See Setting the Import File Layouts
350

Importing Locations
To preview a report summarizing the layout information, including the name and
location of the file being imported and the starting position and length of each
field, click the [File Layout] arrow and choose Preview from the menu that pops
up. A Preview Report window opens, displaying the report. From this window you
can print or export the report.
If you have fields in your import or export layout that overlap, these will be noted
on the report, so that you can fix them if necessary. Overlapping fields when you
import/export data may lead to unexpected results.
To update information for existing locations only, click the Update Existing
Locations Only box.
The Import Locations window shows the

status of the import process. Before you
import locations, you can specify the
format of the latitude and longitude
information and the format of the service
times. When the import is complete you
can view an import log or a report listing
any errors encountered during the
import.
Step 3: To import latitudes and longitudes for your locations, click the Latitude/
Longitude Coordinate Format arrow and select the format of the coordinates in
the raw file. You may import latitudes and longitudes in:
Degrees, minutes, seconds the latitude/longitude must be formatted so that
the minutes and seconds fields are two digits each. The degrees field has no
requirements. For instance, 35 degrees, 2 minutes, 3 seconds should be
imported as 350203, while 5 degrees, 2 minutes, 3 seconds would be imported
as 50203.
Decimal degrees x 10000the latitude/longitude must be at least 5 digits
long. For instance, a latitude of 0.0345 should be imported as 00345, while a
latitude of 51.1234 should be imported as 511234.
Decimal degrees x 1000000 the latitude/longitude must be at least 7 digits
long. For instance, a latitude of 0.032245 should be imported as 0032245, while a
latitude of 51.122234 should be imported as 51122234.
Decimal degreesthere are no requirements for formatting the latitude/
longitude. For instance, all of the following entries are acceptable: .0001 can be
formatted as .0001 and 42.1234 can be formatted as 42.1234.
Operations Guide
351
Importing Locations
Degrees, minutes, seconds, hundredths of secondsthe latitude/longitude

must be formatted so that the minutes and whole portion of the seconds are two
digits each. The degrees field has no requirements. For instance, 35 degrees, 2
minutes, 3.21 seconds should be imported as 35020321, while 5 degrees, 2
minutes, 3.01 seconds should be imported as 5020301.
Degrees, minutes, ten-thousandth of minutesthe latitude/longitude must be
formatted so that the whole number portion of the minutes is two digits. The
degrees field has no requirements. For instance, 35 degrees, 2.1234 minutes
should be imported as 35021234, while 5 degrees, 2.6789 minutes should be
imported as 5026789.
Notes: If you were not granted permission to change import and export options in the
Administration module, you will not be able to change the options selected when
importing locations.
For the coordinates to import correctly, make sure the punctuation is appropriate
for the language setting on your computer.
Step 4: To import service times for your locations, click on the Variable Service Time
Format arrow and choose the format of the variable service times in the raw file.
Variable service time is the time per unit delivered (per piece/case, etc.) . You
may import variable service time in:
minutes (1 = 1 minute)
tenths of minutes (1 = 0.1 minute; 10 pieces = 1 minute
hundredths of minutes (1 = 0.01 minute)
thousandths of minutes (1 = 0.001 minute)
ten-thousandths of minutes (1 = 0.0001 minute)
hundred-thousandths of minutes (1 = 0.00001 minute)
millionths of minutes (1 = 0.000001 minute)
If you do not want the Roadnet Transportation Suite geocode the imported
locations (if you are importing latitude and longitude or simply updating address
information for existing locations but do not want the locations re-geocoded),
check the Do NOT Geocode box.
Step 5: Click the [Import] button to begin the import process. The progress bar displays
the status of the import.
Note: After importing locations you can view the import log or any errors that may have
occurred during the import. Click [View Log] or [View Errors].
Step 6: When the import is complete and you are finished viewing any reports, click the
Close box.
Importer Import Maintenance Locations [Import]
352

Importing Locations
Note: Once locations have been imported, you can edit or delete them as necessary. See
Working with Locations or more information.
Hint: You can use the Importer to delete location records in your database. A record in
the location import file containing only the location ID will delete any
corresponding record(s) in the location database. You can also add a singlecharacter delete field in the import file; Y or y in the delete field will delete
corresponding records. See the Location Import File Available Fields for more
information.
Operations Guide
353
Importing Location Extensions

If you are using Territory Planner to create strategic planning routes, you will need to
import location extension information. Location extensions contain information about the
location that is specific to a planning session, such as the delivery options (service pattern
set), delivery quantity, and possibly even routing information. When importing location
extension information, it is important to remember a few rules:
if the delivery quantity imported does not allow each stop to be equally divisible by
the number of deliveries per cycle, then the total quantity will be increased.
a service pattern set of 0 is called Manual Load Distribution. A location extension

with a service pattern set of 0 will not be routed when Assign Days is run.
if a service pattern is provided and it conflicts with the provided service pattern set,
the stop will be routed according to the service pattern.
make sure the punctuation is appropriate for the language setting on your computer.
Before the location extensions are imported, the locations must be imported. You can
import the locations at the same time as the location extensions, or separately. See
Importing Locations for more information. To see the information that can be imported
with the location extensions, see Location Extensions Layout Fields.
Important: Before importing location extensions for the first time, you should set the
default active weeks and service pattern set. The default active weeks are used if
the active weeks specified in the download file do not match the cycle weeks or if
you specify day loads but not active weeks. The default service pattern set is used
if no service pattern set is specified in the download file. To specify the defaults,
click the [Other Options] button. Select the default service pattern and check the
default active weeks. Typically, the default service pattern set is manual load
distribution and the default active weeks are all weeks.
Step 2: Click on the Import menu and select Location Extensions. The Import Location
Extensions window opens.
Switching between Layout Sets for more information.
354

If you were not granted permission to change import and export options in the
importing location extensions.
Before you import location extensions, click the [Other Options] button
and choose your default service pattern set and default active weeks.
Step 3: If you are importing locations check Import Location in the Locations area and
choose the import locations options. See Importing Locations for more
information on these options.
Step 4: In the Location Extensions area, select the planning sessions you want to import
the location extensions into. To select more than one session, hold down the
[Ctrl] key while clicking on the sessions.
Hint: If necessary, size the columns in the planning session list so that you can see all
the information. The column widths are automatically saved, so the next time you
open the window you will be able to see all the information.
Step 5: If you only want to update existing location extensions in the sessions with new
information, check Update Only. If there are new location extensions in the
import file, they will be ignored.
Step 6: Click the [Import] button. If you are importing locations, they will be imported
into all sessions, and the location extensions will be imported into the selected
sessions and the stops placed on routes as specified.
Operations Guide
355
Note:
After importing you can view the import log or any errors that may have
occurred during the import. Click the [View Log] or [View Errors] button.
Step 7: When all location extensions have been imported, click the Close box to close
the Import Location Extensions window.
Importer Import Maintenance Location Extensions [Import]
356

Importing Daily Orders

Used with: Roadnet
If you are using Roadnet to create your daily routes, you will need to import orders on a
daily basis. The Import module allows you to establish how the order information is read
during the import process. You can specify the import file layout, void orders for specific
locations so that you wont see them in the Routing Editor, send orders for one location
to another location (drop shipments), automatically generate reports on the days orders,
as well as many other options.
Note: When you import future orders, you may receive a warning stating that another
user is working with one or more future orders. If this happens, then you will not
be able to import the future orders until the other user has saved and closed out of
the future order(s).
Step 2: Click on the Import menu and select Orders. The Import Orders window opens.
Click the [Other Options]

button to specify how
Roadnet should handle the
orders it is importing.
Operations Guide
357
Step 3: The Session(s) For section will automatically display the next delivery date and
the session(s) associated with that date. If you are importing orders for a different
date, click the Session(s) For arrow and choose the correct delivery date from the
calendar that appears. This date will be used unless there is one specified in the
import file.
Step 4: Click on the session(s) you want to import the orders into. To select more than
one session, hold down the [Ctrl] key while clicking on the sessions. The orders
will be imported into all of the session you selected.
Note: If there is no session for the selected date or you just want to create a new session,
click the [Create New Session] button. The Add Routing Session window opens.
For more information on this window, see Creating a New Routing Session. Once
this new session is created and saved, it will appear in the Session(s) For list.
Step 5: To remove any existing orders or routes from the session before importing the
new orders, check Clear Session Prior to Import.
Step 6: To set other import options (such as how multiple orders for the same location
are handled, how to handle new orders on built routes, or what reports you want
to print after importing orders), click [Other Options]. See Setting the Order
Import Options for more information.
Note: If you were not granted permission to change import and export options in the
importing orders.
Step 7: To perform database maintenance prior to importing orders, click the
[Database] button. See Database Maintenance for more information.
Note: If you were not granted permission to control deletion of routing sessions in the
Administration module, you will not be able to set this option.
Note:
After importing orders you can view the import log for any errors that may have
occurred during the import. Click [View Log] or [View Errors].
Close box.
Importer Import Orders [Other Options] Import
358

Setting the Order Import Options
importing orders.
Roadnet allows you to configure how the Importer functions when importing order
information. There are several settings you can choose to accomplish different things
during the import process:
choose to combine or alter orders for a location that already exists on a built route (a
route you have finished editing).
choose to alter orders that have been entered manually.
choose to apply location substitution for more than one stop (i.e., multiple stops
within the same building) so that the individual stops are routed together.
designate the letter P to denote pickups.
if you are importing line items and have set up equivalencies, you can have them
considered during the import. Choose the size alias where the original quantity is as
the Source and the size alias where the equivalency quantity will be placed as the
Destination.
choose to automatically lock orders that are combined with existing locked orders.
if you import SKU detail, and if there is more than one occurrence of a SKU in a
record, you can choose to have the SKU fields totaled. If this option is not selected,
the last occurrence of the SKU in the record will determine the total for that SKU.
choose to automatically generate and/or print order summary reports.
You can access these settings from the Import Orders window.
Step 1: On the Import Orders window, click the [Other Options] button. The Import
Orders Options window opens.
The Import Orders

Options window allows
you to determine how
orders will be processed
during the import.
Operations Guide
359
Step 2: Choose the desired settings for handling orders and/or report options. See the
Order Import Options table for an explanation of the settings.
Step 3: To save the settings, click [OK] to return to the Import Orders window.
To exit the Import Orders Options window without saving the settings, click the
Close box.
Importer Import Orders [Other Options] [OK]
Order Import Options
Used with: Roadnet
The following options are available when you are importing daily orders. To set the
options, click the [Other Options] button on the Import Orders window.
Setting
Description
Add Orders To Built

Routes
If you import orders for a location more than once per

session, and that location is already on a built route, the new
order will be added to the location on the built route instead
of creating a new stop in the Routing Editor. Similarly, you
can import new stops to a built route.
Note: If you choose this option you should always verify the
changes to any built routes. Additional orders may result in
routes that exceed equipment capacity or run time settings.
Alter Orders on Built

Routes
If you import orders for a location more than once per

session, and that location is already on a built route, you can
change the order on the built route.
Alter Manually
Entered Orders
If manually entered orders exist, you can change the orders

as necessary, provided you have a matching region ID,
delivery date, session, order number, selector, location ID,
and location type.
Apply Location
Substitution
Groups two or more locations by allotting one location ID to

multiple locations, as set up in Maintenance.
Treat SKU Fields As

Cumulative
If you import SKU detail in the order import, and if there is

more than one occurrence of a SKU in a record (line), the
SKU fields will be totaled. If not selected, the last occurrence
of the SKU in the record will determine the total for that
SKU.
Treat A Selector Of
P As A Pickup
If the letter P appears in the selector field, the Routing

Editor routes it as a pickup.
Use Equivalencies
If you have set up equivalencies for your package types,

choose the size alias that contains the original order quantity
as the Source, and the size alias that will contain the
equivalent quantity (original quantity * equivalency factor)
as the Destination.
360

Setting
Description
Lock Orders that are

Combined with
Existing Locked
Orders
When using the combine orders option, any imported order

that is combined with an existing order will be locked if the
existing order is locked. If not selected, imported orders that
are combined with existing locked orders will not be locked.
Automatically Print
Summary Reports to
Default Printer
Automatically prints all summary reportsVoid Orders,

Orders With An Invalid Location ID, and Orders for
Locations on Built Routes to the default printer. If not
selected, the reports appear in a separate window on the
screen for viewing. You can then print the report or close the
window.
Operations Guide
361
Importing Daily Route Information for MobileCast

If you are not using Roadnet or Territory Planner to create your routes, you will need to
download the routes from your routing package into MobileCast by performing a daily
import. The daily import will download the days routes, including the delivery quantities,
container assignments (if available), any breaks, waits, layovers, or mid-route depots,
unassigneds, scenarios, and other necessary information. Static routes also can be
imported on a daily basis. For more information, see Setting the Import File Layouts,
Importing Container Assignments, or Importing Static Routes.
Notes: If you are using Roadnet or Territory Planner to create your routes, you do not
need to import them. You can simply push the routes from either the Routing
Editor or Planning Editor to MobileCast. See Sending the Daily Routes to
MobileCast or Sending the Planning Routes to MobileCast for more information.
If importing static routes or static route sets, see Importing Static Routes.
Before routes can be imported, all statuses and types must be entered into
MobileCast. If you are importing driver and equipment information for the routes,
the drivers and equipment must also be entered.
All route IDs must be in uppercase for importing purposes. If the stop is an
Unassigned, the route ID must be UNASSIGN, or left blank and the stop number
must be unique.
Step 1: Click the Import icon to open the Import module. The Import window opens.
Note: If you have multiple regions, verify the appropriate one is displayed at the bottom
of your screen. To change the region simply click on the arrow and choose the
region from the list that appears. The scenario shown here is not used during this
import.
Step 2: Click on the Import menu and select Dispatch, then Daily, then Full. The Daily
Import window appears.
and select Edit Layout, then the layout name, from the menu that pops up. See
Setting the Import File Layouts for more information.
field, click the [File Layout] arrow and select Preview Report, then the layout you
want to see the report for, from the menu that pops up. A Preview Report window
362

opens, displaying the report. From this window you can print or export the report.
If you selected to preview all reports, each layout will print on a separate page.
The Daily Import window allows you to

set the route date, specify a location for
the database files, calculate times and
distances and sequence the routes you
import, and set the time zone for your
location. You also import your routes
from this window.
Step 3: Make any necessary changes to the Route Date, Starting Ref. Number, Data
Path, Route Calculation Options, and Time Zone:
Route DateThe date the routes are for; by default, the current date. You can
enter the dates manually, or click the arrow to open a calendar. If entering the dates
manually, use the arrow keys to move from the month to day to year field. If using
the calendar to change the month, use the arrows on the top of the calendar to
scroll through the month or click on the month and select it from the menu that
pops up. To change the year, click on the year and use the arrows to scroll to the
correct year. Click on a date to select it.
Starting Ref. NumberThe first reference number for the route data you are
importing (optional).
Data PathTo import a file from a different location than specified in the File
Layout, check the Override layout data path box, then click the [...] button and
browse to the proper file. You cannot change the name of the file being imported
from here.
Time ZoneThe time zone any times in the import file are in.
Route Calculation OptionsRefers to the amount of processing that
MobileCast does to the routes as they are imported.
NoneThe default option. Routes are imported with the travel times and stop
sequences entered when the data was created outside of MobileCast.
Time and DistanceMobileCast computes its own travel times for the routes
instead of using those in the import files.
Operations Guide
363
SequenceMobileCast computes both travel times and its own best order for
the stops on the routes.
doing a daily import into MobileCast.
If all the dates are the same as the route date, you will only need to supply the
times.
If you are having MobileCast calculate the route for you, the Planned Distance,
Planned Arrival, and Planned Complete fields are not required. If this information
is provided, it will be overwritten with the results of the route calculation.
Step 4: Click the [Import] button to begin the import process. The status bar and
message box in the Import Process window show you the status of the import.
Any problems during importing will halt the process.
Note: After importing the daily routes, click the [View Log] button for a summary of the
routes that were imported.
Step 5: Click the Close box to close the Import Process and Import windows.
Importer Import Dispatch Daily Full
Importing Daily Container Assignments
If your container assignments were not imported with the routes during the daily import,
you can import them separately. This import will download all the containers that are
associated with routes for that day. You must import the routes for that day before you
import the containers. For more information, see Setting the Import File Layouts or Daily
Import.
Note: If you have multiple regions, verify the appropriate one is displayed at the bottom
of your screen. To change the region, simply click on the arrow and select the
proper one from the list that opens. The scenario shown here is not used during
this import.
Step 2: Click on the Import menu and select Daily, then Container Assignments. The
Import Container Assignments window appears.
If you want to review or change the layout of the import file, click the [File
Layout] arrow and select Edit from the menu that pops up. See Setting the Import
File Layouts for more information.
364

field, click the [File Layout] arrow and select Preview from the menu that pops up.
A Preview Report window opens, displaying the report. From this window you
Step 3: Verify that the appropriate date is displayed in the Route field. You can enter the
dates manually, or click the arrow to open a calendar. If entering the dates
manually, use the arrow keys to move from the month to day to year field. If
using the calendar to change the month, use the arrows on the top of the calendar
to scroll through the month or click on the month and select it from the menu that
pops up. To change the year, click on the year and use the arrows to scroll to the
correct year. Click on a date to select it.
Note: If you want to use the route date specified here, you must indicate so when creating
the import layout. To use this date, enter ##ROUTEDATE## in the Constant Text
field and select Replace. Specify a Mask of MM-DD-YYYY.
Step 4: Enter the path and name of the file containing the information for that table in
the Data Path field.
OR
If you dont remember the path and file name, click the [...] button to bring up the
Select File window. You can then find the file in any directory on your hard drive
or server.
The Import Container

Assignments window
allows you to import
containers on a daily
basis.
Step 5: When you import items into a system that already has these items, you need to
tell MobileCast how to handle duplicates. If there are already items for this
region in MobileCast, select an option for situations where items being imported
have the same ID as existing ones:
Operations Guide
365
UpdateUpdate the information in those fields being imported with the

information in the import file.
ReplaceCompletely replace the existing item with the new, imported one. This
means that any changes you made to the original item will be lost.
ErrorIgnore any items in the import file that duplicate existing ones, and give
error messages stating which items were not imported.
importing container assignments.
Step 6: Click the [Import] button to start the import process. The status-indicator bar
and message box in the Import Process window show you the status of the
import.
Note: After importing the container assignments, click the [View Log] button for a
summary of the routes that were imported.
Importer Import Dispatch Daily Container Assignments
366

Importing Static Routes
Importing Static Routes

Static routes are routes that do not change from run to run. You can create static routes in
the Static Route Editor and group them together in sets. To be able to work with the routes
in the Dispatcher, they must first be imported through the Import module. For more
information, see Setting the Import Layouts or Importing Daily Routes into MobileCast.
bottom of your screen. To change the region, simply click the arrow and select the
proper one from the list that opens. The scenario shown here is not used during
this import.
Step 2: Click the Import menu and select Static, then Route or Route Set. The Route
Sets or Routes Import Dialog opens.
The Static Route and Route Set

import module allows you to import
the static routes you set up
previously in the Static Route
module.
Note: The name of the current layout set is displayed in the status bar at the bottom of
If you want to review or change the layout of the import file, you need to open the
layout set and use the Import Layout window. See Setting the Import File Layouts
All route IDs must be in uppercase for importing purposes.
Step 3: Select the route date for which you are importing the routes.
Step 4: Click on the route or route sets to be imported. If importing routes, verify that
the route(s) you are selecting is from the correct route set.
Step 5: Click on the [Import] button. The status of the import is shown in the Import
Status bar; when it is complete, click on the Close box to close the Import Dialog.
Import Import Dispatcher Static Route/Route Set [Import]
Operations Guide
367
Importing a Routed Solution

Before FleetLoader can load your trucks, you need to import the routes created in a
routing package. Once the routes have been imported you can use the Loading Editor to
load the trucks and evaluate and edit how they were loaded.
Step 2: Click on the Import menu and select Routed Solution. The Import Routed
Solution window opens, showing the current layout set in the title bar.
You can choose the delivery

date and session to import
the routed solution into.
Once the solution has been
imported, you can view the
routes in the Routing Editor
or load them in the Loading
Editor.
and choose Edit from the menu that pops up. See Setting the Import File Layouts
Step 3: The Session(s) For section will automatically display the next delivery date and
the session(s) associated with that date. If you are importing routes for a different
date, click the Session(s) For arrow and choose the correct delivery date from the
368

calendar that appears. This date will be used unless there is one specified in the
import file.
Step 4: Click on the session(s) you want to import the routes into. To select more than
one session, hold down the [Ctrl] key while clicking on the sessions. The routes
will be imported into all of the sessions you selected.
Note: If there is no session for the selected date or you just want to create a new session,
click the [Create New Session] button. The Add Routing Session window opens.
For more information on this window, see Creating a New Routing Session. Once
this new session is created and saved, it will appear in the Session(s) For list.
Step 5: To remove any existing routes from the session before importing the new
orders, check Clear Session Prior to Import.
Step 6: Click the Time Zone arrow and select the time zone to use for the routes start
time.
Step 7: To set other import options (such as how to handle SKU information or what
reports you want to print after importing orders), click the [Other Options]
button. See Setting the Routed Solution Options for more information.
importing a routed solution.To perform database maintenance prior to importing
orders, click the [Database] button. See Database Maintenance for more
information.
Note:
After importing the solution you can view the import log for any errors that may
have occurred. Click [View Log] or [View Errors].
Close box.
Import Import Routed Solution [Import]
Note: If you are re-importing orders for a route, make sure you include the route ID and
stop sequence number. If this information is not included, your updated
information may be ignored. If there is any change to a route that has already been
loaded in FleetLoader, the truck will need to be reloaded.
Setting the Routed Solution Options
Roadnet Transportation Suite allows you to configure how the Import module functions
when importing routed solution information. There are several settings you can choose to
accomplish different things during the import process:
choose to apply location substitution for more than one stop (i.e., multiple stops
within the same building) so that the individual stops are routed together.
Operations Guide
369
if you import SKU level detail, you can choose to treat SKU fields as cumulative so
that SKUs are totaled in the Routing Editor instead of listed by the order.
designate the letter P to denote pickups.
choose to automatically generate and/or print order summary reports.
if you are importing line items and have set up equivalencies, you can have them
considered during the import. Choose the size alias where the original quantity is as
the Source and the size alias where the equivalency quantity will be placed as the
Destination.
You can access these settings from the Import Routed Solution window.
Step 1: On the Import Routed Solution window, click [Other Options]. The Import
Routed Solution Options window opens.
The Import Routed Solution

Options window allows you to
determine how orders will be
processed during the import.
Step 2: Choose the desired settings for handling orders and/or report options. See the
Routed Solution Import Options table for an explanation of the settings.
Step 3: To save the settings, click [OK] to return to the Import Routed Solution
window.
To exit the Import Routed Solution Options window without saving the settings,
click the Close box.
Import Routed Solution [Other Options] [OK]
Routed Solution Import Options
The following options are available when you are importing a routed solution. To set the
options, click the [Other Options] button on the Import Routed Solution window
Setting
Description
Apply Location
Substitution
Groups two or more locations by allotting one location ID to

more than one location, as set up in Maintenance.
370

Setting
Description
Treat SKU Fields As

Cumulative
If you import SKU detail in the order import, and if there is

more than one occurrence of a SKU in a record (line), the
SKU fields will be totaled. If not selected, the last occurrence
of the SKU in the record will determine the total for that
SKU.
Treat A Selector Of
P As A Pickup
If the letter P appears in the selector field, the Routing

Editor routes it as a pickup.
Use Equivalencies
If you have set up equivalencies for your package types,

choose the size alias that contains the original order quantity
as the Source, and the size alias that will contain the
equivalent quantity (original quantity * equivalency factor)
as the Destination.
Automatically Print
Summary Reports to
Default Printer
Automatically prints the summary reportsVoid Orders and

Orders With An Invalid Location ID to the printer selected
in Print Setup. If not selected, the reports appear in a separate
window on the screen for viewing. You can then print the
report or close the window.
Operations Guide
371
Importing Maintenance Items

Maintenance imports let you import information about your locations, location
extensions, drivers, employees, equipment, equipment types, SKUs, SKU brands,
package types, skill sets, skill set activities, and containers from other files, instead of
manually entering the information. You can import maintenance items daily, or when
substantial changes occur in your operation. For more information on importing locations
or location extensions, see Importing Locations or Importing Location Extensions. For
more information on creating the layouts, see Setting the File Layouts. To import drivers,
equipment, equipment types, Depot SKUs, employees, SKUS, SKU brands, package
types, skill sets, skill set activities, containers, pallet type capacities, or bay type
capacities, follow the steps below.
Note: Before maintenance items are imported, the corresponding type must be added.
For instance, before employees are imported, employee types must be added. See
Working with Statuses and Types for more information.
Step 2: Click the Import menu and select Maintenance, then the item you want to
import. The Import window appears. Make any necessary changes to the Data
Path.
When you perform a

maintenance import, you
can tell the system where
the data files are located
and how to handle
duplicate records.
372

Note: The name of the current layout set is displayed in the status bar at the bottom of
importing maintenance items.
Step 3: When you import maintenance items into a system that already has employees/
drivers/equipment/equipment types/SKUs/SKU brands/package types/
containers/pallet type capacities/bay type capacitites, you need to tell the
Roadnet Transportation Suite how to handle duplicates. If there are already
maintenance items for this region in the Roadnet Transportation Suite, select an
option for situations where items being imported have the same ID as existing
ones:
UpdateUpdate the information in those fields being imported with the
information in the import file.
ReplaceCompletely replace the existing item with the new, imported one. This
means that any changes you made to the original item, such as where a piece of
equipment is located, will be lost.
ErrorIgnore any items in the import file that duplicate existing ones, and give
error messages stating which items were not imported.
Step 4: If the option to Auto share to all items is available (such as when importing
equipment and employees), check to have the items being imported available for
all regions to use. If this option is selected, all regions will be able to assign these
items to their routes.
Step 5: Click the [Import] button to open the Import Process window.
Note: After importing the daily routes, click the [View Log] button for a summary of the
items that were imported.
Import Import Maintenance Drivers/Employees/Equipment/Depot SKUs/SKUs/
Package Types/Skill Sets/ Skill Sets Activities/Containers/Pallet Type Capacities/Bay Type
Capacities [Import]
Operations Guide
373
lmporting OnBoard Data

Used with: Roadnet
The Roadnet Transportation Suiteallows you to import actual delivery information

obtained from onboard computers, such as Cadec, Tripmaster, XATA, etc. These onboard
computer systems track information such as arrival and departure times, time spent
delivering to a location, travel time between stops, and many other things.
You can use this actual delivery information for several purposes within Roadnet:
generate actual vs. projected reports (actual delivery data vs. Roadnets estimated
delivery times) to ensure Roadnet data accuracy for service and travel times.
use the historical data from actual delivery times to help Roadnet determine more
accurate service times (see Updating Service Times for more information).
view the actual vs. projected reports to track driver productivity issues.
The Import module also allows you to set up how the Transportation Suite reads the
onboard computer information during the import process. You can specify the import file
name and location, as well as the file layout.
Step 2: Click on the Import menu and select OnBoard. The Import OnBoard window
opens.
Step 3: If you have created more than one session for a particular days orders, use the
scroll bar if necessary and choose the appropriate session for the import.
Step 4: Click on the Time Zone arrow and select the time zone the route and stop times
are in.
Step 5: If you want to update the location information with the latitude and longitude
gathered by the onboard computer, check Update Location Table. Click the Lat/
374

Lon Coordinate Format arrow and select the format the latitude and longitude are
in the import file.
importing onboard data
For the coordinates to import correctly, make sure the punctuation is appropriate
Roadnet allows you to

import actual route
information the drivers enter
into onboard computers
while driving the route.
Step 6: Click on [Import OnBoard] to begin the import process. The progress bar
displays the status of the import.
Note:
After importing onboard information you can view the import log or any errors
that may have occurred during the import. Click [View Log] or [View Errors].
Close box.
Import Import OnBoard [Import OnBoard]
Operations Guide
375
Combine from Archive

Used with: Roadnet
The Combine from Archive feature of the Import module allows you to combine multiple
routing sessions into a single routing session in Roadnet. For example, if two computers
are being used during the routing process for a particular day, you can archive the session
from one computer and combine it with the session on the main computer.
In order for the routes to be combined, the following conditions must exist:
into.
the archive must have been created in the same version of Roadnet as you are
importing into.
Note: This option is only available if you are using a Microsoft Access database. To
combine sessions using another type of database, use Combine Routing Sessions
in the Maintenance module or Routing Editor.
your selection from the drop-down menu that appears.
Step 2: Click on the Import menu and select Combine from Archive. The Combine
From Archive window opens.
Step 3: Click on the [...] button and browse to the directory in which the archived
session is stored. Select the database containing the session you want to combine.
The session appears in the Source Session list.
The Combine from

Archive feature allows
you to save and
combine daily routing
sessions from multiple
computers.
Step 4: In the lists, select the Source Session and the Destination Session.
Step 5: To prevent orders from being added to the destination session that did not
already exist in the session, make sure that Combine orders from Source that do
not exist in Destination is not checked.
376

using the Combine from Archive feature.
Step 6: Click the [Start] button to import the routes from the archived session into the
current session.
Import Import Combine from Archive [Start]
Operations Guide
377
Using the Batch Import Process

If you routinely import a large quantity of orders, locations, routes, or other data, you may
want to set up your system to automatically import the information at a specific time. The
Roadnet Transportation Suite includes a batch importer that allows you to use batch files
to automatically import any data that can be imported manually through the Import
module. In order for the suite to import information, you must set up the import options
for each item, allowing you to easily run the batch import process from a command
prompt using the executable tsImpApp.exe.
Note: Combine from archive and onboard data cannot be imported using the batch
import process.
Import options are set in a batch import configuration file, and since these options can
vary from one import item to another, you need to create separate configuration files for
each item. When the batch import process is run, the Import module will look for these
configuration files in the directory defined by the CPCONFIGPATH environment
variable. If this variable does not exist, the Import module will use the configuration file
found in your local directory.
Note: If you are using auto batch import to import various items (locations, orders, etc.),
then you need to create a separate auto batch import for each item you want to
import. For instance, you would have an auto batch import that calls
batchImpLocations to import the locations and a second file that calls
batchImpOrders for importing the orders.
Follow the steps below to set up the batch import process. The setup process only needs
to be done once, although the information can be edited or changed at anytime prior to
running a batch import.
Step 1: Check the environment variables for log in and the directory for your
cpconfigpath. An example of each variable and its path is listed below.
CPCONFIGPATH=directory that holds all batchimp.cfg files
TS_AUTOLOGIN=1
TS_USERNAME=your Transportation Suite username
TS_PASSWORD=your Transportation Suite password
TS_DATABASE=the name of the ODBC connection the Transportation Suite
uses
Step 2: Follow the examples below to create your configuration files for the various
import items. Although the examples contain all possible fields for that specific
configuration file, you do not need to use all the fields.
File Name: batchImpContainerAssignments.cfg
REGION ID=DLOYD
IMPORT TYPE=CONTAINER ASSIGNMENT
LAYOUT SET=CONTAINERS
LAYOUT SET IS GLOBAL=FALSE
378

ROUTE DATE=##TODAY##
DATA PATH=F:\TMP\IMPORT\
CALCULATE TYPE=SEQUENCE
TIME ZONE=8
File Name: batchImpContainers.cfg

REGION ID=DLOYD
IMPORT TYPE=CONTAINER
LAYOUT SET=MAINTENANCE
File Name: batchImpDailyFull.cfg

REGION ID=DLOYD
IMPORT TYPE=DAILY FULL
LAYOUT SET=FULL
ROUTE DATE=##TODAY##
CALCULATE TYPE=SEQUENCE
TIME ZONE=8
File Name: batchImpDrivers.cfg

REGION ID=DLOYD
IMPORT TYPE=DRIVER
File Name: batchImpEmployees.cfg

REGION ID=DLOYD
IMPORT TYPE=EMPLOYEE
File Name: batchImpEquipment.cfg

REGION ID=DLOYD
IMPORT TYPE=EQUIPMENT
Operations Guide
379
File Name: batchImpEquipmentType.cfg

REGION ID=DLOYD
IMPORT TYPE=EQUIPMENTTYPE
File Name: batchImpPackageType.cfg

REGION ID=DLOYD
IMPORT TYPE=PACKAGE TYPE
File Name: batchImpSku.cfg

REGION ID=DLOYD
IMPORT TYPE=SKU
File Name: batchImpSkubrand.cfg

REGION ID=DLOYD
IMPORT TYPE=SKU BRAND
File Name: batchImpLocationExt.cfg

REGION ID=DLOYD
IMPORT TYPE=LOCATION EXTENSION
SESSION DESCRIPTION=4 WEEK CYCLE
SESSION SCENARIO=DELIVERY
UPDATE ONLY=FALSE
File Name: batchImpLocations.cfg

REGION ID=DLOYD
IMPORT TYPE=LOCATION
SCENARIO=DELIVERY
UPDATE ONLY=FALSE
380

NO GEOCODE=TRUE
LAYOUT SET=MD LOCATIONS
File Name: batchImpOrders.cfg

REGION ID=DLOYD
IMPORT TYPE=ORDER
SCENARIO=DELIVERY
LAYOUT SET=ORDERS
DELIVERY DATE=##TODAY##
SUM SKUS=TRUE
AUTO PRINT REPORT=FALSE
CLEAR CURRENT SESSION=FALSE
TIME ZONE=8
File Name: batchImpRoutedSolution.cfg

REGION ID=DLOYD
IMPORT TYPE=ROUTED SOLUTION
SCENARIO=DELIVERY
LAYOUT SET=ROUTED SOLUTION
DELIVERY DATE=##TODAY##
SUM SKUS=TRUE
AUTO PRINT REPORT=FALSE
CLEAR CURRENT SESSION=TRUE
TIME ZONE=8
File Name: batchImpStaticRoute.cfg

REGION ID=DLOYD
IMPORT TYPE=STATIC
ROUTE ID=RTI001
ROUTE SET ID=RTI078
ROUTE DATE=020603
File Name: batchImpStaticRouteSet.cfg

REGION ID=DLOYD
IMPORT TYPE=STATIC
ROUTE SET ID=RTI078
Operations Guide
381
Notes: The options for each configuration file are found in the Import window for that
specific import item. If a value is not specified in the configuration file, the value
last saved on the window will be used.
The acceptable date formats are:
MM-DD-YYYY enter month, day, and year with dashes.
##TODAY## to always import routes for today, enter the date in this
format, with all caps and no spaces.
##NEXTDAY## to always import routes for the next day, enter the
date in this format, with all caps and no spaces.
The acceptable North American time zone integers are:
Eastern=8
Central=10
Mountain=14
Pacific=15
Alaska=16
If you want the importer to use a global layout set, instead of a region specific set, make
sure that LAYOUT SET IS GLOBAL is set to TRUE in the file.
If you want the importer to use the last layout set used, make sure the layout set line in
the file reads LAYOUT SET=##DEFAULT##. If you simply type DEFAULT it will
use the layout set named default.
Once your setup is complete, use the following parameters to run the batch import
process from a command line using the executable tsImpApp.exe. All items are required.
For instance, from the command prompt you may type:
c:>tsimpapp /b /c batchimpdriver.cfg
Parameter
Description
Example
/d
Database options. Pass in the following information:

Transportation Suite username/password@database
/d admin/admin@ts_v30
/b
Sets batch mode.
/c
Looks for the batch import config file.
/c batchimpdriver.cfg
Important: If you have the environment variables from Step 1 set correctly for your
username and password, then you do not need to use the /d parameter.
After running the batch import, you can check the batch import log file to see whether it
has succeeded, failed, or succeeded with additional information. This batch import log file
is located in the same directory as the configuration files, as defined by the
CPCONFIGPATH environment variable.
For more information on importing, see Importing into the Roadnet Transportation Suite.
382

Import Layouts
Import Layouts
Location, location extension, order, maintenance, and onboard computer information can
be imported from a host or another computer into the Roadnet Transportation Suite. For
the suite to accept this information and place it where it can be accessed and used, you
must tell it where to find the information in the import files.Import layouts are used to
communicate this information to the Roadnet Transportation Suite. You can group import
layouts into import layout sets which are customized for your different importing needs.
When preparing import files, you should follow the guidelines below (onboard computer
programs generate these files in their own formats; the Roadnet Transportation Suite is
equipped to read the files from most major onboard systems):
ASCII text file
single record per line
fixed-width fields (but order is not important)
no delimiters
A detailed description and maximum length of the possible fields for the appropriate
import files is shown in the tables located at the end of this section. Refer to these tables
Creating Import Layout Sets
Location, location extension, order, maintenance, and onboard computer information can
be imported from a host or another computer into the Roadnet Transportation Suite. For
the suite to accept this information and place it where it can be accessed and used, you
must tell it where to find the information in the import files. Import layouts are used to
communicate this information to the Roadnet Transportation Suite. You can group import
layouts into import layout sets which are customized for your different importing
needs.Import layout sets allow you to group your import layouts. And, since you can have
multiple layout sets, you can create separate sets for various importing situations.
Before an import file layout can be designed, at least one import layout set must be
created.
Step 1: Click the Import icon to open the Import module. The name of the current Import
Set appears in the title bar.
Step 2: Click the Import menu and select Setup. The Edit Layout Set window appears,
and all layouts in the current Layout Set appear in the list window.
Note: If you have not created any layout sets, the Layout Set window opens; Proceed to
Step 4.
Step 3: Click the Open Layout Set icon. The Layout Sets window appears listing all
existing layout sets.
Operations Guide
383
Import Layouts
Step 4: Click the [New] button. Enter a name for the set, press [Enter] and click the
[Yes] button on the pop-up box to confirm that you want to add a new layout set.
The Edit Layout window appears once again, now displaying the set just added.
Notes: If you want the layout set to be available to all regions, click the [Make Global]
button on the Layout Sets window. If a layout set is global, the word Global will
appear in parentheses after the name in the Status Bar, and a blue circle is
displayed next to it in the layout set list. You cannot include region specific items
if you are selecting to make a layout set global.
The layout set name cannot contain an apostrophe, sometimes known as a single
quote.
Importer Import Setup Open icon
Setting the Import File Layouts
Location, location extension, order, routed solution, maintenance, daily routing, and
onboard computer information can be imported from a host or another computer into the
Roadnet Transportation Suite. For the suite to accept this information and place it where
it can be accessed and used, you must tell it where to find the information in the import
files. Import layouts are used to communicate this information to the Roadnet
Transportation Suite. You can group import layouts into import layout sets which are
customized for your different importing needs.
Some general instructions for creating the import files are shown below. A detailed
description and maximum length of the possible fields for the appropriate import files is
shown in the available fields tables for each import. Refer to these tables for more
information.
The import layouts used to communicate information about where data is located in the
import files all work in the same way, but the data you can import changes. A detailed
description and maximum length of the possible fields for the appropriate import files is
shown in the available fields tables for each import. Refer to these tables for more
information.
Note: If you were not granted permission to configure layouts in the Administration
module, you will not be able to access this option.
Step 2: Click on the Import menu and select Setup. The Edit Layout window opens for
the current layout set.
To change to a different layout set click on the Open Layout Set icon. The Edit
Layout window opens displaying all existing sets. Double-click on the layout set
with which you wish to work.
Step 3: Double-click on the item for which you want to create a layout. The Import
Layout window opens.
384

Import Layouts
Step 4: Enter the path and name of the file containing the information for that table in
the Text File field.
OR
If you dont remember the path and file name, click the Browse icon to bring up
the Select File window. You can then find the file in any directory on your hard
drive or network.
Step 5: To specify a preprocessor or postprocessor, enter the name of the preprocessor/
postprocessor in the Preprocessor/Postprocessor field. A preprocessor is a
program that manipulates the raw data before the Roadnet Transportation Suite
imports it (typically a batch file), while a postprocessor manipulates the data after
the import/export is complete.
Some layout windows may contain additional options to force the data to be left
or right justified, or to trim or remove excess white space from the fields.
Step 6: Specify the position and length of each field in the import file.
At the top of the layout setup window is a ruler with the top line of the import file
displayed underneath. The ruler shows the position of each character in the file.
Below the file display is a list of all the possible fields for the table. To specify the
position and length of each field, select the field in the list and then, in the
displayed line, use the mouse to highlight the entire length of the field. The field
is highlighted with the same color indicated in the list below, and the Start Position
and Length are automatically entered in the appropriate fields.
OR
Click on the field in the list. Enter the starting position in the Start Pos box and the
length in the Length box.
Note: When entering the starting position, start counting at position 0, not position 1.
Step 7: To edit the data in any highlighted field, you may select from the options
explained below:
Operations Guide
385
Import Layouts
UpperCase/LowerCaseCheck to convert all characters in the file to upper or

lower case letters.
Left Justify/Right JustifyCheck to specify if the data should be left or right
justified in the column. If neither option is checked, the default justification will
be used. The default justification is alpha/numeric fields are left justified and
numeric fields are right justified. These options are only available when setting up
export layouts, such as Send Orders or User Upload.
Trim Left/Trim RightCheck to remove excess white space before or after the
data in the field. These options are not available for all layouts.
Constant TextEnter the value that will be associated with all entries for a
particular field and select whether to Replace the entry with this value, Prepend
the value to the entry (insert the value before the entry), or Append the value to
the entry (insert the value after the entry). Simply click on the field name to select
it.
MaskEnter the format for the date and time fields if needed. If a mask is not
specified, the default mask will be used. The acceptable masks are:
HHHour
MIMinute
dday
mmonth
YYYear
YYYYYear
Step 8: Repeat for any other fields in the table. Click on the [OK] button to accept the
layout information.
Importer Import Setup Open icon [OK]
Printing a Layout Report
Once you have created your import layouts, you may want to print a report summarizing
the different layouts. The report includes name of the layout set, the type of import/export,
the file name and location, and the starting position and length for all fields. You can print
layout reports for all the imports and exports; the reports can be printed from the import
or export window, or from the Edit Layout Set window.
Before printing the layout report, you need to set the options that will be used. The options
are set from the Edit Layout Set window; these options will be used for all layout reports
printed for the region.
To set the layout report options, click on the Show Options icon; the Layout Fields
Options window opens. Select the desired options:
386

Import Layouts
Suppress Unused Fieldscheck to only include fields that have an starting

position and length in the report. To include all fields, remove the check.
Group by Layout Typecheck to have the fields grouped according to the
layout they are from. This only applies to imports/exports that use multiple layout
types, such as User Upload and Send Orders. If this option is selected, the report
will separate the field information for each layout type, placing it on a separate
page. If this option is not selected, the fields from the different layouts will be
intermingled, and an additional column is added indicating the layout type the
field is from.
Sort Bychoose the parameter the report should be sorted by, and whether you
want the items listed in Ascending (ABC) or Descending (CBA) order.
To preview a layout report, select the layout type in the Edit Layout Set window, then
click the Preview Layout icon, or right-click and select Preview from the menu that pops
up. To preview a report from the import/export window, click on the [File Layout] button
and select Preview from the menu that pops up. The report opens in a Preview window.
To print a layout report, click the Printer icon on the Preview Report window. The Print
window opens; choose the printer and click [OK]. The report is sent to the printer.
To export a layout report, click the Export Report icon on the Preview Report window.
In the Export window, choose the format to export the report to and click [OK].
Switching Between Import Layout Sets
You can create multiple layout sets to cover different users needs, or even different
importing situations. Each set can be marked as Global, so it is available to all the
different regions. The current Import Set will always be the last set used and its name will
be displayed in the title bar. If you need to change to a different layout set, follow the steps
below.
Step 1: Click the Import icon to open the Import module. The name of the current Import
Set appears in the status bar at the bottom of the Import module.
Step 2: Click the Import menu and select Setup. The Edit Layout Set window appears,
and all layouts in the current Layout Set appear in the list window.
Step 3: Click the Open Layout Set icon. The Layout Sets window appears. Click the
Layout set you want to use and then click the [Open] button.
Location Import File Available Fields
The tables below list the possible fields that can be imported for locations, along with the
maximum length, a brief description, and whether or not the field is required. Any fields
that are bold on the import layout screen are required.
Operations Guide
387
Import Layouts
Note: All fields are string (text) fields unless the data calls for a specific format (such as
date, time, longitude and latitude).
Field
Required
Max.
Length
Description
Location ID
Yes
15
Unique identifier for the location. 3
Location
Name
Yes
60
Name of the location (use name of the business such as Simons Streudelhaus - not owners name
or other).
Location Type
No
Location type ID, such as SIT. The type must

exist in the Transportation Suite. If no type is
specified, the default type is used. 3
Address 1
Yes
50
Complete street address, such as 123 E Main

Street. No PO Box or RR#.
Address 2
No
20
Information that did not fit on the first line, such

as a suite or apartment number.
City
Yes
30
City
State
Yes
20
State or province
Country
No
The two character ISO country code for the

country, such as US for United States or IT for
Italy.
Zip Code
Yes
10
Zip, Zip+4, or Postal Code.
Delivery Days
No
Locations usual days for delivery. Use

MTWRFSU, with no spaces.
Latitude
No
11
In acceptable format that you specify (see

Longitude).
Cross Street
No
30
The nearest intersecting street.
Phone Number
No
20
Area code and phone number (no dashes or

parentheses needed).
Fax Number
No
20
Area code and fax number (no dashes or

parentheses needed)
Account Type
No
Account type ID. The type must exist in the

Roadnet Transportation Suite. If no type is
Service Time
Type
No
Service time type ID. The type must exist in the

388

Import Layouts
Field
Required
Max.
Length
Description
Longitude
No
12
Must be in acceptable format that you specify

Degrees, minutes, seconds the latitude/
longitude must be formatted so that the minutes
and seconds fields are two digits each. The
degrees field has no requirements. For instance,
35 degrees, 2 minutes, 3 seconds should be
imported as 350203, while 5 degrees, 2 minutes,
3 seconds would be imported as 50203.
Decimal degrees x 10000 the latitude/longitude
must be at least 5 digits long. For instance, a
latitude of 0.0345 should be imported as 00345,
while a latitude of 51.1234 should be imported as
511234.
Decimal degrees x 1000000 the latitude/
longitude must be at least 7 digits long. For
instance, a latitude of 0.032245 should be
imported as 0032245, while a latitude of
51.122234 should be imported as 51122234.
Decimal degreesthere are no requirements for
formatting the latitude/longitude. For instance, all
of the following entries are acceptable: .0001 can
be formatted as .0001 and 42.1234 can be
formatted as 42.1234.
Degrees, minutes, seconds, hundredths of
secondsthe latitude/longitude must be
formatted so that the minutes and whole portion
of the seconds are two digits each. The degrees
field has no requirements. For instance, 35
degrees, 2 minutes, 3.21 seconds should be
imported as 35020321, while 5 degrees, 2
minutes, 3.01 seconds should be imported as
5020301.
Degrees, minutes, ten-thousandth of
minutesthe latitude/longitude must be
formatted so that the whole number portion of the
minutes is two digits. The degrees field has no
requirements. For instance, 35 degrees, 2.1234
minutes should be imported as 35021234, while 5
degrees, 2.6789 minutes should be imported as
5026789.
Time Window
Factor
No
Number between 0 and 5 reflecting the

importance of meeting the locations time
windows. 1=low, 5=high, 0=default.
Time Window
Type
No
Time window type. The type must exist in the

Operations Guide
389
Import Layouts
Field
Required
Max.
Length
Description
Equipment
Type
No
15
The unique identifier for the equipment type

assigned to the location. 3
User field 1, 2,
3
No
20 each
User-defined field.
Zone ID
No
15
Zone ID. The type must exist in the Roadnet

Transportation Suite. 3
Priority
No
Priority rating from 1 to 9 (lowest to highest);

locations with a priority of 9 are placed first on a
route in dynamic routing.
Fixed Fee
No
11
The fee that is assigned to the route every time the

location is visited.
Variable Fee
No
11
The fee that is assigned for each unit of cost

received or delivered at the location.
Minimum
Bulk Quantity
1, 2, 3
No
9 each
Minimum bulk quantity for size value.
Override Days
No
Days to apply time window and/or service time

overrides. Use MTWRFSU, with no spaces.
Open Time
No
Time
Locations open time override. Use military time,

such as 09:00 or 13:00.12
Close Time
No
Time
Locations close time override. Use military time,

such as 09:00 or 13:00.12
TW1 Start/
Stop
No
Time
Beginning and end of time window 1 override.

Use military time, such as 09:00 or 13:00.12
TW2 Start/
Stop
No
Time

Helper/No
Helper Fixed
Service Time
No
9 each
Fixed service time with or without a helper, in

tenths of minutes.
Helper/No
Helper
Variable
Service Time
No
11 each
Variable service time with or without a helper.

Must be in acceptable format that you specify: 1
minute units to 0.000001 minute units.2
Bulk Helper/
No Helper
Fixed Time
No
9 each
Bulk fixed service time with or without a helper,

in tenths of minutes.2
Bulk Helper/
No Helper
Variable Time
No
11 each
Bulk variable service time with or without a

helper. Must be in acceptable format that you
specify: 1 minute units to 0.000001 minute units.2
Employee ID
No
15
The employee for this location. 3
390

Import Layouts
Field
Required
Max.
Length
Description
Standard
Instructions
No
255
Location-specific delivery instructions.
Delete
Location
No
If Y, 1, or T is entered, any existing database

record with a matching ID will be deleted. If a N,
0, or F is entered the record will not be deleted.
Any other characters will cause the location not to
be deleted.
Force
Geocode
No
If N, 0 or F is entered, the imported location will

not be geocoded; if a Y, 1, or T is entered the
location will be geocoded. All other characters
will cause the location to be geocoded. You can
use this field to update address information for
existing locations without re-geocoding.
Delete ST
Override
No
If Y, 1, or T is entered in this field, the service

time override(s) for any existing database record
with a matching ID field will be cleared. If a N, 0,
or F is entered, the service time override will not
be cleared. All other characters will not delete the
service time override.
Delete TW
Override
No
If Y, 1, or T is entered in this field, the time

window override(s) for any existing database
record with a matching ID field will be cleared.If
a N, 0, or F is entered, the time window override
will not be cleared. All other characters will be
ignored.
Store Number
No
15
The stores individual number if part of a chain,

such as #10 for Giant #10.
Contact
No
255
The name of the contact person for the location.
Alternate
Contact
No
255
The name of the alternate contact person for the

location.
Service
Failure Notify
Flag
No
Indicates whether or not the location uses service

failure overrides to notify customers when a
delivery is delayed. If a Y, T, or 1 is entered, a
service failure notification is used and the
remaining service failure fields must be used. If a
N, F, or 0 is entered there is no service failure
notification. This information is only used with
MobileCast.
Service
Failure Notify
Type
No
A number indicating how the location wants to be

notified of a delay. The options are 0 (e-mail to
location) or 1 (message to dispatcher). This
information is only used with MobileCast.
Operations Guide
391
Import Layouts
Field
Required
Max.
Length
Description
Service
Failure
Contact
No
64
The e-mail address of the location. This is only

necessary if the Service Failure Notify Type is email. This information is only used with
MobileCast.
Service
Failure
Notification
Minutes
No
The number of minutes the stop should be

delayed before a service failure notification is
created. This information is only used with
MobileCast.
Mark as Void
No
If a Y, 1, or T is entered in this field, the location

will be marked as Void in the Maintenance
module. Orders imported for locations marked as
void will be marked as void.
Preferred
Route ID
No
15
The unique ID of the route the locations orders

should be placed on. If a preferred route ID is
specified, the orders will be placed on that route
during preferred route ID routing in the Routing
Editor. The preferred route ID must be uppercase
and cannot contain spaces. 3
Building
Delivery
Sequence
Numbers
No
A number indicating the sequence the location

should be delivered in relation to other locations
on the same route with the same latitude and
longitude.
Delivery
Radius
No
The distance surrounding a location that the

driver must travel into or out of for MobileCast to
automatically consider that the driver has arrived
or departed a stop. The drivers equipment must
not move within this circle for the amount of time
specified in the
RTS.Telematics.Adapter.exe.config file or either
of the minimum stop time fields on the Dispatch Java Phone page for the stop to be auto-arrived in
MobileCast. Enter the distance in miles.The
maximum value is 9.999.
Time Zone
No
A number indicating the time zone you want all

times relating to the location to be displayed in. If
no time zone is specified, the default time zone is
used. The acceptable North American time zones
are:
Eastern = 8
Central = 10
Mountain = 14
Pacific = 15
Alaska = 16
392

Import Layouts
Field
Required
Max.
Length
Description
Preferred
Pallet Type
No
The ID of the pallet type preferred by this

location.
Accepts
Manufacturer
Pallet Type
No
Specifies if manufacturer pallet types can be

delivered to this location, if the order is large
enough and the equipment will accept that pallet
type. Enter T, Y, or 1 for Yes; F, N, or 0 for No.
You must specify the mask indicating how the data is formatted. If no mask is specified, the Roadnet
Transportation Suite will assume your data is formatted according to the default mask. The default masks
are:
For date fields: YYYY-MM-DD
For time fields: HH:MI
For running time fields: HH:MM
For date/time fields: YYYY-MM-DD HH:MI:SS
2If
3
none is specified, default will be used.
You cannot enter a blank space or the following characters in this field: % , ? \
Location Extensions Import File Available Fields

The table below list the possible fields that can be imported for location extensions, along
with the maximum length, a brief description, and whether or not the field is required.
Any fields that are bold on the import layout screen are required
Field
Required
Max.
Length
Description
Location ID
Yes
15
The unique identifier for the location. 1
Location Type
No
The type of location (SIT, DPT, etc.). If a type is

not specified, the default type will be used. 1
Territory ID
No
15
The ID of the territory the location is on. If the

territory does not exist in the planning session,
Territory Planner will create it. If the location
extension is not on a territory (that is, if it is
unassigned), enter *U*. 1
Service
Pattern Set
No
The service pattern set for the location. If one is

not specified, the default service pattern set will
be assigned. 1
Operations Guide
393
Import Layouts
Field
Required
Max.
Length
Description
Size 1, Size 2,
Size 3
No
16 (9.6)
each
The total quantity for the cycle measured as that

size alias. If the delivery quantity imported does
not allow each stop to be equally divisible by the
number of deliveries per cycle, then the total
quantity will be increased. The number of digits
to the right of the decimal is established in the
Roadnet Transportation Suite prior to import.
While it is not required that you import a quantity,
it is highly recommended. If you do not import a
size 1 with your location extension, the location
extension will be assigned the minimum quantity
necessary to meet the service pattern set.
Service
Pattern
No
The service pattern assigned to the location

extension. The stops will be routed based on the
specified service pattern. If the service pattern
specified is not part of the service pattern set, the
service pattern will be used to route the stop. 1
Active Weeks
No
24
Indicates whether or not the location should be

routed that week. The location extension will be
placed on routes for the specific active weeks.
The active weeks field should equal the length of
the cycle; an X in a space means the stop is
delivered that week; a blank means no delivery
that week. If the active weeks do not match the
service pattern set, the stop will be routed based
on the active weeks. If the specified active weeks
are invalid for the cycle, the default active weeks
will be used. If you are uploading active weeks
with User Upload in the Planning Editor, leave 24
spaces for this field.
Assign Days
Flag
No
Indicates whether or not the location extension

should be included when Assign Days is run. A Y,
1, or T in the field means to include the location
in Assign Days. A N, 0, or F means to exclude the
location from Assign Days. All other characters
will cause the assign days flag to be set to yes.
Day String
No
Indicates which days the extension should be

routed. The location extension will be placed on
routes on the specified day(s). The valid days are
MTWRFSU. If the day string does not match the
specified service pattern set, the stop will be
unassigned. If using with User Upload to export
route information, the day string starts with
Sunday.
394

Import Layouts
Field
Required
Max.
Length
Description
Day Shift
No
The number of days the location extension should

be shifted when Day Shift is run. Must be
between 0 and 7.
Previous
Depot ID
No
15
The unique identifier of the depot the extension

previously was delivered from. 1
Previous
Territory ID
No
15
The ID of the territory the location extension was

previously routed on. If the location extension is
not on a territory (that is, if it is unassigned), enter
*U*. 1
Previous
Weeks
No
24
Indicates the active weeks the location extension

was previously routed on. The previous weeks
field should equal the length of the cycle; an X in
a space means the stop is delivered that week; a
blank means no delivery that week.
Previous Days
No
The day string indicating the days the location

extension was previously routed on.
Week
No
The number of the week the location extension

should be delivered (ex. 2). This field is used
when you are specifying the stop number by day.
Monday/
Tuesday/
Wednesday/
Thursday/
Friday/
Saturday/
Sunday Stop
Number
No
3 each
The number the stop is on that days route. If this

does not match the service pattern or service
pattern set, this information will be ignored. If the
stop number is entered, the week number must
also be entered; if the week number is not entered,
the same stop number will be used for each active
week. If you are importing Active Weeks and Day
String, you should not import the stop number.
Monday/
Tuesday/
Wednesday/
Thursday/
Friday/
Saturday/
Sunday Load
No
16 (9.6)
each
The delivery quantity for all of that day (i.e.

Monday) in the cycle. If the load is defined the
territory ID and active weeks must be specified; if
the active weeks are not specified, the default
active weeks will be used. If you are importing
Active Weeks and Day String, you should not
import the Day Loads.
Delete Record
No
A single character indicating whether or not to

delete the location extension. A Y, 1, or T means
to delete the record; a N, 0, or F means not to
delete the records. All other characters will not
delete the record.
Service Time
Type Override
No
The service time type that should be used for the

extension in the planning session(s). If no service
time type is specified, the locations service time
will be used. 1
Operations Guide
395
Import Layouts
Field
Required
Max.
Length
Description
Anchor Days
Range
No
The number of days from the Previous Days that

the location extension can receive their deliveries
when a re-route is done. Must be a number from
0 to 6. If no anchor days range is specified, 0 will
be used.
Anchor Any
Day Flag
No
Specifies if Any Day will be selected for day

anchoring. A Y, 1, or T means Any Day will be
selected; a N, 0, or F means Any Day will not be
selected. If no anchor any day flag is specified
and no anchor days range is specified, Any Day
will be selected. If no anchor any day flag is
specified but an anchor days range is specified,
Any Day will not be selected.
Anchor Days
Wrap Flag
No
Specifies whether the anchor day range will be

allowed to wrap across non-delivery days. A Y, 1,
or T means Allow Wrap will be selected; a N, 0,
or F means Allow Wrap will not be selected. If no
anchor day wrap flag is specified, Allow Wrap
will be selected.
Anchor Weeks
Range
No
The number of weeks from the Previous Weeks

that the location extension can receive their
deliveries when a re-route is done. Must be a
number from 0 to one less than the total number
of weeks in the planning sessions cycle. If no
anchor weeks range is specified, 0 will be used.
Anchor Any
Week Flag
No
Specifies if Any Week will be selected for week

anchoring. A Y, 1, or T means Any Week will be
selected; a N, 0, or F means Any Week will not be
selected. If no any week flag is specified, Any
Week will be selected.
Anchor Weeks
Wrap Flag
No
Specifies whether the anchor week range will be

allowed to continue through the first and last
week of the delivery cycle. A Y, 1, or T means
Allow Wrap will be selected; a N, 0, or F means
Allow Wrap will not be selected. If no anchor any
week flag is specified and no anchor week range
is specified, Any Week will be selected. If no
anchor any week flag is specified but an anchor
week range is specified, Any Week will not be
selected.
User Defined
Fields
No
255
The contents of the user-defined fields for the

location extensions. If importing numeric userdefined fields, you should only import whole
numbers; any numbers beyond the decimal place
will be deleted when the information is exported
out of Territory Planner.
396

Import Layouts
1
Daily Orders Import File Available Fields

Used with: Roadnet
The tables below list the possible fields that can be imported for daily orders, along with
the maximum length, a brief description, and whether or not the field is required. Any
fields that are bold on the import layout screen are required.
Field
Required
Max.
Length
Description
Location ID
Yes
15
Location Type
No
The location type, such as SIT. If no type is

imported, the default type will be used. 5
Order Number
No
15
Unique identifier for each order. You may have

multiple orders for each location. If you are using
order sourcing, both parts of the order pair must
have the same order number.
Note: This field is required if you have
MobileCast installed. If you do not have
MobileCast, it is strongly recommended that you
include this field. 5
Order Selector
No
Single-character field used to designate orders

that require special treatment. This field is only
used in the Roadnet Transportation Suite if you
are using Roadnet and FleetLoader and having
Roadnet capacitize your trucks for pallets.
Order Type
No

that require special treatment. Character must be
one of four letters: O = Delivery, F = Future, P =
Pickup, R = Return. This field affects the way the
Roadnet Transportation Suite will process and
route data. If you are using order sourcing, one
order of the pair needs to be a type P and the
second a type O. 5
Void Order
No
An order that has been voided. Enter Y, 1, V, or T

to void the order; enter No, 0, or F to not void the
order. Any other character will not void the order.
Total of Size 1,
2, 3
No
16 (9.6)
each
Quantity of the size 1,2, or 3 measurement (such

as pieces). The number of digits to the right of the
decimal is established in the Roadnet
Transportation Suite prior to the import.
Operations Guide
397
Import Layouts
Field
Required
Max.
Length
Description
Subtotal of
Size 1, 2, 3
Category 1, 2,
3
No
16 (9.6)
each
Quantity of the size/category measurement (such

as the number of frozen pieces). The number of
digits to the right of the decimal is established in
the Roadnet Transportation Suite prior to the
import.
Add Fixed
Service Time
No
Amount of extra service time added to a delivery

(for merchandising, customer service, etc.) in
minutes.
Special
Instructions
No
255
Additional delivery instructions for the order.
Date Added
No
Date
Date and time the order was entered.1
Taken By
No
Name of the employee who entered the order.
Open Time
No
Time
Order open time override. Use military time, such

as 09:00 or 13:00.123
Close Time
No
Time
Order close time override. Use military time, such

as 09:00 or 13:00.123
TW1 Start/
Stop
No
Time

TW2 Start/
Stop
No
Time

Item ID
No
32
Unique identifier of a SKU or activity. This field

is only used if importing SKU-level detail or
activities. If an item ID is specified, a Item Type
must be specified.4, 5
Item Type
No
Indicates whether the Item ID is for a SKU (S) or

activity (A).4, 5
Total SKU
Size 1, 2, 3
No
16 (9.6)
each
Quantity of the size measurement for the SKU.4
Session Date
No
Date
The date of the session you want the order added

to. If a date is not specified, the order will be
added to the session(s) specified on the Import
Orders window.1
Preferred
Origin ID
No
15
The unique identifier of the location you want to

be the origin for the route. 5
Preferred
Origin Type
No
The type for the location you want to be the origin

of the route. Usually this will be DPT. 5
Preferred MidRoute
Sourcing
Depot ID
No
15
The unique ID of the preferred delivery location

for an order. This is only used for a pickup order
when Mid-Route Sourcing is enabled.
398

Import Layouts
Field
Required
Max.
Length
Description
Preferred MidRoute
Sourcing
Depot Type
No
The location type of the preferred delivery

location for an order. If left blank, a type of DPT
will be assigned if a valid Depot ID is provided. If
no valid Depot ID exists, a Preferred MRS Depot
will not be assigned. This is only used when MidRoute Sourcing is enabled.
Dependency
No
A number between 0 and 100 assigned to an

order. The number 1 receives the highest priority.
If two orders with the same order number are
assigned the same dependency, the pickup will
occur before the delivery, with no stops in
between. This is only used when Mid-Route
Sourcing is enabled.
Force Bulk
Service Time
No
Indicates whether the order should use bulk

service times, even if the quantity does not meet
the locations bulk threshold. Enter Y, 1 or T to
force bulk service times; a N, 0, or F means do not
force the bulk service time. All other characters
will cause the order not to be forced bulk.
Order User
Defined Field
1, 2, 3
No
20 each
The contents of the user-defined field. The name

of this field is set in the Maintenance Options
notebook.
SKU User
Defined Field
1, 2, 3
No
20 each
The contents of the SKU user-defined field. The

name of this field is set in the Maintenance
Options notebook.
Daily Increase
Size 1, 2, 3
No
16 (9.6)
each
The amount the quantity for the size alias

increases each day between the begin and end
date.
Order Begin
Date
No
Date
The first date the order can be delivered.1
Order End
Date
No
Date
The date the order must be delivered by.1
Urgency
Factor
No
A number between 0 and 100 indicating the

importance of delivering the order on the
beginning date.
Daily Urgency
Factor
Increase
No
The amount the orders urgency increases each

day it is not delivered.
Preferred
Route ID
Override
No
15
The unique ID of the route the order should be

placed on. If a preferred route ID is specified, the
orders will be placed on that route during
preferred route ID routing in the Routing Editor.
The preferred route ID must be uppercase and
cannot contain spaces. 5
Operations Guide
399
Import Layouts
1
are:
2Overrides
in the order import file are temporary overrides (for that delivery date only). For permanent
overrides, use location maintenance
3
Any missing values will be replaced with the location's time window's type's corresponding value for the
session's scenario. If this would cause the time windows to fall outside the order's open and close times, the
time windows will be adjusted to within the order's open and close times.
4
The item related fields and line item user-defined fields must always be the last fields in each record. The
Roadnet Transportation Suite will automatically repeat the sequence you have specified as the Item ID,
SKU size measurements, Item Type, and line item user-defined fields until the end of the record, so you
should specify only the first group of item ID, item type, sizes, and line items in the Import Orders Layout
window. See the example below.
ABC123 RN7772 S 100 110 2500 Breakable Stackable ID RN7773 S 89 101 2225 Fragile Produce ID
The underlined section of the sample above shows the item ID, item type, three size measurements, and
three line item user-defined fields. Note that only the first set of item ID, item type, sizes, and user-defined
fields is underlined. If you are importing both SKUs and activities, the activity fields must match the SKU
fields. This means that you will need to leave space for the quantity, even if it is empty.
5
Click on a link below for more information on that topic:

Routed Solution Import File Available Fields
The tables below list the possible fields that can be imported for a routed solution, along
with the maximum length, a brief description, and whether or not the field is required.
Any fields that are bold on the import layout screen are required. If you are importing
waits, breaks, or layovers, associate the break with the stop preceding it, and a wait or
layover with the stop following it
date, time, longitude and latitude)..
Field
Required
Max.
Length
Description
Location ID
Yes
15
The unique identifier for the location. 5
Location Type
No
The type for the location, such as SIT or DPT. If

no type is specified, the default will be used. 5
400

Import Layouts
Field
Required
Max.
Length
Description
Order Number
No
15
Unique identifier for each order.

Note: This field is required if you have
MobileCast installed. If you do not have
MobileCast, it is strongly recommended that you
include this field. 5
Order Selector
No
Single-character field used to designate order that

require special treatment. This field does not
affect the way Roadnet processes or routes the
order.
Order Type
No

that require special treatment. Character must be
one of four letters: O = Delivery, F = Future, P =
Pickup, R = Return. This field affects the way
Roadnet will process and route data. 5
Void Order
No
An order that has been voided. Enter Y, 1, V, or T

to void the order; enter No, 0, or F to not void the
order. Any other character will not void the order
Total of Size 1,
2, 3
No
16 (9.6)
each
Quantity of the size 1, 2, or 3 measurement (such

as pieces). The number of digits to the right of the
the decimal is established in Roadnet
Subtotal of
Size 1,2, 3
Category 1, 2,
3
No
16 (9.6)
each
Quantity of the size/category measurement (such

as frozen pieces). The number of digits to the
right of the decimal is established in Roadnet
Add Fixed
Service Time
No
Amount of extra service time added to a stop (for

merchandising, customer service, etc.) in
minutes.
Special
Instructions
No
255
Date Added
No
Date/time
Date and time the order was entered.1
Taken By
No
ID of the employee who entered the order.
Open Time
No
Time
Order open time override. Use military time, such

as 09:00 or 13:00.123
Close Time
No
Time
Order close time override. Use military time, such

as 09:00 or 13:00.123
TW1 Start/
Stop
No
Time

TW2 Start/
Stop
No
Time

Operations Guide
401
Import Layouts
Field
Required
Max.
Length
Description
Item ID
No
32
Unique identifier of the SKU or activity. This

field is used only if you are importing SKU-level
detail or activities. If importing items, you need to
specify the item ID.4, 5
Item Type
No
Indicates whether the item ID is for an SKU (S) or

an activity (A).4, 5
Total SKU
Size 1, 2, 3
No
16 (9.6)
each
Quantity of the size measurement for the SKU.

The number of digits to the right of the decimal is
established in the Roadnet Transportation Suite
prior to import.4
Session Date
No
Date
The date you want the order to be delivered. If a

date is not specified, the order will be routed on
the date specified on the Import Routed solution
window.1
Preferred
Origin ID
No
15
The unique ID of the location you want the order

to come from, usually the depot the order is
coming from. This does not need to match the
routes origin, and will only be used if routes are
created in the Routing Editor. 5
Preferred
Origin Type
No
The type for the location you want the order to

come from, usually DPT. This field is used in
conjunction with the Preferred Origin ID.This
does not need to match the routes origin, and will
only be used if routes are created in the Routing
Editor. 5
Force Bulk
Service Time
No
Indicates whether the order should use bulk

service times, even if the quantity does not meet
the locations bulk threshold. Enter Y or T to
force bulk service times.
Route ID
No
15
The ID for the route. If a route ID is not imported,

the order will be unassigned. If you will be doing
subsequent transmissions, include the route ID in
those imports. All route IDs must be uppercase.5
Stop Sequence
No
The stop number on the route. This field is 1based. If you will be doing subsequent
transmissions, include the stop sequence in those
transmissions.
Unpaid Wait
No
The length of the unpaid wait, in minutes.
Paid Wait
No
The length of the paid wait, in minutes.
Unpaid Break
No
The length of the unpaid break, in minutes.
Paid Break
No
The length of the paid break, in minutes.
402

Import Layouts
Field
Required
Max.
Length
Description
Unpaid
Layover
No
The length of the unpaid layover, in minutes.
Paid Layover
No
The length of the paid layover, in minutes.
Driver 1, 2 ID
No
15 each
The ID of the driver(s) assigned to the route. 5
Preferred Skill
Set
No
15
The ID of the skill set you would like any

employee assigned to the route to have. Normally
the skill set would allow the employee to
complete order activities on the route. This
information is only necessary if you are using
order activities. 5
Equipment ID
No
20
The ID of the equipment assigned to the route. 5
Equipment
Type ID
No
15
The ID of the equipment type assigned to the

route. 5
Route Start
Date
No
Date
The date the route is scheduled to begin. If a start

date is not specified, the session date is used.1
Route Start
Time
No
Time
The time the route is scheduled to begin. If the

start time is not defined, the default start time is
used.1
Route
Description
No
30
A description of the route, such as the city name.
Origin Depot
ID
No
15
Last Stop is
Destination
No
Indicates whether or not the route returns to a

depot, or ends at the last stop. A Y, T, or 1
indicates the last stop is the routes destination; a
N, F, 0, or blank indicates the route returns to the
depot.
Destination
Depot ID
No
15
The identifier of the depot where the route ends.5
Order User
Defined Field
1, 2, 3
No
20 each
The contents for the order level user defined

fields. The name of this field is set in the
SKU User
Defined Field
1, 2, 3
No
20 each
The contents of the SKU user defined field. The

name of this field is set in the Maintenance
Options notebook.
Daily Increase
Size 1, 2, 3
No
16 (9.6)
each
The amount the quantity for the size alias

increases each day between the begin and end
date.
Order Begin
Date
No
Date
The first date the order can be delivered.1
The identifier of the depot where the route begins.
Operations Guide
403
Import Layouts
Field
Required
Max.
Length
Description
Order End
Date
No
Date
The date the order must be delivered by.1
Urgency
Factor
No
A number between 0 and 100 indicating the

importance of delivering the order on the
beginning date.
Daily Urgency
Factor
Increase
No
The amount the orders urgency increases each

day it is not delivered.
Pre-Route
Time
No
The number of minutes to add to the route after

the driver arrives at the origin but before
departing. Since the driver is paid for pre-route
time, it is included when the total route time is
calculated.
Post-Route
Time
No
The number of minutes to add to the route after

the driver arrives at the destination but before
clocking out for the day. Since the driver is paid
for the post-route time, it is included when the
total route time is calculated.
Preferred
Route ID
Override
No
15
The unique ID of the route the order should be

placed on. If a preferred route ID is specified, the
orders will be placed on that route during
preferred route ID routing in the Routing Editor.
The preferred route ID must be uppercase and
cannot contain spaces. 5
Dispatch ID
No
The unique identifier of the dispatcher who will

be tracking the route. 5
are:
2Overrides
in the order import file are temporary overrides (for that delivery date only). For permanent
overrides, use location maintenance.
3
Any missing values will be replaced with the location's time window's type's corresponding value for the
session's scenario. If this would cause the time windows to fall outside the order's open and close times, the
time windows will be adjusted to within the order's open and close times.
4
The item related fields and line item user-defined fields must always be the last fields in each record. The
Roadnet Transportation Suite will automatically repeat the sequence you have specified as the Item ID,
SKU size measurements, Item Type, and line item user-defined fields until the end of the record, so you
should specify only the first group of item ID, item type, sizes, and line items in the Import Orders Layout
window. See the example below.
404
ABC123 RN7772 S 100 110 2500 Breakable Stackable ID RN7773 S 89 101 2225 Fragile Produce ID
Import Layouts
The underlined section of the sample above shows the item ID, item type, three size measurements, and
three line item user-defined fields. Note that only the first set of item ID, item type, sizes, and user-defined
fields is underlined. If you are importing both SKUs and activities, the activity fields must match the SKU
fields. This means that you will need to leave space for the quantity, even if it is empty.
5You
cannot enter a blank space or the following characters in this field: % , ? \
OnBoard Import File Available Fields

Used with: Roadnet
The tables below list the possible fields that can be imported for onboard data, along with
the maximum length, a brief description, and whether or not the field is required. Any
fields that are bold on the import layout screen are required.
Field
Required
Max.
Length
Description
Location ID
Yes
15
Location Type
No
The type for the location, such as SIT or DPT. 1
Latitude
No
15
The latitude of the location.
Longitude
No
15
The longitude of the location.
Arrival Date
No
Date
Date the driver arrived at the location.^
Route ID
Yes
15
Identifier for the locations route. All route IDs

must be uppercase. 1
Arrival Time
No
Time
Time of day the driver arrived at the location

(military time, such as 09:00, 13:00).^
Departure
Date
No
Date
Date the driver departed from the location.^
Departure
Time
No
Time
Time of day the driver departed the location

(military time, such as 0:900, 13:00).^
Distance
No
Distance traveled from the previous stop to reach

the location.
Odometer
Reading
No
15
The odometer reading at the stop.
Size 1,2,3
No
16 (9.6)
each
Quantity delivered to the location (onboard

systems use only one measurement although
Roadnet allows several). The number of digits to
the right of the decimal is established in the
Transportation Suite prior to import.
Stop Number
Yes
Identifier for the stop sequence on the route.
Operations Guide
405
Import Layouts
Field
Required
Max.
Length
Description
Location ID
Yes
15
Comment
Codes
No
The actual vs. planned comment code explaining

why the planned does not equal the actual.
Driver ID
No
15
Unique identifier for the driver. 1
*All fields are string (text) fields unless the data calls for a specific format (such as date, time).
^You must specify the mask indicating how the data is formatted. If no mask is specified, the Roadnet
are:
1
Send Orders Export File Available Fields

Used with: Roadnet
The fields that can be included in the send orders file are listed in the following table.
These fields deal with routing information, and are appended to the original orders file
that was imported.
Field
Maximum
Length
Description
Route ID
15
The unique ID assigned to the route. All route IDs must be

uppercase.
Stop Number
The sequence number of the stop on the route.
Stop Type
The type of stop, such as a normal stop, break, wait, or

layover.
Stop Arrival Time
Time
The time the driver is scheduled to arrive at the stop.

Formatted using the 24 hour clock.^
Stop Arrival Date
Date
The date the driver is scheduled to arrive the stop.^
Stop Departure
Time
Time
The time the driver is scheduled to leave the stop. Formatted

using the 24 hour clock.^
Stop Departure
Date
Date
The date the driver is scheduled to leave the stop.^
Route Name
30
The description given to the route.
Route Start Date
Date
The date the route is scheduled to start.^
Route Start Time
Time
The time the route is scheduled to start. ^
406

Import Layouts
Field
Maximum
Length
Description
Route Complete
Time
Time
The time the is route is scheduled to end. ^
Driver 1, 2 ID
15 each
The drivers unique identifier.
Equipment 1, 2 ID
20 each
The unique identifier for the equipment assigned to the route.
Equipment 1, 2
Type
15 each
The equipment type for the equipment assigned to the route.
Equipment 1, 2
Owner ID
9 each
The ID of the region that owns the equipment assigned to the

route.
Equipment 1, 2
Description
255 each
The description of the equipment assigned to the route.
Depot ID
15
The unique identifier for the routes origin.
Depot Type
The type for the routes origin.
Previous Distance
10
The distance from the previous stop in tenths of miles.
Previous Travel
Time
Time
The travel time from the previous stop in tenths of minutes.
Stop Service Time
Time
The total service time for the stop in tenths of minutes.
Total Distance
10
The routes total distance in tenths of miles.
Total Travel Time
Time
The total travel time for the route, formatted in tenths of

minutes.
Total Service Time
Time
The total service time for the route, formatted in tenths of

minutes.
Open/Close Times
Time
The open and close time for the stop; formatted using 24
hour clock, times are run together (08001700). ^
Load Route
Priority
The routes load priority.
Time Windows
Time
The locations time windows; formatted using 24-hour

clock, times are run together (0900110013001600). ^
Session Date
Date
The planned delivery date for the route.^
Upload Selector
The selector associated with the order, such as P for pickup.
User Field 1,2,3
20 each
The contents of the locations user-defined fields.
Description
60
The description or name of the location.
Address Line 1
50
The street address of the location.
Address Line 2
20
The remainder of the street address, such as a suite or

apartment number.
City
30
The city for the location.
Operations Guide
407
Import Layouts
Field
Maximum
Length
Description
State
10
The state or province for the location.
Latitude
The latitude of the stops location.
Longitude
10
The longitude of the stops location.
Geocode Quality
80
A phrase indicating the how the location was geocoded.
Zip Code
10
Phone Number
10
The phone number for the location. Do not include dashes or

parentheses.
Driver 1, 2 First
Name
35 each
The first name of the driver(s) assigned to the route.
Driver 1, 2 Middle
Name
35 each
The middle name of the driver(s) assigned to the route.
Driver 1, 2 Last
Name
35 each
The last name of the driver(s) assigned to the route.
Trip Number
10
Individual segments on a route separated by a depot. If the

route is a reload that is being viewed as a single route, or a
depot was inserted on the route, the number will be 2 or
greater. Most routes will have 1 trip.
Fixed Service Time
Time
The amount of time that was needed at the stop without

delivering any product, such as to get paperwork signed.
When exported, the decimal is removed from the time; you
will need to multiply by 0.1 to reflect the actual service time.
For example, a service time of five minutes reads as 0:05.0
in Roadnet. After you export this value, this five-minute
service time will appear as 50. A service time of four-tenths
of a minute, or 0:00.4, will appear in the export as 4.
Variable Service
Time
Time
The amount of time needed to deliver one unit at the stop.

The size alias selected as the Unit of Service is used to
determine the variable service time. Before exporting, you
choose the portions of minutes the variable service time
represents. When exported, the decimal is removed from the
time; you will need to multiply by the appropriate number to
reflect the actual service time.
For example, a service time of five minutes reads as 0:05.0
in Roadnet. After you export this value, this five-minute
service time will appear as 50. A service time of four-tenths
of a minute, or 0:00.4, will appear in the export as 4.
Route Departure
Time
Time
The time the driver left the routes origin. ^
Route Arrival Time
Time
The time the driver arrived at the routes destination.^
408

Import Layouts
Field
Maximum
Length
Description
Internal ID
10
A unique identifier indicating the stops sequence number on

the route. This information can be used if you are importing
the routes and stops into MobileCast.
Current Size 1, 2, 3
16 each (9.6)
The orders current quantity when measured as Size 1, 2, or

3. The orders quantity may have changed from the original
if you split orders or if the quantities increase daily in
Roadnet because you are using weekly routing. To have this
information replace the imported quantities, simply match
the Start Position and Length to the value entered for the
import daily orders layout.
Current Urgency
The orders current urgency. The orders urgency may have

changed from the original if the urgency increase daily in
Roadnet because you are using weekly routing. To have this
information replace the imported urgency, simply match the
Start Position and Length to the value entered for the import
daily orders layout.
Building Delivery
Sequence
A number indicating the sequence the location should be

delivered in relation to other locations on the same route
with the same latitude and longitude.
Standard Stop
Number
80
The sequence number of a stop on a standard route, which

will remain the same regardless of where it appears on that
route.
Note: The standard stop number that is exported is the
number on the most recently saved standard route.
are:
Export Routes File Available Fields

Used with: Roadnet
The fields that can be included in file when you choose Export Routes from the Tools
menu in the Routing Editor, or Export when you right-click on a route, are outlined in the
table below, along with a description.
Field
Maximum
Length
Description
Session Date
Date
The session date. ^
Operations Guide
409
Import Layouts
Field
Maximum
Length
Description
Route ID
15
The routes ID. All route IDs must be uppercase.
Route Description
30
The description or name of the route.
Route Start Date
Date
The date the route is scheduled to start.^
Route Start Time
Time
The time the route is scheduled to start.^
Depot ID
15
The unique identifier of the depot the route starts at.
Depot Type
The type for the location the route starts at. Normally, this
would be DPT.
Stop Number
The sequence number of the stop on the route. Only stops

will have a stop number; the Internal ID is used to include
breaks, waits, layovers, and mid-route depots in the route.
Stop Locations
15
The location ID for the stop.
Location Type
The location type ID, such as SIT. The type must exist in the
Roadnet Transportation Suite. If no type is specified, the
default type is used.
Location
Description
60
The name of the location.
Address Line 1
50
The street address for the stop.
Address Line 2
20
The remaining street address that did not fit on the first line,
such as a suite number.
City
30
The town the stop is in.
Phone Number
10
The phone number for the stop. Do not include dashes or

parentheses.
Zip Code
10
State
20
The state or province the town is in.
Latitude
The latitude of the stop. The format of the latitude is selected

on the Export Routes window.
Longitude
10
The longitude for the stop. The format of the longitude is

selected on the Export Routes window.
Open Close Time
Time
The earliest and latest time the location can accept a delivery.
All times use a 24 hour clock.^
Time Windows
Time
The starting and ending time of the period(s) the location

would prefer to receive deliveries. There are can be up to two
time window periods. All times use a 24-hour clock.^
Travel Time
10
Amount of time needed to travel from the previous stop to

this stop.
Distance
10
Distance from the previous stop to this stop.
410

Import Layouts
Field
Maximum
Length
Description
Arrival Date
Date
The date the route is scheduled to arrive at the stop.^
Arrival Time
Time
The planned arrival time at the stop; formatted using a 24hour clock. If exporting seconds, use SS as the mask.
Service Time
Time
Amount of time needed to service the stop.
Size 1, 2, 3
16 (9.6) each
The delivery quantity for each size.
Driver 1,2 ID
15 each
The unique identifier of the driver(s) assigned to the route.
Previous Location
15
The location ID for the previous stop.
Driver 1,2 First

Name
35 each
The first name of the driver(s) assigned to the route.
Driver 1,2 Middle

Name
35 each
The middle name of the driver(s) assigned to the route.
Driver 1,2 Last

Name
35 each
The last name of the driver(s) assigned to the route.
Route Equipment
ID
20
The unique identifier of the equipment assigned to the route.
Route Equipment
Type
15
The type of equipment assigned to the route.
Route Equipment
Owner ID
The region that owns the equipment.
Trip Number
10
Individual segments on a route separated by a depot. If the

route is a reload that is being viewed as a single route, or a
depot was inserted on the route, the number will be 2 or
greater. Most routes will have 1 trip.
Fixed Service Time
The amount of time that was needed at the stop without

delivering any product, such as to get paperwork signed.
When exported, the decimal is removed from the time; you
will need to multiply by 0.1 to reflect the actual service time.
Variable Service
Time
11
The amount of time needed to deliver one unit at the stop.

The size alias selected as the Unit of Service is used to
determine the variable service time. Before exporting, you
choose the portions of minutes the variable service time
represents. When exported, the decimal is removed from the
time; you will need to multiply by the appropriate number to
reflect the actual service time.
Pre-Route Time
The amount of time between when the driver clocks in and

leaving the depot, in minutes.
Stop Type
The type of stop, such as a normal stop, break, wait, or

layover.
Operations Guide
411
Import Layouts
Field
Maximum
Length
Description
Post-Route Time
The amount of time between when the driver arrives at the

destination and clocks out.
Route Departure
Time
Time
The time the driver leaves the routes origin.^
Route Arrival Time
Time
The time the driver arrives at the routes destination.^
Route Complete
Time
Time
The time the route is completed. ^
Internal ID
10
A unique identifier indicating the stops sequence number on

the route. All items exported, including breaks, waits,
layovers, and mid-route depots will have an internal ID.
Building Delivery
Sequence
A number indicating the sequence the location should be

delivered in relation to other locations on the same route
with the same latitude and longitude.
are:
User Upload File Available Fields

User upload allows you to export the routes you created in the Planning Editor to a
network, mainframe, or wherever you specify. The table below lists the fields that you can
include in the User Upload file. In addition to these fields, any fields that are specified in
the Location or Location Extension layout are included in the file, in the positions
specified in those layouts.
Field
Maximum
Length
Description
Open
Time
The earliest time the stop can be delivered.
Close
Time
The latest time the stop can be delivered.
TW1 Start/Stop
Time
The beginning and ending times for the stops first time
window.^
TW2 Start/Stop
Time
The beginning and ending times for the stops second time
window.^
412

Import Layouts
Field
Maximum
Length
Description
TW Factor
A number indicating the importance of meeting the

locations time windows. 1=least importance, 5=most
important
No Helper Fixed
The amount of time needed at the stop without delivering

anything, without a helper.
No Helper Variable
11
The amount of time needed at the stop to deliver one unit,

without a helper.
Helper Fixed
The amount of time needed at the stop without delivering

anything, with a helper.
Helper Variable
11
The amount of time needed at the stop to deliver one unit,

with a helper.
Geo Status
80
The method used to geocode the location.
Session
Description
255
The description used to identify the planning session.
Stop Number
Day
A number indicating the stops delivery day. Monday=1,

Tuesday=2, etc.
Arrival Time
Time
The time the driver arrives at the stop.^
Travel Time
Time
The amount of time needed to get from the previous stop to

this stop.
Distance
The distance from the previous stop to this stop.
Service Time
Time
The total amount of time needed to service the stop. This

includes the fixed and variable time.
Stop Size 1, 2, 3
16 (9.6) each
The amount delivered based on each of the size aliases.
Origin ID
15
The unique identifier for the routes origin.
Origin Type
The type for the routes origin. Normally, this will be DPT.
Equipment ID
20
The unique identifier for the equipment assigned to the route.
Equipment Type
15
The ID for the type of equipment assigned to the route.
Driver ID
15
The unique identifier for the driver assigned to the route.
Helper
Indicates whether or not a helper has been assigned to the

route.
Route ID
15
The unique identifier for the route. All route IDs must be
uppercase.
are:
Operations Guide
413
Import Layouts

Exporting Loaded Routes Available Fields

The fields that can be included in a file when you choose Export All Routes from the
Tools menu in the Loading Editor, or Export Selected Route(s) when you right-click on a
route, are outlined in the table below.
Field
Maximum
Length
Description
Session Date
Date
The date of the routing session.
Route ID
15
The routes ID. All route IDs must be uppercase.
Route Start Time
Time
The time the route is scheduled to begin. If the start time is

not defined, the default start time is used.
Route Start Date
Date
The date the route is scheduled to begin. If a start date is not

specified, the session date is used.
Load Status
15
The status of the route in FleetLoader, such as whether it is

Edited or Locked.
Driver1 ID
15
The unique identifier for the first driver assigned to the route.
Driver1 First Name
35
The last name of the first driver assigned to the route.
Driver1 Middle
Name
35
The middle name of the first driver assigned to the route.
Driver1 Last Name
35
The first name of the first driver assigned to the route.
Driver2 ID
15
The unique identifier of the second driver assigned to the

route.
Driver2 First Name
35
The first name of the second driver assigned to the route.
Driver2 Middle
Name
35
The middle name of the second driver assigned to the route.
Driver2 Last Name
35
The last name of the second driver assigned to the route.
Route Equipment
ID
20
The unique identifier for the equipment assigned to a route.
Route Equipment
Type
15
The type of equipment assigned to the route.
Route Equipment
Owner
The ID of the region that owns the equipment assigned to the

route.
Stop Location ID
15
Unique identifier for the location.
414

Import Layouts
Field
Maximum
Length
Description
Stop Location
Type
The stop location type such as SIT. If no type is specified, the

default type is used.
Stop Number
Order Number
15
Unique identifier for each order.
Order Selector
A selector associated with the order.
Bay Number
15
The bay that the SKU should be loaded on.
Layer
10
If using pallets, the layer the SKU is loaded on.
SKU
32
The unique identifier for the SKU.
SKU Description
128
The description of the SKU.
SKU Layer
Quantity
16
The total quantity of the SKU in this layer for this order only.
Pallet Bay Quantity
16
The total quantity of the SKU for the entire pallet/bay.
SKU Layer Weight
15
The weight of the SKU in this layer for this order only.
Pallet Bay Weight
15
The total weight of the SKU for the entire pallet/bay.
Package Type
15
The ID for the package type. This field must be completed.
Warehouse Zone
ID
15
The portion of the warehouse where the SKU is located.
Pallet Type ID
The type of pallet the product is being loaded on.
are:
Import Route Available Fields

If you are importing your daily routes into MobileCast, you will need to import
information into the Import Route table. The table below lists the fields that can be
imported, along with the maximum length and a brief description of each field.
Field
Required
Max.
Length
Description
Common
Carrier ID
No
15
The ID of the common carrier transporting the

route. 1
Operations Guide
415
Import Layouts
Field
Required
Max.
Length
Description
Description
No
255
A description of the route, such as the area it covers.
Destination ID
NO
15
The unique identification of the place the route

ends, such as the depots ID. 1
Destination
Type
No
The type of location where the route ends, such as

DPT for depot. 1
Dispatch ID
No
The unique identifier of the dispatcher who will be

tracking the route. 1
Group
No
64
The group the route belongs to (if the routes are

grouped together).
Last Stop is
Destination
No
A Y or N indicating whether the last stop on the

route is the end of the route or not. The default is N.
Origin ID
Yes
15
The unique identification of the place the route

starts, such as the depots ID. 1
Origin Type
Yes
The type of location where the route starts, such as

DPT for depot. 1
Planned Start
Yes
Date/
Time
The date and time the route is expected to start; the

time the driver clocks in. If date is not supplied, if
will default to the route date. If date is supplied,
time must also be supplied. Must always be
specified.
Planned
Departure
Yes
Date/
Time
The date and time when the route is expected to

leave the origin. If date is not supplied, if will
default to the planned start date. If date is supplied,
time must also be supplied.
Planned
Distance
Yes*
11 digits
(9.2 )
The total amount of distance the route is expected

to cover.
Planned
Arrival
Yes*
Date/
Time
The date and time when the route is expected to

reach the destination. If date is not supplied, if will
default to the planned departure date. If date is
supplied, time must also be supplied.
Planned
Complete
Yes*
Date/
Time
The date and time the route is expected to be

finished; the time the driver clocks out. If date is not
supplied, if will default to the planned arrival date.
If date is supplied, time must also be supplied.
Reference
Number
No
15
The DTR number for the route. The name of this

field can be changed in MobileCast.
Route Date
Yes
Date
The date the route will occur.
Route ID
Yes
15
The unique ID of the route. All route IDs must be

uppercase. 1
416

Import Layouts
Field
Required
Max.
Length
Description
Route Type
No
The type of product the route carries, such as

flammable (FLM). 1
Scenario
No
15
The scenario the route belongs to (if scenarios are

used.) The default is Delivery. 1
Seal
No
32
The unique numbers of the seals (if the contents are

sealed). You can have up to three seals per route.
User Defined
Fields 1, 2, and
3
No
20 each
User-defined fields contain information to be

tracked that is not contained elsewhere in the file.
Pre-Route
Survey
No
The unique identifier for the survey.
Post-Route
Survey
No
Helper
No
Indicates whether or not a helper has been assigned

to the route.
* Field not required if MobileCast is calculating the route. If this information is provided, it will be
overwritten with the results of the route calculation.
1
Stop Available Fields

If you are importing daily routes into MobileCast, you will need to import stop
information for the routes. The table below lists the fields that can be imported, the
maximum length and a description for each.
Field
Required
Max.
Length
Description
Additional
Service Time
No
Time (in
seconds)
Any additional time a driver may need to deliver a

stop.
Close Time
No
Date
The latest possible time the driver can deliver the

stop.
Instructions
No
255
Any instructions associated with the stop. If

wireless communication is used, the instructions
will appear to the driver on the wireless device.
Location ID
Yes
15
The unique identification of the location. 1
Location Type
Yes
The type of location, such as DPT for depot or SIT

for site. 1
Operations Guide
417
Import Layouts
Field
Required
Max.
Length
Description
Open Time
No
Date
The earliest possible time the driver can deliver the

stop.
Planned
Arrival
No
Date/
Time
The date and time the driver should arrive at the

stop.
Planned
Departure
No
Date/
Time
The date and time the driver should leave the stop.
Planned
Distance
No
11 (8.2 )
each
The distance between the previous stop and the

current stop.
Planned
Pickup Size 1,
2, and 3
No
16 (9.6)
each
If a product is being picked up at the stop, the

amount planned for pick up as size 1, size 2, and
size 3. The number of digits to the right of the
decimal is established in MobileCast before the
import.
Planned Size
1, 2, and 3
No
16 (9.6)
each
If a product is being delivered to the stop, the

amount planned for delivery as size 1, size 2, and
size 3. The number of digits to the right of the
import.
Route Date
No
Date
The date of the route the stop is on.
Route ID
No
15
The unique ID of the route. All route IDs must be

uppercase. 1
Sequence #
Yes
The stop number for the route.
Time Window
1, 2 Open/
Close
No
Date
The starting and ending times for the preferred

delivery times at the stop.
Type
No
The type of stop, such as 0 for stop, 1 for a paid

break, 2 for an unpaid break, 3 for a paid wait, 4 for
an unpaid wait, 5 for a paid layover, 6 for an unpaid
layover, and 7 for a mid-route depot. 1
User Defined
Fields 1, 2, and
3
No
20 each
User-defined fields contain information to be

tracked that is not contained elsewhere in the file.
Stop Survey
Code
No
Notes: When importing the open time, close time, and time window information, you can
include both the date and time in the file, or just the time. If only the time is
imported, the stops planned arrival date will be used as the time windows date.
All date and time fields can be entered in several ways. For instance, MobileCast
can accept dates as MM/DD/YYYY, DD/MM/YYYY, or MM-DD-YYYY and
418

Import Layouts
times as HH:MI or HH:MI:SS. One requirement is that the year must be a fourdigit number and you must specify the format being used. If you are importing
only the time for the open/close times and time windows, the mask can only
specify time information, not date information.
To import a stop as unassigned, the Route ID must either be UNASSIGN or left
blank.
Product Order Table Available Fields
If you are importing daily routes into MobileCast, and are tracking your routes at the order
level, you will need to import Product Order information. The available fields, the
maximum length and a brief description, are listed in the table below.
Field
Required
Max.
Length
Description
Sequence
Number
Yes
The unique stop number where the order is being

delivered.
Order Number
Yes
15
The unique ID for the order. 1
Planned
Pickup Sizes
1, 2, and 3
No
16 (9.6)
each
The pickup quantity measured as that size. The

number of digits to the right of the decimal is
established in MobileCast before the import.
Planned Sizes
1, 2, and 3
No
16 (9.6)
each
The delivery quantity measured as that size. The

number of digits to the right of the decimal is
Reference
Number
No
32
The unique reference for the order.
Route Date
No
Date
The date of the route.
Route ID
No
15
The unique ID for the route. All route IDs must be

uppercase. 1
Special
Instructions
No
255
User Defined
Fields 1, 2, and
3
No
20 each
User-defined fields contain information not found

elsewhere in the file.
Note: All date fields can be entered in several ways. For instance, MobileCast can accept
dates as MM/DD/YYYY, DD/MM/YYYY, or MM-DD-YYYY. The only
Operations Guide
419
Import Layouts
requirement is that the year must be a four-digit number and you must specify the
format being used.
To import an order as unassigned, the Route ID must either be UNASSIGN or left
blank.
Line Item Table Available Fields
If you are importing daily routes into MobileCast and are tracking line item information,
you will need to import line items with your routes. The table below lists the available
fields, maximum length, and a brief description of each field.
Field
Required
Max.
Length
Description
Description
No
128
The name or other description of the item.
Line Item ID
Yes
32
The unique ID of the item on the order.
Order Number
Yes
15
The unique ID for the order. 1
Planned
Pickup Sizes
1, 2, and 3
No
16 (9.6)
each
The planned pickup quantity measured as that size.

The number of digits to the right of the decimal is
Planned Sizes
1, 2, and 3
No
16 (9.6)
each
The planned delivery quantity measured as that

size. The number of digits to the right of the
import.
Route Date
No
Date
Route ID
No
15

uppercase. 1
Stop Sequence
Number
Yes
The number for the stop the order is delivered to.
User Defined
Fields 1, 2, and
3
No
20 each
User-defined fields contain information not found

elsewhere in the file.
format being used.
To import a line item as unassigned, the Route ID must either be UNASSIGN or
left blank.
420

Import Layouts
Route Driver Table Available Fields

If you are importing daily routes into MobileCast you can include the driver information
for the routes by importing it into the Route Driver table. The available fields in the Route
Driver table, along with the maximum length and a brief description of each, are included
in the table below.
Field
Required
Max.
Length
Description
Driver ID
Yes
15
The drivers unique ID. Normally this is the

drivers social security number. 1
Route Date
Yes
Date
Route ID
Yes
15

uppercase. 1
Sequence
Number
Yes
The number 1 or 2 which refers to driver 1 or 2 on

the route. The default is 1.
Owner ID
No
ID of the region that owns the driver. 1
1You
format being used.
Order Container Assignments Table Available Fields
If you are importing daily routes into MobileCast, and are tracking orders using
containers, you will need to import order container assignment information. The available
fields, the maximum length and a brief description of each, are listed in the table below.
Field
Required
Max.
Length
Description
Barcode
Yes
32
The barcode of the container.
Container ID
Yes
32
The unique identifier for the container. 1
Drop off
Yes
A T or F indicating whether the container is

supposed to be dropped off at the stop.
Sequence
Number
Yes
The number for the stop the container is delivered

to.
Order Number
Yes
15
The order number the container is being associated

with. 1
Operations Guide
421
Import Layouts
Field
Required
Max.
Length
Description
Service Type
Yes
A single character indicating whether the stop is a

drop off (0) or pickup (1). The default is 0 (drop
off).
Route Date
Yes
Date
Route ID
Yes
15

uppercase. 1
Container
Type
No
The type of container. 1
format being used
All unassigneds must have the Route ID of either UNASSIGN or left blank.
Line Item Container Assignments Table Available Fields
If you are importing daily routes into MobileCast, and tracking line items with containers,
you will need to import the line item container assignments for the routes. The available
fields, maximum length, and a brief description of each field are listed in the table below.
Field
Required
Max.
Length
Description
Route Date
Yes
Date
Route ID
Yes
15

uppercase. 1
Container ID
Yes
32
Sequence
Number
Yes
The number for the stop the line item is delivered

to.
Line Item ID
Yes
32
The unique identifier for the line item.
Order Number
Yes
15
The order number the line item is being associated

with. 1
Planned
Pickup Size 1
No
22 (15.6)
The quantity being picked up, measured as size 1.
Planned Size 1
No
22 (15.6)
The quantity being delivered, measured as size 1.
422

Import Layouts
format used.
All Unassigneds must have the Route ID as either UNASSIGN or left blank.
Order Financial Details Table Available Fields
If you are importing daily routes into MobileCast, and are tracking orders and their
financial information, then you will need to import order financial detail information. The
available fields, the maximum length and a brief description of each, are listed in the table
below.
Field
Required
Max.
Length
Description
Order Number
Yes
15
The order number the financial detail is being

associated with. 1
Route Date
Yes
Date
Route ID
Yes
15

uppercase. 1
Sequence
Number
Yes
Code
Yes
The financial code associated with the orders

financial detail. 1
Detail Amount
Yes
16
The amount, in dollars and cents, associated with

the financial information. If negative, then a
negative sign before the number is required.
Detail ID
No
32
The identification number associated with the

financial detail. For example, if the financial detail
is a charge, and the customer paid using a credit
card, then enter the credit card number.
Detail Date
No
Date
The date associated with the financial detail. 1
Detail
Description
No
32
The description of the financial detail.
format being used
All unassigneds must have the Route ID of either UNASSIGN or left blank.
Operations Guide
423
Import Layouts
Order Activities Table Available Fields

If you are importing daily routes into MobileCast, and are using activities with your
orders, then you can import the activities with the routes. The available fields, the
maximum length and a brief description of each, are listed in the table below.
Field
Required
Max.
Length
Description
Route Date
Yes
Date
Route ID
Yes
15

uppercase. 1
Sequence
Number
Yes
Order Number
Yes
15
The order number the financial detail is being

associated with. 1
Activity ID
Yes
32
The unique identifier for the activity. 1
Route Equipment Table Available Fields

If you are importing daily routes into MobileCast, you can include the equipment assigned
to each route by importing into the Route Equipment table. The available fields,
maximum length, and a brief description, are listed in the table below.
Field
Max.
Length
Description
Ending Sequence
Number
The stop number where the equipment leaves the

route.
Equipment ID
20
The unique ID for the piece of equipment. 1
Equipment Type
The type of equipment. Equipment types must be

established in MobileCast before the import. 1
Owner ID
ID of the region that owns the equipment.1
Route Date
Date
Route ID
15
The unique ID of the route. 1
Starting Sequence
Number
The stop number where the equipment joins the

route.
424

Import Layouts
requirement is that the year must be a four-digit number. Specify the format being
used to enter these fields in the Import module of MobileCast.
Employee Available Fields
The table below lists the fields that you can import for employees, the maximum length,
and a brief description.
Field
Required
Max.
Length
Description
Employee ID
Yes
15
The employees unique identification. This is

usually the social security number. 1
Employee
Type
Yes
The employees type, such as DRV for Driver. 1
First Name
No
35
The employees first name, as it should appear on

payroll reports; not a nickname.
Middle Name
No
35
The employees middle name.
Last Name
No
35
The employees last name.
Status
No
The employees status, such as RDY for available.1
Active
No
A Y or N indicating if the employee is available to

be assigned to a route.
Address Line 1
No
50
The employees home address; use the street

address, such as 849 Fairmount Ave.
Address Line 2
No
20
Any portion of the employees home address that

did not fit on the first line, such as an apartment or
suite number.
Country
No
The three letter abbreviation for the country where

the employee lives, such as USA.
Zip Code
No
15
Work Phone
Number
No
20
The phone number the employee can be contacted

at while at work; include the area code. Do not
include dashes or parentheses.
Home Phone
Number
No
20
The phone number the employee can be contacted

at while not at work; include area code. Do not
include dashes or parentheses.
Date of Birth
No
Date
The employees date of birth.^
Start Date
No
Date
The date the employee started employment.^
Operations Guide
425
Import Layouts
Field
Required
Max.
Length
Description
Termination
Date
No
Date
The employees final date of employment.^
ADP File
Number
No
10
If you use ADP to process payroll, the employees

unique ADP number. See your ADP software for
more information.
City
No
30
The city where the employee lives.
County
No
30
The county where the employee lives.
State
No
20
The state where the employee lives.
Skill Set ID
No
15
The unique ID of the skill set containing the

activities the employee can complete. 1
Password
No
The employees password to log into the

MobileCast mobile application.
are:
1
Driver Available Fields

The fields that can be imported for drivers, along with the maximum length and a brief
description are listed in the table below.
Field
Required
Max.
Length
Description
Driver ID
Yes
15
The drivers unique identification. This must match

the drivers employee ID. 1
Driver Type
No
The type of driver, such as TRN for trainee. 1
Preferred
Depot
Location ID
No
15
The unique identifier of the depot the driver works

out of. 1
Preferred
Depot
Location Type
No
The type for the depot; normally this would be

DPT. 1
426

Import Layouts
Field
Required
Max.
Length
Description
Preferred
Equipment
Owner ID
No
The region that owns the drivers preferred

equipment. 1
Preferred
Equipment ID
No
20
The unique identifier of the equipment the driver

uses. The equipment can automatically be assigned
to the drivers route in the Routing Editor. 1
Preferred
Equipment
Type
No
The type of equipment the driver uses. 1
Preferred
Route ID
No
15
The ID used for the route the driver is assigned to.

The ID can automatically be assigned to the
drivers route in the Routing Editor. 1
Non-Help
Regular Rate
No
11
The amount the driver is paid per minute, if paid per

hour. Enter as DOLLARS.CENTS.
Helper
Regular Rate
No
11
The amount the driver and helper are paid per

minute, if they are paid by the hour. Enter as
DOLLARS.CENTS. These costs are for both the
driver and the helper.
Non-Help
Overtime Rate
No
11
The amount the driver is paid per minute when on

overtime, if paid per hour. Enter as
DOLLARS.CENTS.
Helper
Overtime Rate
No
11
The amount the driver and helper are paid per

minute when on overtime, if they are paid by the
hour. Enter as DOLLARS.CENTS. These costs are
for both the driver and the helper.
Non-Help
Minimum
Time
No
11
The minimum amount of time the driver is

guaranteed to be paid for, if paid by the hour. Enter
in seconds.
Helper
Minimum
Time
No
11
The minimum amount of time the driver and helper

are guaranteed to be paid for, if they paid by the
hour. Enter the time in seconds.
Non-Help
Overtime
Begin
No
11
The amount of time into the route when the

overtime pay rate starts, if the driver is paid per
hour. Enter the time in seconds.
Helper
Overtime
Begin
No
11
The amount of time into the route when the

overtime pay rate starts, if they are paid per hour.
Enter the time in seconds.
Non-Help Per
Stop Rate
No
11
The amount the driver is for each stop, if paid per

stop. Enter as DOLLARS.CENTS.
Operations Guide
427
Import Layouts
Field
Required
Max.
Length
Description
Helper per
Stop Rate
No
11
The amount the driver and helper are paid per stop,
if they are paid by the stop. Enter as
DOLLARS.CENTS. These costs are for both the
driver and the helper.
Non-Help
Minimum
Stops
No
11
The minimum number of stops the driver is

guaranteed to be paid for, if paid by the stop.
Helper
Minimum
Stops
No
11
The minimum number of stops the driver and

helper are guaranteed to be paid for, if they are paid
per stop.
Non-Help Per
Distance Rate
No
11
The amount the driver is paid per mile/kilometer

driver, if paid by distance. Enter as
DOLLARS.CENTS.
Helper Per
Distance Rate
No
11
The cost for the driver and helper for each mile/
kilometer on the route, if they are paid by distance.
Enter as DOLLARS.CENTS. These costs are for
both the driver and the helper.
Non-Help
Minimum
Distance
No
11
The minimum distance the driver is guaranteed to

be paid for, if paid by distance.
Helper
Minimum
Distance
No
11
The minimum distance the driver and helper are

guaranteed to be paid for, if they are paid by
distance.
Non-Help Per
Piece Rate
No
The amount the driver is paid per piece delivered, if

paid by piece. Enter as DOLLARS.CENTS.
Helper per
Piece Rate
No
The amount the driver and helper are paid for each
piece delivered/picked up, if they are paid by the
piece. Enter as DOLLARS.CENTS. These costs are
for both the driver and the helper.
Non-Help
Minimum
Pieces
No
11
The minimum number of pieces the driver is

guaranteed to be paid for, if paid by the quantity
delivered/picked up.
Helper
Minimum
Pieces
No
11
The minimum number of pieces the driver and

helper are guaranteed to be paid for, if they are paid
on a per piece rate.
Non-Help
Fixed Route
Cost
No
12
Any fixed driver costs which are applied to every

route the driver is assigned to and are not directly
associated with the route, such as flat rate payment.
Enter as DOLLARS.CENTS.
428

Import Layouts
Field
Required
Max.
Length
Description
Helper Fixed
Route Cost
No
12
Any driver and helper costs which are applied to

every route the driver and helper are assigned to and
are not directly associated with the route, such as
flat rate payment. Enter as DOLLARS.CENTS.
These costs are for both the driver and the helper.
License
Number
No
30
The drivers license number.
Date of
License
Expiration
No
Date
The date the drivers license expires. If a driver

with an expired license is assigned to a route, a
warning appears in MobileCast.^
Date of Last
Physical
No
Date
The date of the drivers last physical.^
Date of Last
Drug Test
No
Date
The date of the drivers last drug test.^
Wireless ID
No
24
If the driver is assigned a wireless device, the

unique identification of the device. 1
Wireless
Provider
No
The number indicating the wireless provider being

used. Enter a 0 for none or 1 for Qualcomm.
Driver
Directions
No
Indicates whether of not to download driver

directions onto the mobile device when the route is
loaded. Enter a Y to download directions, an N to
prevent directions from being downloaded. If left
blank, directions are not downloaded.
are:
1
Container Available Fields

If you are using containers with MobileCast you can import them. The available fields,
maximum length and a brief description are listed in the table below.
Field
Required
Max.
Length
Description
Container ID
Yes
32
Operations Guide
429
Import Layouts
Field
Required
Max.
Length
Description
Last Dropped
at Location ID
Yes
15
The unique identifier for the location where the

container is currently located. 1
Last Dropped
at Location
Type
Yes
The type of location where the container is

currently located. 1
Type Code
No
The type of the container. 1
1You
Equipment Available Fields

You can import information about your equipment, rather than entering it manually. The
available fields, the maximum length and a brief description of each are listed in the table
below.
Field
Required
Max.
Length
Description
Equipment ID
Yes
20
The unique identifier for the equipment. 1
Equipment
Type
Yes
15
The type of equipment, such as TRC for tractor or

TRL for trailer. 1
Description
No
255
A description of the equipment.
Status
No
The equipments status, such as RDY for ready/

available. 1
Location ID
No
15
The unique identification of the location where the

equipment currently is. 1
Note: If you use MobileCast Dispatcher, it is
recommended that you set up a Location ID and
Location Type to import equipment.
Location Type
No
The type of location where the equipment is, such

as DPT for depot. 1
Note: If you use MobileCast Dispatcher, it is
recommended that you set up a Location ID and
Location Type to import equipment.
Preferred
Driver Owner
ID
No
The region that the preferred driver is assigned to. 1
Preferred
Driver
No
15
The unique ID of the driver for the equipment. 1
430

Import Layouts
Field
Required
Max.
Length
Description
Date of
Inspection
No
Date
The date of the equipments most recent

inspection.^
GPS Unit ID
No
32
If the equipment is assigned an external GPS

device, the unique identification for the device.
Onboard
Computer
No
A Y or N indicating if an onboard computer is

associated with the equipment.
Wireless ID
No
24
If the equipment is assigned a wireless device, the

unique identification for the device. 1
Wireless
Provider
No
The two digits for the appropriate wireless

provider. Enter a 0 for none or a 1 for Qualcomm.
Date Dropped
Off
No
Date
The date the equipment was dropped at the location

where it is currently.^
Buddy
Equipment ID
No
20
The ID of the buddy equipment, such as a trailer.

Buddy equipment can automatically be assigned to
a route with the equipment in the Routing Editor. 1
Buddy
Equipment
Type ID
No
15
The type ID for the buddy equipment. Buddy

equipment can automatically be assigned to a route
with the equipment in the Routing Editor. 1
Buddy
Equipment
Owner ID
No
The region that the buddy equipment is assigned to.

1
are:
1
Package Type Available Fields

You can import information about your package types, rather than entering it manually.
The available fields, the maximum length, and a brief description of each field are listed
in the table below.
Field
Required
Max.
Length
Description
Package Type
ID
Yes
15
The unique identifier for the package type. This

field must be completed. 1
Operations Guide
431
Import Layouts
Field
Required
Max.
Length
Description
Description
No
30
A description of the package type.
Bitmap
No
255
The path and file name of the bitmap that will be

used to represent the package type in the Loading
Editor. The image must be a .bmp file that is 28x28
pixels and 256 colors or less.
Height
No
15
The height of the package type.
Width
No
15
The width of the package type.
Depth
No
15
The depth of the package type.
Weight
No
15
The weight of the package type.
Equivalency
No
15
The equivalency factor the package type quantity is

multiplied by to even out the package type sizes,
service times, etc.
SKU Available Fields

You can import information about your SKUs, rather than entering it manually. The
available fields, the maximum length, and a brief description of each field are listed in the
table below.
Field
Required
Max.
Length
Description
SKU
Yes
32
The unique identifier for the SKU. 1
Package Type
ID
Yes
15
The ID for the package type. This field must be

completed. 1
Brand ID
Yes
15
The ID of the SKU brand. This field must be

completed. 1
Description
No
128
A description of the SKU.
Bitmap
No
255
The path and file name of the bitmap that will be

used to represent the SKU in the Loading Editor.
The image must be a .bmp file that is 28x28 pixels
and 256 colors or less.
Unload First
No
Indicates if the SKU should be handled first, before

any other items on an order. A Y, 1, or T indicates
that the SKU is marked Unload First. A N, 0, or F
indicates that the SKU is not marked Unload First.
This is only used when Mid-Route Sourcing is
enabled.
432

Import Layouts
Field
Required
Max.
Length
Description
Warehouse
Zone
No
15
The zone in the warehouse where the time is

located. This information is used for building
pallets in the Loading Editor. 1
Pallet Primary
Zone
No
15
The primary location in the warehouse where

pallets of the item are stored. This information is
used for the Pick Sheet. 1
Pallet
Secondary
Zone
No
15
A second place in the warehouse where pallets of

the item are stored. This information is used for the
Pick Sheet. 1
Layer Primary
Zone
No
15
The primary location in the warehouse where layers

of the item are located. This information is only
used on the Pick Sheet.
Layer
Secondary
Zone
No
15
A second location in the warehouse where layers of

the item are located. This information is only used
on the Pick Sheet.
Hand Primary
Zone
No
15
The primary location in the warehouse where

singles of the item are located. This information is
only used on the Pick Sheet.
Hand
Secondary
Zone
No
15
The secondary location in the warehouse where

singles of the item are located. This information is
only used on the Pick Sheet.
Helper
Variable
Service Time
Size 1, 2, 3
No
11 each
The amount of time needed to deliver one unit with

a helper. The variable service time must be
formatted as listed below:
Non-helper
Variable
Service Time
Size 1, 2, 3
No
Ten minutes - 10000000

Minutes - 1000000
Tenths of Minutes - 100000
Hundredths of Minutes - 10000
Thousandths of Minutes - 1000
Ten Thousandths of Minutes - 100
Hundred Thousandths of Minutes - 10
Millionths of Minutes - 1
11 each
The amount of time needed to deliver one unit

without a helper. The variable service time must be
formatted as listed below:
Ten minutes - 10000000
Minutes - 1000000
Tenths of Minutes - 100000
Hundredths of Minutes - 10000
Thousandths of Minutes - 1000
Ten Thousandths of Minutes - 100
Hundred Thousandths of Minutes - 10
Millionths of Minutes - 1
Operations Guide
433
Import Layouts
Field
Required
Max.
Length
Description
Product Type
No
The product type of the SKU.
Manufacturer
Pallet Type
No
Indicates if the SKUs may be delivered on

manufacturers pallets. This information is only
used with FleetLoader.
Minimum
Percent to use
Manufacturer
Pallet Type
No
The minimum amount the manufacturer pallet type

must be filled with that SKU in order for that
particular pallet type to be used when loading the
truck.
1You
SKU Brand Available Fields

You can import information about your SKU brands, rather than entering it manually. The
available fields, the maximum length, and a brief description of each field are listed in the
table below.
Field
Required
Max.
Length
Description
Brand ID
Yes
15
The unique identified for the SKU brand. This field

must be completed. 1
Description
No
30
A description of the brand, such RN Cola.
1You
Depot SKUs Available Fields

Used with: Roadnet
You can import information about your Depot SKUs, rather than entering it manually.
in the table below.
Field
Required
Max.
Length
Description
Location Type
No
The Location Type ID. This must exist in the

Location Type table. The Location Type for a
Depot SKU must be DPT. If left blank and there is
a matching Location ID in Roadnet, it will default
to DPT.
434

Import Layouts
Field
Required
Max.
Length
Description
Location ID
Yes
15
The unique ID for the location. The Location ID

must already exist in Roadnet. 1
SKU ID
Yes
32
The unique ID of the SKU. The SKU ID must

already exist in Roadnet. 1
Accepts
No
Indicates if the location accepts this SKU. A Y, 1,

or T indicates that the location accepts this SKU. A
N, 0, or F indicates that the location does not accept
this SKU.
Distributes
No
Indicates if the location distributes this SKU. A Y,

1, or T indicates that the location distributes this
SKU. A N, 0, or F indicates that the location does
not distribute this SKU.
Cost Size 1, 2,
or 3
No
30
Cost for accepting this SKU, per Size 1, 2, or 3, at

this location. A negative sign in front of the number
indicates profit.
Click on a link below for more information.

Working with Depot SKUs
Equipment Types Available Fields
Used with: Roadnet, Territory Planner, MobileCast, FleetLoader
You can import information about your equipment types, rather than entering it manually.
in the table below.
Field
Required
Max.
Length
Description
Equipment
Type ID
Yes
15
The unique identifier for the type. This field is

required. 1
Description
No
255
A description of the type, such as 16 Bay Truck.
Height
No
11
The height of the equipment.
Weight
No
11
The weight of the equipment type.
Fixed Cost
No
11
The cost for running the equipment regardless of

the distance traveled. This includes costs such as
insurance, license fees, etc.
Operations Guide
435
Import Layouts
Field
Required
Max.
Length
Description
Variable Cost
No
11
The total operating cost per mile/kilometer for the

equipment type. This cost includes things such as
wear and tear, gasoline, and oil.
Total of Size 1,
2, 3
No
11 each
The amount of product the equipment can hold

when measured as size 1, 2 or 3.
Subtotal of
Size 1, 2, 3
Category 1, 2,
3
No
11 each
The amount of product the equipment can hold

when measured as size 1, category 1, 2 or 3.
Front Wheel
Bays
No
The number of bays over the front wheels on the

drivers side of the equipment;.the corresponding
positions for the passenger side of the equipment
will automatically be added. This information is
only used for FleetLoader.
Full Bays
Between
Wheel Bays
No
The number of full bays between the front and rear

wheels on the drivers side of the equipment; the
corresponding positions for the passenger side of
the equipment will automatically be added. This
information is only used for FleetLoader.
Rear Wheel
Bays
No
The number of bays over the rear wheels on the

drivers side of the equipment; the corresponding
Full Bays
Behind Rear
Wheel Bays
No
The number of bays behind the rear wheels on the

drivers side of the equipment; the corresponding
Rear Bays
No
The number of rear bays on the equipment. Include

only bays that can only be accessed from the rear of
the equipment. This information is only used for
FleetLoader.
Rear Axles
No
The number of rear axles on the equipment. This

information is only used for FleetLoader.
Body Type
No
15
The type for the equipment. Use 0 for a side loader,

1 for a straight truck, and 10 for a trailer. This
information is only used for FleetLoader. 1
Prohibited
from Time of
Day Restricted
Areas and
Paths
No
Indicates whether or not the equipment type is

prohibited from traveling on restricted rush hour
areas or paths during specified rush hours. A T
indicates the type is restricted; all other characters
indicate the type is not restricted.
436

Import Layouts
Field
Required
Max.
Length
Description
Power Unit
No
Indicates whether or not the type has an engine,

such as a tractor. A T indicates the type is a power
unit; all other characters indicate the type is not a
power unit. This information is only used for
MobileCast.
Carries Load
No
Indicates if the equipment type is a trailer, bulk

truck, or other that has capacity to carry product.
Use a T for true, all other characters indicate false.
This information is only used for MobileCast.
Travel Time
Variation Pct
No
The change in the travel time for the equipment

type expressed as a percentage. Include a negative
to indicate a slower travel time. This information is
only needed when Travel Time Variation is
enabled.
Travel Time
Variation
Enable
No
Allows for adjustments to the overall travel time

depending upon the equipment type. A T, 1, or Y
indicates the variation is enabled; all other
characters indicate the variation is not enabled. If
you enable the Travel Time Variation, you also
must specify the Travel Time Variation Percentage.
Prohibited
from
Commercially
Restricted
Roads
No

prohibited from traveling on commercially
restricted roads. A T, Y, or 1 indicates the type is
prohibited; all other characters indicate the type is
not prohibited.
Road
Restrictions
No

prohibited from traveling on roads that are
restricted due to their height and weight limits. A T,
Y, or 1 indicates the type is prohibited; all other
characters indicate the type is not prohibited.
Avg. Fuel
Consumptions
No
The amount of fuel the type consumes per mile.

Must be entered as miles per gallon (ex. 10.5
MPG).
Carbon
Emission
Factor
No
The amount of carbon produced the type produces

per fule unit or distance driven (ex. 19.6 CO2/
gallon).
Bulk Truck
Bed Width
No
62
The width of the bulk truck bed, measured from

side to side. This information is only used with
FleetLoader. The unit of measurement used here
must match the units used in the other pallet type
and package type dimensions.
Operations Guide
437
Import Layouts
Field
Required
Max.
Length
Description
Bulk Truck
Bed Depth
No
The depth of the bulk truck bed, measured from

front to rear. This information is only used with
Minimum
Empty Space
Within Row
No
The minimum total empty space within the

row.This information is only used with
Fixed Empty
Space
Between Rows
No
The fixed amount of empty space between the rows

of pallets. This information is only used with
1You
Skill Set Available Fields

You can import information about your skill sets, rather than entering it manually. Once
the skill sets and activities have been imported, you can import the skill set activities,
which tells which activities are in the skill sets. The available fields, the maximum length,
and a brief description of each field are listed in the table below.
Field
Required
Max.
Length
Description
Skill Set ID
Yes
15
The unique identified for the skill set. This field

Description
No
60
A description of the skill set, such as Master

Plumber.
Service Time
Factor
No
11
The factor each activitys service time should be

multiplied by to calculate the service time for an
employee with this skill set. If no factor is entered,
the activitys service time will be used.
1You
438

Import Layouts
Activities Available Fields

You can import information about your activities, rather than entering it manually. Once
both the skill sets and activities have been imported, you can import the skill set activities,
which tells which activities are in the skill sets. The available fields, the maximum length,
and a brief description of each field are listed in the table below.
Field
Required
Max.
Length
Description
Activity ID
Yes
32
The unique identified for the activity. This field

Description
No
255
A description of the activity, such as Install

Dishwasher.
Service Time
No
11
The amount of time, in minutes, needed to complete

the activity.
Skill Set - Activities Available Fields

You can import information about the activities that are included in each skill set, rather
than entering it manually. This information cannot be imported until both the activities
and skill sets have been imported. The available fields, the maximum length, and a brief
description of each field are listed in the table below.
Field
Required
Max.
Length
Description
Skill Set ID
Yes
15
The unique identified for the skill set. This field

Activity ID
Yes
32
The unique identifier for the activity. This field

1You
Bay Type Capacity Available Fields

You can import information about your bay type capacity, rather than entering it
manually. This information cannot be imported until both the bay types and package types
Operations Guide
439
Import Layouts
have been entered. The available fields, the maximum length, and a brief description of
each field are listed in the table below.
Field
Required
Max.
Length
Description
Package Type
ID
Yes
15
The unique identifier for this package type. 1
Bay Type ID
Yes
15
The unique identifier for this bay type. 1
Bay Capacity
No
The total amount of this package type that can fit in

this bay.
Pallet Type Capacity Available Fields

You can import information about your pallet type capacity, rather than entering it
manually. This information cannot be imported until both the pallet types and package
types have been entered. The available fields, the maximum length, and a brief description
of each field are listed in the table below..
Field
Required
Max.
Length
Description
Package Type
ID
Yes
15
The unique identifier for this package type. 1
Pallet Loading
Method ID
Yes
Specifies the loading method you are using. The

pallet loading method has been defined as the
Loading Method ID in the Maintenance module. 1
Pallet Type ID
Yes
The unique identifier for this pallet type. 1
Quantity Per
Layer
No
The number of package type items that can be

packed in one layer.
Layers Per
Pallet
No
The number of layers of this package type that can

be contained in a single pallet.
Full Pallet
Capacity
No
The total number of this package type that can be

put on a pallet
440

Roadnet-Routing Editor
Creating Routes in the Routing Editor
Creating Routes in the Routing Editor

Used with: Roadnet
Note: If you were not granted access to the Routing Editor in the Administration module,
The Roadnet Routing Editor is where you create the daily routes for your drivers. In the
Routing Editor you can:
Use maps to display and edit routes
Create standard routes and standard route sets
Create daily routes
Use standard sequencing to combine standard and dynamic routing
Lock and unlock orders
Evaluate and edit routes
Search for specific routes, stops, and orders
Print reports
Print driver directions
Send routes to MobileCast
Export routes to a host computer
The Routing Editor lets you route your daily orders and evaluate the subsequent routes
and change them as needed. You can assign equipment and drivers to the routes in the
Editor, and upload the resulting routing information to the host. Both standard routes and
daily routes can be created in the Routing Editor. The daily routes can be standard or
dynamic routes, or a combination of both.
Standard routes are routes with specific locations in a certain order. If you are using
standard routing, when orders are received for any of the stops on the route, that stop is
included in the route for the day. One of the benefits of using standard routes is that you
know which drivers are going to which customers on each day. Standard routes also tend
to require less maintenance; the downside to standard routes is that they typically are more
expensive to run.
Dynamic routes are made from scratch, considering only that days orders. Dynamic
routes tend to be less expensive to run, but require more maintenance since location,
equipment, and driver information must be current. Roadnet lets you create a combination
of standard and dynamic routes.
Within the Editor, routes are organized into sessions. A routing session is all the
information about the route, including the orders, locations, and routes. Typically, you
would have one routing session per day, with all the routes for that day. However, if you
wanted to try a what-if scenario for a days routes, you could copy the orders into
another session and run the new session without damaging your actual routes for the day.
Operations Guide
441
When orders are entered into Roadnet, whether by importing or manual entry, they appear
in the Editor as unassigneds, or orders that have not been assigned to a route. In the Editor,
you can choose to route all unassigned orders, or select specific unassigneds to route.
442

Entering the Routing Editor
Entering the Routing Editor

Used with: Roadnet
Before performing any tasks in the Routing Editor, you must first get into the module and
choose the session you want to work with.
Step 1: Click on the Routing icon to open the Routing Editor. The Editor opens with the
Routing Sessions window visible.
When you first enter the Routing Editor, the Routing Sessions window appears, listing
all existing sessions. Double-click on the session you want to work with.
Step 2: In the Routing Sessions window, double-click on the session you want to work
with. The session opens.
Hint: Within a routing session, you can arrange the commonly used windows to suit you
and then save their size and positions using Windows Favorites. When you
enter the session, the windows will open, already sized and positioned.
Operations Guide
443
Maintaining Items in the Routing Editor
Maintaining Items in the Routing Editor

Used with: Roadnet
You can add and maintain employees, equipment, and other resources in the Routing
Editor. These items are added and edited in the same manner as they are in the
Maintenance module. General instructions on adding and editing these items are below;
for more information see the appropriate section in Maintenance.
Note: If your login rights established in the Administration module do not include the
permission to perform maintenance, you will not be able to add or edit items in the
Routing Editor.
Locations cannot be added from within the Routing Editor, and orders cannot be
added or changed in the Editor.
Step 1: If necessary, click on the Routing icon to open the Routing Editor. The Editor
opens with the Routing Sessions window visible. Double-click on the session you
want to work with.
Step 2: Click on the List menu and select the item to be maintained. A window opens
listing all of that item that exists.
Step 3: To add an item, click on the Add icon or press [Insert]. The Add window
opens. When the window is complete, click the Save icon or press [Ctrl]+[S] to
save the new item.
To edit an existing item, double-click on the item, or right-click on it and select
Edit from the menu that pops up. The Edit window opens. Make the necessary
changes and click the Save icon, or press [Ctrl]+[S].
444

Using Maps in the Routing Editor

Used with: Roadnet
The maps can be very useful as a way to display and work with your daily and standard
routes in the Routing Editor. This section discusses some map options that are specific to
Roadnets Routing Editor. See Maps and RouteNet for more information on using maps.
You can work almost totally from the map in the Routing Editor, selecting routes or stops
that you want to edit. To select a route or stop on the map to work with, click on the route/
stop; to select multiple routes/stops, hold down the [Ctrl] key while clicking. To deselect
all selected items, click the Deselect All icon or press [Ctrl]+[Shift]+[D].
Depending on the maps zoom level and the quantity of routes and stops being displayed,
it may be difficult to select a single stop or route. You can use the Map Picked Items list
to help determine when more than one item has been selected; in addition when you drag
stops/routes and more than one item is selected, the cursor changes to indicate multiple
items are selected.
In the Routing Editor the map has some extra icons specific to routing. These icons, which
are for standard routes and daily routes, are available when more than one route is
displayed on the map; simply click on the icon for a list of all displayed routes, and you
can choose the route you want to work with. In addition, the Plot Information icon is
available; this icon opens a window to provide information about the route or location the
mouse is currently over.
The three icons shown above

appear only in the Routing
Editor. The first icon, the Daily
Routes icon, lists all daily
routes displayed on the
map.The second icon, the
Standard Routes icon, lists all
standard routes displayed on
the map. You can use either of
these icons to open the Routes
menu for a displayed route. The
third icon, the Plot Information
icon, displays information in a
separate window about the
location the mouse is currently
over.
If you have several routes plotted on a map, or more than one map open, you can have the
map zoom to a route(s) or stop(s), flash a route(s) or stop(s), or the route animate to help
locate it on the map. To use one of the options, select the route(s) or stop(s) you want to
find, then right-click on a selected item and choose the appropriate option from the menu
that pops up. Additionally, when you click on the route in the Active or Built Routes
Operations Guide
445
window, it is highlighted on the map. Likewise, when you click on a stop in a Stop list, it
is highlighted on the map.
Using the Plot Info Window
The Plot Info window allows you to quickly view information about stops and routes that
are plotted on the map. You can customize this window so that it displays the information
that is important to your organization. You can also change the layout of the window so
that the information is organized how you like.
To use the Plot Info window, on the map toolbar click the Plot Information icon. To see
information about a feature on the map, simply position the mouse pointer on the feature.
For example, to see information about a stop, put the mouse pointer over that stop on the
map.
Notes: To prevent the Plot Info window from changing as you pass over another stop,
route, etc., hold down the [Ctrl] key.
The Plot Info window may contain information about both delivery and pickup
quantities. The delivery quantities are displayed in black and the pickup quantities
are displayed in red.
You can change the size and shape of the Plot Info window to find the best fit for
your screen. To change the size and shape of the Plot Information window, hold
the mouse over an edge or the bottom right corner of the window; when a doubleended arrow appears, hold down the left mouse button and drag the mouse to size
the window.
The Plot Info window lets you

easily see information about the
stop or route the mouse is over
on the map.
To customize the Plot Info window, click the Customize icon. Click on the tab for the
plot feature you want to customize the Plot Info window for.
To add a piece of information to the Plot Info window, drag and drop that item from
Available Fields column to the Displayed Fields column. To remove a piece of
information from the Plot Info window, drag and drop that item from the Displayed Fields
column to the Available Fields column.
446

Note: Information will be displayed in the Plot Info window in the same order as it is
arranged in the Displayed Fields column. You can drag and drop the items in the
Displayed Fields column to arrange the information in the order you desire.
To have information always appear on a new line in the Plot Info window, drag and
drop <Line Break> to anywhere in the Displayed Fields column where you want a new
line to start.
To have the Plot Info window show the description of each piece of information that
is displayed, check Show each fields text label. If this option is not selected, information
will be shown without any descriptions. However, you will be able to hover the mouse
over each piece of information to display its description.
Click on another tab to customize the Plot Info window for another plot feature. When
you are finished, click the Save icon. The Plot Info window will appear as you arranged
it until it is changed again. Depending on how the Roadnet Transportation Suite is set up,
changes you make may only apply to you or they may apply to all users.
Using the Map Picked Items List
When using a map in the Routing Editor, you may sometimes find it difficult to determine
exactly what is selected on the map, especially if you have several routes displayed. This
can cause problems, because if you choose to perform an action from the map, such as
sequencing a route, that action will be performed on all selected items, so you may
unintentionally sequence a route. To help prevent this problem, you can open the Picked
Items list for the map and see which items are selected. On the selected items list, you can
deselect items you dont want selected, as well as use the same right-click menus that are
available on the map, or drag and drop items as you would from other list windows.
Operations Guide
447
The selected item list appears as a notebook, with several tabs showing different items
that could be selected: Stops, Routes, Standard Stops, or Standard Routes. Click on the
appropriate tab to see those selected items.
You can view the stops, routes, standard stops, and standard routes that are selected on the
map in the Selected Items list.
To open the Picked Items list, click on the Show Hide Pick List icon or press the [F9]
key. The list opens on the left side of the map with all selected items displayed. As you
select additional items on the map, this list will be automatically updated.
To remove an item from the Picked Items list, hold down the [Ctrl] key and click on it.
After removing the items you do not want selected, click the [Update Map Selection]
button to deselect the items on the map.
To perform an action on the picked items, right-click on a selected item and select the
desired action from the menu that pops up.
To close the Picked Items list, click the Show Hide Pick List icon or press the [F9] key.
To open the map with the Picked Items list displayed, check Show Pick List Notebook
on the General Page of the Map Options notebook.
Using the Map in Route Scroll Mode
You can choose to view your routes using the Route Scroll Mode. If you are using Route
Scroll mode, you can easily see the Route window, Stop List, and map for a selected route,
making it very handy to use when analyzing your routes. And, if you have several routes
in Route Scroll mode, you can easily move from one route to the next, easily seeing the
information for each route. From Route Scroll mode you can access any of the menus
448

normally available from a Route window, Stop List, or map; the windows are simply
arranged and connected so you are seeing all the information for a single route at once.
Route Scroll Mode lets you analyze a single route at a time, and then click the arrow to
move to the next route.
Note: When a Mid-Route Sourcing depot is selected in Route Scroll mode, the rooftop
displays in black, making it easier to locate.
To start Route Scroll Mode, click the Scroll View icon on the map. The map changes to
Route Scroll Mode; if several routes were displayed on the map when you switched to
Route Scroll mode, the first route will be displayed in the Route Scroll window. You can
use the arrows to move from route to route.
Note: To have the map always open in Route Scroll Mode, check Open in Route
Scrolling Mode on the General page of the Map Options notebook.
To display all routes that are in the Route Scroll window on the map, while the Route
window and Stop List still show one route, click the Show Multiple/Single Route In Map
View icon. This can help you see the main route in perspective with the other routes.
To add routes to the Route Scroll Mode, drag the routes from the Routes window to the
Route Scroll window. The routes may not be displayed on the map, but they will be added
to the Route list at the top of the Route Scroll window, and you can use the arrow icons
to move from one route to another.
To change the route that is displayed in the Route window and Stop List, hold down
the [Alt] key and, on the map, double-click on the route you want to become the main
route in the Route Scroll window.
To turn off Route Scroll Mode, and have a simple map displayed, click the Scroll View
Mode icon.
Operations Guide
449
Setting up the Map
You have some choices regarding how routes are displayed on the map, including whether
or not the depot is displayed, whether or not unassigned stops are displayed, and how the
stop markers appear on the map. These options are all available in the Map Properties
notebook. To specify your preferences, click on the Map Options icon and select
Properties from the menu that appears. The Map Properties notebook opens. The first six
pages of the notebook are discussed in Maps and RouteNet; the options that are specific
to the Routing Editor are discussed in the following sections.
The General page of the Map Options notebook lets you specify some generic options that
will apply to all maps in the Planning Editor or Routing Editor.
To set the speed that territories, routes, etc. will flash when Flash on Map is chosen,
move the Flash Speed slider bar.
To have the map zoom to the selected territory, week, route, or stop before flashing,
check Locate First.
To have the map open with the Selected Items list visible, check Show Pick List
Notebook. If this option is selected, the map will always open with a list on the side
displaying all items selected on the map. To turn the pick list on and off from any
individual map click the Show Hide Pick List icon.
To have the map open in Route Scroll mode, check Open in Route Scrolling Mode. If
this option is selected, the map will always open with the Route list displayed at the top,
and the Stop List for the displayed route below the map. Route Scrolling mode can be very
helpful for analyzing individual routes. To turn Route Scroll mode on and off from any
individual map click the Scroll View icon.
To specify how daily and standard routes appear on the map, click on the Daily Routes or
Std Routes tab.
To display the route path between
stops, verify that a check appears in the
Show route paths box.
To have the path follow actual roads,
verify that a check is in the Show full
paths box.
To have the path displayed as straight
lines, make sure there is not a check in the
Show full paths box.
To change the width of the route path,
click in the Line width box and enter the
desired thickness in pixels.
To change the line style (solid or
dashed), click on the down arrow next to
Line style and select the line you want.
You can have daily and standard routes

displayed differently on the map so that they
can be easily differentiated.
450

You can use the line style to help differentiate between standard and daily routes.
To select whether the routes path color will indicate the route or the day of the week,
click the Color By arrow and choose the appropriate option. When you are viewing routes
for multiple days, you may want to see the route paths by day of the week, but when
viewing routes for a single day you want to use the route color.
To fade the route path and markers, click on the slider bar and move the indicator to
the left (faded) or right (normal).
To change the stop marker, click on the arrow next to Marker and select the marker you
want. To change the font style or size on the marker, click on the arrow next to Marker
Font and choose the style and size in the window that opens.
To choose how the stop markers are colored on the map, click on the down arrow next
to Color by and select the choice you want (by route, account type, time window type,
service time type, or day of week).
To choose the text that will appear on the marker, click the Marker Text arrow to open
a list of options; click on an option to select it. The choices are: route ID, stop number,
location ID, and location type/ID.
To show exceptions on the map, verify that a check is present in the Route or Stop boxes.
To change the colors used for the days of the week, click on the [Day Colors] button;
the Day Colors window opens. To change the color for a day, click on the color chip and
select the new color from the palette that opens. Click the [OK] button to save the
changes.
To show the depot or unassigned stops on the map, verify that a check is present in the
Show depot or Show unassigneds boxes. You can also toggle to have the depots and
unassigned stops visible by pressing [Alt]+[D] (depots) or [Alt]+[U] (unassigneds).
Hint: Choose a different marker, font, and line style for your standard routes than you
use for your daily routes. It will be much easier to distinguish daily from standard
routes on the map. Also, you may want to leave daily routes as Normal fade and
standard routes as Faded.
To set the default speeds for the flash or animate options, click on the General tab in the
Map Options notebook.
To set the speed at which the stops or routes flash or animate on the map, move the
slider bar.
To have the map zoom to the stop or route before flashing/animating, check the
Locate First box.
To see saved area attributes displayed on the maps, click on the Area Attributes tab.
To select the area attribute set you want to see on the map, click the Area Attribute
Set arrow and select the saved area attribute set you want to display, then check the
appropriate days. Saved area attribute information will be displayed in the status bar of
the map when the cursor is hovered over an area attribute. The location of area attributes
are indicated by a triangle appearing at the centroid of the original route. This triangle is
Operations Guide
451
the same color as the source route. If multiple icons are stacked on top of each other, this
is indicated by an asterisk (*) on the status bar.
To turn off the area attributes display function, click the Area Attribute Set arrow and
select <NONE>.
To move the centroid of the area attribute set on the map, right-click on the Area
Attributes icon and select Move. The cursor changes to a crosshair. Click on the desired
location on the map to place the crosshair. The icon is now moved to this location.
Notes: While you are in Move mode, you can use the zoom and center options to move
around the map as needed.
Moving saved area attributes does not change routes that have already been
created; in order to affect the outcome of dynamic routing, you must move the
centroid before you create the route.
452

Viewing Routes in the Routing Editor

Used with: Roadnet
Roadnet offers two ways you can view the routes in the Routing Editor. You can use the
map or list window to look at the routes. The list window provides more information
about the route, while the map lets you see how the route looks graphically. The list
window also lets you access the stops and orders for the route. Right-clicking the route on
either the map or list window opens the menu from which you can work with the route.
To see the route(s) on a map, right-click on the route and select Plot from the menu that
pops up ([Ctrl]+[P]), or click the Plot icon on the Routes toolbar. A map opens with the
route visible. If you want to add the route to a map that is already open, right-click on the
route in the Routes window, drag the route to the map, and choose the desired fit option.
Hint: If only portions of the routes are visible on the map, click the Fit All icon to see
all the complete routes.
To see the route and its surrounding locations and routes, and parts of routes, on a
map, right-click on a route and select Plot Vicinity from the menu that pops up.
You can view routes on the map or

in a list window.
To see a specific route or stop when multiple routes are displayed on the map, select
the route or stop you want to view, then right-click on a selected item and choose Locate,
Flash, or Animate (routes only) from the menu that pops up. If you select Locate, the map
zooms to the selected items; if you select Flash the selected items flash one at a time.
To easily see route on a map and the stop list simultaneously, click the Scroll View
icon on the map; the map switches to Scroll mode. In Scroll mode the map window
changes so that the Route window is displayed above the map, and the Stop List, showing
all the stops in the route, is displayed below the map. When in Scroll Mode, you can
perform any of the actions normally available from any of these windows. If more than
Operations Guide
453
one route was selected when you started scroll mode, you can use the arrows above the
map to move between routes.
To see the route in the list window, click on the List menu and select Routes, then All,
Active, or Built. The appropriate list window opens. You can arrange the columns in the
list window so that the information you want to see is visible. See Arranging List and
Maintenance Windows for more information.
To see all the routes for a specific day of the week, click on the List menu and select
Routes, then the day of the week. A window will open listing all routes for that weekday.
To see all the routes for a range of dates, such as for an entire week, click on the List
menu and select Routes, then Date; the Specify Date Range window opens. Enter the first
and last date you want to see routes for and click the [OK] button; a window opens listing
all routes in that date range.
To see a list of only selected routes, such as all the routes in a geographic area, select the
routes, then right-click on a selected route and select Open subset view from the menu that
pops up. You can add and delete routes from a subset view window; see Adding a Route
To remove a route(s) from the map, select the route(s) then right-click on a selected
route and select Remove from Map from the menu that pops up. All selected routes will
be removed from the map.
To see the stops on the route, double-click on the route in the Routes window. To see
the orders for the stop, double-click on the stop; to see the line items for the order, doubleclick on the order. All the windows can be arranged so that information you want to see
is easily found.
To view saved area attributes on the map, select the area attribute set and days on the
Area Attributes page of the Map Properties notebook. See Using Maps in the Routing
Editor for more information.
To edit saved area attribute sets, right-click on the Saved Area Attributes icon and
select Edit from the menu that pops up. See Editing the Area Attributes for more
information.
454

Using the Toolbars in the Routing Editor

Used with: Roadnet
The Routing Editor includes toolbars that allow you to quickly and easily perform several
common tasks. To use the toolbar, open it and place in an accessible, yet out of the way
place, on the screen; when you need to perform a task simply click the appropriate icon
on the toolbar. In many cases, this is quicker and easier than using the corresponding
menu option. The following toolbars, and the tasks you can perform from them, are
available in the Routing Editor:
Generalincludes icons for Create Routes, Speed Assign, Send Orders, and Locate.
These options will be available once you are working in a session.
Routeincludes options for both daily routes and standard routes. The icons that are
available depend on the type of route(s) selected. The Route toolbar contains icons for
Plot, Properties, Assign Sequential Route ID, Sequence, Flip, Standard Route Sequence,
Line Sequence Endpoint, Line Sequence Midpoint, Time Window, Time Window Swap,
Balance by Time, Balance by % Capacity, Balance by Load, Combine No Resequence,
Combine Resequence, and Add Stops to Standard Routes.
Stopincludes icons for Suggest Route and Assign Break/Wait.
The actions available on each toolbar will depend on what is selected in the windows. For
instance, if only built routes are selected the only option that will be available in the
Routes toolbar is Plot. Likewise, if only one active route is selected, Line Sequence, Time
Window Swap, Balance, and Combine will not be available in the Routes toolbar.
Step 2: Click on the Tools menu and select Toolbars, then the toolbar you want to open.
Step 3: Move the toolbar where you want it to be located on the screen. The toolbar will
reopen in that position next time you enter the editor. You can dock the toolbars
to the top, bottom, or either side of the Editor window, or place them within the
window.
Step 4: Open other toolbars and position them as desired.
To use one of the options on a toolbar, simply click on it to launch the action. The icon
for each action is shown in the procedure for the action.
The icons available in each toolbar, and the action associated with it, are shown in the
following tables.
General Toolbar
Icon
Name
Action
Route All
Available Orders
Opens the Route Creation Process window, where

you can to choose the options that will be used to
create routes or create routes from all available
orders.
Operations Guide
455
Icon
Name
Action
Speed Assign
Active Routes
Opens the Speed Assign window where you can

assign drivers, equipment, and route IDs to the
routes.
Send All Orders
Opens the Send Orders window, where you can

export your orders to a mainframe or network.
Locate
Opens a window where you can search for routes,

stops, or orders containing a specific location,
driver, or equipment.
Route Toolbar
Icon
Name
Action
Plot
Opens a map displaying the selected routes.
Route Properties
Opens the Route Properties window, where you can

assign a driver, equipment, or change other
attributes of the route.
Sequence
Sequences the stops on the selected routes based on

least distance.
Flip
Reverses the order of the stops on the selected

routes so that the first stop becomes the last stop,
etc.
Line Sequence
By Midpoint
Sequences the stops on the selected routes so that

the stop that is furthest from the other stops is
routed first.
Line Sequence
By Endpoint
Sequences the stops on the selected routes so that

the two stops that are furthest from each other are
the first and last stop on the route.
Adjust MidRoute Sourcing
Reassigns mid-route sourcing depots to the route

without changing the stop sequence.
Combine and No
Resequence
Combines the selected routes without resequencing

the stops.
Combine
Resequence
Combines the selected routes then resequences the

stops on the subsequent route.
Assign
Sequential Route
ID
Opens the Assign Sequential Route ID window

where you can assign IDs to the selected routes.
Standard Route
Sequence

selected standard routes. Stops that are not on the
standard route are either placed at the end of the
route or intermingled with other stops.
456

Icon
Name
Action
Time Window

their time windows and the time window options
selected in the Options notebook. The goal is to
make as many time windows as possible.
Time Window
Swap

their time windows and the time window options
selected in the Options notebook. Stops may be
swapped between routes to meet more time
windows.
Balance by Time
Moves stops between the selected routes so that the

resulting routes will have more balanced run times.
Balance by %
Capacity

resulting routes will have more balanced capacities.
Balance by Load

resulting routes will have more balanced loads.
Add Standard
Stops
Opens the Add Stop window, where you can add

stops to the selected standard route.
Stop Toolbar
Icon
Name
Action
Suggest Route
Opens the Suggest Route window, where you can

have the Routing Editor suggest the best route for
the stop based on the criteria you specify.
Assign Break/
Wait
Opens the Assign Break or Wait window, where

you can assign a break or layover (after the selected
stop) or a wait (before the selected stop).
Routing Editor Tools Toolbars General/Route/Stop
Operations Guide
457
Setting the Routing Editor Options

Used with: Roadnet
The Options notebook lets you specify how many things appear and function in the
Routing Editor, such as how route and stop exceptions are displayed, how split orders are
numbered, and the factors that are considered when routes are time windowed.
Routing Sessions window visible. Double-click on the session you want to work
with.
Step 3: Select the options as appropriate. The choices on each page are described in the
following sections.
In the Options
notebook, you can
specify how route
reloads are viewed in
the Editor.
Step 4: Click the [Apply] button, then the [Save] button.

Routing Editor Tools Options Apply Save
General Routing Options
The General page of the Options notebook lets you specify how route reloads are viewed
in the Editor.
The Options notebook is opened by selecting Options from the Tools menu in the Routing
Editor.
458

To specify that route reloads appear as a single route in the Routes window, check
Create Reload As One Route.
To have Roadnet check the equipments available capacity while sequencing, time
windowing, balancing, or performing other route actions, check the appropriate size
alias in the Check Capacity while Performing Route Actions box. This option is
particularly helpful if your routes contain both pickups and deliveries, and you want to
monitor the capacity available during the route.
Display Routing Options
The Display page of the Options notebook lets you specify how some windows appear in
the Routing Editor. You can choose whether or not to have additional routing information
shown in the Stop list and what windows are opened when you open an order.
Editor.
To have the origin, destination, and pre- and post-route stops displayed in the
routes stop list, check Enable Advanced View in the Stop View area. If selected,
additional rows containing the routes origin and destination, as well as any pre- and postroute stops, will be shown. In the Row Colors area, click the arrow to open a color palette
and choose the color that will be used for each row. The selection made here will affect
how both standard routes and daily routes are displayed.
To choose the windows that open when you double-click on an order, select one of
the options in the Action when opening an Order area. To have only the Line Items
window open, select Show Line Items. To have only the order activities open, select Show
Order Activities. To have both windows open, select Show Line Items and Order
Activities.
Hint: If you are using both order activities and line items, select Show Line Items and
Order Activities so you can see both items.
To have the Roadnet Transportation Suite automatically round stop quantities up
to whole numbers, check each size alias you want to be rounded in the Increase Stop Qty
to Whole Number area. For example, if you check the Size 1 alias and there is a stop with
a Size 1 quantity of 15.2, it will be displayed as 16. 15.2 will be retained by the Roadnet
Transportation Suite and used when making any calculations involving that Size 1 stop
quantity.
To use row coloring to show exceptions, check Display Text with Exception Color.
When this option is selected, windows that list stops or routes will display a row of text
in color if an enabled exception occurred on that rows stop or route. The text will appear
in the color that is assigned to the exception that occurred. When more than one exception
occurred on a stop or route, the color assigned to the exception that is highest in the
exception list will be used. The text color will remain the default color for any stop or
route where no enabled exceptions occurred.
Note: When the Display Text with Exception Color option is selected, column coloring
will not be used in windows that use row coloring. Column coloring is used in
Operations Guide
459
several columns throughout Roadnet to alert you of possible problems. For

example, in the Stops window any stop that is unassigned will have red text in the
Route Number column. If you rely on column coloring to alert you, do not select
the Display Text with Exception Color option.
Breaks/Waits Routing Options
The Breaks/Waits page of the Routing Options notebook lets you specify that breaks and/
or waits are automatically added to the routes at specified times. Breaks will be added
after stops based on the specified time span, while waits will be added before stops to
allow the driver to meet the stops time windows. If these options are selected, breaks and
waits will be automatically added when the routes are created, sequenced, or when you
manually move stops on the routes. When breaks/waits are automatically added, it is not
necessary to work with them manually or have them added elsewhere, so the following
options in the Routing Editor are no longer available:
You will not be able to manually add breaks or move breaks on the routes.
The breaks options will not be available in the Routing Pass Options notebook.
The waits options will not be available on the Time Windows page of the Routing
Options notebook or the Routing Pass Options notebook.
If you have breaks and

waits automatically
inserted onto your
routes, you will not be
able to manually add
breaks, drag breaks or
waits to a different place
on the route, or use the
specify waits elsewhere
in the Editor.
460

Editor.
To have breaks automatically inserted when the routes are created, sequenced, or
stops are manually moved, check Insert Breaks Automatically and enter the information
for when each break should occur.
Choose how the Routing Editor should calculate when the break(s) should begin:
Span from start of routeuse the routes starting time to determine when the break
should occur. If this option is selected, the span time starts when the driver leaves the
depot.
Span from previous breakuse the ending time of the previous break to determine
when the break should start. If this option is selected, the span time starts when the driver
leaves the last break entered.
Choose whether or not the break can occur after the span time has expired:
Span is approximatethe break will be placed after a stop as close as possible to the
proper span time, but may occur after the span has expired.
Span is maximumthe break will be placed after a stop as close as possible to the proper
span time, but will not occur after the span has expired. The break may occur before the
span expires.
Enter the spans and duration for each break. In the Span field, enter the length of time
after the start of the route or previous break when the break should start; in the Travel
Span field, enter the length of time the driver can drive before a break must occur. Enter
the length of the break in Duration. If the driver is paid for the break, check Paid. Click
the [Update] button to save the break information. To enter another break, click the next
line in the list of breaks.
Note: If you enter times in both the Span and Travel Span fields, the first one to be met
will be used to determine where to place the break. If one span time is 00:00, it
will not be considered when determining where to place the break; in other words,
if you only want to consider travel time when determining when a break should
occur, enter a Travel Span but leave Span at 00:00.
To have waits automatically inserted when the routes are created, sequenced, or
stops are manually moved, check Insert Waits to Make Open Times and Time Windows.
Enter the maximum amount of time the driver can wait to make the open time/time
window in the Maximum Wait Time field. If the driver is paid for the wait, check Paid.
Note: All paid breaks and waits are included in the drivers service time and driver costs
for the route.
Operations Guide
461
Time Window Routing Options
The Time Window page of the Options notebook lets you establish the criteria used when
routes or stops are time windowed. The Options notebook is opened by selecting Options
from the Tools menu in the Routing Editor.
The options selected

on the Time
Windows page are
used when you
choose to time
window routes.
To indicate the importance of meeting time windows versus reducing route costs,
move the slider bar at the top of the page. Enter the maximum amount of time Roadnet
should spend analyzing each route in the Timeout after field.
To allow Roadnet to adjust the start time to meet time windows, check Adjust Start
Times and enter the maximum amount it can be adjusted before (Early) and after (Late)
the current start time, and the increments to adjust it in.
To allow Roadnet to add wait times at a stop to meet the open time or time window,
check the appropriate box(es). Enter the maximum amount of time the driver can wait,
and check the Paid box if the driver is paid for the wait.
Split Orders Routing Options
The Split Orders page of the Options notebook lets you specify the criteria used to identify
the orders when split orders are manually created in the Editor. Choose the desired
method to name the split; you can select the prefix to be the location ID, the original order
number, or a customized prefix that you specify. The Options notebook is opened by
selecting Options from the Tools menu in the Routing Editor.
462

Important: Make sure that enough space is allocated in the order file for the order
number to be sent to the host with Send Orders.
Each order, including a split order, must have a unique order number. You can choose
whether the order numbers for each location must be unique (different locations can have
identical order numbers) or each order number in the routing session must be unique.
If you want to designate a selector to indicate an order is a split order, such as S, enter the
selector in the Upload Selector field.
Drag/Drop Routing Options
The Drag/Drop page of the Options notebook lets you specify the default actions that
occur when you drag stops to an active or standard route while holding down the left
mouse button, or while holding down the left mouse button and the [Ctrl] key. If you hold
down the right mouse button while dragging, you will get the complete menu so you can
choose the desired option. The Options notebook is opened by selecting Options from the
Tools menu in the Routing Editor.
To choose the actions that will occur when dragging to an active route, click on the
appropriate arrow in the Dragging Stops to Routes area to open a list of actions. Click on
an action to select it. The choices are:
Insert by best cost
Insert by best distance
Insert by best time
Insert by best TW
Insert first
Insert last
Insert near closest location
To choose the actions that will occur when dragging stops to a standard route, click
on the appropriate arrow in the Dragging Stops to Std. Routes area to open a list of actions.
Click on an action to select it. The choices are:
Copy/Move first
Copy/Move near closest location
Copy/Move by best distance
Copy/Move last
Auto Assign Route IDs in the Routing Editor
When you build your final routes in the Routing Editor, you may want sequential IDs
assigned to the routes. You can choose to have these IDs automatically assigned, as well
as the prefix that will start each ID and the number range that will be used. Once the
highest number is reached, the Editor starts at the lowest number you specify. The
Operations Guide
463
maximum length of the prefix plus the ID number is 15 characters. The Options notebook
is opened by selecting Options from the Tools menu in the Routing Editor.
When outlining the

rules used to assign IDs
to the routes, you can
specify the highest
number to use, and
what number you want
to restart the
numbering at. Make
sure you allot enough
number to cover all the
possible routes in the
session so you do not
have duplicate IDs.
To have sequential IDs assigned when you build routes, check Auto assign sequential
route IDs when building routes and enter the guidelines in the correct fields.
...prefix ofthe prefix that will start each ID (ex. a city name).
...an ID ofthe next number that will be assigned as an ID.
...Reset the ID tothe number you want to restart numbering at when the maximum
value is reached.
...exceeds a Maximum value ofthe highest number you want assigned as an ID. When
this number is reached, the IDs will start with the value specified in Reset the ID to.
Compartments Routing Options
The Compartments page of the Routing Options notebook allows you to specify whether
or not the editor should consider capacity sizes when determining what SKUs belong in
which compartments.
To have the editor automatically consider the capacity sizes when determining which
SKUs belong in which compartments, check Enable Compartments. In the Consider
Capacity section, check the size alias(es) for the sizes you want the compartment capacity
checked for.
464

Note: In order for this to work correctly, you must select the same size alias in the
Consider Capacity section as was selected on the Restrictions page of the Routing
Pass Options notebook.
Compute Pallet Options
The Compute Pallets page of the Routing Options notebook lets you define how Roadnet
knows which orders should have the pallet counts computed, and the guidelines Roadnet
should use when computing the pallet counts for those orders. This information is useful
if you are using FleetLoader to build the pallets for your bulk trucks. By having Roadnet
use the same FleetLoader pass and rules that you will use when loading the truck in
FleetLoader, Roadnet is more accurately able to compute the proper number of pallets for
the equipment and create the route accordingly. The Editor Options notebook is opened
by clicking on the Tools menu and choosing Options.
Hint: Before starting this process, make sure you have the FleetLoader pass and Pallet
Loading Method set up.
To have Roadnet compute the pallet count for marked orders, check Enable Compute
Pallets and complete the remaining fields on the page.
Click the FleetLoader Pass arrow and select the pass you will use in FleetLoader to load
your bulk trucks.
Click the Pallet Loading Method arrow and select the method that will be used in
FleetLoader to build the pallets.
Operations Guide
465
In the Destination Size for Pallet Count area, select the size where the computed number
of pallets will be stored. Normally, this is Size 3.
The new Compute Pallets page lets you set the options Roadnet will use when
determining the number of pallets an order needs.
In the Compute Pallets area, specify which orders should have the pallet count computed.
To select specific orders, click Stops That Have An Order With and select the
options you want to use:
Selectorscheck if the orders are marked by a selector that was imported with
the order or added to the order in Maintenance, such as B for Bulk. List the
selectors in the entry field. If you are entering multiple selectors in the field, do
not put commas or spaces between the selectors; for instance if you wanted to use
B and D as the selectors, enter BD in the field.
Upload Selectorscheck if the orders are marked by an upload selector that was
added to the order in the Routing Editor. List the selectors in the entry field. If you
are entering multiple upload selectors in the field, do not put commas or spaces
between the selectors; for instance if you wanted to use B and D as the selectors,
enter BD in the field.
Force Bulk Service Timecheck if the order is marked to use bulk service time.
To have the pallets computed for all stops, select All Stops.
466

Note: If one order on a stop has the pallets computed, all orders for that stop will have
the pallets computed.
Compact Database Options in the Routing Editor
As you use the Routing Editor to create routes, and especially if you create new sessions,
the database can grow quite large. To help control the size of the database you can specify
to have it compacted when you save and/or exit in the Routing Editor. When the database
is compacted, any items that you deleted are permanently removed from the database.
You can choose to have Roadnet always compact, never compact, or ask you whether or
not to compact, when you save and exit the Routing Editor.
To select the compact option, click on the appropriate arrow to open a list of options, then
click on an option to select it.
Exceptions in the Routing Editor
When routes are created in Roadnet you can place restrictions on the route, such as
equipment capacity and runtimes. If the route exceeds these restrictions, it is called an
exception. You can monitor any exceptions for a route in the Routes window and on the
map.
Similar to routes, stops and standard stops can have exceptions. The Route Exceptions,
Stop Exceptions, and Std. Stop Exceptions pages of the Options notebook allow you to
choose which exceptions you are interested in tracking, the color associated with the
exception, and the order of importance for the exceptions. The order is important for
displaying the exceptions on the map; only the first exception met for each route or stop
is displayed on the map, rather than all exceptions being displayed. Also, if you use the
row coloring feature, the row text for stops and routes will be in the color associated with
the first exception met by that stop or route. All exceptions for a route or stop are indicated
by colored flags in the Exceptions column of the appropriate window; the color of the flag
matches the color chosen on the Exceptions page. All stops with a specific exception can
also be seen in the appropriate window, opened by selecting Exceptions from the List
menu in the Routing Editor. The Exceptions are created in the Options notebook, opened
by selecting Options from the Tools menu in the Routing Editor.
Operations Guide
467
To track an exception, click the box in the Enabled column. A check in the box means
that the item is tracked.
On a map, a route will

be highlighted the color
of the first exception it
meets.
To choose the color for an exception, hold down the [Alt] key and click on the color
chip. Click on the arrow that appears next to the color chip and select the new color from
the palette that opens. Press the [Enter] key to accept the color change.
To change the order of importance for the exceptions, click on the exception to move
and drag it to the desired position in the list. Only the first exception met will be shown
on the map.
The exceptions for each page are explained in the following sections.
Route Exceptions in the Routing Editor
Route exceptions appear when a route exceeds one of the restrictions established in the
routes properties. The Route Exceptions page of the Options notebook lets you choose
the route exceptions you are interested in tracking, the colors associated with the
exceptions, and the order of importance for the exceptions; only the first exception met
will be shown on the map. The Options notebook is opened by selecting Options from the
Tools menu in the Routing Editor.
The route exception options are listed below.
468

Exceeds size 1, 2, 3 capacitythe route contains more product than the equipment can
hold when measured as size 1, 2, or 3.
Exceeds preferred timethe routes total runtime is greater than the preferred runtime.
Exceeds maximum timethe routes total runtime is greater than the maximum
runtime.
Has stop exceptionsone of the stops on the route has an exception.
Exceeds Compartment Capacitythere is a compartment on the route that is filled
beyond its capacity with product. You will only receive this exception if you are using
compartment routing.
No Matching Compartment Typethere is a line item on the route that is of a product
type that is not allowed to be loaded into any of the compartments present on the truck.
You will only receive this exception if you are using compartment routing.
Duty Period Violationthe routes driver will violate a duty period rule by running the
route. Duty period rules regulate the length of time that drivers can work and are used to
help your organization comply with safety and labor laws. To receive this exception, you
must have duty period rules enabled on the Duty Period Monitor page of the Maintenance
options notebook.
Time of Day Restriction Violationa stop on the route is in a restricted area at a
restricted time. The route displays on the map showing a dotted path between stops if the
path violates the time of day travel restriction.
Has Mid-Route Sourcing Exceptiona Mid-Route Sourcing rule is broken, such as
there is no source for a delivery. Running Adjust Mid-Route Sourcing may fix the
problem.
Stop Exceptions in the Routing Editor
Stops can have exceptions that are associated with the location or with the stops
placement on a route. The Stops Exceptions page of the Options notebook lets you choose
the stop exceptions you are interested in tracking, the colors associated with the
exceptions, and the order of importance for the exceptions.
Prioritythe locations priority as established in the Locations notebook is greater than
or equal to the threshold set in the Priority threshold. For instance, if the Priority
Threshold is set to 8, all locations with a priority of 8 or 9 would be flagged.
Geocodethe method used to geocode the location is less than the method selected in the
Geocode Threshold. For instance, if Postal Detail is selected as the threshold, all locations
with a geocode method of Cross Street and Postal Area will be flagged.
Arrive before open timewhen the stop is routed, the driver is scheduled to arrive
before the stops established open time.
Arrive after close timewhen the stop is routed, the driver is scheduled to arrive after
the stops established closed time.
Operations Guide
469
Work past close timewhen the stop is routed, the driver is scheduled to arrive at the
stop before the close time, but the service time indicates that the driver will not finish until
after the stops close time.
Missed Time Windowwhen the stop is routed, the driver is scheduled to make the
delivery outside the stops time window.
Time Window Factorthe locations time window factor established in the Locations
notebook is greater than or equal to the Time Window Factor threshold selected below.
For instance, if the Time Window Factor threshold is 4, all locations with a factor of 4 or
5 would be flagged.
Offday deliverythe location has a delivery scheduled on a day not selected as a valid
delivery day in the Location notebook.
Equipmentyou can specify a list of equipment available for delivery at each location
in the Location notebook. If a delivery is attempted using a piece of equipment not in the
Available list for that location, then the stop will be flagged.
Date Rangethe stop contains an order that is being delivered before its begin date or
after its end date.
Skill Setthe stop contains an order that contains an order activity not included in the
drivers skill set.
Preferred Routethe stop contains an order that is not on its preferred route.
Building Delivery Sequencethe stop is out of order on the route according to its
assigned building delivery sequence number.
Reversed Order Pairboth the pickup and delivery are placed on the same route, but
the delivery occurs before the pickup.
Separated Order Pairthe pickup and delivery are not on the same route.
Time of Day Restriction Violationthe stop is forcing restricted equipment to travel in
a restricted area during a restricted time.
Dependency Sequence Violationthe dependencies for orders on the stop are out of
sequence. An order with a lower priority (4) is fulfilled before one with a higher priority
(1).
Invalid Mid-Route Sourcea storage facility or waste station has been assigned that
does not accept or distribute an SKU that is on an order for the stop.
Std. Stop Exceptions in the Routing Editor
Standard stops can have exceptions that are associated with the location, such as the
geocode or the priority. The Std. Stops Exceptions page of the Options notebook lets you
choose the standard stop exceptions you are interested in tracking, the colors associated
with the exceptions, and the order of importance for the exceptions.
470


Order Locking Routing Options
You can prevent orders from being removed from their current route by locking them. The
Order Locking page of the Routing Options notebook allows you to restrict locked orders
and sent orders from being manually moved to a different route. There is also an option
that lets you specify how Roadnet will assign the lock status of orders that have been
moved to a different route.
When Removing a Locked Order from its Routedetermines how Roadnet will
respond when you attempt to manually remove locked orders from their route. Click on
the arrow and choose an option.
Proceed without warningyou can freely unassign locked orders and move
locked orders to a different route.
Deny and abortyou cannot remove any locked orders from their route.
Ask the user to confirmRoadnet requires that you give confirmation when
removing locked orders from their route. If you attempt to move or unassign a
locked order, a window will appear stating that the order is locked. You must click
[Yes] or [No] to confirm whether or not you wish to proceed with the action.
After Orders are Moved to Another Routedetermines how Roadnet will assign the
lock status of orders that have been moved to a different route. Click on the arrow and
choose an option.
Lock all moved orders to new routeany order that is moved to a different
route will be automatically locked to its new route. All orders will be locked to
their new route regardless of their previous lock status.
Unlock all moved ordersany order that is moved to a different route will be
automatically put in unlocked status. All orders will be put in unlocked status
regardless of their previous lock status.
Lock previously locked orders to new routewhen moved to a new route,
orders that were locked to their previous route will be automatically locked to their
new route. Orders that were not locked will remain unlocked.
Ask the user what to dowhen moving orders to a different route, Roadnet will
ask you what lock status to assign to the orders that are being moved. You have
Operations Guide
471
three choices: Lock all orders to the new route, Lock only previously locked
orders to the new route, or Unlock all orders.
When Removing a Sent Order from its Routedetermines how Roadnet will respond
when you attempt to manually remove sent orders from their route. Click on the arrow
and choose an option.
Proceed without warningyou can freely unassign sent orders and move sent
orders to a different route.
Deny and abortyou cannot remove any sent orders from their route.
Ask the user to confirmRoadnet requires that you give confirmation when
removing sent orders from their route. If you attempt to move or unassign a sent
order, a window will appear stating that the order is sent. You must click [Yes] or
[No] to confirm whether or not you wish to proceed with the action.
Order Sourcing
If you are using order sourcing to ensure that two orders with the same order number but
different order types (one a pickup and the other a delivery) are considered together, you
can choose the rules Roadnet should follow when an order pair is reversed or broken by
moves made in the Routing Editor. Remember, the two orders are only considered a pair
if they are both in the same routing session.
Note: When Mid-Route Sourcing is enabled, use the Order Sourcing Options notebook
to define the rules for what happens when an order pair is broken.
The Order Sourcing page will not be visible unless order sourcing or mid-route
sourcing is enabled in the Maintenance Options notebook.
Click on the arrow and choose the appropriate result for each option.
When a manual operation will result in reversing the order pair(s)determines how
Roadnet will react when a move will result in the delivery occurring before the pickup on
the route. The choices are:
Ask the user to confirma message box appears, asking the user to confirm the
move before putting the delivery before the pickup.
Deny and abortthe user will not be allowed to make the move.
Proceed without warningthe move will occur without warning the user the
delivery now occurs before the pickup.
When a manual operation will separate an order pairdetermines how Roadnet will
react when a move will result in the paired orders being on separate routes. The choices
are:
472

Ask the user to confirma message box appears, asking the user to confirm the
move before splitting the order pair.
Deny and abortthe user will not be allowed to separate the order pair.
Proceed without warningthe move will occur without warning the user the
pickup and delivery have been placed on separate routes. If this option is selected,
you can check Always move both orders when part of an order pair is moved to
assure that the delivery and pickup remain on the same route.
Operations Guide
473
Working with Standard Routes

Used with: Roadnet
Roadnet allows you to create standard routes, or routes with set stops that run in a set
order. Standard routes require less maintenance than dynamic routes and are helpful if
your orders do not change from day to day, but they may not be as efficient as dynamic
routes. Roadnet lets you use standard routes as the basis for dynamic routes, or you can
route just using your standard routes. When you create your daily routes, you can choose
to have any orders on a standard stop routed on the standard route. Once standard routes
are created, they can be evaluated, re-sequenced, and routed using all the features of the
Routing Editor.
Note: When you open a standard route set, a standard route, or a standard route stop, you
may receive a warning stating that another user is working with that set, route, or
stop. You can open the set, route, stop for viewing purposes only. Once the other
user has saved and closed out of the set, route, or stop, you will then need to
refresh the window (either click the Refresh icon or close and re-open the
window) before making any changes.
To create standard routes, you must complete the following steps:
Create the standard route sets
Create the standard routes
Add the standard routes to standard route sets
Add stops to the standard routes
Creating Standard Route Sets
Standard routes are grouped in sets. Typically, there would be a route set for each day you
deliver through the week, with all the routes for a given day on that days set. For instance,
you might have a Monday set that contains all the standard routes for Monday. You must
add the standard route set before you can add the standard routes to the set.
When you create the standard route sets, you can give the sets a description. If you make
the description something that is easily distinguishable and recognizable, such as the day
of the week the routes are for, it will be easier to choose the proper set when you are
creating routes.
Step 2: Click on the Standard Routes menu and select Sets. The Standard Route Sets
window opens.
Step 3: Click on the Add icon or press [Insert]. The Add Standard Route Sets window
opens.
474

entry.
Step 4: Enter the ID for the standard route set. This field must be completed.
When adding a standard

route set, you can specify
the days the set contains
routes for.
Step 5: Enter the Description for the set.

Step 6: In the Days area, check the days for which the set will contain routes.
Step 7: Click the Save icon, or press [Ctrl]+[S] to save the set.
Step 8: Repeat Steps 2 - 7 to add any other standard route sets.
Step 9: When you are finished adding standard route sets, click the Close box to close
the Add Standard Route Sets window.
Routing Editor Standard Routes Sets Add ([Insert]) Save ([Ctrl]+[S])
Once standard route sets have been added, they can be changed or deleted as necessary.
You can also add standard routes to the standard route sets.
To edit a standard route set, right-click on the set and select Edit from the menu that
pops up. The Edit Standard Route Sets window opens.
To delete a standard route set, right-click on the set and select Delete from the menu
that pops up.
Creating Standard Routes
When you create a standard route you can specify the driver, runtime, equipment, depot
and other attributes of the route. When a daily route is created using the standard route as
a base, these attributes will be assigned to the daily route.
Step 2: Click on the Standard Routes menu and select Routes. The Standard Routes
window opens, listing all existing standard routes.
Step 3: Click the Add icon, or press [Insert]. The Add Standard Route window opens,
with the Attributes page visible.
Operations Guide
475
Step 4: Enter the ID and Description for the route. The ID must be completed.
Any resources you assign to a

standard route will overrule
resources assigned to an
individual order or stop on
the route when daily routes
are created.
Step 5: To choose the drivers for the route, click on the appropriate arrow to open a
Lookup window; double-click on an option to select it, or click on the option then
on the Process icon.
Step 6: To choose the depot or model for the route, click on the arrow to open a list of
options; click on an option to select it.
Step 7: To indicate the routes final destination, click on the Destination arrow and
select Origin, Last Stop, or a specific depot. If Last Stop is selected, the cost,
distance, and times will not consider any time needed to return to the depot.
Step 8: If the driver has a helper, check the Helper box. If the driver and helper split the
pay equally check the Team Split box. If you want to communicate to warehouse
personnel the importance of loading the route, enter a single character in the
Load Priority field.
Step 9: To specify the preferred runtime or the maximum runtime for the route, enter
the length in the appropriate field. Enter in the format of HH:MM.
Step 10: To specify the start time for the route, enter the time in the Start Time field.
You can enter the time manually, or use arrows to scroll to the correct time. If
entering the time manually, use the arrow keys to move from the hour to minute
field. If using the scroll arrows, click on the correct field (hour to minute) before
476

scrolling. Use a 24-hour clock when entering the time. For example, enter 1:00
PM as 13:00.
Step 11: If the route will have pre- or post-route stops, enter the length of the stops in
the Pre-Rte Time and Post-Rte Time fields. Enter the time in the format HH:MM.
Pre- and post-route stops are time at the routes origin and destination that the
driver is paid for; this time can be used to check the load, have meetings, etc.
Step 12: Click on the Starting Quantity arrow and select either As Needed, Empty, or
Full as your route's default starting quantity. For example, if a fuel truck is
typically refilled at the last stop, then enter Full. If a fuel truck is typically refilled
at the first stop, then enter Empty. Finally, if a fuel truck starts the route with just
enough fuel for that route, then enter As Needed.
Note: If you are using Mid-Route Sourcing, do not choose Full as a Starting Quantity. If
you do, the route will use As Needed.
Step 13: Enter the load priority. This information is not used by Roadnet, but it can be
uploaded with the route and used by warehouse personnel to determine which
route should be loaded first.
Step 14: To specify the day(s) for the route, click on the appropriate day in the Days
area.
Note: If you are using overrides for your time windows, the time window displayed will
be affected by the day selected.
Step 15: To assign equipment to the route, click on the Equipment tab to open the
Equipment page.
You can assign

individual pieces of
equipment to the
standard route, or a
type of equipment.
Operations Guide
477
To assign a specific piece(s) of equipment to the route, click on the equipment

in the Available list and drag it to the Assigned list.
To assign a type of equipment to the route, click on the Equipment Type arrow
to open the Lookup Equipment Type window. Double-click on a type to select
it, or click on the type and then click on the Process icon.
Note: If both an equipment type and piece of equipment is selected, the piece of
equipment will be assigned to the route.
Step 16: When all information has been entered, click on the Save icon or press
[Ctrl]+[S] to save the standard route.
Step 17: Continue adding standard routes as necessary. When all standard routes have
been added, click the Close box to close the Add Standard Route window.
Standard Routes Routes Add ([Insert]) Save ([Ctrl]+[S])
Once standard routes have been added, they can be added to the standard route sets. You
can also modify or delete standard routes as necessary.
To change a standard route, right-click on the route and select Properties from the menu
that pops up. The Edit Standard Routes window opens. Make the necessary changes and
click the Save icon.
To delete a standard route, right-click on the route in the Standard Routes window and
select Delete from the menu that pops up, or click on the standard route and then on the
Delete icon. Click [Yes] to confirm the deletion.
Creating Standard Routes and Standard Route Overrides from Existing Routes
You can create a new standard route from an existing route, replace an existing standard
route, or create an override for a standard route with the same route ID. Once a route has
been created as a standard route or a standard route override, it can be added to a set and
used as a basis for future routing. Both standard routes and standard route overrides can
be used when creating daily routes.
with.
Step 2: Right-click on the route(s), drag it to the Standard Routes window, and select
the appropriate menu option before dropping the route. You can choose to Create
Std. Route or Create override.
If you choose Create override, a standard route override will be created.
If you choose Create Std. Route, the Create Standard Routes window opens.
Choose whether you want to Replace the existing standard route with the daily
478

route or Merge the daily route with the standard route. Replace will make a
duplicate copy of the daily route as the standard route. Merge will
If you want to update the standard routes driver, equipment, and other properties
with the daily routes properties, check Overwrite Standard Route Properties with
Daily Route Properties
If you want the breaks and layovers on the daily route to be part of the standard
route, check Include Breaks and/or Layovers. If you are having Roadnet add
breaks to your routes when daily routes are created, you should not choose this
option.
Adding Standard Routes to a Standard Route Set
Once you have created your standard routes, you can add them to the standard route sets.
A standard route can be placed on more than one standard route set. For instance, if you
have a set for Monday and another set for Wednesday, but the same route is run on both
days, you can add the route to both sets. Likewise, if a route is no longer run on that day,
you can remove it from the set.
Step 1: In the Routing Editor, click on the Standard Routes menu and select Sets. The
Standard Route Sets window opens.
Step 2: Double-click on the set you want to add standard routes to. The Routes window
for the set opens.
Step 3: Click on the Edit This List icon. The Standard Routes in Set window opens.
Step 4: The Standard Routes in Set window has two lists: one list of all available
standard routes and one list of the standard routes in the set.
To add a standard route to the set, drag it from the Available Routes list to the
Routes in Set list. To select multiple routes, [Ctrl]+click the routes and drag them
to the Routes in Set list; to select routes listed sequentially, click the first route,
then hold down the [Shift] key and select the last route.
To remove a standard route from the set, drag it from the Routes in Set list to
the Available Routes list.
Step 5: When all routes have been added to the set, click the Save icon or press
[Ctrl]+[S].
Notes: You can also add standard routes to a set by dragging them from the Standard
Routes window to the set in the Standard Route Sets window. If you right-click
and drag the routes, you can choose whether to add the standard route to the set
(Add Route(s)), combine it with the standard route it is dropped on (Combine), or
combine it with another standard route and then resequence both routes to obtain
the shortest route (Combine and Sequence).
You can remove standard routes from the set by selecting the route and clicking
the Delete icon on the Routes for Set window.
Routing Editor Standard Routes Sets Routes window Edit List icon Save
([Ctrl]+[S])
Operations Guide
479
Adding Stops to a Standard Route
There are two methods you can use to add stops to a standard route. If you have a list of
stops to place on the route, and the preferred order for the stops, you can use the Add Stops
window to quickly build your routes. If, on the other hand, you are not sure of the order
of the stops, or want to quickly add a few stops to an existing standard route, you can drag
the stop to a route and choose how the stop is routed.
You can add stops to a selected standard route, or you can add a single stop to a group of
standard routes. The same stop can appear on multiple standard routes.
Note: If you are not sure which route to add the stop to, right-click on the stop in the
Stops list and select Suggest Route from the menu that pops up. See Letting
Roadnet Determine the Best Route in Routing Unassigned Stops for more
information.
Using the Add Stops Window
Once you have added your standard routes, there are two methods you can use to add stops
to the routes. If you have a list of stops that need to be added to standard routes, and you
already know the order the stops should be in, you can use the Add Stops window to
quickly build your standard routes. Once the stops have been added, you can use the
sequence, flip, and other features to have Roadnet organize the stops. On the other hand,
if you want Roadnet to determine where to place the stops, you can drag the stops to the
route and choose how you want them placed in comparison to the existing stops. You
must be in the Routing Editor to perform this procedure.
Step 1: Click on the Standard Routes menu and select Add Stops ([Ctrl]+[Shift]+[A]).
OR
Right-click on a route in the Standard Routes window and select Add Stops from
OR
Click on the Standard Routes window, then click the Add Stops icon on the Routes
toolbar.
The Add Stops window opens.
Step 2: The Add Stops window lets you add stops to the route using either a Speed
Mode or Lookup Mode. Click on a tab to choose the desired mode.
To use the Speed Mode, select the type for the location and enter the ID in the
Location ID field. Enter the ID for the standard route in the Std Route ID field;
once the standard route ID has been entered all stops currently on the route appear
in the list at the bottom of the window. Choose whether the stop should be first,
last, or after a specified stop on the route and click the [Insert] button.
To use the Lookup Mode, select the route in the Add to Standard Route list at the
top of the window. In the Locations area, click on the location to add to the route,
and in the Insert area, select whether the location should be added as the first, last,
480

or after an existing stop. You can view the existing stops for the route in the list at
the bottom of the window. Click the [Insert] button.
When adding stops to your

standard routes, you can
choose to use either the
Speed Mode or the Lookup
Mode. In either case, you
can specify where in the
route the stop should be.
Step 3: Continue adding stops to routes as needed. Click the Close box when all stops
have been added.
Routing Editor Standard Routes Add Stops ([Ctrl]+[Shift]+[A]) [Insert]
Hint: If routes have changed, and you want to see the best route for a stop, right-click
on the stop and select Suggest Route. See Letting Roadnet Determine the Best
Route in Routing Unassigned Stops for more information.
Notes: To remove a stop(s) from a standard route, right-click on the stop in the Stops
window and select Unassign from the menu that pops up.
To add a break or layover to the standard route, in the Stops list right-click on
the stop you want to precede the break/layover and select Assign, then Break,
from the menu that pops up. See Adding Breaks and Layovers to Standard Routes
To add a depot during the route, in the Stops list right-click on the stop you want
to precede the depot and select Assign, then Insert Depot, from the menu that pops
up. See Adding Mid-Route Depots to Standard Routes for more information.
To remove duplicate locations from a standard route, right-click on the route
in the Standard Routes window and select Remove Duplicate Locations from the
menu that pops up.
Operations Guide
481
To remove assigned locations from the Standard Unassigneds window, click

on the Remove Assigned Locations icon. The assigned locations will be removed
from the Standard Unassigneds window.
Dragging the Stops to a Route
Once you have added your standard routes, there are two methods you can use to add stops
to the routes. If you have a list of stops that need to be added to standard routes, and you
already know the order the stops should be in, you can use the Add Stops window to
quickly build your standard routes. However, if If you only need to add a few stops to a
standard route, or you want Roadnet to determine the best placement for the stops without
resequencing the other stops, you can drag the stops from the Unassigned window to the
Standard Routes window. When dragging the stops you can hold down the left or right
mouse button. If you hold down the left mouse button, the option you selected on the
Drag/Drop page of the Options notebook will occur; if you hold down the right mouse
button while dragging, you will get a menu to choose from. You must be in the Routing
Editor to perform this procedure.
Step 1: Make sure the Standard Routes and Standard Unassigneds windows are open and
visible.
Step 2: In the Standard Unassigneds window, select the stops you want to add to the
standard route.
Step 3: Right-click on one of the selected stops and, holding down the right mouse
button, drag the stops to the desired standard route. Choose the desired option
from the menu that appears. The options are to Move/Copy (Insert) First, Move/
Copy (Insert) near closest location, Move/Copy (Insert) by best distance, and
Move/Copy (Insert) Last.
Note: If the action you want to perform is the one selected on the Drag/Drop page of the
Options notebook, you can hold down the left mouse button, or [Ctrl] and the left
mouse button while dragging; the selected option will be performed
automatically.
Step 4: Continue moving unassigned stops to other routes as necessary.
Note: To add a break or layover to the standard route, right-click on the stop you
want to precede the break/layover and select Assign, then Break from the menu
that pops up. See Adding Breaks and Layovers to Standard Routes for more
information.
To add a depot during the course of the route, right-click on the stop you want
to precede the depot and select Assign, then Insert Depot from the menu that pops
up. See Adding Mid-Route Depots to Standard Routes for more information.
Removing Inactive Stops from Standard Routes
A standard route is a collection of stops that are sequenced. On any given day, those stops
on the route with orders are delivered in the predetermined order.
482

Over time, your customers may change and your standard routes may become cluttered
with stops that you no longer make deliveries to. Keeping these inactive stops on your
standard routes can result in slow routing times, so its a good idea to maintain your
standard routes by removing these stops. To select the inactive stops and remove them
from the standard routes, follow these steps.
Step 1: From the Standard Routes menu, select Remove Inactive Locations. The Inactive
Locations window opens.
Step 2: Enter the Inactivity Date. Any location which has not been serviced on or
before this date is considered inactive. You can enter the date manually or click
on the arrow to open a calendar. To change the month either use the arrows on the
top of the calendar to scroll through the months or click on the month and select
from the menu that pops up. To change the year, click on the year and use the
small arrows to scroll to the correct year. Click on a date to select it.
All locations that have been inactive since the date entered in the Inactive Date field
appear in the Inactive Locations list.
Step 3: Click the Refresh icon. Any locations without orders in sessions dated on or
before the Inactivity Date date will appear in the list.
Step 4: Click on a location to select it. To select multiple locations, hold down the
[Ctrl] key as you click; to select all the locations, right click on a column header,
and choose Select All Rows.
Hint: You can sort on any of the fields by clicking on the column header.
Step 5: When you have finished selecting the locations you want to remove from the
standard routes, click [Remove]. The stops associated with these locations will be
removed from the standard routes.
Routing Editor Standard Routes Remove Inactive LocationsInactivity DateRefresh
Select Location(s) [Remove]
Operations Guide
483
Adding Breaks and Layovers to Standard Routes
If you know that your driver will always take a break or visit another depot after a specific
stop, you can add the breaks directly to the standard route. When the daily routes are
created from the standard routes, the break/mid-route depot will be added to the daily
route, even if the stop preceding it is not on the route. In other words, if a break is
scheduled after visiting The ABC Shop, the break will be placed on the route even if The
ABC Shop does not place an order on that day.
Hint: If you are manually inserting breaks on the standard routes, make sure Insert
Breaks Automatically in the Options notebook is not selected. If Insert Breaks
Automatically is selected, any breaks placed on the standard routes will be deleted
and the automatic breaks used instead when the daily routes are created.
Step 1: Open the Assign Break window.
From a standard stop listright-click on the stop you want to precede the break
or layover and select Assign, then Break/Layover from the menu that pops up. The
Assign Break/Layover window opens.
From the Add Stops windowright-click on the stop you want to precede the
break or layover and select Assign, then Break/Layover, from the menu that pops
up. The Assign Break/Layover window opens.
Step 2: In the Type area, select whether you are adding a Break or Layover.
If the driver is paid for the break or layover check the

Paid box.
Step 3: In the Time field, enter the length of the break/layover in the format HH:MM. If
the driver is paid for the break/layover, check the Paid box.
Note: If the driver is paid for the break/layover, the break/layover is included when the
daily routes time is calculated.
Step 4: Click the [OK] button. The break is added to the standard route.
Note: To change an existing break/layover, right-click on the break/layover and select
Properties from the menu that pops up. The Assign Break/Layover window opens;
make the necessary changes and click the [OK] button. To delete a break/layover
from the route, right-click on the break/layover and select Remove from the menu
that pops up.
Routing Editor Std. Routes/Add Stops window Assign Break/Layover [OK]
484

Adding Mid-Route Depots to Standard Routes
If your drivers need to visit a depot during the course of the route, either to pick up
additional product to be delivered or to drop off product, you can add these mid-route
depots to your standard routes. When daily routes are created from the standard route, the
mid-route depots will be included on the daily route, even if the stops directly surrounding
it on the standard route do not have orders for that day.
Notes: If Create Reload as One Route is not selected in the Options notebook, or you
manually unlink the routes, each mid-route depot will start a new daily route.
These routes will use the standard routes ID, followed by a number indicating
how many segments were created from that route. For instance, if the standard
route has two mid-route depots and the standard route ID is BALT, the route IDs
would be BALT, BALT01 (the route after the first depot) and BALT02 (the route
after the second depot).
Step 1: Open the Insert Depot window.
From a standard stop listright-click on the stop you want to precede the break
or layover and select Assign, then Insert Depot from the menu that pops up. The
Insert Depot window opens.
From the Add Stops windowright-click on the stop you want to precede the
break or layover and select Assign, then Insert Depot, from the menu that pops up.
The Insert Depot window opens.
Step 2: Select whether you want the depot to occur before or after the stop you click on.
You can have a mid-route depot use the

service time established in the Location
notebook or specify a service time.
Step 3: In the Service Time area, specify the amount of time that will be needed at the
depot. Click Specify Time to enter the time, or Use Depot Service Time to use the
service time specified in the Location notebook.
Step 4: To specify whether the driver is dropping off or picking up product, click the
Action Taken arrow and choose the proper action. The options are explained
below:
Operations Guide
485
Fill to Capacityequipment is completely refilled at the depot.

Emptyequipment empties entire load at the depot.
Fill As Neededequipment is only filled with product needed to complete the
route.
Noneequipment does not load or unload.
Step 5: Click the [OK] button. The depot is added to the route.
Note: To change an existing depot, right-click on the depot and select Properties from
the menu that pops up. The Insert Depot window opens; make the necessary
changes and click the [OK] button. To delete a depot from the route, right-click
on the depot and select Remove from the menu that pops up.
Routing Editor Std. Routes/Add Stops window Assign Insert Depot [OK]
Sequencing Standard Routes
Once the stops have been added to the standard route, you can have Roadnet sequence the
stops based on your selections. Simply right-click on the route and select Actions from
the menu that pops up, or click the appropriate icon on the Routes toolbar. The options
are sequence, flip, line sequence, and combine.
Note: When sequencing linked routes, the sequence works separately on each trip on the
route. The mid-route depot(s) will remain where it is and the sequencing action is
only performed on each trip.
Any breaks on the route will remain with the stop sequence they were originally
associated with. For instance, if there is a break after stop 2, a break will be
inserted after stop 2 during the sequence, even if stop 2 is now a different location.
Sequencetakes the list of stops and calculates the travel time between each stop and the
depot. The stops are placed and sequenced on the route in the way that produces the least
distance.
Flipreverses the current order of stops on the route.
Line Sequencere-sequences the routes based on the travel time between stops.
Typically, if End Point is selected, the two stops that are the greatest distance from each
other are the first and last stops on the route; if Midpoint is selected the stop that is furthest
from all other stops is selected.
Combinecombines the routes into one. You can choose to have the stops resequenced
(Sequence) or not (No Resequence). If the stops are not resequenced, the route that you
right-click on to access the menu is placed first, then the remaining routes are combined
in the order selected.
Routing Editor Std. Routes window Actions Sequence ([Ctrl]+[Q])/Flip ([Ctrl]+[F])/
Line Sequence Midpoint ([Ctrl]+[M])/Line Sequence Endpoint ([Ctrl]+[Z])/Combine No
Resequence ([Ctrl]+[Shift]+[N])/ Combine Resequence ([Ctrl]+[Shift]+[R])
486

Saving the Standard Routes in the Routing Editor
Once the standard route sets, standard routes, or standard route stops are created, at any
point during the editing and evaluation process you can save them as they exist, so that
you do not lose the current status when other changes are made.
When you save a standard route set, you are saving all the necessary information for the
set, including the routes, stops, and orders, plus information on the equipment, drivers,
and locations that are part of the route. You must be in the Routing Editor to perform this
procedure.
To save the standard route information:
Click the File menu and select Save Standard Route.
Routing Editor File Save Standard Route
Operations Guide
487
Creating Daily Routes

Used with: Roadnet
Once the orders have been entered into the Roadnet Transportation Suite, you can route
them in the Routing Editor. You can choose to route using your standard routes, let
Roadnet create dynamic routes using parameters you outline, or create a combination of
the two. Before creating routes for the first time, or to change the parameters used to
create the routes, you need to establish the parameters in the Routing Pass Options
notebook.
Step 1: Click the Routing icon to open the Routing Editor. The Editor opens with the
Routing Sessions window visible. Double-click on the desired session to work
with.
Step 2: To route all orders, click on the Tools menu, then Route All Available Orders
or click the Route All Available Orders icon on the Routes toolbar. The Process
window opens.
Routing Editor Tools Route ALL Available Orders ([Ctrl]+[R])
To route selected orders, click on the List menu and select Orders. The Orders
window opens, listing all orders. [Ctrl]+click on each order that you want to route,
then right-click on an order and select Create Routes from the menu that pops up.
The Process window opens.
Routing Editor List Orders Create Routes
To route unassigned orders, click on the List menu and select Unassigneds. The
Unassigneds window opens, listing all unassigned orders. [Ctrl]+click on each
order that you want to route, then right-click and select Create Routes from the
menu that pops up. The Process window appears.
Routing Editor List Unassigneds Create Routes
Step 3: Select the pass(es) to route. To select multiple passes, hold down the [Ctrl] key
and click the pass names. The passes will be run in the order listed in the window.
To have multiple passes run and the lowest cost routing solution chosen from the
selected passes, check Compare Selected Passes. If this option is not selected, the
passes will be run consecutively, with each pass using the orders remaining from
the previous pass.
Hint: Compare Selected Passes lets you easily try various routing options and have
Roadnet choose the least expensive alternative. For instance, you could have one
routing pass that has an 8 hour maximum runtime and another that has a 10 hour
maximum runtime, and Roadnet would automatically choose the least expensive
alternative for your routes.
Note: To set up the criteria for the pass, click the [Options] button to open the Routing
Pass Options notebook. See Routing Pass Options Roadnet Transportation Suite
for more information. If you were not granted permission to change Routing Pass
Options, you will not be able to open the Routing Pass Options notebook.
488

Step 4: To display the progress indicator while routing, check the Show Progress
Indicator box. Click the [Start] button.
Note: If duplicate route IDs are being assigned to the routes, the Duplicate Route ID
window opens, with options to resolve the duplicates. Choose the desired option,
and check Apply to all to have the option apply to all duplicate route IDs
encountered during this route creation process.
Once the routes have been created, you can use the features of the Routing Editor to
evaluate the routes and change them as needed. See Evaluating Routes for more
information.
Operations Guide
489
Using the Routing Pass Options Notebook

Used with: Roadnet
The Routing Pass Options notebook is where you select the options that will be
considered when your routes are created. The pages displayed in the Routing Options
notebook can change, depending on the options being worked with. You can work with
general information, the filters for the stops being selected, standard routes, and dynamic
routes. In general, click on the icon at the top of the notebook to open the pages dealing
with those options, then select the pass(es) that will be run from the list at the bottom of
the notebook. You can also add or remove passes from the notebook.
When setting up the options in the Routing Pass Options notebook, you are establishing
the parameters that will be used for an individual pass. By creating separate passes, you
can allow different types of orders to be routed in different ways. For instance, all orders
being delivered to large grocery stores could be routed using standard routes, while orders
for smaller stores could be routed dynamically. This would involve creating one pass for
standard routes and one for dynamic routes.
The Routing Pass Options notebook lets you create multiple routing passes that
each have different criteria to use when creating routes.
Creating Routing Passes
For each different set of routing options you want to use, you need to create a pass. The
options you select in the Routing Pass Options notebook are associated with the pass
highlighted at the bottom of the window, and when you create routes, the options for the
highlighted pass will be used.
Step 1: Click the Routing icon to open the Routing Editor. The Editor opens with the
with.
490

Step 2: Click on the Tools menu, then Route All Available Orders. The Route Creation
Process window opens.
Routing Editor Tools Route ALL Available Orders
Step 3: On the General page, click the [Add] button. A pass named New Pass is added
to the list of passes at the bottom of the window.
Step 4: Complete the options for the pass, making sure the pass name is highlighted in
the Pass Name field. Click the [Save] button to save the pass options. The pass is
now available to choose when you want to create routes.
General Options
Click on the General Options icon to open the General Options pages. There are three
pages of general options: General, Breaks, and Weekly Routing.
Setting the Pass Information
On the General page, enter a name for the pass in the Label field, and select whether you
are doing standard and/or dynamic routing. When the routes are created, Roadnet will
create your daily routes using this choice and the options you select in the notebook.
Setting the Break Information
Click on the Breaks page to have automatically inserted when the routes are created.
Complete the information on the page as outlined below.
Choose how the Routing Editor should calculate when the break(s) should begin:
Span from start of routeuse the routes starting time to determine when the break
should occur.
Span from previous breakuse the ending time of the previous break to determine
when the break should start. If this option is selected, the span time starts when the driver
leaves the depot.
Choose whether or not the break can occur after the span time has expired:
Span is approximatethe break will be placed after a stop as close as possible to the
proper span time, but may occur after the span has expired.
Span is maximumthe break will be placed after a stop as close as possible to the proper
span time, but will not occur after the span has expired. The break may occur before the
span expires.
Enter the spans and duration for each break. In the Span field, enter the length of time
after the start of the route or previous break when the break should start; in the Travel
Span field enter the length of time the driver can drive before a break must occur. Enter
the length of the break in Duration. If the driver is paid for the break, check Paid. Click
the [Update] button to save the break information. To enter another break, click the next
line in the list of breaks.
Operations Guide
491
Notes: If you enter times in both the Span and Travel Span fields, the first one to be met
will be used to determine where to place the break. If one span time is 00:00, it
will not be considered when determining where to place the break; in other words,
if you only want to consider travel time when determining when a break should
occur, enter a Travel Span but leave Span at 00:00.
If the Editor is automatically entering breaks (you chose Insert Breaks
Automatically in the Routing Options notebook), no options will be available on
the Breaks page.
Setting the Weekly Routing Information
Click on the Weekly Routing page to set up the options that will be used if you want to
create routes for more than one day. To have routes for an extended period created, check
Enable. If the first route should start on the same date as the sessions date, check Use
Session Date as Start Date. Otherwise, set the Start Date. Select the days you want to
create routes for in the Delivery Days area. In the # Days to Route, enter the number of
days you want to create routes for; when determining this number do not include days not
marked as Delivery Days.
Note: If you want to ignore the orders Begin and End dates when creating routes, check
Consider Orders before their Begin Date and/or Consider Orders after their End
Date. If selected, the Begin and End dates for all the orders will be ignored.
Filters
Click on the Filters icon to open the Filters pages. These pages let you select the orders
that will be considered when routes are created. The first page, Include Stops, allows you
to choose which orders will be considered, while the second page, Exclude Stops, lets you
choose which of those considered orders will be ignored. For instance, on the first page
you could choose to route all orders with a Size1 value between 0 and 1000, but on the
second page you could eliminate those orders that are for stops in a specific zone, which
may need a smaller vehicle because it is in a downtown area with crowded streets. Each
page has essentially the same options. You can choose whether an order needs to meet all
the criteria (And) or only one of the specified criteria (Or). The display area next to the
Include/Exclude Stops based on: list shows the selected criteria.
492

To include an option in the filter, check it in the Include/Exclude stops based on: list
and make the necessary entries or selections.
You can use the filters pages to select the orders that you want to route.
Standard Routing
The Standard Routing page lets you specify which standard route set(s) to use when
routing, and whether or not to use any route overrides that exist in the set. Your daily
routes will be created using the standard routes you have created and added to the set.
Click on the Standard Routes icon and select the standard route sets to use from the list.
If you want to use existing route overrides instead of the standard route, check the box. If
you want to only use standard routes for the day they are designated, check Use route
days. If this is not checked, all standard routes in the set will be used on every delivery
day.
Dynamic Routing
Roadnet offers many choices when you use dynamic routing, so the dynamic routing
section of the Routing Pass Options notebook contains many pages of options. To select
the dynamic routing options, click on the Dynamic icon to open the dynamic routing
options. Each page of options is discussed below.
Operations Guide
493
Restrictions
The Restrictions page allows you to set restrictions on the route being built, including
time limits, capacity minimums and maximums that must be met, and whether or not cells
are considered.
The Restrictions page is where you establish the basic limits of the routes that will be
created. The subsequent pages let you fine tune how the routes are created.
To limit the route to the capacity of the equipment type, check the size being used. The
equipment capacities were entered when the equipment types were created.
To select a start time for the route, enter it in the Start Time field.
To restrict the length of the route, enter the preferred runtime and the maximum
runtime in the Preferred Time and Maximum Time fields. When routing, Roadnet will try
not to exceed to preferred runtime and will not exceed the maximum runtime unless you
manually add a stop to the route or otherwise specify this time can be exceeded.
To have pre-route and post-route stops created, enter the length of the stops in the PreRoute Time and Post-Route Time fields. Pre- and post-route stops can be used to
compensate for time between when the driver clocks in and when he departs from the
depot, and at the end of the day the time between returning to the depot and clocking out.
The driver is paid for the pre- and post-route time, so therefore it is included when
calculating the total time of the route.
494

To ignore equipment types assigned to the locations in the Maintenance module,

check Ignore Stops Equipment Type Restriction. If this option is checked, the stops will
be routed without regard to any equipment types assigned to the location. If this box is not
checked, stops will only be placed on a route using an equipment type assigned to the
location; if no routes using an assigned equipment type are available, the stop will be
unassigned.
To select the starting quantity on the equipment, click on the Starting Quantity arrow
and select either As Needed, Empty, or Full. For example, if a fuel truck is typically
refilled at the last stop, then enter Full. If a fuel truck is typically refilled at the first stop,
then enter Empty. Finally, if a fuel truck starts the route with just enough fuel for that
route, then enter As Needed.
To assure that you are running routes of at least a certain size, enter the route
minimum information. The route must meet one of the specified minimums unless Build
Small Routes is selected on the Strategies page or Ignore Route Restriction Minimums is
selected on the Standard Sequencing page. In the Equipment Capacity area, choose either
Consider All Selected Restrictions or Consider Any Selected Restrictions. If you choose
Consider All Selected Restrictions the route minimum will be based on all sizes selected
for capacity restrictions, meaning each selected size must meet the capacity minimum. If
you choose Consider Any Selected Restrictions the route minimum will only require that
at least one of the selected sizes meets the capacity minimum. In the % Full box, enter the
percentage of the established equipment capacity that must be met for the route to be
created. In the % Preferred Time box, enter the percentage of the preferred run time that
must be met for the route to be created.
To assure that your routes do not exceed a specified number of stops, check Restrict
Stops per Route in the Maximums area. Enter the maximum number of stops in the Max
Number of Stops field below. The number of stops on the route, including all the trips on
a reloaded route, will not exceed this number unless the route is part of a standard route
sequence.
Note: If you are using standard route sequencing and the standard route contains more
stops than the number specified here, the number of stops on the standard route
will prevail.
To have cells used when routing, select the cell pattern to be used. Cells are created on
the map; if cells are considered when routing, cell boundaries will not be crossed when
the routes are created. To have the cell attributes considered, check Use cell attributes.
These restrictions will override other restrictions established in the Routing Pass Options
notebook.
Resources
The Resources page lets you specify the type of equipment available and the depots that
can be the starting and ending points of the routes.
To select the equipment types or the depots available for routing, specify the number
of pieces of equipment available. Hold down the [Alt] key and click in the Resources
Operations Guide
495
column for the equipment type of depot you want to assign resources to; enter the number
in the column and press the [Enter] key. Or, double-click on the equipment type and make
the changes in the Modify window that opens. If no equipment types are allocated, no
routes will be created. If no resources are allocated to any depots, all routes will stem from
the default depot selected in the Options notebook.
To specify the types of routes that should be created for an equipment type, doubleclick on the type in the Equipment Types list. The Modify Equipment Type window
opens, where you can specify that routes using that equipment type should be extended or
multi-day runs. If you want to create routes using the preferred run time specified on the
Restrictions page, Off would be the correct choice; this is the normal choice. If specifying
extended runs, enter the preferred runtime, overnight break, and maximum day
information on the Extended Runs page.
To have Roadnet determine the least expensive order in which to use the equipment
types, check Choose Least Expensive Equipment Type Usage Order. If this option is
selected, all possible equipment type orders will be investigated. For instance, if you have
equipment types A, B, and C, and they are listed in that order, Roadnet will not only try
A then B then C, but ACB, BCA, BAC, CAB, and CBA to determine which order
produces the least cost solution. If this option is not selected, then the equipment types
will be used in the order listed. Selecting this option will make the route creation process
take longer.
If the equipment type has a helper associated with it, check the box in the Helper
column for the type, or check the Helper box in the Modify Equipment Type window.
Skill Sets
The Skill Sets page lets you specify whether or not skill sets need to be considered when
the routes are created, as well as indicate the number of employees available with each
skill set.
To specify that skill sets should be considered when orders are created, check Use Skill
Sets. If this option is selected, stops will only be added to routes that have a preferred skill
set that includes that orders activities. Skill sets are only used if your are using order
activities.
To indicate the number of employees available with each skill set, double-click in
Resources column for that skill set; the Modify Skill Set window opens. Enter the number
of available employees with that skill set in the Resources field and click the [OK] button.
496

Strategies - Basic
The Strategies - Basic page lets you choose how Roadnet will analyze different locations
and choose the ones that will be part of each route, as well as the order in which they are
routed.
The Strategies-Basic
page lets you select
how the initial and
subsequent stops are
selected for each
route.
Selecting the Initial Stop

To select the location that will be the basis for the route, click Far Out Point, Closest Point,
or Size in the Seed by area. As the routes are created and sequenced, this location may not
be the first stop on the route; it is simply the location used as the basis for the route. If Far
Out Point is chosen, the location that has the longest travel time from the depot is selected
as the first stop to be routed. If Closest Point is selected, the location that has the shortest
travel time from the depot is selected. If Size is selected, the location with the largest order
is selected as the first stop to be routed. If Urgency is selected, the location with the order
with the highest urgency will be selected as the first stop to be routed. Normally, Far Out
Point is selected.
Routing Subsequent Stops
Once the initial stop for the route is selected, use the options in the Sort Friends by area
to choose the method that will be used to select and sequence the subsequent stops. Slide
the bar to indicate whether to sort the friends based on the orders urgency (Urgency) or
the selected distance options, or a mix of the two. In the Distance Options area, select the
Operations Guide
497
methods you want to use to sort the list of possible stops. If multiple methods are selected,
the different strategies will be combined. These options all work from the list of friends
that is generated using the options entered in the Grouping area.
Grouping Locations Considered for a Route
You can specify how different locations make it onto each routes list of friends by the
options you choose in the Grouping area.
Duplicate Lat/Longroutes orders for locations with identical latitudes and longitudes
together. Orders for locations with identical latitudes and longitudes will be routed
together if the orders have the same preferred origin, urgency, daily urgency increase, and
begin and end dates; and if the locations have the same time windows, preferred
equipment type, preferred route IDs, and valid delivery days.
Note: Orders will not be routed together in the following situations:
if priority stops are being used and one of the locations is assigned a priority, or
if pickups at end of route is being used and one of the orders is a pickup, or
if order sourcing is being used and one of the orders is a pickup.
Visual Clusteringtends to group the stops geographically instead of by time needed to

to drive from one stop to the next. This option is helpful if you are routing in metropolitan
areas with one-way streets and your stops are close together.
Vicinitywill only consider stops that are in the specified vicinity of the initial stop.
Enter the furthest distance a location can be from the initial stop in the Distance field, and
the percentage locations can be outside this radius but still be considered. These two
factors form a cone from the depot to a circle surrounding the initial stop; locations in the
cone are included by the percentage factor.
Max friendsthe maximum number of locations that will be considered for a route. The
list is created based on the initial stop and the routing strategy selected in the Routing area;
the friends are taken from the locations that seem the most viable.
Max insertion attemptsthe maximum number of attempts to insert a stop onto a route
per group of friends. Once this maximum has been reached, no further attempts are made.
Establishing the Routes Destination
You can specify the routes final destination.
Last Stop is Destinationroutes are created using their last stop as the destination. This
means that travel time and paid time will be calculated without considering the time back
to the depot at the end of the route.
Strategies - Advanced
The Strategies - Advanced page lets you select some additional strategies that will be used
when the routes are being created.
498

Auto increment runtimeonce the routes have been created, if there is more than the
maximum number of unassigneds allowed in the Max field, Roadnet re-creates the routes,
until either the max unassigned level is reached, or the routes exceed the maximum
runtime.
Build small routesallows Roadnet to build routes that do not meet the minimums
specified on the Restrictions page.
Priority stopsvisits stops according to priority. If selected, all locations with a Stop
Priority of 9 will be delivered first, then all the 8s, etc. It is possible to have more than
one stop with a priority of 9 on a route, but all 9s will be delivered before the 8s.
If you have helpers

on your routes, check
Create Helper Routes
to have the service
times calculated
using helpers,
instead of a solo
driver.
Pickups at end of routeroutes orders with a selector of P as a pickup. If an order is

specified as a pickup, it will be placed at the end of the route. If this option is not selected,
the pickups will be placed throughout the route.
Pass Advisorturns on the pass advisor, a window that appears before each pass is
routed, giving you an opportunity to change equipment availability, etc.
Create Helper Routescalculates the service time for the stops using the helper fixed
and variable service time.
Assign Equip Types Driverassigns a driver who is associated with the routes
equipment type to the route, even if that driver is already assigned to another route.
Equipment is assigned to the driver on the Drivers window in the Maintenance module.
Operations Guide
499
Choosing the Depot Strategy

The Depot Selection area lets you choose which locations are considered for routes
stemming from each depot. The normal choice is Distinct, where each depot has its own
set of locations that are routed, and does not pick up locations for other depots. Shared is
used if more than one depot covers a delivery area.
Choosing the Compartment Routing Options
The Compartment Routing area lets control whether or not compartment routing will be
used when routes are built. Select Enable Compartment Routing to use compartment
routing. If you select to use compartment routing and want to require that every
compartment be at least a certain amount full to be used, select the Enforce Minimums
option. You can specify what percent full each compartment must be to be used in the
Compartment Minimum % field. If a compartment is not at least as full as you specify,
no product will loaded into the compartment.
Preferred Route ID Routing
Preferred route ID routing allows you to define which route locations or orders should be
placed on, but lets Roadnet determine the best sequence for the stops. This can be useful
if you want to make sure that all locations that need a special kind of truck, or are in the
same geographic area, are grouped together. Preferred route ID routing lets you retain
much of the control of standard routing, while still letting Roadnet help with cost
savings.
If you choose to use preferred route ID routing when creating your daily routes, orders
that have a preferred route ID associated with them (whether through the order or the
location) will be placed on that route. If the equipment associated with the route does not
500

have enough capacity, or the route extends beyond the preferred runtime, the orders with
the preferred route IDs may be unassigned.
If you choose to blend

orders without
preferred route IDs
onto preferred route
ID routes, those
orders will only be
added to the routes
after all orders with
that preferred route
ID have been tried.
To use preferred route ID routing, check Enable Preferred Route ID Routing and
select how you want Roadnet to handle orders that do not have a preferred route ID. The
options are:
Leave them unassignedwill only use orders with preferred route IDs to create
routes; orders without a preferred route ID will be unassigned. Orders with
preferred route IDs will be placed on the correct route.
Create non preferred routes and assign them to these routes onlywill create
both preferred routes and not preferred routes, but will not add orders without
preferred route IDs to preferred routes. In other words, preferred routes will only
contain stops with preferred route IDs, and non-preferred routes will only contain
stops without preferred route IDs.
Allow them to be assigned to preferred routes onlywill only create preferred
routes but will complete them with orders that do not have preferred route IDs.
Allow them to be assigned to preferred routes or newly created non preferred
routeswill create both preferred routes and not preferred routes, and will
complete preferred routes with orders that do not have preferred route IDs.
Operations Guide
501
Time Window
The Time Window page allows you to specify how important it is that customer time
windows are met and what adjustments to make to the route to meet the time windows, if
necessary.
To have the routes created without considering the locations time windows, click on
No Time Windowing.
To have time windows considered after the routes are created, and the routes
resequenced based on time windows, click on As Post Process. This option may create
routes that exceed the preferred runtime or the max runtime.
To have time windows considered while the route is being created, click on Check
While Creates Routes. After each stop is added to the route, the route is resequenced based
on the time windows. This option may cause the routing process to take longer, but there
is less chance of the route exceeding the preferred runtime.
To have time windows weighed very heavily, even at the expense of runtime and cost,
click on Make All. Almost all stops will make their time windows, but you may have a
lot of unassigned stops.
Hint: If this option is selected, you should check Adjust Start Times and allow the driver
to wait to make time windows. Also, on the Strategies page, increase the Max.
Insertion Attempts to at least 10.
To weigh the importance of meeting locations time windows against minimizing the
cost of the route, use the slider bar. The farther the bar is to the right, the more weight is
given to meeting locations time windows.
To allow Roadnet to adjust the routes start time, check the Adjust Start Times box
and specify the amount of time early and late the route can be started, and the number of
minutes to increment the start time in.
To allow Roadnet to let the equipment wait at a stop to meet the time window or open
time, check the appropriate box in the Wait Time area, and specify the maximum amount
of time the driver can wait, and whether or not the driver is paid for the wait time. If this
option is not checked, Roadnet will not allow the driver to wait at all to meet the time.
Auto Assign
The Auto Assign page lets you specify how the routes will be named and whether or not
the saved area attributes, such as the driver, equipment, and route ID, will be assigned to
the route.
To have Roadnet create a description of the route based on the geographic center of
the route, check Route Name. If this option is not selected, Roadnet will not generate a
description of the route.
To specify a prefix that will be used for the route IDs, enter the prefix in the Route ID
seed field. The IDs will be numbered sequentially using this prefix. For instance, if the
502

seed is RN the route IDs will be RN1, RN2, etc. If no prefix is entered, the route IDs will
just be the numbers.
Notes: The total route ID cannot exceed 15 characters, including the prefix and the
assigned route ID. If this combination exceeds 15 characters, the prefix will be
shortened to accommodate all digits of the assigned route ID.
If you are using saved area attributes or standard route fragments, the route prefix
will not be used.
To have the saved area attributes automatically assigned to the route, such as the
driver, load priority, equipment, start time, color, and route description and ID, click the
Area Attribute Set arrow and select the area attribute set you want to use. In the Attraction
(distance) field, enter the maximum distance the center of the newly created route can be
from the center of the saved area for the route to be considered for those area attributes.
In the Days area, check the days attributes that you want to use. If you do not want any
attributes automatically applied to created routes, select <NONE> from the list.
Note: When routes are created, if the equipment or equipment type saved to the area
attributes does not match the equipment type assigned to the route, the equipment
or equipment type in the saved area attribute set will be ignored.
Mid-Route Sourcing
The Mid-Route Sourcing page lets you specify how long it takes to service a stop. It also
lets you specify which depots to have considered as mid-route sources in the routing pass.
The Mid-Route Sourcing page displays only when Mid-Route Sourcing is enabled for the
routing session.
Notes: Disabling the Mid-Route Sourcing feature for a routing session will remove the
Mid-Route Sourcing tab from the Dynamic Routing Pass Options notebook. The
Reloads and Reload Limits tabs will be available in its place. If the Mid-Route
Sourcing settings are defined and then the Mid-Route Sourcing function is
disabled, the Reloads tab will reflect the settings from the Mid-Route Sourcing
tab.
Operations Guide
503
If you are using Mid-Route Sourcing, you can not use Stranded Stop Evalulation
on the Post Process page.
Depots with a check in the Available column will be included in the Dynamic
Routing Pass.
To set the mid-route sourcing service time, select either Specify Time or Use Depot
Service Time. The service time is the amount of time needed to perform all the necessary
functions at a stop. If you select Specify Time, enter the exact time using the format
HH:MM.
Note: The Depots list will contain all depots for that region; however, only depots marked
as Available will be considered as mid-route sources.
The Depots list can be sorted by clicking on the column header of the column you
want to sort by.
Reloads
The Reloads page lets you specify that if a truck finishes its route early enough in the day,
and other conditions are met, it can be reloaded and sent out on a second trip.
Notes: Reloaded routes cannot contain any stops with a higher priority than the stops on
the first route. Stops with a priority of 9 cannot be placed on reloaded routes; these
stops will either be placed on the first route or remain unassigned.
504

The maximum number of stops allowed on the entire route, including all trips, is
specified on the Restrictions page.
The reload limits, such as the number of reloads per route and the maximum
distance to the reload depot, are set on the Reload Limits page.
The Reloads page will not be available if Mid-Route Sourcing is enabled for the
session.
To allow the equipment to be reloaded based on the equipments capacity, check the
Enable Capacity Reloads box and enter when the reload should occur in the Capacity %
Threshold field. Typically, if you are creating delivery routes this percentage will be small
(20%), but if you are creating pickup routes the percentage would be high (80%). You can
enter the information manually, or use the arrows to scroll to the correct percentage. This
option is not available if Fill As Needed is selected as the reload action.
To use the service

time established for
the depot when
reloading, select
Use Reload Depot
Service Time.
To allow the equipment to be reloaded based on the routes runtime, check the Enable
Runtime Reloads box.
To set the maximum runtime for the route before a reload, enter the time in the
Runtime Threshold field as HH:MM.
Note: If runtime thresholds are enabled, the threshold represents the maximum runtime
for any trip, including routes that contain only one trip.
To set the geographical area of the reload route, select Geographic or NonGeographic. Geographic reloading will create the next trip using stops closest to the
Operations Guide
505
previous trip. Non-geographic reloading will create the next trip closest to the reloading
depot.
Note: If you are allowing Roadnet to split orders that are too large to fit on the equipment
and you select Geographic reloads, Roadnet will attempt to use the same piece of
equipment for the entire order.
To automatically have the equipment visit a depot and reload after the last stop,
check Always Reload After Last Stop. If the depot the equipment is returning to (final
destination) can reload the equipment, then it will use that depot for reloading. If not, then
Roadnet will find the best available depot for a reload.
To set the equipment's reload action, click the Reload Action Taken arrow and select
either Fill As Needed, Fill to Capacity, or Empty. Whatever option you choose here will
be used for every reload on your route. For example, if a fuel truck is typically refilled to
capacity upon reload, then select Fill to Capacity. If a waste disposal truck plans on
dumping at each depot, then select Empty. If a food delivery truck plans on only filling
the truck with enough food for its next trip, then select Fill As Needed.
To set the reload service time, select either Specify Time or Use Reload Depot Service
Time. The reload service time is the amount of time needed to reload the truck if it is being
sent out for another route. If you selected Specify Time, enter in the exact time using the
format HH:MM.
To select the depot used for reloads, select either Use Origin or Use Best Available. If
you select Use Origin, then the depot the equipment departed from/Origin will be used. If
you choose Use Best Available, Roadnet will determine the best available depot for the
reload from the list below.
Note: The Depots list will contain all depots for that region; however, only depots
marked as Available and with open/close times that include the reload time will
be considered for reloads. If the depot is not marked available, double-click on the
depot and check Available on the Modify Depot window, or check the box in the
Available column.
Reload Limits
Roadnet offers many choices when you use dynamic routing, so the dynamic routing
section of the Routing Pass Options notebook contains many pages of options. To select
the dynamic routing options, click on the Dynamic icon to open the dynamic routing
options.
The Reload Limits page of the Routing Pass Options notebook lets you set limits on the
reloads that are created for your routes. The options on this page work with the options
you set on the Reloads page, and are not available unless the Enable box on the Reloads
page is checked.
506

Note: The Reload Limits page will not be available if Mid-Route Sourcing is enabled for
the session.
To limit the number of reloads a route can have, check Limit Number of Reloads.
Enter the maximum number of allowed reloads per route in the Maximum Number of
Reloads field below. Routes will not be created with more than this number of reloads,
which may cause some orders to not be routed. If this option is not selected, reloads will
continue to be created until another limit (such as the routes runtime or the maximum
stops) has been reached.
To limit the total quantity for the route, check the appropriate size in the Maximum
Quantity per Route area. For each selected size, enter the maximum quantity for the route
in the field to the right. If this option is selected, the total quantity for the route, including
all trips, will not exceed this amount.
To set the percentage capacity the equipment must be at to be considered for a
reload, enter the percentage in the Next trip min % capacity field. If you are routing
deliveries this number would normally be a low number (ex. 20%), but if you are routing
pickups this number would normally be a high percentage (ex. 80%). You can enter the
percentage manually, or use the arrows to scroll to the percentage.
To set the minimum runtime for any subsequent trip, enter the runtime in the Next
Trips Min Runtime field as HH:MM.
To set the maximum time from the last stop on the route to the reload depot, enter
the time in the First Trip's Max Return Time. If the equipments return time is greater than
this time, a reload will not be created. The time must be entered using the format HH:MM.
Extended Runs
The Extended Runs page lets you establish guidelines for Roadnet to use when creating
routes longer than the preferred runtime or multi-day runs. Extended runs may be
necessary if the first stop is a significant distance from the depot, causing a long stem. You
can create extended runs or multi-day runs.
Note: If you have specified extended runs for equipment types on the Modify Equipment
Types window, make sure the Enabled box are NOT checked on this page. You
will need to check the boxes to enter the information, but then uncheck the boxes
before creating the routes.
To allow extended or multi-day runs, check the appropriate Enable box. Enter the least
amount of travel time (HH:MM) between the depot and the first stop for the route to be
considered for extended or multi-day runs in the Stem Length box. Enter the new
preferred runtime for the extended run in the Preferred Time box; this time will be used
instead of the preferred run time specified on the Restrictions page. If creating multi-day
runs, enter the maximum amount of time for the overnight break in the Overnight Break
box. Click the small arrows in the Maximum Days box to enter the maximum number of
days the route can last. To have drivers paid for the overnight break, check the Paid box.
Operations Guide
507
Post Process
The Post Process page lets you specify the kind of evaluation, if any, Roadnet will do after
the routing process is complete. All of the options on this page, and the Backtracking
page, refer to different things Roadnet can do during the post process evaluation. The
options on the Post Process page deal with evaluating stranded stops, or stops that cause
the driver to travel out of the way to deliver, but might be closer to another route, as well
as unassigned stops. The options on the Backtracking page deal with unassigned stops.
Notes: Stranded stops will only be routed if the maximum runtime allows for it.
Stranded stops can not be used with Mid-Route Sourcing.
To evaluate the stranded stops, move the slider bar towards Maximum Evaluation. The
farther the bar is to the right, the more time will be spent evaluating the stranded stops.
To place the stranded or unassigned stop on the end of a route, check Stem Insertions.
To allow the maximum runtime to be extended, enter the additional amount of time
allowed in HH:MM. To exclude stranded and unassigned stops that are not in the same
cell from being considered, check Adhere to cell boundaries.
To allow Roadnet to pack additional stranded or unassigned stops onto a route,
exceeding the established preferred runtime if necessary, check Intelligent Packing.
Roadnet may exceed the preferred runtime when adding stops to the route, but will not
exceed the maximum runtime. In the Packing Factor field, enter the maximum amount of
time that an individual stop can add to the route.
Note: Intelligent Packing will not work if you are using reloads or have Make all Time
Windows selected.
To allow Roadnet to assign a smaller truck to the route, if the route does not fill the
originally routed truck and a smaller truck is available, check Optimize equipment type.
Backtracking
The Backtracking page allows Roadnet to evaluate unassigned stops after the routing
process is complete to see if they can be added to an existing route.
To allow backtracking, check the Enable backtracking box.
Enter the maximum distance the unassigned stop can be from the route on the first try
(Initial Radius) and on subsequent backtracking passes (Maximum Radius). Enter the
amount the maximum runtime can be extended by in the Additional maximum runtime
box.
To limit the amount of time Roadnet can spend on backtracking per pass, enter the
maximum time in the Time Out field.
To have only locations in the same cell added to a route, check Adhere to cell
boundaries.
Standard Sequencing
The Standard Sequencing page allows Roadnet to use standard route sets as the basis for
dynamic routes. If this option is selected, locations with orders that appear on the selected
508

standard route sets will be routed first on those routes; locations with orders that are not
on the standard route sets will be used to complete the routes. Check the Enable box and
click on the route sets in the list that can be used.
To ignore the minimum restrictions defined on the Restrictions page, and create routes
even if they do not meet these minimums, check Ignore Route Restriction Minimums. If
this option is not selected, and the route does not meet either of the defined minimums,
the stops will be unassigned.
To have the daily routes based on standard route overrides that exist, check Use Route
Overrides. If this option is selected, for those standard routes that have an override the
override will be used as the basis for the standard route; if no overrides exist for a standard
route, the daily routes will be based on the standard route
Split Orders
The Split Orders page lets Roadnet split orders, if necessary, to fit on equipment. If this
option is selected, Roadnet will split an order between multiple pieces of equipment if it
cannot fit on a single piece of equipment; if this option is not selected the order will not
be routed. The split order is assigned a new order number, which is the specified prefix
plus a number, starting with 001.
Note: Orders on standard routes will not be split, even if they are too large to fit on a
piece of equipment.
To keep orders from being split, click Do Not Split Orders.
To split orders, even if it means putting one order on multiple pieces of equipment,
click Split Orders.
Note: If you are splitting orders that are too large to fit on the equipment and are also
using reloads to create multiple routes for the equipment during the day, you can
have Roadnet attempt to use the same piece of equipment for the entire day by
selecting Geographic reloads on the Reload page.
To keep an individual order from being split between multiple pieces of equipment,
click Split on Order Boundaries. Multiple orders to the same stop may still be split
between multiple pieces of equipment. If you only have one order per stop, this option is
not valid.
Select the method that will be used to assign a number to the new order. The choices
are Location ID (the locations ID will precede the new order number), Order Number
(the order number of the original order will precede the order number), and Custom (you
can choose the characters that will precede the order number).
Important: If you are uploading order numbers to the host, make sure that the field is
large enough to accommodate the order number and prefix.
When the new order numbers are assigned for the split orders, they need to be unique.
Select whether the new order number should be unique for the location or for the session.
Operations Guide
509
To assign a selector to split orders, that will indicate the order is a split, enter the single
character in the Upload Selector field.
510

Locking and Unlocking Orders
Locking and Unlocking Orders

Used with: Roadnet
Order locking allows you to prevent orders that are on a route from being moved to a
different route. Orders that are locked will not be removed from their current route upon
performing actions such as creating routes, balancing routes, or time window swapping
routes. Locked orders can only change sequence when performing these actions.
In the Routing Options Notebook you can select whether Roadnet will allow you, prohibit
you, or warn you when you try to manually remove locked orders from their route. You
can also set how Roadnet will assign the lock status of orders that have been moved to a
different route.
Roadnet prioritizes keeping locked orders on their current route above all other
considerations. Therefore, if you have locked orders the create routes process may build
routes that run longer than the maximum runtime or exceed the equipments capacity.
Also, any attributes or properties associated with a route that contains a locked order will
not be changed when routes are created. For example, if you assign an unavailable
equipment type to a route, Roadnet will not change the equipment type if the route has a
locked order on it.
When importing orders and sending orders, you can select to have Roadnet automatically
change the lock status of the orders included in the import or send.
To lock/unlock all orders on a route, click on the List menu and select Active Routes.
The Active Routes window opens. [Ctrl]+click on each route that you want to lock/unlock
the orders on, then right-click and select either Lock Order(s) to Route or Unlock Order(s)
from Route from the menu that pops up.
To lock/unlock individual orders, click on the List menu and select Active Routes. In
the Active Routes window double-click on the route that the orders that you want to lock/
unlock are on. Double-click on the stop that the orders that you want to lock/unlock are
on. In the Order window, [Ctrl]+click the orders that you want to lock/unlock, then rightclick on any of the selected orders and select either Lock Order(s) to Route or Unlock
Order(s) from Route from the menu that pops up.
OR
Click on the List menu and select Orders. The Orders window opens, listing all orders for
that routing session. [Ctrl]+click on each order that you want to lock/unlock, then rightclick on any of the selected orders and select either Lock Order(s) to Route or Unlock
Order(s) from Route from the menu that pops up.
Operations Guide
511
Evaluating the Routes in the Routing Editor

Used with: Roadnet
Once you have created the routes in the Routing Editor, you can use the map, reports, and
windows to look at the routes and make any necessary changes, including manually
adding stops to a route, transferring stops from one route to another, re-sequencing routes,
time windowing the route, assigning unassigned stops to a route, etc.
To see all the routes for a specific day of the week, (for instance to see all the Monday
routes), click on the List menu and select Routes, then the day of the week (Monday). A
Routes window opens listing all the sessions routes for that day.
To see all the routes for a range of dates, click on the List menu and select Routes, then
Date. The Specify Date Range window opens. Click on the arrows to enter the From and
To dates for the range you want to view. A Routes window opens listing all routes in that
range.
To display the route on a map, right-click on the route and select Plot from the menu
that pops up ([Ctrl]+[P]), or press the Plot icon on the Routes toolbar. If a map is already
open, click on the route and drag it to the map.
To display the route and its surrounding locations and routes on a map, right-click
on the route and select Plot Vicinity from the menu that pops up.
To see the stops on a route, double-click on the route in the Routes window, or rightclick on the route in the Routes window or on the map and select Open from the menu that
pops up. The Stops window for the route opens.
You can use the map, route summary, or list window to see information about
the stops and routes.
512

To see a summary of the selected routes, such as the total, average, maximum, and
minimum for stops, load as each of the sizes, runtime, distance, cost, time window
information, service time, and travel time, select the routes to summarize in the Routes
window. Right-click on a selected route and select Summary from the menu that pops up.
The Summary window opens, with information for all the selected routes. To print the
summary, click on the Print icon.
The Route Summary
window will show
information for all
routes, or only selected
routes, depending on
how it is opened.
To see a summary of all the routes, click on the File menu and select Summary. The
Route Summary window opens, showing route information for the entire session.
To see a summary for the entire week, click on the File menu and select Weekly
Summary. The Weekly Summary window opens, showing a summary of the sessions
routes for the next 7 days. The first date on the summary defaults to the session date; to
change the starting date click on the Calendar icon and select a different date. You can
choose to see totals, averages, minimums, or maximums for each day. Click the Print icon
to print the summary.
To see any exceptions for all the routes, such as stops that missed the time windows,
off-day deliveries, priority stops, geocode exceptions, or missed time window factor,
click on the List menu and select Exceptions, then the desired choice. The appropriate
window opens. You can drag stops from these windows to the routes; see Routing
Unassigned Stops or Transferring Stops for more information.
Note: You can easily see the exceptions for an individual stop or route by looking at the
Exceptions column in the Route or Stops window.
Balancing the Routes
When evaluating the routes, you may find two routes that appear to be unequal for
instance, one has a total time of 4 hours and another route has a total time of 10
Operations Guide
513
hoursyou could select these two routes and have Roadnet re-route only the stops on the
selected routes. When routes are balanced, only the selected routes are affected.
Notes: When balancing routes with mid-route depots, the balancing works separately on
each trip on the route. The mid-route depot(s) will remain where it is and the
balancing action is only performed on each trip.
Any orders that are locked will not be removed from their route when balancing
routes. However, locked orders can change sequence.
Step 1: Select the routes to be balanced in the Routes window, or on the map. Click on
the first route, then hold down the [Ctrl] key while clicking the subsequent routes.
Step 2: Right-click on one of the selected routes and select Action, then Balance, then
the balancing criteria, from the menu that pops up, or click the appropriate icon
on the Routes toolbar. The different options are explained below.
By timetransfers and sequences stops as needed to create routes with total
runtimes as close as possible.
By loadtransfers and sequences the stops as needed to create routes with load
sizes as close as possible. The loads are measured using the size alias specified as
the Unit of Measure in the Options notebook.
By % capacitytransfers and sequences the stops as needed to create routes with
the equipment's capacity as close as possible. The capacity for the equipment is
established when the equipment type is created.
Step 3: The routes are balanced as requested, and the results can be seen by checking
the appropriate column in the Routes window.
Note: Balance By Load and Balance By % Capacity are not available when Mid-Route
Sourcing is enabled.
Routing Editor Routes window Action Balance By Time([Ctrl]+[Shift]+[T])/By
Load ([Ctrl]+[Shift]+[L])/By % Capacity ([Ctrl]+[Shift]+[C])
Combining Routes
When evaluating the routes, you may find that you have several small routes that could
be combined to create a larger route; you can have Roadnet combine those routes into one.
You must be in the Routing Editor to perform this procedure.
Note: When combining routes with mid-route depots, the depot(s) will be treated like a
stop and combined onto the route.
Step 1: Select the routes to be combined in the Active Routes window, or on the map.
Click on the first route, then hold down the [Ctrl] key while clicking the
subsequent routes.
514

Step 2: Right-click on one of the selected routes and select Action, then Combine, then
the combine criteria, from the menu that pops up, or press the appropriate icon on
the toolbar.
No Resequencecombines the selected routes without sequencing the stops. The
route that you right-click on to access the menu is placed first, then the remaining
routes are combined in the order selected.
Sequencecombines the selected routes, re-sequencing the stops as needed to
make the new route more efficient.
Step 3: The routes are combined as requested, and the results can be seen in the Routes
window.
Routing Editor Routes window Action Combine No Resequence
([Ctrl]+[Shift]+[N])/Sequence ([Ctrl]+[Shift]+[R])
Time Window Swap
If you have several routes that are not meeting the locations time windows, you can
transfer stops between the routes and re-sequence the stops on the routes to make more
time windows. The time window options set in the Options notebook are used when this
action is selected. See Setting the Route Options for more information. You must be in
the Routing Editor to perform this procedure.
Notes: If you want to simply sequence the stops on the routes considering time windows,
without switching stops between routes, use the Time Window option.
When sequencing routes, the sequence works separately on each trip on the route.
The mid-route depot(s) will remain where they are and the sequencing action is
Any orders that are locked will not be removed from their route when time
window swapping routes. However, locked orders can change sequence.
Step 1: Select the routes to be time windowed in the Active Routes window, or on the
map. Click on the first route then hold down the [Ctrl] key while clicking the
subsequent routes.
Step 2: Right-click on one of the selected routes and select Action, then Time Window
Swap, from the menu that pops up, or press the Time Window Swap icon on the
Routes toolbar.
Step 3: The routes are time windowed as requested, and the results can be seen in the
Routes window.
Routing Editor Routes window Action Time Window Swap ([Ctrl]+[Y]))
Adjust Mid-Route Sourcing
You can use Adjust Mid-Route Sourcing to reassign the mid-route sourcing depots on
your route without moving the stops that you changed. The moves you make to your stops
Operations Guide
515
will remain, only the mid-route sourcing depots inserted by the Roadnet Transportation
Suite will be reworked.
Step 1: Select the route to be adjusted in the Active Routes window, or on the map. If
you want to work with more than one route, click on the first route, then hold down
the [CTRL] key while clicking the subsequent routes.
Step 2: Right-click on the selected route and select Route, then Actions, then Adjust
Mid-Route Sourcing from the menu that pops up, or press the Adjust Mid-Route
Sourcing icon on the toolbar.
Step 3: Roadnet reassigns the mid-route sourcing depots without changing the stop
sequence. The results can be seen in the Routes window.
Routing Editor Routes window Action Adjust Mid-Route Sourcing ([Ctrl]+[U]))
516

Finding Paired Orders
Finding Paired Orders

Used with: Roadnet
If you are using order sourcing to ensure that your paired pickup and delivery orders are
placed on the same route, there may be times when the orders become separated and you
need to find the other part of the order pair. Roadnet provides a feature that lets you easily
find the second part of the order pair.
Note: These options are not displayed if order sourcing is not enabled on the General
page of the Maintenance Options notebook.
want to work with.
Step 2: If you are looking at an order and want to find its paired order, right-click
on the order and select Find Paired Orders from the menu that pops up. An
Orders window opens, showing both orders in the pair, and the route each order
is currently on.
Finding the missing part of an order pair is easy using Find Paired Orders or
Find Paired Stops.
If you are looking at a stop and want to find its paired stop, right-click on the
stop and select Find Paired Stops from the menu that pops up. A Stops window
opens, showing both stops in the pair, and the route each stop is currently on.
Routing Editor Orders window Find Paired Orders
Routing Editor Stops window Find Paired Stops
Operations Guide
517
Listing Duplicate Geocodes
Listing Duplicate Geocodes

Used with: Roadnet
As part of evaluating your routes in the Routing Editor, you may want to determine if
stops on different routes have the same geocode, or the exact same latitude and longitude.
Two locations with the same geocode placed on two separate routes, or one location
placed on more than one route, means that the same spot is being visited more than once.
This situation could be caused by several factors, including meeting customer time
windows or equipment capacity, but it may indicate inefficient routes. You can use
Roadnet to determine if stops on different routes have the same geocodes.
want to work with.
Step 2: In a Routes window, click on the routes you want to check for duplicate
geocodes.
Step 3: Right-click on one of the selected routes and select List Duplicate Geocodes
from the menu that pops up. The Duplicate Geocodes window opens, listing all
stops with duplicate geocodes, including the stop on the original route.
You may want to consider placing stops that have the same geocode, or latitude and
longitude, on the same route.
Note: All routes will be searched for geocodes matching the stops on the selected routes,
but duplicate geocodes may exist on two unselected routes that will not appear in
the list.
Routing Editor Routes window List Duplicate Geocodes
518

Regeocoding A Stop in the Routing Editor
Regeocoding A Stop in the Routing Editor

Used with: Roadnet
When evaluating routes you may discover a location has an incorrect geocode, or there
may be other instances where a delivery needs to be made to a different place but you still
want it recorded as being delivered to the original location. You can handle both types of
situations by regeocoding the stop in the Routing Editor. In the first case, you would
permanently regeocode the location, so that its geocode information would be correct for
future routing. In the second case, you could temporarily regeocode the stop, meaning the
geocode would change for that instance only.
want to work with.
Step 2: Open a map showing the location you want to regeocode.
Step 3: To permanently regeocode a location, right-click on it and select Geocode,
then Permanent from the menu that pops up. The cursor changes to a cross hair,
indicating that you are in Geocode mode; click where you want the location to be
geocoded to.
Routing Editor Geocode Permanent
To temporarily geocode the stop to another place, right-click and select

Geocode, then Temporary, from the menu that pops up. The cursor changes to a
cross hair, indicating that you are in Geocode mode; click where you want the stop
be temporarily geocoded to. Or, right-click on a stop in a Stop window and drag
it to the desired location on the map and select Move Here & Temporarily
Regeocode from the menu that pops up. The new geocode remains in effect in this
session until routes are created again.
Routing Editor Geocode Temporary
Routing Editor Geocode Move Here & Temporarily Regeocode
Operations Guide
519
Working With Route Reloads

Used with: Roadnet
If you have a route that finishes substantially early, its possible that the driver will be sent
back to the depot to reload the truck. Roadnets dynamic routing settings allow you to turn
on the automatic route reload option based on criteria you establish. You also have the
option to create route reloads manually for both dynamic and standard routes. Once a
route reload is assigned, a second route is created and linked to its preceding route. The
Start time for the linked route will be calculated using the return time of the previous route
and the linked routes reload time.
Whether the reload is created manually in the Routing Editor, or automatically when the
routes are created, you can choose to view the reloads as a single route or as individual
routes in the Options notebook. If the linked routes are viewed as a single route, you can
use the # of Routes column to determine which routes contain reloads. If the routes are
not shown as a single route, you can use the Prev Reload Rte Num and Next Reload Rte
Num columns to determine which routes are linked.
Linking Routes
Once you have manually linked the routes, you can use the Prev Reload Rte Num and
Next Reload Rte Num columns to determine which routes have been linked, or the
Number of Routes column to determine if a route is linked to another route.
want to work with.
Step 2: In the Active Routes window, select the routes you want to link in the order you
want to link them.
Step 3: Right-click on a selected route and select Reloads, then Link from the menu
that pops up. The routes are now linked.
Notes: The first routes origin will be the linked routes origin.
If the first routes destination is not the same as the second routes origin, then
the second routes shuttle time and shuttle distance will be calculated.
The second routes origin will be inserted on the linked route as a mid-route
depot, and the action taken at this depot depend on the second routes properties.
Also, the reload time for this depot is set to the default.
The linked routes destination is the destination of the final route being linked.
Routing Editor Routes window Reloads Link
Unlinking Routes
You can use the Prev Reload Rte Num and Next Reload Rte Num columns in the Route
window to determine which routes are linked, and which you want to view separately.
Once the routes are unlinked, they will both appear in the Routes window.
want to work with.
520

Step 2: In the Active Routes window, select the routes you want to unlink.
Step 3: Right-click on a selected route and select Reloads, then Unlink from the menu
that pops up. The routes are no longer linked.
Notes: If Create Reloads as One Route is enabled in the Options notebook, when you
unlink the routes there will be no driver or equipment assigned to the unlinked
route.
If Create Reloads as One Route is not enabled in the Options notebook, when you
unlink the routes, the unlinked route will get the same start time as the first route
in the link chain.
If there is a single mid-route depot on the route, when unlinked, the mid-route
depot becomes the first routes destination and the second routes origin.
If there are two adjacent mid-route depots on the route, when unlinked, the first
depot becomes the first routes destination and the second depot becomes the
second routes origin.
Routing Editor Routes window Reloads Unlink
Operations Guide
521
Routing Unassigned Stops or Transferring Stops

Used with: Roadnet
You can add an unassigned stop to an existing route or create a new route from several
unassigned stops. In addition, if there are stops you think should be on a different route
you can transfer them. In either case, you can specify which route to add the stop to, or
you can let Roadnet suggest a route.
Notes: All of these procedures can also be done using the map. Make sure that
unassigneds are displayed on the map; simply right-click on the stop and select the
appropriate menu option or drag the stop to the desired position.
Stops listed in the Exceptions windows (List Exceptions) can also be routed
using these procedures.
Specifying Which Route to Add the Stop to
Used with: Roadnet
You can add an unassigned stop to an existing route or create a new route from several
unassigned stops. In addition, if there are stops you think should be on a different route
you can transfer them. In either case, you can specify which route to add the stop to, or
you can let Roadnet suggest a route. You must be in the Routing Editor to perform this
procedure.
If you drag a stop to the Stops window for a route, you can specify where the stop is placed
on the route. If you drag the stop to the route in the Active Routes window, you can select
how you want Roadnet to place the stop on the route.
If you use compartment routing, Roadnet will do the following when you add stops to a
route:
If you add a stop to a route that has one or more compartments, Roadnet will
redistribute the orders into appropriate compartments.
If you add a stop to a route that does not have an appropriate compartment for the
stops orders, the stop will be assigned to the route but the stops orders will be
considered uncompartmentalized.
If you add a stop to a route that has an appropriate compartment, but the
compartment does not have enough available space, Roadnet will fill the
compartment beyond capacity.
Step 1: Open the Active Routes window.

OR
Open a map and drag all the routes you want to work with onto the map. Zoom the
map to show all the routes.
Note: If you want to specify where the stop is placed on the route, double-click on the
route in the Active Routes window to open the Stops window.
Step 2: To route an unassigned stop, click on the List menu and select Unassigned.
The Unassigned window opens.
522

OR
To transfer a routed stop, double-click on the route containing the stop. The
Stops window opens.
Step 3: Click on the stop(s) to be added to the route.
Step 4: Drag the selected stop(s) to the route. You can specify where in the route the
stop should be placed, or allow Roadnet to sequence the stop for you.
To specify where the route should be sequenced, click on the stop and drag it
to the Stops window for the route or onto the map. Drop the stop on the stop it
should follow. To place the stop as the first stop on the route, drop the stop on the
column header/depot.
To allow Roadnet to determine the best place for the stop, right-click on the
stop and drag it to the route in the Active Routes window; a menu appears with
several options for placing the stop. The options are Insert first, Insert near closest
location, Insert by best cost, Insert by best time, Insert by best TW, and Insert last.
Choose the appropriate option and Roadnet will sequence the stop accordingly.
This option is not available if you are dropping the stops on the map.
Notes: If you want Roadnet to use the option you selected on the Drag/Drop page of the
Options notebook, hold down the left mouse button, or the [Ctrl] key and the left
mouse button, while dragging the stops to the route. That action will automatically
be performed when you drop the stops on the route.
If a stop in a rush hour restricted area is placed on a route with a restricted
equipment type, the map will not follow a path to the route; it will simply show
straight lines. In addition, the driver directions will not include directions to the
stop.
The stop is placed in the selected spot.
Letting Roadnet Determine the Best Route
If you are not sure which route is best to place a stop onto, you can have Roadnet suggest
a route and the differences adding the stop to different routes will make.
Step 1: To route an unassigned stop, click on the List menu and select Unassigneds.
The Unassigned window opens, listing all stops that have not been routed.
OR
To transfer a routed stop, double-click on the route containing the stop in the
Routes window. The Stops window opens.
Step 2: Right-click on the stop and select Actions, then Suggest Route from the menu
that pops up, or click the Suggest Route icon on the Stop toolbar. The Suggest
Route window opens.
Step 3: Select the routes you want to consider in the Routes list; if no routes are
selected all routes will be considered.
Operations Guide
523
Step 4: Choose the criteria you want Roadnet to use when choosing a route. The
options are Closest location, Best distance, Best cost, Best time, and Best Time
Window. If you are working with standard unassigned stops, some options will
not be available.
Note: The slider bar setting on the Time Window page of the Options notebook does not
affect the routes Roadnet suggests.
Step 5: To eliminate routes that would exceed selected guidelines, choose the
appropriate options in the Do no exceed... area.
To prevent the route from exceeding capacity, check the size alias(es) that
cannot be exceeded. Only routes that will not exceed the specified capacity(ies) if
this stop of unassigned is added will be suggested.
To only suggest routes that do not exceed a specified number of stops, check
Stops Per Route. Enter the maximum number of stops allowed per route below.
Only routes that will not exceed this number if this stop or unassigned is added
will be suggested.
To place a time constraint on the suggested routes, choose the appropriate
restriction. The options are No time constraints, Regular time, and Max time. Only
routes that will not exceed the selected time restriction if this stop or unassigned
is added will be suggested.
Step 6: Choose the other guidelines that should be used when suggesting routes.
To have skill sets considered when routes are suggested, check Consider Skill
Set. If this option is selected, only routes assigned an employee with the
appropriate skill set will be suggested as possible routes.
To have compartments considered when routes are suggested, check Enforce
Compartment. If this option is selected, only routes that have enough available
space in compartments appropriate for the order will be suggested. This option
will only be used if you use compartment routing.
To restrict suggested routes to those occurring within the stops begin and
end dates, check Enforce Stops Begin / End Date. If this option is selected, only
routes that fall within the orders begin and end dates will be suggested.
524

To only suggest routes that are assigned an equipment type not restricted by
the stop or unassigned, check Enforce Equipment Type Restrictions.
You can have Roadnet suggest a route based on the closest location, best distance,
best cost, best time, or best time window.
To only consider routes with the orders preferred route ID, check Suggest
Preferred Route Only. If this option is selected, only the route with an ID that
matches the orders preferred route ID will be suggested.
To only consider routes where no duty period rules will be violated if the stop
is added, check Filter Out Duty Period Violations. Duty period rules regulate the
length of time that drivers can work and are used to help your organization comply
with safety and labor laws. You must have duty period rules enabled on the Duty
Period Monitor page of the Maintenance Options notebook for this option to be
available.
All possible routes are listed in the Suggestions panel, with the suggested route
highlighted. The panel includes columns showing the change in cost, distance,
time, and other routing factors. Choose the route you want to add the stop to and
click the [Accept] button.
Operations Guide
525
Note: If the stop contains part of an order pair, the route containing the other part of the
order pair will be the only route suggested.
Step 7: If you selected more than one stop, use the arrows next to the Stops for
suggestion panel to scroll to another stop; Roadnet will automatically proceed to
the next stop when you accept a route for the current stop.
To view a list of the stops, and the route they are on, check Show Accepted
Results; an additional window opens showing the accepted routes.
To automatically insert all selected stops on the selected routes, without being
able to choose the routes the stops are added to, select the suggestion option and
click the [Auto Insert] button.
The stop is moved to the selected route.
Routing Editor Stop Actions Suggest Route ([Ctrl]+[G]) Suggest Accept
To Create New Routes from Several Unassigned Stops
On especially heavy order days, you may find that you have enough unassigned stops to
justify putting more trucks on the road. In these cases, you can create routes from the
unassigned stops without bothering your existing routes.
Step 1: To route an unassigned stop, click on the List menu and select Unassigneds.
The Unassigned window opens, listing all stops that have not been routed.
OR
To transfer a routed stop, double-click on the route containing the stop in the
Routes window. The Stops window opens.
Step 2: In the Unassigneds window, [Ctrl]+click the stops to be routed.
Step 3: Right-click on a selected stop and select Create Routes from the menu that pops
up. The Route Creation Process notebook opens; click the [Start] button to create
the routes, or the [Options] button to change the routing options. See Creating
Daily Routes for more information.
Routing Editor List Unassigneds Create Routes
526

Adding Not Considered, Void, or Future Orders to a Route
Adding Not Considered, Void, or Future Orders to a Route

Used with: Roadnet
There may be times when you want to route an existing order that is not normally included
in the routing problem. For instance, a locations orders may be voided because they are
behind on their payments, but you have agreed to deliver this particular order COD. You
can manually add this order to a route. Likewise, you can add existing future orders and
not considered orders to routes.
Notes: If the future order was created with a trigger, and the same location receives an
order, the future order will automatically be routed with that order.
When a user works with a future order in a specific region, then that future order
becomes locked. This means that if a second user opens that future order in the
same region, then an error message occurs. However, the second user can view a
read-only version of the future order. This future order only becomes active if
the first user closes or saves it. The second user will then need to refresh, or close
and re-open, the future order to make any modifications. This refresh will allow
the second user to see any changes that may have been saved by the first user. This
feature is only used with Oracle and SQL databases.
Step 1: If necessary, click the Routing icon to open the Routing Editor. The Editor opens
with the Routing Sessions window visible. Double-click on the session you want
to work with.
Step 2: In the Active Routes window, double-click on the route to add the order to. The
Stops window for the route opens.
OR
Open a map and drag all the routes you want to work with onto the map. Click the
Zoom to Fit icon to zoom the map to show all the routes.
Step 3: Click the List menu and select Not Considereds, Void, or Futures. The
appropriate window opens. Select the stop(s) to be routed.
Step 4: Drag the selected stop(s) to the route. Click on the stop and drag it to the Stops
window for the route or onto the map. Drop the stop on the stop it should follow.
To have the stop as the first stop on the route, drop the stop on the column header/
depot.
Notes: A not considered stop will use the geocode of the location preceding it in the
sequence.
stop.
Routing Editor List Not Considereds/Void/Futures
Operations Guide
527
Sequencing Stops in the Routing Editor

Used with: Roadnet
There may be times when you need to change the order of stops on an active route to meet
a customer request. You can resequence the stops manually, or have Roadnet resequence
the stops based on one of several options, including the placement of the stops, time
windows, line sequence, etc.
Note: When sequencing linked routes, the sequence works separately on each trip on the
route. The mid-route depot(s) will remain where it is and the sequencing action is
To Manually Change the Order of the Stops
Step 1: Double-click on the route in the Active Routes window. The Stops window
opens.
OR
Open a map showing the route.
Step 2: Click on the stop to be moved and drag it to the stop that should precede it;
release the mouse button. To make the stop first on the route, drop it on the
column header/depot.
Hint: Keep track of the location ID for the stop to identify it if you need to move it back.
To Have Roadnet Sequence the Stops
Right-click on the route in the Active Routes window, or on the map and select Action,
then the desired option from the menu that pops up, or click the appropriate icon on the
Routes toolbar. A description of each option follows.
Note: If you only want to sequence some stops on the route, double-click on the route to
open the Stops window. Click on the first stop in the range, then [Ctrl]+click the
last stop in the range; right-click on one of the stops and select Actions, then the
Any breaks that are on the routes will be maintained and sequenced according to
the expected starting time of the break. If breaks are being added automatically,
the Editor will insert a break as needed based on the specified span; if the breaks
were added manually, they will be sequenced as close to the breaks original
starting time as possible.
Waits that are added manually will be deleted; if waits are being added
automatically they will be added as needed to meet the stops time windows.
Sequencetakes the list of stops and calculates the travel time between each stop and the
depot. The stops are placed and sequenced on the route in the way that produces the least
distance.
Flipreverses the current order of stops on the route.
528

Std. Route Sequenceif there are several stops on the route that are on a standard route
(such as you are routing for Thursday but many of the stops exist on a Wednesday
standard route), you can sequence the route so that it follows the selected standard route.
Any stops that are not on the standard route can be placed at the end of the route, or
intermingled among the standard route stops in the best possible sequence.
Note: If the daily route includes mid-route depots, they will be sequenced according to
the placement of the depot with the same ID on the standard route. If the same
depot appears more than once on the daily route, all instances of it will be placed
together when the route is standard route sequenced.
If the daily route includes Mid-Route Sourcing depots, the stops will be arranged
in the same sequence as those in the standard route, without the MRS depots. Once
the route is sequenced, MRS depots will be inserted automatically.
Line Sequenceresequences the routes based on the travel time between stops.
Typically, if End Point is selected, the two stops that are the greatest distance from each
other are the first and last stops on the route; if Midpoint is selected, the stop that is
furthest from all other stops is selected.
Time Windowsequences the stops using the locations time windows and the time
window information established in the Options notebook. See Setting the Options for
more information.
Adjust Mid-Route Sourcingreassigns mid-route sourcing depots without changing
the stop sequence.
Routing Editor Active Routes window Action Sequence ([Ctrl]+[Q])/Flip ([Ctrl]+[F])/
Std. Route Sequence([Ctrl]+[D])/Line Sequence, Midpoint ([Ctrl]+[M])/Line Sequence
Endpoint ([Ctrl]+[Z])/Time Window ([Ctrl]+[W])/Adjust Mid-Route Sourcing ([Ctrl]+[U])
Operations Guide
529
Unassigning Stops on a Route
Unassigning Stops on a Route

Used with: Roadnet
There may be times when you need to remove a stop from a route because an order was
canceled or the route exceeds one of the established limits after editing. You can easily
move stops to the Unassigned window to remove them from the route.
want work with.
Step 2: In the Active Routes window, double-click on the route containing the stop(s)
to be removed. The Stops window opens.
Step 3: Select the stop(s) to be unassigned.
Step 4: Drag the selected stops to the Unassigned window, or right-click on one of the
selected stops and select Unassign from the menu that pops up. The stops are
moved to the Unassigned window.
Routing Editor Active Routes window Stops Unassign
Note: If you click the Delete icon on the Routes window to delete selected routes, the
stops on those routes will be moved to the Unassigned window.
530

Finding a Route, Stop, or Order

Used with: Roadnet
Roadnet allows you to search for a specific route, stop, or order, based on known
information. For instance, if you want to know what route a specific location is on, you
can search for the location type and ID to find it. You can also use this option to find out
what orders are being delivered for a location, or which stops a driver is making for the
day.
want to work with.
Step 2: Click on the Tools menu and select Locate, or click the Locate icon on the
General toolbar. The Locate window opens.
Step 3: In the Return results as area, choose whether you want to see the results as
standard routes or stops, or daily routes, stops, or orders.
You can use the Locate window to find a route, stop or order if you know the location, driver,
order number, or equipment.
Step 4: Enter the search criteria on the appropriate page.

Detailselect whether you are searching for a location or an order. If you are
searching for a location, select the type and enter the ID or enter the Description;
if searching for an order enter the order number.
Driverenter the drivers name in the Name field, or click on the driver in the
list.
Equipmentselect the equipment type and enter the ID in the appropriate fields.
Step 5: Click the Search icon. The results will be listed in the window. To work with
one of the found items, right-click on it and select the desired option from the
menu that pops up.
Operations Guide
531
Note: To save the results of a previous search, such as if you are searching for more than
one item, check the Retain Results box before starting the next search.
Routing Editor Tools Locate ([Ctrl]+[L]) Search icon
532

Changing a Routes Properties in the Routing Editor

Used with: Roadnet
You can change the properties of an active or standard route, including the depot,
preferred runtime, starting time, and other features of the route, as well as assign the
driver, equipment, and route ID.
want to work with.
Step 2: Right-click the route in the Active or Standard Routes window and select
Properties from the menu that pops up, or click the Properties icon on the Routes
toolbar. The Edit Route window opens.
Step 3: Change the route information as needed. See Adding a Route for more
information on the route properties.
Note: If a stop in a rush hour restricted area is placed on a route with a restricted
stop.
Step 4: Click the Save icon, or press ([Ctrl]+[S]) to save the changes.
You can use the Edit Route

window to change the routes
start time, or the driver
assigned to the route.
Operations Guide
533
To delete the route, click the Delete icon in the Edit Properties window. If you delete a
route, all of its orders will move to the Unassigned window.
Routing Editor Routes window Properties ([Ctrl]+[T]) Save ([Ctrl]+[S])
534

Adding a Route
Adding a Route
Used with: Roadnet
Roadnet allows you to manually create routes as needed. Any routes you create are active
routes. Once you have created a route, you can add the stops and sequence them.
want to work with.
Step 2: In the Active Routes or Subset Routes window, click on the Add icon. The Add
Route window opens.
Step 3: Enter the ID for the route. Enter a Description, if desired. The Route Number is
selected by Roadnet.
Hint: Make the ID something meaningful that youll remember when searching for the
route.
If the driver on your route

has a helper, check the
Helper box. If the pay is
evenly split between two
drivers, check Team split.
Step 4: Click on the Origin arrow to open a list of depots. Click on a depot to select it.
This is where the route will start. You must select an origin.
Step 5: To select the travel model that will be used to calculate travel times, click on the
Models arrow to open a list of options; click on an option to choose it. You must
select a travel model.
Operations Guide
535
Adding a Route
select Origin, Last Stop, or a specific depot. If Last Stop is selected, the cost,
distance, and times will not consider any time needed to return to the depot.
Step 7: To assign a driver(s) to the route, click on the Driver arrow to open the Lookup
- Driver window. Double-click on a driver, or click on the driver and then on the
Process icon, to select it.
Step 8: If there is a helper on the route, check Helper. If the driver cost is split evenly
between the two drivers, check Team Split.
Step 9: If the route requires an employee with a specific skill set, choose the necessary
skill set in the Preferred Skill Set field. To choose a skill set, click the Preferred
Skill Set arrow; the Skill Set window opens. Double-click on a skill set, or click
on a skill set and then on the Process icon, to select it.
Step 10: Enter the starting date and time for the route. You can enter the date manually,
or click on the arrow to open the calendar. To change the month, either use the
arrows on the top of the calendar to scroll through the months, or click on the
month and select from the menu that pops up. To change the year, click on the
year and use the arrows to scroll to the correct year. When entering the time, you
can enter the time manually, or use arrows to scroll to the correct time. If entering
the time manually, use the arrow keys to move to from the hour to minute field. If
using the scroll arrows, click on the correct field, (hour or minute) before
scrolling. Use a 24-hour clock when entering the time. For example, enter 1:00
PM as 13:00.
Step 11: Enter the Pref. Time and Max. Time for the route. The preferred time is the
desired length of the route; the route may be longer than this. The maximum time
is the longest the route can be; Roadnet will not create a route longer than the
maximum time.
Step 15: If applicable, select either Specify Time or Use Reload Depot Service Time.
Reload Time is the amount of time needed to reload the truck if it is being sent
out for a second route. To set, select either Specify Time or Use Reload Depot
536

Adding a Route
Service Time. If you selected Specify Time, enter the exact time using the format
HH:MM.
Step 16: Click on the Equipment tab to open the Equipment page. You can assign
specific pieces of equipment to the route, or simply an equipment type. If both
equipment and equipment types are assigned to the route, the equipment is used.
To assign equipment to the route, click on Equipment. Then, click on it in the
Available list and drag it to the Assigned list.
To assign an equipment type to a route, click on Equipment Type. Then, click on
the arrow to open the Lookup-Equipment Type window. Double-click on a type
to select it, or click on a type then on the Process icon.
Step 17: Click the Save icon, or press [Ctrl]+[S] to save the route.
Routing Editor Active Routes window Add ([Insert]) Save ([Ctrl]+[S])
Once a route has been created you can add stops. See Routing Unassigned Stops for more
information.
Operations Guide
537
Working with Preferred Route Properties

If you are using preferred route ID routing when creating your routes, you can create
properties for those routes which will automatically be used when the routes are created.
For instance, if you create a preferred route property with an ID of BAL123, and you have
orders with a preferred route ID of BAL123, when routes are created a route with an ID
of BAL123 will be created and it will contain all the properties outlined in the preferred
route property. Some of the properties you can give to a preferred route are the start time,
preferred and max time, origin and destination, and equipment. These values will be used
instead of the corresponding values specified in the Routing Pass Options notebook.
opens with the Routing Session window visible.
Step 2: Click on the List menu and select Preferred Route Properties. The Preferred
Route Properties window opens, listing all existing preferred route properties.
Step 3: Click on the Add icon. The Add Preferred Route Property window opens.
Step 4: Enter the preferred route ID in the ID field. Enter a Description, if desired.
Enter the preferred route

ID in the ID field.
Step 5: Click on the Origin arrow to open a list of depots. Click on a depot to select it.
This is where the route will start.
Step 6: To select the travel model that will be used to calculate travel times, click on the
Models arrow to open a list of options; click on an option to choose it.
538

select Origin, Last Stop, or a specific depot.
Step 8: To assign a driver(s) to the route, click on the Driver arrow to open the Lookup
- Driver window. Double-click on a driver, or click on the driver and then on the
Process icon, to select it. If the driver cost is split evenly between the two drivers,
check Team Split.
Step 9: If there is a helper on the route, check Helper.
Step 10: If the route requires an employee with a specific skill set, choose the necessary
skill set in the Preferred Skill Set field. To choose a skill set, click the Preferred
Skill Set arrow; the Skill Set window opens. Double-click on a skill set, or click
on a skill set and then on the Process icon, to select it.
Step 11: Enter the starting time for the route in the Start Time field. You can enter the
time manually, or use arrows to scroll to the correct time. If entering the time
scroll arrows, click on the correct field (hour to minute) before scrolling. Use a
Step 12: Enter the Pref. Time and Max. Time for the route. The preferred time is the
desired length of the route; the route may be longer than this. The maximum time
is the longest the route can be; Roadnet will not create a route longer than the
maximum time.
Note: If you are using Mid-Route Sourcing, do not choose Full as a Starting Quantity. If
you do, the route will use As Needed.
Step 16: If applicable, select either Specify Time or Use Reload Depot Service Time.
Reload Time is the amount of time needed to reload the truck if it is being sent
out for a second route. To set, select either Specify Time or Use Reload Depot
Service Time. If you selected Specify Time, enter the exact time using the format
HH:MM.
Operations Guide
539
Step 17: Click on the Equipment tab to open the Equipment page. You can assign
specific pieces of equipment to the route, or simply an equipment type. If both
equipment and equipment types are assigned to the route, the equipment is used.
To assign equipment to the route, click on Equipment. Then, click on it in the
Available list and drag it to the Assigned list.
To assign an equipment type to a route, click on Equipment Type. Then, click on
the arrow to open the Lookup-Equipment Type window. Double-click on a type
to select it, or click on a type then on the Process icon.
Note: If you specify equipment or an equipment type, and none of that type is available
when routes are created, the orders with that preferred route ID will not be routed.
Step 18: Click the Save icon, or press [Ctrl]+[S] to save the preferred route property.
Routing Editor List Preferred Route Properties Add ([Insert]) Save ([Ctrl]+[S])
540

Assigning Drivers and Equipment to Routes

Used with: Roadnet
Once the routes have been created in the Routing Editor, you can assign the driver and
equipment to the route. The Speed Assign option lets you assign all these options at once,
or you can assign them individually using the Route Properties window.
Assigning all the Options at Once
equipment to the route. If you have several routes to assign drivers, IDs, and equipment
to, you can use the Speed Assign window. If you assigned buddy equipment to equipment,
or equipment and IDs to drivers, you can choose to have them automatically assigned to
the route at the same time. The Speed Assign window also lets you assign all the values
you created for a preferred route property to a route. If you are not using preferred route
properties and need to assign the depot, start time, preferred and maximum time, as well
as the driver and equipment, you can use the Properties window.
You can also create dynamic route IDs from the Speed Assign window.
want to work with.
Step 2: In the Active Routes window, select the routes to be assigned. If selecting
multiple routes, [Ctrl]+click the routes.
Step 3: Right-click on a selected route and select Speed Assign ([Ctrl]+[E]) from the
menu that pops up, or click the Speed Assign icon on the General toolbar. The
Speed Assign window opens.
Operations Guide
541
Step 4: The top of the Speed Assign window lists the routes selected to be assigned.
The route currently being assigned is highlighted in the list.
You can have Roadnet assign the equipment
Step 5: If you are going to assign the resources individually, go to Step 6.

If you are using preferred route properties and want to assign those
properties to the route, click the By Pref. Rte. tab. Select the preferred route
property you want to assign to the route and click the [Assign] button.
Step 6: On the By Resources page, select the drivers that will appear in the list.
Allall drivers will be displayed in the list
Having routes preferred skill setonly drivers assigned a skill set that matches
the routes preferred skill set will be displayed.
Capable of performing all activities on routeonly drivers assigned a skill set
that allows them to perform all order activities on the route will the displayed.
Step 7: Select the driver, equipment, and ID to assign to the route.
To assign a driver(s) to the route, click on the driver in the list. If selecting
multiple drivers, [Ctrl]+click the drivers.
To assign equipment to the route, click on the equipment in the list. If selecting
multiple equipment, [Ctrl]+click the equipment.
To assign a route ID to the route, click on the ID in the list.
To assign the drivers route ID to the route, check Pre-fill with drivers route
ID. The driver can be assigned a route ID in the Drivers window.
542

To have Roadnet automatically assign the drivers equipment to the route

when the driver is assigned, check Pre-fill with drivers equipment. The
equipment is associated with the driver in the Drivers window.
To have Roadnet automatically assign buddy equipment associated with a
piece of equipment, check Assign buddy equipment. Buddy equipment is
associated with equipment in the Equipment window.
Notes: You can sort the windows within the Speed Assign window on any column you
want by simply clicking on the column name. See Arranging List and
Maintenance Windows in for more information.
Once an item has been assigned, it is grayed out in the list to indicate that it is not
available to be assigned to another route.
To add a dynamic route ID, click on the Dynamic Route ID icon at the bottom of
the window; the Dynamic Route ID window opens. To add a new ID, click the
Add icon. Enter the ID and Description in the appropriate fields, then click the
Save icon. Click the Close box to close the Dynamic Route IDs window.
stop.
Step 8: Click the [Assign] button. The information is assigned to the route. Continue
assigning the remaining routes, or click the Close box to close the Speed Assign
window.
Routing Editor Active Routes window Speed Assign ([Ctrl]+[E]) Assign
Assigning the Options Separately
equipment to the route. You can use the Route Properties window not only to assign the
driver, ID, and equipment to the route, but also to specify the depot and run times for the
route. If you are assigning multiple routes, use the arrows at the top of the window to
move from one route to another.
want to work with.
Step 2: In the Active Routes or Built Routes window, or on the map, right-click on the
route and select Properties from the menu that pops up ([Ctrl]+[T]) or click the
Properties icon on the Routes toolbar.
Step 3: On the Attributes page, enter the route properties as desired.
To enter the ID, description, load priority, preferred time or maximum time,
type the information in the field.
Operations Guide
543
To choose a depot, driver, model, or color, click on the arrow and select the item
from the Lookup window that opens.
To choose the start time, you can enter the time manually, or use arrows to scroll
to the correct time. If entering the time manually, use the arrow keys to move from
the hour to minute field. If using the scroll arrows, click on the correct field (hour
to minute) before scrolling. Use a 24-hour clock when entering the time. For
example, enter 1:00 PM as 13:00.
Step 4: To assign equipment to the route, click on the Equipment tab to open the
Equipment page. In the Available list, click on the equipment and drag it to the
Assigned list.
Note: If a stop in a rush hour restricted area is placed on a route with a restricted
stop.
Step 5: Click the Save icon, or press [Ctrl]+[S] to save the route assignments.
Routing Editor Route window Properties ([Ctrl]+[T]) Save icon ([Ctrl]+[S])
544

Assigning Sequential Route IDs

Used with: Roadnet
Roadnet gives you the option to assign your route IDs sequentially and add alphanumeric
prefixes to them. For instance, if you wanted to organize your routes geographically, you
could add a citys name, zip code, or any other identifier as your prefix. Prefixes are added
only to routes that you have selected, and the sequence of the routes is based on the order
in which youve selected them.
want to work with.
Step 2: In the Active Routes window, select the routes to which you want to assign
sequential route IDs. If selecting multiple routes, [Ctrl]+click the routes.
Step 3: Right-click on a selected route and select Assign Sequential Route ID from the
menu that pops up, or click the Assign Sequential Route IDs icon on the Routes
toolbar. The Assign Sequential Route ID window opens.
Step 4: Enter the prefix and the starting number, and click [OK] to apply. The total
length of the prefix and starting number cannot exceed 15 characters.
Enter a prefix and starting
number to assign your
route IDs.
Routing Editor Active Routes window Assign Sequential Route ID ([Ctrl]+[I]) [OK]
Operations Guide
545
Assigning Start Times to the Routes in the Routing Editor
Assigning Start Times to the Routes in the Routing Editor

Used with: Roadnet
You can assign a starting time to a route using the Route Properties notebook. But, there
may be times when only the date, or the time, may need to be updated on several routes
simultaneously without changing the other. You can choose to assign either the date or
the time, or both the date and the time, to all the selected routes using Assign Start Time.
Step 1: If necessary, click on the Routing icon to open the Route Editor. The Editor
want to work with.
Step 2: In the Active Routes window, select the routes to which you want to assign the
start time. If selecting multiple routes, [Ctrl]+click the routes.
Step 3: Right-click on a selected route and select Assign Start Time from the menu that
pops up. The Assign Start Time window opens.
The Assign Start Time window lets
you easily assign the same start time
to several routes simultaneously.
Step 4: Check the Date box if you want to assign a date for the route(s) to start. You can
enter the date manually, or click on the arrow to open the calendar. If you are
scroll to the correct time. Click on a date to select it. This option is only available
Step 5: Check the Time box if you want to assign a time for the route(s) to start. You
can enter the time manually, or use the arrows to scroll to the correct time. If
entering the time manually, use the arrow keys to move from the hour to minute
field. If using the scroll arrows, click on the correct field (hour to minute) before
scrolling. Use a 24-hour clock when entering the time for example, enter 1:00
PM as 13:00.
Note: You must select either the date or the time.
Step 6: Click the [OK] button. All selected routes now have the new starting date and/
or time.
546

Splitting an Order
Splitting an Order
Used with: Roadnet
In addition to automatically splitting orders that are too large to fit on the equipment,
Roadnet lets you manually split an order. You can split an order that has been routed, or
you can split an unassigned order so that you can route it. The selections you made on the
Split Orders page of the Options notebook are used to pre-fill some values when the order
is split, but you can change any of the information as needed.
want to work with.
Step 2: In the Active Routes window, double-click on the route containing the order to
be split. The Stops window opens. Double-click on the stop containing the order
to be split. The Orders window opens.
OR
Click on the List menu and select Unassigneds. The Unassigneds window opens,
listing all unassigned stops. Double-click on the stop containing the order to be
split. The Orders window opens.
Step 3: Right-click on the order to be split and select Split from the menu that pops up.
The Split Order window opens.
The Split Orders window

contains information
about the original order
for reference.
Step 4: Enter the Order Number for the split order in the New Order area. This field is
pre-filled with an order number based on the prefix selected in the Options
notebook. This field must be completed.
Step 5: Enter the selector to be uploaded with the original order or the split order. This
field is pre-filled with the value specified in the Options notebook.
Step 6: Enter the quantities for the split order. The quantities for the original order are
displayed in the Order to Split area.
Operations Guide
547
Splitting an Order
Note: If you need to refer to the original order information, it is displayed at the top of
the window in the Original Information area.
Step 7: Click the [OK] button. The split order appears on the same stop as the original
order, or if the original order was unassigned, it appears on the Unassigned list.
From here, the split order can be dragged to another stop or route.
Routing Editor Orders window Split [OK]
548

Saving the Routes Attributes

Used with: Roadnet
You can save the attributes associated with a route so that they are available for future
routes in the same geographic area. For instance, if you like to have the same driver
deliver in an area, and you saved the routes attributes, you could choose the option in the
Routing Pass Options notebook to automatically assign the driver and other attributes to
the route when it is created. The attributes that are saved are:
Route ID
Route Description
Depot
Driver
Start Time
Load Priority
Equipment
Color
want to work with.
Step 2: In the Active Routes or Built Routes window, right-click on the route
containing the attributes you want to save, then select Area Attributes from the
menu that pops up. The Area Attributes window opens.
Note: To save all the routes area attributes at once, click the File menu and select Save
ALL Routes area attributes.
Step 3: To add a new area attribute set, click the Add Icon. The Add a New Area
Attributes Set window opens.
The Area Attributes window is where you

choose saved area attribute sets and days
as well as create and delete attribute sets.
To change the area attributes of an existing set, skip to Step 5.
Operations Guide
549
Step 4: Enter the name of this area attribute set in the New Area Attribute Set ID field.
Click [OK] to close this window and return to the Area Attributes window.
You can create new area attribute sets containing
the attributes of active and built routes, and apply
these attributes to other routes.
Step 5: To change the attributes of an existing set, click the Area Attribute Set arrow
and select the name of the area attribute set you want to change.
Step 6: Select the days with the attributes you want to include in the set. If you dont
want to include a currently selected day, click on the checked box to uncheck it
Note: In order to create or save an area attribute set, at least one day must be selected.
Step 7: When you are finished, click [Save]
To delete an area attribute set, click the Area Attribute Set arrow and select the set name
from the list, then click the Delete icon and [Yes] to confirm.
Routing Editor Active Routes/Built Routes window Area Attributes Add/Delete Area
Attribute Sets [Save]
Editing the Area Attributes
Used with: Roadnet
After you have created your area attribute sets, you may need to change them. For
example, there may be a new driver in the area, or you may have to replace a piece of
equipment.
Note: Changing the area attributes will not affect existing routes, only routes created in
the future.
want to work with.
Step 2: In the Active Routes or Built Routes window, right-click on the route
containing the attributes you want to save, then select Plot from the menu that
pops up. The map opens with the Saved Area Attributes icon visible at the route
centroid.
Note: If the Saved Area Attributes icon is not visible on the map, make sure the Area
Attributes page in the Route Properties notebook is set to display the selected
area attribute set. For more information, see Using Maps in Routing Editor.
Step 3: Right-click on the Saved Area Attributes icon If the icon represents multiple,
stacked saved area attributes, select the one you want to edit from the list that
appears.
550

Step 4: Select Edit from the menu that appears. The Edit Area Attributes notebook
opens.
Step 5: To change attributes, click the Attributes tab. The Attributes page opens.
You can edit the values of the

saved area attribute set,
including description, drivers,
and the color of the icon.
Step 6: Make the desired changes to the area attributes. You can edit the description,
the drivers, the color, the load priority, or the start time.
Step 7: To change equipment, click the Equipment tab. The Equipment page opens.
You can change either the equipment type or the equipment.
Important: The equipment or equipment type specified in the saved attribute set must
match the equipment type assigned to the route. When routes are created, if the
equipment or equipment type saved to the area attributes does not match the
equipment type assigned to the route, the equipment or equipment type in the
saved area attribute set will be ignored.
To change an equipment type, click the Equipment Type arrow and select it
from the list.
To add equipment, click on Equipment, then drag it to the Assigned list.To
unassign equipment, drag it from the Assigned list to the Available list.
Step 8: When you are finished editing the values and the equipment, click the Save
icon, or press [Ctrl]+[S] to save the changes.
Active/ Built Routes windowMap Edit Area Attributes Attributes Equipment
[Save]
Operations Guide
551
Saving the Routes in the Routing Editor
Saving the Routes in the Routing Editor

Used with: Roadnet
Once the routes are created, at any point during the editing and evaluation process you can
save the routes as they exist, so that you do not lose the current status when other changes
are made. In addition, when you choose to leave the Editor, you will be prompted to save
any changes that have been made. You will also be given the option to save the routes
when changing to a new routing session.
When you save a sessions routes, you are saving all the necessary information for the
session, including the routes, stops, and orders, plus information on the equipment,
drivers, and locations that are part of the route. You must be in the Routing Editor to
perform this procedure.
To save the route information:
Click the File menu and select Save.
Depending on your selection in the Options notebook, you may be prompted to compact
the database or it may automatically be compacted after it is saved.
Routing Editor File Save ([Ctrl]+[S])
Note: You can also choose to Save Session As, which creates a new session using the
selected routes and orders, but can have different properties. See Creating a New
Routing Session for more information.
552

Uploading Selectors
Uploading Selectors
Used with: Roadnet
You can assign each order on a route a single character selector which will be uploaded
with the order to the host. The Routing Editor does not use the selector, but it can help
signify orders in your host system. You can assign an upload selector for a single order,
for all the orders for a stop, or for all the orders on a route.
Note: You can also assign the upload selectors from the map. Simply right-click on the
route or stop and select the appropriate menu option from the menu that pops up.
want to work with.
Step 2: To assign the same upload selector to all orders on a route, right-click on the
route in the Active Routes window and select Assign Upload Selector from the
menu that appears.
To assign the same upload selector to all orders for a stop, double-click on the
route in the Active Routes window to open the Stops window. Right-click on the
stop and select Assign, then Upload Selector from the menu that pops up.
To assign an upload selector to an order, double-click the stop the order is on
to open the Orders window. Right-click on the order and select Assign, then
Upload Selector from the menu that pops up.
Step 3: Enter the selector to be uploaded.
You can assign a single upload selector to all
the orders on a route by selecting Assign
Upload Selector from the Route menu.
Step 4: Click the [OK] button to assign the selector to the orders.
Routing Editor Route/Stops/Orders window Assign Upload Selector [OK]
Operations Guide
553
Adding Breaks to a Route in the Routing Editor

Used with: Roadnet
There may be times when you need to add a break or wait to route, such as to allow the
driver a lunch period, or allow the driver to wait and meet a locations time window. You
can have Roadnet automatically assign breaks to a route when the route is created, or you
can assign them manually in the Routing Editor. You can add a break after a stop, a wait
before a stop, or a layover after a stop. All breaks, waits, and layovers can either be paid
or unpaid. Any breaks/waits/layovers that are paid are considered when the total time for
the route is calculated, so they will count against the preferred time and maximum time.
Breaks are displayed in the Stop Type column of the Stops window as a coffee cup; waits
are displayed as a clock; and layovers are displayed as a bed. If the break is paid, a dollar
sign is added to the stop type.
Note: If the Editor is automatically adding breaks and/or waits (set on the Breaks/Waits
page of the Routing Options notebook), you will not be able to add breaks/waits
here.
want to work with.
Step 2: Double-click on the route you want to add the break/wait/layover to in the
Active Routes window. The Stops window opens.
Step 3: Right-click on the stop to assign the wait or break to and select Assign, then
Break/Wait/Layover, from the menu that pops up, or click the Add Breaks icon
on the Stop toolbar. The Assign Break/Wait/Layover window opens.
Breaks, waits, and layovers each have a
unique graphic in the Stop Type column
so that you can easily determine what
kind of stop it is.
To assign a break or layover, right-click on the stop before the break should
occur.
To assign a wait, right-click on the stop after the wait should occur.
Step 4: Select whether a break, wait, or layover is being added in the Type area. Enter
the number of minutes the break should last in the Time field.
Step 5: If the driver is to be paid for the break/wait/layover, check the Paid box.
Step 6: Click the [OK] button to accept the new break/wait/layover. It appears in the
Stops window.
554

Each type of break has an icon associated with it in the Stop Type column. A dollar sign
next to the Stop Type indicates the break is paid.
Icon
Meaning
Icon
Meaning
Icon
Meaning
Break
Layover
Wait
Paid Break
Paid Layover
Paid Wait
To change a break or wait, such as changing the duration, right-click on the break and
select Properties from the menu that pops up.
To remove a break or wait, right-click on the break and select Remove from the menu
that pops up.
Routing Editor Stops window Assign Break/Wait/Layover ([Ctrl]+[B]) [OK]
Operations Guide
555
Inserting a Depot onto a Route

Used with: Roadnet
There may be times when a driver needs to stop at another depot during a route, maybe
because the original depot did not have the product on hand, or another order came in
during the day. To provide for these instances, you can insert depots onto routes in the
Routing Editor. Once the depot has been inserted onto the route, it appears in the Stop list
and on the map. If you decide to sequence, line sequence, or time window the route, each
action will be performed on the group of stops between depots. For instance, if your route
is Depot (Origin), Stop 1, Stop 2, Depot, Stop 3, Stop 4, Stop 5, Depot (Destination), it
will sequence Stops 1 and 2, and then Stops 3, 4, and 5. In addition, you cannot perform
any of the range actions (Sequence Range, Time Window Range, or Standard Route
Sequence Range) on a range of stops that encompass a depot.
Note:
with.
Step 2: In the Active Routes window, double-click on the route you want to work with.
The Stops window for the route opens.
Step 3: Right-click on the stop preceding or following where you want to insert the
depot and select Assign, then Insert Depot from the menu that pops up. The
Insert Depot window opens.
When you insert a depot onto a

route, you can specify the length
of time the driver needs at the
depot in the Service Time area.
Step 4: Choose the depot to be inserted, and specify whether it should be placed before
or after the selected stop.
Step 5: Select either Specify Time or Use Reload Depot Service Time. Service Time is
the amount of time needed to reload the truck if it is being sent out for a second
route. If you selected Specify Time, enter the exact time using the format
HH:MM.
Step 6: Click the Action Taken arrow and select either Fill As Needed, Fill to Capacity,
or Empty. Whatever reload option you choose here will only apply to this reload.
For example, if a fuel truck is typically refilled to capacity upon reload, then
556

select Fill to Capacity. If a waste disposal truck plans on dumping at each depot,
then select Empty. If a food delivery truck plans on only filling the truck with
enough food for its next trip, then select Fill As Needed.
Step 7: Click the [OK] button. The depot is inserted into the route, and appears on the
map and in the Stops list. In the Location Type column, the depots type is DPT,
and the icon is a building with arrows going in and out.
Routing Editor Stops window Assign Insert Depot [OK]
Once the depot has been added to the route, it can be removed or its service time changed
as necessary.
To remove the depot from the route, right-click on the depot and select Remove from
the menu that pops up. The depot is removed from the route.
To change the service time for the depot, right-click on the depot and select Properties
from the menu that pops up. Enter the new service time in the Insert Depot window and
click the [OK] button.
Operations Guide
557
Working with Mid-Route Sourcing Depots on a Route
Working with Mid-Route Sourcing Depots on a Route

Used with: Roadnet
There may be times when you need to remove or replace a Mid-Route Sourcing depot on
the daily route. Maybe the Mid-Route Sourcing depot doesnt have the container size you
need to swap or it isnt accepting a certain type of waste. Or, you might need to change
the service time needed at the depot. To allow for these types of circumstances, you can
make changes to Mid-Route Sourcing depots that are already on a route in the Routing
Editor.
with.
Step 2: In the Active Routes window, double-click on the route you want to work with.
The Stops window for the route opens.
Step 3: Right-click on the Mid-Route Sourcing depot you want to work with and select
the function you want to perform from the menu that pops up.
To remove the Mid-Route Sourcing depot from the route, right-click on the
depot and select Remove from the menu that pops up. The depot is removed from
the route.
To adjust a Mid-Route Sourcing depots service time, right-click on the depot
and select Assign, then Service Time, from the menu that pops up. Choose to
adjust the fixed or variable service time. To adjust the service time manually, click
on Set Time To and enter the new time in the field. To adjust the service time by
a percentage, click on Percentage and use the arrows to change the percent.
Choose whether the time is increased or decreased by that percentage. Click the
[OK] button. The Mid-Route Sourcing depots service time is adjusted.
To replace a Mid-Route Sourcing depot on the route with a different one
from the Available Depots list , right-click on the depot and select Replace from
the menu that pops up. Choose from the Available Depots list, the Mid-Route
Sourcing depot to replace the current one on the route. In the Service Time area,
specify the amount of time that will be needed at the depot. Click Specify Time to
enter the time or Use Depot Service Time to use the service time specified in the
Location notebook. Click the [OK] button. The previous Mid-Route Sourcing
depot is replaced in the stops list with the new one.
Routing Editor Active Routes Stops window Remove/Assign/Replace
558

Adjusting the Service Time for a Stop
Adjusting the Service Time for a Stop

Used with: Roadnet
There may be times when the service time for an individual stop needs to be changed for
that delivery only, or the service times for all the stops on a route need to be adjusted. You
can easily make this adjustment in the Routing Editor using Adjust Service Time. This
option adjusts the service time being used for the affected stops. You can adjust the
service time by a percentage, or change it to a specific time.
Note: The service times established for the stop using this feature will override any other
service times for that stop.
want to work with.
Step 2: To change the service time for all stops on a route, right-click on the route in
the Active Routes window, or on the map and select Assign Service Time from
the menu that pops up. The Adjust Service Time window opens.
To change the service time for an individual stop, double-click the route the
stop is on to open the Stops window, or select the stop on the map. Right-click on
the stop and select Assign, then Service Time, from the menu that pops up. The
Adjust Service Time window opens.
Step 3: Select whether to adjust the Fixed Time or the Variable Time.
Adjust Service Times lets you change the
service time for all the stops on a route at
once to compensate for an uncommon
occurrence, such as a heavy delivery day
when drivers may need to wait to unload.
Step 4: To adjust the service time by a percentage, click on Percentage and enter the
percent to adjust the stops service time. Choose whether the time is increased or
decreased by that amount.
To change the stops service time to a new set amount, enter the new time in
the Time field.
Step 5: Click the [OK] button. The service times are updated.
Routing Editor Active Routes window/Map Assign Service Time [OK]
OR
Routing Editor Stops window/Map Assign Service Time [OK]
Operations Guide
559
Assigning the Load Priority
Assigning the Load Priority

Used with: Roadnet
Roadnet allows you to assign a load priority to routes in the Routing Editor. While
Roadnet does not use this information, it can be sent to the host with the orders so that the
warehouse knows which orders to load first.
want to work with.
Step 2: In the Active Routes window, select the route(s) to assign a priority to.
Step 3: Right-click on a selected route and select Assign Load Priority from the menu
that pops up. The Assign Load Priority window opens.
Step 4: Enter the load priority in the Priority field. If multiple routes are selected, you
can have Roadnet automatically increment the priority for each route, rather than
assigning them manually.
The load priority assigned in Roadnet
can be used to tell warehouse personnel
the order to load the routes.
Step 5: Click the [OK] button. The priority is assigned to the route(s).
Routing Editor Active Routes window Assign Load Priority [OK]
560

Updating the Locations Preferred Route ID

Used with: Roadnet
If you are using preferred route IDs when creating routes, you may want to update your
locations preferred route ID with the current routes ID. You can easily update a single
location, all the locations on a single route, or the locations on several routes. A report is
available that summarizes the updates that occurred.
opens with the Routing sessions window visible. Double-click on the session you
want to work with.
Step 2: To update all the locations on a route(s), right-click on the route in the Active
Routes or Built Routes window and select Update Preferred Route IDs from the
menu that pops up. The Update Preferred Route ID window opens.
To update the location for a stop(s) on a route, double-click on the route
containing the stop; the Stops window for the route opens. Right-click on the stop
and select Update Preferred Route IDs from the menu that pops up. The Update
Preferred Route ID window opens.
After the locations have been updated you
can view a report summarizing which
locations were updated, and, if there were
any locations that were not updated, why
they were not updated.
Step 3: To update the preferred route ID for locations that already have a preferred
route ID, check Overwrite existing Preferred Route ID. If this option is not
selected, only locations that do not have a preferred route ID will be updated.
Note: If an order has a preferred route ID override (the preferred route ID is displayed
in red in the Stops or Orders window) but the location does not have a preferred
route ID, the locations preferred route ID will be updated even if overwrite is not
selected.
Step 4: If you want to select how the information is organized on the report, click the
[Report Options] button. The Update Preferred Route ID Report Options window
opens. You can choose how the locations are grouped in the report, as well as
how they are sorted within the group. Click the [OK] button to save the report
options.
Step 5: Click the [Update] button. The selected locations are updated with the
appropriate preferred route ID. Once the update is complete, click the [View
Report] button to see the report summarizing the update. You can view the report
on the screen, print it, or export it to a file. See Report View Windows for more
information.
Operations Guide
561
Routing Editor Route or Stops window Update Preferred Route ID [Update]
562

Printing Reports in the Routing Editor
Printing Reports in the Routing Editor

Used with: Roadnet
The Roadnet Transportation Suite comes with many different reports that can be used to
inform drivers of their daily routes, as well as track historical data, such as off-day
deliveries. The reports can be previewed or printed in the Reports module or in the
Routing Editor. Some basic instructions for printing reports are listed below; for more
information see Printing Reports, Previewing Reports, and Printing Report Groups in the
Reports section of this manual. A description of each report is also included in the Reports
section of the manual.
To print a saved group of reports:
want to work with.
Step 2: Click on the Reports menu and select Groups, then choose the group. The
Report Data Selection window opens.
Step 3: Choose the date range to print the reports for. The Route Session List displays
the sessions for those dates.
Step 4: Click on the session; the Route List displays the routes for that session. Click on
the routes to include in the reports, then on the [OK] button.
Routing Editor Reports Groups Group [OK]
To preview or print a single report:

want to work with.
Step 2: Click the Reports menu and select List. The Reports window opens listing all
the reports.
Step 3: Right-click on the report, and select either Preview or Print from the menu that
pops up. The Report Data Selection window opens.
Step 4: Enter the selection criteria to define the routes to include in the report and click
the [OK] button.
Routing Editor Reports List Preview/Print [OK]
Operations Guide
563
Printing Driver Directions

Used with: Roadnet
Once the routes have been created, you can print route directions for the driver to use.
These directions can be very helpful to a new driver who is not familiar with the area or
a driver on an unfamiliar route. You can print normal driver directions, which contain
directions to travel from stop to stop, or extended driver directions, which include more
information about the stop, such as time windows and planned arrival times. You can
choose to print the directions with or without maps, or, if printing normal driver
directions, to a file.
Notes: If you were not granted permission to print maps in the Administration module,
you will not be able to print any driver directions that include maps, such as turn
by turn directions.
If a Not Considered location is on the route, the Description and Address for that
stop will be blank on the driver directions.
want to work with.
Step 2: To print extended driver directions, right click on the route(s) in the Active or
Built Routes window, or on a map, and select Print Extended Driver Directions,
then with turn by turn (to print the maps) or without turn by turn (to print without
the maps), from the menu that pops up. If printing with turn by turn, select the
size maps that should be printed with the directions; the smaller the maps the
more directions can fit on a piece of paper.
To print driver directions, right-click on the route in the Active or Built Routes
window, or on a map, and select Driver Directions from the menu that pops up.
There will be a pause while Roadnet calculates the paths from stop to stop.
Step 3: If Driver Directions was selected, the Route Directions for Route window
opens, listing the driver directions. Click on the Print icon and choose the desired
option.
Unformattedprints the directions as they appear on the screen. This option
allows you to print the directions to an ASCII file instead of the printer.
Formattedprints the directions formatted as a report.
Turn by Turnprints the directions with maps for each step in the directions.
You can choose the name that will appear at the top of the report, whether or not
to print an overview map, and the size of the maps to print. The size of the map
dictates how many pages will be needed to print the route.
Note: If you were not granted permission to print maps, you will not be able to print Turn
by Turn driver directions.
If Print Extended Driver Directions without Turn by Turn was selected, the
directions are sent directly to the printer.
564

If Print Extended Driver Directions with Turn by Turn was selected, the
Detailed Map Printer Options window opens. You can change the name that will
print at the top of the map, whether or not to print an overview map, and choose
the size of the maps to print. The size of the map dictates how many pages will be
needed to print the report.
Routing Editor Active/Built Routes window/Map Driver Directions/Print Extended
Driver Directions
Operations Guide
565
Building the Routes
Building the Routes

Used with: Roadnet
Once you have evaluated and edited a route, and it is complete, you can build the route.
A built route will not be changed without a warning. If the option is selected in the
Importer, stops and orders can be added to built routes when subsequent orders are
transmitted.
Note: IDs will be assigned to the routes when they are built if you enabled the option in
the Options notebook. The IDs assigned will use the prefix and numbers specified
on the Auto Assign Route IDs page of the Options notebook.
want to work with.
Step 2: Select the route(s) to be built in the Active Routes window. If selecting multiple
routes, hold down the [Ctrl] key while clicking on the routes.
Step 3: Click on a selected route(s) and drag it to the Built Routes window.
OR
Right-click on a route and select Build from the menu that pops up.
Routing Editor Active Routes window Build
566

Sending Orders from the Routing Editor

Used with: Roadnet
Once you have completed routing, you can copy the orders to your host or elsewhere for
storage or use by other people within your organization. When orders are sent, an ASCII
file is created. The file contains the information that was in the original orders file, plus
additional information specific to the routes. The Send Orders layout specifies where the
additional information will be added to the original file.
Once the export is complete, you can view a report listing any problems that occurred
during the export process.
want to work with.
Step 2: To send all orders, click on the Tools menu and select Send all orders, or click
the Send Orders icon on the General toolbar. The Send Orders window opens.
You can print a report of any orders that were created in Roadnet, such as any split
orders, future orders, returns, or manual orders created in the Maintenance module.
OR
Operations Guide
567
To only send the orders for selected routes, right-click on a route(s) in the
Active Routes or Built Routes window and select Send Orders, or press
[Ctrl]+[N]. The Send Orders window opens.
Step 3: To prevent an ASCII text file from being generated, check the box next to Do
Not Generate Output File (Generate Notifications Only).
Note: This option is enabled only when there are Orders Sent notification recipients
configured in the Administration module. See Working with Notification
Recipients for more information on using this feature.
Step 4: Click the Choose Layout Set arrow to open a list of layout sets and click on the
layout set you want to use. The name and location for the output file is displayed
in the Output File Name field below.
Step 5: To change the name or location of the export file, or review or change the
position and length of fields in the destination file, click the [File Layout] arrow
and select Edit Layout, then the layout name. See Setting the Import File Layouts
or Send Orders Available Fields for more information.
To view a report of the layout being used, including the location and name of the
file being created and the starting position and lengths of the fields in the file, click
the [File Layout] arrow and select Preview from the menu that pops up. The report
will include the layout information for both layouts (import orders and send
orders). The organization of the layouts in the report - separate pages vs.
intermingled - will depend on the import layout report options selected in the
Import module.
Administration module, you will not be able to change any of the options selected
when sending orders.
Step 6: To automatically lock all orders that are sent, check Lock Orders After Sent.
If this option is not selected, orders lock status will not change when you send
orders.
To keep active routes in active status upon sending orders, check Keep
Routes Status After Sent. If this option is not selected, any active routes that
contain an order that is sent will change to built status.
Step 7: To include routed orders that were not imported, such as split orders or
manually entered orders, check Send Orders Which Were Not Downloaded.
To report any routed orders that were not imported, such as split orders or
manually entered orders, check Report Orders Which Were Not Downloaded.
To include breaks, waits, layovers, and mid-route depots, check Send Breaks/
Waits/Layovers.
To select whether the stop numbers are associated with the stop, order, or
location in the upload file, click the Assign Stop Numbers Per arrow and select
the desired option. If per order is selected, each order will have a unique stop
number. If per stop is selected, each stop will have a unique stop number, but all
568

orders for the stop will have the same stop number. Per location is only used if
location substitution is being used. In the upload file, if the original location ID
changes, a new stop number is assigned; if two consecutive orders have the same
location ID they are assigned the same stop number.
To send the orders directly to MobileCast, check Update MobileCast. If any
errors occurred during the push process, click the [View Errors] button to see a list
of the errors. This button will only be available if errors occurred. For more
information on pushing the routes to MobileCast, see Sending the Routes to
MobileCast.
Step 8: To convert all times in the export file to a specific time zone, click Time Zone.
Below, click the arrow and select the time zone all times should be exported as. If
you do not want times to be converted to a different time zone, click Driver's
Time.
Step 9: If you are exporting variable service times, click the Variable Service Time
Format arrow and choose the portions of minutes you want the service times
exported in.
Note: When the service time is written to the text file, the actual decimal point is
removed and a whole number is written to the file; this number will need to be
multiplied by the appropriate amount to reflect the actual time.
For example, a service time of five minutes reads as 0:05.0 in Roadnet. After you
export this value, this five-minute service time will appear as 50. A service time
of four-tenths of a minute, or 0:00.4, will appear in the export as 4.
Step 10: If you are exporting the latitude and longitudes, click on the Latitude/
Longitude Coordinate Format arrow and select the format you want the latitude
and longitude exported in. If you are using decimal degrees fields, enter the
numbers to the right of the decimal you want in the Lat/Lon precision. Choose
whether to have the quadrant on the globe indicated by negative and positive
signs on the latitude and longitude, or have the actual quadrant appear after the
latitude or longitude (ex. 39.2654N).
Note: For the coordinates to export correctly, make sure the punctuation is appropriate
Step 11: Click the [Send Orders] button.
Step 12: To see any errors that occurred during the export, click the [View Errors]
button. If no errors occurred, the button will not be available.
Routing Editor Tools Send ALL Orders [Send Orders]
-ORRouting Editor Active/Built Routes window Send Orders ([Ctrl]+[N]) [Send Orders]
Operations Guide
569
Removing Orders from the Routing Editor
Removing Orders from the Routing Editor

Used with: Roadnet
The Routing Editor allows you to remove orders from the problem and export them to a
file elsewhere, such as on a disk. Exported orders remain in the database until you save in
the Editor, at which time they are removed from the database. When orders are exported,
the pertinent records from the original ASCII file that was imported are transferred to the
designated file. If you are removing orders that were manually entered, the Import Orders
layout in the specified layout set is used to determine the position and length of the fields.
You can export a single order, all the orders for selected stops, or all the orders on selected
routes.
want to work with.
Step 2: In the Active Routes, Stops, or Orders window, select the route, stop, or order to
be exported.
Step 3: Right-click on a selected item and select Remove Orders from Session from the
menu that pops up. The Remove Orders from Session window opens.
If you entered orders in the
Maintenance module, make sure
you specify a layout set that will
be used to determine the order of
information in the exported
records.
Step 4: If you are removing orders that were manually entered, you need to specify
which Import Orders layout to use when creating the ASCII file. Click the
Choose Layout Set arrow to open a list of layout sets; select the layout set you
want to use.
Step 5: Click the [...] button next to the Output File Name field and browse to where
you want the orders saved.
Routing Editor Active Routes/Stops/Orders window Remove Orders from Session Save
570

Sending the Routes to MobileCast
Sending the Routes to MobileCast

Used with: Roadnet
If you have also purchased MobileCast, Roadnet Technologies dispatch tracking system,
you can have Roadnet transfer your route(s) directly to MobileCast. This means that the
Dispatcher does not need to import the routes to track them.
Before you can push the routes to MobileCast, each route being pushed must have an ID
assigned to it.
Note: If you were not granted permission to update MobileCast in the Administration
module, this option will not be available.
want to work with.
Step 2: Right-click on the selected route(s) and select Update MobileCast from the
menu that pops up.
Step 3: Click the [Update] button. The route(s) will be transferred to MobileCast.
Each route being pushed to MobileCast
must have an ID assigned to it.
Note: If any errors occurred during the push process, the [View Errors] button will be
available. Click the button to review a list of the errors.
Routing Editor Routes window Update MobileCast [OK]
Operations Guide
571
Archiving the Routing Session
Archiving the Routing Session

Used with: Roadnet
You create an archive containing all the information in an individual routing session,
which you can then import into another routing session on another computer. When the
archive is created, all necessary information for the session, including employee,
equipment, and location information, is included in the archive. This feature is very handy
if you have multiple routers creating routes for the same day on independent computers,
and all these routes eventually need to be combined into one routing session. The archived
session can be imported into a session on another computer using the Import module. You
can also use this feature if you need to send data to Roadnet Technologies.
want to work with.
Step 2: Right-click on the session in the Routing Sessions window and select Archive
from the menu that pops up, or click the Archive icon. A Save As window opens.
Step 3: Enter the name to archive the session as, and browse to where you want the
archive stored.
Step 4: Click the [OK] button to archive the routing session.
Note: Once an archive has been created, you can import that archive into another routing
session to combine the sessions. See Combine from Archive or Combining
Routing Sessions in the Routing Editor for more information.
Routing Editor Routing Sessions window Archive ([Ctrl]+[V])
572

Combining Routing Sessions in the Routing Editor

Used with: Roadnet
If you have more than one router creating routes for the same region, you may want to
combine all those routes into a single session so you can evaluate the picture for the
complete day, as well as printing reports. When combining sessions, the routes from the
selected source session are added to the existing destination session. The destination
session must be in the database you are currently working with. The source session can
come from two different places: it can be another session in the current database, or, if
you are using an Access database, it can be an archive database that you created.
In order for the sessions to be combined, the following conditions must exist:
into.
if you select Import file, the archive must have been created in the same version of
Roadnet as you are importing into.
You can combine the routes into a single session in either the Maintenance module or the
Routing Editor.
opens with the Routing Sessions window visible.
your selection from the menu that pops up.
Step 2: Click on the File menu and select Combine Routing Sessions. The Combine
Routing Sessions window opens.
Step 3: In the Source area, select the database where the source session exists.
If you selected Import file, click the [...] icon and browse to the database
containing the source session.
Note: If you are not using an Access database, Current database is the only option
available.
Operations Guide
573
Step 4: In the Source Sessions list, select the session containing the routes you want to
add to the destination session.
If both the source session and destination session exist in the same database, you
cannot select the same session for both the Source and Destination.
Step 5: In the Destination Sessions list, select the session the routes should be added to.
Step 6: To only move orders into the destination session that do not already exist there,
check Combine orders from Source that do not exist in Destination.
Step 7: Click [Start] to begin the import process.
Notes: If a routing session is open, it will be closed before the import process begins. If
there are any unsaved changes in the session, you will be asked if you want to save
the changes before it closes.
Active routes cannot be combined, either as source or destination routes. Only
built routes from the source session will be transferred as routes to the destination
session. Orders on active routes will appear in the destination session as
unassigned.
Routing Editor File Combine Routing Sessions [Start]
574

Exporting Routes from the Routing Editor

Used with: Roadnet
Roadnet lets you export information about the stops on selected routes to a data file. This
data file can be used to load routes onto an onboard computer so that the driver can use
the information.
want to work with.
Step 2: To export stop information for all the routes, click on the Tools menu and
select Export All Routes. The Export Routes window opens.
To export stop information for selected routes, select the routes in the Active
Routes window. Right-click on a route and select Export from the menu that pops
up. The Export Routes window opens.
position and length of fields in the destination file, click the [File Layout] button
arrow and select Edit from the menu that pops up. See Setting the Import File
Layouts or Export Routes Available Fields for more information.
To view a report of the layout being used, including the location and name of
the file being created and the starting position and lengths of the fields in the file,
click the [File Layout] button and choose Preview from the menu that pops up.
Step 5: Check Export Complete Route to include breaks, waits, layovers, and mid-route
depots in the file.
exporting routes.
Time.
Step 7: If you are exporting variable service time, click the Variable Service Time
Format arrow and choose the portions of minutes you want the variable service
time exported in.
Note: When the service time is written to the text file, the actual decimal point is
removed and a whole number is written to the file; this number will need to be
multiplied by the appropriate amount to reflect the actual time.
Operations Guide
575
For example, a service time of five minutes reads as 0:05.0 in Roadnet. After you
export this value, this five-minute service time will appear as 50. A service time
of four-tenths of a minute, or 0:00.4, will appear in the export as 4.
Step 8: If you are exporting the latitude and longitudes, click on the Latitude/Longitude
Coordinate Format arrow and select the format you want the latitude and
longitude exported in. If you are using decimal degrees fields, enter the number
of numbers to the right of the decimal you want in the Lat/Lon precision. Select
whether to have the quadrant on the globe indicated by negative and positive
signs on the latitude and longitude, or have the actual quadrant appear after the
latitude or longitude (ex. 39.2654N).
Note: For the coordinates to export correctly, make sure the punctuation is appropriate for
the language setting on your computer.
Step 9: Click the [Export Routes] button. The stops information is sent to a file in the
specified location.
If any problems occurred during the export process, the [View Log] button is
available. Click on the button to view a report indicating the problems that
occurred.
Routing Editor Tools Export All Routes [Export Routes]
OR
Routing Editor Active Routes Export [Export Routes]
576

Creating a New Routing Session

Used with: Roadnet
You can create a new routing session, copying existing routes or only the orders from the
routes into the new session. The new session will contain the properties of the original
session, unless you change them here. By creating a new routing session, you can try
what-if scenarios with actual orders without worrying about altering your routes for the
day.
Routing Sessions window visible. Double-click on the session containing the
orders you want to move.
Step 2: Click on the File menu and select Save Session As The Save Session As
window opens.
When you create a new routing session, you can transfer selected orders from the current
session to the new session.
Step 3: The Save Session As window is pre-filled with the current sessions delivery
date and scenario. Change either of these as needed.
Operations Guide
577
Step 4: Enter a Description for the new session.

Step 5: Check the days deliveries will be made in the Valid Delivery Days area.
Step 6: Choose the method to use to calculate travel times and distances. If XY is
selected, you can choose to have barriers considered or not. If RouteNet or the
SuperMatrix are selected, and you are using a rush hour model, check Advanced
Rush Hour to have the rush hour information used to determine the actual streets
the routes will take. If you are using the SuperMatrix, you need to specify how
you want the Routing Editor to handle locations that have been added since the
SuperMatrix was last built. In the Realtime Updating area, select whether you
want to use XY or RouteNet to calculate the distances to these locations.
directory.
Step 7: To enable the commercial vehicle restrictions feature in the routing session,
check Apply Commercial Vehicle Restrictions. Commercial Vehicle Restrictions
prevent specified equipment types from being routed on street segments that are
considered commercially restricted roads. If it is impossible to reach a stop
without traveling on a street segment that is restricted as well as the equipment
type being restricted, the stop will be routed using the XY method.
Step 8: To enable the road restrictions feature in the routing session, check Apply Road
Restrictions. Road Restrictions prevent specified equipment types from being
routed on street segments with a height limit that is less than the Height
Restriction or a weight limit that is less than the Weight Restriction. To use this
feature, a Height Restriction and Weight Restriction must be entered on the
General page of the Maintenance Options notebook. When the road restrictions
feature is enabled, equipment types that are prohibited from traveling on height
and weight restricted roads will only be routed on street segments that are not
restricted. If it is impossible to reach a stop without traveling on a street segment
that is restricted, the stop will be routed using the XY method and no driver
directions will be generated.
Step 9: Select one of the following rush hour options.
speeds when creating routes in the routing session
creating routes in the routing session
To select the rush hour model, click on the arrow to open the Lookup - Rush
Hour Model window. Double-click on a model to select it, or click on the model
and then on the Process icon. If you are using RouteNet or SuperMatrix and want
to use advanced rush hour features, such as paths, check Advanced Rush Hour
578

Use Historical Traffic Speedsif you want to use historical traffic data when
the routing session.This allows you to choose a time of day restriction model to
designate periods during the day in which restricted equipment types cannot
travel in restricted areas or paths. This prevents some vehicles, such as large
trucks, from being routed on restricted roads while allowing other vehicles, such
as small trucks or vans, to use those roads.
Step 11: To combine multiple orders for a single location so they will be placed on the
same route, check Combine Orders. The orders will only be combined if they
meet the criteria specified on the Combine Orders Options window, which is
If Enable Mid-Route Sourcing is checked, the Combine Orders option will not be
available.
Step 12: To have mid-route sourcing depots added to the route, check Enable MidRoute Sourcing. When this option is selected, mid-route sourcing depots will be
added to the route so a visit can be made between customers in order to pick up
or drop off a container or empty a container of its contents. If Combine Orders is
checked, the Enable Mid-Route Sourcing option will not be available.
Step 13: To update drivers planned work time history based on the routes you create
and edit in Roadnet, check Update Duty Period History. When this option is
selected, drivers' work time history will be updated based on both active and built
routes every time you save the session. The drivers' work time history, also
known as the Duty Period History, is used by the Roadnet Transportation Suite
when determining if duty period rules have been violated. Duty period rules
regulate the length of time that drivers can work and are used to help your
organization comply with safety and labor laws. This option is only available
when you have duty period rules enabled on the Duty Period Monitor page of the
Maintenance Options notebook. You may not want to use this option when you
are experimenting with different route possibilities.
Step 14: Use the Filters area to select which orders will be included in the new routing
session.
To filter the orders by the type of route they are on, select Simple and select
whether to move orders on: active route, built routes, or unassigned orders.
To use a more complicated filter, select Advanced and click on the [Advanced]
button to select the criteria. Select whether to select orders based on quantity,
account type, and/or selectors, and enter the criteria for each. The orders can meet
Operations Guide
579
all the criteria or only one of the specified criteria. Click the [Select] button to
make the selections, and the [Done] button when the selection process is complete.
To remove all orders from routes in the new session, so that you are starting
with a fresh problem, check Unassign all orders in new session.
Hint: To filter orders based on options not available through the advanced query, use the
Search Manager. See Using the Search Manager for more information.
Step 15: Click the [OK] button. The new session is created.
Routing Editor File Save Session As [OK]
580

Rolling Routes and Orders to a New Session
Rolling Routes and Orders to a New Session

Used with: Roadnet
If you are using Roadnet to perform weekly routing, you may want to create new sessions
each day, rolling over the routes already created for subsequent days, while keeping that
days routes in the current session. For instance, if your business week is Monday-Friday,
on Sunday night your router comes in and imports orders for the entire week (MondayFriday); all these orders will go into the Monday routing session. In the Editor, the router
creates routes for the entire week and sends the Monday routes back to the host. Then,
before importing orders again on Monday night, the router rolls all Tuesday through
Friday routes, and any unassigneds, to a new routing session. By using this process, each
session contains only one day worth of routes.
Some important things to remember when using Prepare for Next Day:
a new routing session is created, with a delivery date that is the next business day
all routes that are not built are moved to the new session
all unassigned stops and orders are moved to the new session
Warning: The actions done when Prepare for Next Day is run are permanent and cannot
be undone. Be sure you are ready to run the process before starting this procedure.
Routing Sessions window visible. Double-click on the session containing the
orders you want to move.
Note: Verify that the routes for the current day are built before proceeding.
Step 2: Click on the File menu and select Prepare for Next Day. A message box may
appear; click [OK] to proceed.
Note: If a session with the same delivery date, scenario, and description already exists,
a warning appears giving you the choice to replace the existing session or change
your new session. If you select Replace the existing session is overwritten and all
data in it is lost. If you select Change the Change Session Keys window opens,
where you can change the delivery date, scenario, or description of the new
session you are creating.
Routing Editor File Prepare for Next Day [OK]
Operations Guide
581
Working with Merchandisers

Used with: Roadnet
Sometimes after the driver makes the delivery, a merchandiser needs to follow behind to
set up a display. Roadnet allows you to filter your existing routes to determine which stops
qualify for a merchandiser, and then to route just those stops in their own routing session.
Merchandiser routes can be built and edited in the same manner as delivery routes;
Roadnet simply has a different list of stops to work with.
You can create a new session that will only contain those stops that qualify for a
merchandiser. The session can be for the same day as the delivery or for a different day.
Note: Prepare for Merchandiser is a purchasable option within the Roadnet
Transportation Suite. If you have not purchased this option, the menu will not be
available. Contact your sales representative for more information on Prepare for
Merchandiser.
with.
582

Step 2: Click on the File menu and select Prepare for Merchandising. The Prepare for
Merchandising notebook opens, with the New Session Criteria page showing.
You can create a routing session that only contains orders that a merchandiser
will complete.
Step 3: Select the date the merchandiser will be routed for in the Planned Delivery area.
Step 4: Click on the arrow to open the Lookup - Scenario window. Select the scenario
Roadnet will use when routing the merchandiser.
Note: The service times that will be used to route the merchandiser are determined based
on the scenario selected.
Step 5: Enter a Description for the session.
Step 6: Check the days deliveries will be made in the Valid Delivery Days area.
Step 7: Choose the method to use to calculate travel times and distances. If XY is
selected, you can choose to have barriers considered or not. If RouteNet or the
SuperMatrix are selected, and you are using a rush hour model, check Advanced
Rush Hour to have the rush hour information used to determine the actual streets
the routes will take. If you are using the SuperMatrix, you need to specify how
you want the Routing Editor to handle locations that have been added since the
Operations Guide
583
SuperMatrix was last built. In the Realtime Updating area, select to calculate the
distances to these locations.
directory.
Step 8: To enable the commercial vehicle restrictions feature, check Apply Commercial
Vehicle Restrictions. Commercial Vehicle Restrictions prevent specified
equipment types from being routed on street segments that are considered
commercially restricted roads. If it is impossible to reach a stop without traveling
on a street segment that is restricted as well as the equipment type being
restricted, the stop will be routed using the XY method.
Step 9: To enable the road restrictions feature, check Apply Road Restrictions. Road
restrictions prevent specified equipment types from being routed on street
segments with a height limit that is less than the Height Restriction or a weight
limit that is less than the Weight Restriction. To use this feature, a Height
Restriction and Weight Restriction must be entered on the General page of the
Maintenance Options notebook. When the road restrictions feature is enabled,
equipment types that are prohibited from traveling on height and weight
restricted roads will only be routed on street segments that are not restricted. If it
is impossible to reach a stop without traveling on a street segment that is
restricted, the stop will be routed using the XY method and no driver directions
will be generated.
speeds when creating routes in the routing session
the routing session. This allows you to choose a time of day restriction model to
designate periods in/during the day in which restricted equipment types cannot
travel in restricted areas or paths. This prevents some vehicles, such as large
trucks, from being routed on restricted roads while allowing other vehicles, such
as small trucks or vans, to use those roads.
584

Step 12: To combine multiple orders for a single location so they will be placed on the
same route, check Combine Orders. The orders will only be combined if they
meet the criteria specified on the Combine Orders Options window, which is
If Enable Mid-Route Sourcing is checked, Combine Orders will not be available.
Step 13: To have mid-route sourcing depots added to the route, check Enable MidRoute Sourcing. When this option is selected, mid-route sourcing depots will be
added to the route so a visit can be made between customers in order to pick up
or drop off a container or empty a container of its contents. If Combine Orders is
checked, the Enable Mid-Route Sourcing option will not be available.
Step 14: To update drivers planned work time history based on the routes you create
and edit in Roadnet, check Update Duty Period History. When this option is
selected, drivers' work time history will be updated based on both active and built
routes every time you save the session. The drivers' work time history, also
known as the Duty Period History, is used by the Roadnet Transportation Suite
when determining if duty period rules have been violated. Duty period rules
regulate the length of time that drivers can work and are used to help your
organization comply with safety and labor laws. This option is only available
when you have duty period rules enabled on the Duty Period Monitor page of the
Maintenance Options notebook. You may not want to use this option when you
are experimenting with different route possibilities.
Step 15: Filter the stops from the current session so that only those that qualify are in
the new merchandising session.
To filter the orders by the type of route they are on, select Simple and select
whether to Only use orders on: active route, built routes, or all orders (including
those that are unassigned).
To do a more complicated filter, select Advanced and click on the [Advanced]
button to select the criteria. Select whether to select orders based on quantity,
account type, and or selectors, and enter the criteria for each. The orders can meet
all the criteria or only one of the specified criteria. Click the [Select] button to
make the selections, and the [Done] button when the selection process is complete.
To remove all orders from routes in the new session, so that you are starting
with a fresh problem, check Unassign all orders in new session.
Operations Guide
585
Step 16: To have Roadnet adjust the time windows for the merchandiser route, click on
the Merchandiser tab. Use the information below to complete the fields on this
page.
You can specify how much

time you want to elapse
between when the driver
departs a location and the
merchandiser arrives.
Follow delivery byenter the amount of time after the drivers departure from
the stop to start the time window. If this is left blank, the drivers departure time
is used as the TW Open. This option allows you to specify how closely the
merchandiser should follow behind the driver.
Time window spanenter the length of the time window. If left blank, the end
of the time window will be the same as the stops close time.
Step 17: Check Remove All Additional Service Time from Orders to eliminate
additional service time from all orders in the new merchandiser session.
Note: The only service time that is affected by this option is the service time added
directly to the order; service time associated with the location, stop, or route is not
affected.
Step 18: Click the [OK] button. The new session is created.
Once you have created a session containing the stops for the merchandiser, you can route
the merchandisers as you would a delivery.
Routing Editor File Prepare for Merchandising [OK]
586

Territory Planner - Planning Editor

Creating Strategic Routes in the Planning Editor
Creating Strategic Routes in the Planning Editor

Note: If you were not granted permission to access the Planning Editor in the
The Territory Planner Planning Editor allows you to create strategic routes that consider
your customers delivery history or expected deliveries. Using the customers expected
delivery quantities and delivery frequency options you specify, the Planning Editor
creates cost-efficient routes. Once you have created routes you can transfer selected
information to another planning session, where you can try a different what-if scenario
without losing your original routes. There are even reports you can use to track the
differences for each location when you perform a re-route. In addition to transferring the
routes to another planning session, you can import them into the Roadnet Routing Editor
where they can be used as the basis for your daily routes, or push them directly into the
MobileCast dispatch management system where they can be run as your daily routes.
In order to create these strategic routes, the Planning Editor breaks the problem into two
parts. First, all the locations in the planning session are grouped into geographic areas
called territories. Then, each territory is divided into the specified number of weeks, and
routes are created for each day of the week. Once the routes are created, you can use the
features of the Planning Editor to evaluate and edit the routes as necessary.
In the Planning Editor you can:
Use maps to display and edit territories and routes
Create planning routes
Create planning routes with reloads
Evaluate and edit territories
Evaluate and edit routes
Search for specific territories, routes, stops, and location extensions
Transfer selected location extensions to another session to try a what-if scenario
View how account types are distributed across the territories
Print reports
Print driver directions
Print maps
Send routes to
Send routes to
Send routes to netScheduler
Export the routes to a host computer
Operations Guide
587
Entering the Planning Editor
Entering the Planning Editor

Before doing any work in the Planning Editor, you need to enter the module and select the
planning session you want to work with.
Step 1: Click on the Planning icon to open the Planning Editor. The Editor opens with
the Planning Sessions window visible.
Step 2: Double-click on the session you want to work with. The session opens.
Hint: Within a planning session, you can arrange the commonly used windows to suit
you and then save their size and positions using Windows Favorites.
Subsequently, when you enter the session the windows will automatically open,
already sized and positioned.
588

Maintaining Items in the Planning Editor
Maintaining Items in the Planning Editor

Territory Planner lets you add and maintain employees, equipment, service patterns, and
other resources in the Planning Editor. These items are added and edited in the same
manner as they are in the Maintenance module. General instructions on maintaining these
items are below; for more information see the appropriate section in Maintenance.
Notes: If you do not have rights to the Maintenance module, you will not be able to add
or edit items in the Planning Editor.
Locations cannot be added from within the Planning Editor, and location
extensions cannot be added or changed in the Editor.
Step 1: If necessary, click on the Planning icon to open the Planning Editor. The Editor
opens with the Planning Sessions window visible. Double-click on the session you
want to work with.
Step 2: Click on the List menu and select the item to be maintained. A window opens
listing all of that item that exists.
Step 3: To add an item, click on the Add icon or press [Insert]. The Add window
opens. When the window is complete, click the Save icon, or press [Ctrl]+[S] to
save the new item.
To edit an existing item, double-click on the item, or right-click on it and select
Edit from the menu that pops up. The Edit window opens. Make the necessary
changes and click the Save icon, or press [Ctrl]+[S].
Operations Guide
589
Setting the Options
Setting the Options

The Options notebook lets you specify how the Planning Editor functions and things are
displayed, such as how route and stop exceptions are displayed, the colors used to display
the weeks and days on the map, and the factors that are considered when routes are time
windowed.
the Planning Sessions window visible. Double-click on the session you want to
work with.
Step 3: Select the options as appropriate. The choices on each page are described in the
following sections.
The General page of the Options

notebook lets you select how the
route costs are calculated. The
calculated cost appears in the
Routes window.
Step 4: Click the [Apply] button, then the [Save] button.

Planning Editor Tools Options Apply Save
General
The General page of the Options notebook lets you specify how the routes travel time,
distance, and cost are calculated in the Planning Editor.
To have the stem distance excluded when the routes travel time, distance, and cost are
calculated, check Do not Compute Travel Time and Distance to and from Origin. Stem
distance is the distance from the origin to the first stop and the distance from the last stop
to the origin.
590

Setting the Options
Display
The Display page of the Options notebook lets you choose whether or not to have
additional routing information shown in the Stop list. If selected, additional rows
containing the routes origin and destination, as well as any pre- and post- route stops, will
be shown. In addition, you can select the colors each piece of information will be
displayed in; the routes stops will be displayed in black. The selection made here will
affect how both standard routes and daily routes are displayed.
To have the origin, destination, and pre- and post-route stops displayed, check
Enable Advanced View. In the Row Colors area, click the arrow to open a color palette
and choose the color that will be used for each row.
To use row coloring to show exceptions, check Display Text with Exception Color.
When this option is selected, any windows within Territory Planner that list stops or routes
will display a rows text in color if an enabled exception occurred on that rows stop or
route. The text will appear in the color that is assigned to the exception that occurred.
When more than one exception occurred on a stop or route, the color assigned to the
exception that is highest in the exception list will be used. The text color will remain the
default color for any stop or route where no enabled exceptions occurred.
Note: When the Display Text with Exception Color option is selected, column coloring
will not be used in windows that use row coloring. Column coloring is used in
several columns throughout Territory Planner to alert you of possible problems.
For example, in the Stops window any stop that is unassigned will have red text
in the Route Number column. If you rely on column coloring to alert you, do not
select the Display Text with Exception Color option.
Time Window
The Time Window page of the Options notebook lets you establish the criteria used when
routes or stops are sequenced based on time windows.
To indicate the importance of meeting time windows versus reducing route costs,
move the slider bar at the top of the page. Enter the maximum amount of time the Planning
Editor should spend analyzing each route in the Timeout after field.
To allow the Planning Editor to adjust the start time to meet time windows, check
Adjust Start Times and enter the maximum amount it can be adjusted before (Early) and
after (Late) the current start time, and the increments to adjust it in.
To allow the Planning Editor to add wait times at a stop to meet the open time or
time window, check the appropriate box(es). Enter the maximum amount of time the
driver can wait, and check the Paid box if the driver is paid for the wait.
Operations Guide
591
Setting the Options
Drag/Drop
The Drag/Drop page of the Options notebook lets you specify the default actions that
occur when you drag stops to a territory, week, or route while holding down the left mouse
button, or while holding down the left mouse button and the [Ctrl] key. If you hold down
the right mouse button while dragging, you will get the complete menu so you can choose
the desired option.
To choose the actions that will occur when dragging to a territory, week, or route,
click on the appropriate arrow to open a list of actions. Click on an action to select it. The
choices are to insert:
as first stop
after closest stop
to minimize distance
to minimize cost
to minimize time
to maximize time window performance
as last stop
To specify how the new route will be selected when the stop or location extension is
dragged to a territory or week, choose the appropriate option under Dragging Stops or
Location Extensions to a Week or Territory. If you want to Maintain Currently Assigned
Days, but route location extensions that are currently unrouted, check Assign Best Days
if Unrouted. This is particularly helpful if you are dragging multiple location extensions
simultaneously and want to make sure all are routed.
Colors
The Colors page of the Options notebook lets you specify the colors that will be used to
display the weeks and days on the map.
To select a color for a week or day, click on the arrow next to the color chip to open a
color palette. Click on the color you want to use.
Compact Database Options
As you use Territory Planner to create routes, and especially if you create new sessions,
the database can grow quite large. To help control the size of the database you can specify
to have it compacted when you save and/or exit in the Planning Editor. When the database
is compacted, any items that you deleted are permanently removed from the database.
You can choose to have Territory Planner always compact, never compact, or ask you
whether or not to compact, when you save and exit the Planning Editor.
To select the compact option, click on the appropriate arrow to open a list of options, then
click on an option to select it.
592

Setting the Options
Note: The Compact Database page of the Options notebook is only available when using
an Microsoft Access database.
Exceptions
When routes are created in the Planning Editor you can place restrictions on the route,
such as exceeding size capacity and runtimes. If the route exceeds these restrictions, it is
called an exception. You can monitor any exceptions for a route in the Routes window
and on the map.
Similar to routes, stops can have exceptions. The Route Exceptions and Stop Exceptions
pages of the Options notebook allow you to choose which exceptions you are interested
in tracking, the color associated with the exception, and the order of importance for the
exceptions. The order is important for displaying the exceptions on the map; only the first
exception met for each route or stop is displayed on the map, rather than all exceptions
being displayed. Also, if you use the row coloring feature, the row text for stops and routes
will be in the color associated with the first exception met by that stop or route. All
exceptions for a route or stop are indicated by colored flags in the Exceptions column of
the appropriate window; the color of the flag matches the color chosen on the Exceptions
page. All stops with a specific exception can also be seen in the appropriate window,
which is opened by selecting Exceptions from the List menu in the Planning Editor.
To track an exception, click the box in the Enabled column. A check in the box means
that the item is tracked.
On a map, a route will be

highlighted the color of the
first exception it meets.
To choose the color for an exception, hold down the [Alt] key and click on the color
chip. Click on the arrow that appears next to the color chip and select the new color from
the palette that opens. Press the [Enter] key to accept the new color.
Operations Guide
593
Setting the Options
To change the order of importance for the exceptions, click on the exception to move
and drag it to the desired position in the list. Only the first exception met will be shown
on the map.
The exceptions for each page are listed below.
Route Exceptions
Route exceptions appear when a route exceeds one of the restrictions established in the
routes properties.The Route Exceptions page of the Options notebook lets you choose the
route exceptions you are interested in tracking, the colors associated with the exceptions,
and the order of importance for the exceptions; only the first exception met will be shown
on the map.
See Exceptions for more information on establishing how the exceptions are displayed.
The route exception options are listed below.
Exceeds size 1, 2, 3 capacitythe route contains more product than the equipment can
hold when measured as size 1, 2, or 3.
Exceeds preferred timethe routes total runtime is greater than the preferred runtime.
Exceeds maximum timethe routes total runtime is greater than the maximum
runtime.
Has stop exceptionsone of the stops on the route has an exception.
Time of Day Restriction Violationa stop on the route is in a restricted area at a
restricted time. The route displays on the map showing a dotted path between stops if the
path violates the time of day travel restriction.
Stop Exceptions
Stops can have exceptions that are associated with the location or with the stops
placement on a route. The Stops Exceptions page of the Options notebook lets you choose
the stop exceptions you are interested in tracking, the colors associated with the
exceptions, and the order of importance for the exceptions.
Arrive before open timewhen the stop is routed, the driver is scheduled to arrive
before the stops established open time.
Arrive after close timewhen the stop is routed, the driver is scheduled to arrive after
the stops established closed time.
594

Setting the Options
Work passed close timewhen the stop is routed, the driver is scheduled to arrive at the
stop before the close time, but the service time indicates that the driver will not finish until
after the stops close time.
Missed Time Windowwhen the stop is routed, the driver is scheduled to make the
delivery outside the stops time window.
Time Window Factorthe locations time window factor established in the Locations
notebook is greater than or equal to the Time Window Factor threshold selected below.
For instance, if the Time Window Factor threshold is 4, all locations with a factor of 4 or
5 would be flagged.
Off-day Deliverythe location has a delivery scheduled on a day not selected as a valid
delivery day in the Location notebook.
Time of Day Restriction Violationthe stop is forcing restricted equipment to travel in
a restricted area during a restricted time.
Operations Guide
595
Using Maps in the Planning Editor

In the Planning Editor, maps can be very useful for viewing your routes and territories, as
well as editing them. Some features that are unique to the map in the Planning Editor are
discussed here. See Maps and RouteNet for more information on using the maps.
To open a map displaying a single territory, week, or route, right-click on the territory/
week/route and select Plot from the menu that pops up ([Ctrl]+[P]).
To open a map displaying multiple territories/weeks/routes, select the territories/
weeks/routes in the appropriate window, then right-click on a selected entry and select
Plot from the menu that pops up ([Ctrl]+[P]). A map opens showing the selected
territories/weeks/routes.
To display additional territories/weeks/routes on an open map, right-click on the
territory(s)/week(s)/route(s) in the Territory/Week/Route window and drag it to the map.
You can choose to simply add the territory to the map without changing the view (Add to
view), change the map view to encompass the borders of the new territory (Add and fit)
or change the map view to show all territories (Add and fit all).
To remove a territory(ies) from the map, select the territory(s) then right-click on a
selected territory and select Remove from Map from the menu that pops up. All selected
territories will be removed from the map.
To see the routes on the territory(ies), click on the Map View Mode icon and select
Route View or press [Alt]+[R]. A panel opens at the bottom of the map with buttons for
each week and day. To see the route for a particular day, click on the appropriate week
and day. If your session only covers one week, you only need to select a day. To return to
the Territory View, click on the Map View Mode icon and choose Territory View or press
[Alt]+[T]. A small circle next to the view name indicates which view is currently
displayed.
To work with territories, weeks, routes, or stops on the map, select the item(s) you
want to work with. To select a territory, week, route, or stop on the map, click on the
territory/week/route/stop; to select multiple items, hold down the [Ctrl] key while
clicking. To deselect all selected items, click the Deselect All icon or press
[Ctrl]+[Shift]+[D].
Note: Depending on the maps zoom level, the quantity of routes, and the stops being
displayed, it may be difficult to select a single stop, route, or territory. You can use
the Map Picked Items list to help determine when more than one item has been
selected; in addition, when you drag stops/routes/territories and more than one
item is selected, the cursor changes to indicate multiple items are selected.
In the Planning Editor the map has some extra icons specific to routing. The first icon
(Map View Mode) lets you switch from viewing territories to viewing routes, while the
second icon (Territory Information) lets you choose a territory and open an options menu
to work with that territory. In addition, the Plot Information icon is available; this icon
opens a window to provide information about the territory, location, route, or stop the
596

mouse is currently over. Finally, the Geocode icon lets you geocode a location directly on
the map, without opening the Location notebook.
These icons only appear on the map in the Planning Editor. The first icon, the Map View Mode
icon, lets you change from viewing territories to routes, or territory overview. The second icon,
the Territory Information icon, lists all territories displayed on the map. The third icon, the Plot
Information icon, displays information in a separate window about the territory, route, stop, or
location extension the mouse is currently over. The Geocode icon lets you geocode a location on
the map. The last icon, the Route Summary icon, opens or closes the maps Route Summary
window.
If you have several territories or routes plotted on a map, or more than one map open, there
are several ways you can locate a specific territory, week, or route. You can:
Zoom to a territory, week, or route
Flash a route ([Ctrl]+[H])
Animate the territory, week, or route to help locate it on the map
To use one of these options, select the territory(ies), route(s), or stop(s) you want to view,
then right-click on a selected item and choose the appropriate option from the menu that
pops up.
In addition to the zoom and flash features described above, if you select a territory, route,
or stop in a list window, it will be highlighted on the map.
Operations Guide
597
Plot Info Window
The Plot Info window allows you to quickly view information about territories, location
extensions, routes, and stops that are plotted on the map. You can customize this window
so that it displays the information that is important to your organization. You can also
change the layout of the window so that the information is organized how you like.
To use the Plot Info window, on the map toolbar click the Plot Information icon. To see
information about a feature on the map, simply position the mouse pointer on the feature.
For example, to see information about a territory, put the mouse pointer over the line on
the map that surrounds the territory.
Notes: To prevent the Plot Info window from changing as you pass over another stop,
route, etc., hold down the [Ctrl] key.
You can change the size and shape of the Plot Info window to find the best fit for
your screen. Simply hold the mouse over an edge or the bottom right corner; when
a double-ended arrow appears, simply drag the mouse to size the window.
The Plot Info window provides

information about the location, stop,
territory, or route the mouse is over on
the map.
To customize the Plot Info window, click the Customize This Window icon. Click on
the tab for the plot feature you want to customize the Plot Info window for.
To add a piece of information to the Plot Info window, drag and drop that item from
Available Fields column to the Displayed Fields column. To remove a piece of
information from the Plot Info window, drag and drop that item from the Displayed Fields
column to the Available Fields column.
Note: Information will be displayed in the Plot Info window in the same order as it is
arranged in the Displayed Fields column. You can drag and drop the items in the
Displayed Fields column to arrange the information in the order you desire.
To have information always appear on a new line in the Plot Info window, drag and
drop <Line Break> to anywhere in the Displayed Fields column where you want a new
line to start.
To have the Plot Info window show the description of each piece of information that
is displayed, check Show each fields text label. If this option is not selected, information
598

will be shown without any descriptions. However, you will be able to hover the mouse
over each piece of information to display its description.
Click on another tab to customize the Plot Info window for another plot feature. When
you are finished, click the Save icon. The Plot Info window will appear as you arranged
it until it is changed again. Depending on how the Roadnet Transportation Suite is set up,
changes you make may only apply you or they may apply to all users.
Map Picked Items List
When using a map in the Planning Editor, you may sometimes find it difficult to
determine exactly what is selected on the map, especially if you have several territories
or routes displayed. This can cause problems, because if you choose to perform an action
from the map, such as sequencing a route, that action will be performed on all selected
items, so you may unintentionally sequence a route. To help prevent this problem, you
can open the Picked Items list for the map and see what items are selected. On the selected
items list, you can deselect items you dont want selected, as well as use the same rightclick menus that are available on the map.
The selected item list appears as a notebook, with tabs varying depending on whether on
are viewing the territories or routes on the map. If you are viewing territories, there are
two lists of selected items: Territories and Location Extensions. If you are in the Territory
Overview, only the Territories tab is displayed. If you are viewing routes, you can see the
selected Stops or Routes.
The Selected Items list lets you quickly determine which items are selected on
the map, preventing possible error when performing actions.
To open the Picked Items list, click on the Show Hide Pick List icon or press the [F9]
key. The list opens on the left side of the map with all selected items displayed. As you
select additional items on the map, this list will be automatically updated.
To remove an item from the Picked Items list, hold down the [Ctrl] key and click on it.
After removing the items you do not want selected, click the [Update Map Selection]
button to deselect the items on the map.
Operations Guide
599
To perform an action on the selected items, right-click on a selected item and select the
To close the Picked Items list, click the Show/Hide Pick List icon or press the [F9] key.
To have the map open with the Picked Items list displayed, check the Show Pick List
Notebook option on the General Page of the Map Options notebook.
Using the Map Route Summary Window
If the map is in Route Mode, you can use the Route Summary window to gather
information about the amount of product being delivered for the routes displayed on the
map. The information in the Summary window is automatically updated as changes are
made on the map, such as when you move a stop from one route to another or drag another
territory to the map, making it easy to see the effect of any changes you make. You can
also change what is displayed on the map, and the Summary window, by using the weeks
and days buttons on the map. The Route Summary is attached to the map, so you do not
have to arrange windows to see it and the map simultaneously.
To open or close the Summary window, click the Show/Hide Summary icon on the map
toolbar. Once the Summary window is open, you can choose to see the information
summarized for weeks or days; in addition you can choose the size alias that is used and
whether you want to see the total, average, minimum, or maximum for each piece of
information.
To change the size alias displayed, or the type of information displayed (total, average,
minimum or maximum), click on the appropriate choice.
To switch from displaying summary information by day to summary information by
week, click Week in the Summary area. Likewise, to change from a weekly summary to
a daily summary, click Day in the Summary area.
To print the summary information, click the Printer icon. The information currently
displayed in the window is sent to the printer. All of the information in the list, including
columns that may not be displayed, is printed.
Map Options Notebook
You have some choices regarding how territories and routes are displayed on the map,
including whether the depot is displayed, whether or not unassigned stops are displayed,
and how the stop markers appear on the map. These options are all available in the Map
Properties notebook. To specify your preferences, click on the Options icon and select
Properties from the menu that appears. The Map Properties notebook opens. The first six
pages of the notebook are discussed in Maps and RouteNet; the options on the Territories
and Routes pages are discussed in the following sections.
The General page of the Map Options notebook lets you specify some generic options that
will apply to all maps in the Planning Editor or Routing Editor.
600

To set the speed that territories, routes, etc. will flash when Flash on Map is chosen,
move the Flash Speed slider bar.
To have the map zoom to the selected territory, week, route, or stop before flashing,
check Locate First.
To have the map open with the Picked Items list visible, check Show Pick List
Notebook.
The Territories page of the Map Options notebook lets you specify how the territories will
appear on the map. You must be in Territory View for this page to be available.
In addition to using the Options

notebook to specify whether or not
the depots and unassigned
locations appear on the map, you
can use the [Alt]+[D] and
[Alt]+[U] hot keys to toggle their
appearance directly from the map.
To have locations, unassigned locations, depots, or the territory ID displayed on the

map, check the appropriate box.
Note: You can use hot keys to toggle the unassigned locations and depots on and off.
Press [Alt]+[U] to toggle the unassigned locations and [Alt]+[D] to toggle the
depots.
To have the territory filled with color, instead of just outlined, check Fill Territory.
To select how the locations are displayed, choose the proper Location Marker, Marker
Font, and criteria for coloring the locations (Color By). For each item, click the
appropriate arrow to open a list of options, then click on an option to select it.
To have the locations displayed according to the delivery quantity, check Display
Size as Box and enter the maximum quantities for Small and Medium locations. Each
location will be drawn as a box, depending on its delivery quantity.
To specify whether or not the territory borders are drawn to include the depot, select
With Depot or Without Depot in the Borders area. To not display the borders at all, select
None.
Note: Even if the None option is selected in the Borders area, the Territory Overview
plot automatically displays each territory with border lines, but the territory will
not necessarily include the depot.
Operations Guide
601
The Routes page of the Map Options notebook lets you specify how the routes will appear
on the map. You must be in Route View for this page to be available.
The Routes page of the Map

Options notebook lets you
specify how the routes will
appear on the map, including
the marker shape used to
indicate the stops.
To display the route path between stops, verify that a check is in the Show route paths
box.
To have the route path follow the actual roads, verify that a check is in the Show full
paths box. If this box is not checked, the route path will appear as a straight line.
To specify the width of the route path, enter the desired thickness, in pixels, in the Line
width box.
To have the depot, or route origin, included in the route path, check Show Depot
([Alt]+[D]).
To have unassigned and unrouted stops displayed, check Show Unassigned and
Unrouted ([Alt]+[U]). Unrouted stop markers are magenta with a U on it, while
unassigned stops are displayed using red markers with a U on it.
Note: You can use hot keys to toggle the unassigned locations and depots on and off.
Press [Alt]+[U] to toggle the unassigned locations and [Alt]+[D] to toggle the
depots.
To have the route and stop display any exceptions that are met, check the appropriate
boxes in the Show Exceptions area. If checked, the route color will reflect the first
exception that is met; if checked a colored flag will appear next to a stop for the first
exception it meets. The color and order for the exceptions are specified on the appropriate
Exceptions page in the Options notebook.
To specify how the locations appear on the map, choose the marker, marker font,
marker text, and criteria for coloring the locations (Color By). For each item, click on the
appropriate arrow to open a list of options; click on an option to select it. If choosing a
font, choose the style, type, and size in the Font window that opens and click the [OK]
button.
602

To have locations displayed according to the delivery quantity, check Box Size by
Load and enter the maximum quantities for Small and Medium locations; any location
with a quantity greater than Medium will be drawn as a large location. Each location will
be drawn as a box, depending on its delivery quantity for that day.
The Markers page of the Map Options notebook is available when you are using Depot
Planner to evaluate the location of your depots. On this page you can specify how the
locations appear in Depot Planner.
To choose the marker used to display the locations, click the Location Marker arrow
to open a list of marker and click on one to select it.
To choose the color used to signify unassigned locations, click on the Unassigned
Location Color arrow to open a color palette; click on a color to select it.
Operations Guide
603
Viewing Territories and Routes

Once you have created your territories and routes, you can view them using either the list
windows or maps. The list windows provide more information about the territories and
routes, but the map lets you see how they look graphically. The list windows also let you
drill down from the territory to the week to the routes. Right-clicking on territories and
routes in either the list window or on the map opens a menu from which you can choose
actions that can be performed on the item you clicked.
Viewing Territories
The Planning Editor offers many different ways you can view the territories, and some
helpful tools that provide you with information about your territories.
To see a list of the location extensions that are included in the territory, right-click on
the territory and select Location Extension from the menu that pops up ([Ctrl]+[E]), or
click the Location Extension icon on the Territories toolbar.
To see a list of the locations that are on the territory but have not been assigned to a
route, right-click on the territory and select Unrouted from the menu that pops up
([Ctrl]+[N]) or click the Unrouted icon on the Territory toolbar.
To see the territory on a map, right-click on the territory in the Territories window and
select Plot from the menu that pops up ([Ctrl]+[P]). A map opens with the territory visible.
If you want to add a territory to a map that is already open, right-click on the territory in
the Territories window, drag the territory to the map, and choose the desired fit option.
Hint: If only portions of the territories are visible on the map, click the Fit icon to see
all the complete territories.
To see a specific territory, route, or stop when multiple territories or routes are
displayed on the map, select the items you want to view, then right-click on a selected
item and select Locate, Flash, or Animate (routes only) from the menu that pops up. If you
select Locate, the map zooms to the selected items; if you select Flash the selected items
flash one at a time.
To have the territory borders include the depot when viewed on the map, click the
Options icon and select Properties from the menu that pops up. On the Territories page,
select With Depot in the borders area. To have the territory borders exclude the depot,
select Without Depot.
To view the overlap between territories on the map, plot the territories you want to
view, the click the Map View Mode icon and choose Territory Overview, or press
[Alt]+[O].
To see how the account types are distributed among the territories on the map, click
the Options icon and select Properties. On the Territories page, click the Color by arrow
and select Account Type. The locations will be colored according to their account type.
604

To remove a territory(ies) from the map, select the territory(s) then right-click on a
selected territory and choose Remove from Map from the menu that pops up. All selected
territories will be removed from the map.
To change the map from the territory view to the route view, click the Map View
Mode icon and select Route View ([Alt]+[R]).
Viewing Routes
The Planning Editor has many ways that you can view your routes, and several tools to
help you analyze the routes.
To view the routes in a list window, double-click on the territory to open a list of weeks.
Double-click on the week to open a list of the daily routes. To view the stops on a route,
double-click on the day.
To see the route on a map, right-click on the route in the Routes window and select Plot
from the menu that pops up ([Ctrl]+[P]), or click the Plot icon on the Route toolbar. A
map opens. At the bottom of the map, select the week(s) and day(s) you want to see routes
for. If you want to add a route to a map that is already open, right-click on the route in the
Route window, drag the route to the map, and choose the desired fit option.
Hint: If only portions of the routes are visible on the map, click the Fit icon to see all the
complete routes.
To remove a route(s) from the map, select the route(s) then right-click on a selected
route and select Remove from Map from the menu that pops up. All selected routes will
be removed from the map.
To change the map from viewing territories to viewing routes, click the Map View
Mode icon and select Route View ([Alt]+[R]). To switch from the Route View to the
Territory View, click on the View icon and select Territory View ([Alt]+[T]).
To have the displayed routes follow the actual roads on the map, instead of simply
drawing straight lines from stop to stop, click the Options icon and select Properties. On
the Routes page, check Show Full Paths and Show Route Paths. The routes will be
redrawn using the actual roads.
Operations Guide
605
Using the Toolbars
Using the Toolbars

The Planning Editor includes toolbars that allow you to quickly and easily perform
several common tasks. To use the toolbar, open it and drag it to an accessible, yet out of
the way place, on the screen; when you need to perform a task simply click the appropriate
icon on the toolbar. In many cases, this is quicker and easier than using the corresponding
menu option. The following toolbars, and the tasks you can perform from them, are
available in the Planning Editor:
Generalincludes icons for Make Territories, Assign Days, Locate, Territory
Scoreboard, Route Summary, and Unassigneds. These options will be available once you
are working in a session.
Territoryincludes icons for Unrouted, Location Extension, Assign Sequential
Territory ID, and Balance. These options are available when at least one territory is
selected.
Locationincludes icons for Assign Break/Wait, Speed Editor, Suggest Territory,
Locate on Map, and Flash on Map. These options are available when at least one location
extension is selected.
Routingincludes icons for Plot, Properties, Assign Sequential Route ID, Sequence,
Flip, Time Window, Line Sequence Midpoint, Line Sequence Endpoint, Locate on Map,
and Flash on Map. These options are available when at least one route is selected.
the Planning Sessions window displayed.
Step 2: Click on the Tools menu and select Toolbars, then the toolbar you want to open.
Planning Editor Tools Toolbars General/Territory/Location/Routing
Step 3: Move the toolbar where you want it to be located on the screen. The toolbar will
reopen in that position next time you enter the editor. You can dock the toolbars
to the top, bottom, or either side of the editor window, or place them within the
window.
Step 4: Open other toolbars and position them as desired.
To use one of the options on a toolbar, simply click on it to launch the action. The icon
for each action is shown in the instructions for the action.
The icons available in each toolbar, and the action associated with it, are shown in the
following tables.
606

Using the Toolbars
General Toolbar
Icon
Name
Action
Make All
Territories
Opens the Make Territories window, where you can

choose the options or run Make Territories on all
location extensions.
Assign Days
Opens the Assign Days window, where you can

choose the options or run Assign Days on all
territories.
Locate
Opens the Locate window, which you can use to

find a location, driver, or equipment on a territory,
week, or route.
Territory
Scoreboard
Opens the Territory Scoreboard, which shows

statistical information about the territories.
Route Summary
Opens the Route Summary, which shows statistical

information about the routes.
Unassigned
Opens the Unassigned window, which lists all

location extensions not assigned to a territory.
Territory Toolbar
Icon
Name
Action
Unrouted
Opens a list of location extensions in the territory

that have not been placed on routes.
Location
Extension
Opens a list of location extensions assigned to the

territory.
Assign
Sequential
Territory ID
Opens the Assign Sequential Territory ID window,

where you can specify a prefix and starting number
that will be used for the selected territories new
IDs.
Balance
Territories
Balances the selected territories using the

parameters last saved in the Make Territories
Options notebook.
Operations Guide
607
Using the Toolbars
Routing Toolbar
Icon
Name
Action
Plot
Opens a map showing the selected routes.
Route Properties
Opens the Route Attributes notebook, showing the

attributes for the selected routes.
Assign
Sequential Route
ID
Opens the Assign Sequential Route ID window,

where you can specify the prefix and starting
number that will be used for the selected routes
new IDs.
Sequence
Sequences the selected routes based on least

distance.
Flip
Reverses the stop order on the selected routes.
Time Window
Sequences the selected routes based on the stops

time windows and the selections made in the
Options notebook.
Line Sequence
Midpoint
Sequences the selected routes based on the travel

time between stops, using the stop that is furthest
from the others as the starting point.
Line Sequence
Endpoint
Sequences the selected routes based on travel time

between stops, using the two stops that are farthest
apart as the first and last stops.
Locate on Map
Zooms an open map to the route.
Flash on Map
Flashes the route on an open map.
608

Using the Toolbars
Location Toolbar
Icon
Name
Action
Assign Break or
Wait
Opens the Assign Break/Wait window, where you

can associate a break, wait, or layover with the
location/stop.
Speed Editor
Opens the Speed Editor, where you can review the

locations current delivery information and change
it as necessary.
Suggest
Territory
Opens the Suggest Territory window, where you

can have Territory Planner suggest the best route
for the location extensions based on the criteria you
specify.
Locate on Map
Zooms an open map to the route.
Flash on Map
Flashes the route on an open map.
Operations Guide
609
Creating the Territories
Creating the Territories

Before you can create routes, the locations to be routed must be divided into geographic
areas called territories. You can specify how you want your territories created (clusters or
spokes), as well as the number of territories you want to create or the average of a size,
number of stops, number of locations, or other criteria. Once the territories have been
created the Planning Editor has several tools you can use to evaluate and edit the
territories.
work with.
Step 2: To make territories for all locations in the session, click on the Tools menu
and select Make Territories ([Ctrl]+[K]), or click the Make All Territories icon on
the General toolbar. The Make Territories window opens.
To make territories using only locations not already on a territory, select the
locations in the Unassigned window. Right-click on a selected location and
choose Make Territories from the menu that pops up. The Make Territories
window opens.
To create territories from selected existing territories, select the territories in
the Territories window. Right-click on a selected territory and select Make
Territories from the menu that pops up. The Make Territories window opens.
Step 3: To make territories using previously established parameters, click the [Start]
button. Check Show Progress Indicator to have the progress of the territory
creation process graphically displayed. During the territory creation process, you
can stop the process by clicking the [Accept] button.
To exit without making territories click the [Cancel] button.
To set up the parameters that will be used, click on the [Options] button. The Make
Territories Options notebook opens. See Make Territories Options Notebook for
more information.
Note: If you were not granted permission to change Make Territories Options in the
Administration module, you will not be able to open the Make Territories Options
notebook.
Step 4: Once the territories have been created, use the features of the Planning Editor to
evaluate and edit the territories.
Planning Editor Tools Make Territories ([Ctrl]+[K]) [Start]
610

Using the Make Territories Options Notebook

The Make Territories Options notebook gives you many choices on how you want your
territories created in the Planning Editor. You can specify the number of territories you
want created or the average number of stops, locations, or quantity in each territory, and
even the general shape of the territories.
The Make Territories Options notebook is opened by clicking the [Options] button on the
Make Territories window.
General Page
The General Page of the Make Territories notebook lets you specify the basic parameters
that will be used when your territories are created, such as the number of territories you
want to create and the shape of the territories. Each of the options on the General page is
explained below.
Clusters is the most common

strategy selected for making
territories. If you choose
cluster, you can also specify
secondary criteria, as well
as optimization parameters.
Step 1: Choose a strategy for creating the territories. The strategy you select will affect
the shape of the territories that are built. This choice will be the most important
criteria that is usde when creating the territories. You can also choose to create
proportional territories based on the capacity of the available equipment types.
Clustersthe most common choice. The cluster strategy attempts to create
territories where the locations are closely grouped together around the depot,
which is near the center of the territory. If you choose this strategy you can specify
the number of territories you want created and have the Planning Editor calculate
the average number of stops, quantity, locations, and service time for each
Operations Guide
611
territory. Or, you can specify the average number of stops, quantity, locations, and
service time you want in each territory and let the editor determine the number of
territories that will be needed. This choice will be the most important criteria that
is used when creating the territories. You can also choose to create proportional
territories based on the capacity of the available equipment types. The cluster
option also lets you choose secondary balance criteria, and to optimize the
territories.
Spokes (radiating from depot)the spokes strategy creates territories that are
oriented to each other like the spokes of a wheel, with the depot at the center of
the spokes. If you choose this strategy you can specify the number of territories
you want created and have the Planning Editor calculate the average number of
stops, quantity, locations, and service time for each territory. Or, you can specify
the average number of stops, quantity, locations, and service time you want in
each territory and let the editor determine the number of territories that will be
needed. Alternatively, you can choose to create proportional territories based on
the capacity of the available equipment types using this strategy.
Depot Distance Onlythe simplest strategy of all. The depot distance only
strategy simply groups the locations in territories according to the nearest depot.
If you choose this option you can not specify the number of territories you want
made, any optimization parameters, or any of the options on the Advanced page.
Step 2: If you choose the cluster or spokes strategy, specify the primary criteria for
creating territories. Select either Specify Number of Territories or Specify Goals.
If you chose Specify Number of Territories, enter the number of territories you
want created; the Planning Editor calculates the average number of stops,
locations, quantity, and service time for each territory.
If you chose Specify Goals, select the parameter you want to set the goal for and
enter the average you want in each territory; the Planning Editor will calculate the
number of territories needed to meet that goal.
If you chose the depot distance only strategy, skip to Step 4.
Step 3: If you want equipment types to be considered when making territories, choose
from the options in the Equipment Types area.
If you only want locations assigned to a territory that use an allowed
equipment type, check Enforce Location Equipment Type Restrictions. Allowed
equipment types are assigned to the location on the Equipment Types page of the
Location notebook. The number of territories defined in the Primary Criteria
cannot exceed the number of resources defined on the Resource page.
If you chose to make proportional territories according to the capacity of
your equipment types, check Use Equipment Types To Specify Goals and select
612

the appropriate Equipment Type Usage method: Use All or Fill Each. You will
also want to specify the Primary Criteria to use.
Use Allall available pieces of equipment will be used when creating the
territories.
Fill EachTerritory Planner will determine the optimum amount of equipment
to use, based on the equipment types you have selected
Step 4: Click to complete another tab or click [Save] or [Apply].
Reloads Page
The Reloads page of the Make Territories notebook lets you enable reloads and allows
you to specify the estimated number of reloads and estimated reload service time.
Although Make Territories does not create routes, it will calculate the number of
territories to create based on possible reloads that will be generated when the routes are
created.
Note: Reloads is best used with Make Territories when Equipment Type Usage is
selected as part of the territory creation strategy. For more information on
Equipment Type Usage, see Make Territories Options Notebook - General Page.
Step 1: Check Enable Reloads to allow the equipment to be reloaded.
Step 2: Enter the Estimated Number of Reloads per Route. This is the number of
reloads you plan to have on a route per territory.
Step 3: Enter the amount of time you may need to reload your equipment in the
Estimated Reload Time field using the format HH:MM.
Optimization Page
The Optimizations page of the Make Territories notebook lets you specify the secondary
criteria that is used when creating and optimizing the territories, as well as place some
limits on the optimization process. These options are only available if the Cluster
strategy was selected on the General Options page.
Step 1: Move the slider bars to indicate the relative importance of balancing the
territories on that factor. The options are the same as on the General page, where
you selected the primary balance criteria, with the addition of balanced runtime.
The Balanced Run Times slider works a little differently than the other slider bars.
If the slider is maximized (High), the effort to create territories with balanced
runtimes is greater than the effort to balance territories on the criteria selected on
the General page. If the slider bar is minimized (Low), no effort will be made to
create territories with balanced runtime.
Operations Guide
613
Notes: Leave the slider bar for your selected primary criteria at High; moving it will not
change the balance on that option.
If you chose to make territories by equipment type, make sure to set the slider bar
of your primary criteria to High.
Step 2: If you want to optimize the territories, check Enable Optimizations and choose
when the optimization process should stop. You can specify the number of
iterations the optimization should include, or you can let the software decided
when no improvements can be made.
Account Guidelines Page
The Account Guidelines page of the Make Territories notebook lets you specify which
account types must be included in every territory, and how many must be in each
territory. For instance, your business may require that each territory contain at least one
large grocery store. You could simply set up a grocery account type, assign it to the
appropriate locations, and then specify here that each territory must contain at least one
grocery store. The account guidelines are only available if the Cluster strategy was
selected on the General page.
Step 1: Check the Enable Guidelines (Only available for Clusters strategy) box and
select the account types that must be included in every territory from the list
below.
Step 2: Choose whether to specify that each territory must contain a certain number of
that type (Minimum number of each type desired per territory) or whether the
number in each territory is based on the primary criteria (Use whatever number
corresponds to this percent of a territorys primary criteria).
Resources Page
The Make Territories Options notebook gives you many choices on how you want your
territories created in the Planning Editor. You can specify the number of territories you
want created or the average number of stops, locations, or quantity in each territory, and
even the general shape of the territories. You can also specify how many pieces of each
equipment type are available to make territories, and determine the order in which you
want the equipment types to be used.
The Resources page of the Make Territories notebook lets you indicate which depots are
active, and the number of pieces of equipment that are available at the depot. When
territories are created only depots that are assigned resources will be given territories, but
all depots with resources will be considered. So, if you do not want a depot to be used,
make sure it has no resources assigned to it.
614

Step 1: To specify how many pieces of each equipment type are available, double-click
on the appropriate Equipment Type ID in the top window, Equipment Types. The
Modify Equipment Type window opens. Enter the number of pieces of that type
available and click the [OK] button. Or, hold down the [Alt] key and click on the
Resources column for that equipment type. Enter the number of trucks and press
[Enter].
Step 2: To assign resources to the depot, double-click on the entry in the Resources
column in the bottom window, Depots. The Modify Depot window opens. Enter
the number of resources and click the [OK] button. Or, hold down the [Alt] key
and click on the Resources column for that depot. Enter the number of trucks and
press [Enter].
Step 3: If you selected Enforce Location Equipment Type Restrictions or Use
Equipment Types To Specify Goals, drag and drop the equipment types so that
they are listed in the order you want them considered when creating territories.
Step 4: Click [Save] or [Apply] to save the settings.
Note: If more territories are requested than equipment is assigned to the depots, the
remaining territories will be assigned to the default depot specified in the Options
notebook.
Operations Guide
615
Evaluating the Territories

Once you have created your territories, you can use the features of the Planning Editor to
evaluate the territories and edit them as necessary. You can view the territories on a map,
or in a list window, as well as using the features below to evaluate the territories.
List Windows
The Territory list window provides a lot of information about each territory, as well as
totals information for all the territories. For instance, you can use the appropriate column
to see how well the territories are balanced on your selected primary criteria. To see the
list of location extensions assigned to the territory, right-click on the territory and select
Location Extensions from the menu that pops up, or click the Location Extension icon on
the Territory toolbar. To see a list of all location extensions that were not assigned to any
territory, click the List menu and select Unassigned.
The Territory list window provides a lot of information about the territories. You can
arrange the columns so you can easily see the information that is important to you.
Map
You can use the map and its features to visually evaluate the territories. To display a
territory on a map, right-click on the territory and select Plot from the menu that pops up.
See Viewing Territories and Routes in the Planning Editor for more information.
Territory Scoreboard
The Territory Scoreboard, opened by selecting Territory Scoreboard from the File menu
([Ctrl]+[D]) or clicking the Territory Scoreboard icon on the General toolbar, provides an
easy way to evaluate all the territories in the planning session. It displays totals, averages,
minimum and maximum values, as well as variance information for all three size aliases,
service time, and the number of locations and stops. The bottom of the window provides
616

geometric and geographic information about the territories, including the total area, total
overlap, and the extreme latitude and longitude for all the territories.
The Territory
Scoreboard shows a
score for all territories
based on the primary
and secondary criteria
selected in the Make
Territories Options
notebook.
In addition, there is a score at the top that reflects the primary and secondary criteria
settings in the Make Territories Options notebook. As you move locations between
territories, this score will be updated to reflect the move, making it easy for you to see if
the move improved or lowered the score.
Planning Editor File Territory Scoreboard ([Ctrl]+[D])
Note: The Equipment [Options] and Score Weighting Factors [Adjust] buttons allow
you to change the settings of the parameters used to calculate the score. The
Equipment [Options] button enables you to switch on the option to make
territories according to equipment type and allows you to adjust the primary
criteria for scoring. When you create territories by equipment type, the primary
criteria calculations are expressed in percentages that are determined by how
much of the equipments capacity is used. The Score Weighting Factors [Adjust]
button opens a window with the eight slider-bars showing the settings that were
established in the Make Territories Options notebook. You can change the settings
here if desired; the score will be updated to reflect the changes, which will also
appear in the Make Territories Options notebook. To close these windows without
changing any settings, press the [Esc] key.
Territory Analysis
The Territory Analysis window, opened by right-clicking on a territory and selecting

Territory Analysis from the menu that pops up, provides statistical and geometric
information about a single territory. You can view information about the territorys
Operations Guide
617
centroid and area, as well as the actual percent value of the total for each size, service
time, number of locations, and stops. The bottom of the window lists the other territories,
and the amount of overlap between each territory and the territory being analyzed. If you
leave the Territory Analysis window open while editing the territory, it will automatically
be updated with new information.
You can use the

Territory Analysis
window to
determine which
territories overlap
the selected
territory and by
how much.
In addition to viewing this information, you can perform some actions from this window.
To balance the analyzed territory with another territory from this window, simply select
the other territory(s) in the Overlapping Territories: list and click the [Balance] button.
The territories will be balanced based on the last options saved in the Make Territories
Options notebook.
To print the Territory Analysis window, click the Printer icon.
Viewing Overlap Between the Territories
Overlapping territories are often a sign of poorly constructed territories, which in turn will
produce less efficient and cost-effective routes. The Territory Scoreboard tells you how
much total overlap you have between all your territories, and the Territory Analysis tells
you the amount of overlap between one territory and the others, but the Territory
Overview lets you see the actual territories and overlap on the map.
Step 1: Open a map with the pertinent territories displayed.
Step 2: Click on the Map View icon and select Territory Overview, or press [Alt]+[O].
The map changes to show the filled territories on a black background, making it
easy to see any overlap between the territories.
618

Viewing Account Type Information for the Territories
To view account type information for the territory(s), right-click on the territory and
choose Account Type Summary from the menu that pops up. The Account Type
Summary window opens showing the actual number of each account type on the territory;
to see the value as a percentage of the overall territory, click Values as Percentages.
To view the account type information for all territories, click File, then scroll to Account
Type Summary. The Account Type Summary window opens, displaying the account type
information for all the territories.
You can use the Account Type Summary to determine how

many of each account type exist on the selected territory.
Operations Guide
619
Editing the Territories

As you are evaluating the territories you may want to change them, moving locations from
one territory to another, or even unassigning locations, to help balance the territories or
reduce overlap. You can move the locations around using either the map or the list
windows.
Hint: If the Territory Scoreboard is open, the score will automatically update to reflect
any moves you make.
If using the map to move locations, select the location(s) you want to move to a new
territory and drag it to its new territory.
If using list windows to move locations, right-click on the Territories window and select
Location Extensions from the menu that pops up. In the Location Extensions window,
select the location extension(s) you want to move to another territory. Right-click on the
selected extension(s) and drag it to its new territory.
To move unassigned location extension(s) to a territory, select them in the Unassigned
window. Right-click on the selected unassigned(s) and drag it to its new territory.
When you release the mouse button from dragging the assigned or unassigned location
extension, the Moving Stops to a Territory window opens. Choose how you want the
location extension(s) routed on the new territory. The options are:
Maintain Currently Assigned Daysmoves the location extension to the new
territory and adds it to the daily route(s) for the day(s) it is currently assigned to
on the old territory. Select an option in the Insert on Route box to specify how you
want the stops placed on the routes.
Assign Best Daysplaces the stops on the routes based on the option you select
in the Insert on Route box.
Unroute on New Territorymoves the location extension to the new territory
but does not place it on a route; it is unassigned on the territory.
Insert on Route(s)specifies where on the daily route to place the moved
location extension(s).
Note: If you hold down the left mouse button, or the left mouse button and the [Ctrl] key,
when dragging the extension, it is placed on its currently assigned day. The stops
sequence on the route is based on the selection made on the Drag/Drop page of the
Options notebook.
To have the Planning Editor suggest which territory to place the location extensions
on, right-click on the location extension and select Suggest Territory from the menu that
pops up. The Suggest Territory window opens. Choose Unrouted in the Placement in
route section. Select the other options as necessary and click [Suggest]. The Planning
Editor will suggest the possible territories with the best suggestion highlighted. For more
information on letting the Planning Editor suggest the best territory, see Letting the
Planning Editor Suggest the Territory or Routes.
620

If there are some territories that are unbalanced, you can let the Planning Editor balance
only those territories. In the Territories window, select the territories you want to balance.
Right-click on a selected territory and choose Balance Territories from the menu that pops
up ([Shift]+[B]), or click the Balance icon on the Territory toolbar.
Note: When you balance territories, the saved options in the Make Territories Options
notebook are used as guidelines.
If you balance territories when the Enforce Equipment Type Restrictions is turned
on, the balance will not put a location in a territory where the assigned equipment
types are prohibited. The quality of the balanced territories can be limited by the
available locations and their assigned equipment types.
If you balance territories when the Use Equipment Types To Specify Goals option
is turned on, the balance will be proportional based on the equipment types you
have selected.
Operations Guide
621
Assigning Drivers, Equipment, and Other Items to a Territory

You can assign several properties to a territory, such as a driver, depot, equipment, even
a travel model if necessary. When the territory is created, it is automatically assigned the
depot and travel model (if you are using XY as the time/distance calculation method)
specified on the Routing page of the Options notebook. You can change any of these items
for a territory at any time.
Note: You can also assign depots, models, drivers, and equipment to the territory by
selecting the item from the List menu to open its list window. Drag the territory to
the item in the window; it is now assigned to the territory.
the Planning Session window visible. Double-click on the session you want to
work with.
Step 2: In the Territories window, right-click on the territory you want to work with and
select Properties from the menu that pops up ([Ctrl]+[T]), or select the territory
and then click the Properties icon on the Territory toolbar. The Properties
notebook for the territory opens.
If the territory has two drivers

and the cost should be split
evenly between them, check Team
Split.
Step 3: Change the information as needed. To change the ID or Description, enter the
new information in the appropriate field. To change the driver, travel model, or
depot, click on the appropriate arrow, then click on an option to select it. To
change the equipment, click on the Equipment tab. Drag the equipment to and
from the Assigned window as necessary.
Note: If you have several territories that you want to change the ID for, and the new IDs
will all be sequential, use Assign Sequential Territory ID.
Step 4: Click the Save icon, or press [Ctrl]+[S] to save the territorys new attributes.
622

Planning Editor Territories Window Properties ([Ctrl]+[T]) Save icon ([Ctrl]+[S])
Operations Guide
623
Viewing Account Type Distribution Information
Viewing Account Type Distribution Information

You can categorize the types of businesses you deal with by account type. One benefit of
categorizing your customers this way is that you can determine how much of your
business goes to the different types of accounts. For instance, you may want to see how
much you deliver to bars versus restaurants or grocery stores. The Account Type
Summary window in the Planning Editor lets you see this information as either actual
numbers or percentages of the total value for all the territories or for individual territories.
the Planning Sessions window visible. Double-click on the planning session you
want to work with.
Step 2: To view the account type information for all the territories, click on the File
menu and select Account Type Summary. The Account Type Summary window
opens.
To view the account type information for an individual territory(ies), rightclick on the territory in the Territory window and select Account Type Summary
from the menu that pops up. The Account Type Summary window opens.
You can easily see how your account types are distributed in the
Account Type Summary.
Step 3: The Account Type Summary window provides information about all your
established account types, including the total quantity for each size alias, the
number of locations and stops with the account type, and the total service time
for all the stops.
By default, the Account Type Summary window shows the account type
information as the actual values. To view the information as percentages of the
total value, click on Value as Percentages.
Planning Editor File Account Type Summary
OR
Planning Editor Territories Window Account Type Summary
624

Adding a Territory
Adding a Territory
Territories are created automatically when you import location extensions with territory
information or run Make Territories. However, you may find that you need to manually
create territories from time to time. For instance, you could create a territory that contains
all the stops that you want to transfer to another planning session using Session Transfer.
When you create a new territory you can assign a driver, equipment, and other properties
associated with a territory.
want to work with.
Step 2: On the Territory window, click on the Add icon or press [Insert]. The Add
Territory window opens.
Step 3: Enter the ID and description for the territory. You must enter an ID.
When you add a territory, you can

assign the driver, depot, equipment,
and model in the Properties notebook,
or you can drag the territory to the
driver, equipment, etc. in its list
window.
Step 4: Choose the driver(s) for the territory. To select a driver, click on the Driver
arrow; the Lookup - Driver window opens. Double-click on a driver, or click on
the driver and then on the Process icon, to select it. If the driver cost is split
equally between two drivers, check Team Split.
Step 5: Choose the color and, if necessary, the depot and model. To choose one of these
items, click on the appropriate arrow to open a list of options. Click on an entry
to choose it.
Operations Guide
625
Adding a Territory
Notes: A depot and model are already entered, based on the information you selected on
the Routing page of the Options notebook. You can change these entries, if
desired.
You can also assign depots, models, drivers, equipment, and equipment types to
the territory by selecting the item from the List menu to open its list window. Drag
the territory to the item in the window to assign it to the territory. See Assigning
Drivers, Equipment, and Other Items to a Territory.
Step 6: To assign equipment or equipment type to the territory, click on the Equipment
tab.
Step 7: To assign an individual piece of equipment to the territory, select Equipment.
Drag the equipment from the Available list to the Assigned list to assign it to the
territory.
The Add Territory Equipment

window allows you to assign
equipment to a territory.
Step 8: To assign an equipment type to the territory, select Equipment Type. Then click
on the arrow to open the Lookup - Equipment Type window. Double-click on an
equipment type, or click on the type and then on the Process icon to select it.
Step 9: Click the Save icon, or press [Ctrl]+[S] to save the new territory.
626

Adding a Territory
Step 10: When all new territories have been added, click the Close box to close the Add
Territory window.
Planning Editor Territories Window Add icon ([Insert]) Save icon ([Ctrl]+[S])
Operations Guide
627
Assigning IDs to Several Territories
Assigning IDs to Several Territories

When you use Make Territories to create your territories, it automatically assigns a unique
ID to each territory, starting with the first available number. You may want to change
these IDs, or make them more descriptive. For instance, you could select all the territories
that serve a single city and give them all IDs that start with the city name, followed by
sequential numbers. The Planning Editor allows you to easily assign these IDs to selected
territories using the Assign Sequential Territory ID feature.
work with.
Step 2: In the Territory window, select the territories you want to assign new IDs. To
select territories that are listed simultaneously, click on the first territory then
hold down the [Shift] key and click the last territory. To select territories that are
not listed simultaneously, hold down the [Ctrl] key as you click on the territories.
Step 3: Right-click on a selected territory and select Assign, then Assign Sequential
Territory ID ([Ctrl]+[G]) from the menu that pops up, or click on the Assign
Sequential Territory ID icon on the Territory toolbar. The Assign Sequential
Territory ID window opens.
Step 4: Enter the prefix and starting number for the IDs you want to assign. The total
length of the prefix and starting number can not exceed 15 characters.
If you have several territories that cover the
same geographic area, you can enter the name
of that area as the prefix, and all selected
territories will include that name in the ID.
Step 5: Click the [OK] button. The new IDs are assigned in the order you selected the
territories.
Planning Editor Territories Window Assign Assign Sequential Territory ID
([Ctrl]+[G])
628

Creating Routes
Creating Routes
When territories are created in the Planning Editor, empty routes are automatically
created for each territory. So, if you double-click on a territory you get a list of weeks,
then daily routes. However, the locations that are assigned to the territory have not been
placed on routes. You can route the locations manually, or use Assign Days to place the
locations on routes.
Assign Days looks at the possible delivery options for the location, as defined by the
delivery quantity and the service pattern set, and determines the best route(s) for the
location based on the other options you specify. Once the routes have been created, you
can evaluate them and change them as needed.
want to work with.
Step 2: To create routes for all existing territories, click on the Tools menu and select
Assign Days to all ([Ctrl]+[Y]), or click the Assign Days icon on the General
toolbar. The Assign Days window opens.
To create routes only for some territories, select the territories in the Territory
window. Right-click on a selected territory and choose Assign Days from the
menu that pops up. The Assign Days window opens.
Step 3: To create routes using previously established options, click the [Start]
button.
To have a display show the progress of Assign Days, check Show Progress
Indicators.
To change the options being used to create routes, click the [Options] button.
See Assign Days Options Notebook for more information.
Note: If you were not granted permission to change Assign Days Options in the
Administration module, you will not be able to open the Assign Days Options
notebook.
Step 4: When the routes have been created, the Assign Days window closes. You can
now evaluate the routes and edit them as needed.
Planning Editor Tools Assign Days to all ([Ctrl]+[Y]) [Start]
Operations Guide
629
Using the Assign Days Options Notebook

Before Assign Days can create your routes, you need to specify the guidelines and rules
you want the system to use. The Assign Days Options notebook allows you to specify
these guidelines and rules. To open the Assign Days Options notebook, click the
[Options] button on the Assign Days window. The pages of the Assign Days Options
notebook are explained below. After completing each page, you can save your selections
or click on a tab to move to another page.
The Assign Days Options notebook lets you specify the rules and
guidelines that will be used when the routes are created.
Score Parameters Page
The Score Parameters page of the Assign Days Options notebook lets you specify the
factor(s) that should be considered when the routes are created, and how heavily each
factor should be considered. The choices are Importance of Balanced Run Length,
Importance of Balanced Load, and Importance of Cost. Slide the bars to indicate the
relative importance of each option to the other options.
630

Hint: The position of the slider bars is relative, therefore sliding all the bars to the High
position is the same as leaving all of them in the Low position.
Importance of Balanced Run Lengthindicates the importance of the routes within
each territory having similar runtimes.
Importance of Balanced Loadindicates the importance of the routes within each
territory having similar quantities. The size alias used for balancing is determined by the
Primary Balance Size setting on the Load Parameters page.
Importance of Costindicates the importance of running the lowest possible cost route.
The route cost is calculated using the costs assigned to the drivers and equipment.
Load Parameters Page
The Load Parameters page of the Assign Days Options notebook lets you establish how
you want the load balanced throughout the week, select the size alias to use for balancing
load, and enable capacity restrictions.
To balance the load other than evenly throughout your delivery week, check the
Enable box in the Daily Load Distribution Goal Percentages area. Enter the percentage of
the load you want delivered on each day; the total must equal 100 percent. If Importance
of Balanced Load is set on the Score Parameters page, it will use these percentages when
balancing the routes.
Hint: If there is a day when you do not want any product to be delivered, you can use
this feature and set that days percentage to 0.
To choose the size alias that will be used to balance the load, click on the appropriate
choice in the Primary Balance Size area.
To keep routes with more than a specified quantity from being built, check the size
alias(es) in the Route Capacity Restrictions area and enter the maximum quantity the
route can contain for that size. If you would rather simply use the equipments capacity,
check Use Equipment Capacity. Any stops that cause a route to exceed its capacity
restriction will be unassigned and not placed on another route.
Reloads Page
The Reloads page of the Assign Days Options notebook lets you enable your equipment
to be reloaded and allows you to specify reload parameters.
To have reloads created based on the equipments capacity, check Enable Capacity
Reloads.
Note: Capacity reloads can only be created when you select a capacity restriction in the
Load Params page. See Assign Days Options Notebook - Load Params Page for
more information.
To have reloads created based on the routes paid runtime, check Enable Runtime
Reloads. Enter the maximum runtime for a single trip in the Runtime Threshold field.
Operations Guide
631
Note: If a route has only one trip, the Runtime Threshold is the maximum runtime for
the route.
To set the depot used for reloads, select either Use Origin or Use Best Available. If you
choose Use Origin, then the depot that the route started from will be used. If you choose
Use Best Available, Territory Planner will determine the best depot based on the closest
depot.
Note: The Depots list will contain all depots for that region; however, only depots
marked as Available will be considered for reloads. If the depot is not marked
available, double-click on the depot and check Available on the Modify Depot
window, or check the box in the Available column.
The Reloads page allows you

to enable reloads and
customize reload settings.
To set the reload service time, select Specify Time or Use Reload Depot Service Time.
If you selected Specify Time, enter the time using the format HH:MM.
To automatically have the equipment visit a depot and reload after the last stop,
check Always Reload After Last Stop.
To limit the number of reloads a route can have, check Limit Number of Reloads.
Enter the maximum number of allowed reloads per route in the Maximum Number of
Reloads field below.
To limit the total quantity for the route, check the appropriate size alias(es) in the
Maximum Quantity per Route section and enter the maximum quantity for that size.
632

Time Parameters Page
The Time Parameter page of the Assign Days Options notebook lets you specify several
route factors dealing with time, including the daily start times, and preferred and
maximum run lengths for each day of the week.
To establish route start times on a daily basis, enter the desired start time for the day
in the Start Time Override fields. These start times are overrides, and, where specified,
will be used instead of the start time entered on the Routing page of the Options notebook.
To create preferred runtimes on a daily basis, enter the desired runtime for the day in
the Preferred Run Length fields. If you enter a preferred run length on one or more days,
days without a specified run length will not be routed.
Hint: This feature can be used to create uneven routes throughout the week. For instance,
if you wanted to create shorter routes on Friday, you could give Friday a shorter
preferred run length than the remaining days of the week. This feature can also be
used to prevent routes from being created on specific days; simply enter a
preferred run length of 00:00 on days you do not want to have routes.
To specify a maximum run length on a daily basis, enter the maximum run length in
the Maximum Run Length fields. Any stops that cause a route to exceed its maximum run
length will be unassigned and will not be placed on other routes.
Time Windows Page
The Time Windows page of the Assign Days Options notebook lets you enable time
window processing of the routes. If time window processing is enabled, the routes are
sequenced according to the stops time windows after the routes have been created.
To allow the routes to be resequenced by time windows, check Enable Time Window
Processing.
To allow the routes start times to be adjusted to meet more stops windows, check
Adjust Start Times and enter the earliest and latest the start times can be moved to, and
the number of minutes to move start times in (15 minutes increments, 30 minute
increments, etc.).
Optimization Parameters Page
The Optimizations Parameters page of the Assign Days Options notebook lets you define
the rules that will be used to optimize the routes. The optimization process occurs after
the initial routes have been created, and involves moving stops from one route to another
to see if the answer is improved.
To limit the length of the optimization process, select one or both of the choices in the
Optimization Completion Criteria area. You can choose to have the process end when a
specified amount of time has passed, or when the variance between the largest and
smallest load and run length has reached a defined level. If you select both choices, the
optimization process will quit once one of the criteria is met.
Operations Guide
633
Note: Using these options may cause Assign Days to stop working before the best
solution has been found.
To indicate how hard the optimization process should work, move the Optimization
Effort Level slider at the bottom of the page. The higher the optimization level, the longer
the optimization process will take. The slider setting directly affects some of the
parameters on the Advanced Parameters page.
Advanced Parameters Page
The Advanced Parameters page of the Assign Days Options notebook lets you tweak the
rules used for the optimization process plus specify some advanced features for how the
routes are created. The options on this page should not be used until you are fine tuning
your routes. Each option is discussed below.
Use the following options to tweak the optimization process:
Number of Optimization Passesspecifies the number of routes to optimize. A
pass is considered complete when one route has been optimized.
Number of Moves to Look Aheaddefines how hard Assign Days should
analyze the results of every move made during the optimization process.
Increasing the number of moves to look ahead can quickly and dramatically
increase the amount of time needed to optimize the routes. This number should not
be set higher than 3.
Quit Recursion when First Better Move Foundcheck to allow Assign Days
to stop the optimization process as soon as a better move is found, even if not all
possible moves have been tried. If this option is checked, the best route may not
be created.
Number of Grid Squares Along a Sidedefines the size of the area the
optimization process can use to move stops to other routes. There are three entry
fields here. The optimization process starts with the Large Count, and if it can not
find a satisfactory answer within grid squares that size moves to the Medium
Count, and finally to the Small Count.
Use the following options to provide additional guidelines for the initial route creation
process:
Cluster Duplicate Lat/Longsgroups locations together that are on identical
latitudes and longitudes, as well as have the same service pattern sets and cycle
quantities that place them within the same service pattern set levels, and have
matching time windows. The anchor range must allow the location extensions to
be on the same day/week.
Precision Factorthe number of digits to ignore at the end of the latitudes
and longitudes before determining if they can be grouped together. For
instance, if the Precision Factor is set to 2, 39.8405 and 39.8410 would be
634

considered duplicate latitudes, but if the Precision Factor is set to 1 they

would not be considered duplicates.
Method for Laying Out the Routesyou can choose to have your routes created
based on clusters or spokes. These options are similar to the cluster and spoke
options in Make Territories, and refer to the shape of the routes that will be
created.
Group Days Geographicallygroups nearby stops together and moves the
entire group from one route to another during the optimization process. Moving
groups of stops, instead of individual stops, should help reduce overlap between
the routes.
Balance Number of Stops Across Weeksattempts to balance the number of
stops between each week during the optimization process.
Use the following Anchor Range Override options if you want to override how the
location extensions being routed are anchored:
Set Anchor Day Rangeoverrides the day anchoring for all of the location
extensions being routed. If you select this option, you must then select either Any
Day or Select Day Range.
Any Dayplaces no limit on the number of days from the Previous Days that
location extensions can be scheduled for delivery when new routes are created.
Select Day Rangeprevents the location extensions' delivery days from being
moved more than a specified number of days when new routes are created. If you
select this option, in the box below enter the maximum number of days from the
Previous Days that the location extensions can be scheduled for delivery when
new routes are created. You can enter a number from 0 to 6. If you enter 0, the
location extensions will be scheduled for delivery on the same days as their
Previous Days when new routes are created.
Allow Wraplets the range of allowed delivery days wrap across non-delivery
days into another delivery week. For example, there may be a location extension
with Friday as its Previous Day and an anchor range of 1 day. If the 5 day business
week is being used and wrap is allowed, the location extension could be scheduled
to receive delivery on Thursday, Friday, or Monday when routes are created. If
wrap is not allowed, the location extension could only receive delivery on
Thursday or Friday. A location extension will only be scheduled to receive
delivery on a day that complies with both its service pattern set and its anchor
range.
Set Anchor Week Rangeoverrides the week anchoring for all of the location
extensions being routed. If you select this option, you must then select either Any
Week or Select Week Range.
Any Weekplaces no limit on the number of weeks from the Previous Weeks
that location extensions can be scheduled for delivery when new routes are
created.
Operations Guide
635
Select Week Rangeprevents the location extensions' delivery weeks from

being moved more than a specified number of weeks when new routes are created.
If you select this option, in the box below enter the maximum number of weeks
from the Previous Weeks that the location extensions can be scheduled for
delivery when new routes are created. You can enter a number from 0 to the
number of weeks in the planning session's cycle. If you enter 0, the location
extensions will be scheduled for delivery in the same weeks as their previous
weeks when new routes are created.
Allow Wraplets the range of allowed delivery weeks wrap into another
delivery cycle. For example, in an 8 week cycle there may be a location extension
with week 8 as its Previous Week and an anchor range of 1 week. If wrap is
allowed, when routes are created the location extension could be scheduled to
receive delivery on week 7, week 8, or week 1 of the following cycle. If wrap is
not allowed, the location extension could only be scheduled for delivery on week
7 or week 8. A location extension will only be scheduled to receive a delivery on
a day that complies with both its service pattern set and its anchor range.
636

Evaluating the Routes

Whether you have existing routes or newly created routes, you can evaluate them using
the features of the Planning Editor. As you review the routes, you may want to make
changes; see Editing the Routes for more information.
List Windows
List windows can be helpful for viewing detail information about the routes, such as the
time, distance, service time, delivery quantity, stops, etc. You can also view a list of the
stops on the route in a list window.
To see the time, distance, quantity, number of stops and other information about the route,
open the Daily Routes window. To open the Daily Routes window, double-click on the
territory in the Territory window; the Weeks window opens. Double-click on the week in
the Weeks window; the Daily Routes window opens. Arrange the Daily Routes window
as necessary so you can view the columns containing the information you want to see.
To see a list of stops for the route, double-click on the route in the Daily Routes window.
The stop list for the day opens, listing the stops on the route.
Map
While the list window can provide a lot of detail information about the route, it is
sometimes helpful to see how the routes are laid out. The map allows you to see the actual
routes. You can also choose to use the Route Summary window to easily determine the
effect of any changes you make to displayed routes. For more information on setting up
the map to see the routes, see Using the Maps in the Planning Editor in the Roadnet
Transportation Suite Operations Guide.
To see an individual route on the map, right-click on the route and select Plot from the
menu that pops up ([Ctrl]+[P]), or click the Plot icon on the Routes toolbar. The map
opens with the route displayed.
To see all the routes for a week, right-click on the week in the Weeks window and select
Plot from the menu that pops up ([Ctrl]+[P]). A map opens in Route View with the week
selected; click on the buttons for the days you want to view.
To see all the routes for a territory, right-click on the territory and select Plot from the
menu that pops up ([Ctrl]+[P]). The map opens in the Territory View, showing the
territory. To see the routes, click on the Map View Mode icon and select Route View.
Click on the buttons for the weeks and days you want to see.
Notes: The Planning Editor includes some features that make it easier to see a route on a
map, especially if the map already has several routes on it. You can choose to
animate, flash, or locate the route on the map. Animate highlights the stops in
order, flash ([Ctrl]+[H]) flashes the route several times, and locate ([Ctrl]+[O])
zooms the map to the route. To use any of these options, right-click on the route
Operations Guide
637
and select the option from the menu that pops up. You can also flash or locate the
route by selecting the route, then selecting the icon on the Routing toolbar, or
pressing the hotkey combination. Flash and locate are also available from lists of
stops or location extensions or the Location toolbar to help you find individual
extensions on the map. In addition, when you select a territory or week in the list
window, it is highlighted on the map.
To quickly select/deselect all the weeks or days on the map, double-click on the
word Weeks or Days. If all weeks/days are selected they will be unselected,
otherwise all weeks/days will be selected.
To open the Route Summary window and see the effects of changes made to
displayed routes, click the Show/Hide Summary icon. The Route Summary window will
open on the side of the map, attached to the map. Click the appropriate options to see the
information you want to evaluate.
If you open the maps Route Summary window, you can easily see the effects of
any changes you make to the displayed routes.
To change the day that a location extension is routed on, drag the location to the map
button for the new day. If the location extension was already on a route (you are simply
changing its day), it will be routed on the same week. If you drop an unrouted extension
on a day, it will be routed on the first week of the cycle. You can also drag a location
extension to a week button; if the extension is already routed it will keep its same day on
the new week; if it is unrouted Territory Planner will pick the best day on the week.
Route Summary
The Route Summary is an easy way to see information about all or selected routes. Any
changes you make to your routes will be automatically reflected in the Route Summary,
638

so if you leave the Route Summary open you can immediately see the effects of any
changes you make to your routes.
The Route Summary

provides
information about
the routes for the
territories and
weeks you select.
To open the Route Summary, click on the File menu and select Route Summary
([Ctrl]+[R]), or click the Route Summary icon on the General toolbar. Once the window
is open, you can choose the territory(s) and week(s) you want included in the summary.
The top of the Route Summary window displays daily totals about the number of routes,
trips, stops, load (quantity), runtime, distance, and cost. In the middle of the window,
statistical information about the same categories is displayed. At the bottom of the
window, you can see how well the routes are balanced by looking at the runtime and load
variance, displayed in the Route % Variance box.
Note: You can choose which size alias you want the load displayed as, as well as whether
the statistics are displaying the average, minimum, or maximum for the selected
routes.
Planning Editor File Route Summary ([Ctrl]+[R])
Operations Guide
639
Editing Routes
Editing Routes
As you evaluate your routes, you will probably want to make changes to the routes. The
Planning Editor has several features that make it easy to change your routes as needed.
Hint: As you edit your routes, leave the Route Summary open to see the effects of the
changes you make.
Moving Stops from One Route to Another
You can drag stops from one route to another, or place unassigned or unrouted stops on
routes. Both the map and the list windows can be used to change routes this way.
To view the routes in a window, double-click on the territory in the Territory window,
then double-click on the week in the Weeks window. A list of daily routes opens; to see
the stop list for a route double-click on the day.
To view a route on the map, right-click on the route and select Plot from the menu that
pops up, or click the Plot icon on the Routing toolbar.
To display the location extensions that are not routed on a territory, right-click on the
territory and select Unrouted from the menu that pops up.
Notes: If you drop the stop on a route that does not match the locations service pattern
set, the Illegal Location Move window appears. The Illegal Location Move
window gives you two options for how to proceed. You can choose a new service
pattern set for the location that will allow it to be moved to the route you are
dropping it on, or you can choose a new service pattern. If you choose a new
service pattern, the stop will be moved to that route, not the route you initially
selected.
Location extensions listed in the Exceptions windows (List - Exceptions - Off
Day/Missed Time Windows/Missed Time Window Factor/Priority/Geocode) can
also be routed using this method.
When moving stops from one route to another, you can specify where you want the stop
placed on the new route, or you can allow the Planning Editor to determine the best spot
for the stop based on criteria you select.
To specify where the stop should be placed on the route, drag the stop to the stop list
for the new route or to the new route on the map. Drop the stop on the stop you want it to
be placed after; to make the stop the first stop on the new route drop it on a column header
(the depot on the map).
To allow the Planning Editor to determine where the stop should be placed, drag the
stop to the Daily Routes window and drop it on the new route. If you held down the left
mouse button while dragging the stop, the stop will be sequenced as specified on the Drag/
Drop page of the Options notebook. If you held down the right mouse button while
dragging the stop, a menu appears when you drop the stop. Choose the appropriate option.
The choices are:
Insert first
Insert by best cost
640

Editing Routes
Insert by best distance

Insert near closest location
Insert by best time
Insert by best time window
Insert last
Note: If a stop in a time of day restricted area is placed on a route with a restricted
equipment type, driver directions will display directions using non-restricted time
and distance information for that stop.
To have the Planning Editor suggest where the stop should be placed, right-click on
the route and select Suggest Territory from the menu that pops up. The Suggest Territory
window opens. Choose either Closest Location, Best Distance, Best Cost, Best Time, or
Best Time Window in the Placement in route section. Select the other options as
necessary. The Planning Editor will suggest the possible routes with the best suggestion
highlighted. For more information on letting the Planning Editor suggest the best route,
see Letting the Planning Editor Suggest the Territory or Routes.
Removing Stops from the Route or Territory
If your route is too long or exceeds the capacity of the equipment, you can remove stops
from the route. You have the option for the locations to still be assigned to the territory,
but not routed, or you can remove them completely from the territory. If stops are
removed from the territory they will be moved to the Unassigned window.
To remove the stop from the territory, right-click on the stop in the Stops window and
choose Unassign Completely from the menu that pops up. The stop will be moved to the
Unassigned window.
To remove the stop from the route, but leave it on the territory, right-click on the stop
in the Stops window and select Unroute on Territory from the menu that pops up. The stop
will be moved to the Unrouted window for the territory.
Sequencing the Routes
If you like the stops that are on the route, but dont like the order in which they are run,
you can change the order of the stops on the route. You can move the stops manually, or
have the Planning Editor choose the best order for the stops.
To move the stops manually, drag the stop from its current position and drop it on the stop
you want it to follow. You can do this using either a list window or the map.
To have the Planning Editor resequence the stops, right-click on the route and select
Action, then choose the proper option from the menu that pops up, or click the icon on the
Routing toolbar. The choices are:
Sequence ([Ctrl]+[Q])takes the list of stops and calculates the travel time between
each stop and the depot. The stops are placed and sequenced on the route in the way that
produces the least distance.
Operations Guide
641
Editing Routes
Flip ([Ctrl]+[F])reverses the current order of stops on the route.

Line Sequence ([Ctrl]+[M] or [Ctrl]+[Z])resequences the routes based on the travel
time between stops. Typically, if End Point is selected, the two stops that are the greatest
distance from each other are the first and last stops on the route; if Midpoint is selected,
the stop that is furthest from all other stops is selected.
Time Window ([Ctrl]+[W])sequences the stops using the locations time windows
and the time window information established in the Options notebook. See Setting the
Options in the Roadnet Transportation Suite Operations Guide for more information.
Notes: If you want to perform one of these actions on all a territorys routes, or all the
routes for a week, right-click on the territory/week and select Action, then the
action from the menu that pops up. This saves you from having to work with each
route separately.
When sequencing routes, the sequence works separately on each trip on the route.
The mid-route depot(s) will remain where they are and the sequencing action is
only performed on each trip
Using the Speed Editor
The Speed Editor is another option you can use to change a locations route. When you
open the Speed Editor it lists the routing information for the location, including the
current territory, delivery days, and cycle quantity, as well as some other information.
You can change any of these items, thereby rerouting the location.
Step 1: In the Stop List for the route, right-click on the location and select Speed Editor
from the menu that pops up ([Ctrl]+[J]), or click the Speed Editor icon on the
Location toolbar. The Speed Editor opens.
642

Editing Routes
Step 2: To change the locations delivery days and weeks, click on the appropriate
week and day buttons. A red button indicates the location is scheduled to be
delivered that week/day.
You can use the Speed Editor to reroute a location extension.
Step 3: If necessary, change the service pattern set and service pattern to match the new
routes. Click on the appropriate arrow to open the list; click on an option to select
it.
Step 4: If you are changing the route the location extension will be on, click the Insert
on Route(s) arrow to open a list of options, and choose how the stop should be
placed on the new route.
If you are making changes that leave the location extension on the current route,
and you want the extension to maintain its current position, check the Try To
Maintain Stop Order on Route box.
Step 5: Click the [Assign] button.
Notes: You can also change the delivery quantity or territory for a location using the
Speed Editor. Changing either of these items may require you to either change the
locations delivery days or service pattern and service pattern set.
If the delivery days and weeks you assigned do not correspond to a service pattern
in the service pattern set you selected, the Service Pattern Set Selection window
opens. Choose a new service pattern set and click the [OK] button, or click the
[Cancel] button to return to the Speed Editor. If you are changing multiple location
extensions and decide you do not want to make any of the changes, click the
[Cancel All] button.
If the Service Pattern Set is Manual Load Distribution, you can enter the delivery
quantities for each day of the week, allowing you to have uneven deliveries
throughout the week. If you want even deliveries throughout the week, you can
Operations Guide
643
Editing Routes
enter the total quantity for the entire cycle and click [Adjust Daily Quantities]. The
Speed Editor will spread the deliveries as evenly as possible throughout the week.
644

Letting the Planning Editor Suggest the Territory or Routes

If you are not sure which territory/routes would be the best place for the location
extension, you can have the Planning Editor make suggestions for placing the location
extension on the territory/routes. Using the guidelines that you establish, the Planning
Editor will list the possible territories and routes for the location extensions, with the best
territory/routes highlighted. You can accept the highlighted suggestion, select one of the
other suggestions that best work for you, or automatically have the location extensions
inserted onto the best territories/routes. By having the Planning Editor suggest the
territory and routes for that location extension, you take the guess-work out of
determining the best placement for the location extension.
work with.
Step 2: To find the best possible place for an unassigned location extension, click
on the List menu and select Unassigned. The Unassigned window opens.
To find the best possible place for a location extension from a stop list
window, click on the List menu and select Territories. The Territories window
opens. Double-click on the territory to open a list of weeks. Double-click on the
week to open a list of the daily routes. To view the stops on a route, double-click
on the day.
Step 3: Right-click on the location extension and select Suggest Territory from the
menu that pops up.
Step 4: Select the territories you want to consider in the Territories list; if no territories
are selected, all territories will be considered.
You can choose how you want
the Planning Editor to
sequence the stop on the
route; however, if you select
Unrouted as the route
placement, then the Planning
Editor will only suggest
territories. The Territories
panel lists all the existing
territories; the Location
Extension for suggestion
panel lists the location
extensions selected for
suggestions; and the
Suggestion panel will list all
the possible suggestions with
the best suggestion
highlighted.
Operations Guide
645
Step 5: To specify the guidelines that the Planning Editor should use to determine the
best territory/routes, click the [Score Weighting Factors...] button. The Suggest
Territory Score Weighting Factors window opens.
Note: To reset the settings to match those in Make Territories or Assign Days, click the
Reset icon located to the right of each section. For more information, see Using
the Make Territories Options Notebook, and Using the Assign Days Options
Notebook.
Important: When moving the slider bars, the weights are relative to each other so moving
all the bars to High would have the same effect as leaving them all at Off.
In the Proximity section, move the Minimal Distance to Territory slider bar to
indicate the importance of the location extension being close to the suggested
territory. Then, to select how the distance should be determined, click the
Estimation Method arrow and select the appropriate option. For example, if the
location extension should be near a territory border that includes the origin, then
choose Closest Border With Origin. The choices are Closest Centroid, Closest
Location, Closest Border With Origin, and Closest Border Without Origin:
Closest Centroiddistance from the location extension for suggestion
to the geographic center of the territory.
Closest Locationdistance from the location extension for suggestion
to the closest location extension in the territory.
Closest Border With Origindistance from the location extension for
suggestion to the closest territory border that includes the origin.
646

Closest Border Without Origindistance from the location extension

for suggestion to the closest territory border that does not include the
origin.
Move the appropriate bars to set the options for the Planning Editor to use
when suggesting territories/routes for location extensions.
In the Territory section, specify the importance of balancing the territories on

each factor.
In the Route section, select the options for selecting the best route. If you want
to balance on load, choose the size alias that the route should be balanced on. Click
the Primary Balance Size arrow and select the appropriate size.
When you are finished, click the [OK] button to save the options.
Step 6: Check Enforce Equipment Type Restrictions to have only territories with
allowed equipment types considered for suggestion.
Step 7: In the Suggest Territory window, click the Placement in route arrow and select
the appropriate option to specify how the location extension should be placed on
the route.
To have the Planning Editor suggest the best possible placement on the
routes, select Closest Location, Best Distance, Best Cost, Best Time, or Best
Time Window.
Operations Guide
647
To have the Planning Editor suggest only the best possible territories, select
Unrouted.
Note: The Daily route will not exceed section will be disabled when you select Unrouted.
Step 8: To specify the capacity and time restrictions for suggested routes, choose the
appropriate options in the Daily route will not exceed section.
To prevent the routes from exceeding capacity, check the size aliases that
cannot be exceeded.
Choose the appropriate time restriction.
Step 9: In the Max. no. of suggestions to display, specify the maximum number of
results that will be suggested.
Step 10: Check Show accepted results to open a separate results window listing the
territory/routes that each location extension was placed on.
Step 11: Once you have specified the criteria, click the [Suggest] button to have the
Planning Editor determine the best territories/routes. The results are displayed in
a suggestion list, with the best suggested territory/routes highlighted.
Notes: To automatically insert the best suggestions for each location extension without
having to manually choose the territory/routes, click the [Auto Insert] button. The
location extensions are moved to the territories/ routes with the best suggestion
score.
If a location extension has a manual load distribution as a service pattern set, the
Planning Editor will only suggest territories, even if you selected a placement in
route option to suggest routes.
Step 12: Choose the territory/routes that you want to add the location extension to and
click the [Accept] button. The location extension is moved to that territory/
routes; if you checked Show accepted results, the Suggest Territory Results
window opens in a separate window showing the accepted results.
Step 13: When you are finished, click the Close box to close the Suggest Territory
window.
648

Saving the Territories and Routes
Saving the Territories and Routes

As you create, evaluate, and edit your territories and routes in the Planning Editor, you
will want to periodically save your work to prevent loss. You can choose to perform a
backup save or a full save. The backup save, which takes less time, creates a file that is
used if the Planning Editor exits unexpectedly, such as if you lose power. If you use the
backup save, you must do a full save when exiting the editor to prevent losing all of your
changes. The full save, which may take longer, permanently saves any changes you made.
To perform a backup save, click the File menu and select Backup Save ([Ctrl]+[B]).
To perform a full save, click the File menu and select Save ([Ctrl]+[S]). The current
territories and routes are saved.
Note: If you have selected to be prompted to compact the database before saving, you
will be asked whether or not you want to compact the database before a regular
save. Since the database can become very large, it is a good idea to periodically
compact the database to improve performance.
Planning Editor File Save ([Ctrl]+[S])
Planning Editor File Backup Save ([Ctrl]+[B])
Operations Guide
649
Finding Territories, Weeks, Routes, Stops, or Location Extensions

When evaluating or editing the territories or routes in the Planning Editor, you may need
to find a specific location, stop, route, week, or even territory. Instead of searching
through several windows, and double-clicking down to the level you want, you can use
the Locate feature to find it. This means that if you know the locations ID, you can search
for a list of routes the location is on.
In addition to helping you find the items, you can perform the same actions on them in the
Locate window as you could in any other window. For instance, if you searched for stops,
the Locate window would give you a list of stops, and you could right-click on a stop and
get the same menu options you would have if you double-clicked on the route to open a
Stop List. You could even drag the stop out of the Locate window and drop it on another
route.
If you know the location ID, description, driver, or equipment, you can use the Locate
window to find the information. The results can be returned as territories, weeks, routes,
stops, or location extensions.
work with.
Step 2: Click on the Tools menu and select Locate ([Ctrl]+[L]), or click the Locate icon
on the General toolbar. The Locate window opens.
The Locate window can save you time, since you dont have to search through
several windows to find the particular territory, week, route, stop, or location
extension you are looking for.
Step 3: Click on the appropriate tab for the item you are searching for and enter the
search criteria.
650

If you are know the location type, ID, or description, use the Detail page. Enter the
location type and ID or the description.
If you know the driver, click on the Driver tab. Enter the drivers name in the
Name field, or select the driver from the list.
If you know the equipment type and ID, click on the Equipment tab. Select the
equipment type and enter the ID, or simply choose the equipment type.
Step 4: Choose whether you want the results displayed as territories, weeks, routes,
stops, or location extensions.
Step 5: Click the Execute Query Using Criteria icon. The entries that match the search
criteria are listed at the top of the window.
To perform multiple searches without losing the results of previous searches,
check Retain Results before doing a subsequent search.
To remove the search criteria, click the Erase icon.
Planning Editor Tools Locate ([Ctrl]+[L])
Operations Guide
651
Changing a Routes Properties
Changing a Routes Properties

When Assign Days creates the routes, it assigns an ID, start time, etc. based on the rules
you specify on the Routing page of the Options notebook, or in the Assign Days Options
notebook. You can change any of these parameters for a route at any time.
Note: If you want to assign sequential IDs to several routes, use Assign Sequential Route
ID instead.
the Planning Session window visible. Double-click on the session you want to
work with.
Step 2: Find the route you want to change.
If you know the territory and week the route is on, double-click on the territory
in the Territories window to open the Weeks window, then double-click on the
week to open the Daily Routes window.
If you are not sure which territory the route is on, use the Locate feature to find
the route; see Finding Territories, Weeks, Routes, Stops, or Location Extensions
Step 3: In the Daily Routes window, Locate window, or on the map, right-click on the
route and select Properties from the menu that pops up ([Ctrl]+[T]) or click the
Properties icon on the Routes toolbar. The Edit Route window opens.
You can change the starting time, preferred

time, regular time or maximum time, as
well as pre- and post-route times from the
Edit Routes window.
Step 4: Change the route information as necessary.

Step 5: Click the Save icon, or press [Ctrl]+[S].
If you selected multiple routes, the properties for the next route appear in the
window. You can also use the arrows on the top of the window to move from one
route to another.
Planning Editor Routes Window Properties ([Ctrl]+[T]) Save icon ([Ctrl]+[S])
652

Assigning Start Times to Several Routes
Assigning Start Times to Several Routes

When the routes are first created, they are assigned start times based on the entries made
in the Assign Days notebook. You can change the start times for the routes using the
Route Properties notebook, or, if you want to assign several routes the same new start
time, you can use the Assign Start Time feature.
work with.
Step 2: Find the route(s) you want to change.
Step 3: In the Daily Routes or Locate window, click on the routes to which you want to
assign new start times. To select routes listed simultaneously, click on the first
route then, holding down the [Shift] key, click on the last route. To select routes
not listed sequentially, hold down the [Ctrl] key while clicking on the routes.
Note: You can also assign new start times to all routes on a territory or a week by
selecting the menu option from the Territory or Week window.
Step 4: Right-click on the selected routes and select Assign then Start Time from the
menu that pops up. The Modify Start Time window opens.
You can change the start time for several
routes simultaneously using the Modify
Start Time window.
Step 5: Enter the new Start Time. You can enter the time manually, or use the arrow s
to scroll to the correct time. If entering the time manually, use the arrow keys to
move from the hour to minute field. If using the scroll arrows, click on the
correct field (hour to minute) before scrolling. Use a 24-hour clock when
Step 6: Click the [OK] button to assign the new starting time to the routes.
Operations Guide
653

When Assign Days creates the routes, it automatically assigns an ID to each route.
Usually this ID is simply the day of the week. You can change the ID as desired. If you
are only changing one ID or do not want to give the routes sequentially numbered IDs,
use the Edit Routes window. However, if you want to give several routes numerically
sequential IDs you can use Assign Sequential Route IDs.
work with.
Step 2: Find the route(s) you want to change.
Step 3: In the Daily Routes or Locate window, click on the routes to which you want to
assign new IDs. To select routes listed simultaneously, click on the first route
then, holding down the [Shift] key, click on the last route. To select routes not
listed sequentially, hold down the [Ctrl] key while clicking on the routes.
Note: You can also assign sequential route IDs to all routes on a territory or a week by
selecting the menu option from the Territory or Week window.
Step 4: Right-click on a selected route and select Assign, then Assign Sequential Route
ID from the menu that pops up ([Ctrl]+[I]), or click the Assign Sequential Route
ID icon on the Routing toolbar. The Assign Sequential Route ID window opens.
The prefix plus number for the ID
cannot exceed 15 characters.
Step 5: Enter the prefix and number for the first route. For instance, if you want to ID
your routes by city, the first route ID might be BALT100. The combination of the
prefix and ID can not exceed 15 characters.
Step 6: Click the [OK] button. The routes are assigned new IDs in the order they were
selected.
Planning Editor Routes Window Assign Assign Sequential Route ID ([Ctrl]+[I])
[OK]
654

Assigning Breaks and Waits to Routes

When Assign Days creates routes in the Planning Editor, it does not include time for lunch
or other breaks, or allow the driver to wait at a stop to make a time window. However,
you can add both breaks and waits to routes. When you add breaks and waits, the travel
time for the route is increased by that amount. You can add a break after a stop, a wait
before a stop, or a layover after a stop. All breaks, waits, and layovers can either be paid
or unpaid. Any breaks/waits/layovers that are paid are considered when the total time for
the route is considered, so they will count against the preferred time and maximum time.
Each type of break has an icon associated with it in the Stop Type column. A dollar sign
next to the Stop Type indicates the break is paid. The icons are summarized in the table
below.
Icon
Meaning
Icon
Meaning
Icon
Meaning
Break
Layover
Wait
Paid Break
Paid Layover
Paid Wait
If you are exporting these routes to Roadnet as daily routes, the breaks and waits will be
included with the exported routes. However, the breaks and wait will not be transferred
to a new session during a session transfer.
work with.
Step 2: Find the route to which you want to add the break or wait.
week to open the Daily Routes window. Double-click on the route to open the
Stop List.
If you are not sure of the territory the route is on, use the Locate feature to find
Step 3: Right-click on the stop to assign the wait or break to and select Assign, then
Break/Wait, from the menu that pops up ([Ctrl]+[B]), or click the Assign Break/
Wait icon on the Location toolbar. The Assign Break or Wait window opens.
Breaks, waits, and layovers each have
a unique graphic in the Stop Type
column so that you can easily
determine what kind of stop it is.
Operations Guide
655
To assign a break or layover, right-click on the stop before the break should
occur.
To assign a wait, right-click on the stop after the wait should occur.
Step 4: Select whether a break, wait, or layover is being added in the Type area. Enter
the number of minutes the break should last in the Time field.
Step 6: Click the [OK] button to accept the new break/wait/layover. It appears in the
Stops window.
Planning Editor Stops Window Assign Break/Wait ([Ctrl]+[B]) [OK]
656

Inserting a Depot onto a Route in the Planning Editor

When your equipment has completed its route and has enough time left, it can return to a
depot and reload for additional deliveries. For example, you may only have equipment
types that hold half of a days total delivery capacity. In this case, to make all the
deliveries for the day, you can reload the equipment and finish the deliveries. Use reloads
so that you can strategically plan your routes to maximize your available resource
capacity. Once a depot has been inserted, it appears as a stop on a routes stop list or any
other stop list or a map. You also have the flexibility to delete or move the depot after the
depot has been inserted. If you decide to sequence, sequence range actions can only take
place on a trip, not between trips. In other words, only stops of the route between reload
depots will be rearranged, and stops will not be moved between reload depots.
Note: If the quantity for a single delivery exceeds the equipment capacity, then the
equipment will not be reloaded. In other words, the equipment will not make
multiple trips to the same locations on the same route.
the Planning Sessions window visible.
Step 2: Double-click on the planning session you wish to open. The Territories window
opens with a list of all the territories associated with the session.
Step 3: Open the routes stop listclick List, then click Territories. Double-click on the
territory to open a list of weeks. Double-click on the week to open a list of the
daily routes. Double-click on the day to view the route, including any mid-route
depots.
Step 4: Right-click on the stop preceding or following where you want to insert the
reload depot, then select Insert, then Reload Depot from the menu that pops up.
The Insert Depot window opens.
To manually insert a
reload depot, select
Reload Depot from the
menu that pops up.
Note: Reload depots cannot be inserted onto a Stops windowopened by clicking List,
then Stops.
Step 5: Choose the depot to be inserted, and specify whether it should be placed before
or after the selected stop.
Operations Guide
657
Step 6: Select either Specify Time or Use Depot Service Time. Service time is the
amount of time needed to reload the equipment if it is being sent out for a
subsequent trip. If you selected Specify Time, enter the time using the format
HH:MM.
Step 7: Click the Action Taken arrow and select either None or Fill as Needed.
Normally, Fill as Needed will be selected.
Step 8: Click on the [OK] button. The depot is inserted onto the route, and appears on
the map and in the routes stop list. In the Location Type column, the depots type
is DPT, and the icon is a building with arrows going in and out.
Step 9: To manually remove a reload depot from a route, right-click anywhere on a
reload depot and select Remove from the menu that pops up. The reload depot is
removed from the route.
You can manually remove multiple reload depots by holding down the [Ctrl] key while
clicking on the reload depots.
Tip:
You can also manually move a reload depot. For example, to move a reload depot
within a routes stop list, click on the reload depot that you want to move, and then
drag and drop it in the new location within that routes stop list.
Once the depots have been inserted onto the routes, you can modify the properties of the
depots.
To modify the properties of a reload depot, right-click on the reload depot and select
Properties from the menu that pops up.
OR
Double-click on existing reload depot.
The Insert Depot window opens. Make changes to the properties, as necessary. Click on
the [OK] button to save.
658

Assigning New Service Pattern Sets to Location Extensions
Assigning New Service Pattern Sets to Location Extensions

When you first import or enter a location extension, you assign a service pattern set to it.
However, you may find that you want to change the service pattern set associated with
one or more location extensions. If you want to change the service pattern set assigned to
location extensions within the Planning Editor, you can simply drag the location
extensions to the new service pattern set. This same procedure can also be used to assign
new service time types, time window types, and account types to locations in the Planning
Editor.
the Planning Session window visible. Double-click on the planning session you
want to work with.
Step 2: Click on the List menu and select Service Pattern Sets. The Service Pattern Sets
window opens.
Step 3: To assign the new service pattern set/type to a stop, double-click on the
territory, then week, then day containing the stop. The Stops window opens,
listing all stops on that route. Select the stops you want to assign the new type or
service pattern set to.
To assign the new service pattern set/type to a location extension, click on the
List menu and select Locations, then Location Extensions. The Location
Extensions window opens. Select the extensions you want to assign the new type
or service pattern set to.
Step 4: Click on the selected items and, holding down the mouse button, drag them to
the service pattern set you want to assign to them. If the extensions are currently
routed, they will be placed on new routes based on your instructions. If you held
down the left mouse button when dragging, the extensions will be placed on the
new routes based on the selection you made in the Options notebook. If you held
down the right mouse button when dragging, a menu pops up from which you
can choose how you want the extensions placed on the new routes. The new
assignments are made.
Notes: If the new service pattern set does not have a service pattern that matches the
stops current routes, the stop will be moved to routes matching the new set. If the
set contains more than one service pattern the Service Pattern Set Change
Possibilities window opens. Choose the desired service pattern in the list and click
[Select].
If you are assigning a new service pattern set to several location extensions, you
can click the [Auto Assign] button on the Service Pattern Set Change Possibilities
window. The Planning Editor will automatically assign the first viable service
pattern to all the location extensions.
Operations Guide
659
Assigning Service Time Overrides to Location Extensions
Assigning Service Time Overrides to Location Extensions

Location extensions usually use the service time assigned to the location in the
Maintenance module. However, you may find that while performing a re-route that you
want to change the locations service time only for a single planning session. You can
assign a different service time type to a location extension in the Maintenance module or
in the Planning Editor, creating a service time override that is used in the selected
planning session. Any service time overrides assigned to a location extension will be
transferred with the extension when Shift Days is run, so the override will exist in the new
planning session as well. You can also assign a new service time type to a location using
this procedure.
the Planning Session window visible. Double-click on the planning session you
want to work with.
Step 2: Click on the List menu and select Service Time Types. The Service Time Types
window opens.
Step 3: To assign the service time type to a stop, double-click on the territory, then
week, then day containing the stop. The Stops window opens, listing all stops on
that route. Select the stops you want to assign the service time type override to.
To assign the new service time type to a location extension, click on the List
menu and select Locations, then Location Extensions. The Location Extensions
window opens. Select the extensions you want to assign the service time type
override to.
Step 4: To update the location extensions with a service time override, click on the
selected items and, holding down the [Ctrl] key drag the location extensions to
the service time type in the Service Time Type window. The service times for any
routes the location extension is on will be updated with the new service time
information.
To update the location with a new service time type, which will then be used in
all planning sessions and Roadnet, click on the selected items and drag the
location extensions to the service time type in the Service Time Type window. The
service times for all routes containing that location will be updated with the new
service time information.
Note: You can also drag the selected extensions while holding down the right mouse
button and select the appropriate option from the menu that pops up.
660

Anchoring Location Extensions

Anchoring allows you to limit how much a location extensions delivery days will
change in relation to its Previous Days and Weeks when a re-route is done. Using
anchoring prevents excessively long periods of time from lapsing where a location
extension does not receive a delivery. For example, you could have a location extension
that needs a delivery once every 8 weeks. Before being re-routed, this location extension
may have received their delivery in week 1. After doing a re-route, the location extension
could be scheduled to receive their delivery in week 8, resulting in 15 weeks passing
without a delivery. With anchoring, you can prevent this by requiring that the location
extension always receive a delivery some time during week 1 of the planning sessions
cycle.
To use anchoring, first you need to set how the location extensions are anchored to their
Previous Days and Weeks. You will set the anchor range, which determines how far the
delivery days and weeks can move from the Previous Days and Weeks when a re-route is
done. You can anchor location extensions several different ways. This section explains
how to anchor select location extensions from the list windows and how to anchor all
location extensions within a planning session at once. However, you can also import
location extensions anchor settings and use the Assign Days Options Notebook to
override how all location extensions being routed are anchored.
After setting how the location extensions are anchored, you need to establish the Previous
Days and Weeks. This will set the days and weeks that the location extensions deliveries
are anchored to.
Once you set the anchoring and the Previous Days and Weeks for the location extensions,
the anchor settings will automatically be applied when new routes are created. However,
if you override the location extensions anchor settings by using the Assign Days Options
Notebook, all location extensions being routed will be anchored based on the selections
made in the Assign Days Options Notebook. Location extensions will only be scheduled
for delivery on days that comply with both their service pattern set and their anchor range.
Anchoring Location Extensions from the List Windows
From the Location Extensions list window, you can anchor an individual location
extension or a group of location extensions. From the Territories list window you can
anchor all locations within a territory.
wish to work with.
Step 2: To anchor one location extension or a group of location extensions, click on
the List menu and select Location Extensions. The Location Extensions window
opens. [Ctrl]+click each location extension you want to anchor. Right-click on
Operations Guide
661
any one of the selected location extensions and select Anchoring from the menu
that pops up.
To anchor all of the location extensions in a territory, click on the List menu
and select Territories. The Territories window opens. Right-click on the territory
that contains the location extensions that you wish to anchor and select Anchoring
from the menu that pops up.
You can quickly set the

anchoring for multiple
location extensions.
certain number of days, select Select Day Range. In the box, enter the
maximum number of days from the Previous Days that the location extensions
can receive delivery. For example, if a location extensions Previous Day is
Wednesday and you enter 1, the location extension could be scheduled to receive
their delivery Tuesday, Wednesday, or Thursday when a re-route is done. If you
enter 0, the location extension must be scheduled for delivery on Wednesday.
To let the range of allowed delivery days wrap across non-delivery days,
check Allow Wrap. For example, there may be a location extension with Friday
as its Previous Day and an anchor day range of 1. If the 5 day business week is
being used and wrap is allowed, the location extension could be scheduled to
receive delivery on Thursday, Friday, or Monday when a re-route is done. If wrap
is not allowed, the location extension could only be scheduled for either Thursday
or Friday.
Step 4: To prevent the location extensions delivery weeks from moving more than
a certain number of weeks, select Select Week Range. In the box, enter the
maximum number of weeks from the Previous Weeks that the location extensions
can receive delivery. For example, if a location extensions Previous Week is
week 7 of an 8 week delivery cycle and you enter 1, the location extension could
be scheduled to receive its delivery in week 6, week 7, or week 8 when a re-route
is done. If you enter 0, the location extension must be scheduled for delivery in
week 7.
To let the range of allowed delivery weeks continue through the first and last
week in the cycle, check Allow Wrap. For example, in an 8 week cycle there may
be a location extension with week 8 as its Previous Week and an anchor week
range of 1. If wrap is allowed, when a re-route is done the location extension could
662

be scheduled to receive delivery on week 7, week 8, or week 1. If wrap is not

allowed, the location extension could only be scheduled for week 7 or week 8.
Step 5: Click [OK].
Planning Editor Location Extensions or Territories Window Anchoring [OK]
Anchoring All Location Extensions in a Planning Session
If you want to anchor all location extensions in a planning session the same way, you can
quickly anchor them at once.
wish to work with.
Step 2: Click on the Tools menu and select Anchoring. The Anchoring window opens.
certain number of days, select Select Day Range. In the box, enter the number
of days from the Previous Days the location extensions can their receive
deliveries when a re-route is done. For example, if a location extensions
Previous Day is Wednesday and you enter 1, the assign days process will allow
the location extension to receive delivery on Tuesday, Wednesday, or Thursday.
If you enter 0, the location extension must be scheduled for delivery on
Wednesday.
To let the range of allowed delivery days wrap across non-delivery days,
check Allow Wrap. For example, there may be a location extension with Friday
as its Previous Day and an anchor day range of 1. If the 5 day business week is
being used and wrap is allowed, the location extension could be scheduled to
receive delivery on Thursday, Friday, or Monday when a re-route is done. If wrap
is not allowed, the location extension could only be scheduled for either Thursday
or Friday.
Step 4: To prevent the location extensions delivery weeks from moving more than
a certain number of weeks, select Select Week Range. In the box, enter the
number of weeks from the Previous Weeks the location extensions can receive
their deliveries when a re-route is done. For example, if a location extensions
Previous Week is week 7 of an 8 week delivery cycle and you enter 1, the assign
days process will allow the location extension to receive delivery in week 6,
week 7, or week 8. If you enter 0, the location extension must be scheduled for
delivery in week 7.
To let the range of allowed delivery weeks continue through the first and last
week in the cycle, check Allow Wrap. For example, in an 8 week cycle there may
be a location extension with week 8 as its Previous Week and an anchor week
range of 1. If wrap is allowed, when a re-route is done the location extension could
Operations Guide
663
be scheduled to receive delivery on week 7, week 8, or week 1. If wrap is not

allowed, the location extension could only be scheduled for week 7 or week 8.
Step 5: Click [OK].
Planning Editor Tools Anchoring [OK]
Setting the Previous Days and Weeks
For anchoring to work, you need to set the Previous Days and Weeks to the days and
weeks that you want the location extensions anchored to. You can use the Update
Previous Days and Weeks feature to quickly anchor to the current delivery schedule. The
Update Previous Days and Weeks feature automatically sets the Previous Days and
Weeks for all location extensions in the planning session to the current delivery days and
weeks.
Note: When you do a re-route, the Previous Days and Weeks will not automatically
change. Therefore, unless you change the Previous Days and Weeks, the location
extensions will remain anchored to the same days and weeks even if you do
multiple re-routes.
the Planning Sessions window. Double-click on the planning session you wish to
work with.
Step 2: Click on the Tools menu and select Update Previous Days and Weeks.
Note: The Previous Days and Previous Weeks columns in the Location Extensions
window show the Previous Days and Weeks for each location extension.
Upon using the Update Previous Days and Weeks feature, the Previous Days will
become the same as the Delivery Days and the Previous Weeks will become the same as
the Delivery Weeks.
Planning Editor Tools Update Previous Days and Weeks
664

Geocoding a Location on the Map in the Planning Editor
Geocoding a Location on the Map in the Planning Editor

When evaluating territories and routes you may discover a location has an incorrect
geocode and you need to correct it. You can easily regeocode a location on a map from
either the Territory view or the Route view. Any geocodes you change here are permanent
and will be reflected in all planning sessions.
want to work with.
Step 2: Open a map showing the location you want to geocode.
Step 3: Right-click on the location you want to geocode and select Geocode from the
menu that pops up.
OR
Left-click on the location you want to geocode and click the Geocode icon from
the Map toolbar.
The cursor changes to a cross hair, indicating that you are in Geocode mode; click
where you want the location to be geocoded to.
Note: You can use many of the map features, such as Zoom In, Zoom Out, Center, and
Zoom to Zip or City to navigate around the map and find the proper place to
geocode the location to. To use these features while in Geocode mode, right-click
on the map and select the desired mode from the menu that pops up; to return to
Geocode mode right-click on the map and select Cancel Mode.
Planning Editor Map Geocode
Operations Guide
665
Printing Driver Directions in the Planning Editor

If you have a new driver, or a driver who is simply driving in an unfamiliar area, you may
want to provide directions for him/her to follow. The Planning Editor lets you print turnby-turn directions for the route, either with or without maps. You can print normal driver
directions, which contain directions to travel from stop to stop, or extended driver
directions, which include more information about the stop, such as time windows and
planned arrival times. You can choose to print the extended directions with or without
maps, or, if printing normal driver directions, to a file. You can print driver directions for
a single route, or for an entire weeks or territorys routes.
Notes: You can also print driver directions from the Report window. See Printing Reports
in the Planning Editor in the Roadnet Transportation Suite Operations Guide for
more information.
Driver directions, as opposed to extended driver directions, can only be printed by
right-clicking on a route.
If you were not granted permission to print maps in the Administration module,
you will not be able to print any driver directions with maps, such as turn by turn
directions.
want to work with.
Step 2: To print extended driver directions, right-click on the territory, week, or
route(s) and select Print Extended Driver Directions, then With Turn by Turn (to
print the maps) or Without Turn by Turn (to print without the maps), from the
menu that pops up. If printing with maps, choose the size maps that should be
printed with the directions; the smaller the maps the more directions can fit on a
piece of paper.
To print driver directions, right-click on the route and select Driver Directions
from the menu that pops up. There will be a pause while the path from stop to stop
is calculated.
Note: If you print extended driver directions by selecting a week or territory, directions
will be printed for all routes on the week or territory.
Step 3: If Driver Directions was selected, the Route Directions for Route window
opens, listing the driver directions. Click on the Printer icon and choose the
desired option.
666

If Print Extended Driver Directions without Turn by Turn was selected, the
directions are sent directly to the printer.
If Print Extended Driver Directions with Turn by Turn was selected, the Detailed
Map Printer Options window opens. You can change the name that will print at the top of
the map, whether or not to print an overview map, and choose the size of the maps to print.
The size of the map dictates how many pages will be needed to print the report.
The Detailed Map Printer Options

window appears if you choose to print
Driver Directions with Turn by Turn,
or Print Extended Driver Direction
with Turn by Turn.
Planning Editor Routes Window Driver Directions/Print Extended Driver Directions
Operations Guide
667
Shifting the Delivery Days

You can use Territory Planner to create routes for different delivery situations, such as
creating routes for your sales force as well as creating routes for the drivers. In this case,
you may want to have the driver follow the sales person to the customers location by a
set number of days. The Planning Editors Day Shift tool lets you automatically shift the
delivery day for a stop by a set number of days. There are two ways you can set the
number of days the delivery is shifted. You can specify the number of days an individual
location extension will be shifted in the Locations notebook. Or, when performing the day
shift, you can specify that you want all included stops shifted a set number of days.
Because shifting the days may invalidate a location extensions service pattern set, you
can have the Planning Editor select a new valid service pattern set for the new delivery
day. When the stops are shifted to new days, they remain on the same territory, and, if
possible, keep the same stop number.
The Shift Days tool can be very helpful when used in conjunction with Session Transfer.
For instance, you can transfer the selected locations from the sales session, then run day
shift to move the days, without altering the sales forces routes.
want to work with.
Step 2: Click on the Tools menu and select Shift Days. The Select Routes window
opens. Select the territories, weeks, and days containing the stops you want to
shift. All stops on those selected items will be shifted. Click the [OK] button. The
Day Shift window opens, showing the location extensions that were selected to
shift.
Note: If you only want to shift items on a selected territory, week, or day, right-click on
the territory, week, or day in the Territories, Weeks, or Days window and select
Shift Days from the menu that pops up. The Day Shift window opens showing the
location extensions that were selected to shift.
668

Step 3: In the Valid Days area, check the days that are valid delivery days. When the
days are shifted, stops will only be moved to these valid delivery days; the days
not checked are not counted.
Before shifting the delivery days, you

need to specify the valid delivery days
after the shift. When assigning the
stops to the new delivery days, the
Planning Editor will skip days not
selected as valid delivery days.
Step 4: To have all the selected stops shifted the same number of days, instead of the
number of days specified in the Location notebook, check Day Shift Override.
Enter the number of days you want the stops to be shifted.
Note: If you want your depots and breaks/waits/layovers to carry over to the new session,
you must check the Day Shift Override box and enter the number of days to shift.
Step 5: Choose the direction of the shift.
Step 6: Check the appropriate boxes to allow the Planning Editor to assign a new
service pattern set or manual load distribution to the extension based on the shift
if the extensions current service pattern set is no longer valid. A stop will not be
moved to a new delivery day if the new day violates the current service pattern
and a new valid set is not able to be found.
If Assign New Service Pattern Set is selected, the Planning Editor searches for a
service pattern set that contains a valid delivery option for the location extension.
If a new service pattern set is not found, it will assign service pattern set 0 (manual
load distribution) if Assign Manual Load Distribution is checked. If Assign
Manual Load Distribution is not checked, the stop will not be shifted.
Step 7: Click the [OK] button. The stops are shifted to the new days, and placed on
routes.
Note: Once the transfer is complete, you can view logs of the process. The logs, called
SessionTransferStatus.log and SessionTrasferError.log, are stored in the directory
referenced by the cpconfigpath environment variable.
Planning Editor Tools Shift Days [OK]
Operations Guide
669
Printing Reports in the Planning Editor
Printing Reports in the Planning Editor

Territory Planner comes with several different reports that can be used to inform drivers
of their daily routes, as well as management reports that summarize your territories,
routes, and even a re-route analysis. The reports can be previewed or printed in the
Reports module or in the Planning Editor. Some basic instructions for printing reports are
listed below; for more information see Printing Reports, Previewing Reports, and Printing
Report Groups in the Reports section of this manual. A description of each report is also
included in the Reports section of the manual.
Note: Maps can only be printed from within the Planning Editor.
you will not be able to print any reports that include maps.
opens with the Planning Session window visible. Double-click on the planning
session you want to work with.
Planning Editor Reports Groups Group [OK]
Note: If your report group contains plots, you must print it from within the Planning
Editor, not the Reports module.
opens with the Planning Sessions window visible. Double-click on the planning
the reports.
the [OK] button.
Planning Editor Reports List Preview/Print [OK]
670

Printing Maps in the Planning Editor
Printing Maps in the Planning Editor

Once you have created your routes, you may want to print maps to see how the routes
look. You can accomplish this by plotting the routes you want to print and pressing the
Print icon on the map, or you can print the maps as reports from the Reports window. The
following plots are available as reports:
Session Plotprints a map showing all location extensions in the selected session(s), as
well as territory borders.
Territory Plotprints a map showing all location extensions in the selected territory(s).
Week Plotprints a map showing the routes for the selected territory(s) and week(s).
You can include the plots as part of a report group. If you include plots in your report
group, the group must be printed from the Planning Editor, not the Reports module.
Notes: The plot reports use the options most recently saved in the Map Options notebook.
this option will not be available to you.
opens with the Planning Sessions window visible. Double-click on the planning
the reports.
Step 3: Right-click on the report, and select Print from the menu that pops up. The
Step 4: Select the session(s), territory(s), and week(s) as appropriate for the report and
Planning Editor Reports List Session Plot/Territory Plot/Week Plot Preview/Print
[OK]
Operations Guide
671
Transferring Data to a New Planning Session

The Planning Editor uses planning sessions to encapsulate all the data needed to solve a
single routing problem. One of the benefits of keeping all this data in the planning session
is you can transfer selected portions of the data to another planning session, where you
can solve the problem a different way without losing the solution you came up with in the
original session. The Session Transfer tool allows you to easily select location extensions
that you want to transfer to a different planning session, as well as select some of the
supporting information you want to transfer.
Note: You must be in the planning session that contains the location extensions you want
to transfer.
want to work with.
Step 2: Click on the Tools menu and select Session Transfer. The Session Transfer
window opens.
Step 3: In the Destination Sessions area, click on the sessions you want to receive the
information. If selecting multiple destination sessions, hold down the [Ctrl] key
while clicking on the sessions.
Note: If you need to create a new destination session, click the [Add Session] button.
The Add Session window opens. Complete the information and click the Save
icon. See Working with Planning Sessions for more information.
Step 4: Select the session(s) you want the editor to switch to once the transfer is
complete in the Current Session on Exit area.
When transferring extensions to another planning session, you can

specify some of the data that is transferred.
672

Step 5: In the Filters area, choose the location extensions you want to transfer.
To transfer all the location extensions, click All Location Extensions.
To transfer selected location extensions, click Advanced, then click the
[Advanced] button. The Session Transfer - Advanced Selection window opens.
Click in the boxes to define the criteria for your search and enter the search
criteria. Specify whether you are searching for entries that meet all the criteria (an
AND search) or entries that meet at least one of the criteria (an OR search) and
click [Select]. You can also search on any column shown in the window. For these
more complex searches, use the Search Manager. Click [Done] when all desired
entries have been selected.
Note: Breaks, waits, and layovers will not be transferred.
Step 6: Select the Transfer Options you want to use. Each option is described below.
Transfer User Defined Fieldstransfers the contents of the user defined fields
to the destination session(s). Even if you choose not to transfer the contents of the
fields, the headers will exist in the destination session(s).
Maintain Territory IDplace the location extension in the same territory in the
destination session(s) as it is in the source session. If no territory with this ID
exists in the destination session, the Planning Editor will create it. If the
destination session already has a territory with that ID, the location extensions will
be added to the existing territory.
Update Previous Informationtransfer the current territory ID, weeks,
depot, and days to the Previous fields in the destination session(s).
Set Assign Daysinclude the location extensions when Assign Days is run in the
destination session(s).
Location Extensionscopy or move the extensions from the source session. If
you move the extensions, they will be deleted from the source session when the
session is saved.
Notes: If the destination session has the same number of cycle weeks as the source
session, all routing information will automatically be transferred.
If the number of weeks defined for a location extensions service pattern set does
not match the number of weeks in the new planning session, the extension will be
unrouted in the new session.
Step 7: Click the [Transfer] button to transfer the selected location extensions to the
destination session(s).
Planning Editor Tools Session Transfer [OK]
Operations Guide
673
Saving a Copy of the Current Session

As you are working with a session, you may want to create an exact copy of the current
session so that you can try a what-if scenario without worrying about altering your
original routes. The Save Session As menu option will allow you to create an exact copy
of your current session. The copy will have the same properties as the original session,
such as same weeks and extensions, and will include breaks and mid-route depots.
Step 1: Click File, then Save Session As. The Save Session As window opens.
Use the Save Session As menu to

save an exact copy of your current
session.
Step 2: Enter a Description for the session.

Step 3: Choose the session options, such as the Scenario and Time/Distance
Calculation.
speeds when creating routes in the planning session
creating routes in the planning sessions
674

creating routes in the planning sessions
Note: In order to use the historical travel speed feature, you must select the RouteNet or
SuperMatrix as your time/distance calculation.
Step 5: If you want to use a time of day model to restrict travel in defined areas during
defined time, click the Time of Day Restriction Model arrow to select the model
to use for the planning session. This allows you to choose a time of day
restriction model to choose a time of day restriction model to designate periods
during the day in which restricted equipment types cannot travel in restricted
areas or paths. This prevents some vehicles, such as large trucks, from being
routed on restricted roads while allowing other vehicles, such as small trucks or
vans, to use those roads.
Step 6: Complete the other fields as necessary.
Step 7: Click on the [OK] button. An exact copy of your current session appears in the
list of planning sessions in the Planning Sessions window.
Operations Guide
675
Archiving the Planning Session
Archiving the Planning Session

The Planning Editor lets you create an archive containing all the information in an
individual planning session. When the archive is created, all necessary information for the
session, including employee, equipment, location, and location extension information, is
included in the archive. This feature is very handy if you need to send data to Roadnet
Technologies.
Note: You can also archive a planning session in the Maintenance module.
opens with the Planning Sessions window displayed.
Step 2: Right-click on the session in the Planning Sessions window and select Archive
from the menu that pops up ([Ctrl]+[V]), or click the Archive icon. A Save As
window opens.
Step 3: Enter the name to archive the session as, then browse to where you want the
archive stored.
Step 4: Click the [OK] button to archive the routing session.
Planning Editor Planning Sessions window Archive ([Ctrl]+[V])
676

Uploading the Planning Routes

After you have created your routes in the Planning Editor, you can transfer the routing
information to your network, mainframe, or another computer. The User Upload tool
creates an ASCII file in which you can specify the fields to be included, as well as their
placement and length in the file. You can upload any of the fields that can be imported
from the location or location extension file. In fact, User Upload will automatically
include any field included in the location or location extension layout for the layout set,
using the position and length specified in those layouts. See Import Locations or Import
Location Extensions for more information on those fields. In addition to those fields, you
can upload additional fields, which are specified in the User Upload layout. See Creating
Import Layout Sets, Setting the Import File Layouts, and User Upload Available Fields
Note: Create a layout set for exporting data before starting this procedure. See Creating
Import Layout Sets for more information.
want to work with.
Step 2: Click on the Tools menu and select User Upload. The Select Routes window
opens. Select the territories, weeks, and days containing the stops you want to
upload. If you want to include location extensions unassigned to a territory or not
placed on a route, check Use Unassigned or Use Unrouted. All routes on those
selected items will be uploaded. Click the [OK] button. The User Upload
window opens.
Note: Reload depots cannot be uploaded to User Upload.
in the Output File Name field below. See Creating Import Layout Sets for more
information on creating an layout set for exporting data.
You can change the file layout for

the user upload file by clicking the
[File Layout] button and selecting
Edit to open the Layout window.
Operations Guide
677
Step 4: To change the name or location of the export file, click the [File Layout] button
and select Edit Layout, then User Upload. The User Upload Layout window
opens. Enter the path and name of the file to be created.
Step 5: To review or change the position and length of fields in the destination file,
click the [File Layout] arrow and select Edit Layout, then the name of the layout.
See Setting the Import File Layouts, User Upload Available Fields, Location
Available Fields, or Location Extension Available Fields for more information.
the [File Layout] arrow and choose Preview from the menu that pops up. The
report will include the layout information for all three layouts (import locations,
import location extensions, and user upload). The organization of the three layouts
in the report - separate pages vs. intermingled - will depend on the import layout
report options selected in the Import module.
Notes: Any changes made to the location or location extension layouts will be used when
these items are imported. To avoid potential problems, use separate layout sets for
importing and exporting, and verify the correct export layout set is displayed in
Choose Layout Set before making any changes to a layout.
uploading planning routes.
Step 6: If you specified to include week information in the upload file, such as active
weeks from the location extension layout or previous weeks, choose whether you
want the weeks shown as 1 and 0 (true and false) or X and space.
For instance, in a four week cycle, if the location extension is delivered on weeks
1 and 3, the information will appear in one of these formats:
1010
XX
Note: Twenty-four weeks of data will always appear in the upload file, even if the
planning session is less than 24 weeks. The data will simply repeat to look like 24
weeks. For instance, if your session is 2 weeks, and a location is delivered the first
week, the active weeks will be uploaded as 101010101010101010101010.
Step 7: If you specified to include day information in the upload file, such as a day
string from the location extension layout or the previous days, specify whether
you want the days indicated by a letter (MTWRFSU) or 1 and a 0.
For instance, if the location extension is delivered on Monday and Friday, the
information will appear in one of these formats:
M F
010001
Note: When exporting the day string, Sunday is placed in the first position - the days of
the week are UMTWRFS.
678

Step 8: If you specified to have the latitude and longitude uploaded in the Locations
layout, enter the numbers to the right of the decimal you want in the Lat/Lon
precision if using decimal degrees fields. Choose whether to have the quadrant
on the globe indicated by negative and positive signs on the latitude and
longitude, or have the actual quadrant appear after the latitude or longitude (ex.
39.2654N).
Note: Make sure the punctuation is appropriate for the language setting on your computer.
Time.
Step 10: Click the [Upload] button. When the upload is complete, click the [View
Errors] button to display a list of errors that occurred.
Planning Editor Tools User Upload [Upload]
Operations Guide
679
Updating the Delivery Days in Roadnet

After you have created your routes in the Planning Editor, you may want to update the
delivery day information used for the locations in the Roadnet Routing Editor. If the
locations delivery days are not updated for the Routing Editor, you may have unexpected
off-day deliveries when using the routes created in Territory Planer. You can update the
delivery days while sending the routes to Roadnet, or without sending the routes; to
update the delivery days without sending the routes, follow the steps below. You can
update the delivery days for all locations on a territory, week, or route, or only for selected
locations.
work with.
Step 2: Click on the Tools menu and select Update Delivery Days. The Select Routes
window opens. Select the territories, weeks, and days containing the stops you
want to push. To include location extensions that are unassigned to a territory or
unrouted, check Use Unassigned or Use Unrouted. The delivery days for all
locations on the selected items will be updated. Click the [OK] button. The
Update Delivery Days window opens, showing the routes that were selected.
Note: If you only want to push routes on a selected territory, week, or day, right-click
on the territory, week, or day in the Territories, Weeks, or Days window and select
Update Delivery Days from the menu that pops up. The Update Delivery Days
window opens, showing the routes that were selected to be pushed.
Step 3: If you do not want to update the delivery days for locations that were not
routed, check Skip Unrouted Extensions. If this option is not selected, those
locations that are not routed in this planning session will have no valid delivery
days for the Routing Editor.
Once the delivery days have been updated, you can review a
report summarizing the locations that were affected.
Note: If you started Update Delivery Days from the Tools menu or from the Route or
Weeks window, the Skip Unrouted Extensions box is not available. The delivery
days for all locations, including those that are not routed, will be updated.
680

Step 4: Click the [OK] button. The valid delivery day information for the selected
locations is updated.
Step 5: When the update is complete, you can view a report summarizing the update.
To set the report options, click on the [Report Options] button. To include only
those locations whose delivery days were changed, check Show Only Updated
Locations. Click on the Sort By arrow and choose the criteria that will be used to
sort the report. Select whether the report should be sorted in ascending (ABC) or
descending (CBA) order.
Click the [Preview Report] button to view the report. You can print or export the
report. See Report View Windows for more information.
Planning Editor Tools Update Delivery Days [OK]
Operations Guide
681
Sending the Routes to Roadnet

Once you have created your strategic routes in the Planning Editor, you can transfer the
routes directly into Roadnets Routing Editor, where you can use them as your daily
routes or convert them to standard routes.
work with.
Step 2: Click on the Tools menu and select Update Roadnet Daily Routes. The Select
Routes window opens. Select the territories, weeks, and days containing the stops
you want to push. All stops on those selected items will be pushed to Roadnet.
Click the [OK] button. The Update Roadnet Daily Routes window opens,
showing the routes that were selected to be pushed.
Notes: If you only want to push routes on a selected territory, week, or day, right-click
Update Roadnet Daily Routes from the menu that pops up. The Update Roadnet
window opens, showing the routes that were selected to be pushed.
Any unassigned or unrouted extensions will be unassigned in Roadnet.
All breaks, waits, layovers, reload depots, and depots will be transferred to the
Routing Editor along with the routes.
Step 3: Select the starting date for the routes in Roadnet. The first routing session in
Roadnet will use this date; subsequent sessions will use the next appropriate date.
For instance, if you are pushing routes for Monday, Tuesday, Wednesday,
Thursday, and Friday, and you make the starting date December 17, 2001 (a
Monday) the Monday session will be December 17, the Tuesday session will be
December 18, etc.
To select the starting date, click on the arrow to open a calendar. To change the
month, either use the arrows on the top of the calendar to scroll through the
months, or click on the month and select from the menu that pops up. To change
the year, click on the year and use the small arrows to scroll to the correct year.
Click on a date to select it.
682

Step 4: To have all the routes placed in a single session, check Create Single Session. If
this option is not selected, a session will be created for each day of the week for
which routes were pushed.
When the routes are pushed to
Roadnet, you can have all of
them placed in a single session,
or have sessions created for
each day.
Step 5: To remove any information that already exists in the routing session, check
Clear Session(s) Prior to Update.
Step 6: To have the locations delivery days updated to match the routes being sent,
check Update Delivery Days.
Step 7: Click the [OK] button to push the routes to Roadnet. Once the push is complete,
click the [View Log] or [View Errors] buttons to see results of the push.
Step 8: If Update Delivery Days was checked, you can view a report summarizing the
locations that were updated.
To set the report options, click on the [Report Options] button. To include only
those locations whose delivery days were changed, check Show Only Updated
Location Extensions. Click on the Sort By arrow and choose the criteria that will
be used to sort the report. Select whether the report should be sorted in ascending
(ABC) or descending (CBA) order.
Click the [Preview Report] button to view the report. You can print or export the
report. See Report View Windows for more information.
Planning Editor Tools Update Roadnet Daily Routes [OK]
Operations Guide
683
Sending the Planning Routes to MobileCast

Once you have created routes in the Planning Editor, you can send them to MobileCast,
Roadnet Technologies dispatching system. In MobileCast, the dispatcher can track the
routes as they are run, updating the information as necessary.
Before you can push the routes to MobileCast, each route being pushed must have an ID
assigned to it.
Note: If you were not granted permission to update MobileCast in the Administration
module, this option will not be available to you.
work with.
Step 2: Click on the Tools menu and select Update MobileCast. The Select Routes
window opens. Select the territories, weeks, and days containing the routes you
want to transfer. All routes on those selected items will be sent to MobileCast.
Click the [OK] button. The Update MobileCast window opens, showing the
routes that were selected to send.
The Update MobileCast window displays the

routes you have selected to transfer to
MobileCast. If a selected route has no stops, it
will not appear in the list or be transferred.
Notes: If you only want to transfer items on a selected territory, week, or day, right-click
Update MobileCast from the menu that pops up. The Update MobileCast window
opens, showing the routes that were selected to send.
All breaks, waits, layovers, reload depots, and depots will be transferred to the
Dispatcher along with the routes.
Step 3: Select the date you want the first route to be run as the beginning route date.
Routes for that weekday will be assigned to that date; routes for subsequent days
will be assigned the subsequent dates. For instance, if you select January 14,
2002, a Monday, as the beginning date, all Monday routes will be assigned to the
14th, Tuesday routes will be assigned to the 15th, etc.
Note: Routes for prior days will not be transferred. In this example, any routes you have
for Sunday would not be transferred.
684

Step 4: Click the [OK] button to transfer the routes. If there were errors during the
transfer, the [View Errors] button will be available; click the button to view the
errors.
Planning Editor Tools Update MobileCast [OK]
Operations Guide
685
Send Routes to netScheduler

Used with: Territory Planner, netScheduler
Once you have created your strategic routes in the Planning Editor, you can transfer the
routes directly to netScheduler, where they will form the basis of your netScheduler
routes.
Step 1: Click on the Planning icon to open the Territory Planner module.The Editor
opens with the Planning Sessions window visible.
Step 2: Click on the Tools menu and select Seed NetScheduler. The Seed NetScheduler
window opens.
Step 3: Select the territories, weeks, and days containing the stops you want to push.
All stops on those selected items will be pushed to netScheduler. Click the [OK]
button. The Seed NetScheduler window opens, showing the routes that were
selected to be pushed.
You can send routes to

netScheduler so that on-demand
deliveries can fill up existing
planned routes.
Notes: If you only want to push routes on a selected territory, week, or day, right-click
Seed NetScheduler from the menu that pops up. The Seed NetScheduler window
opens, showing the routes were selected to be pushed.
Reload depots cannot be uploaded to NetScheduler.
Step 4: Select the starting date so that the system knows where to start inserting route
information for netScheduler. For instance, if you are pushing routes for Monday,
Tuesday, Wednesday, Thursday, and Friday and you make the starting date
December 17, 2001 (a Monday), the Monday session will be December 17, the
Tuesday session will be December 18, etc.
686

You can type the starting date, or click on the arrow to open a calendar. If you are
Step 5: To schedule the delivery times, select one of the following options from the
Delivery Window Options section.
Planned arrival/dateselect this option if you want to assign stops in
netScheduler to the delivery time window that most closely matches the planned
delivery time in Territory Planner.
Closest location time windowselect this option if you want to assign stops in
netScheduler to the delivery time window that most closely matches the desired
delivery time specified for the location.
All day windowselect this option if you want to use netScheduler to schedule
the delivery at the most optimum time window available (lowest delivery cost)
within the same route assignment.
Step 6: To allow the system to place stops in a different order but on the same route,
check Allow stops to be resequenced.
Step 7: To delete orders that already exist in netScheduler, check Purge existing orders.
This will delete all orders for that specific scheduler session (Region/Area/
Delivery Day).
Step 8: Click on the [OK] button to push the routes to netScheduler. Once the push is
complete, click the [View Log] or [View Errors] buttons to review any errors or
stops that were pushed.
Planning Editor Tools Seed NetScheduler [OK]
Operations Guide
687
Working with Depot Planner

Note: If you were not granted permission to access Depot Planner in the Administration
module, this feature will not be available to you.
The Planning Editor includes a tool that allows you to evaluate potential locations for new
depots, or the effects of closing an existing depot. Using this tool, called Depot Planner,
you can easily add new depots, close existing depots, and see the effects of changing
your depots.
Depot Planner is started from the Tools menu in the Planning Editor. When Depot Planner
is started, a map opens, showing all existing depots and location extensions. Most of the
work for Depot Planner is done from the map. All changes made to depots in Depot
Planner, such as adding a new depot or geocoding an existing depot, are reflected in all
planning sessions in Territory Planner. When changes are made in Depot Planner, the
routing information for the current group is erased. Therefore, it is recommended that a
separate planning session be created when using Depot Planner.
Note: Depot Planner is a purchasable option within the Roadnet Transportation Suite. If
you have not purchased this option, the menu will not be available. Contact your
sales representative for more information on Depot Planner.
Starting Depot Planner
In order to evaluate potential new depots, you need to start Depot Planner.
work with.
Step 2: Click on the Tools menu and select Depot Planner. The Depot Planner map
opens, showing all existing depots and location extensions.
Planning Editor Tools Depot Planner
Adding a Depot
When you add a depot in Depot Planner, it is added to the database and becomes available
for all planning sessions. As you add new depots, they will appear on the map.
Step 1: On the Depot Planner map, click the Add Depot icon. The Add Location window
opens.
Step 2: In the ID field, enter the unique ID for the depot.
Step 3: On the Attributes page, enter the Description and address information for the
depot. The address information will be used to geocode the depot.
Step 4: Choose a time window type, service time type, and account type for the depot.
These can all be set to the default or a special depot type, if desired.
688

Step 5: Click on the Map tab to geocode the depot, or click the Save icon ([Ctrl]+[S]) to
save the depot.
Planning Editor Depot Planner Add Depot icon Save icon ([Ctrl]+[S])
Geocoding a Depot in Depot Planner
One of the purposes of Depot Planner is to help you determine the best place to add a new
depot. The easiest way to test depots in multiple places is to add one new depot, geocode
it in different locations and test it.
Note: Regeocoding a depot takes effect immediately and affects the depot throughout
the Roadnet Transportation Suite. Therefore, if you want to evaluate closing an
existing depot and opening a depot in a new location, add the new depot and
geocode it, rather than regeocoding the existing depot.
Step 1: On the Depot Planner map, right-click on the depot and select Geocode from the
menu that pops up. The cursor changes to a cross-hair.
Step 2: Click where you want the depot to be moved to. The depot is geocoded to the
new location.
Note: Many of the map features, such as zoom in, zoom out, and center, are available to
help you move around the map.
Assigning Location Extensions to the Depots
Once you have added the new depots and have geocoded them in the proper location, you
can assign the location extensions to the depots. You can assign the location extensions
to the closest depot based on distance or travel time. Only depots that are selected are
considered when the location extensions are processed; selected depots are colored, while
deselected depots are gray. To select or deselect a depot, click on it.
To assign the location extensions to all selected depots based on distance, click the
Process icon on the Depot Planner map. All the location extensions will be assigned to the
nearest selected depot, and will be displayed with the same color as the depot.
Note: You do not need to unassign the location extensions before processing; they will
automatically be unassigned before processing starts.
To assign location extensions to a depot by travel time, rather than distance, right-click
on the depot and select Process by Time from the menu that pops up. Enter the maximum
number of minutes in the Process by Time window and click [Process]. All location
extensions within that time will be assigned and will be displayed with the same color as
the depot.
Note: In order for Process by Time to work, all location extensions need to be
unassigned. Click the Unassign All icon to unassign the location extensions.
Any assignments made using Process by Time will be overridden when Process is
run again.
Operations Guide
689
Evaluating the Depot Planner Results
Once you have assigned the locations to the depots, you can use the features of the
Planning Editor to evaluate the assignments that were made.
To see the number of location extensions assigned to each depot, the cumulative
distance from the depot to each location extension, and cumulative load and service time,
use the Territory window. You can arrange the columns in the window to make the
pertinent information easily accessible, and even print the results as a report.
To see the current and previous depot for the locations, including the difference in the
distance between the location and the current and previous depot, use the Location Origin
Summary window. To see the list of all locations in the planning session, click on File,
then Location Origin Summary. The Location Origin Summary for all locations opens.
To see the list of all locations for an individual territory(ies), right-click on the territory
in the Territory window and select Location Origin Summary from the menu that pops up.
The Locations Origin Summary for all selected territories opens.
To see geometric and statistical information about a territory, right-click on the
territory and select Territory Analysis from the menu that pops up. The Territory Analysis
window for the territory opens, showing the territorys centroid, the average distance from
the depot to each location, and the total quantity on the territory.
The Territory Analysis

window can provide a lot of
information about the
locations assigned to the
depot, including the
average distance from each
location to the depot.
690

To see statistical information for all the territories, such as the total quantity, service
time, stops, etc. click on the File menu and select Territory Scoreboard.
Operations Guide
691
692

Loading Trucks in the FleetLoader Loading Editor
Loading Trucks in the FleetLoader Loading Editor

Note: If you were not granted permission to open the Loading Editor in the
The FleetLoader Loading Editor allows you to load your trucks, evaluate how they were
loaded, and edit them as necessary. You can use the Loading Editor to build pallets that
will be loaded in bulk trucks or to load side loaders; there are tools designed to use in each
situation. In the Loading Editor you can:
Enter FleetLoader
Load Trucks
Define FleetLoader Options
Prepare to Edit Trucks
Move SKUs
Save the Trucks
Print Reports
When loading the trucks, you can choose from driver-friendly, warehouse-friendly, or a
hybrid of the two. Once the trucks are loaded, you can move SKUs from bay to bay, layer
to layer in a pallet, move unassigned product to a bay, or even reload a truck from scratch,
trying a different strategy. In addition, you can print reports directly from the Loading
Editor to give to the drivers and warehouse personnel.
Operations Guide
693
Setting Up to Load Bay Trucks

If you are using FleetLoader to load bay trucks, there are some Maintenance items you
will want to make sure are properly set, as well as some settings in the Loading Editor you
will want to set. This section is intended to guide you through these steps.
Setting the Bay Truck Maintenance Items
Before loading your bay trucks, you will want to make sure the following items are
created and updated with the appropriate information in the Maintenance module:
Set up Product items:
Package Typesmake sure to enter the ID and Description. If the bay types have been
entered, set the bay type capacity.
SKU Brandsmake sure to enter the ID and Description.
SKUsmake sure to enter the ID and Description, and select the proper package type and
SKU brand. If using warehouse zones, make sure to select the correct warehouse zone.
Warehouse Zones (if applicable)make sure to enter the ID and Description, and
choose the loading priority.
Set up Equipment items:
Bay Typesenter the ID, Description, and the bays height, width, and depth. If the
package types have been entered, set the bay type capacities.
694

Equipment Typesenter the ID and Description. On the FleetLoader tab, check Trailer
and enter the number of rear axles. Select Side Loader and enter the Driver Side Bay Info.
Click the [Define Bays] button to specify the ID and description for each bay.
When creating a bay truck equipment type, check Side Loader and enter the
number of bays on the drivers side. FleetLoader will automatically
duplicate the information for the passenger side of the truck.
EquipmentOn the General page, enter the ID and Description and select the
Equipment Type. To specify information about the individual bays, such as the preferred
package types and preferred SKUs. or to designate the bay as disabled, or to reserve the
bay for small quantities of SKUs, click the [Define Bay Preferences] button, double click
on the individual bays, and complete the pages of the Bay Preference Maintenance
notebook as appropriate.
Equipment Overrides (if applicable)enter the Route ID and Description, and select
the equipment that will be used.
Set up Loading Rules, as necessary:
Stack Rules Methodsset up the groups for the stack rules you want to use.
Mix Rules Methodsset up the groups for the layer and pallet mix rules you want to use.
Operations Guide
695
Warehouse Zone Pick Order Methodsset up the groups for the warehouse zone pick
orders you want to use.
Stack Rulesselect the package type and the package type it cannot stack on top of.
Pallet/Bay Mix Rulescreate the mix rules that prevent product from different
warehouse zones from mixing, product of different package types from mixing, or
product from product with different SKU brands from mixing. SKUs that have any mix
rules preventing them from mixing will not be loaded together in the Loading Editor.
Set up Location information, as necessary:
Loading Preferences (if applicable)only used with Driver Friendly. Enter the Location
ID and Type, and choose the portion of the truck where product should be loaded for that
location.
Once the maintenance items have been established, you need to set the loading
parameters.
Setting the Bay Truck Loading Parameters
In the Loading Editor, there are some settings that are more appropriate for loading bay
trucks than for loading bulk trucks and pallets. The following are recommendations for
setting the loading and viewing options in the Loading Editor.
Choosing the editor options:
The Editor Options notebook lets you specify how the windows in the Loading Editor will
appear, as well as when warnings will be displayed.
On the Warnings page, select the warnings you want to use. Layer mix rules will most
likely not be used when loading bay trucks.
On the General page, select the colors you want to represent the ways the bays were
loaded.
696

On the Truck Profile page, select the options you want to use.
Choose the Display

options you want by
checking the associated
box here.
Choosing the loading options:

You will also need to establish the options you want to use when loading trucks in the
Loading Options notebook.
Strategy pageselect the strategy you want the Loading Editor to use. Most likely, this
will be Warehouse Friendly or Hybrid (Warehouse First).
Driver Friendly pageselect the appropriate Bay/Pallet Mix Rules Method.
Warehouse Friendly pagemake sure the following options are selected: Optimization
Pass, Allow SKUs to Split Between Bays/Pallets and SKU and/or Package Type
Preference Passes. Choose the Loading Order and Loading Rules. Make sure Enable
Pallet Loading is not selected.
Operations Guide
697
Make sure you choose the loading order to specify which SKUs will be loaded first.
Global pagemake sure Load Front to Rear and Obey Stack Rules are selected.
Evaluating and Editing the Loaded Trucks
Once the trucks have been loaded, and you are viewing the trucks, you may want to use
the following windows for evaluating and editing each loaded truck:
Truck Profileuses a picture of the truck to show how full each bay is. You can move
product into a bay in the Truck Profile but cannot move it out. To see more detailed
information about a bay, click on it in the Truck Profile; the Bay Contents window
changes to show that bay.
Bay Contents windowshows the product loaded into each bay, and the order in which
it is loaded. You can move SKUs between bays or into bays using the Bay Contents
window.
698

Unassigned SKUs windowlists the SKUs that are not loaded on the truck. You can
move SKUs from the Unassigned SKU window to the Bay Contents window or Truck
Profile to load them on the truck.
Once you have the load parameters set, you can load the trucks.
After the trucks have been loaded, you can print reports to help the warehouse personnel
load the trucks.
Printing the Bay Truck Reports
Once your bay trucks have been loaded, you will want to print reports for the warehouse
telling how the trucks are to be loaded. Some of the commonly used reports are the Pick
Sheet and Load Truck Diagram, but there are many you can choose from.
Operations Guide
699
Setting Up to Load Bulk Trucks

If you are using FleetLoader to load pallets and bulk trucks, you will want to set up your
maintenance items in a certain way, as well as some settings in the Loading Editor. The
following sections outline the steps you need to follow when loading bulk trucks.
Setting the Bulk Truck Maintenance Items
In the Maintenance module, you will want to make sure the following items are created
and updated with the appropriate information:
Set up Product items:
Package Typesmake sure to enter the ID and Description. If the pallet types have been
entered, enter the pallet capacities.
SKU Brandsmake sure to enter the ID and Description.
SKUsmake sure to enter the ID and Description, and select the proper package type and
SKU brand. If using warehouse zones, make sure to select the correct warehouse zone.
Warehouse Zones (if applicable)make sure to enter the ID and Description, and
choose the loading priority.
Set up Equipment items:
Pallet Typesenter the ID, Description, Width, and Depth.
700

Equipment Typeson the General tab, enter the ID and Description. On the FleetLoader
tab, select Bulk, then enter the Width and Depth of the bulk equipment type as well as the
empty space within the rows and between the pallets.
Width and depth must be measured in the same units as the pallet type dimensions.
Equipmenton the General page, enter the ID and Description and select the Equipment
Type.
Equipment Overrides (if applicable)enter the Route ID and Description, and select
the equipment that will be used.
Set up Loading Rules, as necessary:
Stack Rules Methodsset up the groups for the stack rules you want to use.
Mix Rules Methodsset up the groups for the layer and pallet mix rules you want to use.
Warehouse Zone Pick Order Methodsset up the groups for the warehouse zone pick
orders you want to use.
Stack Rulesselect the package type and the package type it cannot stack on top of.
Pallet/Bay and Layer Mix Rulescreate the mix rules that prevent product from
different warehouse zones from mixing, product of different package types from mixing,
or product from product with different SKU brands from mixing. SKUs that have any mix
rules preventing them from mixing will not be loaded together in the Loading Editor. You
Operations Guide
701
can create mix rules that prevent SKUs from loading on the same layer, as well as mix
rules that prevent them from loading on the same pallet.
Pallet Loading Methodsenter the ID and Description.
Set up Location information:
Loading Preferences (if applicable)only used with Driver Friendly. Enter the Location
ID and Type, and choose the portion of the truck where product should be loaded for that
location.
Once the maintenance items have been created, the parameters used in the Loading Editor
can be established.
Setting the Bulk Truck Loading Parameters
In the Loading Editor, there are some settings that are more appropriate for loading bulk
trucks than for loading bay trucks. The following are recommendations for setting the
loading and viewing options in the Loading Editor.
Choosing the editor options:
The Editor Options notebook lets you specify how the windows in the Loading Editor will
appear, as well as when warnings will be displayed.
On the Warnings page, select the warnings you want to use.
On the General page, Under Bulk Truck Percent-Full Calculation, elect .
Select how you want

the windows in the
Loading Editor to
appear on the General
page of the Options
notebook.
Choosing the loading options:

You will also need to establish the options you want to use when loading trucks in the
Loading Options notebook.
702

Strategy pageselect the strategy you want the Loading Editor to use. Most likely, this
will be Driver Friendly or Hybrid (Driver First).
Driver Friendly pagemake sure the following options are selected: Alternate Sides of
Vehicle (for Same Stop) and Limit to One Stop per Pallet. Choose the Loading Order and
Loading Rules. Make sure Enable Pallet Loading is selected, then click the [Pallet
Loading Options] button to enter the pallet loading options.
Note: For more information on the Pallet Loading Options, see Pallet Loading Options
on the Driver Friendly Page of the Loading Options notebook.
When loading bulk trucks, make sure Alternate Sides of Vehicle is checked so
that all product will not be loaded on one side of the truck.
Warehouse Friendly pagemake sure Full Pallet Loading for Same SKU is not
selected.
Global pagemake sure Load Front to Rear is selected.
Evaluating and Editing the Loaded Trucks
Once the trucks have been loaded, and you are viewing the trucks, you may want to use
the following windows for evaluating and editing each loaded truck:
Operations Guide
703
Unassigned SKUs windowlists the SKUs that are not loaded on the truck. You can
move SKUs from the Unassigned SKU window to the Layer View to load them on the
truck.
Layers Viewdisplays the loaded truck; for each pallet on the truck you can see the
SKUs and stops in each layer. You can move SKUs from pallet to pallet, layer to layer,
or to the Unassigned SKU window.
Truck Profileuses a picture of the truck to show the location and type of each pallet,
and how full each one is. You can rearrange pallets, remove them or add new ones using
this view window; you can also move product from one pallet to another. To see more
detailed information about a pallet, click on it in the Truck Profile; the Pallet Contents
View window changes to show that pallet.
Once the loading parameters have been established, you can load the bulk trucks. Once
the trucks have been loaded, you can print reports that house personnel can use to load the
trucks.
After the trucks have been loaded, you can print reports to give to your warehouse
personnel.
Printing the Bulk Truck Reports
Once your trucks have been loaded, you will want to print reports for the warehouse
telling how the trucks are to be loaded. Some of the commonly used reports are the Load
Truck Diagram and the Load Validation Diagram, but there are many you can choose
from.
704

Entering the Loading Editor
Entering the Loading Editor

The FleetLoader Loading Editor will load your trucks according to rules you establish,
and then lets you analyze and edit the loaded trucks. You can also print reports about the
loaded trucks directly from the Loading Editor. Before you can use the features of the
Loading Editor, you must start it.
Step 1: Click the Loading icon to open the FleetLoader module. The Editor window
opens.
Step 2: When the module opens, the Routing Sessions window displays, listing all
existing sessions. Double-click on the appropriate session to view the routes for
that session. The Route Sessions window opens.
Operations Guide
705
Loading Trucks in the Loading Editor

Before you can load the days orders onto the trucks/pallets, you must have the location
preferences, stack rules, mix rules, warehouse zones, pallet loading methods, stack rules
methods, mix rules methods, warehouse zone pick order methods, pallet types, and other
necessary information established in the Maintenance module. After this information is
available, you can load your trucks from within the Loading Editor.
Notes: Although the routes are listed, they are not loaded unless you have run Load
Trucks. If Load Trucks has not been run, all products are currently unassigned to
bays/pallets.
When the routes are retrieved, the Loading Editor looks to see if an equipment
override exists for the route. If the equipment assigned to the route does not match
the equipment listed in the override, a check appears in the Equipment Override
column.
Step 3: Click on the Loading icon to open the FleetLoader module. The Editor window
opens.In the Routing Sessions window, double-click on a routing session to view
the routes for the session.
Step 4: Select the route(s) you want to load.
To load selected routes, click on the Load menu and select Load Selected
Route(s), or click on the Load the Currently Selected Route icon.
To load all available routes, click on the Load menu and select Load All
Available Routes, or click on the Load All Available Routes icon.
The Load Trucks window opens.
Note: If you are loading pallets, make sure the proper pallet method is being used. Rightclick on the route and select Pallet Method from the menu that pops up. Select the
proper method and click the [OK] button.
Step 5: Select the routing pass you want to use to load the route(s).
706

Step 6: To load the selected routes, click the [Load] button. The truck loading process
starts; a message will appear in the bottom of the window when the process is
complete. If any errors occurred, click [View Errors] to review the errors.
After running a loading

pass, the results will
appear at the bottom of
the window.
To change or review the options selected for loading the trucks, click the [Options]
button. See Using the Load Truck Options Notebook for more information.
Note: If you were not granted permission to change the Loading Options in the
Administration module, you will not be able to open the Loading Options
notebook.
Loading icon Load Load all Available Orders/Run [Load]
Operations Guide
707
Using the Loading Options Notebook

Before loading your trucks in the Loading Editor, you need to specify the loading options
you want to use. There are four main strategies you can choose from: Warehouse
Friendly, Driver Friendly, Hybrid (Warehouse First), and Hybrid (Driver First). The
availability of the remaining options depends on the strategy selected. By default, the
Warehouse Friendly settings are selected.
When setting up the options in the Load Options notebook, you are establishing the
parameters that will be used for an individual pass. You can create several passes to allow
different types of routes to be loaded differently. For instance, routes using bay trucks
could be loaded using a driver friendly strategy, while bulk trucks could be loaded
warehouse friendly.
To open and edit your loading options with a routing session open:
opens.
Step 2: In the Routing Sessions window, double-click on a routing session you want to
work with.
Note: To change the loading options without opening a session, such as if you are using
Compute Pallets in the Routing Editor, click the Load menu and select Loading
Options.
Step 3: Select the route(s) you want to load.
To load selected routes, click on the Load menu and select Run, or click on the
Load the Currently Selected Route icon.
To load all available routes, click on the Load menu and select Load All
Available Routes or click on the Load All Available Routes icon.
The Load Trucks window opens.
Step 4: Click the [Options] button. The Loading Options notebook opens.
Step 5: On the Strategy page, create a unique name for the pass in the Pass Label field,
then click [Add] to add this pass to the Pass Name window.
708

Step 6: hoose the primary loading strategy for the pass. See Strategy Options in the
Loading Editor for a description of the strategies.
You can create multiple loading passes, each with a different set of loading options.
Step 7: Click the Driver Friendly, Warehouse Friendly, and Global tabs to move to the
other pages and select the other options you want. A selection is chosen when a
check appears in the box. The options available depend on the strategy selected.
As you move through the pages, make sure the proper pass is selected in the Pass
Name list.
Step 8: Save your settings.
To use your settings for the next time you run the pass only, click the [Apply]
button.
To save your settings for future sessions, click the [Save] button.
To restore the default settings, click the [Defaults] button.
To exit without saving, click the [Cancel] button.
Loading icon Load Options [Apply]/[Save]
Operations Guide
709
Strategy PageLoading Options notebook
The Strategy page of the Loading Options notebook lets you choose the tactic that will be
used when loading the trucks. The strategy selected here affects the options that are
available on the other pages of the notebook.
Warehouse Friendlyfocuses on loading the same SKUs together, making it easier for
the loader to pull product and load the truck. The system groups the same SKUs together
and loads the SKU with the largest volume first. If bay preferences were established in
the Maintenance module, and SKU and/or Package Type Preference Passes are selected,
the system will load those SKUs into bays with established preferences for those SKUs
and package types. If the Optimization Pass is selected, SKUs without bay preferences
will be loaded last.
Note: If you specified a maximum number of SKUs in a bay in the Maintenance module,
any Warehouse Friendly or hybrid loading strategy will use that maximum
number of SKUs in loading. Max SKUs is ignored, however, in Driver Friendly
loading.
Driver Friendlyfocuses on loading product for a stop together, by stop sequence. The
system sorts the orders by stop number and groups them together on the truck. The last
stop to be delivered will be loaded first. A high priority of this strategy is keeping stops
together on the truck; it will not split a stop unless the stop will not fit in one bay or pallet.
If the entire stop will not fit on the truck, the stop will not be loaded. This method ignores
the package type and SKU preferences specified in the Maintenance module.
Hybrid (Warehouse First)loads the truck by the Warehouse Friendly method first,
based on a user-defined quantity threshold. Click the [Options] button to open the Hybrid
Warehouse Options window and set the parameters for product that will be loaded
Warehouse Friendly. The options are explained below.
For Full Pallets of SKUany SKUs with sufficient quantity to fill a pallet will
be loaded Warehouse Friendly. The quantity needed to fill a pallet is based on the
package type and the pallet loading method. Any SKUs that do not fill a pallet will
be loaded Driver Friendly. This option allows you to compensate for the fact that
different quantities of the various package types are necessary to fill a pallet.
For Quantity of SKUany SKUs with a quantity greater than or equal to the
threshold entered below will be loaded Warehouse Friendly. The remaining SKUs
will be loaded Driver Friendly.
Hybrid (Driver First)loads the truck by the Driver Friendly method first, based on a
user-defined quantity threshold for a stop and/or the specified selector, or force bulk
service time. Stops not meeting this criteria will be loaded Warehouse Friendly. Click the
[Options] button to open the Hybrid Driver Options window and set the parameters. The
options are explained below.
For Quantity of SKUs for Stopany stops with a quantity greater than or equal
to the value specified below will be loaded Driver Friendly. The package types
that are excluded from driver friendly loading, as specified on the Driver Friendly
page, will not be included when calculating this quantity. You can choose to
710

combine this option with a selector, upload selector associated with an order, or
have force bulk service time checked in the Selectors area.
Upload Selector(s)any stops containing an order with one of the specified
selectors will be loaded driver friendly. Upload selectors are assigned to the orders
in Roadnet. If you are entering multiple selectors, do not place any spaces or
punctuation between them.
Force Bulk Service Timeloads orders marked Force Bulk Service Time driver
friendly.
And Selectorsan order must meet the quantity threshold and be assigned one of
the selectors, upload selectors, or have force bulk service time checked in the
Selectors area.
Or Selectorsan order must meet the quantity threshold, be assigned one of the
selectors, upload selectors listed in the Selectors area, or have force bulk service
time checked in the Selectors area.
Ignore Selectorsan order must meet the quantity threshold.
Notes: The selector is case sensitive, so make sure the case you enter matches the
download file. If using multiple selectors, type them without spaces or
punctuation separating them. For instance, to include all locations with selectors
A, B, or C, type ABC in the Selector(s) field.
If you specified a maximum number of SKUs in a bay in the Maintenance module,
any Warehouse Friendly or hybrid loading strategy will use that maximum
number of SKUs in loading. Max SKUs is ignored, however, in Driver Friendly
loading.
Or Prebuilt Stopsstops that were saved as prebuilt will also be loaded driver
friendly.
Prebuilt Stops Onlyonly loads stops that were saved as prebuilt driver
friendly; any other criteria established will be ignored.
Operations Guide
711
Global Page
The Global Options page lets you choose some options that are considered when loading
the trucks.
The Global options are used for both driver friendly and warehouse
friendly loading.
Load Front to Rearloads the truck starting from the cab and working toward the rear
of the truck. This option looks for the first available bay that meets all criteria for the
package type being loaded as specified in the Maintenance module.
Note: Load front to rear is the default setting. If it is not checked, the Loading Editor will
load the truck from rear to front.
Advanced Load Distribution
Nonedoes not use the Load Leveling or Minimize Bay Usage options when loading the
truck.
Load Levelingtries to load the truck evenly from side to side and front to back. If
loading Warehouse Friendly each SKU is loaded in the next emptiest bay that will balance
the truck; if loading Driver Friendly each stop is loaded in the next emptiest bay that will
balance the truck. If building pallets, Load Leveling will try to create even pallets for the
same stop, even if neither pallet is full. This prevents having one pallet that is 100% full
and one that is 10% full; instead both pallets will be approximately 55% full.
Minimize Bay Usagetries to load the truck bays using the least amount of bays without
violating the rules.
712

Warehouse Friendly Page
The Warehouse Friendly Options page lets you specify options that are used with the
Warehouse Friendly or hybrid load strategies. Many of these options deal with the order
product is loaded onto the trucks, or how to handle large or small quantities.
The warehouse options are available if you choose Warehouse Friendly or either
hybrid as your strategy.
Loading Options
Full Pallet Loading For Same SKUif the total amount of an SKU is greater than or
equal to a pallet, the Loading Editor will not split a pallet worth of the SKU between
bays when loading the truck. The quantity of an SKU that equals a pallet is defined by the
pallet loading method. If selected, pallets are loaded first within the Preference and
Optimization passes.
Load Full Pallets Onlykeeps any remaining SKUs from being loaded after Full
Pallet Loading is complete. This means that if the total of an SKU is greater than
a pallet, any remaining SKUs after the pallet is loaded will not be loaded
warehouse friendly and may be unassigned. This option is only available if Full
Pallet Loading is selected.
Operations Guide
713
Allow SKUs to Split Between Bays/Palletsif an SKU cannot fit in one bay/pallet,
allows it to be loaded in more than one bay/on more than one pallet. If this option is not
selected and an SKU will not fit in one bay/on one pallet, it will be unassigned. This
option only applies when FleetLoader is attempting to load the SKU into a bay/pallet that
already contains product; if the bay/pallet is empty FleetLoader will split the SKU if
necessary, even if this option is not selected.
Existing Package Preference Loadingtries to load SKUs in a bay/on a pallet that
already contains SKUs with the same package type.
Small SKU Pass for Quantity of SKUloads SKUs with user-defined small
quantities into pre-defined bays specified in the Maintenance module. Any SKU with a
quantity less than or equal to the specified number will be loaded in this manner. If you
want stack rules to be considered when loading product in the small SKU bays, you must
check Consider Stack Rules, even if Obey Stack Rules is checked. The Small SKU Pass
is the first option considered when the Warehouse Friendly strategy is used.
SKU Preference Passloads SKUs in bays with preferences first. If Preference/
Capacity is selected, all SKUs with a preference level 1 will be loaded first, then those
with a level of 2, and so on. If Capacity/Preference is selected, the SKU with the largest
volume will be loaded in the bay with the most available space with a preference for that
SKU, then the next SKU in the established loading order will be loaded in the bay with
the most space that has a preference for that SKU, and so on.
Package Type Preference Passloads package types in bays with preferences first. If
Preference/Capacity is selected, all package types with a preference level 1 will be loaded
first, then those with a level of 2, and so on. If Capacity/Preference is selected, the
package type with the largest volume will be loaded in the bay with the most available
space with a preference for that package type, then the next package type in the
established loading order will be loaded in the bay with the most space that has a
preference for that package type, and so on.
Notes: If Small SKU Pass is selected, those SKUs will be loaded before the SKU and/or
package type preferences.
If both SKU preferences and package type preferences are selected, all SKU
preferences will be considered before any package type preferences are
considered.
Optimization Passloads any product not already loaded into the first available bay. A
bay is considered available if loading product into it does not violate any established rules.
Loading Order
First Priority To Load By/Next Priority To Load Byclick the arrow and choose the
first loading priority criteria to sort the Warehouse Zone Pick Orders, Package Type
Quantities, or SKU Quantities before they are loaded; you can choose up to three levels
of sorting.
Warehouse Zone Pick Order Methodclick the arrow and select the method that
defines the warehouse zone pick order you want to use.
714

Loading Rules
Stack Rules Methodsclick the arrow and choose the method that defines the stack
rules you want to use.
Bay/Pallet Mix Rules Methodsclick the arrow and choose the method that defines the
bay or pallet mix rules you want to use.
Layer Mix Rules Methodclick the arrow and choose the method that defines the layer
mix rules you want to use.
Pallet Loading
Enable Pallet LoadingCheck this box if you are loading pallets, then click the [Pallet
Loading Options] button. The Pallet Loading Options window opens, where you define
how you want your pallets loaded onto the trucks. The options are explained below.
Default Pallet Typeclick the arrow to select the default pallet type. This is the
pallet type that will be used if the manufacturers pallet type is not used for a SKU.
Allow Manufacturers Pallet Typescheck this box if you are using
manufacturers pallet types.
Note: The manufacturers pallet type will only be used if there are enough of that SKU
to fill the required amount.
Obey Bay Capacitiescheck this box if you are loading a pallet onto a bay truck
and want to make sure the pallet will fit in a bay.
Pallet Layering Options
Load Pallets with Layersif you choose to use layers to load your pallets, check
this box and select your pallet layering options below. If you choose to load your
pallets by pallet capacity only, not taking layers into consideration, make sure this
box is not checked.
Partial Layers at Top of Pallet (Maximum)enter the maximum number of
partial layers that can be left at the top of each pallet.
Obey Partial Layer Stack Rulescheck to have stack rules apply to layers that
are partially full.
Obey Partial Layer Mix Rulescheck to have mix rules apply to layers that are
partially full.
Apply Loading Order to Partial Layerscheck to have partial layers use the
same loading order that is used for full layers. The loading order will be used
within each layer, as well as to determine the order the partial layers are loaded on
the pallet.
Keep SKUs on Adjacent Layerscheck to keep SKUs on neighboring layers on
the pallet, instead of allowing partial layers of the SKU to move higher on the
pallet. If this option is selected, all layers containing the SKU will be kept
consecutive, even if this means having a partial layer in the middle of the pallet
Operations Guide
715
instead of at the top, possibly resulting in a less stable pallet. This option is only
available if Load Pallets with Layers is selected.
Load Full Layers of the Same SKUcheck to have quantities of SKUs that can
be selected to create full layers and leave partial layers of SKUs to be loaded at
the top of the pallet. This option is only available if Load Pallets with Layers is
selected.
Note: If both the Keep SKUs on Adjacent Layers and Load Full Layers of the Same SKU
options are checked, both full and partial layers of a SKU will be loaded together,
instead of the partial layers moving to the top of the pallet.
Driver Friendly Page
The Driver Options page displays options that are used if Driver Friendly or one of the
hybrids is chosen as the loading strategy. These options deal with where the product is
loaded on the truck.
The Driver Friendly options focus on loading SKUs for the same stop together.
716

Loading Options
Stop Quantity Loadingloads the stop with the largest quantity first, working down to
the stop with the smallest quantity, instead of loading the last stop first.
Limit To One Stop Per Palletlimits the contents of a pallet to one stop; SKUs from
other stops will not be loaded on the pallet. Any of the stops SKUs that are not loaded on
this pallet because of a mix or stack rule may be loaded on another pallet. If this option is
not selected, multiple stops will be placed on the same pallet only if two conditions are
met: 1. the entire stop must fit on the pallet and 2. the pallets top layer must be full. This
option is only available if Enable Pallet Loading is selected.
Bay Trucks
Location Preference Loadingloads the product for particular user-defined
locations into predetermined areas on the truck (Passenger-Side Front, DriverSide Front, etc.), as specified in the Maintenance module. If the specified area is
already full, this option will keep the product on the same side of the truck. If
selected, locations with preferences will be loaded first.
Alternate Sides of Vehicle (for Same Stop)when loading a stop that requires
more than a single bay, loads the stop by moving from one side of the truck to the
other after filling each bay. If this option is not selected the Loading Editor will
load bays on the same side of the truck. If you are loading a bulk truck this option
should be selected.
Load bays according to capacityload bays according to available capacity,
rather than by position on the truck. If this option is selected, FleetLoader will
consider the size of the stops when loading the bays and assign each one to the
bay with the best available capacity.
Note: If you are loading with pallets and loading bays according to capacity, Obey Bay
Capacities is automatically selected.
Loading Order
Re-order Remaining SKUs for Each Bay/Palletcheck to ensure that each bay/pallet
is loaded using the largest quantity first. If this option is selected, FleetLoader will reorder the product when starting each new bay/pallet, so that the product with the largest
quantity is loaded before smaller quantity product. This will prevent product with a
smaller quantity that spilled over from a previous bay/pallet from being loaded before
product with a higher quantity.
Base Loadingcheck Enable Base Loading to potentially build a more sturdy
base by selecting a different loading priority for the base. Then click the Load
Base By arrow and choose the criteria to use to load the base. Once the base is
loaded using this criteria, the normal loading priorities are used for the rest of the
pallet.
First Priority To Load By/Next Priority to Load Byclick the arrow and
choose the first loading priority criteria to sort the Warehouse Zone Pick Orders,
Operations Guide
717
Package Type Quantities, or SKU Quantities before they are loaded; you can
choose up to three levels of sorting.
Warehouse Zone Pick Order Methodclick the arrow and select the method
that defines the warehouse zone pick order you want to use.
Loading Rules
Stack Rules Methodsclick the arrow and choose the method that defines the stack
rules you want to use.
Bay/Pallet Mix Rules Methodsclick the arrow and choose the method that defines the
bay/pallet mix rules you want to use.
Layer Mix Rules Methodclick the arrow and choose the method that defines the layer
mix rules you want to use.
Exclude Package Typesopens the Exclude Package Types from Driver window,
where you can specify package types that you do not want loaded driver friendly. In the
Exclude Package Types from Driver window, drag the package types you do not want
loaded driver friendly from the Available Package Types list to the Excluded Package
Types list. These excluded package types will be loaded warehouse friendly if a hybrid
strategy is selected; if Driver Friendly was selected as the loading strategy, these package
types will be unassigned. This option is handy if there are specific package types, such as
kegs, that you want to load manually.
Prebuilt Pallets
Apply Prebuilt Solutionload orders saved as prebuilt. If possible, orders previously
loaded and saved as prebuilt are loaded in the same bay type as they were loaded in the
prebuilt solution. If the prebuilt was saved with a bay type and is now being loaded onto
a bulk truck, the passs default pallet type will be used to load the prebuilt.
Load Prebuilts Firstif you are applying a prebuilt solution, this option loads the
prebuilt orders first, assuring there will room for them on the truck. If this option is not
selected, the prebuilt orders are loaded where they fall in the normal loading sequence.
When the truck is loaded in the normal sequence, the potential exists that no bay of the
type specified in the pre-built solution will be available when the pre-built order is loaded;
if this happens the order will not be loaded.
Pallet Loading Options
Enable Pallet Loadingcheck if you are loading pallets, then click the [Pallet Loading
Options] button. The Pallet Loading Options window opens, where you define how you
want your pallets loaded onto the trucks. The options are explained below.
Default Pallet Typeclick the arrow to select the default pallet type. This is the
pallet type that will be used if the manufacturers pallet type or locations preferred
pallet type is not used for a SKU.
Allow Manufacturers Pallet Typescheck this box if you are using
manufacturers pallet types.
718

Note: The manufacturers pallet type will only be used if there are enough of that SKU
to fill the required amount and if the location will accept it.
Obey Bay Capacitiescheck this box if you are loading a pallet onto a bay truck
and want to make sure the pallet will fit in a bay.
Note: Obey Bay Capacities is automatically selected if you are loading the bays according
to capacity.
Pallet Layering Options
Load Pallets with Layersif you choose to use layers to load your pallets, check
this box and select your pallet layering options below. If you choose to load your
pallets by pallet capacity only, not taking layers into consideration, make sure this
box is not checked. Choose the layering options below.
Partial Layers at Top of Pallet (Maximum)enter the maximum number of
partial layers that can be left at the top of each pallet.
Obey Partial Layer Stack Rulescheck to have stack rules apply to layers that
are partially full.
Obey Partial Layer Mix Rulescheck to have mix rules apply to layers that are
partially full.
Apply Loading Order to Partial Layerscheck to have partial layers use the
same loading order that is used for full layers. The loading order will be used
within each layer, as well as to determine the order the partial layers are loaded on
the pallet.
Keep SKUs on Adjacent Layerscheck to keep SKUs on neighboring layers on
the pallet, instead of allowing partial layers of the SKU to move higher on the
pallet. If this option is selected, all layers containing the SKU will be kept
consecutive, even if this means having a partial layer in the middle of the pallet
instead of at the top, possibly resulting in a less stable pallet.
Bulk Trucksenter the number of rows that a stop may be buried. For instance, if this
number is set to 2, the driver may have to remove pallets from up to two rows in order to
access the remaining pallets for this stop.
Operations Guide
719
Preparing to Edit Trucks in the Loading Editor
Preparing to Edit Trucks in the Loading Editor

The Loading Editor provides several tools that make it easy to edit your loaded trucks.
You can view the product in each bay, on each layer of a pallet, as well as by SKU and
by stop. There is also a dynamic truck profile that shows you the available space in each
bay.
Entering Truck Editing Mode
Once the trucks have been loaded in the Loading Editor, you can move product between
bays, between layers on a pallet, load product that was not loaded, and otherwise change
how the truck is loaded. To edit your trucks, you must be in edit mode. When you enter
Edit mode, any windows you saved as favorites open showing the loaded product. The
title bar of the main window displays the ID and name of the route you are editing. It also
displays the equipment assigned to the route, as well as the total quantity, weight (not
including truck weight), and number of potential pallets.
opens.
with.
Step 3: In the Routes window, double-click on the route you want to work with.
OR
In the Routes window, right-click on the route you want to work with and choose
Edit from the menu that pops up.
Hint: To help you determine which routes have unassigned product, the number of
unassigned units for each route is indicated in the Unassigned Quantity column
in the Routes window. Double-click this number to open the Unassigned SKU
window.
720

Setting the Loading Editor Options

The Loading Editor Options notebook allows you customize your colors associated with
Bay Coloring, pick your display options for the Truck Profile, determine your stack order
and default view for Bay Contents View, and select the warning options you want to use
in the Loading Editor.
opens.
Step 2: In the routing Sessions window, double-click on the route you want to work
with.
Step 3: Click File and select Options. The Options notebook opens.
Step 4: Click the Truck Profile, Bay Contents View, and Warnings tabs to move to the
other pages and select the other options you want. A selection is chosen when a
check appears in the box.
Step 5: Save your settings.
To use your setting while in this session of FleetLoader, click the [Apply]
button.
To save your setting for future sessions, click the [Save] button.
To restore the default settings, click the [Defaults] button.
To exit without saving, click the [Cancel] button.
General Options
The General Options tab lets you choose some generic display options, such as colors to
indicate how the bay was loaded, which types of routes are shown, and how the bays
percentage full is calculated.
To open the General page of the Options notebook, click the General tab.
Choose the options you want to use; a check indicates an option is selected.
By Loading Methodcheck if you want to use colors to identify the loading method
used for the bays on your truck. Click on the arrow in each field to select the color you
want associated with each loading method. You can change the colors that identify how
each bay of your truck was loaded using the Driver Friendly, Warehouse Friendly, and
Manual methods.
When Overfilledcheck if you want to use colors to identify when a bay is filled over
its capacity. Click on the arrow to select the color you want associated with an overfilled
bay.
Note: The following settings affect only how the information is displayed. They do not
affect how capacities are calculated when the trucks are loaded
Sideloader Percent-Full Calculationselect how you want the product loaded in your
sideloader trucks to be displayed.
Operations Guide
721
Use Bay Capacityif you want to use the capacity of the bays to determine how
much product is loaded.
Use Pallet Capacityif you want to use the capacity of the pallets inside the bays
to determine how much product is loaded.
Use Layer Limitsif you want to use pallet layers to determine how much
product is loaded.
Note: If you choose Use Pallet Capacity or Use Layer Limits for your Sideloader
Percent-Full Calculation and there is no pallet in that bay, you will see Bay
Capacity information displayed.
Bulk Truck Percent Full Calculationselect how you want the product loaded in your
bulk trucks to be displayed.
Use Pallet Capacityif you want to use the capacity of the pallets inside the bays
to determine how much product is loaded.
Use Layer Limitsif you want to use pallet layers to determine how much
product is loaded.
Show Active Routescheck Show Active Routes, if you want both active and built
routes to show in FleetLoader. If this option is not selected, only built routes will be
displayed.
Save As Prebuilt Solutioncheck to save the orders that are loaded a pre-built solution.
The solutions will be loaded as planned in the same type of bay when the pre-built
solution is applied during the final loading.
You can choose the colors that identify how each bay was loaded.
722

Truck Profile Options
The Truck Profile page of the FleetLoader Options notebook lets you choose how what
will be displayed on the Truck Profile. For instance, you can choose whether or not stop
numbers and bay numbers will be visible.
To access the Truck Profile page of the Options notebook, click the Truck Profile tab.
Stop Numberscheck if you want to display the stop numbers loaded in each bay.
Note: If this is a bulk truck and you are displaying the truck profile in the top-down view,
the stop numbers will replace the pallet position.
Bay Numberscheck if you want to display the bay numbers for each bay at the top of
the bay in the Truck Profile. If selected, the Define Bays - Equipment Type and Define
Bay Preferences - Equipment windows in the Maintenance module will display the bay
numbers as well.
Note: If you are displaying a bulk truck, the bay number setting is ignored.
Top-Down View for Sideloaderscheck if you want to display the bays as an aerialview, instead of as a side view. If selected, or you are viewing a bulk truck, the numbers
may not appear if the Truck Profile is not sized accordingly.
Cabcheck if you want the Truck Profile to display the cab and wheels. Displaying the
truck without the cab and wheels may be helpful if you are loading pre-built solutions and
want to differentiate the phantom truck from your regular trucks.
Check the appropriate Truck Profile display options here.
Overloaded Colorclick on the arrow to open a color palette, then click on a color to
select the one you want to represent the overloaded area around a truck when you have
exceeded its capacity.
Operations Guide
723
Bay Contents View
The Bay Contents View page is where you choose how the SKUs will be displayed in the
Bay Contents View. Make the appropriate selections from the Bay Contents View tab in
the Options notebook. Click on the Bay Contents View tab in the Options notebook to
open the Bay Contents View page.
Note: You can also set up your bay colors which will be reflected in the Bay Contents
View Window on the General page of the Options notebook.
Click next to the Stack Order you want to used in the Loading Editor. This option
determines how SKUs appear in the bay.
Manualshows SKUs as they are actually stacked in the bay. After running Load Trucks
the SKUs should be stacked according to the Stack Rules set up in the Maintenance
module.
SKUshows SKUs sorted numerically by SKU number. You can also choose
either ascending or descending order by clicking the box next to Ascending.
Quantityshows SKUs sorted by the largest quantity per SKU (not order size).
You can also choose ascending or descending order by clicking the box next to
Ascending.
Package Typeshows SKUs sorted by their package type. You can also choose
either ascending or descending order by clicking the box next to Ascending.
In the Default View area, select either Detailed or Condensed to choose your default view
in the editor.
Detailedshows a product image, SKU, quantity, order number, and site ID. Use
this view if you decide to load your trucks using a Driver-Friendly approach. You
can only use the Layer View if Detailed is selected.
Condensedshows a product image, SKU, and quantity only. Use this view if
you decide to load your trucks using a Warehouse-Friendly approach.
724

Note: You can also toggle between Detailed and Condensed views from the View menu.
See Using Loading Editor Windows for more information.
You can decide how to display the skus in the Bay

Contents View window.
Warnings
The Warnings page is where you can determine which warnings you want to have appear
when you move product or save the truck.
Click on the Warnings tab located in the Loading Editor Options notebook to access the
Warnings page.
Operations Guide
725
In the Warnings area, check the boxes next to the warning options you want to use. If
When moving is selected, a warning will appear if a move violates one of the specified
rules. If When saving is selected, the warning appears when you save your changes.
You can choose to have

warnings about broken
rules appear when you
move product, when you
save the truck, or not at
all.
No capacity definedwarns you if you have not specified a capacity for the
package type you are moving into the target bay. These package types will not be
considered when the percent of the bays capacity filled is calculated, and
therefore will not be shown on the Truck Profile.
Capacity violationswarns you if the move violates either the capacity or the
max SKUs for the target bay. The warning will indicate whether capacity or max
SKUs has been violated.
Disabled Bay usedwarns you if the bay receiving the product has been
designated as disabled.
Bay/Layer No-Mix violationswarns you if the move violates a Mix Rule
established for the SKU brand, warehouse zone, or package type with any other
SKU brand, warehouse zone, or package type currently in the target bay/layer.
Stack Rule violationswarns you if the move violates a Stack Rule for the
package type with a package type already in the target bay.
Note: The Stack Rule violations setting looks at where you place the moved product in
the bay. If Manual stack order is selected, all bays/pallets are displayed as if you
were looking at them on the truck, so SKUs at the bottom of the list are loaded at
the bottom of the bay/pallet. If you drop the product at the top of the bay, this
setting will determine whether any product below it violates the Stack Rule
settings as specified in the Maintenance module.
726

Using Loading Editor Windows

The Loading Editor has several windows that allow you to view the loaded truck in many
ways, assuring at least one window easily provides the information you need. All the
windows discussed in this section can be opened by selecting it from the View menu. A
brief summary of the information contained in each window, and how it can be used, is
included.
Bay/Pallet Contents View Window
Note: The colors you see in the Bay/Pallet Contents View Window were chosen on the
General page of the Options notebook.
The main editing tool in the Loading Editor is the Bay/Pallet Contents View window.
Within the Bay/Pallet Contents View window, each bay/pallet and its contents are
displayed in list window format, meaning you can size and move each column in the
window as you can in any list window; any change you make will affect all the windows
in the Bay/Pallet Contents view. In addition, you can choose to view the images or not by
selecting the Show Images/Do Not Show Images icon.
To display the Bay/Pallet Contents View for a truck, follow the steps listed in Entering
Edit Mode or select Bay/Pallet Contents from the View menu.
Note: The available Contents View window depends upon your equipment type. If you
are working with bay trucks, Bay Contents will appear in the View menu; if you
are working with bulk trucks, Pallet Contents will appear in the View menu. The
presentation and format of this window is the same, whether you are working with
bay trucks or bulk trucks.
The bays/pallets are designed to appear in the window in a top-down view of your truck;
they are listed with the passenger side bays/pallets on top and the driver side bays/pallets
on the bottom.
In the Loading Editor, you can move all or some of the product in a window at one time.
You can split an order and move only a portion of the product to another bay/pallet, or
you can swap the contents of two selected bays/pallets. You can also reload an individual
bay/pallet. If you have chosen manual stack order in the Loading Editor Options
notebook, you can also move product from one position to another (lower or higher) in
the same bay/pallet, changing the stack order. For more information on moving product
see Editing Trucks.
Note: When you move product in the Bay/Pallet Content View windows, all items will
be placed on the first layer of the bay/pallet they are moved to. Also, all product
moved into an empty bay/pallet in the Bay/Pallet Content View windows will be
placed on the same layer of the new bay/pallet, even if the product is moved from
Operations Guide
727
multiple layers. If you need to maintain layer order, you should move product in
the Layer View.
When moving SKUs in the Bay/Pallet Contents View window, all selected SKUs
will be moved, so make sure you only have selected the SKUs you want to move.
Unassigned SKUs Window
The Unassigned SKUs window is essential in the editing process. This window lists all
SKUs not loaded on the truck. If Detailed view was chosen in the Options, it also lists the
stop number and location ID for the unassigned SKUs, as well as other useful information.
By default the window is sorted the same as the Bay Contents View window, but it can
be sorted like any other list window. You can drag and drop SKUs from the Unassigned
SKUs window to load them in any available bay (see Editing Trucks).
The Unassigned SKU window lists all product that is not loaded on the truck.
Split SKU Window
The Split SKUs window allows you to see at a glance how many of the SKUs on the truck
were split into different pallets and bays during the loading process. If you are loading
your trucks Warehouse Friendly, this window can help you to pinpoint problems with the
728

loading strategy or preferences you may have specified. You can also drag and drop SKUs
or pallets from the Split SKUs window into any available bay(s).
The Split SKU Tree View window lets you

easily determine which SKUs are loaded
into different bays. From this window you
can move SKUs to different bays to put
them together.
To open an SKU and see where it is loaded on the truck, click the plus (+) sign next to
the SKU.
To open all SKUs simultaneously, click on the Expand All icon.
To close an SKU, click on the minus (-) sign.
To close all SKUs simultaneously, click on the Collapse All icon.
Note: To hide the images and view the window with just text, click on the Do Not Show
Images icon; to view the images again, click on the Show Images icon.
SKU Window
The SKU window lists the quantity of each SKU for each order on the route. All SKUs
that exist on the routes orders will be listed in this window regardless of whether they
have been loaded on a truck or are unassigned. You can check the Bay column to
determine whether SKUs have been loaded or are unassigned.
You can unassign product from the SKU window by dragging and dropping SKUs into
the Unassigned SKUs window. You cannot move SKUs into the SKU window to load
them; to load unassigned SKUs, see Editing Trucks.
Operations Guide
729
The SKU window lists the order number, location ID, and warehouse zone for the SKUs,
as well as other useful information. By default, the window is sorted by SKU number, but
it can be sorted like any other list window.
You can use the SKU window to easily determine which bays the SKUs are loaded
into.
Bay/Pallet Contents Tree View Window
The Bay/Pallet Contents Tree View window contains the same information as the Bay/
Pallet Contents View window, but uses less space. You may want to use this tool if you
cant see enough information at one time with the Bay/Pallet Contents View window.
Note: The available Contents Tree View window depends upon your equipment type. If
you are working with bay trucks, Bay Tree View will appear in the View menu; if
you are working with bulk trucks, Pallet Tree View will appear in the View menu.
The presentation and format of this window is essentially the same, whether you
are working with bay trucks of bulk trucks.
In the Bay Contents Tree View the bays are presented with driver side bays listed first (1,
3, 5, etc.), followed by the passenger side bays (2, 4, 6, etc.)
730

In the Pallet Contents Tree View, the pallets are alternated by rows, working from the
front of the truck to the back, starting with the drivers side pallet in each row (01-01, 0102, 02-01, etc.
The Bay/Pallet Contents Tree Views use less space than the Bay/Pallet Contents View
windows, but have the same basic functionality.
To open a bay/pallet and see what is loaded in it, click the plus (+) sign next to the SKU.
To open all bays/pallets simultaneously, click on the Expand All icon.
To close a bay/pallet, click on the minus (-) sign.
To close all bays/pallets simultaneously, click on the Collapse All icon.
Images icon; to view the images again, click on the Show Images icon.
SKU and Stops Tree Views
The remaining tree views available in the Loading Editor, the SKU and Stops Tree Views,
function somewhat differently than the other windows. You can click and drag items from
these windows to other windows, but you cannot move items into or within these
windows. However, these view windows are perfect for seeing at a glance where items
Operations Guide
731
are loaded on the truck. The options function just as they do in the Bay Contents Tree
View window.
The SKU and Stops tree views

are very similar, but one may
be more helpful to you than
the other, depending on your
operation.
If you use the Warehouse Friendly strategy for loading, the SKU view may be more
beneficial to you; likewise, the Stops view may be helpful if you are using the Driver
Friendly approach. You are not limited to using one or the other, though; both views are
available as soon as you enter Edit Mode.
To open an SKU or stop and see where it is loaded on the truck, click the plus (+) sign
next to the SKU.
To open all SKUs/stops simultaneously, click on the Expand All icon.
To close an SKU/stop, click on the minus (-) sign.
To close all SKUs/stops simultaneously, click on the Collapse All icon.
Images icon; to view the images again click on the Show Images icon.
Truck Profile Window
The Truck Profile lets you see at a glance how much space is available in each bay/pallet.
You can choose to view the bay Truck Profile from the side (as shown below), or looking
down from the top. Whichever view you choose, the bay Truck Profile behaves the same
way. If you are viewing a bulk Truck Profile, only the top-down view is available.
732

To help you maintain a balanced load, the Truck Profile displays the calculated total
weight of the load, as well as the driver side weight and the passenger side weight. This
information is displayed at the bottom of the Truck Profile window when the cursor is not
hovering directly over a bay/pallet.
Note: If you are working with a bulk truck that contains middle pallets, the weights of the
driver side and the passenger side will be estimated based on the positions of the
pallets.
You can also drag and drop items from the Bay/Pallet Contents View or any of the tree
view windows into any bay or pallet on the truck. If you choose manual stack order in the
editor options and you drop product into the Truck Profile, it is loaded automatically at
the top of the bay/pallet.
The Truck Profile window is handy if you want to quickly see how
full each bay/pallet on the truck is.
You can move the entire contents of a bay/pallet from the Truck Profile. Simply click on
the bay/pallet and drag the contents to another bay/pallet in the Truck Profile, or Bay/
Pallet Contents View window.
You can reload a bay/pallet from the Truck Profile. Right-click on a bay/pallet and select
Reload Bay/Pallet Contents from the menu that pops up.
Operations Guide
733
You can also open windows that will show the properties, preferences, or capacity for the
bay/pallet the mouse is currently over. Simply right-click on a bay, truck bed, or pallet
and choose the desired window from the menu that opens.
Side Loader Truck Options
Insert Shelf/Remove Shelfallows you to insert or remove a shelf from a bay.
If you insert a shelf, a dashed line appears separating the bay into an upper bay and
lower bay. If you remove a shelf, the dashed line appears and the bay now
becomes a full-size bay.
Reload Bay Contentsselect the loading pass to use to reload an individual bay.
Preferencesdisplays what types of SKUs or packages you would prefer to load
in this bay. These preferences are defined in Equipment Preferences and
Fleetloader.
Capacities provides a handy reference showing each package type, description,
and how many units of this package type can fit in the bay. The information in this
window will change depending on which bay your mouse hovers over.
Important: If a product with no defined capacity for a bay /pallet is loaded manually into
the bay/pallet, it will not be reflected as part of the percentage shown in the Truck
Profile.
Propertiesdisplays the bays description and position, loading strategy, and
percent full, as well as any violations that may have prevented product from being
loaded. You can also use this window to change rules methods, or to change, add,
or remove pallet types.
Bulk Truck Options
New Palletplaces a new pallet on the truck. As you hover the cursor over the
empty truck bed, a red line indicates where the pallet will be placed. Right-click
on the red line and select New Pallet to open the Select new Pallet Type window,
then click the pallet type arrow and select a pallet type from the list. When you
have finished, click [OK] to close the Select new Pallet Type window.
Remove Palletdeletes the pallet from the truck bed.
Unassign Contentsremoves all product from the pallet and returns it to the
Unassigned SKUs window.
Change Pallet Typeallows you to select a different pallet type. Click the pallet
type arrow and select a pallet type from the list. When you have finished, click
[OK] to close the Select new Pallet Type window.
Reload Pallet Typeselect the loading pass to use to reload an individual pallet.
Capacities provides a handy reference showing each pallet loading method,
each package type, and how much of a package type can be loaded onto the pallet
using a loading method. The information in this window remains the same
regardless of which pallet your mouse hovers over.
734

Important: If a product with no defined capacity for a pallet is loaded manually into the
pallet, it will not be reflected as part of the percentage shown in the Truck Profile.
Propertiesdisplays the pallets description and position, loading strategy, and
percent full, as well as any violations that may have prevented product from being
loaded. You can also use this window to change rules methods, or to change pallet
types.
Layer View
The Layer View provides an easy way to see the contents of pallets loaded on a truck.
Because of the information displayed, the Layer View is only available if you have
selected Detailed in the Editor Options. The Layer View displays information about the
SKU and quantity for each layer, as well as the pallet type and all the stops on the pallet.
You can move SKUs from layer to layer within a pallet, or from pallet to pallet. When
moving a blue outline or frame helps identify where you are dropping the SKUs/layer.
When you move product in the Layer

View, a blue outline shows where the
product is being moved to.
The Layer View has several display features that make it easy to determine the state of a
layer or pallet.
Across the top of the pallet is a bar indicating how full the pallet is. If the bar is
green, there is room on the pallet; if it is yellow the pallet is overloaded. The pallet
layering method is used to determine how much product can be placed on the pallet.
The colors you see in the Layer View Window are chosen on the General page of the
Options notebook.
All the contents for a stop are listed under the stop; the stop information includes the
stop number and location name and ID.
The quantity and name and description for each SKU on a layer is shown.
On the left side of each pallet is a column displaying the layer number; this is called
the layer selector. The color of the layer selector indicates how full the layer is; blue
Operations Guide
735
means no more product can be put on the layer, green means there is room on the
layer for more product, and yellow means there is too much product on the layer.
A red line across a pallet indicates the maximum number of layers as defined in the
pallet layering method has been reached.
The weight for each pallet is displayed under the pallet, and the total product weight
for the truck is displayed at the bottom of the Layer View.
The calculated total weight of the load of the truck is displayed at the bottom of the
window, as well as the driver side weight and the passenger side weight. Seeing the
calculated weight distribution of each side of the truck can help you maintain a
balanced load.
You can resize the Layer View, making the individual pallets as large or small as desired.
To size the window, simply click on the corner and drag to the desired size. To resize all
the pallets so that they all fit in the current Layer View size, click the Anchor icon.
To select all the pallets, click the Select All Bays/Pallets icon.
To deselect all the pallets, click the Deselect All Bays/Pallets icon.
To unassign all SKUs in the window, click the Move All Selected Items to Unassigned
Skus List icon.
To move an SKU from one layer to an existing layer, click on the SKU, then drag it
and drop it on the existing layer. The layer you are adding the SKU to will be outlined in
blue.
To move an SKU to a new layer, click on the SKU and drag it on top of the layer you
want it to be on top of. For instance, if you want the new layer to be between an existing
layers 2 and 3, drop it on top of layer 2. A blue line appears when you are between layers.
To move a layer to another place, click on the layer number and drag it to the new
location. If adding to an existing layer, drop it on the layer; if adding on top of an existing
layer, drop it on top of the layer.
To move part of an SKU, right-click on the SKU and drag it to the new position. When
you release the mouse button, the Quantity to Move window opens. Enter the number of
the SKU you want to move and click the [OK] button. This option is only available if only
one SKU is selected.
To swap the contents of two pallets, select the bays/pallets and click the Swap Contents
of Two Selected Bays/Pallets icon.
To reload a bay/pallet, select the bay/pallet you wish to reload and click the Reload Just
This Bay/Pallet icon. The Select Reloading Pass window opens. Click the arrow and
select the loading pass to use to reload.
736

Editing Trucks
Editing Trucks
Once your trucks have been loaded, you can move contents from bay/pallet to bay or
pallet, or within a bay or pallet, as needed. SKUs can be moved freely in the Bay/Pallet
Contents View and Bay/Pallet Contents Tree View windows. In addition SKUs can be
moved from the Unassigned, Split SKU, and Stop and SKU Tree View windows into the
Bay/Pallet Contents View and Bay/Pallet Contents Tree View windows; however, SKUs
cannot be moved within the Unassigned, SKUs, Split SKU, or Stop and SKU Tree View
windows, or into these windows. Any moves you make will be reflected in all the
windows. The editor also provides tools you can use to analyze why product was loaded
in specific bays/pallets.
Important: When moving product from bay to bay, pallet to pallet, or within a bay or
pallet, you may receive a message warning you that the move violates an existing
rule. If so, you can choose between four options:
[Yes] moves the SKU and goes to the next violation.
[Yes to All] moves all selected SKUs and ignores other error messages that may
occur from the move.
[Skip] will not move that SKU but will continue with other selected SKUs.
[Cancel] cancels the entire move.
These warning messages will only occur if you have violated one of the choices selected
under Options. These warning messages may also occur when saving moves if you made
that choice in Options.
Operations Guide
737
Editing Trucks
Analyzing the Loaded Truck
The Loading Editor offers many features you can use to determine why specific SKUs or
package types were loaded in one bay or pallet and not another. You can also customize
your colors associated with Bay Coloring. You must be in editing mode to use any of these
options.
Checking the preferences for a bay
When reviewing the loaded truck, it may be necessary to review the preferences defined
for a particular bay to determine why a SKU or package type was not loaded in that bay.
To find this information, right-click on a bay in the Truck Profile and select Preferences
from the menu that pops up. A floating window opens indicating the preferences for
whatever bay the mouse is over. This information was established when the equipment
was added.
Checking the properties for a bay/pallet
When reviewing the loaded truck, it may be necessary to review the properties for a
particular bay/pallet to determine why a SKU or package type was not loaded in that bay/
pallet, such as whether it is full, disabled, or designated a Small SKU bay. You can also
view the loading method used for each bay/pallet and choose the appropriate method for
each bay/pallet based on whether it is being loaded driver friendly or warehouse friendly.
To find this information, right-click on a bay/pallet in the Truck Profile and select
Properties from the menu that pops up. A floating window opens indicating the properties
for whatever bay the mouse is over. Some of this information was established when the
equipment was added.
Notes: The Over Capacity icon will appear if the bay is over capacity, or if there are more
than the allowable max SKUs in the bay.
The convertible bay checkbox will be checked if the bay is convertible.
Hint: You can also add and change pallet types from the Bay Properties window. See
Placing Unassigned SKUs in a Bay/Pallet for more information.
Adding a pallet to a bay
You can add or remove a pallet to a bay from the Properties window. To add a pallet to a
bay, right-click on a bay in the Truck Profile and select Properties from the menu that pops
up. The Properties window opens. Click the Pallet Type arrow and select a pallet type
from the list. To remove a pallet from the bay, select None.
Checking the capacity for a bay/pallet
When reviewing the loaded truck, it may be necessary to review the capacities defined for
a particular bay to determine why a SKU or package type was not loaded in that bay. To
find this information, right-click on a bay in the Truck Profile and select Capacities from
the menu that pops up. A floating window opens, indicating the package type capacity for
738

Editing Trucks
whatever bay the mouse is over. This information was established in the Maintenance
module.
Note: When you are working with bay trucks, the information in this window will
change depending on which bay your mouse hovers over. However, when you are
working with bulk trucks, the information in this window remains the same
regardless of which pallet your mouse hovers over.
Editing the Status of a Convertible Bay
While analyzing the loaded truck, you may decide you want to manually insert or remove
a shelf in a convertible bay. The notches on both sides of a bay will indicate that this is a
convertible bay with the option to insert a shelf, and a dashed line will indicate that this
is a convertible bay with the option to remove a shelf.
To insert a shelf, right-click on the bay in the Truck Profile and choose Insert Shelf from
the menu that pops up. A dashed line appears separating the bay into upper bay and lower
bay.
To remove a shelf, right-click on the bay in the Truck Profile and choose Remove Shelf
from the menu that pops up. The dashed line disappears and the bay now becomes a fullsize bay.
As you are working with convertible bays, it is important to understand what will happen
when you perform certain actions, such as manually removing the shelf when the bay
contains products. The following describes what happens for each possible scenario:
Inserting a shelf in an empty convertible baythe full-size bay will be split and
you will have an empty upper and an empty lower bay.
Inserting a shelf in an occupied convertible baythe contents will be placed in
the lower bay.
Removing a shelf from a convertible bay in which the upper and the lower bays
are emptythe shelf from the convertible bay will be removed, and you will have a
full-size empty bay.
Removing a shelf from a convertible bay in which only the lower bay is
occupiedthe shelf from the convertible bay will be removed, and the contents will
be placed in the full-size bay.
Removing a shelf from a convertible bay in which only the upper bay is
occupiedthe shelf from the convertible bay will be removed, and the contents will
be placed in the full-size bay.
Removing a shelf from a convertible bay in which the upper and lower bays are
occupiedyou will receive a warning indicating that the contents in the upper bay
will be unassigned. If you proceed with the action, the shelf will be removed, and the
contents in the upper bay will be unassigned. The contents of the lower bay will be
placed in the full bay. If you cancel the action, no change will occur.
Operations Guide
739
Editing Trucks
Reloading an Individual Bay/Pallet
In the Loading Editor, you are able to reload an individual bay/pallet from several
windows. This feature allows you to reload a bay/pallet based on the guidelines defined
in the selected loading pass without reloading the rest of the truck.
Step 1: If you are on the Layer View or Bay/Pallet Contents View window, highlight
the entire contents of the bay/pallet you wish to reload. Click the Reload Just This
Bay/Pallet icon. The Select Reloading Pass window opens.
OR
If you are on the Truck Profile window, right-click on the bay/pallet you wish
to reload. Select Reload Bay/Pallet Contents from the menu that pops up. The
Select Reloading Pass window opens.
You can select the loading pass you
want to use to reload the individual
bay or pallet,
Step 2: Click the arrow and select the loading pass to use to reload the bay/pallet.
Step 3: Click the [OK] button. The bay or pallet is reloaded using the rules defined in
the selected loading pass.
740

Moving SKUs on the Loaded Truck

The purpose of FleetLoader is to let you analyze the loaded truck and move product
around as necessary to fine-tune the load. You can use the different windows to move
product between bays and pallets, or move it around within a bay or a pallet.
Placing Unassigned SKUs in a bay/pallet
As you analyze the truck, you may find that it is easier to move product between the
windows, instead of within a window. There are some restrictions about which windows
product can be moved into and out of. SKUs can be moved into or out of the Bay/Pallet
Contents View, Truck Profile, and Bay /Pallet Contents Tree Views; product can be
moved out of, but not into, the Split SKUs, and Stops and SKU Tree Views. You must be
in Truck Editing mode to perform this procedure.
Note: If you need to place a pallet on the bulk truck or in a bay to put the unassigned
SKUs on, follow the steps below.
From the Truck Profile for a bulk truck, right-click on the truck bed and choose New
Pallet from the menu that pops up. The Select New Pallet Type window opens. Click the
arrow and choose the proper pallet type, it will be placed on the truck.
From the Truck Profile for a side loader, right-click on the bay and choose Properties
from the menu that pops up. The Properties window opens. Click the arrow and select the
pallet type you want to place on the truck. A brown line in the bay indicates a pallet.
Hint: The Properties window updates every time the mouse cursor moves over a new
bay. To make sure you are adding the pallet to the proper bay, hold down the
[Shift] key as you move the mouse from the desired bay to the Properties window.
Step 1: Click on the unassigned SKU(s) you want to move. It will be highlighted. If
selecting more than one item, hold down the [Ctrl] key while clicking on the
SKUs. If you dont hold down the [Ctrl] key all selections other than the current
selection will be cleared.
Step 2: Drag the selected SKU(s) to the bay/pallet and place where you want to drop it;
release the mouse button.
If you chose manual stack order in the Options notebook, decide where in the bay/
pallet you want to drop the item. If you drop the item on another product, the item
will be loaded below that product. If you drop the item on the column header, that
item will be loaded at the top of the bay/pallet.
If you are using the Layer View, a blue line indicates where on the pallet the SKU
is being loaded.
Moving SKU(s) to another bay/pallet
You can move a single SKU to another bay or pallet position, or move a group of SKUs
simultaneously, as long as they all have the same destination.
You must be in Truck Editing mode to perform this procedure.
Operations Guide
741
Note: If you are using the Bay/Pallet Contents View or Layer View, all products that are
selected will be moved. To move only part of a SKU, see Moving part of an SKU
to another bay/pallet.
Step 1: Click on the item you want to move. It will be highlighted. If selecting more than
one item, hold down the [Ctrl] key while clicking on the SKUs. If you dont hold
down the [Ctrl] key all selections other than the current selection will be cleared.
Step 2: Drag the selected SKU(s) to the bay/pallet and place where you want to drop it;
release the mouse button.
If you chose manual stack order in the Options notebook, decide where in the bay/
pallet you want to drop the item. If you drop the item on another product, the item
will be loaded below that product. If you drop the item on the column header, that
item will be loaded at the top of the bay/pallet.
If you are using the Layer View, a blue line indicates where on the pallet the SKU
is being loaded.
Note: If you are starting the move from the Truck Profile for a bulk truck, hold down the
[Shift] key to move the SKUs to another pallet and remove the original pallet from
the truck. If you want the pallet to remain, right-click on the SKUs to move and
drag the SKUs to their new pallet.
If you are starting from the Truck Profile for a side loader using pallets, and you
want the pallet to remain in the original bay, right-click on the product and drag it
to the new bay.
Moving part of an SKU to another bay/pallet
You may find that you only want to move part of an SKU from one bay /pallet to another,
rather than moving the entire SKU.
Note: This option, which is only available if only one SKU is selected, is not available
from the Truck Profile.
Step 1: Right-click on the SKU and, holding down the right mouse button, drag the SKU
to the new location.
Step 2: When you drop the SKU in the new bay/pallet, a pop-up window appears to
allow you to specify the quantity of that SKU you wish to move to the new
location.
You can move all or only a portion
of an SKU to another bay.
Type the quantity you want to move and click the [OK] button.
OR
Click the up or down arrows to increase or decrease the quantity. Then click the
[OK] button.
The product moves to the new location.
742

Moving an SKU within a bay/pallet
In addition to moving product to another bay, you can reorganize product within the bay,
making it easier for the driver to reach items at a stop.
Notes: If you are using the Bay/Pallet Contents window, all product that is selected will
be moved.
You should be using the Layer View when making these moves. You cannot move
selected SKUs from the Truck Profile.
down the [Ctrl] key all selections other than the current selection will be cleared.
Step 2: Drag the SKU to the new position in the bay/pallet and release the mouse
button. The SKU moves to that location.
If you drop the SKU on another product, it will fall below that product in the bay/
pallet.
If you drop the SKU on the column header, it will be dropped at the top of the bay/
pallet.
If you are adding the SKU to another layer, a blue rectangle surrounds the layer
you are adding to in the Layer View.
If you are creating a new layer, a blue line indicates where the new layer will be
added on the pallet in the Layer View.
Changing the Pallet Type
moved out of, but not into, the Split SKUs, and Stops and SKU Tree Views.
Note: You can only change the pallet type from the Truck Profile.
To change the pallet type that is loaded onto a bulk truck, follow these steps.
Step 1: Right-click on the pallet in the truck bed and select Change Pallet Type. The
Select new Pallet Type window opens.
Step 2: Click on the arrow and choose the desired pallet type. When you have finished,
click [OK].
To change the pallet type that is loaded onto a bay in a side loader truck, follow these
steps.
Operations Guide
743
Step 1: Right-click on the bay/pallet and select Properties from the menu that pops up.
The Properties window opens.
Step 2: Click on the Pallet Type arrow and choose the desired pallet type.
Hint: The Properties window updates every time the mouse cursor moves over a new
bay. To make sure you are adding the pallet to the proper bay, hold down the
[Shift] key as you move the mouse from the desired bay to the Properties window.
Moving an SKU to another window
moved out of, but not into, the Split SKUs, and Stops and SKU Tree Views. You must be
in Truck Editing mode to perform this procedure.
If you have several windows open, such as the tree views or the Truck Profile, you can
move items from one window to another. SKUs can be moved into or out of the Bay/Pallet
Contents View, Truck Profile, and Bay/Pallet Contents Tree Views; product can be
moved out of, but not into, the Split SKUs, and Stops and SKU Tree Views.
Note: If you are using the Bay /Pallet Contents view window, all product that is selected
will be moved. If you are using the Truck Profile, the entire contents of the bay
will be moved.
down the Ctrl key all selections other than the current selection will be cleared.
Step 2: Drag the SKU(s) to the new position in another window and release the mouse
button. The SKU moves to the new location.
Note: If you have chosen manual stack order in the editor options and you drop the item
on another product in the new window, the item will be loaded below that product.
If you drop the item on the bay/pallet symbol in the Bay/Pallet Contents Tree
View, that item will be loaded at the top of the bay/pallet. If you drop the item on
a bay/pallet in the Truck Profile, that item will be loaded at the top of the bay/
pallet.
Unassigning SKUs
If a bay/pallet is overloaded or you simply need to take some product off the truck, you
can move product to the Unassigned window. You must be in Truck Editing mode to
perform this procedure.
You can also move product off the truck, or unassign product, by moving it to the
Unassigned window.
If you are unassigning SKUs from a side loader, follow the steps below.
744

Step 1: Click on the SKU(s) you want to unassign. That item will be highlighted.
Step 2: Drag the SKU(s) to the Unassigned window and release the mouse button.
Step 3: To remove the pallet, right click on the bay and choose Properties from the
menu that pops up. Click on the Pallet Type arrow and choose None.
Notes: If you are using the Bay Contents window to move the product, you can select the
items you want to unassign and click the Move All Selected Items to Unassigned
Skus List icon. All selected products will be moved to the Unassigned window.
You cannot unassign SKUs from bay trucks by changing the pallet type to None
If you are unassigning SKUs from a bulk truck, simply right-click on the pallet in the
Truck Profile and select Remove Pallet from the menu that pops up. The SKUS are
unassigned and the pallet is removed from the truck.
Note: If you want to unassign the SKUs on a bulk truck but leave the pallet behind, rightclick on the pallet and select Unassign Contents from the menu that pops up. The
SKUs are unassigned and the pallet remains on the truck.
Swapping Bay/Pallet Contents
If the weight distribution on your truck is unequal, you can swap the contents of two bays/
pallets. You must be in Truck Editing mode to perform this procedure.
You can swap bay/pallet contents in either the Layer View or the Bay/Pallet Contents
View windows.
Step 1: Select the first bay/pallet by clicking on the bar above the list of SKUs The
contents of the bay/pallet will be highlighted.
Step 2: [Ctrl]-click the second bay/pallet. The contents of the second/bay pallet will be
highlighted, and the Swap Bay/Pallet icon will be activated.
Step 3: Click the Swap Bay/Pallet icon. The contents of the two bays/pallets will be
swapped.
Note: When you swap bay/pallet contents in the Bay /Pallet Content View windows, all
items will be placed on the first layer of the bay/pallet they are moved to. If you
need to maintain layer order, you should swap contents in the Layer View.
Operations Guide
745
Saving Your Work in the Loading Editor
Saving Your Work in the Loading Editor

You should save your work periodically in the Loading Editor. If you have edited your
routes and must leave the Loading Editor, or you want to work on another route, you can
save the work you have done. If you have to import more routes, you can save your work
and lock certain routes to prevent any changes to those routes. As with any computer
program, you should save your work frequently.
You can either save or save and lock a route. If you save a route you simply save the work
you have already done on that route. You can then leave the editor or work on another
route. However, if you reload your trucks, the loading algorithm will return the truck to
its original configuration (before editing).
If you save and lock a route, you prevent the loading algorithm from reloading that locked
truck. You can still edit that truck and make additional changes manually, but the loading
algorithm will not touch that truck.
Step 1: To save your work on a route(s), select the route(s) in the Routes window. The
route(s) is then highlighted.
Step 2: Click the File menu and select Save, or Save and Lock.
Step 3: The route will be saved, and the Status field in the Route window will change to
EDITED if the route was saved, or LOCKED if you chose Save & Lock.
Changing the Route Status
Once the routes have been saved or locked, you may need to change its status. You can
lock, unlock, or clear the status of a route easily from within the Routes window.
Step 1: Right-click on a route. A pop-up menu appears.
Step 2: Click on either Lock or Unlocked. The Load Status field in the Route window
will change to reflect the new status.
Note: If you unlock a locked route, its load status will be edited.
746

Deleting Pre-Built Loading Solutions
Deleting Pre-Built Loading Solutions

If you are importing stops or orders to be pre-built by the warehouse personnel, you want
to make sure that the orders you are working with are for the correct day. If you have a
pre-built solution that was imported and saved in the wrong routing session, you can
delete the pre-built solution for that session and then import the correct orders.
Notes: All pre-built solutions for the specified session will be deleted, so make sure you
delete before importing the orders you want to use.
Only solutions that were saved as pre-built solutions (Save as Pre-built was
checked in the Options notebook) will be deleted.
The pre-built solution for a session will also be deleted if the routing session is
deleted using Database Maintenance.
Step 1: If necessary, click on the Loading icon to open the FleetLoader module. The
Editor window opens.
Step 2: In the Routing Session window, double-click on a session you want to work
with.
Step 3: Click on the Tools menu and select Delete Prebuilt Solution. Click [Yes] to
confirm you want to delete the prebuilt solution for the selected routing session.
Operations Guide
747
Exporting the Loaded Routes

When you are finished loading, you are ready to export loading information for others to
use. Once the export is complete, you can view a report listing any problems that occurred
during the export process.
with.
Step 3: To export all loaded routes, click on the Tools menu and select Export All
Routes. The Export Loaded Routes window opens.
OR
To export a selected route or routes, right-click on a route(s) in the Route(s)
window and select Export Selected Route(s) from the menu that pops up. The
Export Loaded Routes window opens.
You can choose your Layout Set, change

the Output File Name, and select to
output times in either your Time Zone,
or by Drivers time in the Export Loaded
Routes window.
position and length of fields in the destination file, click the [File Layout] arrow
and select Edit. See Setting the Import File Layouts or Export Loaded Routes
Available Fields in the Roadnet Transportation Suite Operations Guide for more
information.
748

the [File Layout] arrow and choose Preview Report from the menu that pops up.
Administration module, you will not be able to change any of the options selected
when exporting loaded routes.
Step 6: To convert all times in the export file to a specific time zone, select Time Zone,
then click the arrow and select the appropriate time zone to be used when
exporting all loaded routes. If you want to use the times displayed in FleetLoader,
click Driver's Time.
Step 7: Click the [Export Routes] button.
Step 8: To see any errors that occurred during the export, click the [View Errors]
button. If no errors occurred, the button will not be available.
Loading Editor Tools Export ALL Routes [Export Routes]
OR
Loading Editor Routes window Export Selected Route(s) [Export Routes]
Operations Guide
749
Printing Reports in the Loading Editor
Printing Reports in the Loading Editor

Once the trucks are loaded, and all necessary changes to the loads have been made and
saved, you can print reports to help the driver and loader from within the Loading Editor.
The same reports that are available in the Reports module, and the same options for
printing the reports, are available in the Loading Editor.
Reports Groups Group [OK]

the reports.
the [OK] button.
Reports List Preview/Print [OK]
750

Exiting the Loading Editor

Once you have finished loading and editing your trucks, you can leave the Loading Editor.
If your routes have not been saved, you will be prompted to save them before exiting the
editor.
Click the close box (the X) in the upper-right corner of the Loading Editor window.
OR
Click on the File menu, then click on Exit.
When you exit the Loading Editor, you will be prompted to save your work. You can
either Save, Save and Lock, Discard, or Cancel.
If you save a route, you simply save the work you have already done on that route.
If you save and lock, you prevent the loading algorithm from reloading the route(s).
If you discard, you abandon any changes you have made to the route(s).
If you cancel, you return to the Loading Editor.
Operations Guide
751
752

MobileCast - Dispatcher
Dispatching in MobileCast
Dispatching in MobileCast
Note: If you were not granted access to the Dispatcher in the Administration module,
The MobileCast Dispatcher module is where you can track your drivers throughout the
day, and make on the fly changes to the routes as needed and communicate them to the
drivers. In the Dispatcher, you can:
Start, complete, and delete routes
Add, edit, delete, and unassign stops from routes
Add breaks, waits, and layovers, or insert mid-route depots to your routes
Track stops being completed throughout the day
Add and delete orders
Create new routes
Create and add unassigned stops to a route
Communicate with the drivers, if your operation uses wireless devices
Find where a route is during the day
Track the position history for a route or piece of equipment
View exceptions for a specific route
Determine if there is enough space on a truck to add a load to the route
View the routes that are only assigned to you
The Dispatcher provides several ways for you to look at the routes. The Overview
window provides a list of the routes, and allows you to view the stops for each route, the
orders for each stop, and the line items for each order. To see more detailed information
on the routes, stops, or orders, use a list window. The list window provides more detailed
information about the route, stop, or order, including planned, projected, and actual times,
and delay information.
In addition to the Overview and list windows, routes can be viewed on a map, which
makes it easy to visually track the route throughout the day. See Using the Map for more
information on maps. The Route Summary window also provides an easy way to track
routes, using icons to indicate the status of route elements.
Note: In order to view all dispatchers routes within your region, you must have the
permission set to view other dispatcher routes within the Administrative module.
See Working with Privileges for more information on setting this permission.
Operations Guide
753
Using Windows in the Dispatcher Module

MobileCast lets you work with your routes from several different types of windows:
The Overview window provides the least information, but also takes the least amount
of space on the screen.
A list window provides more information, but it is more likely you will have to scroll
to see the desired route.
The summary window provides a quick way to check the route assignments and
status.
The map window allows you to visually follow the route throughout the day, but can
use a lot of space.
Hint: Whichever type of window you use, right-click on the route to open a menu with
all the necessary options to run it from beginning to end.
Using the Overview Window
There are several types of windows in the Dispatcher that you can use to work with your
routes. One of these is the Overview window. The Overview window lets you create and
organize your routes into specific lists, giving you the chance to see many routes at once.
The default list is the Not Completed Routes list, which shows both routes that have not
started and routes that have left the origin but have not reached their final destination.
To view a list, click its title bar in the Overview window.
To add a list, use the Route Query to find the routes you want to create a list for; then,
once the results are listed in the Route Query window, click the Add Query to Route
Overview icon. Enter the name of the list and click [OK]. The list now appears in the
Overview window.
To delete a list, right-click on its title bar in the Overview window, and then select Delete
from the pop-up menu.
To view the stops for a route, click the plus sign next to the route. The stops for the route
appear beneath the route. Similarly, to view a stops orders, click the stops plus sign, and
to view an orders line items, click its plus sign. If an element does not have a plus sign,
it means there are no lower levels of detail for it.
To work with a particular route, right-click on it and select the desired option from the
menu that pops up.
To work with a stop, right-click on it and select the desired option from the menu that
pops up.
You can see the stops, orders, and line items for routes from the Overview window, but
you cannot see any details about the route, such as quantities delivered. To see that kind
754

of detail, right-click on the route and select either Show Details or Properties from the
menu that pops up.
Right-clicking on a route and selecting Show Details opens the Route Query Results
window. You can use the horizontal scroll bar to see extensive information for this route,
such as its planned and actual start times, how many stops have been delivered, and when
the information for the route was last updated.
The Properties
window is best for
making changes to
the route, such as
changing its
destination.
Operations Guide
755
Using the Route Window
To display the most detailed information about several routes, use a Route window. There
are separate Route windows for the two different types of routes: Not Assigned Routes
and Not Completed Routes. In addition to viewing and managing route information from
a Route window, you can also open the map directly from it.
The Not Completed Routes list window provides detailed information

on all of the routes that are running or will be run.
To see the stops for a route, double-click the route. The Stops window for the route
opens.
Note: The stop list may or may not display the routes origin and destination, as well as
any pre- and post-route time associated with the route. To add rows showing the
origin, destination, and pre- and post-route time, click on the Options icon on the
stop list. In the Stop Display Options window check Enable Advanced View and
choose the colors for each row. Click the [Save] button to save the options.
Important: The stop list window does not give actual distance information for the origin
or the destination. The total shown at the bottom of the Actual Distance column
does not include the distance from the origin to the first stop or the distance from
the last stop to the destination.
To see the order activities for a stop, right-click on the stop and select Order Activities from the menu that pops up. The Order Activities window opens, displaying all
order activities for the stop.
To see one or more routes displayed on a map, select the route(s) and then click
the Plot icon or right-click on the route and select Map from the menu that pops up.
The map opens, displaying the selected route(s).
To work with a route or stop, right-click on the route/stop and select the desired
item from the menu that pops up.
Reading the Data Quality
When you are looking at Routes and Stops windows in MobileCast, you will see Data
Quality columns presented along with the planned, projected, and actual data. These
columns tell you by what means this information is gathered. This information may be
assumed from projection, manually entered by the driver or the dispatcher, or computed
756

automatically based on driver entry or incoming GPS transmission. The data quality
columns include:
Start Time Qualityregards how the route was started.
Departure Time Qualityregards how the driver departed the depot to begin the
route, or how the driver departed each stop.
Arrival Time Qualityregards how the driver arrived at each of the stops, or
how the driver arrived at the end of the route.
Complete Time Qualityregards how the route was completed.
Distance Data Qualityregards the distance traveled on the stop or route.
All five of these columns are included in the Routes window; the Arrival Time Quality,
Departure Time Quality, and Distance Data Quality columns also appear in the Stops
window.
Note: For more information about the information in the MobileCast list windows, turn
to Window Columns in the Dispatcher.
Depending on how this information was entered into MobileCast, one of the following
descriptors will appear in each column:
Assumed from Projectionindicated as such when stops on the route were
manually completed as projected.
Driver Enteredodometer reading was manually entered into the handheld
device by the driver (applies only to Distance Data Quality).
Dispatcher Enteredinformation manually entered by the dispatcher.
Auto Capturedinformation captured when driver enters arrivals and
departures on the wireless device.
GPS Computedinformation automatically computed based on GPS (applies
only when Auto Arrive/Depart Mode is being used).
Geo Computed Clusterinformation automatically computed based on GPS
and service time average in a cluster of close locations when the driver arrived at
a group of stops (applies only when Auto Arrive/Depart Mode is being used).
Geo Computed Sparseinformation is computed based on the GPS data
received (applies only to Actual Distance).
Mixedinformation gathered is from more than one distance data quality.
Using the Route Summary Window
The Route Summary window lets you quickly check the status of all routes within a
selected range of departure dates. You can both view and update items from the Route
Summary window. To update an item, just double-click on it. For instance, suppose you
want to assign a driver from the Route Summary window. Double-click on the Driver icon
for the route, and the Assignments for Route notebook opens to the Drivers page.
Operations Guide
757
Step 1: Click the Routes menu and select Summary. The Route Summary window
opens.
Step 2: Select the range of dates to view. You can enter the dates manually, or click on
the arrow to open a calendar. If entering the dates manually, use the arrow keys to
move from the month to day to year field. If you are using the calendar to change
the month, either use the arrows on the top of the calendar to scroll to the month,
or click on the month and select it from the menu that pops up. To change the
year, click on the year and use the arrows to scroll to the correct year. Click on a
date to select it. If searching for a date range, check the box before entering the
final date.
Step 3: Click the Execute Query Using Criteria icon. The list of routes appears above
the search area. For each route, the departure date and ID is listed. The row of
icons provides information about the routes status. If an icon is colored, that
aspect of the route is true; if the icon is gray the route has not achieved that status.
The Route Summary window is an easy way to manage many routes that
are running or will run soon, especially in a wireless environment.
See the table below for a description of the icons in the Route Summary window.
Icon
Indicates
Indicates the overall status of the route. A red light means the
route is complete. A yellow light means the route has
exceptions that have not been acknowledged. A green light
means the route is running on time.
Indicates where the route is based on the latest information
from the wireless device. If there is no information, this field
will be blank.
Indicates a driver has been assigned to the route.
Indicates a power unit has been assigned to the route.
Indicates there are notes about the route that have not been
acknowledged.
Indicates there are wireless events for the route that have not
been processed.
758

Indicates the route is part of a load.
Indicates at least one stop on the route has a proof of delivery

signature or signature code.
Displays the number of time windows missed, or projected
to be missed, on the route.
Indicates accounting has been done for the route.
Indicates how many stops have been completed on the route.
Dispatcher Routes Summary

Using the Map
The maps in the Dispatcher module have three main elements:

The icon bar at the top of the map window, with buttons for using and moving
around the map.
The map area, with all stops for the selected route(s) visible, numbered and colorcoded by route.
The status bar at the bottom of the map window, which gives the address or stop
information (if any) of the current mouse position on the left, and the corresponding
latitude and longitude on the right.
In the map area, you will see several different symbols:

Red building icons indicate depots.
Red rectangles with the letter T and the route identifier indicate the estimated
locations of drivers on routes. So, if a red rectangle with the letter T is sitting on a
red building icon (at the depot), the route either hasnt started or has ended.
A circle or square with the letter U identifies Unassigneds stops. Refer to User
settings for more information.
Numbered squares indicate stops that havent been completed.
Numbered circles indicate stops that have been completed.
Small pushpins, bulls-eyes, and similar graphics indicate landmarks that have been
added by a user to your particular version of the map.
Yellow diamonds represent route exceptions, and white diamonds are acknowledged
route exceptions. Exceptions will appear on all maps displaying routes in the
Dispatcher module. Refer to Working with Route Exceptions for more information.
An X in a box the same color as the route indicates a cancelled stop. Refer to
Cancelling a Stop for more information.
Operations Guide
759
To identify any point on a map, roll the mouse onto it. If it is a stop on a route, its name
and stop number appear in the status bar at the bottom of the map. If it is an address on a
road, its address appears in the status bar.
To work with a route, right-click on its rectangle. A menu pops up offering all of the
choices you need for starting and managing the route, such as assigning drivers and
reordering stops. For details on working with these menu items, see the individual tasks,
such as Starting a route.
To work with a stop, right-click on its symbol on the map. A small menu pops up, offering
the following choices:
CompleteIf the route has been started, clicking Complete opens a window from
which you can complete the stop.
CancelCancels the stop. A cancelled stop is not included in the actual
information for the route, but remains in the plan for the route. The segment of the
route containing the cancelled stop is removed from the map, and the cancelled
stop is indicated by an X in a box the same color as the route.
Calculate % EmptyThe Calculate Percent Empty window appears, showing
the unused capacity of the truck at that stop.
Load Stop DetailsIf the stop is part of a load, the Load Stop window opens,
from which you can edit load information for the stop.
ProcessA window opens to let you record delivery information about the stop,
if any.
NotesThe Notes window opens, where you can type any short note (less than
500 characters). The note is stored with the stop when you click the [Update]
button.
PropertiesThe Properties window opens, where you can see information on the
stop, order, or line item, depending on the level of detail you specified in the
Options notebook in the Maintenance module. You can edit the stop, order, or line
item data from this window, and you can add or delete stops, orders, or line items.
Show path to next stopIf your map options are set so that the actual path does
not show for the route, clicking Show path to next stop shows the actual roads that
the driver will travel between the current stop and the next stop. If the actual path
is already showing for the whole route, this item is grayed out.
User Settings
You can customize the maps used in MobileCast to look the way you want. For instance,
you can change the background color, the color of the roads, specify whether or not zip
codes and city names are displayed, and specify whether or not Unassigneds are displayed
on the map. Many of these options can be found in the Map Properties notebook, opened
by clicking on the Map Options icon and selecting Properties from the menu that opens.
To set specific user-defined setting, click on the User tab.
To have the map redraw to show all routes when information is refreshed from the
database, check Make all routes visible after reading.
760

To show the routes actual path, following the roads instead of using straight lines,
check Show routes using actual paths.
To show a stops delivery area, check Show Delivery Radius.
To show unassigned stops on the map, check Show Unassigneds.
To see route exceptions on the maps, check Show Exceptions. Then, in the list, check
the Show box for all the exceptions you want to see displayed on the maps.
Note: The Route Watch Map and the Plot map opened from the Show Me menu for an
exception will always show the route exceptions.
To view exceptions after they have been acknowledged, check Show Acknowledged
Exceptions.
Note: Only acknowledged exceptions which have been selected on the User page of the
Map Options notebook will be shown.
The Route Watch Map will not show acknowledged exceptions.
Note: When you open the Plot map from the exceptions list, the exceptions selected on
the Users page will be displayed on the map, as well as the exception selected from
the exceptions list. For instance, if you selected the GPS Gap, Late GPS, and No
GPS exceptions on the User page, but then clicked on a Out of Sequence exception,
the Plot will open showing the three GPS exceptions, plus any Out of Sequence
exceptions.
Use the User page of the Map

Properties notebook to specify
your preferences when viewing
items on the map.
Operations Guide
761
Starting a Route
Starting a Route
Before you can do anything to a route in the Dispatcher, such as completing its stops or
processing orders, you must start it. Starting a route involves the following steps:
Step 1: Display the route you want to start. If necessary, use the Route Query to find the
route.
Step 2: Assign resources to the route. Typically, a depot and at least one driver and
piece of equipment are assigned before you can start the route. All the other
resources (additional drivers and equipment, dispatcher, route type, and wireless
device) are optional.
Step 3: Tell MobileCast to start the route, which locks the resources you have selected.
Locked resources can be assigned to other routes that arent running yet (for
planning purposes), but they cannot be used on another running route. If you are
using wireless communications, the driver will start the route.
Routes that havent had Step 3 completed appear in the Not Assigned Routes list. All
routes that are not completed, whether or not they have been started, appear in the Not
Completed Routes list. If the route is early, then the actual and projected times appear in
green.
Note: You can open the Not Assigned Routes list and the Not Completed Routes list
from the Dispatchers Routes menu, or by selecting route Overview from the
View menu and clicking on the route list. If no routes appear in any of the
windows, you probably need to import route data or push them from the Routing
editor. See Importing Daily Routes into MobileCast or Sending the Routes to
MobileCast for more information.
Hint: You can start routes from the map window in Dispatcher as well as from the
Dispatchers list and Overview windows. Right-click on the routes rectangle to
get a pop-up menu with all of the options necessary to start and run the route.
Starting Routes, Step 1: Display the Route
You can display a route in any of several different windows to start it: a map window, the
Overview window, a Route window, or the Route Summary window. Which one you
choose depends on personal preference and how much detail you want to seethe
Overview window provides the least detail, while a Route window provides the most.
Whichever window you choose, the procedure for working with the route is the same. For
more information on starting a route, see Starting Routes, Step 2: Assigning Resources.
Step 1: If necessary, click the Dispatching icon to open the Dispatcher module. The
Dispatcher window opens. If necessary, use the Route Query to find the route.
Step 2: To open the routes list, click Routes and select the desired type of route. The
appropriate list window opens.
To open the Overview window, if not already open, click View in the menu bar
and click Route Overview. The Overview window opens, with the Not Completed
762

Starting a Route
Routes list visible. To see just routes that have not assigned drivers and/or
equipment, click the Not Assigned bar at the bottom of the Overview window.
To open the Route Summary window, click Summary from the Routes menu,
then select the range of dates to view and click the Execute Query Using Criteria
icon.
Dispatcher Routes Desired Route
OR
Dispatcher View Route Overview
OR
Dispatcher Routes Summary Execute Query Using Criteria icon
Starting Routes, Step 2: Assign Resources
Before you can start a route, you must make the necessary assignments. Typically, at least
one driver and one piece of equipment must be assigned to the route. The default for these
required assignments is in the Maintenance Options notebook but can be changed for an
individual route in the Assignments for Route notebook by adding or removing the check
on the appropriate page. If these assignments were not made when the route was first
created, you must make them in the Dispatcher module. If the driver is not downloading
the route to the wireless device, you can assign a wireless device to the route either
directly or through the driver or equipment. All assignments are made from the
Assignments for Route notebook.
Step 2: From an Overview or Route window, right-click on a route you want to
assign resources to, then click Assignments from the menu that pops up. The
Assignments for Route notebook opens.
To work on multiple routes from an Overview or Route window, hold down
the [Ctrl] key and click on each route, or, if the routes are listed together, click the
first route, hold down the [Shift] key, and click the last route. Then, right-click on
the first route you want to work on and click Assignments. The Assignments for
Route notebook opens.
From the Route Summary window, double-click either the Driver1, Driver2, or
Tractor icon for the route. The Assignments for Route notebook opens.
Step 3: The Assignments for Route notebook contains three pages:
GeneralAssign drivers, a dispatcher, a color to identify the route, a reference
number, a route type, and a seal number and mark if a driver assignment is
required or a helper is assigned to the route.
EquipmentSelect the tractors, trailers, and other equipment to be used on the
route, and the locations where each piece of equipment is picked up and dropped
off.
Operations Guide
763
Starting a Route
WirelessThis tab is only used if the driver is not downloading the route to the
device, or a device is not already assigned to a driver or equipment on the route.
The Assignments for Route notebook is used to assign

equipment, drivers, and other resources to routes.
Click a tab to assign a resource from it. See Assigning Drivers, Assigning
Equipment, or Assigning Wireless Devices for more information.
Step 4: When all the assignments are complete for a route, click the Save icon or press
[Ctrl]+[S] to save the assignments for that route. If multiple routes were selected,
the next route is automatically displayed in the notebook, ready to be assigned. If
you are working on the last or only route when you click the Save icon, the
notebook closes.
When all the resources have been assigned, you can start the route.
Hint: If you are assigning multiple routes, you can use the arrows at the top of the
notebook to move through the routes.
Dispatcher Not Assigned Routes window Assignments Save icon ([Ctrl]+[S])
Assigning Drivers
Use the General page of the Assignments for Route notebook to assign drivers, a
dispatcher, and other resources to a route. To change the requirement for assigning a
driver for this route, click to add or remove the check from the Assignment Required box.
In addition to the General page of the Assignments for Route notebook, you can use the
Wireless page to assign wireless devices and the Equipment page to assign equipment.
764

Starting a Route
Step 2: Right-click on the route and select Assignments from the menu that pops up.
The Assignments for Route notebook opens; click the General tab, if necessary.
Step 3: Click the Driver #1 arrow; the Lookup - Driver 1 window opens. Double-click
on the driver, or click on a driver and then on the Process icon, to select it.
The Lookup - Driver 1 window, like other Lookup windows in MobileCast, can be
sorted on any field by clicking on the field name at the top of the column. In this
example, the list of drivers is sorted by last name and first name.
Hint: If you prefer to make selections using the keyboard, check to see how the driver
list is being sorted, then type the first few characters in that field for the driver you
want. Press the [Spacebar] to select the driver, then press the [Enter] key to save
the information. This process works for any list in MobileCast.
Step 4: The remaining fields on the General page can be used as follows:
Ref. Numbera number used to track the route, which appears on the Route
windows. This field may have another label, such as DTR. The label is set in the
Maintenance modules Options notebook.
Colorthe color used to help distinguish a route on a map or in a list window. To
change the route color, click the color and select a new one from the palette that
opens.
Dispatcherthe dispatcher/user associated with the route. To select a dispatcher,
click Dispatcher arrow; the Lookup - Dispatcher window opens. Double-click on
the dispatcher, or click on a dispatcher then on the Process icon, to select one.
Route Typethe type of route, such as long-haul or short-haul. To select a
dispatcher, click Route Type arrow; the Lookup - Route Type window opens.
Double-click on the type, or click on a type then on the Process icon, to select one.
Driver #2the second driver assigned to the route.
Sealused if the truck is going through customs. Enter the seal information as
necessary.
Operations Guide
765
Starting a Route
Step 5: If you need to assign equipment or wireless devices, follow the instructions in
Assigning Equipment or Assigning Wireless Devices. When you are finished all
assignments for this route, click the Save icon or press [Ctrl]+[S].
Dispatcher Routes window Assignments General Driver #1 Process Save icon
([Ctrl]+[S])
Assigning Equipment
Use the Equipment page of the Assignments for Route notebook to assign the tractor,
trailers, and other necessary equipment to the route. To change the requirement for
equipment assignment for this route only, click to add or remove the check from the
Assignment Required box. In addition to the Equipment page of the Assignments for
Route notebook, you can use the General page to assign drivers and other resources, and
the Wireless page to assign wireless devices. For more information, see Starting Routes,
Step 1: Display the Route, Starting Routes, Step 2; Assign Resources, Assigning Drivers
in MobileCast, Assigning Wireless Devices in MobileCast, or Starting Routes, Step 3:
Tell MobileCast to Start the Route.
The Assignments for Route notebook opens; click the Equipment tab, if
necessary. Make sure the Insert radio button is selected in the Mode area.
Step 3: In the Equipment area, search for the equipment you are interested in using.
To get a list of all equipment, click the Execute Query Using Criteria icon.
To search for specific equipment, click in the check boxes for the items to search
for, then enter the search criteria. For example, to search for all equipment that is
available, click in the Status check box, enter RDY (short for ready) in the Status
766

Starting a Route
field, then click the Execute Query Using Criteria icon. The ready equipment
appears in the Equipment list.
In this example, a
search has been
done in the
Equipment area
for all tractors
that are ready to
use.
Warning: Fields that can have uppercase and lowercase text, such as Description, are
case-sensitive, so Volvo is not the same as volvo or VOLVO.
Step 4: You can assign more than one piece of equipment at once. All the pieces of
equipment you assign at once will have the same starting and ending locations.
To select a single piece of equipment, click the piece of equipment you want to
assign.
To select more than one piece of equipment, click the first piece, then hold
down the [Ctrl] key and click each additional piece, or, if the pieces are listed
together, click the first one, hold down the [Shift] key, and click the last one.
Step 5: Enter the starting and ending points for the equipment.
If you want to start and end the equipment at the routes starting and ending
points, click the [Insert] button or press [Alt]+[N] and MobileCast will add the
information to the Equipment Assigned to Route list.
If the equipment starts at a location other than the routes starting point,
click Start Location arrow. The Lookup Start Location window appears.
Double-click the location you want, or select the location and then click on the
Process icon, to select it.
If the equipment ends at a location other than the routes ending point, click
the End Location arrow. The Lookup End Location window appears. Doubleclick the location you want, or select the location and then click on the Process
icon, to select it.
Operations Guide
767
Starting a Route
Step 6: When you have the correct starting and ending locations entered, click the
[Insert] button or press [Alt]+[N] to add the equipment to the Assigned
Equipment list.
Note: If you assign a piece of equipment by mistake, click it in the Equipment Assigned
to Route list and click the [Delete] button. If you need to change the route
information about a piece of equipment that youve assigned, click the piece of
equipment in the Assigned Equipment list and make the changes. Click [Update]
or press [Alt]+[P] and then the Save icon when you are finished making changes.
Step 7: If you need to assign drivers, wireless devices, or other resources, follow the
instructions in the Assigning Drivers and Assigning Wireless Devices sections.
When you are finished all assignments for this route, click the Save icon or press
[Ctrl]+[S].
If you are assigning equipment for more than one route, use the arrows at the top of the
notebook (to the right of the Save icon) to move among routes. Once you save a route,
you will automatically be moved to the next route.
Dispatcher Routes window Assignments Equipment Search Insert Save icon
([Ctrl]+[S])
Assigning Wireless Devices in MobileCast
Wireless devices can be assigned to routes in two ways. If a wireless device is associated
with a driver or piece of equipment that is assigned to a route, the device is automatically
assigned to the route. Otherwise, you can assign the wireless device to the route directly.
If your drivers are downloading the route directly into the wireless device, you will not
need to assign wireless devices to the routes. In addition to the Wireless page of the
Assignments for Route notebook, you can use the General page to assign drivers and other
resources, and the Equipment page to assign equipment. For more information, see
Starting Routes, Step 1: Display the Route, Starting Routes, Step 2; Assign Resources,
Assigning Drivers in MobileCast, or Starting Routes, Step 3: Tell MobileCast to Start the
Route.
The Assignments for Route notebook opens; click the Wireless tab, if necessary.
768

Starting a Route
Step 3: Click the Assigned Wireless Device arrow; the Lookup - Wireless window
opens. The Lookup Wireless Device window appears. Double-click the device
you want, or select the device and then click on the Process icon, to select it.
The Wireless tab is

needed only if wireless
devices are not
assigned to drivers or
equipment.
Step 4: If you need to assign drivers, equipment, or other resources, follow the
instructions in the Assigning Resources section. When you are finished all
assignments for this route, click the Save icon or press [Ctrl]+[S].
If you are assigning devices for more than one route, use the arrows at the top of the
notebook (to the right of the Save icon) to move among routes.
Hint: To determine the wireless device assigned to a route, right-click on the route.
Select Lookup, then Wireless Device. A window opens, identifying the routes
wireless device.
Note: To remove a wireless device from a route, click the None box in the LookupWireless Device window.
Starting Routes, Step 3: Tell MobileCast to Start the Route
After drivers, equipment, and any other resources are assigned, you can start the route. If
you are using wireless communication, the route will be started by the driver. For more
information, see Starting Routes, Step 1: Display the Route, Starting Routes, Step 2;
Assign Resources, Assigning Drivers in MobileCast, or Assigning Wireless Devices in
MobileCast.
Step 2: From an Overview or list window, right-click on the route you want to start,
then click Start from the menu that pops up. The Start Route window opens.
From the Route Summary window, double-click the routes gray stoplight. The
Start Route window opens.
Operations Guide
769
Starting a Route
Note: If you double-click a stoplight icon that is not gray, MobileCast knows the route
has already started, so it displays the Stop Complete or Route Complete window.
The Start Route box records the
status of the route when the driver
left the depot (or other start point).
Step 3: If necessary, change the start and departure date and/or time. The Start time is
the time the driver starts the route, while the departure time is when the driver
leaves the origin.
To change the date, click on the arrow next to the date and time field. To change
the month, either use the arrows on top of the calendar to scroll to the month, or
click the month from the menu that pops up. To change the year, click on the year
and use the arrows to scroll to the correct year. Click on a date to select it.
To change the time, type it in the field, using the arrow keys to move from the
hour to minute field.
To set to the current date and time, click the [Now] button.
Step 4: If necessary, change the time zone for the start of the route to the zone you want
from the drop-down list. All of the stop times on the route will be updated to
reflect the change, giving the equivalent time in the default time zone set up in
the Users module.
Step 5: If necessary, enter delay information for the route. Click the Delay arrow to
display the Lookup Delay Type window. Double-click the delay type, or click
on the type and then on the Process icon, to select it. In the number field, enter
the minutes delay by typing or using the small arrows. This delay information is
used for accounting purposes when you want to bill or pay for time other than
what was recorded in the Departure field. For example, a customer delay of 10
minutes might be recorded here as 15, because times for the region are always
rounded to the nearest quarter-hour.
Hint: If there is a delay starting the route, the status of the route can be changed by rightclicking on the route and selecting Properties, then Status. Double-click the
desired status from the window that appears, then click the Save icon.
Step 6: If the route origin is part of a load, click the [Load Info] button to enter
information about the load.
Step 7: Click the Save icon or press [Ctrl]+[S] to save the information. MobileCast
attempts to lock the resources you have selected so they cant be used to run
another route until this one is completed.
770

Starting a Route
If there are conflicts (for example, you assigned a driver who is still on another
route), an error message appears explaining the problem, and the route wont be
started. In that case, click the [OK] button to remove the error message from the
screen, then repeat the process of assigning drivers and equipment until no
conflicts occur.
If there are no conflicts, MobileCast starts the route. If multiple routes were
selected, the next route is automatically displayed in the notebook, ready to be
started. If no other selected routes remain to be started when you click the Save
icon, the notebook closes.
Step 8: If necessary, click the Close box to close the Start Route window.
Dispatcher Overview/List/Route Summary window Start Save icon ([Ctrl]+[S])
Operations Guide
771
Completing Stops on a Route

If a route has wireless communications available, its stops will be completed by the driver
using the wireless device. If a route does not use wireless communication, you will need
to complete the stops.
As you complete each stop you can record any changes from the planned and projected
arrival and departure times, and include a reason for the change. If a stop is early, the
actual and projected times are displayed green in the Route window. If a stop is late, the
actual and projected times are displayed red in the Route window. You can also record
exactly what was delivered, picked up, etc. at the stop, in whatever level of detail your
system requires.
Completing an Individual Stop
Unless a driver is completing stops on a wireless device, you will need to complete each
stop in the Dispatcher module. As you complete a stop, you can verify and edit date, time,
delivery, and mileage information, among other things. For more information, see
Completing Stops on a Route or Completing All Stops at Once.
Dispatcher window opens.
Step 2: From an Overview or list window, right-click on the route and select Stop
Complete from the menu that pops up. (If necessary, use the Route Query to find
the route.) The Stop Complete for Route window opens with the next stop to be
completed highlighted.
772

From the Route Summary window, find the route by searching with the Route
Date boxes, if necessary. Double-click the Stops bar for the route. The Stop
Complete for Route window opens with the next stop to be completed highlighted.
The current stop, 2, is projected to be on time.
Step 3: If necessary, change the dates and/or times when the route actually arrived or
left the stop.
To change the time, type in the correct time, using the arrow keys to move from
the hour to minute field.
To set the Arrival or Departure to the current date and time, click the [Now]
button.
If desired, click the Delay Type arrow and select a delay type, and enter the
number of delay minutes to record for reporting purposes in the Delay Mins box.
Step 4: If necessary, change the actual miles to the stop.
Step 5: If your detail level is set to order or line item, change the delivery information
as necessary:
Operations Guide
773
To view the order or line-item information, click the plus sign next to Delivery
Details in the box at the bottom of the window. The list of orders appears. Click
the order plus sign if you have line items for that order.
To change the delivery information, double-click the order; the Details
notebook has two tabs labeled Planned and Actual. Enter the information
regarding the number of pieces delivered, picked up, damaged, etc. in the
appropriate fields on the Actual page. If there was a mistake in the planned
quantities, enter that information on the Planned page.
Step 6: If necessary, you can enter a reason code to explain why the actual delivery
quantity does not match the projected delivery quantity. Click on the
corresponding [List] button to open a Lookup window, and select the appropriate
reason code. Click the Process icon to apply the reason code.
Step 7: If the stop is part of a load, click the [Load Info] button to update the load
information as needed.
Step 8: Click the Complete icon to accept the information, then the Save icon or press
[Ctrl]+[S] to save it.
Step 9: If necessary, click the Close box to close the Stop Complete for Route window.
Completing All Stops at Once
If you know that all the remaining stops have met their projected times and you dont have
any special information to record for any of them, you can quickly complete all of them
at once. For more information, see Completing Stops on a Route or Completing an
Individual Stop.
Step 2: From an Overview or list window, right-click on the route and select Stop
Complete from the menu that pops up. (If necessary, use the Route Query to find
the route.) The Stop Complete for Route window opens with the next stop to be
Date boxes. Double-click the Stops bar for the route. The Stop Complete for Route
window opens with the next stop highlighted.
Step 3: Click the As Projected icon to fill in the actual Arrive and Depart columns with
the projected times.
If multiple routes were selected, the Stop Complete for Route window for the next route
is automatically displayed, ready to be worked on.
Dispatcher Overview/List/Route Summary window Stop Complete Complete/As
Projected Save icon ([Ctrl]+[S])
774

Completing a Route
Completing a Route
If a route has wireless communication, it will be completed automatically, using a

message from the driver. If a route cannot be completed automatically, use the steps given
here.
Warning: All of the stops on a route must be completed before you can complete the
route.
Completing a route does the following:
Sends any tracked information, such as hours or miles, to MobileCasts Accounting

module.
Removes the route from the list of uncompleted routes.
Releases the drivers and equipment used in the route back into the system so they can
be used for other routes.
Drops the equipment at the routes destination.
Step 2: From an Overview or list window, right-click on the route you want to
complete. Select Complete from the pop-up menu. The Complete Route window
opens, giving the planned return date and time.
If the projected date, time, and
mileage for completing the route
are correct, you do not need to
make any changes here.
To select multiple routes to complete, hold down the [Ctrl] key and click on each
route individually, then right-click on a selected route and select Complete from
the menu that pops up. To select multiple routes that are listed together, click the
first route and, holding down the [Shift] key, click the last route in the list.
Date boxes. When you have found the route, double-click its stop light icon. The
Route Complete window opens.
Step 3: If necessary, change the date and time in the Return field, and enter the mileage
in the Mileage box. Click on the arrow to open a list of time zones, and select the
time zone the Return time is sent in. If there was a delay in returning, select the
delay type and enter the number of minutes the delay lasted. This delay
information is used for reporting purposes only.
Operations Guide
775
Completing a Route
Step 4: If the route involves a load, click on the [Load Info] button to update load
information.
Step 5: Click the Save icon, or press [Ctrl]+[S] to accept the information.
Step 6: If any accounting information is to be created, a window pops up asking
whether you want to edit the information. Click the [Yes] button if you want to
edit individual accounting items; otherwise, click the [No] button to send the
information to the Accounting module without viewing or changing it. For more
on auto creating accounting information, see Working with Track Types and
Accounting for a Route.
Dispatcher Routes window Complete Save icon ([Ctrl]+[S])
776

Deleting a Route
Deleting a Route
Periodically, you may want to delete one or more routes from your database. You can
delete routes for specific dates using the Database Maintenance tool in the Maintenance
module. However, if you only want to delete selected routes on a date, you need to delete
them in the Dispatcher module.
Warning: Deleting a route removes the route and all its associated stops and information
permanently from the database. A deleted route cannot be recovered.
Step 1: From an Overview, Route Summary or list window, right-click on the route
you want to delete and select Delete from Database from the menu that pops up.
To select multiple routes to delete, hold down the [Ctrl] key and click on each
route individually, then right-click on a selected route and select Delete from
Database from the menu that pops up. To select multiple routes that are listed
together, click the first route and, holding down the [Shift] key, click the last route
in the list.
Step 2: A dialog box appears, asking if you want to Delete the Selected Route(s). Click
[Yes] to confirm this action, or [No] to cancel it.
Note: In order to delete routes, you must have the permission set to make changes to
dispatcher routes within the Administrative module. See Working with Privileges
for more information on setting this permission.
Dispatcher Routes window Delete from Database [Yes]
Operations Guide
777
Finding a Route
Finding a Route
Suppose you want to see all the routes that a particular driver has ever run, or you need to
know which route a particular location is on. For cases like these, and whenever you have
trouble finding a route from the normal windows, use the Route Query feature.
Route Query lets you find a route if you know any of the following: route ID, driver,
dispatcher ID, wireless device, the group the route is part of, a load that is on the route, or
a stop or order number on the route.
Step 2: Click Routes on the menu bar, then select Query. The Route Query Results
window opens. The notebook at the bottom of this window lets you search for
routes using several different criteria:
GeneralSearch by route date, ID, reference number, or group. If the route is
part of a load being transported by a common carrier, you can search on the
common carrier.
DetailSearch using a locations type, ID, description, or order number.
DriverSearch for routes assigned to a particular driver.
EquipmentSearch for routes with a particular piece of equipment assigned to
it.
WirelessSearch for routes with a particular wireless device assigned to it, or
with no devices assigned to it.
LoadSearch for routes containing a specific load.
Twenty-one routes were found that match the search for routes that started on 1/06/
2005.
Step 3: Click the appropriate tab and enter the information for the desired search. To
only search completed routes that meet the search criteria, verify a check is
present in the Completed Routes box. Click the Execute Query Using Criteria
778

Finding a Route
icon. MobileCast will list all the routes that meet your criteria in the Route Query
Results window. From there, you can start routes, complete stops, check
variances, etc.
Note: If no routes meet your criteria, MobileCast displays a Route window with no
routes in it.
Dispatcher Routes Query Execute Query Using Criteria icon
Operations Guide
779
Tracking Drivers
Tracking Drivers
Suppose you want to find out where a driver is, or should be, at a particular time.
MobileCast provides two ways to do this, both from the Dispatcher module:
If wireless communication is available, use Request Driver Position.
If wireless communication is unavailable or you dont want to send a wireless
message right now, use the Where function.
Requesting a Drivers Position
If you are using wireless communication and want to locate a driver, you can easily do so
by accessing the latest GPS information. In addition to locating a drivers current position,
you can also play back the route to see where the driver has been previously.
Note: When using wireless communication, the system regularly updates GPS
information at 15 minute intervals by default.
Step 2: Right-click on the route and select Request Driver Position from the menu that
pops up.
Step 3: MobileCast displays a message, verifying that a call has been sent to the
wireless device associated with that route. Click the [OK] button to close the
message window. As soon as possible, the device relays its current position. To
see the drivers current position, use the Position History Map, which is updated
when the result is received from the wireless device.
Hint: To see where the equipment has been so far on the route when it reported its
position, right-click on a route and select Position History. See Following a Route
in MobileCast for more information.
Dispatcher Routes window Request Driver Position
Using the Where Function
The Dispatcher modules Where function allows you to enter a date and time, and
MobileCast will determine the location of the driver at that time based on the current stop
information available for the route. This feature can be used to determine when a driver
will be near an area for a drop and hook or an unexpected pickup.
Step 2: Find the route in the Overview window, route list, or map. If necessary, use the
Route Query to find the route.
Step 3: Right-click on the route and select Where from the menu that pops up. The
Route Where window opens.
Step 4: The current date and time appear in the Route Where window.
780

Tracking Drivers
To change the time, click the hour or minutes and enter the new time. Select the
time zone the time refers to.
Step 5: When the date and time are correct for the route you want, click the [Where]
button. The location of the route at the specified time appears in the Route Where
window.
At 10:15 am on 9/20/2005, this
route is just leaving Landsdowne.
Step 6: Click the Close box to close the Route Where window.
Dispatcher Routes window Where
Operations Guide
781
Tracking Equipment with the Equipment Map

The Dispatcher module includes a special equipment map, which makes it easy to see
exactly where each piece of equipment is at the current time, based on the data that
MobileCast has about the routes. When used in conjunction with Calculate % Empty, this
feature can be very useful in determining which pieces of equipment in a specific area
have space available.
Step 2: Click View on the menu bar, then click Equipment Map. The Equipment Map
opens.
Dispatcher View Equipment Map
Currently, there is one tractor displayed on the map.
You will probably see several colored symbols on the map:
Red rectangles indicate equipment in use.
Green rectangles indicate equipment that is available.
Yellow rectangles indicate equipment that is not available, such as equipment being
repaired.
Blue rectangles indicate locations, such as depots, where there are many available
and unavailable pieces of equipment.
Any rectangle with a question mark in it means more than one piece of equipment is
at that location.
Step 3: Click a rectangle to get a list of the specific equipment at that place on the map.
Step 4: Click the Close box to close the map when finished.
782

Hint: To see the exact location of a particular piece of equipment, right-click anywhere
on the map, then click Equipment from the menu that pops up. The Equipment
window opens, with a search area at the bottom. Use the Search feature to find the
equipment you are looking for. Once the equipment appears in the list, doubleclick on it; MobileCast zooms the map to it and circles it.
Notes: To have the Equipment Map window automatically refresh, set the refresh rate to
a time greater than 0 seconds. To set the refresh rate, click Window on the menu
bar, then select Change Refresh Rate. Enter the refresh rate in seconds, minutes,
or hours, and click [Save].
To see where the equipment has been, right-click on the piece of equipment in the
list at the bottom of the Equipment Map window and select Position History. For
more information on Position History, refer to the Following Equipment and
Route Position History section.
Operations Guide
783
Following Equipment and Using Route Position History

If you are using a wireless device with GPS (Global Positioning System), and have the
device send GPS information throughout the day, you can play back the GPS entries to
see where the driver and/or the equipment has been for that day. This means that you can
follow a particular driver or piece of equipment and see their exact location on a map.
Also, you can display points on the map where the GPS pings detected the driver actually
stopped and, if necessary, re-geocode a location due to poor geocodes, or adjust the
delivery radius for a location. To learn how to re-geocode a location or adjust the delivery
radius, see Evaluating Cancelled Stops for more information.
The Position History map can also be used to pinpoint the exact location of any
unassigned stop, or any exception that may occur during the route. For more information
on unassigned stops or route exceptions, see Working with Unassigned Stops and
Working with Route Exceptions.
Using the Position History Map
The Position History map is easily accessible from the Dispatchers main menu, or from
the Equipment window, the Route window, and the Equipment Map. Also, you can drag
and drop a route or a piece of equipment onto the map to see specific position history
information. One of these methods is briefly described below, along with in-depth details
on setting up and using the Position History window.
Note: For other methods on how to access the Position History window, refer to the
Following Equipment and Following a Route in MobileCast sections.
Step 2: Select View, then select Position History. The Position History map opens.
The Settings button is used to customize the appearance of the playback on the
map. See Setting the Position History Map Options for more information.
The Find feature is used to further define your search when viewing equipment or
route position history. See Using the Find Feature for more information.
The GPS Playback player is used to navigate through the position history on the
map. See Using the GPS Playback Player for more information.
784

The Equipment Query section is used to select a specific piece of equipment,

allowing you to follow that piece of equipment throughout a route. See Following
Equipment for more information.
Use the GPS Playback
player to navigate
through the position
history on the map.
Click the [Settings]

buttons to customize
the map.
Use the Find feature to

further define your search.
Use the Equipment Query section to select a particular piece of equipment. This
allows you to follow that piece of equipment throughout a route.
Note: The icons at the top of the Position History map are the same as the icons on the
Map window. For more information on using these icons, see Map Icons.
For more information on using the map, see Using the Map in the Dispatcher.
Dispatcher View Position History
Setting the Position History Map Options
Before viewing the GPS entries for either your route or piece of equipment or to view the
GPS pings and fine tune a locations geocode, you must change the map settings to fit
your needs. These settings allow you to customize the route/equipments path and
appearance on the map while being played back as well as displaying the detected stop
points on the map.
Operations Guide
785
To customize the appearance of the GPS entries on the map, click the [Settings]
button. The Position Settings window opens.
The settings you select here will be used to customize the

appearance of the GPS entries for either a route or piece of
equipment on the map.
To set the area of the map that is displayed when using the find and play features,
select Zoom, Center, or No Change in the Navigation Type on Find or Play area. If you
select Zoom, then enter the distance you want the zoom to use. The map will zoom in that
distance on the entry being shown, refreshing and continuously zooming as the playback
proceeds. If you select Center, then the map will center the GPS entry on the map. If you
select No Change, then the map will show the path as is, with no zoom or centering.
To use the route color for the equipments path, check Use Route Color for Equipment
with Routes. If the piece of equipment is not associated with a route, then the color you
choose as your Static Position Color will be used instead. To choose the Static Position
Color, click on the arrow and select a color from the palette that appears.
To show data breaks if the piece of equipment or route is inactive for an extended
amount of time, check Show Data Breaks, then enter the maximum number of minutes
a piece of equipment is allowed to be stationary. For example, if you want to show breaks
if the piece of equipment sits for 30 minutes or longer, then enter the number 30. Finally,
click on the arrow and select the color you want to represent the data breaks.
To start the playback at the first GPS entry, check Always Start at First Item When In
Play Mode. If this option is not checked, then the playback will start wherever you place
the Slider Bar in the GPS Playback Player. For more information, see Using the GPS
Playback Player.
To set the playback speed, enter the number of seconds between GPS entries in the Play
Speed in Seconds field. For example, if you have the playback speed set to 2, then there
will be a two second delay between when each GPS entry is displayed on the map. The
minimum playback speed is 0.1 seconds.
786

To fade older items as the playback proceeds, check Fade Older Items In Path. Then,
enter the number of recent items you do not want to fade in the Number of Items Not to
Fade field. For example, if you entered a 3 in this field, then only the 3 most recent
locations for that piece of equipment are bold on the map, the previous positions will be
faded.
To show lines between positions, check Show Lines Between Position Items.
To show locations on the map, check Show Locations. Then, click on the arrow and
select a color from the palette that appears. This color will represent the locations on the
map.
To show equipment position labels when printing, check Show Position Labels When
Printing. This means that when you print the map, the locations date and time are shown
on the map. If the query is for one day, only the time will be shown next to the location.
To show points where the GPS has identified a vehicle has stopped, check Show
Detected Stop Points. Then, click on the arrow and select a color from the palette that
represents the detected stop points. The stop points are shown as stars on the map in the
color selected.
Note: The Show Detected Stop Points field on the Position Settings window for the
Cancelled Stop Analyzer window is checked by default.
In order to see the detected stop points on the Position History map, you must
access the Position Settings window from the Position History window and set it
up. This field is not checked by default.
Make the necessary selections, then click the [Apply] button to save the settings for this
use or click the [Save] button to save for future use.
Dispatcher View Position History [Settings]
Using the Find Feature
The Find feature is used to further define your search. After entering a specific date and
time, MobileCast finds the closest GPS entry and marks it on the map.
To enter a date, either enter it manually or click on the arrow
next to the [Find] button to open a calendar. To change the
month, either use the arrows on the top of the calendar to scroll
through the months, or click on the month and select from the
menu that pops up. To change the year, click on the year and use
the small arrows to scroll to the correct year. Click on a date to
select it. You must enter the time manually.
Dispatcher View Position History [Find]
Using the GPS Playback Player
While the history is being displayed on the map, you can use the GPS Playback player
(located at the top of the Position History map) to move from one GPS entry to another.
Operations Guide
787
The GPS Playback player is similar to a compact disk or cassette player; you can start,
stop, pause, rewind, and forward the route.
Start Time
Slider Bar
End Time
GPS Player
To play the entire route, click the [Play] button. While playing, both time and
location will be displayed on the map.
To stop the playback, and return to the beginning, click the [Stop] button.
To pause the playback, allowing it to resume where you left off, click the [Pause]
button. Click the [Pause] button again to resume play.
To move to the first GPS item, click the First Entry] button.
To move to the previous GPS entry, click the [Previous Entry] button.
To move to the last GPS item, click the [Last Entry] button.
To move to the next GPS entry, click the [Next Entry] button.
To move to specific GPS entry, move the Slider Bar forward or backward. The
time and location that is the closest match for the GPS entry will appear on the
map. To the left and right of the Slider Bar is the date and time of the first and last
GPS entry for the given route or equipment path.
Following Equipment
There are several methods you can use to find a piece of equipment and view its path in
the Position History window:
If you have opened the Position History map from the main toolbar in the
Dispatcher (by selecting View, then Position History), you can use the query option
found at the bottom of the map to search for your equipments position history.
First, in the Timeframe section of the Position History map, enter a starting and, if
necessary, an ending date and time for the position history playback.
Next, select the piece of equipment you want to view by clicking the Equipment arrow
to open the Lookup - Equipment window, with a search area at the bottom. Use the
Search feature to find the equipment you are looking for. Once the equipment appears
in the list, double-click on it, or click on a piece of equipment and then on the Process
icon to select it.
788

Finally, after entering the date, time, and equipment information, click the [Query]
button to find the GPS entries that contain all of the specified information. The
equipments position history playback appears on the map.
If you are viewing the Equipment list, simply right-click on a piece of equipment
and select Position History from the menu that pops up. The equipments position
history playback appears on the map.
OR
Left-click on a piece of equipment, then drag and drop it into an already open Position
History map. This will replace the previous route or equipment position history
displayed with the new path.
If you are using the Equipment Map, right-click on the piece of equipment in the
list at the bottom of the Equipment Map window and select Position History. The
Position History map opens, and the equipments position history playback appears
in the map.
To start the position history playback, click play in the GPS Playback Player. As the
equipments position history is shown on the map, an arrow moves from GPS entry to
GPS entry, displaying the equipments actual path. Also, as the path progresses, a time
stamp appears showing you the exact time for that GPS entry. For more information on
using the Position History map, refer to the Using the Position History Map section.
When you hover your mouse over a location, a tool tip appears displaying its location,
the Route ID, the date and time, and its proximity to the nearest city or set of cross streets.
When you hover your mouse over a

location, the same information that is
displayed in the tool tip also appears
at the bottom of the window.
To display the map and the GPS

Playback player, while hiding the
Equipment Query options, click on
the arrow at the bottom right corner
of the window.
Operations Guide
789
Notes: Until the playback is complete, the Position History map view will not refresh to
show the current equipment position.
To set whether to display the locations proximity to the nearest city or to the
nearest set of cross streets, refer to the Dispatch - General page of the Maintenance
Options notebook for more information.
Following a Route
There are several methods you can use to find a route and view its path in the Position
History map:
From the Route Overview window, right-click on a route and select Position History
from the menu that pops up. The Position History map opens with the route
displayed on the map.
OR
Left-click on a route, then drag and drop it into an already open Position History
map. This will replace the previous route or equipment position history displayed
with the new route.
As the position history is shown on the map, an arrow moves from GPS entry to GPS
entry, displaying the routes actual path. Also, as the path progresses, a time stamp
appears showing you the exact time for that GPS entry. For more information on using
the Position History map, refer to the Using the Position History Map section.
When you hover your mouse over a location, a tool tip appears displaying its location, the
Route ID, the date and time, and its proximity to the nearest city or set of cross streets.
When you hover your mouse over a location, the same information that is displayed
in the tool tip also appears at the bottom of the window.
Notes: The Equipment Query options only appear if you are viewing position history for
a piece of equipment, or if you access the Position History map from the
790

Equipment list, Equipment Map, or from the View menu in the Dispatcher
module.
To set whether to display the locations proximity to the nearest city or to the
nearest set of cross streets, refer to the Dispatch - General page of the Maintenance
Options notebook for more information.
Operations Guide
791
Evaluating Cancelled Stops

If you are using On Track, auto arrive/depart, or telematics, it is vital that your geocodes
are accurate and that the arrival/departure radii are correct. The Cancelled Stop Analyzer
window allows you to review a list of cancelled stops and re-geocode the location and/or
adjust the delivery radius as needed. This will help you fine tune the geocodes of locations
that have incomplete or incorrect addresses, or the arrival/departure radii are inaccurate.
There can be several reasons why a stop was cancelled. There are times when a stop is
cancelled because a location changed their delivery day or cancelled their order. This stop
is cancelled by either the driver or the dispatcher manually. Other cancelled stops may be
due to poor geocodes, or it could be that the size of the delivery radius used to determine
whether the driver is at the location or not needs to be adjusted. These type of stops would
be cancelled automatically. For example, Stop 4 is geocoded to 701 Washington Avenue,
but the GPS information sent doesnt coincide with where the driver stopped - 711
Washington Avenue, so the stop was automatically cancelled.
The Cancelled Stop Analyzer window lists all cancelled stops, whether they were
cancelled manually by the driver or automatically. With each cancelled stop, you can
decide whether to leave its location as is, fine tune the locations geocode, which would
be permanent, and/or adjust the delivery radius for the location. By re-geocoding or
adjusting the delivery radius of a location, the more accurate auto arrive/depart
information for that location will be for future routing.
Note: These actions can also be performed from the Route Watch Map, Plot map, or
Position History window, but the detected stop points do not display on the Route
Watch Map or Plot map.
On the Cancelled Stop Analyzer window, there is a column labelled Cancel Code. The
code in the column identifies whether the stop was cancelled automatically or manually.
When you select a cancelled stop from the list, an X outlined in a box displays on the map
where the stop is currently geocoded along with the original radius. The X represents the
cancelled stop and is the same color as the route. The Detected Stop Points star represents
the calculated position based on the GPS pings detected as to where the driver actually
stopped. When you hover your mouse over a Detected Stop Points star, a tool tip will
display the following information: the Detected Stop Start Time, the Detected Stop End
Time, and the Detected Stop Duration.
Setting Up the Options for the Cancelled Stop Analyzer Window
If you are using a wireless device with GPS (Global Positioning System), and are having
the device send GPS information throughout the day, you can follow a particular driver
or piece of equipment and see their exact location on a map. In order to view the GPS
pings and fine tune a locations geocode, you must change the map settings to fit your
needs.
792

Note: Not all fields on the Position Settings window are valid for the Cancelled Stop
Analyzer window (invalid fields will appear grey).
Step 1: Click the Dispatching icon to open the Dispatcher module. The Dispatcher
window opens.
Step 2: Click on the List menu and select Cancelled Stops. The Cancelled Stop
Analyzer window opens.
Step 3: Click the Options icon and select Position Settings from the menu that pops up.
The Position History window opens.
Note: In order to see GPS entries on both the Cancelled Stop Analyzer window and the
Position History window, you must set up the option in both windows. To access
the Position Settings window from the Position History window, click the
[Settings] button.
The settings you select here
will be used to customize
the appearance of the GPS
entries for either a route or
piece of equipment on the
map.
Step 4: Check Show Detected Stop Points to show points where the GPS determined if
the driver stopped or not. Then, click the arrow and select a color from the palette
that represents the detected stop points. The stop points are shown as stars on the
map in the color selected.
Note: The Show Detected Stop Points field on the Position Settings window for the
Cancelled Stop Analyzer window is checked by default, but not from the Position
History window.
Step 5: Choose the remaining options as appropriate.
To use the route color for the equipments path, check Use Route Color for
Equipment with Routes. If the piece of equipment is not associated with a route,
then the color you choose as your Static Position Color will be used instead. To
choose the Static Position Color, click the arrow and select a color from the palette
that appears.
To show data breaks if the piece of equipment or route is inactive for an
extended amount of time, check Show Data Breaks, then enter the maximum
number of minutes a piece of equipment is allowed to be stationary. For example,
Operations Guide
793
if you want to show breaks if the piece of equipment sits for 30 minutes or longer,
then enter the number 30. Finally, click the arrow and select the color you want to
represent the data breaks.
To fade older items as the playback proceeds, check Fade Older Items In Path.
Then, enter the number of recent items you do not want to fade in the Number of
Items Not to Fade field. For example, if you entered a 3 in this field, then only the
3 most recent locations for that piece of equipment are bold on the map, the
previous positions will be faded.
To show lines between positions, check Show Lines Between Position Items.
To show locations on the map, check Show Locations. Then, click the arrow and
select a color from the palette that appears. This color will represent the locations
on the map.
To show equipment position labels when printing, check Show Position Labels
When Printing. This means that when you print the map, the locations date and
time are shown on the map. If the query is for one day, only the time will be shown
next to the location.
To show points where the GPS has identified a vehicle has stopped, check
Show Detected Stop Points. Then, click on the arrow and select a color from the
palette that represents the detected stop points. The stop points are shown as stars
on the map in the color selected.
Step 6: Click the [Save] button to save the changes.
Dispatcher List Cancelled Stops Options icon Position Settings
Re-geocode and/or Adjust the Radii for Cancelled Stop Locations
When evaluating the list of cancelled stops on the Cancelled Stop Analyzer window, you
may discover that some of the cancelled stops were automatically cancelled because of
poor geocodes, or that the delivery radius was too large or small for the location. You can
fine tune the locations geocode, which would be permanent and/or adjust the delivery
radius for a location from this window. By re-geocoding or adjusting the delivery radius
of a location, the more accurate the auto arrive/depart information for that location will
be for future routing.
Note: The Cancelled Stop Analyzer window is intended to be used with the Auto Arrive
and Depart, On Track, or Telematics features.
window opens.
Step 2: Click on the List menu and select Cancelled Stops. The Cancelled Stop
Analyzer window opens.
Hint: Make sure that the Show Detected Stop Points field is checked in the Position
Settings window. See Setting Up the Options for the Cancelled Stop Analyzer
Window for more information.
794

To make it easier to determine if a stop was cancelled manually or automatically,

move the Cancel Code column so that you can see the column while looking at each
stop.
To see the geocode quality of the location, move the Location Geocode Quality
column so that you can see the column while looking at each stop.
Step 3: In the Timeframe section, the date range displayed is the previous days date by
default. If you want to display cancelled stops for a different date, enter the
starting and ending date. To enter a date, either enter it manually, or click the arrow
to open a calendar. To change the month, either use the arrows on the top of the
scroll to the correct year. Click on the date to select it.
Step 4: Click the [Query] button. A list of cancelled stops displays with the first cancelled
stop on the list highlighted and displayed on the map.
The Cancelled Stop Analyzer window will display a list of stops that were cancelled. The list
consists of driver initiated and automatic cancellations.
Step 5: Looking at the cancelled stop on the map as well as the Cancel Code column,
decide whether or not you need to do anything for this stop. If a stop is cancelled
automatically, you will see AUT in the Cancel Code column. If the stop is
cancelled manually by the driver and cancel codes have been set up, that code
displays. Otherwise, CON is the default for a manually cancelled stop.
Hint: While analyzing a cancelled stop on the map, you can use normal map navigation
functionality to move around the map, as needed. For example, to see a cancelled
stop more closely, click the Zoom In icon.
Operations Guide
795
Step 6: If you decide you want to re-geocode the location, right-click on the stop and
select Re-geocode from the menu that pops up. The cursor changes to a cross hair,
indicating that you are in Geocode mode. Move the cross hair cursor where you
want the location to be geocoded. The message Do you really want to regeocode? displays. Click Yes. When you are done re-geocoding the location,
click the [Remove From View] button. The stop is removed from the list.
- OR If you decide that the delivery radius for a location needs to be adjusted, rightclick on the stop and select Adjust Delivery Radius from the menu that pops up.
The cursor changes to a directional cursor, indicating that you are able to adjust
the radius of the location. Move the directional cursor to adjust the size of the
radius to make it smaller or larger. Once you have made the radius to the size you
want, click the mouse button to end the mode. When you are done adjusting the
radius for the location, click the [Remove From View] button. The stop is removed
from the list.
- OR If you decide that nothing needs to be done for the stop, click the [Remove From
View] button to shorten the list.
Note: If you look at the Location Geocode Quality column after you re-geocode a
location, Self Geocoded displays in the column.
While adjusting the delivery radius for a location, the original delivery radius
continues to display until you click the mouse button to end the mode. Also, the
size of the delivery radius displays in the bottom right corner of the window.
If you want the map to display on the entire screen for a particular stop, click the
Show/Hide Window Extension icon. The cancelled stop list disappears and the map
displays completely on the window. To redisplay the cancelled stop list, click the
Show/Hide Window Extension icon again.
Step 7: Repeat Steps 5 - 6 for each cancelled stop on the list.
Step 8: When you are done, click the Close box to close the Cancelled Stop Analyzer
window.
Dispatcher List Cancelled Stops
796

Working with Route Exceptions

You can set up the Roadnet Transportation Suite so that Dispatcher will let you know
when a route exception has been generated based on parameters you define. For instance,
if you want to know if a driver strays too far from the expected path, you can have
Dispatcher alert you when this happens. These instances are called route exceptions. You
can use the route exception rules wizard in the Maintenance module to easily create
custom route exception rules for a situation that you are interesting in tracking.
Exceptions that are generated based on those rules will display in Dispatcher. For more
information on creating your own route exceptions, refer to Working with Route
Exception Rules.
You can view route exceptions for a specific route; see Viewing Route Exceptions for
more information. You can also keep your eye on specific routes by viewing all the
exceptions as they happen; see Using Route Watch for more information. You can also
view route exceptions on the maps, at the stops and locations where they occurred.
Notes: Routes with unacknowledged exceptions will appear in the Route Summary
window with a yellow light displayed in the Status column. For information on
acknowledging a route exception, refer to Using Route Watch.
Viewing Route Exceptions
You can specify parameters that will cause an exception to generate for routes in
Dispatcher. As routes are created and run, if they meet the parameters that you define,
then exceptions are generated and displayed in Dispatcher. You can view route exceptions
for a specific route. The route exception rules wizard in the Maintenance module lets you
create rules for the exceptions you are interesting in tracking, as well as define parameters.
For more information on creating route exceptions, see Working with Route Exception
Rules.
Step 1: From the Dispatcher, find the route in the Overview window, or route list. If
necessary, use the Route Query to find the route.
Step 2: Right-click on a route and select Lookup, then Exceptions. The Route
Exceptions window opens, displaying that routes exceptions.
The Exceptions window shows all exceptions for the selected route.
From the Route Exceptions window, you can see the region, route ID, route name,
exception rule, the time the exception occurred, the longitude and latitude in
which it occurred, a brief description, whether or not the exception has been
acknowledged, the proximity to the nearest city or cross street, and so on.
Operations Guide
797
Step 3: To see all the exceptions for the route on a map, click the Map icon. A map
opens showing the route, with the exceptions at the locations where they have
occurred.
OR
To see a particular exception from the Route Exceptions window, click on the
exception, then drag it to the Position History map. The map will refresh and zoom
to the place on the route where the exception occurred.
Notes: For more information about setting up maps to view route exceptions, turn to Map
User Settings in Dispatcher.
For more information about working with route exceptions on the maps, turn to
Viewing Route Exceptions on the Maps.
Dispatcher Routes Lookup Exceptions Position History map
Using Route Watch
You can establish parameters that will cause an exception to generate for routes in
then exceptions are generated and displayed in Dispatcher. You can keep an eye on
specific routes using Route Watch. The route exception rules wizard in the Maintenance
module lets you create rules for the exceptions you are interesting in tracking, as well as
define parameters. For more information on creating route exceptions, see Working with
Route Exception Rules.
Route Watch builds on the notion of a route exception by allowing you to view all
exceptions as they happen. This means that as a route is progressing through its stops, you
will see live updates and know exactly when an exception occurs. The Route Watch
window has two sections the top section lists all the routes that have exceptions, while
the bottom section lists the exceptions for the route selected in the top section.
The Route Watch window lets you see a detailed list of a route exceptions, plus you can
acknowledge the route exception. Acknowledging a route exception simply means that
youve seen it and you dont want to be reminded of it anymore. When you acknowledge
an exception, it will no longer appear in the Route Watch window, but it will still appear
in the Route Exceptions list for that particular route.
Note: Routes with unacknowledged exceptions will appear in the Route Summary
window with a yellow light displayed in the Status column.
Route exceptions can be processed several ways. When creating a rule, you can choose
how exceptions for that rule are processed:
Continuallyexceptions are generated as they occur.
Time of Dayexceptions are generated once per day at the specified time.
Event Based exceptions are generated when an event(s) occurs.
798

To access the Route Watch window, open the Dispatcher, click View, and select Route
Watch from the menu. The Route Watch window opens displaying any routes that have
unacknowledged exceptions.
You are able to view the routes that are assigned to you.
Note: If you are only viewing the routes assigned to you, and you have no routes with
exceptions, then the Route Watch window will be empty. For more information
on viewing only your assigned routes, refer to Viewing My Routes Only.
To refresh the window immediately, click on the Refresh icon at the top of the window.
This will update the Route Watch window and give you the most up-to-date information.
To keep an eye on a route that is not already in the Route Watch window, open the
Overview window or a Route list window to view your routes. Then, select the route and
drag it into the Route Watch window. An exception will automatically be generated when
the route is manually dragged onto the Route Watch window; this exception will appear
in the Rule ID column as USER-MC.
To see the exceptions for a particular route, select the route in the top section of the
window. All of the routes exceptions will appear in the lower section.
To view a detailed description of the route exception rule, right-click on the exception
and select View Description from the menu that pops up. The Dispatcher window opens,
displaying the parameters.
To view detailed information for a specific route exception, right-click on the
exception and select Show Me from the menu that pops up. A window will open
displaying detailed information about the route exception. For instance, depending on the
exception, a map will open or, if you selected exception parameters for line items, then
the Line Item window will open.
To acknowledge a route exception, removing it from the Route Watch window, rightclick on the exception and select Acknowledge from the menu that pops up.
To open a map from Route Watch to view the exceptions, click on the Map icon. A
Route Watch Map opens showing all the routes and their unacknowledged exceptions.
For more information about the Route Watch Map, see Using the Route Watch Map.
Operations Guide
799
MapsDispatcher View Route Watch

Using the Route Watch Map
The Route Watch Map continually monitors current route exceptions. You can see where
the route exceptions are happening and acknowledge them right on the map.
Acknowledging a route exception simply means that youve seen it and you dont want
to be reminded of it anymore. When you acknowledge an exception, it will no longer
appear on the Route Watch Map, but it will still appear in the Route Exceptions list for
that particular route.
To access the Route Watch Map, open the Dispatcher, click View, and select Route
Watch Map. The Route Watch Map opens displaying any routes that have
unacknowledged exceptions and where the exceptions occurred.
Hint: You can also open the Route Watch Map from Route Watch by clicking the Map
icon in the Route Watch toolbar
To view a detailed description of the route exception rule, right-click on the exception
and select Show Description from the menu that pops up. A message opens, displaying
the exception and how it was triggered.
To view detailed information for a specific route exception, right-click on the
exception and select Show Details from the menu that pops up. A window will open
displaying detailed information about the route exception. For instance, depending on the
exception, a map will open or, if you selected exception parameters for line items, then
the Line Item window will open.
To acknowledge a route exception, removing it from the Route Watch Map, right-click
on the exception and select Acknowledge from the menu that pops up.
MapsDispatcher View Route Watch Map
Viewing Route Exceptions on the Maps
800

After you have set up your exception rules in Maintenance and set up your map display
options in the Map Properties notebook, you can view exceptions on the new Route
Watch Map, as well as the Route Plot and Position History maps.
Exceptions appear as yellow diamonds outlined in the color of the route, and
acknowledged exceptions appear as white diamonds. The character selected for the route
exception appears in black inside the diamond. Exceptions will appear on all maps
displaying routes in the Dispatcher module.
Note: If multiple exceptions occur at the same location, or if they overlap on the map, they
will be indicated by three exclamation points (!!!), no matter what character you
have chosen to represent each individual exception.
Route exceptions appear on the maps at the location where the exception has occurred. If
there is no latitude and longitude information available for the exception, it will appear at
the routes origin.
You can view all the exceptions for all the routes at once, or all the exceptions for just one
route, or you can look at one particular exception.
GPS-based exceptions appear on the route at the location where the exception has
occurred.
Important: If too many exceptions start to crowd your routes, it will be difficult to see
the exceptions on the map, so its important that you acknowledge your route
exceptions on a frequent basis.
Operations Guide
801
To continually monitor current exceptions on a map as they occur or are

acknowledged, click on the View menu and select Route Watch Map. The Route Watch
Map opens.
Note: Exceptions on the Route Watch Maps are automatically updated based on the
Refresh Rate. For more information, see Refreshing the Windows in Dispatcher in
the Roadnet Transportation Suite Operations Guide or online help.
To see unacknowledged exceptions for all your routes, click the Map icon located in
the Route Watch toolbar to open a map showing the exceptions.
To track exceptions as they occur along the course of the route, open the Overview
window or a Route list window and select Position History.
To see all the exceptions for an individual route, including acknowledged exceptions
if you have chosen to display them, open the Overview window or a Route list window
and select Plot or Position History.
Hint: You can also see all the exceptions for an individual route from the Route Exception
list by clicking the Map icon.
Note: Acknowledged exceptions appear on the Plot and Position History maps as white
diamonds. They will not appear on Route Watch maps.
To view a single exception for a route, right-click on the exception in the Exceptions
window and choose Show Me from the menu that pops up. GPS-based exceptions will
open in a map; all other exceptions will open a Route window.
To see the entire route with all exceptions mapped, click the Map icon on the
Exception list window.
To work with a particular exception on any map, right-click on the exception and
choose one of the following options:
To acknowledge the exceptionclick Acknowledge. This will also update any
exception lists, Route Watch, and the Route Watch Map.
To see a list of all the exceptions for a routeclick Show Details. The Route
Exceptions window for the route opens, containing detailed information for each
of the routes exceptions. The exception you have selected will be highlighted on
this list.
To see a brief description of the exceptionclick Show Description. A window
opens displaying concise information about the exception, such as the exceptions
location and why it was triggered.
802

Viewing Diagnostic Information

MobileCast has a feature that allows the dispatcher to monitor the state of the wireless
device assigned to a route, as well as any problems or issues that have occurred on the
device while the route is being run. This feature, called device diagnostics, allows the
dispatcher to easily see any diagnostic information the device has sent, including battery
strength and signal strength, while the route is being run. In the event there is a problem
with the device that needs to be checked, all necessary information will have been sent to
the server so it can be viewed and easily accessed.
If the dispatcher has not received any messages from a driver or device in a while, he can
view the diagnostic information for the device in the Dispatch module. Diagnostic
information can be seen for routes that have not been started or for routes that have
already been completed. Follow the steps below to view the diagnostic information for a
route.
Notes: Device Diagnostics must be enabled for a driver in order to view diagnostic
information for that drivers wireless device. You can enable device diagnostics
for a driver in the Edit Driver window in Maintenance. You can also enable device
diagnostics for several drivers at once in either Maintenance or Dispatching. To
do this, open the Drivers window that lists all the drivers and [Ctrl]+click each
driver you want to enable device diagnostics for. Right-click and select Device
Diagnostics, then Activate.
You can set how much diagnostic information the wireless devices will report and
how often the devices will report periodically sent information back to the server
in the Maintenance Options notebook.
Step 1: In the Dispatch module, right-click on the route you want to view and select
Lookup - Device Diagnostics from the menu that pops up. The Device Diagnostic
Analysis window opens.
The Device Diagnostic Analysis window has two lists and a map. The top list
shows all the diagnostic events for the route; if you click on an event in the top list
information about the event is displayed in the bottom list, if any detailed
information available for that event. The right side of the window has a map,
showing the route and the events for the route. The various types of events and
map markers are summarized in the table below.
Device Diagnostic Events
Event Type
Map Marker
Description
Periodic
Blue star
Generated at configurable intervals on the device;

intended to capture the devices current state.
Comm
Exception
Black hollow
diamond
Generated when communication problems occur on the

device.
GPS Exception
Green star
Generated when a GPS exception occurs on the device.
Operations Guide
803
Event Type
Map Marker
Description
Device
Exception
Green hollow
square
Generated when a general exception occurs on the device.
Device
Statistics
Solid yellow
square
Generated at the completion of a route on the device.
GPS
Solid red
diamond
Generated when a GPS ping is received on the device.
Event Receipts
Hollow pink
circle
Generated by a message sent from the server to the

device.
General
Diagnostics
Dark blue cross
Generated by other events during the routes progression,

such as a route request, route received, route start and
depart, stop arrive and complete, route arrive and
complete.
Likewise, the battery power and signal strength are displayed in various colors to
indicate the quality. The colors and quality are summarized in the tables below.
Signal Strength
Signal Strength
Status
Color
<-70
Very Good
Green
<-71 and >=-85
Good
Dark Green
<=-86 and >=-100
Moderate
Pink
>-100
Bad
Red
Battery Power
Status
Color
>=80
Very Good
Green
>=60 and <=79
Good
Dark Green
>=40 and <=69
Moderate
Pink
<40
Bad
Red
Battery Power
Step 2: Enter the Start and End date and time for time frame you want to view. To enter
a date, check the box and click on the arrow to open a calendar. To change the
month, either use the arrows on the top of the calendar to scroll through the
the year, click on the year and use the arrows to scroll to the correct year. Click
on a date to select it. To enter a time, type the time in the field.
804

Step 3: To select the events that will be displayed on the map, click the [Options]
button. The Device Diagnostic Options window opens.
The Device Diagnostics

Options window lets you
select the diagnostic events
that will be displayed on the
map.
To display an event on the map, check the box for the event.
To have the devices battery strength indicated on the map, choose Battery Power
in the Path Mode area.
To have the signal strength the device receives indicated on the map, choose
Signal Strength in the Path Mode area.
Click the [Save] button to save the options.
Step 4: On the Device Diagnostics Analysis window, click on a diagnostic event on the
map or in the list; the event will be highlighted in on both the map and the list,
and details about the event are displayed in the lower list.
Notes: Not all events will have details to display in the lower list.
Any exceptions existing on the routes will be displayed on the Device Diagnostic
map. These exceptions are displayed for informational purposes only; you cannot
acknowledge exceptions, open the route exceptions window, or perform any other
action with them from this map.
Operations Guide
805
The Device Diagnostics Analysis window lets you easily see if a driver and the device
went out of coverage or if the devices battery lost its charge.
Step 5: Once your analysis of the route is complete, close the Device Diagnostic
Analysis window.
Dispatcher Route Lookup Device Diagnostics
806

Checking the Route Assignments

In the Dispatcher module, you can easily look up the dispatcher, equipment, wireless
device, and other information associated with a route. You can also look up a routes
status and any messages sent or received using the wireless equipment for a route. These
look-up windows are for viewing information only; you cannot assign resources or
change the information in these windows.
The following information can be checked:
StopsLists the stops on the route.
NotesLists all or acknowledged notes associated with the route.
LoadsLists all loads assigned to the route.
OrdersLists any orders on the route.
Order ActivitiesLists any order activities associated with the route.
Order Financial DetailsLists any order financial details associated with the route.
ContainersLists any containers and their status (i.e. loaded, on route, scanned,
manually entered, etc.) on a route. for more information on statuses, see Container
Statuses.
DriversLists the drivers assigned to the route.
Delay TypeLists any delay types assigned when the route was started or completed.
Stop delays are not listed here; they are included in the Stops lookup list.
OriginLists the location where the route started (usually a depot).
DispatcherLists the dispatcher associated with the route, if one was assigned when the
route was started.
EquipmentLists the equipment assigned to the route.
Proof of DeliveryShows any signatures or stop signature codes that the driver got as
proof of delivery.
Note: From the Proof of Delivery window, you can save the signature to a separate file
by right-clicking on the signature and selecting Save to File.
Route TypeLists any route type assigned to the route from the General page of the
Assignments window.
StatusLists any status assigned to the route.
ExceptionsOpens the Route Exceptions window for that specific route, listing all the
exceptions that have been generated for that route.
User Defined DataLists the user-defined tables, that when selected, allows you to view
the data for that table.
Wireless EventsLists all messages sent and received via the wireless device assigned
to the route.
Operations Guide
807
Event ReceiptsLists all events that are sent back and forth between the server and a
wireless device.
Pre-Route Survey ResultsLists the survey results associated with any pre-route tasks.
Post-Route Survey ResultsLists the survey results associated with any post-route
tasks.
Device Diagnosticsopens the Device Diagnostics Analysis window, where you can
review diagnostic information from the device. See Viewing Diagnostic Information for
more information.
Step 2: Find the desired route in the Overview window, route list, or map. If necessary,
use the Route Query to find the route.
Step 3: Right-click the route you want to check and select Lookup from the menu that
pops up, then the item you want to check.
Step 4: When you are finished viewing a lookup window, click the Close box.
Notes: You can also double-click the route in the Route Summary window to check the
driver and equipment assignments.
Changes to a routes origin or status are made from the Route Properties notebook.
Dispatcher Route Lookup Desired Lookup
Container Statuses
Containers are items you can scan for delivery/pickup tracking. They allow customers to
associate a different barcode (other than the order or line item ID) with a delivery/pickup
item. Containers can contain the following: orders and line items, full, partial, or multiple.
Drivers have the ability to scan the containers at multiple points during their route. This
allows customers to control the detail level of the status updates that are provided to the
system. There are three available scan points:
Scan at Loadoccurs after the route starts, but before the route departs.
Scan at Stopoccurs while servicing a stop.
Scan at Unloadoccurs after the route arrives, but before the route is complete.
Drivers also have the ability to add new containers, or deliver a container to a different
stop. Below is a list of the container statuses and their descriptions.
Container Status
Description
None
There is no status associated with this container. This is the default value.
Initial Add
The container was added to the system.
Loaded
The container was loaded on the truck at the start of the route.
Delivered Dropped Off
The container was delivered to the stop. The physical container was left
with the customer.
808

Delivered Returning
The container was delivered to the stop. The physical container was
loaded back onto the truck.
Picked Up
The container was picked up at the stop.
Not Loaded
The container was not loaded onto the truck at the start of the route.
Note: This is different from Not Found at Loading.
Not Delivered
The container was not delivered to the stop.

Note: This is different from Not Found at Stop.
Not Picked Up
The container was not picked up at the stop.
Not Found at Loading
The container was not loaded onto the truck at the start of the route
because it was not found.
Not Found at Stop
The container was not delivered to the stop because it was not found.
On Route
The container is on the truck.
Return
The container has been returned to the depot.
Delivered to Different Stop
The container was delivered to a different stop than originally planned.
Picked Up from Different

Stop
The container was picked up from a different stop than originally

planned.
Unloaded
The container was unloaded from the truck at the completion of the route.
Not Found at Unloading
The container was not found on the truck at the completion of the route.
Scan Quality
Drivers have the ability to scan, manually check off, or enter a barcode into a text entry
box to update the status of the container at a scan point. This value is reflected in the scan
quality of the status update.
Scan Status
Description
None
There is no scan quality. This is the default value.
Scanned
The container barcode was scanned.
Checked
The driver manually checked the container barcode.
Entered
The driver manually entered the container barcode.
Operations Guide
809
Working with the Route Properties Notebook
Working with the Route Properties Notebook

You can use the Route Properties notebook to add, view, or change information for a
route, stop, order, or line item, depending on the detail level you have established in the
Options notebook. The Route Properties notebook contains basic information about your
routes, such as the ID, origin and destination, user-defined fields, transportation costs, etc.
Simply right-click on a route and select Properties from the menu that pops up; this opens
the Route Properties notebook. In addition to accessing route information, you can use the
overview on the left to access stop, order, and line item information, thus changing the
notebook on the right accordingly. Click on the plus sign next to an item or double-click
the item to expand it.
To add detail to a route, stop, or orderfor example, to add an order to a stop--click
on the item to which you are adding detail and click the Add Detail icon. Complete the
notebook pages as needed.
To add another of the same item to a route, stop, or orderfor example, to add an
additional order to a list of orders--click on an item in the list and click the Add Another
icon. Complete the notebook pages as needed.
Important: Be sure to click the Save icon to save any changes you make within Route
Properties notebook.
Note: In order to delete information about a route that has been loaded onto a device,
you must have been granted permission to delete routes in the Administration
module. See Working with Privileges for more information.
810

Creating a Route
Creating a Route
Although you will probably import most of your routes from a source outside of
MobileCast, you might also need to add some routes from within MobileCast. The
Dispatcher allows you to easily add routes, and the stops, orders, containers, and line
items associated with the routes. For more information, see Adding, Changing, Deleting,
or Unassigning Stops on a Route, Entering Order or Line Item Information, Changing the
Order of Stops on a Route, and Transferring Stops between Routes in MobileCast.
Step 2: On the menu bar, click Routes, then New. The Add Route notebook opens.
The Add Route notebook provides a way to create a route

on the fly.
Step 3: Enter up to 15 letters and/or numbers as the route ID, and select a departure
date. If Auto Generate Route ID is selected on the Dispatch - General page of the
Options notebook, an ID will be pre-filled; you can change this ID if desired.
Step 4: (Optional) Enter a description, and the group the route belongs to. Enter a
reference number for the route, change the color of the route, and select a status
for the route.
Operations Guide
811
Creating a Route
Step 5: Click the Scenario arrow and select the routes scenario. The scenario could
affect the time windows and service time for the route. The Default is Delivery.
For more information on how scenarios will affect your route, see Working with
Scenarios.
Step 6: Choose the origin for the route by selecting the location type and entering the
ID. If you dont know the ID, enter as much as you know followed by an asterisk
(*), such as 12*, and click the [Query] button. Double-click the desired location
from the Locations list that appears.
Step 7: If the route returns to the depot or similar location, choose the destination
for the route by selecting its type and entering the ID. If you dont know the ID,
enter as much as you know followed by an asterisk (*), click the [Query] button,
and double-click the location.
If the last stop for a delivery or pickup is also the destination for the route
(rather than returning to the depot or another location), check the Last stop is
destination box instead of entering a destination.
Step 8: If either the origin or destination are part of a load, click the [Load Info] button
to enter load information.
Step 9: If necessary, change the planned Start time zone, date, and time, depart Planned
time, and the Complete time and time zone. The selected time zones are the ones
the Start, Depart, and Arrive and Complete times are displayed in. The Arrive
date and time are calculated for you by MobileCast based on the stops added to
the route.
Note: The Start time must occur before the Depart time; likewise the Arrive time must
occur before the Complete time. This allows the driver time to attend meetings,
check the load, or perform other tasks before leaving the depot or after returning
to the depot.
Step 10: (Optional) Click the Advanced tab and enter any user-defined information for
the route. To assign a pre- or post-route survey to the route, click either the PreRoute or Post-Route arrow and select the survey from the list that appears.
Note: To view the results of a survey once it has been completed, simply right-click on
the route, select Lookup, then Pre-Route or Post-Route Survey Results.
Step 11: When all of the necessary information is entered for the route, click the Save
icon or press [Ctrl]+[S]. Click the [Yes] button to verify that you want to create
the route.
Note: You can also add a route by clicking the Add Another icon from the Route
Properties notebook.
To enter stops for the new route, see Adding, Changing, Deleting, or Unassigning Stops
on a Route.
Dispatcher Routes New Save icon ([Ctrl]+[S]) Yes
812

Adding, Changing, Deleting, or Unassigning Stops on a Route

In MobileCast, you can add, remove, or change the stops on a route. For example, you
might need to change the planned order quantity on a stop for a customer who increases
an order, or you might add a stop for a pickup. If you are using wireless communication,
the route is automatically updated on the wireless device, and the driver receives a
message about the change.
Adding a Stop
For any reason, you can add additional delivery or pickup stops to a route. Adding a stop
to a route is an easy process that can be done anytime, even after a route has been started.
Step 2: Right-click on the route and select Properties from the menu that pops up. The
Route Properties notebook opens.
Routes are maintained

and changed from the
Route Properties
notebook. The left side
of the notebook shows
an overview of the route.
To see the stops on the
route, click the plus sign
next to the route.
Operations Guide
813
Step 3: Click the Add Detail icon. The Stop Type window opens. Select Stop (Normal)
and click [OK].
The Stop Type window not only
lets you add a stop, but also a
break, wait, layover, or depot.
The notebook changes to show Stop Information for the new stop.
A new stop is being added to the end of this route.
Step 4: In the Position area, select the appropriate place for the stop in the route (First,
Last, or After an existing stop) or let MobileCast determine the best place for the
stop (Auto).
Step 5: In the Location area, enter the type and ID for the stop. If you dont know the
exact ID, enter as much as you know followed by an asterisk (*), such as 12*,
and click the [Query] button. Double-click the desired location in the Locations
list that appears.
Step 6: (Optional) Select the time zone the times will be displayed in, and enter the
number of minutes the driver will spend at the stop in the Service field. If the stop
is part of a load, click the [Load Info] button to enter load information.
814

Step 7: (Optional) Enter any additional service time that may be needed for this stop.
The time must be entered in seconds. The service time entered here will be in
addition to the locations service time.
Step 8: Click the Calculate and Validate icon to have MobileCast compute the times
and distances for the stop being added.
Step 9: Click the Time Windows tab and enter the delivery window information. Each
time needs to have a date associated with it; you can enter the date yourself or
allow MobileCast to determine the date based on the planned route. To have
MobileCast determine the date, check Set delivery window dates based on plan.
Select the time zone the delivery windows are displayed in.
Step 10: (Optional) Click the Advanced tab and enter the information for shipper,
consignee, user-defined fields, instructions, driver alerts, and whether the stop
should be used when calculating the number of stops to bill/pay for. To assign a
survey to the stop, click the Stop Survey arrow and select the survey from the list
that appears.
Note: To view the results of a survey once it has been completed, simply right-click on
the stop and select Survey Results.
Step 11: For each additional stop, click the Add Another icon, then repeat Steps 4
through 10.
Step 12: When all of the necessary information is entered for the route, click the Save
icon or press [Ctrl]+[S], then click the [Yes] button to verify that you want to add
the stops.
Note: To enter order information for a stop, see Entering Order or Line Item Information.
Dispatcher Routes window Properties Add Detail Calculate and Validate Save
icon ([Ctrl]+[S]) Yes
Changing a Stop
At any time you can easily modify information associated with a stop on a particular
route. For example, you can change quantity, time window, shipper, and other
information as necessary. You can also choose to add/change instructions and driver
alerts.
Step 2: View the list of stops for the route:
From the Overview window, click the plus sign next to the route to expand it.
From a Route window, double-click the route to open a Stop for Route window.
From a route map, the stop should already be visible. If it is not, click the Fit icon
to resize the map.
Operations Guide
815
Step 3: Right-click on the stop, then click Properties from the pop-up menu to display
the Stop Properties notebook.
The planned and

projected arrival and
departure times are
calculated by
MobileCast.
Step 4: To change the time window information for this location on this route, click
on the Time Window tab. Enter the open/close time and time windows. Each time
needs to have a date associated with it; you can enter the date yourself or allow
MobileCast to determine the date based on the planned route. To have
Select the time zone the delivery windows should be displayed in.
Step 5: To change Advanced information for this location on this route, click the
Advanced tab and make the appropriate changes.
To change the location being processed at this stop, enter the type and ID in the
Location area. If you dont know the exact ID, enter as much as you know
followed by an asterisk (*) and click the [Query] button. Double-click the desired
location in the Locations list.
Notes: The location for a wait cannot be changed. If you need to change the waits
location, delete the existing wait, then add a new wait with the updated location.
You can change actual times for completed stops during the route only if the
option to Allow Override of Actuals During Routes is selected on the Dispatch General page of the Maintenance Options notebook.
Step 6: If you have made a change that affects times and distances for the route, click
the Calculate and Validate icon. Otherwise, the system will automatically
calculate the new times and distances when you save the route.
816

Step 7: When all of the necessary changes are made, click the Save icon or press
[Ctrl]+[S], then click the [Yes] button to verify that you want to save the changes
to the route.
Warning: If you decide against making a change, just click the Close box for the Stop
Properties notebook without clicking the Save icon. Do not click the Delete icon;
it will delete the stop from the route.
Note: Changes you make from the Stop Properties notebook affect only the stop on this
route; they do not permanently change the locations information.
Dispatcher Routes window Stop Properties (Calculate and Validate) Save icon
([Ctrl]+[S])Yes
Deleting a Stop
As long as a route has not yet been started, you can easily delete stops as necessary.
Deleting a stop removes it from the plan for the route. To remove a stop from the route,
so that it is not counted in the actual totals but remains in the planned information, cancel
the stop. Once the route has been started, the stop cannot be deleted; it must be cancelled.
You can, however, delete the stop once the route has been completed. For more
information, see Adding a Stop to a Route in MobileCast, and Changing a Stop on a Route
in MobileCast.
Step 2: Right-click on the route, then select Properties from the menu that pops up. The
Step 3: Click the plus sign next to the route in the overview area of the notebook to
expand the list of stops on the route.
Step 4: Click the stop you want to remove from the route.
Step 5: Click the Delete Stop icon.
Step 6: Click the [Yes] button to verify that you want to delete the stop.
Step 7: To make the deletion permanent, click the Save icon or press [Ctrl]+[S] and
click the [Yes] button to verify the change. If you click [No] at this point, the
deletion is not saved and the dialog box remains open.
Dispatcher Routes window Properties Stop Delete Yes Save icon
([Ctrl]+[S])Yes
Unassigning a Stop
There may be times when a stop needs to be removed from a route, but you want to keep
it for future use, allowing you to reassign it to another route. In these cases you can
unassign the stop, rather than deleting the stop, and use cancel stop codes to track why the
Operations Guide
817
stop was unassigned. Unassigning a stop removes it from the actual amounts for the route,
so it is not considered when billing and payroll reports are run, but leaves it in the planned
amounts. If you are using wireless communications and the dispatcher unassigns a stop,
a message is sent to the driver.
Note: Unassigning a stop does not cancel it permanently. The stop is placed on the
Unassigneds list so you can assign it to another route when necessary. For more
information on Unassigneds, see Working with Unassigneds.
Step 2: Find the route in the Overview window, route list, or view a route on a map. If
to resize the map.
Step 4: Select the stop(s) you want to unassign from the route. You can select multiple
stops by holding down the [Ctrl] key as you click them.
Step 5: Right-click on a selected stop and select Unassign from the menu that appears.
A dialog appears asking if you are sure you want to unassign the stop(s). Click
the [Yes] button.
Step 6: The Unassigning Stop window opens. elect a cancel stop code, if appropriate,
and click the [OK] button to confirm that you want to unassign the stop(s). The
stop(s) will be crossed out in the route list and automatically sent to the
Unassigneds list, making it available for re-assignment at a later time.
Notes: If you are unassigning multiple stops, they will all receive the same cancel stop
code.
The segment of the route containing the unassigned stop is removed from the map.
The unassigned stop is initially displayed as a cancelled stop and indicated by an
X in a box the same color as the route; when the map refreshes, this stop changes
to an unassigned.
For more information on unassigned stops, refer to Working with Unassigned
Stops.
Dispatcher Routes window Route Unassign [Yes]
818

Entering Order or Line Item Information

If the detail level has been set to either Order or Line Item on the Dispatch-Detail Level
page of the Maintenance Options notebook, you can add new orders to existing stops, or
new line items to existing orders. In addition, you can change existing orders or line items
for a stop. These changes are made in the Properties notebook. If you are using wireless
communication, the route is automatically updated on the wireless device, and the driver
receives a message about the change.
Adding a New Order or Line Item
MobileCast makes it easy to add order or line item information to existing stops, as
needed. If you are using wireless communication, when you add a new order or line item,
the information will be automatically updated on the wireless device; the driver can also
add a new order or line item from the wireless device.
From the Overview window or Route Properties notebook, click the plus sign
next to the route to expand it.
to resize the map.
Step 3: Right-click on the stop and select Properties from the menu that pops up. The
Stop Properties notebook opens.
Note: If accessing the stop from the Route Properties notebook, click on the stop to
switch to the Stop Properties notebook.
Step 4: To add an order, click the Add Detail icon from the Stop Properties notebook.
The notebook changes to show Order Information for the new stop.
To add a line item, double-click the stop to display its orders, click the desired
order, and click the Add Detail icon.
Step 5: Type the order or line-item number in the Order Number or Line Item field.
Step 6: (Optional) Fill in the Reference and User-Defined Fields text boxes with the
appropriate information.
Step 7: (Optional) Enter any special instructions for the order or line item.
Step 8: Click the Quantities tab and fill in the appropriate planned quantities to deliver
and/or pick up.
Step 9: If you are tracking containers, click on the Containers tab.
If you know the containers ID, enter it in the ID field. If you are using container
types, select the appropriate type.
Operations Guide
819
If you dont know the containers ID, choose the correct search option and click
the Execute Query Using Criteria icon; all containers that match the query will be
listed in the Available Containers list. Click on the desired container(s).
In the Service Type section, click in the appropriate circle to select whether the
order is a delivery being dropped off, a delivery being returned, or a pickup. Click
the [Add] button; the selected containers are moved to the Container(s) Assigned
to the Order list.
A new order is about to

be added to this stop.
MobileCast will use
whatever is typed in the
Order Number field as
the orders name.
Notes: If Use Container as Barcode is selected on the Dispatcher-Detail Level page of the
Maintenance Options notebook the container ID will automatically be entered as
the barcode.
To change the service type for an assigned container(s), select the containers in
the Container(s) Assigned to the Order list and the new service type, then click the
[Update] button.
Step 10: If you are tracking an orders financial information, click on the Financial
Details tab.
820

To add a financial detail, click the Add icon. The Add Financial Details window
opens. Click on the arrow and select the financial code.
The dispatcher can add, edit, or

delete any financial detail
associated with an order.
In the Amount field, enter the amount, in dollars and cents, associated with the
financial code. For example, if you adding a charge for this order, then enter the
amount of money the customer will be responsible for paying.
Note: If you are adding an adjustment, such as a coupon for $10.00, then you will need
to enter -10.00 as the amount.
In the ID field, enter the identification number associated with the code. For
example, if you are adding a charge for this order, and the customer will be paying
with a credit card, then enter the credit card number.
In the Date field, click on the arrow to select the date associated with the financial
detail you are adding. This date can be the date the financial detail was added, or,
if you are adding a charge for this order, and the customer will be paying with a
credit card, then this field can be used to enter the expiration date of the card.
Note: You can either enter the date manually, or click on the arrow to open a calendar.
To change the month, either use the arrows on the top of the calendar to scroll
through the months, or click on the month and select from the menu that pops up.
To change the year, click on the year and use the arrows to scroll to the correct
year. Click on a date to select it.
In the Description field, enter the description associated with the financial detail
you are adding. If you are adding a charge for this order, and the customer will be
paying with a credit card, then this field can be used to enter the card type, such
as VISA, MasterCard, or Discover.
Click the Save icon, or press [Ctrl]+[S] to save the information. Youll be returned
to the Financial Detail tab, and the Debits, Adjustments, Charges, and Balance
fields will be adjusted to match the detail information youve added.
Notes: When you add, edit, or delete information on the Order Financial Detail tab,
MobileCast will automatically recalculate the financial information for you.
For more information about order financial codes, see Working with Order
Financial Detail Codes.
Operations Guide
821
To view a stops order financial details, right-click on the stop and select Order
Financial Details from the menu that opens. The Order Financial Details window
opens, displaying all financial details for the stop.
Step 11: If there is an activity associated with the order, click the Activities tab.
To add an activity to this order, click the Add icon. The Add Order Activities
window opens.
The dispatcher can add, edit, or delete

any activity associated with an order.
Click the Activity arrow; the Lookup-Activity window opens. Double-click an

activity, or click on the activity and then on the Process icon, to select it. If there
is a description associated with this activity, then it will be displayed in the
Activity Description field.
If a route has wireless communications available, then the routes order activities
will be marked as complete by the driver using the wireless device. If a route does
not use wireless communication, then you will need to manually mark the order
activity as complete.
Click the Save icon, or press [Ctrl]+[S] to save the information. Youll be returned
to the Activities tab, and the activity you just added will be displayed in the list.
For more information about order activities, see Working with Activities.
Note: To view a stops order activities, right-click on the stop and select Order Activities
from the menu that opens. The Order Activities window opens, displaying all
order activities for the stop.
Step 12: (Optional) To add another order or line item, click the Add Another icon and
repeat Steps 4 through 9.
Step 13: When all of the necessary information is entered for the order(s) or line
item(s), click the Save icon or press [Ctrl]+[S], then click the [Yes] button to
verify that you want to create the item(s).
DispatcherRoutes window Stop Properties Add Detail Save icon ([Ctrl]+[S])
Yes]
Changing or Deleting an Order or Line Item
At any time you can easily change or delete an order or line item on a route. If you are
using wireless communication, any changes you make will automatically be updated on
822

the wireless device. Similarly, a driver can also change or delete an order or line item from
the wireless device.
Note: When you add, edit, or delete information on the Order Financial Detail tab,
MobileCast will automatically recalculate the financial information for you.
Step 1: If necessary, click the Dispatching icon to open the Dispatcher module. If
Step 2: View the list of stops for the route.
From the Overview window, click the plus sign for the route to expand it.
to resize the map.
Step 3: Right-click on the stop, then click Properties from the menu.
Step 4: To work with an order, double-click the stop to display its orders, then click
the desired order.
To work with a line item, double-click the stop to display its orders, double-click
the order to display its line items, then click the desired line item.
Step 5: To change an order or line item, edit the contents of the Reference, User
Defined Fields, Containers, Quantities, or Order Financial Detail areas as
necessary.
To delete an order or line item, make sure you have the correct one selected on
the left side of the notebook, then click the Delete Stop icon. Click the [Yes]
button to verify the deletion.
Step 6: Click the Save icon, or press [Ctrl]+[S] to save the information, then click the
[Yes] button to verify that you want to make the change permanent for the route.
Dispatcher Routes window Stop Properties Change/Delete Save icon ([Ctrl]+[S])
[Yes]
Processing an Order or Line Item
Normally, the planned quantities for a delivery or pickup automatically become the actual
quantities. Sometimes, though, you might need to enter the actual quantities manually.
You can do this when you complete a stop, or you can do it from the Stop Notebook.
From a Route window, double-click the route.
to resize the map.
Operations Guide
823
Step 3: Right-click on the stop with the item you want to process and select Properties
from the menu that pops up. The Stop Properties notebook opens.
Step 4: To process an order, double-click the stop to display its orders, then click the
desired order.
To process a line item, double-click the stop to display its orders, double-click
the order to display its line items, then click the desired line item.
Step 5: Click the Quantities tab, then click its Actual tab and change the actual
quantities. If you are using reason codes, click the appropriate [Reason Codes]
button and select the appropriate reason code.
Step 6: Click the Save icon, or press [Ctrl]+[S] to save the information, then click the
[Yes] button to verify that you want to make the change.
Note: If your quantities are ratios of each other (set in the Options notebook of the
Maintenance module), only the first quantities box will be available for
processing. MobileCast automatically calculates the equivalent amounts for the
other two.
Dispatcher Routes window Stop Order Line Item (optional) Properties
Change/Delete Save icon ([Ctrl]+[S]) Yes]
824


There may be times when you need to add a break, wait, layover, or mid-route depot to a
route, allowing the driver to have a scheduled lunch, to meet a locations time window, or
to perform an unload or reload during the course of a route. You can have the
Transportation Suite automatically assign breaks, waits, or layovers when the route is
created, or you can assign them manually in the Dispatcher. You can add a break after a
stop, a wait before a stop, or a layover after a stop. All breaks, waits, and layovers can
either be paid or unpaid. All breaks, waits, or layovers that are paid are considered when
the total time for the route is calculated. Breaks are displayed in the Stop Type column of
the Stops window as a coffee cup; waits are displayed as a clock; and layovers are
displayed as a bed. If the break, wait, or layover is paid, a dollar sign is added to the stop
type. The table below gives you an example of each icon:
Icon
Meaning
Icon
Meaning
Icon
Meaning
Break
Layover
Wait
Paid Break
Paid Layover
Paid Wait
If you are using wireless communication and the dispatcher adds a break, wait, layover,
or mid-route depot, a message is sent to the driver; likewise, if the driver adds any, the
route is updated in the Dispatcher.
Notes: When you transfer stops to a different route, all waits are deleted from both routes.
For more information on transferring stops, see Transferring Stops between
Routes.
When you resequence stops, all breaks and waits that havent yet occurred on the
route are deleted. For more information on resequencing stops, see Changing the
Order of Stops on a Route.
Step 2: Right-click on the route and select Properties from the menu that pops up. The
Step 3: Click on the Add Detail icon. The Stop Type window opens. Select Break/Wait/
Layover and click [OK].
Breaks, waits, and layovers each have a unique
graphic in the Stop Type column so that you can
easily determine what kind of stop it is. A dollar
sign indicates that the break/wait/layover is paid.
Operations Guide
825
Note: In order to add breaks, waits, and layovers, you must check Allow Additional Stop
Types on the Dispatch - General page of the Maintenance Options notebook.
Step 4: The notebook changes to show the Break/Wait/Layover information. Click the
Type arrow to select what you want to add: Break, Wait, or Layover.
Step 5: Select First, Last, or After in the Position section. If you choose After, click on
the arrow and select the stop that you want the break/wait/layover to follow.
Note: If you are adding a wait, then your options in the Position section are First and
Before since a wait is always associated with the stop it precedes. MobileCast does
not allow a wait to be added to a route with no stops.
From the Route Properties notebook, you can easily add a

break, wait, or layover.
Step 6: (Optional) In the Location area, enter the type and ID for the stop. If you dont
know the exact ID, enter as much as you know followed by an asterisk (*), such
as 12*, and click the [Query] button. Double-click the desired location in the
Locations list that appears.
If a location is not selected, the longitude/latitude from the previous stop (break
and layover) or the longitude/latitude for the next stop (wait) will be used.
Step 7: Select the time zone the times will be displayed in, and enter the length of time
(in minutes) for the break/wait/layover in the Duration field.
826

Note: The actual duration of the drivers wait may change from the length entered here;
the duration of the wait displayed on the wireless device will change as necessary
for the driver to arrive at the stop at the planned arrival time.
Step 9: For each additional break/wait/layover, click the Add Detail icon, then repeat
Steps 4 through 8.
Step 10: When you are finished adding breaks/waits/layovers, click the Save icon or
press [Ctrl]+[S], then click the [Yes] button to verify that you want to save the
route.
Notes: Editing and deleting breaks, waits, or layovers in the Route Properties Notebook
is similar to editing or deleting a stop. However, when editing a wait, the location
cannot be changed. For more information on editing and deleting a break, wait, or
layover, see Changing a Stop or Deleting a Stop.
When looking at a break/wait/layover in the Route Overview window or the Route
Properties notebook, the duration that is displayed is the difference between the
departure and arrival times. These times are computed by MobileCast depending
on the status of the break/wait/layover; if actual times are available (i.e. the driver
has arrived at and/or departed from the stop) these times will be used. When no
actual times are available, the projected time is used.
Dispatcher Routes window Properties Add Detail iconStop Type [OK] Save
Operations Guide
827
Inserting a Mid-Route Depot

There may be times when a driver needs to stop at another depot during a route, maybe
because the original depot doesnt have a certain product on hand, or another order came
in during the day, or you need to reload or unload because of a delivery/pickup. To
provide for these circumstances, you can insert depots onto your routes. Once the depot
has been inserted onto the route, it appears in the Stop list and on the map. If you decide
to resequence the route, the mid-route depot will be treated like a normal stop and placed
in the best spot on the route.
Step 2: Right-click on the route and select Properties. The Route Properties notebook
opens.
Step 3: Click on the Add Detail icon. The Stop Type window opens. Select Mid-Route
Depot and click [OK].
Note: In order to add mid-route depots, you must check Allow Additional Stop Types on
the Dispatch - General page of the Maintenance Options notebook.
Once inserted, the mid-route depot will
appear on your route with a depot icon
next to it.
Step 4: You are returned to the Route Properties notebook with the Mid-Route Depot
information showing. At this point, you need to decide where on the route you
want the depot to be placed. Select First, Last, or After in the Position section. If
you choose After, click the drop-down arrow and select the stop that you want the
depot to follow.
828

When you insert a mid-route

depot onto a route, you can
set the length of time the
driver needs at the depot in
the Additional Service Time
field.
Note: If you want MobileCast to insert the depot onto your route for you, select Auto.
MobileCast will then place the depot on the route in the most cost-efficient spot.
list that appears.
Step 6: Select the time zone the times will be displayed in, and enter any additional
time, in seconds, that the driver will spend at the depot in the Additional Service
Time field.
Step 7: For each additional mid-route depot, click the Add Detail icon, then repeat
Steps 4 through 7.
Step 8: When you are finished, click the Save icon, or press [Ctrl]+[S] to save the
information, then click the [Yes] button to verify that you want to save the route.
Note: Editing and deleting a mid-route depot in the Route Properties Notebook is similar
to editing or deleting a stop. For more information, see Changing a Stop or
Deleting a Stop.
Dispatcher Routes window Properties Add Detail iconStop Type [OK] Save
Operations Guide
829
Working with Unassigned Stops

You can easily add an unassigned stop to a new or existing route. Once the unassigned
has been created, by adding, importing, or even unassigning a stop from a route, you can
modify and assign it to any route, even if the route is already in progress.
If your unassigned stops were not imported during the daily import, you can import them
separately. This import will download all the unassigneds for that day. For more
information, see Importing Daily Route Information for MobileCast.
Note: Some of the following procedures described below can be done using the map;
therefore, make sure that Show Unassigneds is set on the User tab of the Map
Properties Notebook. If you do not have this option checked, then you wont be
able to see any unassigned stops on the map.
Assigning Unassigned Stops to a Route
You can tell MobileCast precisely where you want to place the unassigned stop on a route;
you can let MobileCast help you by having the program suggest the best route for the
unassigned stop; or you can combine an unassigned stop with an existing stop if they have
the same delivery location.
Step 2: On the menu bar, click List, then Unassigneds. The Unassigneds window
opens.
The Unassigned list window provides detailed information on all

unassigned stops.
Step 3: Find the route in the Overview window, route list, or view a route on a map. If
830

to resize the map.
Step 5: To tell MobileCast precisely where you want to place the unassigned stop
on a route, see Manually Assigning an Unassigned Stop.
To let MobileCast help you by having the program suggest the best route for
the unassigned stop, see Letting MobileCast Determine the Best Route.
To combine an unassigned stop with an existing stop that has the same
location, see Combining Unassigned Stops to Existing Stops.
Hint: You can use the Search Manager, sort on any column(s), and use the other features
of list windows to help you group or find unassigneds. See Arranging List and
Maintenance Windows for more information.
To manually assign an unassigned:
Step 1: From the Unassigned window, select the unassigned stop(s) you want to assign
to a route. You can select multiple stops by holding down the [Ctrl] key as you
click them. Then, click and drag the unassigned to the route either in the Stop
window or map. Be certain that you drag the unassigned stop(s) to the spot after
the stop you want it to follow. The Place Unassigned window opens, showing you
where on the route the unassigned has been placed.
Hint: To automatically place the unassigned on the route according to best distance, drag
the stop to the map and drop it on the depot, or on the route between the depot and
the first stop.
Use the Place Unassigned window to preview the unassigned

stop on a route.
Step 2: If you are satisfied with this positioning, click the Save icon, or press
[Ctrl]+[S] to save the information.
OR
Operations Guide
831
If you are not satisfied with the positioning, in the Place Unassigned window
drag the unassigned stop(s) to the desired slot on the route, then click the Save
icon.
The unassigned stop(s) have now been assigned to your route and removed from
the Unassigned list.
Note: The Planned Route Return and Projected Route Return times are shown in the
users time zone.
Dispatcher List Unassigneds Place Unassigned Save icon ([Ctrl]+[S])
Letting MobileCast Determine the Best Route
To prevent MobileCast from overcapacitizing a route by adding an unassigned, make sure

Route Capacity Checking is selected for the appropriate size(s) on the Dispatch - General
page of the Maintenance Options notebook. If this option is selected, MobileCast will not
even suggest routes where adding the unassigned would cause the equipment to be overcapacitized.
To have MobileCast automatically assign the best route for the unassigned stop:
You can set up the criteria in the Maintenance module in order to have MobileCast
constantly and dynamically assign unassigned stops to routes. The options are similar to
the options available for manual suggest route process. Once you have the options
selected, MobileCast will continually assess the unassigneds throughout the day and
assign them to the best possible route. By using this feature, your dispatcher does not need
to take the time during the day as orders are coming in to place them on routes. See Setting
the MobileCast Continuous Optimization for more information.
To have MobileCast suggest the best route for the unassigned stop:
Step 1: From the Unassigned window, right-click select the unassigned stop(s) you want
to assign to a route and select Suggest from the menu that pops up. You can select
multiple stops by holding down the [Ctrl] key as you click them. The Suggest
Route window opens with the ID and description of the first unassigned stop
displayed.
Step 2: In the Best Route Criteria area, select whether you want to route the unassigned
based on the least distance added to the route (Best Distance), the least time
added to the route (Best Time) or the maximum number of stops making their
time windows (Best Time Window).
Step 3: If you chose Best Time Window, select the appropriate options in the Time
Window Options box:
Make Allcheck to only have routes suggested where all the stops make their
time windows. If this option is selected, it is possible that the unassigned cannot
be added to a route without stops missing time windows, so no routes will be
suggested.
Adjust Minimum Start Timecheck if MobileCast can adjust the routes start
time to allow more stops to make their time windows.
832

Minimum Route Start Timechoose the earliest start date and time MobileCast
can select.
Adjust Start Time Incremententer the increments to adjust the start time in
(ex 15 minutes).
Hint: The combination of adjusting the Minimum Route Start Time much earlier and
having Adjust Start Increment a small number (such as 1 minute) can cause
Suggest Route to take a long time to run.
Step 4: Enter the maximum number of routes you want to choose from in the
Maximum Number of Routes to Return field. This means that if you enter the
number 10, then MobileCast will suggest the 10 best routes to place the
unassigned stop.
Operations Guide
833
Note: If you selected RouteNet on the Dispatch - General page of the Maintenance
Options notebook, and you entered a high number of routes youd like to see when
MobileCast suggests a route, then the system results could slow dramatically.
The Suggest Route window takes the guess-work out of assigning

unassigned stops. Simply enter in the information and MobileCast will
suggest the best route for the unassigned stop.
Step 5: To only suggest routes that do not exceed a specified number of stops, check
Maximum Stops Per Route. Enter the maximum number of stops allowed per
route below. Only routes that will not exceed this number if this stop or
unassigned is added will be suggested.
Step 6: To suggest routes whose runtime will not be exceeded if the unassigned is
added, check Maximum Runtime. Enter the maximum duration of the route
below. Any route whose runtime would be exceeded by adding the unassigned
will not be suggested.
Step 7: If you are using skill sets, and would like them to be considered when
suggesting the best route, then check Consider Skill Sets. If this option is
834

selected, only routes with a driver assigned a skill set that allows them to
complete the orders activities will be suggested. For information about skill sets,
see Working with Skill Sets.
Step 8: To limit the suggested routes to those where no duty period rules will be
violated if the stop is added, check Filter out Duty Period Violations. Duty period
rules regulate the length of time that drivers can work and are used to help your
organization comply with safety and labor laws. You must have duty period rules
enabled on the Duty Period Monitor page of the Maintenance Options notebook
for this option to be available.
Step 9: To only suggest routes that are assigned an equipment type not restricted by the
unassigned, check Enforce Equipment Type Restrictions.
Step 10: To suggest placing this unassigned as the next stop on a route that is currently
in transit, check Consider Before Next Arrival. In Minutes Before Next, enter the
minimum number of minutes before the projected arrival at the next stop for this
placement to be considered. Positions on routes that are currently in transit and
have at least this much time before the next scheduled stop or the depot will be
suggested.
Notes: If the next stop on a current route is not eligible, the remainder of the route will
still be analyzed according to the other options selected on the Suggest Routes
window.
This function only applies to current routes that are Not Completed. If either Not
Started or Not Departed Origin is selected under Include Only Routes That Are,
Consider Before Next Arrival is not available.
If Minutes Before Next is set to 0, the unassigned stop will be suggested before
the next stop on the route, regardless of the next stops projected arrival time.
Step 11: In the Include only routes that are: area select which routes to include. You can
choose to include all routes that are Not Completed, only routes that have not
begun (Not Started), or only routes that have started but not left the depot (Not
Departed Origin).
Step 12: To suggest only routes that have the current date as the planned start date,
check Todays Routes.
Step 13: Click the [Suggest] button. MobileCast displays the best routes in the list. For
each route, the time and distance the unassigned stop add to the route is shown,
along with the placement of the unassigned stop on the route and other pertinent
information. Use this information to decide which would be the best route for the
unassigned stop.
Warning: Since all of the routes in the database cannot be locked while running the
suggest a route process, another user may make a change to a route while your
request is being processed. If this happens, then you will be asked to rerun the
process. Simply click [OK] and you are taken directly to the Suggest Route
window.
Operations Guide
835
Note: If the stop contains part of an order pair, the route containing the other part of the
order pair will be the only route suggested.
Step 14: Click on the route you want to place the unassigned stop, and then click
[Accept], the [Yes] to confirm adding the stop to the route. If you selected
multiple unassigneds to route, the Suggest Route window moves to the next
selected unassigned.
Dispatcher List Unassigneds Suggest Suggest [Accept][OK]
Combining Unassigned Stops to Existing Stops in MobileCast
To combine an unassigned with an existing stop that has the same delivery location,
follow the steps below.
Step 1: From the Unassigned window, left-click on the unassigned stop you want to
assign, and then drag the unassigned stop onto the stop that has the same delivery
location.
Step 2: From the pop-up menu, select either Combine or Add Stop.
If an Unassigned and an existing stop have the same delivery location, you can
combine the two or create a new stop for the Unassigned.
Note: MobileCast does not allow you to combine an unassigned stop with a cancelled
stop. If an unassigned stop is dragged onto a cancelled stop, the pop-up menu will
not appear.
If you decide to combine the unassigned and the existing stop, the entire
unassigned will be placed onto the stop, meaning all order/line item/container
information will be merged onto the existing stop. The Place Unassigned window
opens, showing you that the unassigned has been combined with the existing stop.
836

If you decide to add the unassigned as a new stop on the route, the Place
Unassigned window opens, showing you where on the route the unassigned has
been placed. If you are satisfied with this positioning, click the Save icon.
If you are not satisfied with the positioning, in the Place Unassigned window drag
the unassigned to the desired slot on the route, then click the Save icon.
The unassigned has now become an assigned stop on your route and is removed
from the Unassigned list.
Note: To cancel the placement of the Unassigneds onto the route, click the Close box
(X); the Place Unassigned window will close, and you are returned to the
Unassigned list.
Dispatcher List Unassigneds Combine/Add Stop Place Unassigned Save icon
([Ctrl]+[S])
Locating Unassigned Stops on a Map
You can view an unassigned stop on the same map you view your routes, allowing you to
see the unassigneds position plus helping you determine what route you may want the
unassigned stop to be assigned to.
Note: For more information on using maps in MobileCast, refer to the Maps and
RouteNet section.
opens.
The Unassigned list window provides detailed information on all unassigned stops.
Step 3: If necessary, open a Map window. For example, from the menu bar, click View,
then Map.
Operations Guide
837
Step 4: Left-click on an unassigned stop and drag it onto the map. The location of the
unassigned is displayed on the map.
Use the map to locate an unassigned stops exact location.
Notes: To view more than one unassigned stop on the map, press [Ctrl] and click on the
Unassigneds you want to view, then drag the unassigneds to the map. The
locations of the unassigneds are displayed on the map. The map will zoom in or
out, depending on whats necessary to view all the unassigned stops at once.
While viewing an unassigned stop on the map, you can let MobileCast suggest
the best possible route to place the unassigned stop by right-clicking on the
unassigned and selecting Suggest from the menu that appears. For more
information, see Letting MobileCast Determine the Best Route.
Adding and Editing Unassigned Stops
There might be times when it is necessary to create an unassigned stop; MobileCast makes
this process easy. Also, you are able to edit these unassigneds, as needed. If you are using
wireless communication, the route is automatically updated on the wireless device, and
the driver receives a message about the change.
838

opens.
The Unassigned list window provides detailed information on all unassigneds.
Step 3: To add an unassigned stop to the list, click the Add icon.The Unassigned
window opens.
OR
To edit an existing unassigned stop, right-click on an unassigned and select
Properties. The Unassigned window opens.
Use the Unassigned

window to add or edit an
unassigned stop.
Operations Guide
839
Note: You can also edit an unassigned stop from the map window. If you are viewing
the unassigned on a map, simply right-click on the unassigned stop and select
Properties. The Unassigned window opens.
list that appears.
Step 5: (Optional) Select the time zone the times will be displayed in.
Step 6: Enter the default service time for the location, in minutes.
Step 7: Click the Time Windows tab and enter the delivery window information. Each
time needs to have a date associated with it; you can enter the date yourself or
allow MobileCast to determine the date based on the planned route. To have
Select the time zone the delivery windows are displayed in.
Step 8: (Optional) Click the Advanced tab and enter the information for shipper,
consignee, user-defined fields, instructions, driver alerts, and whether the stop
should be used when calculating the number of stops to bill/pay for.
Step 9: To add order information, click the Add Detail icon. The Unassigned window
opens in add detail mode.
840

To edit order information, click the plus sign to expand the stop and select the
order you want to change. The Unassigned window opens in edit mode.
The Unassigned window

is used to modify or add as
many orders/line items/
containers as you need for
the Unassigned.
Step 10: If applicable, type the order number in the Order Number field.
Step 11: (Optional) Enter the Reference and User-Defined Fields text boxes with the
appropriate information.
Step 12: Click the Quantities tab and fill in the appropriate planned quantities to deliver
and/or pick up.
OR
If you are tracking containers, click on the Containers tab.
If you know the containers ID, enter it in the ID field. If you are using container
types, select the appropriate type.
If you dont know the containers ID, choose the correct search option and click
the Execute Query Using Criteria icon; all containers that match the query will be
listed in the Available Containers list. Click on the desired container(s).
In the Service Type section, click in the appropriate circle to select whether the
order is a delivery being dropped off, a delivery being returned, or a pickup. Click
the [Add] button; the selected containers are moved to the Container(s) Assigned
to the Order list.
Operations Guide
841
Notes: If Use Container as Barcode is selected on the Dispatcher-Detail Level page of the
Maintenance Options notebook the container ID will automatically be entered as
the barcode.
To change the service type for an assigned container(s), select the containers in
the Container(s) Assigned to the Order list and the new service type, then click the
[Update] button.
Step 13: When all of the necessary information is entered for the stop, click the Save
icon or press [Ctrl]+[S], then click the [Yes] button to verify that you want to
save.
Dispatcher List Unassigneds Add Add Detail Save icon ([Ctrl]+[S])
OR
Dispatcher List Unassigneds Properties Save icon ([Ctrl]+[S])
Deleting Unassigned Stops
There might be times when it is necessary to delete an unassigned stop from list;
MobileCast makes this process easy.
opens.
The Unassigned list window provides detailed information on all Unassigneds.
Step 3: To delete an unassigned stop, select the unassigned stop from the Unassigned
list and click the Delete icon.
To delete an unassigned order, right-click on the unassigned stop that you want
to delete the order from, and select Properties. From the Unassigned Properties
window, click the plus sign to expand the stop and select the order you want to
delete. Click the Delete Stop icon.
Dispatcher List Unassigneds Delete Save icon ([Ctrl]+[S])
OR
842

Dispatcher List Unassigneds Properties Delete Save icon ([Ctrl]+[S])
Operations Guide
843
Changing the Order of Stops on a Route

There might be times when you need to change the order of the stops on a route, either to
accommodate a customers special request or because of a problem the driver encountered
during the route. If you are using wireless communication, the route is automatically
updated on the wireless device, and the driver receives a message about the change. The
driver can also resequence stops on the wireless device. For more information, see
Transferring Stops between Routes or Cancelling a Stop.
Note: When you resequence stops, all breaks and waits that havent yet occurred are
deleted. For more information on waits, see Adding Breaks, Waits, and Layovers.
Step 2: Right-click on the route and select Stop Sequence from the menu that pops up.
The Stop Sequence window opens.
The Stop Sequence window shows the current order of the stops in the
Actual Stop column, and the original order in the Planned Stop
column.
Step 3: To have MobileCast automatically resequence the remaining undelivered

stops, and find the best order based on travel time and distance, click the [Auto]
button. If you have a mid-route depot on your route, then it will get resequenced
and be placed in the best spot on the route.
To manually resequence, click on the stop you want to move. Hold down the
mouse button and drag the stop to the one that should precede it. For example, if
it should be after a stop named Quickie Mart, drag it to Quickie Mart. If it
should be the first stop, drag it immediately below the column heading. When you
release the mouse button, the stop is moved.
Step 4: Continue resequencing the stops as desired. New times and distances will be
computed for the changed stops based on the current travel calculator.
To change the model used to calculate travel time and distance, click the
[Configure Calculator] button and select the desired model. When changes are
844

made, or the [Calculate] or [Auto] button is clicked, the travel times and distances
will be calculated using the new model. This option is only valid if the XY method
was selected in the Maintenance module; it is not applicable to the SuperMatrix
or RouteNet.
Step 5: When you have made all the necessary changes, click the Save icon or press
[Ctrl]+[S]. The Stop Sequence window closes.
Notes: You cannot resequence stops that have already been completed.
To undo a resequencing, drag the stops back to their proper order using the
information in the Planned Stop column.
If you resequence stops before the route is started, the planned and actual stop
numbers will always match. Refer to the locations name or ID to guide you in
moving the stops.
Resequenced routes have a checkmark in the Sequenced box of Route windows.
All times are shown in the users time zone, with the exception of the drivers
times, which are shown using the drivers time zone.
Dispatcher Routes window Stop Sequence Save icon ([Ctrl]+[S])
Operations Guide
845
Transferring Stops between Routes

MobileCast makes it easy for you to transfer stops between any two routes that are not
completed. You can manually transfer stops or you can have MobileCast automatically
transfer the stops for you. If you are using wireless communication, both routes are
automatically updated on the wireless devices and messages are sent to alert the drivers.
For more information, see Changing or Deleting an Order or Line Item or Cancelling a
Stop.
Note: When you transfer stops to a different route, all waits are deleted from both routes.
For more information about waits, see Adding Breaks, Waits, and Layovers.
To prevent MobileCast from over-capacitizing a route when transferring stops, make sure
Route Capacity Checking is selected for the appropriate size(s) on the Dispatch - General
page of the Maintenance Options notebook. If this option is selected, MobileCast will
warn you if transferring the stop will cause the equipment to be over-capacitized. To have
MobileCast automatically transfer stops to other routes:
You can set up the criteria in the Maintenance module in order to have MobileCast
constantly and dynamically reassign stops to other routes that best meets the criteria. Once
you have the options selected, MobileCast will continually assess the routes and if current
routes exceed the specified guidelines, then stops would be transferred to another route.
See Setting the MobileCast Continuous Optimization for more information.
Note: You cannot transfer stops from a map window because on a map you work with
routes individually. Transferring stops requires you to work with two routes at
once.
Step 2: Select the two routes involved in the transferand only those two routes. To
select, click on the first route, then hold down the [Ctrl] key and click on the
second route.
846

Step 3: Right-click on either of the routes and select Transfer Stops from the menu that
pops up. The Stop Transfer window opens.
The Stop Transfer window

lists the stops planned and
actual information, along
with other information, for
both routes involved in the
stop transfer.
Step 4: Click on the stop to be transferred. Holding down the mouse button, drag the
stop to the other route, on the stop that should precede it. If the stop you are
moving should be the first stop on the other route, drag it immediately below the
routes column heading. The projected times for both routes are updated.
To have MobileCast resequence the stops on either route based on travel time
and distance, click the [Auto] button for the route. The stops are resequenced,
considering any stops that were transferred.
To manually resequence the stops on either route, click on the stop and drag it
to the desired order on the route.
Step 5: Continue transferring stops as necessary. New times and distances will be
computed for the changed stops based on the current travel calculator.
To change the model used to calculate travel time and distance, click the
[Configure Calculator] button and select the desired model. When changes are
made, or the [Calculate] or [Auto] button is clicked, the travel times and distances
will be calculated using the new model. This option is only valid if the XY method
was selected in the Maintenance module; it is not applicable to SuperMatrix or
RouteNet.
Step 6: When all the stops have been transferred, click the Save icon or press
[Ctrl]+[S]. The Transfer Stop window closes.
Dispatcher Two Routes Stop Transfer Save icon ([Ctrl]+[S])
Operations Guide
847
Cancelling a Stop
Cancelling a Stop
There may be times when a stop needs to be removed from a route, but you want to keep
it in the routes plan, such as to track a location that continually cancels their order or
changes it to another day. In these cases you can cancel the stop, rather than deleting the
stop, and use cancel stop codes to track why the stop was cancelled. Canceling a stop
removes it from the actual amounts for the route, so it is not considered when billing and
payroll reports are run, but leaves it in the planned amounts. To remove a stop from the
plan, see Adding, Changing, Deleting, or Unassigning Stops on a Route. If the dispatcher
cancels the stop, a message is sent to the driver; likewise, if the driver cancels a stop, it
appears as cancelled to the dispatcher.
Note: If you want a stop to be available for future use, use the Unassign feature instead.
For more information, see Unassigning a Stop.
From a Route window, double-click on the route to open a Stops for Route
window.
From a route map, the stop should be visible. If it is not, click the Fit icon to
resize the map.
Step 3: Right-click on the stop(s) and select Cancel from the menu that pops up. You
can select multiple stops by holding down the [Ctrl] key as you click them. The
Cancel Stop Code window appears.
Step 4: Click the Cancel Code arrow and select the proper cancel stop code.
Note: If you are cancelling multiple stops, they will all receive the same cancel stop
code.
Step 5: Click the [Yes] button to confirm that you want to cancel the stop(s). The
stop(s) will automatically be sent to the bottom of the list, with a line through it to
indicate that it is cancelled.
Note: The segment of the route containing the cancelled stop is removed from the map,
and the cancelled stop is indicated by an X in a box the same color as the route.
Dispatcher Routes window Route Stop Cancel [Yes]
848

Creating a Static Route
Creating a Static Route

If you have a new or changed route that you want to reuse on other days, you can add it
to a static route set. By making the route part of a static route set, you can import it when
needed instead of creating it each time.
Note: To make a route part of a static route set, the static route set must already exist.
Static route sets are created in the Static Routes module. For more information on
static route sets, see Working.
Step 2: Right-click on the route and select Create as Static from the menu that pops up.
The Static Route Sets window opens.
Step 3: Click the route set the route should be added to, then click the Process icon. The
route is added to the set.
Dispatcher Routes window Route Create as Static Process
Operations Guide
849
Working with Notes
Working with Notes

The ability to send and receive notes is an important part in the communication between
dispatchers, drivers, and MobileCast users. Notes are particularly helpful in a wireless
environment and where there are multiple dispatchers. In addition, drivers can send notes
with pictures attached, which can be helpful in supporting proof of delivery or verifying
the quality of an item or location.
Route notes are notes that are specific to the route. Not only can the dispatcher leave a
note about the route for the next shift, they can alert drivers to conditions on the road, and
drivers can send notes about the truck or traffic to the dispatcher.
Item notes are notes that are specific to a stop, order, or line item. Drivers can create and
send item notes to alert you to the condition of a product that is being picked up or take a
picture of the Closed for the Afternoon sign on the door as proof of an attempted
delivery. Stop, order, and line item notes can be added by the dispatcher, but they cannot
be sent to the driver or other users.
User notes are used to send messages between MobileCast users, and to display non-fatal
system exception notifications, such as database exceptions, route loading errors, and
notifications if the critical minutes for a given location has been exceeded. User notes are
not specific to a route and can be entered manually or generated by the system.
MobileCast allows the dispatcher to send route notes and receive route and item notes.
The driver can create and send notes at all levels of detail: route, stop, order, and line item,
but not user notes. Although the dispatcher can create notes at stop, order, and line item
level, they cannot be sent to the wireless device.
Creating Route and Item Notes
MobileCast lets you create and share notes that are unique to a route, order, stop, or line
item. Sharing information with other dispatchers or drivers is helpful in alerting a driver
to a traffic jam on the route, notifying the dispatcher of an unexpected delivery problem,
leaving notes for the next shift dispatcher, even verifying the condition of an item that is
picked up from a customer. Route notes are specific to a route and can be shared with
other dispatchers or a driver. Item notes are specific to a stop, order, or line item. Item
notes that are created by the dispatcher cannot be sent to the driver, but drivers can send
item notes to the dispatcher. Notes are particularly helpful in a wireless environment and
where there are multiple dispatchers.
Notes: Route notes are carried along with the data for the route, stops, orders, and line
items, but must be viewed in a separate Notes window instead of the list windows.
User-defined fields are also carried along with the data, but can be viewed from a
route or stop window. See Completing User-Defined Fields for more information.
Only the driver can attach a picture to a note. When creating a note from
Dispatcher, you cannot attach a picture.
Step 1: If necessary, click the Dispatcher icon to open the Dispatcher module. The
Dispatcher window opens. If you want to add a note to something other than the
850

Working with Notes
route, double-click down to the appropriate level. If necessary, use the Route
Query to find the route.
Step 2: Right-click on the desired route, stop, order, or line item and select Route
Notes, Stop Notes, Order Notes, or Line Item Notes from the menu that pops up.
The Notes for window opens.
Notes: The fields at the bottom of the window allow you to search for notes from specific
users, specific date(s), or for any note that indicates an error or has been
acknowledged. To search, simply place a check in the boxes for the items to query.
Then, for each item being queried, enter the search criterion. For instance, to
search for all user notes received between March 11 and March 23, 2004, check
Received and enter the date range. Click on the Execute Query Using Criteria
icon. The list of user notes received in the specified date range appears at the top
of the window.
You can also add a note from the Route Notes window. Right-click on the desired
route and choose Lookup, then Notes. The Route Notes window displays, making
the route, and its stops, orders, and line items available. You may need to drill
down to get to the stop, order, or line item you want to view.
Step 3: Click the Add icon, or press the [Insert] key. The Add Note window opens.
This note is attached to a

particular stop. It will be saved
with the stop for reference.
Step 4: Type the contents of the note. Then, click the Save icon, or press [Ctrl]+[S]
when the information is complete.
Hint: To view, edit, or delete existing notes, double-click the note in the Notes for Route
window. The Edit Note window opens. Change the note as needed, clicking the
Save icon or press [Ctrl]+ [S] to save the changes, or click the Delete icon to delete
the note. You can also delete the note by selecting it in the Notes for Route window
and clicking the Delete icon.
Note: Information can also be sent back and forth between MobileCast users. For more
information, see User Notes.
Dispatcher Route/Stop/Order/Line Item Notes Add icon ([Insert]) Save icon
([Ctrl]+[S])
Operations Guide
851
Working with Notes
Viewing and Reporting Route and Item Notes
Route and item notes can be viewed and reported on, at a specific level of detail, in the
Notes for and Route Notes windows. The Preview Report that displays contains the
content of the note and other information related to the route, stop, order, or line item.
Notes: Notes are carried along with the data for the route, stops, orders, and line items,
but must be viewed in a separate Notes window instead of the list windows.
User-defined fields are also carried along with the data, but can be viewed from a
route or stop window. See Completing User-Defined Fields for more information.
Viewing Route and Item Notes
The type of note received dictates where it can be viewed in the Dispatcher.
You can access notes for a specific level of detail: route, stop, order, or line item,
directly from the Route list in Dispatcher. Right-click on a route, stop, order, or line
item, then choose the related Notes option, Route Notes, Stop Notes, Order Notes, or
Line Item Notes, from the menu that pops up. The Notes for window opens. You can
use the search option to see notes that are not initially displayed.
You can access notes using the Lookup - Notes option. Right-click on a route and
choose Lookup, then Notes. The Route Notes window displays, making all notes for
the route, and its stops, orders, and line items available for viewing. You may need to
drill down to get to the stop, order, or line item you want to view. This is the same
852

Working with Notes
window that displays when you double-click on a route in the Route Summary
window.
Notes can be added, removed, reported and printed from the Route Notes window.
To view notes for the route, or a stop, order, or line item, click on the route, stop, order,
or line item, and the related notes will display in the Text column.
To see notes that have or have not been acknowledged, for the route, stop, order, or
line item, check or uncheck the Show Acknowledged Notes box.
To edit a note, double-click on the row and the Edit Note window opens. From this
window you can also open, save, or delete an attached image.
When a note is received with a picture attached, it displays in the Thumbnail column.
To see a full view of the picture, right-click on the row and choose Open Image from the
menu that pops up. Your default image viewer will open and display the graphic.
To save the picture, right-click on the row and select Save Image As. The Save window
opens.
To delete the picture, right-click on the row and select Delete Image.
Note: Route notes can also be viewed using the Message Center; see Working with the
Message Center for more information.
Operations Guide
853
Working with Notes
Other users may send user notes to you. These are viewed in User Notes, under
List.
Generating Reports using Notes
The ability to print a note and the details about its creation can be beneficial when you are
required to send proof of delivery to a customer.
Reporting All Notes for a Route, Stop, Order or Line Item
You can generate and print reports from the Notes for or Route Notes windows that
contain all notes for a single route, stop, order, or line item.
The Preview Report displays all notes for a specific item, which includes the date and time
each note was sent, the text within each note, and any attached picture that was sent with
it. When you preview a note report for a route, stop, order, or line item, other information
related to that specific route, stop, order, or line item displays also.
The Route Note preview includes the Route ID, Route Date, Driver Information,
Equipment ID, Equipment Type ID, and Description.
The Stop Note preview includes all the information on a Route Note Report along
with the Stop Number and Description, Arrive and Depart times, Location Type, and
the Location Address.
The Order Note preview includes all the information on a Stop Note Report along
with the Order Number and Reference ID.
The Line Item Note preview includes all the information on a Order Note Report
along with the Line Item ID and Description.
Note: If more than one note exists, all notes for that specific level of detail display in the
report.
If the level of detail is set to stop or order, the delivery or pickup Reason Code and
Description display.
From the Preview Report window you can quickly scroll through the pages of the
report. You can also zoom in or out to make the report easier to read, export the
report data to a file, or print the report.
To generate a report from the Notes for window, do the following:
Step 1: In Dispatcher, right-click on a route, stop, order, or line item, then choose Route
Notes, Stop Notes, Order Notes, or Line Item Notes from the menu that pops up.
A Notes for window opens.
Notes: You can use the search option to see notes that are not initially displayed.
All notes received for the route, stop, order, or line item will be part of the report,
whether they appear in the search window or not.
Step 2: Click the Preview Notes Report icon. The report opens in the Preview Report
window, showing all notes specific to this route, stop, order, or line item.
854

Working with Notes
To generate a note report from the Route Notes window, do the following:
Step 1: In Dispatcher, right-click on a route and choose Lookup, then Notes. The Route
Notes window displays, making all notes for the route, and its stops, orders, and
line items available for viewing.
Step 2: Click on the route, stop, order, or line item that contains the note you want to
see.
Note: You may need to drill down to get to the stop, order, or line item you want to view.
Step 3: Click the Preview Notes Report icon. The report opens in the Preview Report
window.
Reporting All Notes for a Stop and Its Details
You can generate and print a report for a customer that shows the complete delivery
information from the Dispatcher screen. The report includes the Route ID, Route Date,
Driver Information, Equipment ID, Equipment Type ID, and Description, the Stop
Number, Arrive and Depart times, Location Type, and Location Address. The Order
Number and Reference, the Line Item ID and Description are included, as well as the
Order and Line Item Planned and Actual quantities. Finally, at each detail level, the report
includes the date and time each note was sent, the text within each note, and any attached
picture that was sent with it.
To generate the Stop Delivery Report, do the following:
Step 1: From the Route List in Dispatcher, right-click on the stop that you want to report
on.
Note: The stop does not have to be completed, have notes, or a signature for the report to
be run. If it is not completed, the Actual quantities will be blank.
Step 2: Choose Delivery Report from the menu that pops up. The Preview Report
window opens.
Note: From this window you can quickly scroll through the pages of the report. You can
also zoom in or out to make the report easier to read, export the report data to a file,
or print the report.
Creating and Viewing Users Notes
User notes are used to send messages between MobileCast users, and to display non-fatal
system exception notifications, such as database exceptions, route loading errors, and
notifications if the critical minutes for a given location has been exceeded.
Note: If the critical minutes for a location has been exceeded, a notification will only be
displayed if the locations Service Failure Notification option is set to Message To
Dispatcher. This option can be set in the Extended page of the Location Notebook.
Step 1: If necessary, click the Dispatcher icon to open the Dispatcher module. The
Operations Guide
855
Working with Notes
Step 2: From the menu bar, click List, then select User Notes. The Notes for User
window opens.
Any note that was sent to you will be

displayed in the Notes for User window.
Note: The fields at the bottom of the window allow you to search for notes from specific
users, specific date(s), or for any note that indicates an error or has been
acknowledged. To search, simply place a check in the boxes for the items to query.
Then, for each item being queried, enter the search criterion. For instance, to
search for all user notes received between March 11 and March 23, 2004, check
Received and enter the date range. Click on the [Query] icon. The list of user notes
received in the specified date range appears at the top of the window.
Step 3: To add a user note, click the Add icon or press the [Insert] button. The Add
User Note window opens.
The Add User Note window is

used to create and send a note
to any MobileCast user.
Step 4: Click the down arrow to select who the message will be sent to; then, type the
contents of the note.
Step 5: Click the Save icon, or press [Ctrl]+[S] when the information is complete.
Hint: To view, edit, or delete existing user notes, double-click the note in the Notes for
User window. The Edit User Note window opens. Change the note as needed,
clicking the Save icon or press [Ctrl]+ [S] to save the changes, or click the Delete
856

Working with Notes
icon to delete the user note. You can also delete the user note by selecting it in the
Notes for User window and clicking the Delete icon. Unacknowledged user notes
can also be viewed from the Message Center.
Note: Information can also be attached to routes, stops, orders, and line items. For more
information, see Creating Route and Item Notes.
Dispatcher List User Notes Add icon ([Insert]) Save icon ([Ctrl]+[S])
Operations Guide
857
Completing User-Defined Fields

User-defined fields and notes allow you to attach unique information to individual routes,
stops, orders, etc. This information stays with the item through the Roadnet
Transportation Suite. User-defined fields can be viewed in the list window for a route,
stop, order, line item, or load; simply scroll across the window to find the proper column.
By default, a user-defined field is named User Defined Field 1, User Defined Field 2, or
User Defined Field 3, but you can change the name to a more meaningful one on the
Aliases page in the Maintenance Options notebook. For example, you might have two at
the stop level called Dock and Conveyor.
Each region can have up to three user-defined fields for each route, stop, order, and line
item in MobileCast. Which ones you use, or whether you use any at all, is completely up
to you, depending on the information you want to track.
Dispatcher window opens. If you want to complete a user-defined field for
something other than the route, double-click down to the appropriate level. If
Step 2: Right-click on the desired element and select Properties from the menu that
pops up. The Properties notebook opens.
Step 3: For a route or stop, the user-defined fields are on the Advanced page of the
notebook; for anything else, they are on the General page. Click the tab to display
the proper page of the notebook.
858

Step 4: Enter the appropriate information (up to 20 characters) for each user-defined
field.
User-defined fields can store any information you want for a

route or stop.
Step 5: Click the Save icon, or press [Ctrl]+[S] when all necessary user-defined fields
for the element have been filled in.
Step 6: Click the [Yes] button to verify the save.
Note: To edit a user-defined field, change it in the Properties notebook. To remove the
contents of a user-defined field, delete the entry in the Properties notebook.
Dispatcher Route/Stop/Order/Line Item Properties Save icon ([Ctrl]+[S])
Operations Guide
859
Wireless Communication with MobileCast

If you are using wireless communication, the driver and dispatcher are able to let each
other know about changes that are made to a route throughout the day. Both the driver and
dispatcher are able to make changes to the route, such as adding a stop, changing an
existing stop, adding or changing orders or line items, re-sequencing the stops, or
cancelling a stop. In addition, the dispatcher can transfer stops between two routes, and
the driver can start and complete a route, or designate a stop for redelivery. Text messages
can also be sent between the driver and dispatcher.
In order for the driver to be aware of changes the dispatcher makes to the route, a message
appears on the wireless device when the updated information is received, and the
appropriate route is automatically updated.
On the dispatchers end, when MobileCast receives a message from the wireless device,
it tries to process the event described in the message. If there is no problem, MobileCast
is automatically updated to reflect the event and the results can be seen in the route
window. But, if there is a discrepancy between the message sent and the route outlined in
MobileCast, it will not process the event, or any subsequent events. You can edit the event
so that it will be processed; see Working with Wireless Events for more information. To
view, acknowledge, or search for any event receipt associated with a route, see Viewing
Event Receipts. Text messages, server application responses, and other notes can also be
viewed using the Message Center; see Working with the Message Center for more
information.
Working with Wireless Events
Once a wireless device is associated with a route, whether through the driver download
process, individual assignment, or equipment, messages received from the driver
automatically update MobileCast as appropriate. You can view the messages as they are
sent and received for the route, and even edit them if necessary. Each wireless message is
called an event. For more information, see Wireless Communication with MobileCast,
Viewing Event Receipts, Working with the Message Center, or Sending Messages to the
Driver.
Step 2: To view the events for a specific route, locate the route in the Overview
window, map, or route list. Right-click on the route and select Lookup, then
Wireless Events. The Wireless Events window opens, displaying the list of
events that have not been processed for the route. Unless there is a problem, there
should be no more than one unprocessed event at a time in a particular routes
Wireless Event window.
860

To view all current wireless events for all regions, click List on the menu bar,
then click Wireless Events.
This example shows three text messages sent to a route.
The Wireless Events window includes information about the event, such as the
time and type of message sent. The following events can be sent over the wireless
device:
Message
Explanation
Route Start
Driver has left the depot.
Stop Arrive
Driver has arrived at the stop.
Stop Complete
Driver has completed this stop.
Cancel Stop
Driver has cancelled the stop. The stop is not considered

when calculating actual miles and times, but remains as
part of the plan.
Redeliver
Driver was unable to deliver the stop, but it is still

considered when calculating actual miles and times. The
driver has the option to return to the stop.
Route Refresh
Driver has added orders or line items to the stop.
Mass Sequence/
Stop Sequence
The stops have been resequenced.
Route Complete
Driver has reached the routes destination.
Text Msg
A message or note has been sent.
Picture Note
A message or note with an attached picture has been

sent.
GPS
The latitude and longitude of a specific location have

been sent.
Delivery Detail
Delivery quantities have been updated to reflect changes

due to damaged goods, shortages, pick ups, or other
situations.
Drop Hook
Driver has dropped the equipment for the drop and

hook.
Position Request
Dispatcher has requested the current GPS position of the

route.
Container
Container delivery/pickup exceptions have occurred.
Operations Guide
861
Step 3: To edit a event, double-click on it. The Edit Text Message Event window opens.
The first page of the notebook, Key, provides details about the route, such as the
route ID and date, the region, and the wireless ID. The second page of the
notebook is specific to the type of event being edited.
Step 4: Edit the event, as necessary, to make it correct.
You can open and edit any

wireless event simply by doubleclicking on the event.
Note: If a Stop Complete, Stop Arrive, or Route Start event contains error text use the
[Attempt to Fix Error] button to try and correct the event. If successful, a route
note is created. If there is no error text, the button does not display.
Step 5: Click the Save icon, or press [Ctrl]+[S] when the event has been edited, then
click the Close box to close the Edit Event window.
Step 6: Click the Close box to close the Wireless Events window when all events have
been reviewed.
Warning: You can also delete an event by right-clicking it and clicking Delete from the
menu that pops up. Be careful, though, when deleting events; deleting the wrong
one could cause all future events for that route to fail.
Hints: To edit a group of events, first select the events by clicking on the first one, holding
down the [Shift] key, and clicking the last one. Then, right-click anywhere in the
selected routes and click Edit Selected. You can move through the selected routes
using the buttons at the top of the window.
If you correct an invalid message, the correction is not necessarily processed
immediately. It is processed during the next processing time, typically between
862

ten and thirty seconds. Until an invalid message is corrected, none of the messages
after it will be processed.
Dispatcher Routes window Lookup Wireless Events
Viewing Event Receipts
The Event Receipt window lets you view, acknowledge, and search for any event receipt
associated with a route. Once youve found the even receipt you are looking for, you can
view the event type, description, the time it was sent, the time it was received by the
wireless device, whether or not the wireless device discarded it, and whether or not it has
been acknowledged by the dispatcher or the wireless device.
Step 1: Click on the Dispatching icon to open the Dispatcher module. The Dispatcher
window opens.
Step 2: Click on the List menu and select Event Receipts. The Event Receipts window
opens.
The Event Receipt window lets you query for particular

routes, allowing you to monitor them more closely.
Step 3: Use the query section at the bottom of the window to specify the routes you
want to retrieve. You can search by:
Route Datemanually enter the date or click on the arrow to open a calendar. To
change the month, either use the arrows on the top of the calendar to scroll through
the months, or click on the month and select from the menu that pops up. To
change the year, click on the year and use the arrows to scroll to the correct year.
Operations Guide
863
Click on a date to select it. If you are entering todays date, then simply check the
box.
Route IDenter the routes ID.
Server Addedcheck and enter a date range if you want to search by the date and
time the event was created by the dispatcher. To enter a date, click on the arrow to
open a calendar. To change the month, either use the arrows on the top of the
Server Sentcheck and enter a date range if you want to search by the date and
time the event was sent from the server to the wireless device. To enter a date,
click on the arrow to open a calendar. To change the month, either use the arrows
on the top of the calendar to scroll through the months, or click on the month and
select from the menu that pops up. To change the year, click on the year and use
the arrows to scroll to the correct year. Click on a date to select it.
Dispatcher Acknowledgedcheck if you want to search for those events that
were only acknowledged by the dispatcher.
Device Discardedcheck if you want to search for those events that were
discarded by the wireless device. An event may be discarded by the wireless
device if the driver has already departed the stop or if the stop has been cancelled.
Step 4: Click the Execute Query Using Criteria icon to find the information that meets
the criteria. The routes that meet the specified requirements is listed in the Event
Receipt window.
Note: If you performed a previous search, and would like to keep these results listed
along with any new results, then check Retain Results.
Step 5: To acknowledge an event receipt, scroll through the list and highlight the
route the event is associated with. Scroll through the columns and check
Dispatcher Acknowledged.
OR
Double-click on the route the event is associated with. The Edit Event Receipt
window opens. Check Dispatcher Acknowledged, and then click the Save icon or
press [Ctrl]+[S] to save your changes.
Dispatcher List Event Receipts
Working with the Message Center
The Message Center allows you to easily know when a text message is received from the
driver, or if the system is not functioning properly so that you can respond quickly to any
problems that may have occurred. The window is divided into two sections; the top
section, Messages from Drivers, lists all unacknowledged text messages the drivers have
sent, while the bottom of the window, Messages from System, lists any error messages
from the server, such as network status messages. You can have the window refresh
864

automatically at set intervals, or refresh it as needed. The message bar at the bottom of the
Dispatcher screen indicates how many unacknowledged messages are present.
To open the message center, click the View menu and select Message Center. Resize and
position the window as you want; you can minimize the window to save screen space
when it is not needed.
Unacknowledged messages to and from the driver are listed in the

Message Center.
To set the refresh rate, right-click on the message bar at the bottom of the window and
select the desired refresh rate from the menu that pops up.
To refresh the window immediately, right-click on the message bar at the bottom of the
window and select Now from the menu that pops up.
To view a message, double-click on it in the Message Center. The message opens in a
Notes window; you can acknowledge the message, make an additional notation on it, or
delete the message. Once the message is acknowledged, it disappears from the Message
Center.
To view a picture in the Thumbnail column, right-click on the row and choose Open
Image from the menu that pops up. Your default image viewer will open and display the
graphic.
To save a picture, right-click on the row and select Save Image As.
To delete a picture, right-click on the row and select Delete Image.
To generate a single route note report, right-click on the message and choose Generate
Note Report from the menu that pops up. The Route Notes report opens showing just that
note. You can view, print, or export the report. A single note report contains the text of a
note along with other more detailed information about the route. The report also includes
any picture that is attached to the note.
Operations Guide
865
To reply to a drivers message, right-click on the message and choose Reply from the
menu that pops up. The Send Message window opens. Type your message and click the
[Send] button. The new message is sent to the driver, and the original message is marked
as acknowledged and removed from the Message Center.
To acknowledge a message, right-click on the message and select Acknowledge from the
menu that pops up. The message is acknowledged and removed from the Message Center.
Disabling Wireless Communication
You may encounter situations when you need to change the device a route is loaded on,
or even remove the route information completely from a device. For example, a driver
may have loaded the wrong route or confidential details regarding customers must be
purged from the device for security reasons. In order to load the route onto another
device, you must first disable the wireless communication between the original device
and MobileCast.
If the route has not been started before disabling wireless communication, it can be
reloaded onto another device. If the route has been started, the stops must be manually
completed, or the entire route must be deleted.
If the driver is using a Java-enabled phone, the route will be deleted from the phone and
the application will return to the login screen. If the driver is using a hand held device or
OnTrack, the route will not be removed and the dispatcher must contact the driver to
communicate this information.
To disable wireless communication, right-click on the route and select Disable Wireless
Communication from the menu that pops up. Click the [Yes] button to confirm this action.
Warning: This function cannot be undone and is to be used only in very special
situations. Executing this function will permanently delete all downloaded route
information from the Java-enabled phone.
Notes: In order to disable wireless communication, this permission must be set by your
administrator. See Working with Privileges for more information.
866

Sending Messages to the Driver
Sending Messages to the Driver

If you are using wireless devices, the driver and dispatcher can easily communicate with
each other throughout the day. Not only can the driver send route information and updates
directly to the MobileCast server, but the dispatcher can send messages to one or all
driver(s) about changes that might occur throughout the day.
Hint: The driver will automatically receive a message anytime you update the route, so
you do not need to send messages about route updates.
Step 2: Right-click on the route, then click Send Message to Driver(s) from the menu
that pops up. The Send Message to Driver window opens.
Note: To send a message to more than one driver, click on the first driver, then hold
down the [Shift] key, and click the last one. All of the drivers you want to send a
message to will be selected.
Step 3: Enter a brief message in the Text field, or select a canned text message. If you
are using a canned text message, you can change or add to it as necessary.
Once the [Send] button is clicked,

this message will be sent to the
wireless device assigned to the
route.
Step 4: Click the [Send] button to send the message and close the Send Message to
Driver window.
Step 5: A notification appears, displaying how many messages were sent successfully,
and, if necessary, explaining why some failed. Click the [OK] button when
finished.
Dispatcher Routes window Send Message to Driver(s)
Operations Guide
867

You can print driver directions from any route or map window in Dispatcher. These
directions can be given to a new driver who is not familiar with the route or the area.
Note: The driver can also display directions on a mobile device; you can either choose
to pre-load the directions for the route, or the driver can request directions on an
as-needed basis. See Working with Drivers for more information.
you will not be able to print any directions that include maps, such as turn by turn
directions.
Step 2: Right-click on the route, then select Driver Directions from the menu that pops
up. There will be a pause while the system computes the paths from stop to stop,
and then the Route Directions for Route window opens, listing the driver
directions.
These directions can also

be pre-loaded on the
drivers mobile device.
Step 3: To print the directions, click the Printer icon and select the type of directions
you want to print. The options are:
868


Dispatcher Routes window Driver Directions
Operations Guide
869
Checking for Space on a Piece of Equipment

MobileCast is very helpful for managing loads because it lets you check how much space
a piece of equipment has available at each stop during a route. In MobileCast, this feature
is called Calculate Percent Empty. When used in conjunction with the Equipment map,
this feature can be very useful in determining which pieces of equipment in a specific area
have space available. To further help you plan your loading, MobileCast measures the
empty space in three different ways, according to the size aliases defined in the
Maintenance module.
In order to accurately calculate percent empty, MobileCast must know the capacity of
your equipment and the items delivered and picked up at each stop. In addition, Carries
A Load must be selected. See Working with Equipment Types for more information on
setting the equipment capacity, and Entering Order or Line Item Information for more on
deliveries and pickups.
Step 2: Locate the desired route or stop in the Overview window, list window, or a map.
If necessary, use the Route Query to find the route.
Step 3: Right-click on the route, then select Calculate % Empty from the menu. The
Percent Empty window opens, showing the available space for the three different
sizes of items at that stop.
The Percent Empty for Route

window displays the amount of
available space on a piece of
equipment.
Step 4: Use the arrow buttons at the top of the Percent Empty window to scroll through
the stops, viewing the trucks available capacity as it proceeds through the route.
When you are finished viewing, click the Close box.
870

The colors displayed in the trailer indicate specific information:

Red indicates product that has yet to be delivered.
Green indicates product that was picked up.
White indicates empty space.
Dispatcher Routes windowRoute Calculate % Empty
Operations Guide
871
Swapping Equipment at a Stop

MobileCast allows for the times when two routes meet at the same stop and exchange
equipment, a procedure sometimes called a drop-and-hook. Running a drop-and-hook in
MobileCast is similar to running a regular route. There are slight differences, however, in
two areas:
When assigning equipment, both routes will be assigned the swapped pieces of
equipment (probably trailers) with different starting and ending locations.
When the first route gets to the stop for the swap, click the Stop Complete windows
Stop Arrive icon instead of the Stop Complete icon. This suspends the first route; the
driver must wait for the second driver to arrive before the first routes stop can be
completed.
Note: In order for a drop-and-hook to take place, the two routes must have a location in
common. If necessary, add a stop to one of the routes for the swap location, as
shown in Adding a Stop.
Assigning Equipment to Be Swapped
When you assign equipment to be swapped, you apply the same process you would for
any other route. However, this equipment will change at some point on the route, so when
youre assigning equipment, you need to show where the transfer will occur.
Step 2: Locate the desired routes in the Overview window or a list window. If
Step 3: Assign the drivers, dispatchers, and other non-equipment resources to the
routes.
Step 4: Assign equipment to the first route that will not be swapped (such as a tractor).
Step 5: In the Equipment list of the Assignments for Route window, find the piece of
equipment (probably a trailer) that will start with the first route and end at the
stop where the swap will occur. If necessary, search for the equipment by clicking
the appropriate search check boxes, typing the item to look for, and clicking the
Execute Query Using Criteria icon.
Step 6: Click on the piece of equipment.
Step 7: Click the End Location arrow to open the Lookup End Location window.
Double-click the location where the swap will occur, or click on the location and
then the Process icon.
Step 8: Click the [Insert] button to add the first piece of swapped equipment to the
Equipment assigned to route list.
Step 9: In the Equipment list of the Assignments for Route window, click the piece of
equipment that will be picked up by the first route when the swap occurs.
872

Step 10: Click Start Location arrow to open the Lookup Start Location window.
Double-click the location where the swap will occur, or click on the location and
then on the Process icon.
Step 11: Click the [Insert] button to add the second piece of swapped equipment to the
Equipment assigned to route list.
Step 12: Click the Save icon, or press [Ctrl]+[S] to save the assignment.
Step 13: Repeat these steps for the second route, reversing the information about
starting and ending locations for the swapped equipment.
Step 14: Click the Close box to close the Assignments for Route notebook.
Dispatcher Routes window Assignments Equipment Insert Save icon ([Ctrl]+[S])
Handling the Swap at the Stop
If you are using MobileCast to track a drop and hook, you need to set up both routes so
that there is a common stop, or meetpoint, and assign the equipment to both routes. Before
a swap can occur, both routes need to arrive at the stop. Once the swap has been made,
the stops can be completed.
Step 2: Locate the desired routes in the Overview window or a list window. If
Step 3: Use the stop lists, if necessary, to determine which route gets to the stop first.
For that route, complete all stops up to the one that has the drop-and-hook as you
normally would. See Completing an Individual Stop for instructions.
Step 4: Right-click on the first route and select Stop Complete from the menu that pops
up. The Stop Complete for Route window opens. The stop where the drop-andhook takes place should be selected.
Operations Guide
873
Step 5: Click the Arrive icon, then click the Save icon. At this point, the first route is
essentially suspended until the second route reaches this location.
Click the Complete icon and then the Save icon to

complete a stop.
Step 6: When you are ready to complete the stop for the second route, just complete it
like you normally would: click the Complete icon, then the Save icon.
Step 7: Now that the equipment for the second route has been released, go back to the
first route and complete the stop where the drop-and-hook occurred.
Step 8: Continue running both routes as usual.
DispatcherRoutes windowRouteStop Complete Arrive icon Save icon ([Ctrl]+[S])
Complete icon Save icon ([Ctrl]+[S])Complete Save icon ([Ctrl]+[S])
874

Viewing Item Lists
Viewing Item Lists

The List menu in the Dispatcher module allows you to view lists of canned text messages,
containers, drivers, delay types, employees, equipment, route types, locations, reason
codes, cancel stop codes, route statuses, undeliverable stop codes, stop signature codes,
order financial detail codes, user notes, unassigneds, distance by jurisdiction, skill sets,
user-defined data, wireless events, and event receipts. Use these lists to answer questions
you might have about things like the address of a location or the status of a piece of
equipment.
You can make changes to the lists of user notes and wireless events. All of the other items
in Dispatchers lists are for reference only; they are maintained in the Maintenance
module.
Step 2: Click List and select the item you want to view. A window opens displaying
either all entries for that item.
Step 3: Examine the items.
To edit a user note, double-click it, then make the desired changes. See User
Notes for more information.
To edit a wireless event, double-click it, then make the desired changes. See
Working with Wireless Events for more information.
Step 4: Use the Close box to close the list window when you are finished viewing
items.
Hint: The List menu is for viewing all the items for a region. To view the items for a
particular route, right-click on the route, click Lookup, and click the item you want
to view.
DispatcherList Item Close
Operations Guide
875
Viewing My Routes Only
Viewing My Routes Only

While working in the Dispatcher, MobileCast allows you to only see those routes that
have been assigned to you. This means that, unless permissions are set by the
administrator, you will only see those routes that have your User ID assigned as the
Dispatcher.
You will only see your assigned routes when working with the following windows: Route
List, Route Overview, Not Completed Routes, Not Assigned Routes, Route Summary,
Route Query, and Route Watch.
Notes: In order to view other dispatchers routes within your region, the privilege must
be granted by your administrator. See Working with Privileges for more
information.
If you do not have any routes assigned to you, then no routes will be displayed
when My Routes Only is selected.
For information on assigning routes to specific users, refer to the Assigning
Resources section.
View My Routes Only
When viewing only your assigned routes, your User Name and ID are
displayed at the bottom of the window.
876

Viewing Distance by Jurisdiction

Often organizations need to determine how far they traveled in an individual state or
province for reporting purposes. MobileCast includes a distance by jurisdiction option
that tracks the distance each route travels in a state/province/jurisdiction. Distances are
calculated by measuring the straight line distance between GPS pings. You can gather this
information for one or more routes and use it to generate reports showing the distance
traveled in each area. In order to be able to view these distances, you must select Calculate
Distance by Jurisdiction on the Dispatch - General page of the Maintenance Options
notebook. If this option is selected, the distances for each jurisdiction the route travels
through are automatically calculated when the route is completed. You can periodically
check the distances in the Dispatcher, and even export the information or print a report.
Important: This feature is not intended to replace your local reporting requirements. A
route with exceptions that affect distance will diminish the accuracy of this report.
Check with your local jurisdiction for the legal reporting requirements in your
area.
Note: If you are using handheld devices, such as the Intermec or Symbol devices, you
need to set the devices to send free GPS events for this function to work properly.
Contact your Roadnet Technologies consultant for more information.
window opens.
Step 2: Click on the List menu and select Distance by Jurisdiction. The Distance by
Jurisdiction window opens
Step 3: Use the query section at the bottom of the window to specify the routes you
want to retrieve.
Select the period of time you want the information to cover. You can choose from
many different time periods, including all entries for today, yesterday, last week,
or year to date. If you want to specify the dates to search for, click Specify and
enter the starting and ending dates in the Begin Date and End Date fields.
Operations Guide
877
To select a driver or piece of equipment, click on the arrow to open a Lookup

window. Double-click on the driver/equipment to select it, or click on the item and
then on the Process icon.
Once the results are displayed in the Distance by Jurisdiction

window, you can print a report or export them to Excel.
Step 4: Click the Execute Query Using Criteria icon to find the information that meets
the criteria.
The routes that meet the specified requirements is listed in the Distance By Jurisdiction
window; each jurisdiction for the route is listed separately. Now you can view it, print a
report, or export the information to an Excel file or text file.
To change the distance or jurisdiction, double-click on the route; the Edit Distance
Jurisdiction window opens. Enter the new distance or jurisdiction for the route and click
the Save icon.
When entering the jurisdiction,

make sure you enter it correctly.
For instance, MobileCast
considers PA and Pennsylvania
separate jurisdictions.
To print a report, rearrange the columns as necessary. Make sure the columns you want
included in the report are visible in the window. Click the Printer icon; the List Print
Settings window opens. Choose whether you want to send the report to the default printer
or to a text file. Enter the report title or name of the file. Click the [Print] button.
878

To export the data to Microsoft Excel or a database, right-click on a column header

and select Export from the menu that pops up. To export to a Microsoft Excel spreadsheet,
click Microsoft Excel. Enter the path and name of where the spreadsheet exists, or you
want it to be created, or click the [...] button and browse to the location. Enter the name
of the sheet you want the information stored on. To have Excel automatically open when
the export is complete, check Launch Excel After Export. To export to an ODBC data
source, click ODBC Data Source and enter the table name. Click the [Export] button.
To add a new jurisdiction distance for a route, click the Add icon on the Distance by
Jurisdiction window; the Add Distance by Jurisdiction window opens. Click the Route
arrow; the Route Lookup window opens. Use the notebook at the bottom of the window
to search for the route(s) you want; you can search by driver, equipment, location, or route
information. Once the search information is entered, click the Execute Query Using
Criteria icon; all routes meeting the criteria are listed at the top of the window. Doubleclick on a route, or click on it and then on the Process icon, to select it. In the Add Distance
by Jurisdiction window, enter the jurisdiction and distance for the route. Click the Save
icon to save the information.
DispatcherList Distance by Jurisdiction Execute icon
Operations Guide
879
Viewing User Defined Data
Viewing User Defined Data

There may be times when you have route data retrieved from an outside source, such as
an onboard computer, that you want to keep track of when you use the Roadnet
Transportation Suite. To better help your organization comply with company policies,
you can create your own user-defined database table and user-defined columns to keep
track of this data. The ability to create/maintain the user-defined tables is available
through Roadnet Web Services; the user-defined tables are created in the Roadnet
Transportation Suite database. See Roadnet Transportation Suite Web Services Overview
Once you have created your user-defined data for the user-defined tables in the database,
you can view the data in Dispatcher. If you have added new tables in the database, you
must restart Dispatcher.
Note: You cannot edit user-defined tables in Dispatcher. Changes can only be made
through Roadnet Web Services.
window opens.
Step 2: To view the data for a user-defined table, click on the List menu, and select
User Defined Data, then the appropriate table. The user-defined table window
opens with the name of the table showing at the top of the window. To see the
data for all the routes, click the Search icon or you can search to display only the
data for a specific route(s).
To view the data for a specific route, right-click on the appropriate route, and
select Lookup, then User Defined Data, and finally the appropriate table. The
user-defined table window opens with the name of the table and the Route ID
showing at the top of the window, displaying the data for that route.
Warning: User-defined data that is associated with a MobileCast route will also be
deleted if you delete the route.
880

Working with OnTrack Routes

OnTrack routes are unplanned routes, meaning that they are created automatically as
position data is sent from the Java-enabled phone to the Dispatcher. As the employee
travels from location to location, the phone gathers the position data for each location, and
then relays it back to the Dispatcher. This position data is then used to create the stops on
a route. Creating routes on the fly is useful for managing yours sales or merchandising
teams. By using this routing method, you can gain a better understanding of the
employees day-to-day activities, as well as increase face time with your current or future
customers.
Working with OnTrack routes in the Dispatcher is similar to working with other routes.
By right-clicking on the OnTrack route, a menu pops up, allowing you to view the routes
details, generate stops, get directions for the employee, complete the stop, complete the
route, disable the wireless communication, remove the route from the current view, delete
the route, refresh the route, plot the route on a map, show the routes position history, and
lookup the routes stops, employees, and route exceptions.
A blue car stands for an OnTrack route.
There are two types of OnTrack routing passive and non-passive. Passive routing is
convenient for those employees who want little interaction with the Java-enabled phone.
All the employee needs to do is login, and then, at the end of the day, simply complete the
route. The route is created using the position data the phone relays back to the Dispatcher.
This position data is matched to the locations that are assigned to the employee, and then
the location is added to the route once it is completed or the stops have been generated.
Important: Passive routing starts the route when it receives the first valid GPS ping from
the phone. If your driver starts the day in the warehouse for meetings, or another
Operations Guide
881
place where getting a GPS reading is difficult, the route may not start at the proper
time. To avoid this problem, and make sure all of the drivers hours are included
in the route, assign a location with a type of DPD to the driver in the Maintenance
module. If the driver is assigned a location of this type, when the driver logs into
the phone, the route is started using that location as the depot.
Non-passive routing is a bit more user intense, but provides the Dispatcher with a more
precise location. As the day proceeds, the employee will use the Java-enabled phone to
arrive and depart from each location. Upon departure, the phone relays the locations
position data back to the Dispatcher. The position data is matched to a location assigned
to the employee, and then the location is automatically added to the route. Unlike, passive
routing, you are able to view the stops on the route immediately.
Notes: The Dispatch - Java Phone page of the Options notebook in the Maintenance
module lets you choose the type of OnTrack routing you want to use.
In order for the dispatcher to perform some procedures on the route, such as
completing a stop, communication with the wireless device must be stopped.
Select Disable Wireless Communication from the menu to stop the
communication.
Generating Stops
When you are using passive routing, you have the option to generate the stops on a route
before the route is complete. This is useful if you want to see how the route is progressing
throughout the day. To generate the stops, simply right-click on the OnTrack route and
select Generate Stops from the pop-up menu.
Generating stops for an

OnTrack route is a great way
to track the employees
progress throughout the day.
Note: If you choose to generate the stops after the route has been completed, MobileCast
will clear the route, and then use the position data sent from the phone to redo
all of the stops on the route.
882

Accounting for a Route

Accounting for a route involves adding, deleting, or changing the information in the
routes track types.Track types are the accounting-related items, such as hours driven and
stops delivered, that are used to compute billing and payroll. Track types can also be used
for variance reporting. For example, you might track how the actual temperatures of
perishable loads compares to the planned temperatures.
Track Types are created and maintained in the Maintenance module. They are filled in for
routes from either the Dispatcher module or the Accounting module.
If you re-complete a route that has already been completed, you will also be prompted to
redo the accounting process.
If you click Complete and then the Save icon from a route that has already
been completed, you will see this message. Click [Yes] if you do need to make
a change. This is useful if, for example, you find out after the route was run
that its actual hours were different from what was originally reported.
Note: When you complete a route in the Dispatcher, you have the option to edit its track
types. Clicking [No] does not mean that the route will not have track types. Track
types can be set up in the Maintenance module to be automatically created (autocreated) for every route, whether or not you choose to look at them. Clicking [Yes]
means that you want to change the information in auto-created track types, or add
track types that arent automatically created.
From the Accounting module, you can edit a routes track types by double-clicking on the
route in either the Not Billed, Not Paid, or Query window. Whether you are in Dispatcher
or Accounting, you use the Edit Route Account window to add and change the track type
information for a route.
Step 1: From the Dispatcher module, complete the route as shown in Completing a
Route. Click [Yes] when you are asked whether you want to edit accounting
information.
From the Accounting module, click List from the menu bar and select either Not
Billed, Not Paid, or Query, depending on the status of the route you want to work
with. Double-click the route.
The Edit Route Account window opens.
Step 2: To add an additional track type to the route, click the Track Type arrow and
choose the desired type from the list that opens. If the track type is something
Operations Guide
883
MobileCast knows or can compute, such as the miles, click the Prefill button to
have the Quantities fields filled in for you. Otherwise, click the appropriate check
box(es) and type the information in the field. Click the [Insert] button to add the
new accounting information for the route.
You can add and change track

type information for a route
from the Dispatcher and
Accounting modules.
To edit information for a track type that is already on the route, click the track
type in the Accounts list at the bottom of the window. The track type is highlighted
and the entries displayed in the Quantities fields. Change the entries as appropriate
and click the [Update] button.
To delete a track type from the route information, click the track type in the
Accounts list, then click the [Delete] button. The information will be deleted from
the route.
To apply a value to all checked track types, enter it in the Apply to all checked
quantities field, then click the button. Click the [Update] button for the change to
take effect.
Step 3: Click the Save icon, or press [Ctrl]+[S] when you are finished making changes
to the track types.
Hint: If you are in Update mode in the Edit Route Account window and want to add new
track types for the route, click the [Clear] button to switch to Insert mode.
DispatcherRoute (Complete Yes) Edit Track Types Save icon ([Ctrl]+[S])
884

Refreshing the Windows in Dispatcher

Since MobileCast is constantly receiving updated route information from the drivers, you
need to make sure that the Dispatcher is displaying the most recent information. In order
to assure that you are seeing the most recent information, you can manually refresh the
windows in the Dispatcher; in addition you can choose to have the windows refresh with
the latest information automatically.
window opens.
Step 2: To set the frequency with which information is automatically refreshed, click
on the Windows menu and select Change Refresh Rate. The Change Refresh
Rate window opens.
Step 3: Enter the length of time in the Rate field, and click the Unit arrow and select
Seconds, Minutes, or Hours to set the refresh rate.
You can set the frequency with which
the information is automatically
updated in the Dispatcher.
Note: When setting the refresh rate, make sure the rate is long enough for refreshes to
occur. The length of time needed may depend on your operating environment. For
instance, if you are connected using terminal services, you would want to set a
longer refresh rate.
Step 4: Click the [OK] button to save the change for this session of the Dispatcher. To
permanently save the change, click the [Save] button.
Note: To manually refresh a window, click the Refresh icon on the window.
DispatcherWindow Change Refresh Rate [OK]/[Save]
Operations Guide
885
886

MobileCast - Loads
Using MobileCast to Manage Loads

Many dispatching organizations assign third-party loads to routes. These extra loads
provide additional revenue and keep trailers from running empty. If you manage routes
with extra loads, MobileCast can help.
Note: Load management is a separate purchasable option; contact your sales person for
more information.
By integrating load management into its dispatching system, MobileCast enables you to:
Avoid lost revenue opportunities.
More easily determine which route(s) should carry a particular load.
Track the load across routesor even across MobileCast regions.
Use the data that MobileCast gathers about loads in the reports you create.
Load Key Concepts
A load can be broken down into two types: simple and complex. A simple load consists
of one customer commodity and two stopsa pickup location and a delivery
locationwhereas, a complex load handles multiple customer commodities and stops. If
your load spans more than one route and/or region, there will also be at least one meet
point. If the load goes across routes, the meet point is called a relay in MobileCast. If it is
relayed across regions or to a common carrier, it is also called a transfer.
Load Rights
Loads can be managed by anyone who has the appropriate rights. Load rights are assigned
in the Administration module. There are two levels of these rights: Load User is the basic
level, while Load Admin has all Load User rights plus the ability to see all loads in all
regions.
Loads are created and managed from MobileCasts Dispatcher module. You prepare for
handling loads by entering a few load-specific resources (locations, billing addresses,
etc.) in the Maintenance module. If you have Load User or Load Admin rights, the Loads
menu is added to the Dispatcher and Maintenance menu bars.
Load Phases
Load management in MobileCast has five phases, although not every load goes through
every phase:
1. AvailableThe load was entered into the MobileCast system, but hasnt been taken
yet. Available loads are displayed in the Loads Available list.
2. ClaimedSomeone has decided to take responsibility for the load, but hasnt
decided exactly what to do with it. Claimed loads are displayed in the Loads Active
list.
3. AssignedThe load has been put on a route or given to a common carrier. Assigned
loads are displayed in the Loads Active list.
4. TransferredA load that can only be partly completed by one region has been passed
on to another region. In the first region, the load is displayed in the Loads Active
Operations Guide
887
list. In the second, it is displayed in the Loads Available list until it is assigned by
the second region.
5. CompleteOn regular, dedicated routes, a load is complete either when a Stop Complete has been done on the last location for the load, or, if the route destination is the
loads last location, a Route Complete has been done. On a route that has been
assigned to a common carrier, a load is complete when an actual time has been
entered for the last location from the Route Properties window. To see a completed
load, search for it from the Loads Query window.
The three lists associated with loads are Active, Available, and Query Results. Among these
lists you can see all the possible load phases.
888

Setting Up for Loads

Before you can use MobileCasts load management features, your MobileCast system
needs to be set up to handle loads. Setting up for loads involves the following:
Check in the Administration module to make sure any users who are involved with
load management have the proper user rights.
In the Maintenance module, create at least one load customer and customer
commodity for each MobileCast region (mandatory) and any STCC codes, freight
classes, common carriers, and load types that might be needed (optional).
In the Maintenance module, create any locations that will be involved with loads, if
you know ahead of time what they are. These load locations are separate from the
normal stop locations used in routes. If you do not know the load locations in
advance, you can create them on the fly when you create a load.
Choose the proper load default options on the Loads page of the Maintenance
Options notebook. These options are only available to load admins.
Operations Guide
889
Setting the Load Defaults

The Dispatch - Load page of the Options notebook in the Maintenance module allows you
to specify the default information if you are using MobileCast to manage loads. This tab
will be visible only if you have load admin rights.
To open the Options notebook, select Options from the Tools menu in the Maintenance
module. Click on the Dispatch - Load tab.
Use the Dispatch - Load Page to set up how you want MobileCast to handle loads.
Step 1: Enter the default aliases for your loads, load customers, and common carriers.
These aliases will be used throughout MobileCast when tracking loads.
Step 2: Choose the desired load options; a check indicates the option is selected. The
options are explained below.
Default Reference ID and Descriptionlets you choose to pre-fill the
Reference ID and Description fields on the Add Load window. The Reference ID
will be filled with the destinations description and phone number, while the
Description will be filled with the customer commodity and city of the destination
location. This information will be automatically entered when the load destination
and customer commodity are selected.
890

Default Customer Commoditylets you choose whether the customer

commodity fields on the Load Stop window will be pre-filled with the first entry
in the list or not.
Default Detail Consignee to Bill Tolets you choose to pre-fill the Consignee
on the Add Load window with the load customer selected as the Bill To.
Default Bill To to Detail Consigneelets you choose to pre-fill the Bill To
Customer on the Add Load window with the load customer selected as the
Consignee.
Load Admin Default Access to All Regionsallows you to choose whether the
default is for a new load to be available to all regions or to no regions. Individual
regions can be selected or deselected when the load is added.
Equipment Handlingallows you to choose whether the equipment is
automatically transferred to a route, common carrier, or region with the load. If
checked, you are asked about the equipment each time the load is transferred; if
not checked the equipment is automatically transferred with the load.
Step 3: Enter the prefix that will be placed in front of all load locations. This prefix will
automatically appear in the ID field when adding a location; you can change it at
that point if necessary. If Auto Generate Route ID is selected on the Dispatch General page, the prefix will be used in the route ID when a new route is created.
This option is only available if you have load admin rights.
Step 4: Click on the Default Location Type arrow to select the type for locations added
when load locations are added.
Operations Guide
891
User Rights
A user might have access to all, some, or none of MobileCasts load management
features. Load management rights are assigned in the Administration module, just like
any other rights in MobileCast.
There are two levels of load rights:
Load UserIn the Maintenance module, load users can add and change load
customers and load locations. In the Dispatcher modules Available list, an
authorized load user can create new loads, see loads others have created, and see
loads transferred from other regions. In the Active list, load users can see loads they
have claimed or assigned.
Load AdminIn the Maintenance module, load admins have all of the rights of load
users, plus the ability to create and change customer commodities, STCC codes,
freight classes, common carriers, and load types. In the Dispatcher module, load
admins have all of the rights of load users, plus the ability to see all loads for all
regions, whether or not they would ordinarily have rights to the regions. However,
load admins can make changes only to loads that have been claimed by their own
region(s).
Adding or Changing Load Rights
At any time you can change a users load rights. Load rights can vary from user to user:
you can choose to give a user no rights, user rights, or admin rights.
Step 2: Click on the List menu, then select Privileges. The Privileges window opens,
listing all current privileges. Double-click the privilege whose permissions you
want to review.
Step 3: To give a user load rights, check Can use loads in the Permissions list.
To give a user load admin rights, check Can administer loads in the Permissions
list.
Once the privilege has been updated to include the proper load permissions, all users
associated with that privilege will automatically be updated.
892

Working with Load Customers

Load Customers are the companies to bill for loads, or the shipper or consignee for loads.
They are entered in the Maintenance module by either a Load User or a Load Admin. You
must have at least one load customer set up before you can start creating loads. Each
region has its own list of load customers, but you can choose to let other MobileCast
regions use a load customer when you create it.
Step 2: Click List, Load, then select Customers. The Load Customer window opens,
listing all existing load customers for the MobileCast region.
Step 3: Click the Add icon from the Load Customer window or press the [Insert] key.
Step 4: Complete the boxes of the Add Load Customer window. MobileCast
automatically enters the ID; the remaining information is optional. If entering
address information, enter the mailing address, not the street address.
Hint: Since MobileCast chooses the ID for the load customer, it is recommended that
you enter a name that is meaningful to your organization, rather than leaving that
information blank.
Load customers can

be used as the bill to,
shipper, or consignee
when you are creating
a load.
Step 5: To enter any instructions, user-defined field information, or if you want to make
the load customer visible to other regions, click the Advanced tab. Enter the
instructions or user-defined field information. To allow other regions to use the
load customer, click the first one you want to share with in the Shared by Regions
list at the bottom of the window, then [Ctrl]+click any others.
Operations Guide
893
Maintenance List Load Customers Add icon ([Insert]) Save icon ([Ctrl]+[S])
894

Working with Load Locations

Load locations are set up much like the stop locations (DPTs, SITs, etc.) that make up
normal routes. However, they do have differences. Load locations are entered and stored
in a list of their own, apart from other types of locations. To help distinguish load
locations, you can create a load location prefix that will appear at the beginning of the ID
for all load locations. The load location prefix is established on the Loads page of the
Options notebook in the Maintenance module. Load locations also have their own stop
type, LD, that is automatically applied when you create a load location. When creating
load locations, you can have MobileCast automatically create a corresponding location by
checking Create Location for Load Locations.
If you know ahead of time where you will be picking up, transferring, and delivering
loads, you can create load locations in the Maintenance module. Otherwise, you can
create them when you create a load. In either case, the steps are the same.
Warning: If you want to use an existing regular location on a load, you need to re-create
it as a load location by clicking Locations on the Load menu.
Step 1: In the Maintenance module, click List, Load, then Locations. Click the Add icon
on the Load Locations window or press the [Insert] key. The Add Load Location
window opens.
The Add Load

Location window is
a simplified version
of the regular Add
Location window.
Step 2: For the (mandatory) ID, enter up to 15 letters and/or numbers, or accept the prefilled ID. The ID is automatically entered in uppercase. If a load prefix was
defined on the Loads page of the Options notebook in the Maintenance module, it
will be pre-filled here.
Operations Guide
895
Step 3: Enter a description for the location, such as the name, the default service time
for the location in minutes in the Service Time text box, and select the time zone
the locations times will be reported in from the Time Zone drop-down list.
Step 4: Type as much of the address as you know, so that MobileCast can geocode it for
you, or click the Map tab and geocode the location yourself.
Maintenance List Load Locations Add icon ([Insert]) Save icon ([Ctrl]+[S])
896

Working with Customer Commodities, STCC Codes, Freight Classes,

Common Carriers, and Load Types
Customer commodities, STCC codes, freight classes, common carriers, and load types
can only be created or edited in the Maintenance module by someone with Load Admin
rights. Once created, STCC codes, freight classes, common carriers, and load types are
automatically available to all regions in the system; customer commodities are specific to
each region.
You must create one customer commodity for each region you are tracking loads for, but
you do not have to set up the remaining load items in order to use MobileCasts load
management features. They are optional items designed to provide you with more
information, if you want it.
Load-related items include those things that directly related to loads, such as customer
commodity codes, STCC codes, freight classes, common carriers, and load types. These
items are created in the Maintenance module.
Step 2: Click List, Load, then select the desired menu item: Customer Commodities,
STCC Codes, Freight Classes, Common Carriers, or Types.
Step 3: Click the Add icon on the list window that appears or press the [Insert] key.
Step 4: Fill in the fields for the item you want to create. The mandatory fields for each
item are listed, with the maximum length of the field:
Item
Mandatory
Field(s)
Max.
Length
Customer Commodity
Customer
Commodity
Description
128
STCC Code
Description
128
Class
10
Description
128
Load Type
Load Type
Common Carrier
ID
15
STCC Codes
Freight Classes
Step 5: Click the Save icon, or press [Ctrl]+[S] to save the information. The Add
window stays open, ready for you to enter additional items. When you are
finished, click the Close box to close the Add window.
Operations Guide
897
Managing Loads
There are many ways you can use MobileCast to manage your loads, but four typical
scenarios cover most instances. Each of these scenarios is discussed below, with
references to more detailed information on completing the parts of the scenario.
Claim a load created elsewhere, assign it to a route
The most common example of managing loads is to claim an existing load and assign it
to a route. The load could be created by a load administrator or another load user; whoever
creates the load needs to grant you access to it. For instance, if your organization has a
load administrator who enters loads, and you have a truck that has a long drive back from
its final stop, you could claim an available load and assign it to that route. You can claim
any load that appears in your Loads - Available window.
Follow these steps to complete this example:
Claim the load
Assign the load to a route
Complete the load stops
Create a load, assign it to a route
Another common example of managing loads is to create a load, claim it yourself, and
assign it to a route. For instance, suppose you know of a load that is waiting near a stop
on one of your regular routes. You could enter the load, claim it yourself, and assign it to
the route.
Create the load
Claim the load
Relay a claimed load to another route
Sometimes you might need to use multiple routes to complete a load. For instance,
suppose one route passes near the loads pickup location, but the loads delivery location
takes the route far off course. However, you have another route that passes the loads
delivery location. You can set up a meet point for the two routes, and use two routes to
complete the load.
Create the load
898

Claim the load
Relay the load to another route
Transfer a claimed load to another region
There might be times when one or more MobileCast regions need to work together to
complete a load. For instance, you have a load that you can pick up, but you cant deliver
it within the required time frame. However, you know that another MobileCast region can
deliver the load on time. You can create the load, set up a meet point to meet the other
regions equipment, and transfer the load. Once the load is transferred to another region,
that region must manage the load. The region can transfer the load to another route,
another region, or a common carrier, complete the stops, or do whatever is necessary to
complete the load.
Create the load
Claim the load
Relay the load to another route
Relay the load to another region
Transfer a claimed load to a common carrier
You might decide that a common carrier can complete a claimed load more quickly and
cost effectively than you can. In these cases, you can transfer a claimed load to a common
carrier to complete for you.
When you transfer a load to a common carrier, MobileCast creates a route for the load.
To run a common carrier route, turn off the Equipment and Driver Assignment Required
options on the Assignments for Route notebook. You have the option to record other
information, such as load details and mileage, if you want.
Create the load (optional)
Claim the load
Relay the load to a common carrier
Operations Guide
899
Creating the Load

You can create a load for yourself, or you can create loads that other regions can see and
claim. The load you create will either be a simple load or a complex load; the difference
is that a simple load can contain one customer commodity and two stopsa pickup
location and a delivery locationwhereas, a complex load contains multiple customer
commodities and stops. In order to create a load, you must assign a pickup and delivery
location, a customer commodity code, and a Bill To. All other information is optional.
window opens.
Step 2: Click on the Loads menu, then click Available. The Loads Available window
opens, listing all available loads.
Step 3: Click the Add icon or press the [Insert] key. The Add Load window opens. The
Add Load window is a notebook with three pages. Each load must be assigned a
Bill To, a customer commodity code and an origin and destination; the remaining
information is optional.
Use the Add Load window to add a simple or complex load. For a complex load
requiring more than two stops, click on the Add icon in the Stops section to add stops.
Step 4: In the Date field, enter the date for the load. You can also select the date from
the calendar by clicking the down arrow.
Step 5: A unique ID is automatically assigned to the load. To assign a reference you can
use to track the load, enter it in the Reference ID field. If there is a purchase order
number associated with the load, enter it in the PO# field, and enter a
900

Description, if desired. You can use letters, numbers, spaces, and punctuation
marks.
Step 6: Click the Type arrow to open a list of the Load Types. The Lookup Load Type
window opens. Double-click the desired type, or click it, then on the Process
icon. The Lookup Load Type window closes.
Step 7: Select a load customer to bill the load to. Click the arrow on the Bill To field to
open a list of the load customers. The Bill To window opens.
To search for a specific load customer for the Bill To, click the [Query] button.
Double-click the desired load customer, or click it and then click the Process icon.
Use the [Query] or [New] button to
enter your Bill To information.
To create a new load customer for the Bill To, click the [New] button. The Add
Load Customer window opens. For more information on entering information in
the Add Load Customer window, see Working with Load Customers.
Step 8: In the Total field, enter the amount of money you will make by transporting the
load. Use the Split field to enter the dollar amount to be split for the load, or use
the Split % field to enter the percentage of the load revenue you want to split.
Once you fill either the Split or Split % field, the other will automatically fill to
reflect your calculation.
Step 9: In the Commodity Codes section, click the down arrows to open Lookup
windows for customer commodity codes, STCCs, and freight classes. From each
Lookup window, double-click on the appropriate commodity, or select it and
click on the Process icon. You must select at least one commodity code.
Step 10: To select the pickup location (origin) and delivery stop location (destination),
click on the appropriate Location down arrow to open the Select Load Origin or
the Select Load Destination window.
If you know the ID of the location, enter it in the ID field.
If you dont know the ID, enter as much of it as you know followed by an asterisk
(*) and click the [Query] button. To list all load locations, click [Query].
If the load location does not exist, click the [New] button.
Note: You can add more stops to the load, if necessary. See Adding Load Stops for more
information.
Step 11: In the Pickup Stop Location section, click the Shipper arrow to open the
Lookup Load Customers window. Double-click on the appropriate shipper, or
select it and click on the Process icon. If there is a reference number associated
with the shipper, enter it in the Shipper Ref # field.
Operations Guide
901
Step 12: If the consignee is different from the Bill to, enter it in the Delivery Stop
Location section. Click the Consignee down arrow to open the Lookup Load
Customers window. Double-click on the appropriate consignee, or select it and
click on the Process icon. If there is a reference number associated with the
consignee, enter it in the Consignee Ref # field.
Step 13: In the Planned Temperature Information for Delivery Stop section, enter the
planned pulp low and high temperatures, the planned temperature setting, and the
planned temperature reading.
Step 14: If there are special instructions or user-defined fields for the load, click the
Advanced tab to enter them.
Step 15: To select the other MobileCast regions who have access to the load, click on
the Access tab. Regions with rights to the load are highlighted in the list. Click to
add or remove regions from the access list.
Step 16: Click the Save icon, or press [Ctrl]+[S] to save all the load information.
Step 17: Continue creating loads as needed. When all loads have been created, click the
Close box to close the Add Load notebook.
Dispatcher Loads Available Add icon ([Insert]) Save icon ([Ctrl]+[S])
902

Adding Load Stops

In many cases, a load simply consists of an origin and a destination, which can be added
directly from the Add Load window. However, there may be times when you need more
stops on a load. MobileCast allows you to add stops to existing loads, or add the stops as
the loads are created. In both cases, the same process is used. The load stops will be added
to the load in the order added, but can be resequenced as needed.
window opens.
Step 2: Click on the Loads menu, then click Available. The Loads Available window
Step 3: Double-click an existing load, or click the Add icon to create a new load. The
Add Load window opens. The Add Load window is a notebook with three pages.
Each load must be assigned a Bill To, a customer commodity code and an origin
and destination; the remaining information is optional.
Use the Add Load Stop(s) window to add as many stops as necessary to a
load.
Step 4: In the Stops section of the Add Load window, click the Add icon or press the
[Insert] key to open the Add Load Stop(s) window. The Add Load Stop window
opens.
Step 5: Choose the load location. Double-click the desired location to select it. Enter
the amount of time needed at the stop in the Service Time field. If no value is
entered, the load locations service time will be used.
If you know the ID of the load location, enter it in the ID field.
Operations Guide
903
If you dont know the ID, enter as much of it as you know in the ID field,
followed by an asterisk (*) and click the [Query] button. To list all load locations,
click [Query].
If the load location does not exist, click the [New] button. See Working with
Load Locations for more information.
Step 6: Enter the time window and time zone for the stop. Check the appropriate
box(es) to indicate if the stop is billable, payable, or both.
Step 7: Enter the detail information for the stop. You can have multiple pickups and
deliveries for a load stop. Click the Add Stop Detail icon to save the detail
information.
In the Type area, select whether the detail is for a pickup or a delivery.
Enter the Shipper (for pickup) or Consignee (for delivery) information.
Select the shipper or consignee, and enter the reference number and seal if
applicable.
Step 8: Enter the Commodity Code information. A customer commodity must be
entered; STCC and freight class information is optional. Click on the arrow to
open a list of the specific commodity codes; double-click on a code to select it. If
a commodity code is already in the field and you want to change it, delete the
existing code before clicking the arrow to open the list of codes.
Enter the planned quantities for the selected commodity codes.
Enter the temperature information for the product, if desired.
Step 9: When all the information is complete, click the Add Stop icon to save the stop
information and add another stop.
Step 10: Repeat as necessary to create all needed load stops. At least one pickup and
one delivery are required. When the last load stop is entered, click the Save icon
or press [Ctrl]+[S] to close the Load Stop window and return to the Load Stop
window.
Dispatcher Loads Available Load Add Detail icon Add Load Stops Save icon
([Ctrl]+[S])
904

Claiming a Load
You can claim a load from the Loads - Available window. Claiming a load means that you
accept responsibility for the load being picked up and reaching its destination within the
required time frame. However, you do not actually need to transport the load yourself; you
can claim the load and transfer it to a common carrier, or you can transport the load part
of the way and then transfer it to another region.
window opens.
Step 2: Click on the Loads menu, then click Available. The Loads - Available window
Step 3: Right-click the load in the Loads - Available window and select Claim from the
menu that pops up. The loads Phase changes to Claimed, and the load moves to
your Loads - Active window.
Once you have claimed a load, you can assign it to a new or existing route, or transfer it
to a common carrier. See Assigning the Load to an Existing Route, Assigning the Load to
a New Route, or Assigning the Load to a Common Carrier for more information.
Dispatcher Loads Available Claim
Operations Guide
905
Assigning the Load

You can create loads yourself and then assign them, or you can assign loads someone else
created and gave you access to. When a load is assigned, it means that provisions have
been made to transport it to its destination. You can assign a load to an existing route,
create a new route for it, or assign it to a common carrier.
Hint: Once a load has been assigned, whether to a route or to a common carrier, you can
see a summary of it that provides details on its locations and routes. Right-click
the load in the Loads Active or Loads Query window, then click Summary
from the menu that pops up.
Click the Close box when you are finished viewing the Summary for Load
window that is displayed.
Assigning the Load to an Existing Route
When a load is assigned to an existing route, MobileCast automatically places it at the end
of the route. Once the load has been added to the route, the stops can be Resequence, if
necessary. Loads can only be added to dedicated routes. If Load Equipment Handling is
turned on in the Loads page of the Options notebook in the Maintenance module, you can
choose whether any equipment already assigned to the route should be used for the load.
window opens.
Step 2: Click on the Loads menu, then click Available or Active. The Loads window
opens, listing all current items.
Step 3: Right-click the load in the Loads - Available or Loads - Active window. Select
Assign to, then Existing Route from the menu that pops up. The Assign Existing
Route window opens.
Step 4: Enter the search information for the desired route and click the Search icon.
You can search for a route based on known information, such as the departure
date, route ID, other loads, or driver or equipment assigned to the route. Click the
appropriate notebook tab and enter the search information for the route, then click
the Search icon.
Step 5: The routes that match the search criteria appear in the list. Double-click the
desired route, or click the route and then click the Process icon.
The Assign Existing Route window closes the Select Load Equipment for Route
window opens. Select the route equipment to use for the load, and click the
Process icon. The Load Assignment window opens. From here you can sequence
the stops or transfer the load as needed.See Relaying the Load to Another Route,
906

Transferring the Load to a Common Carrier, or Transferring the Load to Another

Region for more information.
All the routes for

November 11, 2009 are
listed; double-click a
route to assign the load
to it.
Step 6: Click the Save icon, or press [Ctrl]+[S] to save the information. The load status
changes to Assigned in the Loads - Active window.
Note: Once a route is assigned, you need to delete the relay on the Load Assignment
window to return the route to Claimed before it can be returned to the Available
list.
Dispatcher Loads Available/Active Assign to Existing Route Save icon
([Ctrl]+[S])
Assigning the Load to a New Route
When you create a new route for a load, the last delivery location for the load is
automatically the destination for the route. Additional stops can be added to the route; see
Adding, Changing, Deleting, or Unassigning Stops on a Route for more information.
window opens.
Step 3: Right-click the load in the Loads - Available or Loads - Active window and
select Assign to, then New Route, from the menu that pops up. The Add Route
window opens.
Operations Guide
907
Step 4: Enter the route ID, date, and other information.
When creating a route for a load, the route ID can be different than the loads ID. To
see the load IDs of the first and last load locations on a route, click Show Details
from a route menu and select the Origin Load ID and Destination Load ID columns.
Step 5: Select the Origin for the route. If you dont know the ID of the origin, select the
type and enter as much of the ID as you know followed by an asterisk (*) and
click the [Query] button. Double-click the origin in the list that appears, or click
it, then click the Process icon.
Note: The destination for the route is automatically the last delivery location for the load.
Step 6: Enter the time window and other route information, as desired.
Step 7: Click the Save icon, or press [Ctrl]+[S] to save the route, then click the [Yes]
button to verify the new route. The Load Assignment window opens, showing all
the stops on the route. From here you can sequence the stops or transfer the load
as needed. See Relaying the Load to Another Route, Transferring the Load to a
Common Carrier, or Transferring the Load to Another Region for more
information.
Step 8: Click the Save icon, or press [Ctrl]+[S] to save the information. The load phase
changes to Assigned in the Loads - Active window.
Dispatcher Loads Available/Active Assign to New Route Save icon ([Ctrl]+[S])
908

Assigning the Load to a Common Carrier
At times when it is less convenient or cost effective to assign a load within your
organization, you can choose to assign the load to a common carrier. A common carrier
is an outside company that can be used by all regions. Load admins can add common
carriers in the Maintenance module.
window opens.
opens.
Step 3: Right-click the load in the Loads - Available or Loads - Active window and
select Assign to, then Common Carrier from the menu that pops up. The Assign
Common Carrier window opens, listing the available common carriers.
Double-click a
common carrier to
assign it to a load.
Step 4: Double-click the common carrier, or click the carrier and then click the Process
icon. The Add Route window opens.
Step 5: Enter the unique ID for the route.
Operations Guide
909
Step 6: Enter the departure date for the route. The Origin and Destination are already
entered as the first pickup and final delivery locations for the load.
The origin and destination for the route are automatically entered as the first pickup
and final delivery locations.
Step 7: The remaining route information is optional. Enter the desired information and
click the Save icon, then click the [Yes] button to verify that you want to save the
route. The Load Assignment window opens, showing all the stops on the route.
From here you can sequence the stops or transfer the load as needed. See
Relaying the Load to Another Route, Transferring the Load to a Common
Carrier, or Transferring the Load to Another Region for more information.
Step 8: Click the Save icon. The load status changes to Assigned in the Loads - Active
window.
Dispatcher Loads Available/Active Assign to Common Carrier Save icon
([Ctrl]+[S])
910

Completing a Load Stop

Once the load is assigned to a route, the load stops can be completed using the normal
procedure for completing a stop.
window opens.
Step 2: From an Overview or list window in Dispatcher, right-click on the route. (If
necessary, use the Route Query to find the route.) Click Stop Complete from the
menu. The Stop Complete for Route window opens with the next stop to be
From the Route Summary window in Dispatcher, find the route by searching
with the Route Date boxes, if necessary. Double-click the Stops bar for the route.
The Stop Complete for Route window opens with the next stop to be completed
highlighted.
To change the information for a load stop, click the [Load Info] button.
Step 3: If necessary, change the dates and/or times when the route actually arrived or
left the stop.
To change the date, click the drop-down arrow next to the date and time and
select the desired date from the calendar that opens, or type the new date.
To change the time, click the hour or minutes and use the small arrows to change
the time, or type the new time.
Operations Guide
911
To set the Arrival or Departure to the current date and time, click the [Now]
button.
Step 4: If desired, select a reason for the change from the Delay Type drop-down box,
and enter the number of delay minutes to record for reporting purposes in the
Delay Mins box.
Step 5: If necessary, change the actual miles to the stop.
Step 6: To edit the load stop information, click the [Load Info] button. The Edit Load
Stop window opens. You can change the commodity codes, actual quantities,
time window information, and the actual temperatures. Once the load stop
information is correct, click the Save icon or press [Ctrl]+[S]; the Load Stop
window closes.
Note: If there are multiple line items for the stop, make sure the correct line item is
selected in the list.
You can enter the actual temperature information and other details
for the load here.
Step 7: Click the [Complete] button to accept the information, then the Save icon or
press [Ctrl]+[S] to save it.
912

Dispatcher Overview/List/Route Summary window Stop Complete Complete/As

Projected Save icon ([Ctrl]+[S])
Operations Guide
913
Relaying the Load to Another Route

A load does not have to be completed by a single route; multiple routes can combine to
complete a load. In order to relay the load to another route, a meet point must be created
where the two routes exchange the load. If Load Equipment Handling is checked on the
Loads page of the Options notebook in the Maintenance module, you will be given the
option to select equipment to transfer with the load; if it is not checked, the equipment will
automatically be transferred with the load. A load can be relayed only to a dedicated route.
If an adequate route does not exist, you can create a new route to relay the load to.
window opens.
Step 2: Click on the Loads menu, then click Active. The LoadsActive window
opens, listing all active loads.
Step 3: Right-click the load in the LoadsActive window and select Edit Relays from
the menu that pops up. The Load Assignment window opens, listing all the stops
on the load.
Step 4: Click the load stop you want to follow the meet point, then the Add Relay icon.
The Load Relay window opens.
Use the Load Relay window to choose a specific route or to create a

new route to relay the load to.
Step 5: Select the route to relay the load to. All uncompleted routes are listed in the
window. Click on a route to select it.
Step 6: To search for a specific route, use the search feature; enter the search
information for the desired route and click the Search icon. The routes meeting
the search criteria are listed. Click on a route to select it.
914

Step 7: Enter the ID of the meet point. The meet point is considered a load location.
If you dont know the ID of the location, enter as much as you know, followed
by an asterisk (*) and click the [Query] button. Double-click the meet point from
the list that appears, or click it, then click the Process icon.
To add a new load location as the meet point, click the [New] button. See
Working with Load Locations for more information.
To see the location of the meet point and determine if it is near the route, click
the [Show] button. The map zooms to the meet point, which appears as a landmark
on the map.
Step 8: If you need to create a new route to relay the load to, click the [New] button.
The Add Route notebook opens.
Step 9: Click the [OK] button. The Load Relay window closes, and the Select Load
Equipment window appears, if you have Equipment Handling checked on the
Loads page of the Options notebook in the Maintenance module. Choose the
equipment to transfer with the load and click the Process icon. The Load
Assignment window appears, with a separate notebook tab with information for
the new route.
Step 10: Click the Save icon or press [Ctrl]+[S] to save the information. The Load
Assignment window closes.
Note: To return a load from a route, right-click the load and select Edit Relays from the
menu that pops up. With the last route visible in the Load Assignments window,
click the Delete Relays icon. That route is deleted from the load.
Dispatcher Loads Active Edit Relays Add Relay icon Route [OK] Save
icon ([Ctrl]+[S])
Operations Guide
915
Transferring the Load to a Common Carrier

There might be times when you have claimed a load, but do not have the equipment or
personnel to deliver it to its final destination within the required time window. In such
cases, you can transfer the load to a common carrier to transport it for you. If Load
Equipment Handling is checked on the Loads page of the Options notebook in the
Maintenance module, you will be given the option to select equipment to transfer with the
load; if it is not checked the equipment will automatically be transferred with the load. For
more information on transferring loads, see Transferring the Load to another Region.
window opens.
opens.
the menu that pops up. The Load Assignment window opens, listing all the loads
stops.
Step 4: Click the load stop that should follow the meet point, then click the Add Relay
icon. The Load Relay window opens.
Step 5: Click Carrier to open a list of available common carriers. Click on a carrier to
select it.
If you dont see the common carrier you want in the list, you can
search for it and MobileCast will find it for you.
916

To search for the carrier, click the check boxes of the items to search for, then
enter the search criteria. Click the Search icon. Carriers meeting the search criteria
appear in the list.
Step 6: Enter the ID of the load location of the meet point.
by an asterisk (*), and click the [Query] button. Double-click the meet point from
the list that appears, or click it, then click the Process icon.
To see the location of the meet point, click the [Show] button. The map zooms
to the meet point, which appears as a landmark on the map.
the carrier.
Step 8: Click the Save icon, or press [Ctrl]+[S] to save the information. The Load
Note: To retrieve the load from the carrier, right-click the load and select Edit Relays
from the menu that pops up. Click the Delete Relay icon, then the Save icon.
Dispatcher Loads Active Edit Relays Add Relay icon Carrier [OK] Save
icon ([Ctrl]+[S])
Operations Guide
917
Transferring the Load to Another Region

You can transfer an assigned load to another region to complete. Once the load is
transferred to the other region, you no longer have control of the load; the other region is
responsible for completing the loads stops. Loads can only be transferred to regions who
have access to them. If Load Equipment Handling is checked on the Loads page of the
Options notebook in the Maintenance module, you will be given the option to select
equipment to transfer with the load; if it is not checked the equipment will automatically
be transferred with the load.
window opens.
opens, listing all active loads.
the menu that pops up. The Load Assignment window opens, listing all the stops
on the load.
Step 4: Click the load stop you want to follow the meet point, then click the Add Relay
icon. The Load Relay window opens.
Step 5: Click Region to open a list of available MobileCast regions. Click on a region
to select it.
Only customers who were given access to the load are listed in the
Load Relay window.
Step 6: Enter the ID of the location that will be the meet point.
918

by an asterisk (*), then click the [Query] button. Double-click the meet point from
the list that appears, or click it, then click on the Process icon.
To see the location of the meet point, click the [Show] button. The map zooms
to the meet point, which appears as a landmark on the map.
the region.
Step 8: Click the Save icon, or press [Ctrl]+[S] to save the information. The Load
Note: Once the load has been transferred to another region, you cannot retrieve it; the
other region must return the load to you.
Dispatcher Loads Active Edit Relay Region [OK] Save icon ([Ctrl]+[S])
Operations Guide
919
Editing a Load
When you edit a load, you can change the revenue, the Bill To information, the userdefined fields, or special instructions, or load details such as quantities. A load can be
edited by either a load user or a load admin, but it can only be edited from the region where
it was created. Once a load is assigned, you cannot edit the load stops.
window opens.
Step 3: Double-click the load in the LoadsActive or LoadsAvailable window. The
Edit Loads window opens.
You can change the description, reference ID, or Bill To from this window.
Step 4: Edit the load as necessary.

To change the Bill To, click the arrow. The Bill To window opens. To search for
a specific load customer for the Bill To, click the [Query] button. Double-click the
desired load customer, or click it and then click the Process icon. To create a new
load customer for the Bill To, click the [New] button. The Add Load Customer
window opens. For more information on entering information in the Add Load
Customer window, see Working with Load Customers.
To change the reference ID, description, or revenue information, enter the
new information in the field.
To change the special instructions or user-defined field information, click the
Advanced tab. Enter the new information.
920

To change the quantities, double-click on the stop; the Load Stop window opens
in detail mode. Click on the line item to work with, make the necessary changes,
then click on the Save icon.
Note: Once the load has been assigned the planned quantities cannot be altered.
Step 5: Click the Save icon, or press [Ctrl]+[S] to save the changes. The Edit Loads
window closes.
Dispatcher Loads Available/Active Save icon ([Ctrl]+[S])
Operations Guide
921
Searching for Loads

MobileCast includes two separate features you can use to locate loads in the system. You
can use the Route Query to determine which route(s) a load is assigned to, or you can use
the Load Query to find any load, including completed loads.
Searching for Completed Loads
The Load Query lets you search for any loads in MobileCast that you ever had access to,
including completed loads. To search for loads on routes, see Searching for Loads on
Routes.
window opens.
Step 2: Click on the Loads menu, then click Query. The Loads-Query window opens.
Step 3: Click the boxes for the items to search for, then enter the search criteria.
You can use the load query feature to search for loads that are completed.
Step 4: Click the Search icon. The loads meeting the search criteria appear in the
window.
Dispatcher Loads Query Search icon
Searching for Loads on Routes
You can use MobileCasts Route Query feature to determine which route a load is
assigned to. See Finding a Route for more information on using the Route Query. To
search for completed loads, see Searching for Completed Loads.
window opens.
Step 2: Click on the Routes menu, then click Query. The Route Query window opens.
922

Step 3: Click the Load tab.
You can use the Route Query to find which route a load was assigned to.
Step 4: Click the boxes for the items to search for, then enter the search criteria.
Step 5: Click the Search icon. A list of routes meeting the search criteria appears in the
window.
Dispatcher Routes Query Load tab Search icon
Operations Guide
923
Canceling a Load
There may be times when you cant run a load, but want to keep it in the MobileCast
system for future reference, or to clone it to make a future load. In these cases, you can
cancel the load; canceled loads will not appear in the Loads Active or Loads Available
window, but you can query to find them.
window opens.
Step 2: Click on the Loads menu, then select either Active or Available. The Loads
Active or Loads Available window opens, listing all current items.
Step 3: Right-click on the load and select Cancel from the menu that pops up.
Dispatcher Loads Active Cancel
924

Returning a Load to the Available List

There may be times when you claim a load, only to discover that due to changing
circumstances, you cannot run it. In these cases, you can return the load to the Loads Available list, where someone else can claim it. If Load Equipment Handling is selected
on the Loads page of the Options notebook in the Maintenance module, you can choose
whether the equipment is transferred with the load or not; if this option is not selected, the
equipment automatically transfers with the load.
Notes: A load must be in the Claimed phase to be returned. If the load has been transferred
to a carrier or assigned to a route(s), the relays must be deleted. Click the load and
select Edit Relays from the menu that pops up. In the Load Assignments window,
click the Delete Relay icon. When all relays have been deleted, the load returns to
Claimed.
If you transferred a load to another region, you cannot edit the relay. The region
you transferred the route to must return it to you, after deleting the relays, if
necessary. The returned route is set back to the Assigned phase in your Active list.
window opens.
Step 2: Click on the Loads menu, then click Active. The Loads - Active window opens,
listing all active loads.
Step 3: Right-click the claimed load and select Return from the menu that pops up.
MobileCast removes the load from the Loads - Active window and places it in
the Loads - Available window.
Dispatcher Loads Active Return
Operations Guide
925
926

Reports
Working with Reports

One of the most useful features in the Roadnet Transportation Suite is the ability to
generate and print any number of informative reports. These reports provide you and your
employees with information on your routes, warehouses, and territories, as well as
loading diagrams.
Roadnet comes with reports about the routes that you can give the drivers, as well as
management reports that can be used to evaluate the efficiency of your routes. Some of
these reports are: driver manifests and itineraries, actual vs. planned service and travel
times, location returns, location delivery costs, open/close time and time window
performance, resource utilization, and the driver performance.
FleetLoader comes with several reports that can help warehouse personnel load the truck,
as well as help the driver to locate the product at each stop. The Load Truck Diagram
shows the warehouse personnel how to load the truck, while the Load Validation Diagram
lets the driver verify where the product is on the truck and the quantity of each SKU on
the truck. The driver can also use the Stop List to determine where all the products for
each stop are located on the truck. The Load Productivity and Driver Productivity reports
let you track the productivity of your employees. These and the other FleetLoader reports
provide many options for how you want to view your loaded trucks.
Territory Planner lets you generate reports for designated territories and routes, allowing
you to analyze different aspects of your current or newly developed routes and territories.
The Global Itinerary and Global Manifest reports provide you with stop information; the
Re-Route Analysis report is a great tool for determining how a re-route will affect the
location and territory in a particular planning session; plus, there are several reports that
give you complete route-specific information. For more information, refer to the
descriptions for each report.
MobileCast comes standard with several reports that provide you and your employees
with information about the routes, the drivers, and the equipment used to run your routes.
The Delivery Detail report provides you with detailed delivery information, ranging from
a stop comparison to a thorough list of all your stops. The Equipment Utilization report
gives you a graph displaying the time of day your equipment was in use and the amount
of equipment used, while the Equipment Utilization Metrics report lists the equipment
used, the total amount of time, and percent of total working time it was used. The Location
Statistics report lists, by location, the number of deliveries, redeliveries, canceled/skipped
deliveries, average and maximum service time, plus the average and maximum time the
driver was late. MobileCast provides you with many other informative reports, such as
driver returns, driver statistics, driver utilization, notes, time window exception, route
exceptions, route metrics, route summary statistics, and route variance.
In addition to the Reports module, you can access the reports from the various editors. The
Roadnet Transportation Suite also allows you to create your own custom reports using
Crystal Reports. Once you create a report with the report writer and add it to the
Roadnet Transportation Suite, you can generate that report on command. With the
Operations Guide
927
Roadnet Transportation Suite, you can also conveniently group any number of reports
together for printing.
In this section, there are instructions on how to enter the Reports module, how to use the
Reports window to print or preview the reports, and how to use the view windows. Each
existing Roadnet Transportation Suite report is described with a brief explanation of its
contents, as well as general instructions on how to generate and print the report.
Notes: Instructions for printing and previewing reports are for the Reports module only.
Instructions for reports from other modules may be different and are included in
the appropriate module if needed.
Many of the reports have additional printing options associated with them. To
access these options, right-click on a report and select Options from the menu that
pops up. This option will be grayed out for ineligible reports. To see an
explanation of the options for a particular report, see the description for that report
in the Reports Listing section.
For a sample of each report, refer to the Report Samples section.
Operations Guide
928
Printing Reports
Printing Reports
The Roadnet Transportation Suite comes with many reports you can preview on the
screen or print directly to the printer. The report will be sent to the printer selected in the
Print Setup (File Print Setup).
Note: Some report entries may be truncated if the values are too long. For instance, if
the quantity for a session, territory, or week is greater than 9 digits, excluding any
decimals or commas, it will appear as #### on the report. If the quantity for a
route, stop, or location extension is greater than 7 digits, excluding any decimals
or commas, it will appear as ##### on the report.
Step 1: Click on the Reports icon to open the Reports module. The Reports module
opens, with the Reports window listing all available reports.
Step 2: Right-click on the report you want to print. A pop-up menu appears. Choose
Print Report from the pop-up menu. The Selection Criteria window opens.
To have a report sent directly to the printer, without viewing it on

the screen first, right-click on the report and select Print.
Note: You may have to run other program functions before printing some reports. See
the description for each report to determine if any preliminary steps are necessary
for that report.
Step 3: The information contained in the Selection Criteria window will vary according
to the report chosen. Make all necessary selections to set up your report. Then,
click [OK] to print the report.
Reports icon Reports window Print [OK]
Operations Guide
929
Previewing Reports
Previewing Reports
At times you may want to view a report before it is printed, especially if you are uncertain
how long the report will be or if the report contains the information you need. The
Roadnet Transportation Suite allows you to view reports before they are printed so that
you can limit or cancel the printing if necessary. You can preview the reports from either
the Reports module or the Planning Editor, Routing Editor, or Loading Editor. The
directions below explain how to preview the reports from the Reports module; the
procedures are the same to preview the reports from the Planning Editor, Routing Editor,
or Loading Editor.
Note: For a sample of each report, refer to the Report Samples section. For a sample of
each report, click on the report sample link in the report description section.
opens with the Reports window listing all available reports.
Step 2: Right-click on the report name you want to print. A pop-up menu appears.
Choose Preview Report from the pop-up menu. The Selection Criteria window
opens.
You can view a report on the screen to determine if it contains the information
you need before sending it to the printer.
Note: You may have to run other program functions before previewing some reports.
See the description for each report in the Roadnet Transportation Suite
Operations Guide to determine if any preliminary steps are necessary for that
report.
930

Previewing Reports
click [OK] to preview the report.
Step 4: Depending on the report you are previewing, one of two Selection Criteria
windows will open. Enter the dates for the range you want to view, and if
necessary select the routes. Click the [OK] button to preview the report.
Step 5: The report will open in a Report View Window. For more information on
navigating in the view windows, see Report View Windows.
Reports icon Reports window Preview [OK]
Operations Guide
931
Adding Reports
Adding Reports
The Roadnet Transportation Suite allows you to create your own custom reports using a
report writing tool, such as Crystal Reports. Once you create the report with the report
writer, you can add it and generate that report on command.
Important: Any reports you create must have an .rpt extension and must reside in the
same directory as your other reports.
opens with the Reports window lists all available reports.
Step 2: On the Reports window, click the Add icon, or press [Insert]. The Add Reports
window opens.
The reports that you add to the
must be placed in your reports
directory.
Step 3: Enter the Report Name, Description, and File Name for the report you have
created.
Step 4: Click the Save icon, or press [Ctrl]+[S] to save the report. Continue adding
reports as needed.
Step 5: When you have finished adding reports, click the Close box to return to the
Reports window.
Reports icon Reports window Add icon ([Insert]) Save ([Ctrl]+[S])
To edit the description or file name of an existing custom report, double-click on the
report in the list; the Edit Reports window opens. Make the necessary changes and click
on the Save icon or press [Ctrl]+[S].
To delete an existing custom report, click on the report and then click the Delete icon
([Delete]).
Existing reports can be edited or deleted as necessary. See Editing Items and Deleting
932

Grouping Reports
Grouping Reports
The Roadnet Transportation Suite gives you the option to group any number of reports
together so that they will print automatically when selected. For instance, if every day you
print the Driver Manifest, the Off Day Delivery, the Stop List Daily, and the Time
Window Exception reports you may choose to group those reports together so that you
can select the entire group as opposed to printing each report individually.
Step 2: From the Groups menu, select Configure. The Configure window opens. If you
have existing report groups, the configuration for the group shown in the Group
(modified) field is displayed.
Step 3: Click [New] to create a new group. All reports are moved to the Available
Reports list and the Group field at the bottom of the window becomes blank.
Note: To add a report group that is similar to another report group, click the Group arrow
at the bottom of the window and select the group you want as the source. Click the
[Save As] button and enter the name for the new group and click [OK]. The
Configure Report Groups window will now display the new group.
The Groups option lets you group reports that you print at the same time so that
you can simply select the group and print all the reports, rather than printing them
individually.
Step 4: In the Available Reports box, click on the reports you would like to add to your
group and drag them to the Preferred Reports box, or double-click on the report
to move it to the Preferred Reports box.
To move multiple reports simultaneously, select the reports in the Available
Reports box and drag them to the Preferred Reports box.
Step 5: Click the Collate check box to have the reports for a given route print all at
once. For example, if your report group is set to print the Manifest and Stop List
reports, and you select the Collate option, then your reports will print in route
Operations Guide
933
Grouping Reports
order. This means that a Manifest and a Stop List for route 1 will print
consecutively, then a Manifest and a Stop List for route 2, and so on.
Step 6: Once you have added all the desired reports, click [Save] to save your new
group. The Add Group window opens. Enter the name for your new report group
and click [OK].
Reports icon Groups Configure [OK]
Note: To delete a report group, make sure the correct group is displayed in the Group
field, then click the [Delete] button.
Editing Report Groups
Over time, you may need to change the reports that are included in the group to reflect
changes in your operation. You can easily add or remove reports from the group.
Step 2: From the Groups menu, select Configure. The Configure window opens.
Step 3: Click on the Group down arrow at the bottom of the window to select the group
you want to edit.
Step 4: Edit the group as necessary by selecting reports and dragging them either from
the Available Reports box to the Preferred Reports box to add reports to your
group(s), or from the Preferred Reports box to the Available Reports box to
remove reports from your group.
Note: You can also double-click on a report to move it from one list to another.
Step 5: Click [OK] to save the edited group.
Groups Configure [OK]
Deleting Report Groups
As you create new and different report groups, you may find that you no longer need all
of them. In that case you can delete the unneeded groups, which will shorten the list
presented on the Groups menu.
Step 2: From the Groups menu, select Configure. The Configure window opens.
Step 3: Click on the Group down arrow at the bottom of the window to select the group
you want to delete.
Step 4: Click the [Delete] button, then [OK] to confirm your deletion.
Groups Configure [Delete] [OK]
934

Printing Report Groups
Printing Report Groups

Once the report groups have been created, you can simply select the group you want to
print. After entering the date and other parameters needed for the reports, all the reports
are sent to the printer.
Step 2: From the Groups menu, select Print, then scroll to select the report group you
would like to print. The Selection Criteria window opens.
click [OK] to print the reports.
Reports icon Groups Print Name of Group [OK]
Notes: If you selected the Collate option when you configured your report group, then the
reports will print in route order.
If your report group contains plots, then you must print the report from the
Planning Editor.
Operations Guide
935
Report View Windows
Report View Windows

If you choose to preview a report before printing, it will open in a report view window.
From this window you can quickly scroll through the pages of the report. You can also
zoom in or out to make the report easier to read, export the report data to a file, or print
the report.
Number of
pages and
which page
you are
viewing.
Percent of
original
report size in
the view
screen.
To scroll through the pages of the report, click the scroll icons.
Icon
Description
First displays the top of the first page of the report.
Previous displays the previous page.
Next displays the following page.
Last displays the last page of the report.
To zoom the report display in or out, click the down arrow at the top of the report
window and choose a zoom level.
To export the report to a file, click the export icon and choose the format of the file and
destination. Then click [OK] to export or [Cancel] to abort.
Note: The Roadnet Transportation Suite does not support all the export formats, and
cannot guarantee the output of unsupported formats. The following formats are
supported: Acrobat Format (pdf), Rich Text Format (rtf), and HTML.
To print the report, click the Printer icon. Print all pages, one copy, and collate
the report are all default settings, which you may change as needed. Then click
[OK] to print or [Cancel] to abort.
936

Report View Windows
Report Listing
This section provides a description for each report in the Roadnet Transportation Suite,
including what each report displays, any steps you must take before printing, and how to
print. Some reports have additional options that you can access by right-clicking on the
report and selecting Options from the pop-up menu.
For samples of each report, refer to the Report Samples section.
All FleetLoader reports come with a standard header that shows the Route ID and date,
equipment ID, the total number and total weight of the units on the truck.
All Territory Planner reports come with a standard header that includes the time and date
printed, plus the total number of pages.
All MobileCast reports come with a standard header that includes the time and date
printed, plus the total number of pages.
Operations Guide
937
Working with the AVP Route Summary Report
Working with the AVP Route Summary Report

The AVP Route Summary report shows the planned and actual stops, total time, service
time, travel time, distances, sizes, breaks, and total costs for each completed route in the
selected period of time. The report also calculates the difference between the planned and
actual information, as well as the percentage the variance represents of the planned total.
A summary of all the routes is included at the end of the report. For information on the
individual stops, see the AVP Stop Detail report.
Note: Values in the cost fields have been rounded to the nearest whole number.
For a sample of this report, refer to the AVP Route Summary Report Sample.
Printing the Report
Step 1: Enter the Reports module. The Reports window opens.

Step 2: Right-click on the AVP Route Summary report in the Reports list window.
From the pop-up menu, select Preview Report to view the report before printing,
or select Print Report to print directly to the printer. The Selection Criteria
window opens.
Step 3: Enter the Begin Date and End Date to indicate the time span you want to
include in the report. You can enter the date manually, or click the arrow to open
a calendar. If entering manually, check the box before typing the date. If using the
calendar to change the month, use the arrows on the top of the calendar to scroll
Step 4: Click the [OK] button.Your report will either appear in Preview mode, or print
directly to your printer.
938

AVP Stop Detail
AVP Stop Detail

The AVP Stop Detail report provides actual and planned information for routes and the
individual stops on the route. For each stop, the planned and actual stop number, delivery
time, service time, distance, and delivery and pickup information is included. In addition,
the difference between the planned and actual items is displayed, along with the
percentage the variance is of the planned. A summary of all the stops is included at the
end of each route. The report also includes some information for the route: the planned
and actual start and completion times for the route are displayed on the report.
For a sample of this report, refer to the AVP Stop Detail Report Sample.
Printing the Report

Step 2: Right-click on the AVP Route Summary report in the Reports list window.
window opens.
Operations Guide
939
Actual vs. Planned Route Summary

Used with: Roadnet
The Actual vs. Planned Route Summary report lists the routes and the drivers for a
particular day. For each route, the report compares planned data for the route calculated
by Roadnet with actual data reported by drivers or an onboard computer system. The
report also calculates the amount of variance between planned and actual data, and
computes the percent of variance. For information on actual information for individual
stops, see the Actual vs. Planned Stop Detail report.
For a sample of this report, refer to the Actual vs. Planned Route Summary Report
Sample.
Printing the Report
Before you print this report, you need to import actual data from an onboard computer
system. See Importing OnBoard Data for more information. Or, you can manually enter
the actual data.
Step 2: Right-click on the Actual vs. Planned Route Summary report in the Reports list
window. From the pop-up menu, select Preview Report to view the report before
printing, or select Print Report to print directly to the printer. The Selection
Criteria window opens.
Step 4: Select the Routing Session(s) and Route(s) to include in the report.
Step 5: Click the [OK] button. Your report will either appear in Preview mode, or print
940

Actual vs. Planned Stop Detail

Used with: Roadnet
The Actual vs. Planned Stop Detail report includes the same actual and planned
information provided on the Actual vs. Planned Route Summary report, but on a stop-bystop basis. This means that for each route, the report compares planned data for the route
calculated by Roadnet with actual data reported by drivers or an onboard computer
system, and displays the amount of variance as well as the percent of variance. In addition,
this report displays pre- and post-route time, driver breaks/waits, and run time.
Notes: The times shown on this report are displayed using the locations time zone.
Values in the cost fields have been rounded to the nearest whole number.
For a sample of this report, refer to the Actual vs. Planned Stop Detail Report Sample.
Setting the Report Options
The Actual vs. Planned Stop Detail report also allows you to include actual, planned, and
variance information for each stop on the route, as well as for the route, or just for the
complete route. You can also choose to have break and wait information included on the
report.
Step 2: Right-click on the Actual vs. Planned Stop Detail report and select Options
from the menu that pops up. The Actual vs. Planned Stop Detail Options window
opens.
Step 3: Click to choose the options you want included on the report.
Choose to print a summary
or detailed report, and/or to
include break information.

Printing the Report
Before you print this report, you need to import actual data from an onboard computer
system. See Importing OnBoard Data for more information. Or, manually enter the actual
data.
Operations Guide
941

Step 2: Right-click on the Actual vs. Planned Stop Detail report in the Reports list
942

Working with the Carbon Emissions Report

You can use data from Territory Planner, Roadnet, or MobileCast when printing the
carbon emissions report. If you are using Roadnet or MobileCast data, you can choose
either planned or actual data. You can also select how the data is organized on the report,
such as reporting all the carbon emission data by equipment type or by date. The carbon
emission report includes the number of routes, stops, distance, size quantities, and carbon
output for the grouped item (equipment type, date, etc). The report also includes the
average carbon emissions per each item listed above - carbon emission per route, carbon
emission per stop, etc.
Note: If you are printing the Roadnet version of the report and using actual data, you
need to import actual data from an onboard computer or manually enter the actual
data.
For a sample of this report, refer to the Carbon Emissions Report Sample.
Setting the Options
Step 1: Click on the Reports icon to open the Reports module. The Report window
opens.
Step 2: Click on the List menu, then Reports. The Reports window opens.
Step 3: Right-click on the version of the carbon emission report you want to print and
select Options from the menu that opens. The Carbon Emission Report Options
window opens.
Choose the option of how to group the

report information.
Step 4: Click the Group By arrow and choose how you want the information grouped.
Step 5: If you are printing a Roadnet or MobileCast, check the Show Actual Data box if
you want to use actual data for the report. If this option is not checked, the
planned data will be reported.
Printing the Report
Step 1: Enter the Reports module. The Report window opens.

Step 2: Right-click on the Carbon Emissions report in the Reports list window. From
the pop-up menu, select Preview Report to view the report before printing, or
Operations Guide
943
select Print Report to print directly to the printer. The Selection Criteria window
opens.
Step 3: If you are printing a Roadnet or MobileCast report, enter the Begin Date and
End Date to indicate the time span you want to include in the report. You can
enter the date manually, or click the arrow to open a calendar. If entering
manually, check the box before typing the date. If using the calendar to change
the month, use the arrows on the top of the calendar to scroll through the months,
or click on the month and select from the menu that pops up. To change the year,
select it.
If you are printing a Territory Planner report, select the planning session you want
to include in the report.
944

Compartment Summary Report

Used with: Roadnet
The Compartment Summary Report lets you view how the compartments on your trucks
were loaded over a period of time. This report also allows you to view multiple routes for
a date range on one report. Information about the compartments, such as the quantity of
each size in each compartment and the total quantity of each size for the truck is provided.
Some other available route information includes: Route Start Time, Total Time (elapsed),
and Distance (traveled). This report is only valid when using compartment routing.
For a sample of this report, refer to Compartment Summary Report sample.
For more detailed report information on an individual route refer to the Compartment
Detail Report.
Printing the Report

Step 2: Right-click on the Compartment Summary report. From the pop-up menu,
select Preview Report to view the report before printing, or select Print Report to
print directly to the printer. The Selection Criteria window opens.
Operations Guide
945
Compartment Detail Report

Used with: Roadnet
The Compartment Detail Report lets you see the contents of each compartment of the
truck on a route. For each compartment, the report lists each SKU loaded in the
compartment and the quantity of each SKU. Some additional available Compartment
Detail Report information includes: Route Start Time, Total Time (elapsed), and Distance
(traveled). This report is only valid when using compartment routing.
Note: Compartment information is displayed only when there is one trip on a route.
When the route contains multiple reloads, the compartment information area of
this report is blank and the following message is displayed: "This route contains
reloads. Reloads are not represented on this report."
For a sample of this report, refer to the Compartment Detail Report sample.
Printing the Report

Step 2: Right-click on the Compartment Detail report. From the pop-up menu, select
Preview Report to view the report before printing, or select Print Report to print
directly to the printer. The Selection Criteria window opens.
946

Consolidated Off-Day Delivery and Less Than Minimum Stops Report

Used with: Roadnet
The Consolidated Off-Day Delivery and Less Than Minimum Stops report combines the
information given on the Off-Day Delivery Exception report and the Less Than Minimum
Stops report. For a selected routing session, this report lists any stop where the location is
being delivered to on a day that is not one of its regular delivery days and any stop whose
order quantities for any of the three size aliases total less than a user-defined minimum.
For instance, if you run the report for February 21, 2006 a Tuesday and Simons
Salon of Szechuans regular delivery days (set in location maintenance) are Monday and
Wednesday, Simons Salon of Szechuan will appear on the report. Simons Salon of
Szechuan would also appear on the report if you decide to use 25 cases as your minimum
stop size, and Simons Salon of Szechuan orders only total 14 cases.
This report is generated from information in Roadnet. For each stop listed, the report
shows the route ID, stop number, location ID, location type, location name, the sales
person for the location, and the size 1, size 2, and size 3 totals for the delivery. The report
also indicates the reason that each stop appears on the report it indicates whether each
stop is for a location scheduled on an off-day, has order quantities that total less than the
minimum, or both.
For a sample of this report, refer to the Consolidated Off-Day Delivery and Less Than
Minimum Stops Report Sample.

Step 2: Right-click on the Off Day Less Than Minimum report and select Options from
the menu that pops up. The Less Than Minimum Stops Options window opens.
Step 3: Enter the minimum quantities in the size fields. Any stops with less than these
quantities will appear on the report.
Step 4: In the Include area, select whether you want to include pickups, deliveries, or
both on the report. Orders of the selected type will be used to calculate the
quantities for the report.
Define the minimum quantities

for size 1, size 2, and/or size 3.

Operations Guide
947
Printing the Report
Step 1: Enter the Reports module.The Reports window opens.

Step 2: Right-click on the Off Day Less Than Minimum report in the Reports list
Step 4: Select the Routing Session(s) to include in the report.
948

Days Serviced
Days Serviced
The Days Serviced report pulls information from Territory Planner and includes the
location ID, location name, address, sizes 1, 2, and 3, delivery frequency, and days
serviced for selected planning session(s), territory(s), week(s), and day(s).
For a sample of this report, refer to the Days Serviced Report Sample.
The Days Serviced Options window lets you choose the style of report you want to print,
as well as the field the report is sorted by.
Step 2: Right-click on the Days Serviced report and select Options from the menu that
pops up. The Days Serviced Options window opens.
Step 3: From this window, you can choose to sort by location ID, location name, sizes
1, 2, and 3, or stop number, and whether you want to sort in ascending or
descending order. You can also choose whether to print the full report (contains
the complete address and daily quantities), or the condensed report (contains only
the street address and cycle quantities).
Click the drop-down arrow
to choose from a list of sort
options.
Choose to print either a full
or condensed report.

Printing the Report

Step 2: Right-click on the Days Serviced report. From the pop-up menu, select Preview
Report to view the report before printing, or select Print Report to print directly
to the printer. The Selection Criteria window opens. From this window, you are
able to set up your report.
Step 3: Select the Planning Session(s) and Territory(s) to be included in the report.
Step 4: Click the check box(es) that correspond to the week(s) and day(s) you want to
include in the report.
Operations Guide
949
Delivery Detail
Delivery Detail
For a selected period of time, the Delivery Detail report lists the information associated
with a delivery. This information includes the customer, route ID, stops, planned and
actual delivery, quantity, amount over, amount short, damaged items, planned and actual
pickup, and order totals. You can choose to generate the report listing only the stops with
differences or listing all of your stops information.
Note: A redelivered stop displays zero for planned stop quantities.
For a sample of this report, refer to the Delivery Detail Report Sample.
The Delivery Details Options window lets you choose whether or not to print Variance
Only. If you choose to print Variance Only, the Delivery Detail report lists only those
stops with differences between actual and planned delivery. If you do not choose this
option, the report lists the details for each delivery separately.
Step 1: Enter the Reports module. The Reports window will be open.
Step 2: Right-click on the Delivery Detail report and select Options from the menu that
pops up. The Delivery Detail Options window opens.
To include only those stops/orders/line items
where the actual delivery information varied
from the planned, check Variance Only.
Step 3: Check Variance Only to only include those stops with differences between
planned and actual delivery.
Printing the Report

Step 2: Right-click on the Delivery Detail report. From the pop-up menu, select
directly to the printer. The Selection Criteria window opens. From this window,
you are able to set up your report.
950

Delivery Detail
Operations Guide
951
Distance by Area
Distance by Area
Used with: Roadnet
The Distance by Area report lets you summarize how much each piece of equipment has
traveled in the defined areas over a specified range of time. If entered routinely, Roadnet
uses this information to generate the Distance by Area report. This information can be
very helpful when tracking distances for DOT purposes.
For a sample of this report, refer to the Distance by Area Report Sample.
Printing the Report
Before you print this report, you need to enter the actual distances driven in each area
in Area Distances.
Step 2: Right-click on the Distance by Area report in the Reports window. From the
pop-up menu select Preview Report to view before printing, or Print Report to
send the report directly to the printer. The Selection Criteria window appears.
952

Distance by Jurisdiction
The Distance by Jurisdiction report lets you monitor how far a piece of equipment
traveled in each jurisdiction. This report summarizes the distance by jurisdiction
information by using GPS data and can be useful when tracking distances for reporting or
DOT purposes. Distances are calculated by measuring the straight line distance between
GPS pings. The accuracy of the Distance by Jurisdiction report is affected by the amount
of time between each GPS reading from the wireless device (the GPS Update Rate). The
report will be more accurate when the GPS Update Rate is more frequent and less accurate
when the GPS Update Rate is less frequent. See Setting the General Dispatching Options
for information about setting the GPS Update Rate.
Important: This feature is not intended to replace your local reporting requirements. A
route with exceptions that affect distance will diminish the accuracy of this report.
Check with your local jurisdiction for the legal reporting requirements in your
area.
For a sample of this report, see the Distance by Jurisdiction Report Sample.
Printing the Report

Step 2: Right-click on the Distance by Jurisdiction report in the Reports window. From
the pop-up menu select Preview Report to view before printing, or Print Report
to send the report directly to the printer. The Selection Criteria window appears.
Operations Guide
953
Draft Daily
Draft Daily
Used with: Roadnet
The Draft Daily report lists all the stops on a route in projected delivery sequence. When
generated, this report pulls stop-specific information from Roadnet and includes location
name, address, and phone number; arrival and departure times; service and travel times;
distance traveled; open/close times and time windows; and the amounts of the size 1, size
2, and size 3 measurements for the stop. It also shows any projected break time(s).
Note: The times shown on this report are displayed using the locations time zone.
At the top of the Draft Daily report, route-specific information is displayed, such as route
ID and name; total number of stops; driver, equipment, and depot assigned to the route;
pre- and post-route time; and the depot departure and arrival times. Additionally, there are
symbols on the report denoting specific information about the stop.
Symbol
Legend
Arrived before opening time.
Arrived before closing time, but service will extend beyond

closing.
Arrived after closing time.
Arrived within one of the time window ranges.
Arrived outside the time widow ranges.
Location is zip geocoded.
The Draft Route report contains much of the same information as the Driver Itinerary and
Manifest, although in a much more condensed format. It can be a great resource for
administrative personnel.
For a sample of this report, refer to the Draft Daily Report Sample.
Printing the Report

Step 2: Right-click on the Draft report in the Reports list window. From the pop-up
menu, select Preview Report to view the report before printing, or select Print
Report to print directly to the printer. The Selection Criteria window opens.
954

Driver Check Out
Driver Check Out

The Driver Check Out report lets the driver confirm the product that is loaded on the
equipment, and correct the quantity if necessary.
The report pulls information from FleetLoader and lists the contents of the truck, by bay
or pallet, with spaces for the driver to correct quantity, if needed. The route ID and date,
equipment ID and total quantity and total weight loaded are displayed at the top of the
report.
For a sample of this report, refer to the Driver Check Out Report Sample.
Printing the Report

Step 2: Right-click on the Driver Check Out report in the Reports list window. From
opens.
include in the report. All routes for those dates will be listed at the bottom of the
window. You can enter the date manually, or click the arrow to open a calendar. If
entering manually, check the box before typing the date. If using the calendar to
change the month, use the arrows on the top of the calendar to scroll through the
on a date to select it.
Operations Guide
955
Driver Itinerary
Driver Itinerary
Used with: Roadnet
The Driver Itinerary provides some additional information that the Draft Daily report does
not. Generated using Roadnet data, the Itinerary lists all the stops on a route in projected
delivery sequence, including any projected break time. Additionally, there are symbols on
the itinerary denoting specific information about that stop.
Symbol
Legend

closing.
Route-specific information is displayed at the top of the Driver Itinerary, such as route ID
and name; the driver, equipment, and depot assigned to the route; and any pre- or postroute time. At the end of the Driver Itinerary, a collection of totals is displayed, including
travel time, service time, distance, total size measurements, and the total number of stops
and orders. This report also includes blank spaces for the driver to provide actual
information.
For a more condensed version of this information see the Stop List report.
For a sample of this report, refer to the Driver Itinerary Report Sample.
The Driver Itinerary report also gives you the option to display times, order information,
distance by region, and category sizes when you preview or print the report.
Step 2: Right-click on the Driver Itinerary report and select Options from the menu that
pops up. The Driver Itinerary Options window opens.
956

Driver Itinerary
Step 3: Click to place a checkmark next to the option(s) you want to include on the
report.
Choose to include times,
order information,
distance, and/or category
sizes on the Driver
Itinerary report.

Printing the Report

Step 2: Right-click on the Driver Itinerary in the Reports list window. From the pop-up
menu, select Preview Report to view the report before printing, or select Print to
Operations Guide
957
Driver Manifest
Driver Manifest
Used with: Roadnet
The Driver Manifest provides the greatest amount of detail of all stop listings in Roadnet.
The Manifest lists all the stops on a route in order, and includes the stop-specific
information, such as all order numbers for the stop. It also shows planned break time(s),
plus any pre- or post-route time. Beside the stop numbers on the Manifest, there are
symbols denoting specific information about that stop.
Symbol
Legend

closing.
Similar to the Driver Itinerary, route-specific information is displayed at the top of the
report. The collected totals also appear at the end of the Manifest. Like the Itinerary, the
Manifest provides areas for the driver to fill in actual information, such as odometer
readings, arrival and departure times, and signature lines. The Manifest can, therefore, be
a great resource as a way to record and track actual data for companies that do not use
onboard computers.
For a more condensed version of this information see the Stop List.
For a sample of this report, refer to the Driver Manifest Report Sample.
The Driver Manifest report also gives you the option to display any or all of the following
when you preview or print the report: times, order information, line item information,
distance by area, and category sizes.
Step 2: Right-click on the Driver Manifest report and select Options from the menu that
pops up. The Driver Manifest Options window opens.
958

Driver Manifest
Step 3: Click to place a checkmark next to the option(s) you want to include on the
report.
Choose to include times,
order information, line
item information, distance,
and/or category sizes on
the Driver Manifest report.

Printing the Report

Step 2: Right-click on the Driver Manifest in the Reports list window. From the pop-up
Operations Guide
959
Roadnet Driver Performance

Used with: Roadnet
The Driver Performance report lists all of your drivers and compares the planned service
and travel times with the actual service and travel times reported by the drivers or an
onboard computer system. The percent that the drivers went over or under the planned
service and travel times is indicated on the report as percent variance: positive
percentages are used when the actual time is greater than the planned time, while negative
percentages are used when the actual time is less than the planned time. It also provides
the total number of pieces delivered and statistics about pieces delivered per hour and per
stop. At the bottom of the report averages are calculated for each column to provide a
comparison or benchmark. You can generate the Driver Performance report for as long or
as many sessions as you want.
Note: The Driver Performance report can be a valuable tool for tracking productivity
with Roadnet. However, because the comparison of service and travel times uses
planned data, you must be confident that the projected service and travel times
from Roadnet are accurate before using the report as a performance assessment
tool.
For a sample of this report, refer to the Roadnet Driver Performance Report Sample.
The Driver Performance report also gives you the option to sort by any of the following:
actual service time, actual travel time, planned service time, planned travel time, units,
units per service hour, or units per stop.
Step 2: Right-click on the Driver Performance report and select Options from the menu
that pops up. The Driver Performance Options window opens.
Step 3: Click on the Sort By drop-down arrow, and click to select the item you want to
sort by. Choose whether you want the report sorted in ascending or descending
order.
Click the drop-down arrow to
choose from a list of sort
options.
960

Printing the Report
Before you print this report, you should import actual data from an onboard computer
system. See Importing OnBoard Data for more information. Or, manually enter the actual
data.
Step 2: Right-click on the Driver Performance report in the Reports list window. From
opens.
Operations Guide
961
MobileCast Driver Performance Report
MobileCast Driver Performance Report

The MobileCast Driver Performance report lists all of your drivers and compares the
planned service and travel times with the actual service and travel times reported by the
drivers wireless devices. The percent that the drivers went over or under the planned
service and travel times is indicated on the report as percent variance: positive
percentages are used when the actual time is greater than the planned time, while negative
percentages are used when the actual time is less than the planned time. The report also
provides the total number of units delivered, and statistics about units delivered per hour
and per stop. At the bottom of the report averages are calculated for each column to
provide a comparison or benchmark. You can generate the MobileCast Driver
Performance report for as long as you want.
For a sample of this report, refer to the MobileCast Driver Performance Report Sample.
Printing the Report

Step 2: Right-click on the Driver Performance report in the Reports list window. From
opens.
Step 4: Your report will either appear in Preview mode, or print directly to your printer.
962

Driver Productivity
Driver Productivity
The Driver Productivity report is generated from information contained in FleetLoader,

and lets you track the amount of time drivers needed to deliver product on the route. You
can print the report for a single day or for an extended period of time, allowing you to
develop a history of the drivers service rate. The report also prints the service time and
rate per hour for drivers for selected dates.
For a sample of this report, refer to the Driver Productivity Report Sample.
Printing the Report
Before printing this report, you need to enter the driver productivity information. See
Tracking Productivity for more information.
Step 2: Right-click on the Driver Productivity report in the Reports list window. From
opens.
Operations Guide
963
Driver Returns
Driver Returns
For a selected period of time, the Driver Returns report lists the customer, picked up, over,
or damaged quantities for each route. The Driver Returns report varies slightly depending
on the detail level you have set.
For a sample of this report, refer to the Driver Returns Report Sample.
Printing the Report

Step 2: Right-click on the Driver Returns report. From the pop-up menu, select
964

Driver Statistics
Driver Statistics
For a selected period of time, the Driver Statistics report lists the drivers and the number
of routes each driver completed, the number of locations delivered, information about late
deliveries, plus the percentage and total number of stops that the driver met and missed,
as well as the total number of stops the driver was early or late for as compared to the
planned arrival times within a set Time Window.
Note: Time window calculations are based only on stops. Breaks and waits are not
considered for any time window calculation.
For a sample of this report, refer to the Driver Statistics Report Sample.
Printing the Report

Step 2: Right-click on the Driver Statistics report. From the pop-up menu, select
Operations Guide
965
Driver Service Log
Driver Service Log

The Driver Service Log report provides information on the amount of time each driver is
on a route within a specified time period, as entered in the drivers Duty Period History.
This report contains information for individual drivers, such as Route ID, Duty Start Date
and Time, On Duty Time, Travel Time, Off Duty Time, and Total Time.
Important: The Driver Service Log is not a replacement for any records that you are
required to keep by law, such as DOT logs.
For a sample of this report, refer to the Driver Service Log Sample.
Printing the Report

Step 2: Right-click on the Driver Service Log in the Reports list window. From the
pop-up menu, select Preview Report to view the report before printing, or select
Print Report to print directly to the printer. The Selection Criteria window opens.
966

Driver Survey
Driver Survey
Used with: Roadnet
The Driver Survey lists all stops on a route in Roadnet, and is designed to gather
information about your locations. You can hand the Driver Survey to your drivers or
salespeople and have them obtain valuable information about your accounts.
The report lists each locations name and ID, as well as address and phone information.
You can print the report so that the driver has space to write in important delivery-related
information about each location, such as open/close times, time windows; average fixed
and variable service times, and any comments or special instructions.
For a sample of this report, refer to the Driver Survey Report Sample.
The Driver Survey report gives you the option to fill all the fields on the report or to leave
them blank so that the driver can enter the appropriate data.
Step 2: Right-click on the Driver Survey report and select Options from the menu that
pops up. The Driver Survey Options window opens.
Step 3: Click the Create Blank Report box if you want the reports fields to be blank for
subsequent data entry.
Click the check box to create a
blank report

Printing the Report

Step 2: Right-click on the Driver Survey report in the Reports list window. From the
Operations Guide
967
Driver Survey
968

Driver Utilization
Driver Utilization
For a seven-day period, the Driver Utilization report graphically shows the time of day
drivers are used, and the number of drivers used during the period. Each block on the
report represents two hours of a twenty-four hour time span.
For a sample of this report, refer to the Driver Utilization Report Sample.
Printing the Report

Step 2: Right-click on the Driver Utilization report. From the pop-up menu, select
Step 3: Enter the Begin Date for the seven-day period you want to include in the report.
You can enter the date manually, or click the arrow to open a calendar. If entering
select it.
Operations Guide
969
Employee Hours Worked

The Employee Hours Worked report provides you with a detailed report containing
multiple records per employee for the hours worked over a specified date range. The
report shows the employee, route ID, employee ID, the employee type, route date, start
and end times, total hours worked, break time taken, total hours paid, and the number of
regular, overtime, and double time hours paid for the selected period of time. The daily
hours worked for the calculation of overtime and double time hours are initially assigned
default values for each defined employee type. You have the option for each employee
type to enter overtime values for daily hours worked for both the normal overtime and
double time hours to be calculated.
For a sample of this report, refer to the Employee Hours Worked Report Sample.
Setting the Options
The Employee Hours Worked Options window gives you the option to customize the
calculation of employee hours worked. Once you set your values in the options window,
you do not need to specify them each time you run the report unless you want to change
them.
Step 2: In the Reports window, right-click on the Employee Hours Worked report and
select Options from the menu that pops up. The Employee Hours Worked
Options window opens.
Select the options you want on the report for the employee hours worked.
Step 3: Select an Employee Type from the list.

Step 4: In the Hours Worked Calculation Options section, enter the minimum number
of hours the employee must work in a day to qualify for overtime in the Calculate
Overtime Hours for field. If the employee works more hours than this in a day,
they will appear as Overtime on the report.
970

of hours the employee must work in a day to qualify for double time in the
Calculate Double Time Hours for field. If the employee works more hours than
this in a day, they will appear as Double Time on the report.
Step 6: Click the [Update] button to save the information.
Step 7: Repeat Steps 3 through 6 for each employee type.
Printing the Report
The Employee Hours Worked report allows a date range to be specified to show the hours
employees worked for a selected time period.
Step 2: Right-click on the Employee Hours Worked report in the Reports list window.
window opens.
the calendar. If entering manually, check the box before typing the date. If using
the calendar to change the month, use the arrows on top of the calendar to scroll
To change the year, click on the year and use the arrows to select the correct year.
Operations Guide
971
Employee Hours Worked Summary

The Employee Hours Worked Summary report provides you with a summary report
containing one record per employee for the hours worked over a specified date range. The
report shows the employee ID, employee, employee type, the total hours paid, and the
number of regular, overtime, and double time hours paid for the selected time period. The
daily hours worked for the calculation of overtime and double time hours are initially
assigned default values for each defined employee type. You have the option for each
employee type to enter overtime values for daily hours worked for both the normal
overtime and double time hours to be calculated.
For a sample of this report, refer to the Employee Hours Worked Summary Report
Sample.
Setting the Options
The Employee Hours Worked Summary Options window gives you the option to
customize the calculation of employee hours worked. Once you set your values in the
options window, you do not need to specify them each time you run the report unless you
want to change them.
Step 2: In the Reports window, right-click on the Employee Hours Worked Summary
report and select Options from the menu that pops up. The Employee Hours
Worked Summary Options window opens.
Step 3: Select an Employee Type from the list.

of hours the employee must work in a day to qualify for overtime in the Calculate
Overtime Hours for field. If the employee works more hours than this in a day,
they will appear as Overtime on the report.
of hours the employee must work in a day to qualify for double time in the
972

Calculate Double Time Hours for field. If the employee works more hours than
this in a day, they will appear as Double Time on the report.
Step 7: Repeat Steps 3 through 6 for each employee type.
Printing the Report
The Employee Hours Worked Summary report allows a date range to be specified to show
the hours employees worked for a selected time period.
Step 2: Right-click on the Employee Hours Worked Summary report in the Reports list
the calendar. If entering manually, check the box before typing the date. If using
the calendar to change the month, use the arrows on top of the calendar to scroll
To change the year, click on the year and use the arrows to select the correct year.
Operations Guide
973
Equipment Utilization
For a seven-day period, the Equipment Utilization report graphically shows the time of
day the equipment is used and the amount of equipment used during the period. Each
block on the report represents two hours of a twenty-four hour time span.
For a sample of this report, refer to the Equipment Utilization Report Sample.
The Equipment Utilization Options window lets you select the type(s) of equipment to
include in your report.
Step 2: In the Reports window, right-click on the Equipment Utilization report and
select Options from the menu that pops up. The Equipment Utilization Options
window opens.
The Equipment Utilization Options window
lets you choose the type of equipment you
want included in the report.
Step 3: Select the type(s) of equipment to include.

Printing the Report

Step 2: Right-click on the Equipment Utilization report. From the pop-up menu, select
Step 3: Enter the Begin Date for the seven-day period you want to include in the report.
You can enter the date manually, or click the arrow to open a calendar. If entering
select it.
974

Equipment Utilization Metrics

For a selected period of time, the Equipment Utilization Metrics report lists the equipment
used, the total amount of time, and percent of total working time it was used. You can set
the total working time and the type(s) of equipment you want to include in the report.
For a sample of this report, refer to the Equipment Utilization Metrics Report Sample.
The Equipment Utilization Metrics Options window lets you select the type(s) of
equipment to include in your report, and the number of hours that the piece(s) of
equipment are expected to be in use per day to be considered at 100% utilization (ex. 10
hours/day).
Step 2: In the Reports window, right-click on the Equipment Utilization Metrics report
and select Options from the menu that pops up. The Equipment Utilization
Metric Options window opens.
The Working Hours/Day is used to
calculate the percentage of time the
equipment is being used.
Step 3: Select the type(s) of equipment to include and enter the number of hours per
day that the equipment will be used.
Printing the Report

Step 2: Right-click on the Equipment Utilization Metrics report. From the pop-up
Report to print directly to the printer. The Selection Criteria window opens. From
this window, you are able to set up your report.
Operations Guide
975
976

Global Cost
Global Cost
The Global Cost report is generated from information in Territory Planner, and it
summarizes the total cost of a route, including equipment and driver fees. The equipment
cost includes fixed cost, variable cost, and the total cost of the equipment (fixed +
variable). The driver cost includes commission rate, total regular cost, total overtime cost,
and the overall total cost of the driver (commission + regular + overtime). This report also
contains any additional fees (i.e. location/depot visit charges) and the overall cost for the
selected planning session(s).
For a sample of this report, refer to the Global Cost Report Sample.
Printing the Report

Step 2: Right-click on the Global Cost report. From the pop-up menu, select Preview
to the printer. The Selection Criteria window opens.
Operations Guide
977
Global Itinerary
Global Itinerary
The Global Itinerary report provides a detailed list of all the stops on a route for the
selected planning session(s), territory(s), week(s), and day(s). This report includes routespecific information from Territory Planner, and displays the location ID, location name,
address, sizes 1,2, and 3, distance, travel time, arrival time, and service time. At the end
of the Global Itinerary a collection of totals is displayed, including travel time, service
time, distance, size measurements, and the total number of stops and orders.
For a sample of this report, refer to the Global Itinerary Report Sample.
The Global Itinerary report lets you choose whether you want to include the complete
address on the report (849 Fairmount Ave., Towson, MD 21286) or only the street address
(849 Fairmount Ave.).
Step 2: Right-click on the Global Itinerary report and select Options from the menu that
pops up. The Global Itinerary Options window opens.
Step 3: Select whether you want to print the Full report (complete address) or the
Condensed report (street address).
The Condensed version of the Global
Itinerary takes less space to print than the
Full version.

Printing the Report

Step 2: Right-click on the Global Itinerary report. From the pop-up menu, select
978

Global Manifest
Global Manifest
The Global Manifest report provides the greatest amount of detail of all the stop listings
in Territory Planner, and can be customized to show the stop number, customer name, size
1, service set pattern, open/close time, time windows, address, standard instructions,
travel time, service time, and distance. Similar to the Global Itinerary, route-specific
information is displayed at the top of the report, while the collected totals appear at the
end. The report also provides space for the driver to enter the actual arrival and departure
time, as well as any other notes. Therefore, the Manifest can be a great resource for
recording and tracking actual data for those companies that do not use onboard computers.
For a sample of this report, refer to the Global Manifest Report Sample.
The Global Manifest report lets you customize the amount of information shown on the
report. You can choose to include the address, arrival and departure times, travel times,
distances, location IDs, service pattern sets, delivery days, open and close times, time
windows, and standard instructions.
Step 2: Right-click on the Global Manifest report and select Options from the menu
that pops up. The Global Manifest Options window opens.
Step 3: From this window, you can choose to include the following: address, arrival
and departure times, travel times, distances, location IDs, service pattern sets,
delivery days, open and close times, time windows, and any standard
instructions.
Select the information to be

included on the report.

Printing the Report
Operations Guide
979
Global Manifest
Step 2: Right-click on the Global Manifest report. From the pop-up menu, select
980

Global Time/Distance
The Global Time/Distance report lists the anticipated travel and service times, as well as
the overall distance traveled, for the selected planning session(s), territory(s), week(s),
and day(s) calculated in Territory Planner.
Note: The Other column includes breaks, waits, layovers, pre-route, and post-route times.
For a sample of this report, refer to the Global Time/Distance Report Sample.
Printing the Report

Step 2: Right-click on the Global Time/Distance report. From the pop-up menu, select
Operations Guide
981
Key Performance Indicators Detail

Used with: Roadnet
The Key Performance Indicators Detail report lists all routes in Roadnet based on specific
dates entered, and is designed to gather information about the equipment, distance, time,
and cost of each route.
For a sample of this report, refer to the Key Performance Indicators Detail Sample.
Printing the Report

Step 2: Right-click on the Key Performance Indicators Detail in the Reports list
982

Key Performance Indicators Summary

Used with: Roadnet
The Key Performance Summary report lists all routes in Roadnet based on specific dates
entered, and is designed to gather information about the equipment capacity, distance,
time, and cost of each route. This report gives a summary and an average for the data.
For a sample of this report, refer to the Key Performance Indicators Summary Sample.
Printing the Report

Step 2: Right-click on the Key Performance Indicators Summary in the Reports list
Operations Guide
983

Used with: Roadnet
The Less Than Minimum Orders report lists orders that are less than a user-defined
minimum number of the size 1, size 2, and/or size 3 quantities on a particular delivery day.
For instance, if you decide to use 20 cases as your minimum order size, and Simons Salon
of Szechuan has an order for 14 cases, then that order would appear on the report.
This report is generated from stop-specific information in Roadnet, and includes route and
stop number, location ID and name, salesperson, and the size 1, size 2, and size 3 quantity
ordered by that location. The report is sorted on route ID and stop number.
Hint: The Less than Minimum Orders report is an excellent tool for helping to determine
the best way to service your customers and produce more cost-efficient routing.
For a sample of this report, refer to the Less Than Minimum Orders Report Sample.
The Less Than Minimum report gives you the option to define your minimum quantities
for size 1, size 2, and/or size 3.
Step 2: Right-click on the Less Than Minimum report and select Options from the
menu that pops up. The Less Than Minimum Options window opens.
Step 3: Enter the minimum quantities in the size fields. Any orders less than these
quantities will be included on the report.
Define the minimum quantities for size 1,

size 2, and/or size 3.
984

Printing the Report

Step 2: Right-click on the Less Than Minimum report in the Reports list window. From
opens.
Operations Guide
985
Less Than Minimum Stops

Used with: Roadnet
The Less Than Minimum Stops report lists stops whose total orders are less than a userdefined minimum number of the size 1, size 2, and/or size 3 quantities. For instance, if
you decide to use 25 cases as your minimum stop size, and Simons Salon of Szechuan
orders only total 14 cases, then that stop would appear on the report. If those cases were
distributed between two orders (1 for 11 and 1 for 3) and your minimum order size was
10, then the order with 3 cases would also appear on the Less than Minimum Orders
report.
This report is generated from stop-specific information in Roadnet, and includes route and
stop number, location ID and name, salesperson, and the size 1, size 2, and size 3 quantity
ordered by that location. The report is sorted on route ID and stop number.
Hint: The Less than Minimum Stops report is an excellent tool for helping to determine
the best way to service your customers and produce more cost-efficient routing.
For a sample of this report, refer to the Less Than Minimum Stops Report Sample.

Step 2: Right-click on the Less Than Minimum Stops report and select Options from
the menu that pops up. The Less Than Minimum Stops Options window opens.
Step 3: Enter the minimum quantities in the size fields. Any stops with less than these
quantities will appear on the report.
Define the minimum

quantities for size 1, size 2,
and/or size 3.
986

Printing the Report

Step 2: Right-click on the Less Than Minimum report in the Reports list window. From
opens.
Step 4: Select the Routing Session(s) to include in the report
Operations Guide
987
Load Truck Diagram
Load Truck Diagram

The Load Truck Diagram can be used by warehouse personnel when loading the truck to
indicate the total of each SKU loaded into each bay or pallet. The report pulls information
from FleetLoader and displays the truck layout, including bay or pallet placement and
stack order within the bay or pallet, and includes space to update the quantity as necessary.
The report lists the route ID and date, the equipment ID, and the total number of units and
total weight of the units on the equipment, as well as all product to be loaded onto the
truck by bay or pallet.
Note: If there are no SKUs assigned to a bay or pallet, then only the bay or pallet number
appears on the report.
For a sample of this report, refer to the Load Truck Diagram Report Sample.
Setting the Options

Step 2: Right-click on the Load Truck Diagram report in the Reports list window and
select Options from the menu that pops up. The Load Truck Diagram Options
window opens.
To save space on the report, make sure all the

options are turned off.
Step 3: Check the options you want to have appear on the report:
Show Location Infocheck to have the stop's location ID and description appear
on the report. If the ID and description will not fit in the space, for instance if there
is more than one stop in the bay, as much information as possible will be printed,
followed by an ellipse (...).
Show Layer Linescheck to have dashed lines separate the layers on the bay/
pallet. This option may be especially helpful if you are loading pallets.
Note: In order for layer lines to show on the report, Show Detailed Bay/Pallet Contents
must also be checked.
Show SKU Headingscheck to have the words SKU and Description included
on the report. If this option is not selected, the SKU information still appears on
the report, but it is not labeled.
Show Detailed Bay/Pallet Contentscheck to display the bay or pallet contents
as they are displayed in FleetLoader.
988

Load Truck Diagram

Printing the Report

Step 2: Right-click on the Load Truck Diagram report in the Reports list window. From
opens.
Operations Guide
989
Load Productivity
Load Productivity
The Load Productivity report is generated using FleetLoader data, and lets you track the
amount of time warehouse personnel needed to load the bays on the equipment. Because
you can print the report for a period of time, you can develop a history for the employees
loading rates.
The report also prints the service time and rate per hour for warehouse personnel loading
the trucks on a selected date.
For a sample of this report, refer to the Load Productivity Report Sample.
Printing the Report
Before printing this report, you need to enter the load productivity information. See
Tracking Productivity for more information.
Step 2: Right-click on the Load Productivity report in the Reports list window. From
opens.
990

Load Validation Diagram

The Load Validation Diagram allows the driver to confirm all products loaded on the
truck by bay or pallet. The report simulates the truck layout, including bay or pallet
placement and stack order within the bay or pallet, and includes space to enter the quantity
as necessary.
This FleetLoader report displays the route ID, date, equipment ID, the product to be
loaded for each bay or pallet, and provides the driver with spaces to enter the actual
quantity loaded.
For a sample of this report, refer to the Load Validation Diagram Report Sample.
Setting the Options

Step 2: Right-click on the Load Validation Diagram report in the Reports list window
and select Options from the menu that pops up. The Load Validation Diagram
Step 3: Check the options you want to have appear on the report:
Show Location Infocheck to have the stop's location ID and description appear
on the report. If the ID and description will not fit in the space, for instance there
is more than one stop in the bay, as much information as possible will be printed,
followed by an ellipse (...).
Show Layer Linescheck to have dashed lines separate the layers on the bay/
pallet. This option may be especially helpful if you are loading pallets.
Note: In order for layer lines to show on the report, Show Detailed Bay/Pallet Contents
must also be checked.
Show SKU Headingscheck to have the words SKU and Description included
on the report. If this option is not selected, the SKU information still appears on
the report, but it is not labeled.
Show Detailed Bay/Pallet Contentscheck to display the bay or pallet contents
as they are displayed in FleetLoader.
Step 4: Click the [OK] button when you have selected your options.
To save space on the
report, make sure all the
options are turned off.
Operations Guide
991
Printing the Report

Step 2: Right-click on the Load Validation Diagram report in the Reports list window.
window opens.
992

Location Delivery Cost

The Location Delivery Cost report lists the stops for selected delivery dates, the total cost
to deliver the stop, and the cost per unit delivered. Location costs are derived from route
costs in the Routing and Planning Editors, and calculated using the method selected in the
General page of the Maintenance Options notebook.
Note: In order to view/print data on this report, you must have selected a method on the
General page of the Maintenance module.
Hint:
The Off-Day Delivery and Location Delivery Cost reports work well together to
determine how much it costs to service those locations that consistently receive
off-day deliveries.
For a sample of the Roadnet version of this report, refer to the Roadnet Location Delivery
Cost Report Sample.
For a sample of the Territory Planner version of this report, refer to the Territory Planner
Location Delivery Cost Report Sample.
You can choose how the data in the Location Delivery Cost report is grouped, as well as
how it is sorted within the groups. You can group the report by Location ID (all stops for
a location are grouped together), Account Type (all stops for locations with the same
account type are grouped together), or Sales Rep (all stops for locations with the same
sales rep are grouped together).For the Territory Planner report, you can also group by
territory (all stops within the same territory are grouped together), week (all stops for the
same delivery week are grouped together), or week/day (all stops for the same day within
a delivery week are grouped together). In addition, you can sort the report by Cost/Unit
or Total Cost.
Operations Guide
993
Step 2: Right-click on the Location Delivery Cost report for Roadnet or Territory
Planner. From the pop-up menu, select Options. The Location Delivery Cost
Use the Location Delivery Cost Options window to

setup what is printed on your report.
Step 3: For the Roadnet report, click the Grouped By arrow and select what the
report will be grouped by. The options are Location ID, Account Type, and Sales
Rep.
For the Territory Planner report, click the Grouped By Primary and Secondary
arrows and select what the report will be grouped by. The options are None,
Account Type, Sales Rep, Territory, Week, and Week/Day.
Notes: The category you select as the primary grouping option for the Territory Planner
report cannot be used as the secondary grouping option.
If None is selected for the primary grouping for the Territory Planner report, a
secondary grouping cannot be selected.
Step 4: Click the Sort By arrow and select how the report will be sorted. Choose
whether the report should be sorted in ascending or descending order.
Step 5: Choose whether you want to include all locations on the report (All), or only a
defined number (Top). If you only want a defined number of locations, enter the
number in the field; the locations included are based on the Sort By order.
Step 6: Choose the address format you want to use. To include the complete location
address (ex. 849 Fairmount Ave., Towson, MD 21286) select Full in the Style
area. To include only the street address (849 Fairmount Ave.) select Condensed.
Printing the Report
994


Step 2: Right-click on the Location Delivery Cost report for Roadnet or Territory
Planner in the Reports list window. From the pop-up menu, select Preview
to the printer. The Selection Criteria window opens.
Step 3: For the Roadnet report, enter the starting and ending date for the report and
click the [OK] button. Your report will either appear in Preview mode or print
For the Territory Planner report, select a planning session for the report and
click the [OK] button. Your report will either appear in Preview mode or print
Operations Guide
995
Location Returns
Location Returns
Used with: Roadnet
The Location Returns report lists those locations in Roadnet that have product they want
to return. In order for this information to be included on the report, the return must be
added as a pickup in a future session. The report provides the location ID and name, the
order number for the return(s), and the size 1, size 2, and size 3 amounts of the returned
product. You must supply at least one size measurement (typically number of pieces) for
the return to be included on the Location Returns report.
For a sample of this report, refer to the Location Returns Report Sample.
Printing the Report

Step 2: Right-click on the Location Returns report in the Reports list window. From the
996

Location Statistics
Location Statistics
For a selected period of time, the Location Statistics report lists, by location, the number
of stops, redeliveries, cancelled deliveries, service time and quantity of size 1, average
and maximum service times, the drivers average and maximum times late, plus the
percentage and total number of stops that the driver met and missed, as well as the total
number of stops the driver was early or late for as compared to the planned arrival times
within a set Time Window.
For a sample of this report, refer to the Location Statistics Report Sample.
Printing the Report

Step 2: Right-click on the Location Statistics report. From the pop-up menu, select
Operations Guide
997
Multiple Pallet Pick Sheet

The Multiple Pallet Pick Sheet lists all products to be loaded on the truck by pallet. This
report prints several pallets per page and includes the session date, route ID, location ID,
location name, equipment, quantity, and the numbers of layers for each pallet. The
Multiple Pallet Pick Sheet report is similar to the Pallet Pick Sheet report, except the Pallet
Pick Sheet only prints one pallet per page.
Note: If there is more than one stop on a pallet, then the stops loaded on that pallet will
be listed on the bottom of the sheet.
If there is only one stop on a pallet, and the stop is loaded on several pallets, then
the total number of pallets loaded for that stop will be displayed in the lower right
corner of the sheet.
For sample of this report, refer to the Multiple Pallet Pick Sheet Report Sample.
The Multiple Pallet Pick Sheet can also be customized to show even more information,
such as quantity, layers, zones, and printed or unprinted orders.
Step 2: Right-click on the Multiple Pallet Pick Sheet report and select Options from the
menu that pops up.
Place a check next to the
option(s) you want to
show in the report.
Step 3: To include the total quantity of the pallet, check Quantity.

To include the number of layers in the pallet, check Layers.
To include the SKU description, check SKU Description.
To include the number of hands in the pallet, check Hands.
To include the SKU, check SKU.
To include the warehouse zones, check Warehouse Zones.
To only print orders that have not already been printed, check Unprinted
orders only. If this option is selected, a summary page will print at the end of the
report listing any pallets that were already printed. If this option is not checked,
998

all orders that meet the specified criteria will be printed, even if they were
previously print.
Printing the Report
Hint: Mark the orders as printed to prevent the loading of duplicate SKUs in the pallets
when the report is regenerated.
Step 2: Right-click on the Multiple Pallet Pick Sheet report in the Reports list window.
or Print Report to print directly to the printer. The Selection Criteria window
opens.
include on the report. All routes for those dates will be listed at the bottom of the
Operations Guide
999
Notes
Notes
For a selected period of time, this report lists any notes associated with each route. You
can choose to include notes that have been acknowledged, not acknowledged, or both.
For a sample of this report, refer to the Notes Report Sample.
The Notes Options window lets you choose to display notes that are acknowledged, not
acknowledged, or all of your notes.
Step 2: In the Reports window, right-click on the Notes report and select Options from
the menu that pops up. The Notes Options window opens.
The Notes Option window
lets you choose the status
of the notes you want to
Step 3: To list notes that are acknowledged, verify a check is present in the
Acknowledged box; to list notes that were not acknowledged, make sure no
check is present in the box; to list all notes, the box should be grayed out.
Printing the Report

Step 2: Right-click on the Notes report. From the pop-up menu, select Preview Report
to view the report before printing, or select Print Report to print directly to the
printer. The Selection Criteria window opens. From this window, you are able to
set up your report.
1000

Off-Day Delivery Exception
Off-Day Delivery Exception

Used with: Roadnet
The Off-Day Delivery Exception report is generated from Roadnet information, and lists
locations for a given delivery date if their regular delivery days (set up in location
maintenance) do not match that delivery date. For instance, if a locations delivery days
are Monday, Wednesday, and Friday, and the delivery date is July 15, 1999 a Thursday
then that location would appear on the Off-Day Delivery report.
The report shows the location ID and name, the specified delivery days for that location
(in the format MTWRFSU), size 1, size 2, and size 3 totals for the delivery, service time
and open/close time, and the sales person for that location.
Hint: The Off-Day Delivery and Location Delivery Cost reports work well together to
determine how much it costs to service those locations that consistently receive
off-day deliveries.
For a sample of this report, refer to the Off-Day Delivery Exception Report Sample.
Printing the Report

Step 2: Right-click on the Off-Day Delivery report in the Reports list window. From
opens.
Operations Guide
1001
Open/Close Exception
Used with: Roadnet
The Open/Close Exception report lists locations whose arrival or departure time for their
delivery is not within their open and close times. For instance, if the arrival time to
Simons Salon of Szechuan is 08:30 and the open time for Simons isnt until 09:00, then
Simons would appear on the Open/Close Exception report. Likewise, if the departure
time (the time the driver completes delivery for the location) for Simons is 21:30 and the
close time is set at 21:00, then Simons would appear on the report.
The report pulls data from Roadnet to show location ID and name, route and stop number
for that location, open and close times, arrival and departure times, hours and minutes
early or late, and size 1, size 2, and size 3 totals, with complete totals displayed at the
bottom of the report. You can generate the Open/Close Exception report using projected
or actual data.
Note:
If you use planned data for the Open/Close Exception report, you must be
confident that the planned service and travel times in Roadnet are accurate before
using the report as a performance assessment tool.
For a sample of this report, refer to the Open/Close Exception Report Sample.
The Open/Close Exception report options allow you to generate your report using
projected or actual data.
Step 2: Right-click on the Open/Close Exception report and select Options from the
menu that pops up. The Open/Close Exception Options window opens.
Step 3: Click the Use Actual Data box to include actual data instead of planned data.
Do not click the box if you only want to use projected data.
Click the box to
generate the report
using actual data.

Printing the Report
Before you can print this report (actual data only), you need to import actual data from
an onboard computer system. See Importing OnBoard Data for more information. Or,
manually enter the actual data.
1002

Step 2: Right-click on the Open/Close Exception report in the Reports list window.
window opens.
Note: There are several options you can choose when printing the Open/Close Exception
report. See Setting the Open/Close Exception Report Option for more
information.
Operations Guide
1003
Order Summary
Order Summary
Used with: Roadnet
The Order Summary report provides a complete listing of orders in Roadnet for a given
session or delivery date. You can generate the report on a daily basis as a great resource
for tracking customer order quantities, returns, and projected routing information.
You can choose to sort the report by order number and list all orders for a location, any
selectors for those orders, size 1, size 2, and size 3 quantities, location name and ID, route
and stop numbers, and projected arrival and departure times.
For a sample of this report, refer to the Order Summary Report Sample.
The Order Summary report gives you the option to sort by any of the following: location
ID, order number, or route ID.
Step 2: Right-click on the Order Summary report and select Options from the menu
that pops up. The Order Summary Options window opens.
Step 3: Click on the Sort By down arrow to drop down a list, and click to select the item
you want to sort by. Choose whether you want the report sorted in ascending or
descending order. You can also choose to have a page break after each route.
Click the drop-down arrow

to choose from a list of sort
options.

Printing the Report

Step 2: Right-click on the Order Summary report in the Reports list window. From the
pop-up menu, select Preview Report to view the report before printing, or Print
1004

Order Summary
Operations Guide
1005
Pallet Pick Sheet
Pallet Pick Sheet

The Pallet Pick Sheet report lists all products to be loaded on the truck by pallet. This
report prints one pallet per page and includes the session date, route ID, location ID,
location name, equipment, quantity, pallet type, pallet loading method, and, if loading by
layers, the numbers of layers for each pallet. The Pallet Pick Sheet report is similar to the
Multiple Pallet Pick Sheet report, except the Multiple Pallet Pick Sheet prints several
pallets per page.
Note: If there is more than one stop on a pallet, then the stops loaded on that pallet will
be listed.
If there is only one stop on a pallet, and the stop is loaded on several pallets, then
the total number of pallets loaded for that stop will be displayed.
For sample of this report, refer to the Pallet Pick Sheet Report Sample.
The Pallet Pick Sheet report can also be customized to show even more information, such
as quantity, layers, zones, and printed or unprinted orders.
Step 2: Right-click on the Pallet Pick Sheet report and select Options from the menu
that pops up.
Place a check next to the
option(s) you want to
show in the report.
Step 3: To include the total quantity of the pallet, check Show Quantity.
To include the number of layers in the pallet, check Show Layers.
To include the number of hands in the pallet, check Show Hands.
To include the SKU description, check Show SKU Description.
To include the SKU, check Show SKU.
To include the SKU weight, check Show SKU Weight.
To include the warehouse zones, check Show Warehouse Zones.
To only print orders that have not already been printed, check Unprinted
orders only. If this option is selected, a summary page will print at the end of the
1006

Pallet Pick Sheet
report listing any pallets that were already printed. If this option is not checked,
all orders that meet the specified criteria will be printed, even if they were
previously printed.
Printing the Report
Hint: Mark the orders as printed to prevent the loading of duplicate SKUs in the pallets
when the report is regenerated.
Step 2: Right-click on the Pallet Pick Sheet report in the Reports list window. From the
Operations Guide
1007
Pick Sheet
Pick Sheet
The Pick Sheet lists all product to be loaded on the truck by bay or pallet, and if warehouse
location information is included with the SKU information, lists the areas of the
warehouse where the SKU is located. You can choose to have the report printed in a single
column format (one bay or pallet per page) or a 3-column format (3 bays or pallets per
page) to conserve paper.
For a sample of this report, refer to the Pick Sheet Report Sample.
The Pick Sheet and 3-Column Pick Sheet reports give you the option to include all orders
or only those orders that have not already been printed.
Step 2: Right-click on the Pick Sheet or 3 Column Pick Sheet report and select Options
from the menu that pops up. The Pick Sheet Options window opens.
Step 3: Check Unprinted Orders Only to exclude orders that have already been printed.
Printing the Report

Step 2: Right-click on the Pick Sheet (single column format) or 3 Column Pick (3column format) report in the Reports list window. From the pop-up menu, select
Preview to view the report in a window before printing, or Print to print directly
to the default printer.
Step 3: In the Parameter Setup window, enter the starting and ending dates of the range
to consider. All routes for those dates will be listed at the bottom of the window.
Step 4: Select the routes to include in the report. Click the [OK] button.
Step 5: When the message asking Would you like to mark these orders as printed?
appears, click [Yes] or [No] as appropriate. If the orders are marked as printed,
you have the option not to include them the next time the report is printed. Your
report will either appear in Preview mode or print directly to your printer.
1008

Prebuild Orders Customer Invoice

The Prebuild Orders Customer Invoice report can serve many purposes: it can be used to
pre-build orders for specific customers or to just print a list of the products specific
customers have ordered. This report lists the SKUs and quantity for each order being
delivered to the site, with spaces to change quantities as needed. Orders considered for the
Prebuild Orders Customer Invoice report should be included in the same download file as
the other orders, but a special import needs to be completed before the report is run.
For a sample of this report, refer to the Prebuild Orders Customer Invoice Report Sample.
The Prebuild Orders Customer Invoice report allows you to include orders equal to or
greater than a specific quantity, to include specific selectors, and/or to only include
uprinted orders.
Step 2: Right-click on the Prebuild Orders Customer Invoice report and select Options
from the menu that pops up. The Prebuild Orders Customer Invoice Options
window opens.
Step 3: In the Orders with Quantity field, enter the quantity to be included in the report.
Orders with a quantity greater than or equal to the amount you entered will be
included in this report.
Step 4: To include specific selectors, mark the Selector(s) box. Enter the selector(s) you
want to include, with no comma or spaces. For example, if your company uses
the letters B for Bulk and C for Cans, then enter BC.
Step 5: The And/Or fields become active after you include selector(s). Choose to either
sort along with (AND) or only by (OR) the specific selector(s) you entered.
Step 6: Mark the Unprinted Orders Only box if you have printed multiple reports and
only want to include orders that have not already been printed.
Include orders that are
equal to or greater than the
specified quantity.
Select to sort along with
or only by the specified
selector(s).
Choose to include
unprinted orders only.
Operations Guide
1009
Printing the Report

Step 2: Right-click on the Prebuild Orders Summary Customer Invoice report in the
Reports list window. From the pop-up menu, select Preview Report to view the
report before printing, or Print Report to print directly to the printer. The
Selection Criteria window opens.
1010

Prebuilt Pallet Pick Sheet

The Prebuilt Pallet Pick Sheet report prints orders that were loaded as a prebuilt solution,
so that your warehouse workers can start picking and packaging orders that have not
been assigned to a route. The report is organized so that one order is printed on each
page. Each order lists the quantity and product to be packaged, with spaces for both the
picker and a checker to initial that the order was packaged correctly. In addition, a
duplicate sheet is printed for each pallet, with the word Validated printed in large type
down the side so it is easy to determine when the order has been validated. You can
choose to have all prebuilt solutions printed, or only those that have not already been
printed.
For a sample of this report, refer to the Prebuilt Pallet Pick Sheet Report Sample.
The Prebuilt Pallet Pick Sheet report lets you choose whether to print all prebuilt
solution orders or only those that have not already been printed.
Step 2: Right-click on the Prebuilt Pallet Pick Sheet report and select Options from the
menu that pops up. The Prebuilt Pallet Pick Sheet Options window opens.
Step 3: To only include orders that have not already been printed, check Unprinted
Orders only.
To include only those orders not already
printed, check Unprinted Orders only.

Printing the Report

Step 2: Right-click on the Prebuilt Pallet Pick Sheet report in the Reports list window.
opens.
Operations Guide
1011
1012

Prebuilt Pick Sheet
Prebuilt Pick Sheet

The Prebuilt Pick Sheet report prints orders that were loaded as a prebuilt solution, so
that your warehouse workers can start picking and packaging orders that have not been
assigned to a route. The report is organized so that one order is printed on each page.
Each order lists the quantity and product to be packaged, with spaces for both the picker
and a checker to initial that the order was packaged correctly. In addition, a duplicate
sheet is printed for each pallet, with the word Validated printed in large type down the
side so it is easy to determine when the order has been validated. You can choose to have
all prebuilt solutions printed, or only those that have not already been printed.
For a sample of this report, refer to the Prebuilt Pick Sheet Report Sample.
The Prebuilt Pick report lets you choose whether to print all prebuilt solution orders or
only those that have not already been printed.
Step 2: Right-click on the Prebuilt Pick Sheet report and select Options from the menu
that pops up. The Prebuilt Pick Sheet Options window opens.
Orders only.

Printing the Report

Step 2: Right-click on the Prebuilt Pick Sheet report in the Reports list window. From
Operations Guide
1013
Prebuilt Pick Sheet
1014

Re-Route Analysis
Re-Route Analysis
The Re-Route Analysis report provides a tool for determining how performing a re-route
with Territory Planner affected the locations in a selected session. The previous and
current depot, territory, and delivery schedule are listed for each location. You can choose
to include locations that have changed, or kept, the depot, territory, delivery week, and
day. In addition, the sorting parameter can be selected, and you can choose to print either
a full report (name, address, and phone number) or a condensed report (name and ID
only).
For a sample of this report, refer to the Re-Route Analysis Report Sample.
The Re-Route Analysis Options window lets you select the options that will be used when
the Re-Route Analysis report is run. You can select whether to list locations whose depot,
territory, week, or day changed or did not change, the category the report is sorted by, and
whether to print the full or street address.
Step 2: Right-click on the Re-Route Analysis report and select Options from the menu
that pops up. The Re-Route Analysis Options window opens.
Step 3: From this window, select the locations to include in the report. To establish the
selection parameters, check the item in the Changes area and choose whether you
want locations that changed or not. For instance, to list all locations whose
territory changed, check Territories and click the button until an equal sign (=)
appears. You can choose to list locations that meet all the selected criteria
(AND), or locations that meet only one criteria (OR).
Step 4: Click the Sort By arrow to open a list of options the report can be sorted by;
click on an option to select it. Choose whether you want to sort the report in
ascending or descending order.
Step 5: Choose whether you want the Full or Condensed report. The condensed report
lists the location ID and name, while the full report also includes the address and
phone number.
Select the location

and parameters to
include in the
report.
Click the drop-down

arrow to choose from a
list of sort options.
Choose to print a full or
condensed report.

Operations Guide
1015
Re-Route Analysis
Printing the Report
Step 2: Right-click on the Re-Route Analysis report. From the pop-up menu, select
Step 3: Select the Planning Session(s) to include in the report.
1016

Resource Route by Day

The Resource Route by Day report summarizes your administrative, or resource, routes
for a selected range of dates. For each employee, you can see the ID of the completed
routes, along with each routes start time, complete time, and total distance, time, and
stops. At the end of the report the total and average distance, time, and stops are displayed.
For a sample of this report refer to the Resource Route by Day Report Sample.
Printing the Report
Step 2: Right-click on the Resource Route by Day report in the Reports list window.
window opens.
Operations Guide
1017
Resource Stop List
Resource Stop List

The Resource Stop List report provides a complete stop list of each drivers route on the
selected days. For each stop on the route the report provides the location ID, name and
address, arrive and depart times, as well as the service time and distance to the stop. A
summary for each route includes totals for the number of stops, distance, and time, as well
as the percentage of time that is spent with the customer (face time).
For a sample of this report refer to the Resource Stop List Report Sample.
Printing the Report

Step 2: Right-click on the Resource Stop List report in the Reports list window. From
opens.
1018

Resource Utilization
Used with: Roadnet
The Resource Utilization report shows the extent to which personnel and equipment
resources were used in routing. You can generate a Resource Utilization report on a daily,
monthly, and/or yearly basis.
The report lists, by delivery date, the number of pieces of equipment used, amount of size
1 delivered, how full the trucks were, the average size 1 per piece of equipment and stop,
total distance and time traveled, total service time, reload time, driver, equipment,
overtime, and total cost information, the average cost for the selected period, cost per size
1, distance (mile, kilometer), and stop, and the total number of stops.
Notes: The Resource Utilization report is an excellent tool that provides an easy-to-read
overview of routing activity. However, the report is based on Roadnet projected
data only, not actual data.
For a sample of this report, refer to the Resource Utilization Report Sample.
Printing the Report

Step 2: Right-click on the Resource Utilization report in the Reports list window. From
opens.
Operations Guide
1019
Route Exceptions
Route Exceptions
For a selected period of time, this report lists the route date, route ID, driver 1 and 2,
equipment, and any exceptions associated with each route. You can choose to sort the
report by route date or driver.
For a sample of this report, refer to the Route Exceptions Report Sample.
The Route Exceptions Options window lets you choose to sort the report by route date or
driver, and to choose whether or not to include routes with zero exceptions.
Step 2: Right-click on the Route Exceptions report and select Options from the menu
that pops up. The Route Exceptions Options window opens.
The Route Exceptions
Options window lets you
customize the information
contained in the report.
Step 3: Click either Route Date or Driver to choose what you wish to sort by.
Printing the Report

Step 2: Right-click on the Route Exceptions report. From the pop-up menu, select
1020

Route Metrics
Route Metrics
For completed routes in a selected period of time, the Route Metrics report lists the total
number of stops for delivery, the number of canceled stops, the number of stops that were
on time, the percentage and total number of stops that the driver met and missed, as well
as the total number of stops the driver was early or late for as compared to the planned
arrival times within a set time window, the average number of minutes spent servicing
each stop, the total number of miles for the route, the total number of miles not including
the stem distances, and the average number of miles per stop, and the average service
miles per stop.
Note: If time windows are not assigned, open/close times are used to determine time
windows met. If open/close times are not assigned, time windows are always
considered met.
For a sample of this report, refer to the Route Metrics Report Sample.
Printing the Report

Step 2: Right-click on the Route Metrics report. From the pop-up menu, select Preview
to the printer. The Selection Criteria window opens. From this window, you are
able to set up your report.
Operations Guide
1021
Route Pallet Pick Sheet

The Route Pallet Pick Sheet report lists all product to be loaded on the truck by pallet.
Unlike the Pick Sheet, there are spaces for the picker to initial after the order has been
picked, and spaces for the checker to indicate the orders have been checked. In addition,
a duplicate sheet is printed for each pallet, with the word Validated printed in large type
down the side so it is easy to determine when the order has been validated. You can
choose to include all orders, or only those that have not been printed. This report is
intended to be used in conjunction with the Prebuilt Pallet Pick Sheet report. Orders that
were marked as printed in a Route Pallet Pick report will not be included in this report;
they will be indicated as already picked.
For a sample of this report, refer to the Route Pallet Pick Sheet Report Sample.
You can choose to include all orders in the Route Pallet Pick Sheet report, or only those
orders that are not marked as printed. If an order was marked as printed when included on
a Prebuilt Pallet Pick Sheet report, it will not be included in this report.
Step 2: Right-click on the Route Pallet Pick Sheet report and select Options from menu
that pops up. The Route Pallet Pick Sheet Options window opens.
Orders only.

Printing the Report

Step 2: Right-click on the Route Pallet Pick Sheet report in the Reports list window.
opens.
1022

Step 4: Select the Routing Sessions(s) and Route(s) to include in the report.
Operations Guide
1023
Route Pick Sheet
Route Pick Sheet

The Route Pick Sheet report lists all product to be loaded on the truck by bay or pallet.
Unlike the Pick Sheet, there are spaces for the picker to initial after the order has been
picked, and spaces for the checker to indicate the orders have been checked. In addition,
a duplicate sheet is printed for each bay or pallet, with the word Validated printed in large
type down the side so it is easy to determine when the order has been validated. You can
choose to include all orders, or only those that have not been printed. This report is
intended to be used in conjunction with the Prebuilt Pick report. Orders that were marked
as printed in a Prebuilt Pick report will not be included in this report; they will be indicated
as already picked.
For a sample of this report, refer to the Route Pick Sheet Report Sample.
You can choose to include all orders in the Route Pick Sheet report, or only those orders
that are not marked as printed. If an order was marked as printed when included on a
Prebuilt Pick report, it will not be included in this report.
Step 2: Right-click on the Route Pick Sheet report and select Options from the menu
that pops up. The Route Pick Sheet Options window opens.
Orders only.
printed, check Unprinted Orders only,

Printing the Report

Step 2: Right-click on the Route Pick Sheet report in the Reports list window. From the
1024

Route Pick Sheet
Operations Guide
1025
Route Summary Statistics

The Route Summary Statistics report provides a snapshot of the days routing, on a routeby-route basis. It is an excellent indicator of adherence to company guidelines for routing
and scheduling. One benefit of the Route Summary Statistics report is that, at any given
time, you can generate it using either projected or actual data from Roadnet, or using
actual data from MobileCast.
The Roadnet version of the report shows each route for the selected delivery date (or
session) and includes the following:
Total distance traveled
Total number of stops
Travel, service, break, and total run times
Driver, equipment, and total route costs
Type of equipment
Quantities for the route
The statistical information includes the equipments percentage of capacity (how full was
the truck?) and the average number of units delivered per hour, mile, and stop. The bottom
of the report details the average, lowest, and highest routes for distance traveled, number
of stops, time (travel, service, breaks, and total), and cost (driver, equipment, and total).
This version of the report displays statistics using either projected or actual data.
The MobileCast version of the report shows each route for the selected delivery date and
includes the total distance traveled, total number of stops; travel, service, break, and total
run times, total route costs, the type of equipment, and the quantities for each size for the
route. The statistical information includes the average number of units delivered per hour,
mile, and stop. The bottom of the report details the average, lowest, and highest routes for
distance traveled, number of stops, time (travel, service, breaks, and total), and total cost.
This version of the report displays statistics using actual data.
For a sample of the Roadnet version of this report, refer to the Route Summary Statistics
Report Sample.
For a sample of MobileCast version of this report, refer to the Route Summary Statistics
Report Sample.
1026

Notes: The option to use actual or projected data is available only in the Roadnet version
of the Route Summary Statistics report. The MobileCast version of this report uses
only actual data.
To print this report, see Printing the Route Summary Statistics Report.
The Data Options window of the Route Summary Statistics report lets you specify
whether the report uses actual Roadnet data or planned data.
Step 1: Right-click on the Route Summary Statistics report and select Options from the
menu that pops up. The Route Summary Statistics Options window opens.
Step 2: Click the Use Actual Data box to include actual data instead of projected data.
Do not click the box if you only want to use projected data.
Click the box to
generate the report
using actual data.

Printing the Report
Before you print this report (Roadnet actual data), you need to import actual data
from an onboard computer system. See Importing OnBoard Data for more information.
Or, manually enter the actual data.
Step 2: Right-click on the Route Summary Statistics report in the Reports list window.
window opens.
Step 4: Click to select the route session and route for which you want to preview or
print the report, and click [OK]. Your report will either appear in Preview mode
or print directly to your printer.
Operations Guide
1027
Note: You can choose to include actual or projected data on the Roadnet version of the
Route Summary Statistics report. See Setting the Route Summary Statistics
Report Options for more information.
1028

Route Variance
Route Variance
For a selected period of time, the Route Variance report lists completed routes, the stops
on the routes, the driver for each route, the depart from depot time, the return to depot
time, the return to depot distance, the total runtime, the total distance, the planned and
actual miles to the stop, any pre- or post-route time, and the planned and actual arrival and
departure from each stop.
For a sample of this report, refer to the Route Variance Report Sample.
Printing the Report

Step 2: Right-click on the Route Variance report. From the pop-up menu, select
Operations Guide
1029
Selection Summary
Selection Summary
The Selection Summary report provides you with a brief routing summary of the planning
session(s) and territory(s) you selected. The report includes the total cost, sizes 1, 2, and
3, distance, travel time, service time, and the number of stops per route.
Note: The Selection Summary report does not provide the same level of information as
the individual reports provided with Territory Planner.
The Other column includes breaks, waits, layovers, pre-route, and post-route
times.
For a sample of this report, refer to the Selection Summary Report Sample.
Printing the Report

Step 2: Right-click on the Selection Summary report. From the pop-up menu, select
Step 3: Select the Planning Session(s) and Territory(s) to include in the report.
Step 4: Click the checkbox(es) that correspond to the week(s) and day(s) you want to
1030

Session Analysis
Session Analysis
The Session Analysis report is used to analyze differences in the locations contained in a
master session and the sub-sessions that are formed from the master session. The report
lists the session, total cost of each, sizes 1, 2, and 3, service time, number of locations, and
the number of stops for each selected session in Territory Planner.
For a sample of this report, refer to the Session Analysis Report Sample.
Printing the Report
Step 1: Enter the Reports module. The Reports window open.

Step 2: Right-click on the Session Analysis report. From the pop-up menu, select
Step 3: Select the Sub Planning Session(s) to include in the report.
Operations Guide
1031
Session Summary
Session Summary
The Session Summary report offers a wide range of information pertaining to the selected
planning session(s) and territory(s) for any given week and/or day in Territory Planner.
This report includes the total number of locations (assigned and unassigned), territories
(active and inactive), weeks (active and inactive), routes (active and inactive), quantities
(total of assigned and unassigned for sizes 1, 2, and 3), total assigned stops, total distance,
and the total cost of a route. The Session Summary report also provides you with detailed
route stats, such as distance, cost, travel time, service time, total time, and number of
stops. These route stats are divided into three columns (minimum, maximum, and
average), giving you an in-depth breakdown of your routes.
Notes: The Other column includes breaks, waits, layovers, pre-route, and post-route
times.
For a sample of this report, refer to the Session Summary Report Sample.
Printing the Report

Step 2: Right-click on the Session Summary report. From the pop-up menu, select
Step 3: Select the Planning Session(s) to include in the report.
1032

SKU by Package Type
SKU by Package Type

The SKU By Package Type report lists, by route, all SKUs grouped by package type. This
report pulls data from FleetLoader and includes route, route date, quantity for each SKU
and package type, weight of each SKU and package type, and description for each SKU.
For a detailed list of loading information, refer to the SKU Summary Sheet.
For a sample of this report, refer to the SKU by Package Type Report Sample.
Printing the Report

Step 2: Right-click on the SKU by Package Type report. From the pop-up menu, select
Step 4: Select the Routing Session(s) and Session(s) to include in the report.
Operations Guide
1033
SKU Summary Sheet
SKU Summary Sheet

The SKU Summary Sheet lists, by route, all SKUs loaded on a particular vehicle, sorted
in numeric order by SKU. This report pulls data from FleetLoader and includes delivery
date, equipment ID and type, plus total quantity and weight.
For a list of package types per SKU, refer to the SKU By Package Type report.
For a sample of this report, refer to the SKU Summary Sheet Report Sample.
Printing the Report

Step 2: Right-click on the SKU Summary Sheet report in the Reports list window.
or select Print to print directly to the printer. The Selection Criteria window
opens.
1034

Standard Route Driver Survey
Standard Route Driver Survey

Used with: Roadnet
The Standard Route Driver Survey lists all stops on a standard route and is designed to
gather information about your locations. You can hand the Driver Survey to your drivers
or salespeople and have them obtain valuable information about your accounts that can
be entered into Roadnet.
The report lists each locations name and ID, as well as address and phone information.
This report gives the driver space to write in important delivery-related information about
each location, such as open/close times, time windows, average fixed and variable service
times, and any comments or special instructions.
For a sample of this report, refer to the Standard Route Driver Survey Report Sample.
Printing the Report

Step 2: Right-click on the Standard Route Driver Survey report in the Reports list
Step 3: Click to place a checkmark beside the Route(s) for which you would like to run
the report, or [Ctrl]+click to select multiple routes.
Operations Guide
1035
Standard Route Stop List
Standard Route Stop List

Used with: Roadnet
The Standard Route Stop List provides a list of the stops on each standard route in stop
sequence. This Roadnet report is a good tool for determining when it is necessary to make
changes to your standard routes. It can also help determine when to delete inactive
accounts. You can choose one or multiple standard routes to generate a stop list.
The report contains a separate heading for each route. This heading lists all the routespecific information, such as route ID and name, start time, driver(s), depot, any pre- or
post-route time, whether a helper is assigned to the route, and what travel time model the
route uses. For each route, the body of the report lists the sequence of stops and provides
the location ID and name, address information, the salesperson assigned to that account,
and the last sale date (the last date the location received a delivery).
For a sample of this report, refer to the Standard Route Stop List Report Sample.
The Standard Route Stop List report gives you the option to display time windows and/or
last sale date.
Step 1: In the Reports Window, right-click on the Standard Route Stop List report and
select Options from the menu that pops up. The Standard Route Stop List Options
window opens.
Step 2: Click to place a checkmark next to the option(s) you want to include in the
report.
Choose to include the
last sale date and/or
all time windows.

Printing the Report

Step 2: Right-click on the Standard Route Stop List report in the Reports list window.
window opens.
Step 3: Click to place a checkmark beside the Route(s) you would like to run the report,
or [Ctrl]+click to select multiple routes.
1036

Roadnet Stop List
Roadnet Stop List

Used with: Roadnet
The Stop List produces a list of stops on a route, as well as general information about the
route. The report provides an excellent, condensed version of other Roadnet reports that
detail the stops on a route, such as the Manifest and the Itinerary. You can print a Stop
List for any or all of your routes.
The top of the report displays information about the selected route (route ID and
description, driver, equipment, number of stops, start and end time, and depot). The body
of the report lists the stops on the route in stop sequence, the location ID and name, time
window information, arrival and departure time, service time, delivery quantities, and as
much address information as will fit on one line of text. Additionally, there are symbols
on the report denoting specific information about a particular stop.
Symbol
Legend

closing.
For a sample of this report, refer to the Roadnet Stop List Report Sample.
Printing the Roadnet Report

Step 2: Right-click on the Stop List in the Reports list window. From the pop-up menu,
select Preview Report to view the report before printing, or select Print Report to
Operations Guide
1037
FleetLoader Stop List
FleetLoader Stop List

The Stop List displays the contents of the equipment by stop. The report can be used by
the driver to determine where the product for each order is located, especially if you load
your trucks warehouse friendly.
The report is generated from FleetLoader and lists the contents of the truck by stop, and
its location on the truck, as well as the location ID and order number for each order. The
route ID and date, equipment ID and total number of units on the truck are listed at the
top of the report.
For a sample of this report, refer to the FleetLoader Stop List Report Sample.
Printing the FleetLoader Report

Step 2: Right-click on the Stop List report in the Reports list window. From the pop-up
menu, select Preview Report to view the report before printing, or Print Report to
1038

Territory Location
Territory Location
The Territory Location report simply lists all the locations in a given territory. The report
is generated with data from Territory Planner and includes the location ID, location name,
address, phone number, account type, and the service pattern set for the selected planning
session(s) and territory(s).
For a sample of this report, refer to the Territory Location Report Sample.
The Territory Location Options window allows you to choose whether the report will
include assigned (routed) or unassigned (unrouted) locations, the field the report will be
sorted by, and whether or not you want the location's complete address.
Step 2: Right-click on the Territory Location report and select Options from the menu
that pops up. The Territory Location Options window opens.
Step 3: From this window, you can choose to sort by sizes 1, 2, and 3, service pattern
set, location account, location address, location name, location ID, or the location
phone number, and whether to sort in ascending or descending order. Next, select
whether to show just the assigned or unassigned locations. Lastly, you can also
choose whether to print the full report (showing the complete address), or the
condensed report (showing only the street address).
Select to show
routed or
unrouted
locations.
Click the dropdown arrow to

choose from a list
of sort options
Choose to print
either a full or
condensed report.

Printing the Report

Step 2: Right-click on the Territory Location report. From the pop-up menu, select
Operations Guide
1039
Territory Stop List
Territory Stop List

The Territory Stop List report includes stop-specific information from Territory Planner
and summarizes the delivery information for a given territory. The report lists the stop
number, location name, location ID, sizes 1, 2, and 3, distance, travel time, arrival time,
and service time for the selected planning session(s), territory(s), week(s), and day(s).
For a more detailed report on your stops, refer to the Global Itinerary report.
For a sample of this report, refer to the Territory Stop List Report Sample.
The Territory Stop List Options window allows you to choose whether or not you want to
print the location's complete address.
Step 2: Right-click on the Territory Stop List report and select Options from the menu
that pops up. The Territory Stop List Options window opens.
Step 3: From this window, you can choose whether to print the full report (showing the
location name and complete address), or the condensed report (showing only the
location name).
Choose to print either a full
or condensed report.

Printing the Report

Step 2: Right-click on the Territory Stop List report. From the pop-up menu, select
Step 4: Click the checkbox(es) that correspond to the week(s) and day(s) you want to
1040

Territory Summary
Territory Summary
The Territory Summary report lists delivery information by territory for the selected
planning session(s) and territory(s). The report pulls data from Territory Planner and
contains the territory ID, sizes 1, 2, and 3, distance, travel time, service time, total time,
total cost, the number of locations, and the number of stops.
Notes: The Other column includes breaks, waits, layovers, pre-route, and post-route
times.
For a more in-depth look at your territories, refer to the Week Summary report.
For a sample of this report, refer to the Territory Summary Report Sample.
Printing the Report

Step 2: Right-click on the Territory Summary report. From the pop-up menu, select
Operations Guide
1041
Time Window Exception

The Time Window Exception report lists locations whose arrival or departure time for
their delivery is not within the locations time windows (preferred delivery times). For
instance, if the arrival time to Simons Salon of Szechuan is 08:30 and their time window
is 09:00 to 11:00, then Simons would appear on the report.
The report shows location ID and name, route and stop number for that location, time
windows, arrival and departure times, hours and minutes early or late, and size 1, size 2,
and size 3 totals. If you are using the Roadnet version of the report, you can generate the
Time Window Exception report using planned or actual information. If you are using the
MobileCast version of the report, then the times are displayed using the locations time
zone.
Note: If you use projected data for the Time Window Exception report, you must be
confident that the planned service and travel times in Roadnet are accurate before
using the report as a performance assessment tool.
For a sample of this Roadnet report, refer to the Time Window Exception Report Sample.
For a sample of this MobileCast report, refer to the Time Window Exception Report
Sample.
The Time Window Exception report gives you the option to specify a priority range (1
being the lowest and 9 being the highest) for locations displayed in the report. For
instance, if you wanted to look only at locations with high priorities, you could generate
the report so that it displays only those locations with a priority range between 7 and 9.
Step 2: Right-click on the Time Window Exception report and select Options from the
menu that pops up. The Time Window Exception Options window opens.
Step 3: Enter the priority range, 0 being the default (meaning no set priority), 1 being
the lowest, and 9 being the highest.
Step 4: Click the Use Actual Data check box to include actual data in the report.
Enter the reports priority range

for locations, and choose whether
or not to include actual data.

1042

Printing the Report
Before you can print this report (Roadnet actual data only), you must import actual
data from an onboard computer system. See Importing OnBoard Data for more
information. Or, manually enter the actual data.
Step 2: Right-click on the Time Window Exception report in the Reports list window.
opens.
include in the reports. You can enter the date manually, or click the arrow to open
Step 4: Click to select the route session, if printing Roadnet, for which you want to
preview or print the report.
Operations Guide
1043
Time Window Override

Used with: Roadnet
The Time Window Override report lists locations that have time window overrides set up
for one or more days of the week. For instance, say a location has a time window type
with its regular preferred delivery times at 11:00 to 16:30 hours, but on Thursday that
location prefers to receive orders after 16:30. You can set up a time window override on
Thursdays for that location, and the location will appear on the Time Window Override
report.
The report pulls information from Roadnet and lists location ID and name, open/close
times and time windows based on the time window type, delivery days, and the override
for that day.
For a sample of this report, refer to the Time Window Override Report Sample.
The Time Window Override report also gives you the option to sort by any of the
following: delivery days, location ID, time window factor, description, open time, or time
window override open time.
Step 2: Right-click on the Time Window Override report and select Options from the
menu that pops up. The Time Window Override Options window opens.
Step 3: Click on the Sort By drop-down arrow and select the item you want to sort by.
Choose whether you want the report sorted in ascending or descending order.
Click the drop-down arrow to

choose from a list of sort
options.

Printing the Report

Step 2: Right-click on the Time Window Override report in the Reports list window.
or Print to print directly to the printer.
1044

All Loads
All Loads
The All Loads report lists all SKUs loaded on a selected date. The SKUs are sorted by
package type and the number and percentage from each part of the warehouse is
displayed. The warehouse information is based on the Quantity per Layer and Layers per
Pallet entered for the package type in FleetLoader.
For a sample of this report, refer to the All Loads Report Sample.
Printing the Report

Step 2: Right-click on the All Loads report in the Reports list window. From the pop-up
include in your report. All routes for those dates will be listed at the bottom of the
Operations Guide
1045
Week Summary
Week Summary
The Week Summary report provides you with an in-depth breakdown of your routes from
Territory Planner for a specific week. It contains a detailed list that includes territory ID,
territory location, sizes 1,2, and 3 quantities, distance, travel time, service time, total time,
total cost, and the number of stops for the selected planning session(s), territory(s),
week(s), and day(s).
Note: The Other column includes breaks, waits, layovers, pre-route, and post-route times.
For a brief summary of territory information, refer to the Territory Summary report.
For a sample of this report, refer to the Week Summary Report Sample.
Printing the Report

Step 2: Right-click on the Week Summary report. From the pop-up menu, select
Step 3: Select the Planning Session(s) and Territory(s) to include in the report.
Step 4: Click the checkbox(es) that correspond to the week(s) you want to include in
the report.
1046

Report Samples
Report Samples
Report Samples
One of the most useful features in the Roadnet Transportation Suite is the ability to
generate and print any number of informative reports. These reports provide you and your
employees with information on your routes, warehouses, and territories, as well as
loading diagrams.
In this section there are samples of every report featured in the Roadnet Transportation
Suite. For a brief explanation of its contents, as well as general instructions on how to
generate and print the report, refer to the Working With Reports section.
The following reports are available in Roadnet. To see a sample of the report, click on the
report name.
Actual vs. Projected
Route Summary
Driver Performance
Actual vs. Projected

Stop Detail
Driver Service Log
Order Summary
Carbon Emissions
Driver Survey
Prebuild Order
Customer Invoice
Compartment Detail
Key Performance
Indicators Detail
Compartment
Summary
Key Performance
Indicators Summary
Route Summary
Statistics
Consolidated Off-Day
Delivery and Less Than
Minimum Stops
Less than Minimum

Orders
Standard Route Driver

Survey
Distance by Area
Less than Minimum

Stops
Standard Route Stop

List
Draft Daily
Stop List
Driver Itinerary
Location Returns
Time Window
Exception
Driver Manifest
Off-Day Delivery
Exception
If you are using the FleetLoader Truck Loading module, these reports about loading the
equipment are also included. To see a sample of the report, click on the report name.
All Loads
Load Validation
Diagram
Operations Guide
1047
Driver Productivity
Multi Pallet Pick Sheet
Route Pick Sheet
Driver Checkout Sheet
Pallet Pick Sheet
Stop List
Load Productivity
Pick Sheets
SKU by Package Type
Load Truck Diagram
Prebuild Order
Customer Invoice
Loaded SKU Summary
Prebuilt Pick Sheet
Prebuilt Pallet Pick

Sheet
The following reports are available in Territory Planner. To see a sample of the report,
click on the report name.
Carbon Emissions
Session Summary
Days Serviced
Territory Location
Global Cost
Re-Route Analysis
Territory Stop List
Global Itinerary
Selection Summary
Territory Summary
Global Manifest
Session Analysis
Week Summary
The following reports come standard with MobileCast. To see a sample of the report, click
on the report name.
AVP Route Summary
Driver Utilization
Resource Stop List
AVP Stop Detail
Employee Hours
Worked
Route Exceptions
Carbon Emissions
Employee Hours
Worked Summary
Route Metrics
Delivery Detail
Route Summary
Statistics
Metrics
Route Variance
Driver Performance
Location Statistics
Time Window
Exceptions
Driver Returns
Notes
Driver Statistics
1048

AVP Route Summary Report Sample
AVP Route Summary Report Sample

For more information about this report, refer to Working with the AVP Route Summary
report.

! "#$%
&%'(
)

*
%+
,%- . -%''( / &,
( ,%0
1 2 !!3 / 4
(-.(0
/
4 *
5 ) 6 7 '
4 8&'( (1% // !
) 4 !!!!
4
+
)

! !
4
4

+
5 ) 6% 7
+9
1
!!!=
!!#2

!!<
!!<
!!<
!!<
!!<
!!<
:;

+
+
+
!!!!!!
$!!
3##
!!<
!!<
!!<
%
.
!!<
< * .
!!<
/
4 *
5 ) 6% 7 '
5 ) 6 7 '

) 4 !!!!
4 5(% +5%-( //

4
+
)

4
4

+
+9
1
:;

+
+
+

!#!!!3
!!!2=
! 2$=
=2
!
!!!!!!
#"!!
$3#
%
!#!!!3
!!!2=
! 2$=
=2
!
!!!!!!
#"!!
$3#
!!!!!!
!!!!!!
!!!!!!
!!
!!!!!!
!!!
!!!
< * .
!!<
!!<
!!<
!!<
!!<
!!<
!!<
!!<
!!<
!!<
!!<

)

4
4

+
+9
1
:;

+
+
+
.

!2 !=
!! !3
!#$
#$3

!
!!!!!!
3!!
# "
%
!#!!!3
!!!2=
! 2$=
=2
!
!!!!!!
#"!!
$3#
.
/!!!=
/!!#2
/
/#
!!!!!!
/$!!
3#
/2==<
/ $2<
/ # <
/ "#<
!!<
!!<
!!<
/"2<
"#<
< * .
/!!<
/! !
/#!<
;) >

*

?

? )

Operations Guide
1049
AVP Stop Detail Report Sample
AVP Stop Detail Report Sample

For more information about this report, refer to Working with the AVP Stop Detail
report.

% %
! " # #

$
%

&
%

&
%

&

&

%

!) "

%

(
(

(
(

&

&

*

*
*
*
*
*
*
*

*

#!

'

&&

&

&

*
*
*
*
*
*
*
*
*

&

&

*
*
*
*
*
*
*
*
*

&

# "

&

+

*
*
*
*
*
*
*
*

&

*

&

#! "

&

*
*
*
*
*
*
*
*
*

"
,

*
*
*
*
*
*
*
*
*

+
"
&

&

*

*
*
*
*
*
*
*

*

#

&

&

&

*
&*
&
*
*
*
*
*
*
*

+
,

&

@+, "

*

"
)

*
*
*
*
*
*
*
*
*

&

&*

*
*
*
*
*
*
*
1050

Actual vs. Projected Route Summary Report Sample
Actual vs. Projected Route Summary Report Sample

Used with: Roadnet
For more information about this report, refer to the Actual vs. Projected Summary section.

! "#$%
&%'(
)

*
%+
,%- . -%''( / &,
( ,%0
1 2 !!3 / 4
(-.(0
/
4 *
5 ) 6% 7
5 ) 6 7 '
4 8&'( (1% // !
) 4 !!!!
4
+
)

! !
4
4

+
+9
1
!!!=
!!#2

!!<
!!<
!!<
!!<
!!<
!!<
:;

+
+
+
!!!!!!
$!!
3##
!!<
!!<
!!<
%
.
!!<
< * .
!!<
/
4 *
5 ) 6% 7 '
5 ) 6 7 '
4 5(% +5%-( //
) 4 !!!!
4
+
)

4
4

+
+9
1
:;

+
+
+

!#!!!3
!!!2=
! 2$=
=2
!
!!!!!!
#"!!
$3#
%
!#!!!3
!!!2=
! 2$=
=2
!
!!!!!!
#"!!
$3#
.
!!!!!!
!!!!!!
!!!!!!
!!
!!!!!!
!!!
!!!
< * .
!!<
!!<
!!<
!!<
!!<
!!<
!!<
!!<
!!<
!!<
!!<

)

4
4

+
+9
1
:;

+
+
+

!2 !=
!! !3
!#$
#$3

!
!!!!!!
3!!
# "
%
!#!!!3
!!!2=
! 2$=
=2
!
!!!!!!
#"!!
$3#
.
/!!!=
/!!#2
/
/#
!!!!!!
/$!!
3#
/2==<
/ $2<
/ # <
/ "#<
!!<
!!<
!!<
/"2<
"#<
< * .
/!!<
/! !
/#!<
;) >
* ? ? )
Operations Guide
1051
Actual vs. Projected Stop Detail Report Sample
Actual vs. Projected Stop Detail Report Sample

Used with: Roadnet
For more information about this report, refer to the Actual vs. Projected Stop Detail section.

! !

!!

!!!!

!!!

!!

!!!

!!

!!!!

!!!!

!!!!

!!!!

!!!

!!

!!!

!!

!!!!
!!!
!!!

!!!!
!!!
!!!

!!!!!!
!!!!!
!!
!!!

!!!
!!!
!!!
!!!
! !
!!!
!!

! !
!!!
!!

!!!!!!
!!!!!!
!!
!!!
!!!
!!!
!!!
!!!
!!!

!!!

!!!

!!
!!

!!
!

!!!!
!!!
!

!

!!!!
!!!
!

!

!!!!!!
!!!!!!
!!!!!!
!!
!!!
!!!
!!!
!!!
!!!
!!!
!!!
!!!

1052

Operations Guide

$
"

!

+

#
"#

"$
"

"
"
!

+

+

#$%&'
()

+

"
"

%

* )+ ,-

+

!

! " !
Carbon Emissions Report
Carbon Emissions Report
Used with: Roadnet, MobileCast, Territory Planner
For more information about this report, refer to the Carbon Emissions Report section.
1053

3

!
3

2
2

!

!

2

3

2

3

Used with: Roadnet
For more information about this report, refer to the Compartment Detail Report section.
1054

2

3

Used with: Roadnet
For more information about this report, refer to the Compartment Summary Report section.
Operations Guide
1055
(
-
+
#
#%++
#%-3
!
#

,".2"-%%
!"# $%&'%$(%)*+),,*-.,,,-&./&/0"+
#
#

123# 4
#/ "#$
!

!
"#!$
'
'

*-,

*+,
&
5

6$25
%
%$%5
0

%
)
%$%5

0
&
%
$
'

*,

2
-

*
%
%

*-
%
%

*+
"
Used with: Roadnet
For more information about this report, refer to the Consolidated Off-Day Delivery and Less Than
Minimum Stops section.
1056
Days Serviced Report Sample
Days Serviced Report Sample

For more information about this report, refer to the Days Serviced section.
7
2
,8""#"$%7$,%&,&2

!"+! !#

&'& () * +
/, 0 12
, ----- (!
++!.
#
0
0#+
#.--
5

0 .&
0
+ 7
98 0: '

--
$
$%
$
8
8
46

()
<
<
<
;+ %

0#+
#.--
0#+
#.--*
7 /
9 7 5
+&
&'&+ %-9
+
% + ' -#; + + %*
,
8
9%
%
Operations Guide
1057
6

) ; 0)

) ; 0 )

!
) ; 0!)
!
"
!
1058

) ; 0)
!
) ; 0 )

) ; 0!)

) ; 0!)
;
. ?C
!
"

4#"(/B(;9))0
)$/+%(!2/0
"
) ; 0 )
0 !-(+%);

"
424 3(9%3$(;(*
)$/+%(!2/0
"
) ; 0)
0 -
)$/+%(
:(*
!
"
#
($()
A9'
)$/+%(!"/0
"
) ; 0)
0 -3%(;<""
(7
22"2)++%;
)$/+%(!"/0
) ; 0)
0 -((($0%>>%(

6
!
!
%(#2""!! "--34#!-
"
"
) ; 0")

) ; 0")
:(%$);0: 6 #5/0
"
) ; 0!)
0 "-
);9('
)

":(%$);0: 6 #5/0

) ; 0 )
0 !-0(*(9('<!

2" (($:%: 6 ##/0

) ; 0)
0 -%;
(3()3(0
)/;'
(7
#-#
* + ,
!=/((;0
:(($: 6 #5/0

) ; 0)
0 -3%(;<
,)-. /0&)1)(234 >0

78

78
($%&('((%$()
"(9(0:9': 6 #5/0

) ; 0)
0 -)3($(
(
%(#2"" !#--34 25-
#
./0$
!"#

(7

(7

)6

)6

0

0

.

.
01 / 01
'( = )* +
Delivery Detail Report Sample
Delivery Detail Report Sample
For more information about this report, refer to the Delivery Detail section.
$- % %
$- % "

5.678' ()*9+,-
../5

"

' (
")#*$ +, $

!"#$ %
&
Distance by Area Report Sample
Distance by Area Report Sample
Used with: Roadnet
For more information about this report, refer to the Distance by Area section.
Operations Guide
1059
/
-

$

$

$

$
(

%

/

(./0

/
-

(

#
$
%

#
$
/

(./0

"
/
-

(

$
#
#
$
%

%#&'(
)*
+,%'-&
#
$
/

(./0

#

!"#
/

/

/

'
+/
#

+/
#

+/
0001 1-2 3

#

!1!

#

#

. //
Distance by Jurisdiction Report Sample
Distance by Jurisdiction Report Sample
For more information on this report, see the Distance by Jurisdiction section.
1060
Draft Daily Report Sample
Draft Daily Report Sample

Used with: Roadnet
For more information about this report, refer to the Draft Daily section.

2 2 2

2

!

"

!
#

$

( #'
'
! *
'

&
'*'
*

!
*

*

!

!
!

*

:.

'
!

"
$'
'

!
!

.
%

'
%

%

%
%
%

/
. /
/

'

%

"
$'
*
: -
"
()(
*
!
%
"
$'
!
!

%

' $$
*
)$
#*
'

&
"
! :

"
()(
*

+

!*

!

: /

. %

0 D 0 D D E F D " 0
, 0 E EE 0 EE + 0 %
Operations Guide
1061
Driver Checkout Sheet Report Sample
Driver Checkout Sheet Report Sample

For more information about this report, refer to the Driver Checkout Sheet section.
123456578945:;8<34=>55?;8=2@A5B2@5

!
"#
$%(&'(&()*
.$

(/.!0$
(/.!01!$
$ !
2$
31..4
+,
+,
-+,*&(
+1
*
25
25

2(*
89
:
96&)"(&6

96&);)<&6

96&&)"(&6
:
96&(+

96&$(;)<&6
67-1

(/.!02.00 1
3
4
) -.1

$ > ?2.
2.=
*
?2.
1062


"

Operations Guide
$
! *

"

"

$

- + + G + *
+ " + " " , " +

$
$

& #&
$ & )0 '(
$$

$
$

$
$
&& #
%#

'(

$
$

#

'(

$
$

$
$

%& '(

#

$

"

!

0

0

Driver Itinerary Report Sample
Driver Itinerary Report Sample
Used with: Roadnet
For more information about this report, refer to the Driver Itinerary section.
1063
Driver Manifest Report Sample
Driver Manifest Report Sample

Used with: Roadnet
For more information about this report, refer to the Driver Manifest section.

#

&

''''''''

''''''''
!

"

&$

&&
$

%
&
&&

&

(''''''''
(
''''''''

%
&
$(

) " ) " " ! * " )
+ ) ! !! ) !! , )
1064

, ,
(

01

)

03

%*)
(*
) - 5 6 5 7- - 5 7- * ) 2
%(4- (
( &
(

002/
02/
0120/
/ !*
33
31
00
)
53.6708190:;73<3/=0>?1@7:A1

0

%*)
()
12/
12/
102/
/ !*

02
2
2
.)-
!" "#$%&'"
2
2
2
'--
)(-
2
02
02
*,-
23
2
21
.)-
23
2
2
'--
(* +
B3C=<0D.>8150
2
2
20
*,-
23
2
2
.)-
2
2
2
'--

2
2
2
*,-
-./0112134112
Driver Performance Report Sample
Driver Performance Report Sample
Used with: Roadnet
For more information about this report, refer to the Driver Performance section.
Operations Guide
1065
!.5#+
03$5+3
!./#0$1'2!3#44
#)*!+
#0

$%& !"! 0

'
(

4260 7896/4:;8 <68
!"#

' 4
,

./0123 4530
5

-
4 6
Driver Productivity Report Sample
Driver Productivity Report Sample
For more information about this report, refer to the Driver Productivity section.
1066
Driver Service Log Report Sample
Driver Service Log Report Sample

For more information about this report, refer to the Driver Service Log section.
6 =

! !

&'(

5 5

! !
!! &

&

&

!
!
!!!
!!!
!!!!
!!!

!!!
!!!
!!!!
!!!
&'(

&

&

!
!
!!
!!!
!!!!
!!

!!
!!!
!!!!
!!
&'
' &(

&

&

!
!

!!
!!!
!!!!
!!

!!
!!!
!!!!
!!
('' (

&

&

!
!
!!
!!!
!!!!
!!

!!
!!!
!!!!
!!

(

&

&

!
!
!!!
!!!
!!!!
!!!

!!!
!!!
!!!!
!!!
&(

&

&

!
!
!!!
!
!!
!!!!
!!!

!!!
!
!!
!!!!
!!!
Operations Guide
1067
!"
?&@
.3'!((&
#',
' ")8
#'
?&@
.3'!((&
..
7 =
#
'!&,-4.4
) % ,+-4+,--2
' ")8
4,-
#
."&"'"3;
#
'!&3"&4--..3"%#%'5"&
) % -0+,1+,--2

"#$%&'&()*%&+,)-$%./&&01-.#23&+#2& #3&%- &'& %/#/

#',3.#
#'3.>
3 8
9,':
3!&
<) =
<) =
-----1/4/1.('!""3%
3 8
*
++,--./+/+,-
()
%.&&!"#&'
-
-
-
-
'7
-
-
'7
-
-
6)
1
1
6)

2
,
,
%8

%8
#$ ! #$

Driver Returns Report Sample
Driver Returns Report Sample
For more information about this report, refer to the Driver Returns section.
1068
Driver Statistics Report Sample
Driver Statistics Report Sample

For more information about this report, refer to the Driver Statistics section.

4 45

/

!

"

Operations Guide
1069

.

+
(
"
1070

A/(
B /

&=.'+' #* >#.%$' ? ; < 0
>2#..#$@+
+
!8 #$$%+*..' $ 3%%+%49 : ; < 0
4.,>+
#++%4#' =,&
.
#
.
&

1

1 2%&'+ '3#$ 00

1 )

$/ $ 0 $/

!"#
:!" :!"
:!" :!"
%(4

3
7
!
!

6*
+1

+
'.*'$-
!
!

#$%%&'()*+,$-))).$/($%/+01)2+0)341)3556)7)*$8&9$:0
$*'$ +,$*'-
'+/($,)

3

4/5
4
$%#&' $(
4+(
/

)
Driver Survey Report Sample
Driver Survey Report Sample
Used with: Roadnet
For more information about this report, refer to the Driver Survey section.

!!
%+
!"!

! !
!
,
!-!
!
,+
! !!
!

!
&'$
"#
$%
Operations Guide
=+

+

2
. 345/ 45

,+.
3
;

<+
2
%
:
3
!2
%+
!!
-%* %*

%8(%,
","%8

&#5(,4"
6##7
9:
3
!2

%.
'
#
%.
/$,
0
1

#!%!
4#)

! !

! !!
!".#
$%"&"'%%"()
#*(%

*5)- *2

!2
"3.

!

"## %
Driver Utilization Report Sample
Driver Utilization Report Sample
For more information about this report, refer to the Driver Utilization section.
&'$( %)%* ''

%$%
7 8
#'$ ,%
+
$

%
'
./%'
- "'

-

-1
02
02

2!
1071
1072

+* *
+* *

09'
+* *
'9

:::
+* *
+* *

'''
+* *

999
+* *

+* *
+* *

+,+
+* *

+%'4%
+* *
+ 9

++
+* *
+* *

-"
+* *

+* *
+ 9

,
+* *
+* *

)))
+* *

%,0
+* *
528

"607%
+* *
+* *

%"607%
+* *

+%"607%
+* *
,+

"0/4
+* *
+* *
+
(+
%&#
0
1
%6
*

+3
+3
+3
+3
+3
+3
+3
+3
+3
+3
+3
+3
+3
+3
+3
+3
+3
+3
+3
+3
+3
+3
+3
+3
+3
#

5
5
5
5
5

8
8
8
8
8
8
8
8
8
8
8
8
8
2
2
2
2
2
2
(+

5

5
5

8

5
8

8

2
+%/0,0/
22
2
55
5
,

2

2

8
2
2

2

2

8

5

5
2

5

8$8
2
2
5
5
%
$
"&#(

-%.
%&#'()*+
#
&

5

5
2

5

2
/

5

5
2

5

2
(

01&
!"
#

+(!&

+

*

3
Employee Hours Worked Report Sample
Employee Hours Worked Report Sample
For more information about this report, refer to the Employee Hours Worked section.
Employee Hours Worked Summary Report Sample
Employee Hours Worked Summary Report Sample

For more information about this report, refer to the Employee Hours Worked Summary section.
-
</%

/

!"
#%
/
;
&<#( %)%* <<

%#%
"<# >%
+
<
-
&<#
#
/

%
./%<
- !<

-

-%* %*
-1
02
02

2
Operations Guide
1073
1074
5/ /
6(5/
*
60/7 &
'8 /
9

(5/

(5/
"

!!

'
'
'
/'
'
''
'
/'
$
%&!!'
()*"(+*","-".+(.

! "#
'
$'

'
0
'1
'
0/'
-(
2*034

/
;
Equipment Utilization Report Sample
Equipment Utilization Report Sample
For more information about this report, refer to the Equipment Utilization section.
Equipment Utilization Metrics Report Sample
Equipment Utilization Metrics Report Sample

For more information about this report, refer to the Equipment Utilization Metrics section.
-:<%;<?;<

!
!7
"#$% "&$'()& "*"%)

+!,-.
/012/01
3-$&
"4, 56

5$
7$8

00
*,55!9
:;$
:;69%!
:;<!=3,!%!69
>!$

>!$8
007
Operations Guide
1075
#
#
#
#

#
%

%

#

#
"#
"#
%

"

#
#
% "

"

"

"
!

/

%
"
"
"
#$
"
"
#$
"
"
#$
"
"
#$
"

%

&#
&#

$
$

"
" "

"
" "

"
" "

"
" "

9
"$
"$

##
#"

##
#"

##
#"

##
#"

"$
"$
#

#

#

#

2
Global Cost Report Sample
Global Cost Report Sample
For more information about this report, refer to the Global Cost section.
1076
Operations Guide

#
#
-&+&!$$
-&+&!$$1
-&+&!$$6
-&+&!$$
-&+&!$$0
-&+&!$$
-&+&!$$$
-&+&!$$)

7

1
6

0
$
1077

$
3
*

#
-&+&!$$7
)
#
#
#
#
#
#
#
-&+&!$$

-

*
#

*
$$$$$'(##+ (!&
'()*+,+-./*+01.2)*34++51.3(67+8(6+7++,+4
8.*)$6
7)
. 3
+-!&!*)$6
/ 3
4

0$'

(
,
3,*)$0
%& /
0/ *.
+
,
&% *)6
)+

#3$$
&% *)6
)+

#3$$
&% *)6
)+

#3$$
&% *)6
)+

#3)$$
&% *)6
)+

#3)$$
&% *)6
1/
5%

% *)
01-2
#3$$
-

/ 4

7

)

/ 43 +&
+ /
-

!,
$$7
$71
7
$$
$)
$$)
$$$
$$$
$$$
$$$
$$$
$$1
$$)
.
)$
)$)7
7)
$1
6
61
6))
6$6
170
1)
.
,
$
$$$0
$$$0
$$$0
$$$0
$$$0
$$$0
$$$0
$$$0
$$$0
$$$0
#.

)
60
170
$
$$
$$
$$
$$
)
76
0
*
#
$%&
'&

& (!( " (&

)$
)
)
)
)
)
)
)
)
)
)
#(
$
$
$
$
$
$
$
$
$
$
$
#()
$
$
$
$
$
$
$
$
$
$
$
#(

Global Itinerary Report Sample
Global Itinerary Report Sample
For more information about this report, refer to the Global Itinerary section.
Global Manifest Report Sample
Global Manifest Report Sample

For more information about this report, refer to the Global Manifest section.
*9, :)$92)
AB = A9
= 1
@)
;<&:"

#
')"

! "
$ %
&' ("
!
(%
&' ("
$#

#

$
(
# % )
,( %*%
( %*%

)" - $
.
0+/9 ( /

""
#.//
)%*%,1%
( # ( %+%
%./
! %
+%./'222222
%0
# %
+%//'222222
) $
$
) $9
$
) $;
$
) $+
$
) $1
$
) $*
$
) $0
$
) $/
$
0&1

%*%,.%
.%/%,1%
"34 56
.
- 7(" 8)
.
+-
:
8
""
#.1
/
%*%,.%

""
.
9
%*%,.%

"".
.
;
)%*%,1%
%*%,.%

""/
.
+
%*%,.%

""9
.
1
%*%,.%

"";
.
*
%*%,.%
- 7 )
.
0//-
8#!
(#.0/
)%*%,1%
1%..'222222
# %
1%/'222222
%;
! %
1%/+'222222
%0
# %
1%9+'222222
%;
! %
1%;'222222
%0
# %
*%'222222
.%/%,1%

)%*%,1%
! %
%0
&
.)
( /
8
""
#.1
%;
.%/%,1%

)%*%,1%
1%1'222222
&
./)
( /
8
""
#.1
1%1'222222
# %
.%/%,1%
)%*%,1%
! %
%0
&
./)
(
8
""
#.1
%*
.%/%,1%
.)
( .
8
""
#.1
+%;0'222222
&+
)%*%,1%
+%90'222222
# %
.%/%,1%

.;)
( .
8
""
#.1
! %
%0
9&1.
)%*%,1%
%+
%;
! %
*%+'222222
%0
# %
*%+'222222
&
.%/%,1%

%.;
! %
*%9.'222222
%0
# %
*%;.'222222
&1+
%*%,.%
.%/%,1%
1078

Global Time/Distance Report Sample
Global Time/Distance Report Sample

For more information about this report, refer to the Global Time/Distance section.
# ' %<) = =/,-'%-%--
$ 8 =
= $ C
8
D678#6 %'#<#&%$%7$
< == ,
=/

#=

#=
<
& <

<
7

<
& <

-

!"#"$"%"&/!&"/!'"

'"!('!)""'!)" '&'
Operations Guide
1079
Key Performance Indicators Detail Report Sample
Key Performance Indicators Detail Report Sample

Used with: Roadnet
For more information about this report, refer to the Key Performance Indicators Detail
Report section.

* + +,,+

-
.

,+/ 0 ,+/
1 -23-

!

"

# $ $
1080

Key Performance Indicators Summary Report Sample
Key Performance Indicators Summary Report Sample

Used with: Roadnet
For more information about this report, refer to the Key Performance Indicators Summary
Report section.

@

!

!

!

!

!

!

!
!

!

" # #
Operations Guide
1081
Less Than Minimum Orders Report Sample
Less Than Minimum Orders Report Sample

Used with: Roadnet
For more information about this report, refer to the Less Than Minimum Orders section.

"
$
' ,

,

1082

Less Than Minimum Stops Report Sample
Less Than Minimum Stops Report Sample

Used with: Roadnet
For more information about this report, refer to the Less Than Minimum Stops section.
%

"

%

%

%

%

"
"
"
%

%

"
"
%

% !% "
#
#
#
"
%
##
#"
#
#
#
"
%
"
$%
% !%

#
#
#
%
"
% &

"
%
#

'

#
#
#
%
#
%
"

%
"
! (
' %

%
"
%

% %
%

#
#
#

%
"

%

%

%
#
#
#

%

% !%

%
"
%%

#
#
#
"
%

"

"
%
"

#
#
#
"
%

"
%
"
% %

"
"
%

%
% %%
#
#
#
#
%
"
% %
%
#
#
#

%

'

* E
) * E

)

""
"
#"")

""
"
#"")

""
"
#"")

Operations Guide
1083
Load Truck Diagram Report Sample
Load Truck Diagram Report Sample

For more information about this report, refer to the Load Truck Diagram section.

+

- . /
+ ,

+

!
+
#
!
"
#
+
"

% +%

&&&&&&

% + +%

&&&&&&
#
"
$

"

#

"
$

"
$

"
$

"
$

"
$

"
$

"

% ' +%
&&&&&&
% +( + +%

&&&&&&
#
"
$

" )

#

"

% % +%
&&&&&&
% +(
#

&&&&&&
# )
"
$

"

# !

"

%
#

&&&&&&

% +(
+ +%
&&&&&&
#
"
$

"

#

"

%
#

&&&&&&
% +(

#

&&&&&&
#
$

"
#

"

#

"
"

"
*? &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
$

*? &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
1084

&'
*'%&,"3,211-"#
''(')
&'
)
*''.,::,8##::#
.
*''.,8,8-:#
*'.&+,1:23,844 #
''(')
%+
''(')
''(')
''(')

..-1
,7.5/ .
5-
*''+,-
",8"
00#==/%/#0$0#==
1!

,76.-/1.6

2.</06///

+,-./0/123./4526-.78//9:67,;</!,;/"</#=/0//8$8=4!
%0'#''
$'#''
%0'#''
./0#''
$%&#''
!"#
4,.///
#//
Load Productivity Report Sample
Load Productivity Report Sample
For more information about this report, refer to the Load Productivity section.
Operations Guide
1085
Load Validation Diagram Report Sample
Load Validation Diagram Report Sample

For more information about this report, refer to the Load Validation Diagram section.

(5 5 6 7
777

(

% %%
' % %

%

%

%%

%%

' %'

' % %'

' " # %'

' $ % %'

"

' %' %'

' $

%

"
'

!
' $
% %'

%
' %

!
' $

!

"

&'

&'

1086

Operations Guide

'

)

)

)

. /

'

#

'
'

' !
" +"

* ( "
# &

)
!
-

)

' % !

' !
" +"
# &

%!

)
&"
# &

$ %!

'
'

#

! "

(
% ( + %,
# !
# +
("

,

& , &
(

% # % +"
% *
( +%#

%! ( "

% )

'
'

'
'

)

$
'
'

)

$

'
'

)

$

$&%&(

Location Delivery Cost Report Sample
Used with: Roadnet
For more information about this report, refer to the Location Delivery Cost section.
1087
1088

'

)

)

)

. /

'

'
'

#

' !
" +"

* ( "
# &

)
!
-

)

' % !

' !
" +"
# &

%!

)
&"
# &

$ %!

'
'

#

! "

(
% ( + %,
# !
# +
("

,

& , &
(

% # % +"
% *
( +%#

%! ( "

'
'

'
'

)

$
'
'

)

$

'
'

)

$

Used with:
For more information about this report, refer to the Location Delivery Cost section.

00!
0
!

0 !
056!
)
$
#$%#&
8#$9# *8(#
'+7$ *'2(&
#*+& 2(# 4 2''
1# $*' *'2(&
$ (
! "
012345 6789
>;?0 % '20 :&24?025 (&22;

2
2
2

03
56

0
36

3
3
3

)
' (./
$'*'( #+(

'(# )
-

0

,
,
:;10 < 3= <
Location Returns Report Sample
Location Returns Report Sample
Used with: Roadnet
For more information about this report, refer to the Location Returns section.
Operations Guide
1089

$1(&1+7
$1(&1+ 3
$1(&1+
6/%'
:+6;!1
(&$0&)8(&;(;

$1(&1+7
$1(&1+
$1(&1+=
$1(&1+7
$1(&1+==
$1(&1+77
1!44>
)/?/$/
)&!/!
!&/,&892
!&+&/(&/
!;1/)!11

$1(&1+7
1090

)* "

!
'
(
<.*

&"
7

23
2
2

2
72
2
23

2
2

7
2
23

!"
7

23
2
2

2
72
2
23

2
2

7
2
23

%!"

23

23

$
%

$
&"
*
/$0/)/$1(&1+!&!(!
@& "
- A " A B
' "
( A
(1)

$1(&1+
,!<;/+?&

!5/))/!;9 =
,&)/;15!/

$1(&1+ 2

$1(&1+
1/8/!92

<!(;
(1$54&;&$$

$1(&1+
6(
'

$1(&1+
6(
'

$1(&1+
6(
'
6&+92
$1(&1+

$1(&1+7
&$8
)/!&5)&+(&/)+

$1(&1+3
!
'
4)5(/)++6+(
"
$

$

+

=
!#

!#

!"

./0 +1*23,<+4.53
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

,
-
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

/

$
:*+,,-,.;,,-
Location Statistics Report Sample
Location Statistics Report Sample
For more information about this report, refer to the Location Statistics section.

3
3
8 8448
8

8$
8

7443

8
8
A6D7
8658
5
D7D889D73D8
4C
D7
D999DDD8D
D7
D996
7DD8=
A98
8(
8'
D5884D343
88
=4
=
4
$= 4
4!846

$
8 88
7443
6
34D5674
7
89 '46=

8

A6D7
5758
$8=
4
$=84
$ =4
4!846

8

=
88 =

=

DD79
6'!>6>6()6A((>
=

=
=
(99
7889
8=
=
=
8639

8=
8=8
=$

DD79
=
=
=
(99
86+

'87(9D6
D

=

=
=
8639
=
=8
=

DD79
=
=
=
(99
D
=
=
=
8639

C
MobileCast Driver Performance Report Sample
MobileCast Driver Performance Report Sample
For more information about this report, refer to the MobileCast Driver Performance section.
Operations Guide
1091
Multiple Pallet Pick Sheet Report Sample
Multiple Pallet Pick Sheet Report Sample

For more information about this report, refer to the Multiple Pallet Pick Sheet section.

!

!

"

#
#
"

$ "%
! #
! ##
1092

Notes Report Sample
Notes Report Sample

For more information about this report, refer to the Notes section.
'3)**0)*&60)3)**

.,/0 )1'23*4)5,63
&'()**+*,-**+
,##$#
%&"

'

!"
%

(

(
*
) +
%
'%

(
*

+#, -#
) %!./
%
'%

(
*
%
4'%
4
+ 0$1 2-
) % +
+&#1 3 -
)"!"
Operations Guide
1093
Off-Day Delivery Exception Report Sample
Off-Day Delivery Exception Report Sample

Used with: Roadnet
For more information about this report, refer to the Off-Day Delivery Exception section.

! !

9
:
55 & 4& 9

: !!

!!!

!!!!
!! !!

!!

!!

!! !!

!!

!!
!! !!

!!

!!
!! !!

!!

!! !

!! !!

!!

!!
!!
!! !!

!!

!!
!! !!

!!

!! !
!! !!

!!

!!
!! !!

!!

!!
!! !!

1094

Operations Guide

&%
&'!
&%
&'!
&%
&'!
&%
&'!
&%
&'!
&%
&'!
&%
&'!
&%
&'!
&%
&'!!
&%
&'!$
&%
&'!
&%
&'!
&%
&'!!
&%
&'!!
&%
&'!!
&%
&'!!
&%
&'!!
&%
&'!
&%
&'!
&%
&'!
&%
&'!!
&%
&'!
&%
&'!
&%
&'!
&%
&'!
&%
&'!
&%
&'!!
&%
&'!
&%
&'!
&%
&'!
&%
&'!
&%
&'!
&%
&'!!
&%
&'!
&%
&'!
&%
&'!
&%
&'!
&%
&'!$

" ) ' )()
) ' )()

!
!

!
!
!
)

! " " # ! #!!$%
)
%"% " %(%
" % %
%% "(%
(
% " ( &'
()
%'
% @( %@(
%
(
'
%"% "
(
% %% &(

" (
%
"(
%

$ )

)
"& (%(
(%( ## $
$&&&%( '
('%
&'%
$&&&%( '
('%
&'%
%@( % %!
"& $('
&&
%( "& & '
(&'& '
' ((
% $
('
% &@@(
)
!
''(
)
)
)
@% (
%%'
%
('
! "('
# % &

()
()
'

!
!

$
!
!

!

!!
!!

!!
!!

!!
!!

!!
!!

!!
!!

!!
!!

!!
!!
!
!

!!
!!

!!
!!

!!
!!

!!
!!

!

!!
!!

!$

!!
!!

!!
!!

!!
!!

!!
!!
!

!!
!!

!!
!!

!

!!
!!

!!
!!

!!
!!

$

!

!!
!!

!!
!!

!

!!
!!

!

!!
!!

!

!!
!!

!!
!!

!!
!!

!!
!!
!

!!
!!

!!
!!

!!
!!

!
!

!!
!!

!!
!!

!!
!!

!!
!!

!!
!!
!

!!
!!

%
&)

((

! !!
&('$$&%( ((
&'

!!

!

!

!

!

!

!

$

$

!

$

$

$

)
!

!
!$
!
$
!
!
!
!
!
$
!
!
!

!
$
!
$
!
!
!

!

!

!

!

!
$
!
!
!
!
!
!
!

!

!
!$
!

!
!
!

!
!
!

!

!
!
!
!
!

!

!
$
!
!
!

!

!
!
(

&%'(
)
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!
!!

$!
!
!
!
!
!!
!!
!
!
!
!!
!
!
!
!
$!
!
!!
$!
!
!
!
!
!!
$!
!
!!
!
!!
!!
!
!
!!
$!
!
!
!
!

$!
!
!
!
!
!!
!!
!
!
!
!!
!
!
!
!
$!
!
!!
$!
!
!
!
!
!!
$!
!
!!
!
!!
!!
!
!
!!
$!
!
!
!
!

$!
!
!
!
!
!!
!!
!
!
!
!!
!
!
!
!
$!
!
!!
$!
!
!
!
!
!!
$!
!
!!
!
!!
!!
!
!
!!
$!
!
!
!
!

Open/Close Exception Report Sample
Open/Close Exception Report Sample
Used with: Roadnet
For more information about this report, refer to the Open/Close Exception section.
1095
Order Summary Report Sample
Order Summary Report Sample

Used with: Roadnet
For more information about this report, refer to the Order Summary section.
5*6,--8;.,-):;6,--

!"#$%&'
)*+,--.-/0--1
2345678-2,9/:6
!()*0
( #+#,-(4
()./)0
!"#$%&'
!0
2
1
1
2
."$
#
!(
,
,
, .!6!"

345
!(

.!6!"

65
*
!(

.!6!"

5#
!(
,
,
, .!6!"

5 6$2
!(
,
,
, .!6!"

5 #6!
*
!(,
.!6!" ,

7
!(
.!6!"

7
!(8

.!6!" 8

!(=
=
=
= .!6!" =
!(
,
,
!(
!(
,
!(
!(
1 .(
20
4
(2
,
, ,
,
,
,
,

,

,=
7

7

=
, .!6!"

7,
*
.!6!"

56$2

,
,
, .!6!"

56$2

,
,
,
, .!6!"

56$2
, ,,
8
.!6!"

56$2

, ,
!(
.!6!"

56$2
, ,
8
!( ,
8
8
8 .!6!" ,

5(#(#

!(

.!6!"

5(#(#

!( 8

.!6!" 8

5)92
, ,
8
!( =

.!6!" =

5)92
8
,
!(
,
,
, .!6!"

5)92
,
,8
!(
,
,
, .!6!"

5!*)7().
*
!(

.!6!"

7:. ;5..
*
!(

.!6!"

)"5!"!<
*
,
,
)2
)./..)
!(
,
,
, .!6!"

<):/.*)0,
*
!(
,
,
, .!6!"

!"
*
!(,
.!6!" ,

5"0,
*
!(
.!6!"

6!0)
*
"6
!(8

.!6!" 8

57:6/6
"6
!(=
=
=
= .!6!" =

:!=!"7""5
*
6!
!(
,
,
, .!6!"

(67:!!"6
*
!(
.!6!"

")!*".)(

"6
")>6:*"5>
!(
,
,
, .!6!"

,
8 ,
!(
,
,
, .!6!"

6:*"5>:6)
,,
!(
,
,
, .!6!"

57:6)!*6)

8
!(
.!6!"

")"!".

,,
"!!(.)6!
57:6
)"+"!<<6)
!(,
.!6!" ,

!(

.!6!"

+):!776!"6
,

!(8
=
=
= .!6!" 8

)6!"!07""5
8

!(=
,
,
, .!6!" =

8
=
!(
.!6!"

>)?)0
*
!(
,
,
, .!6!"

<)>00
,
!(
,
,
, .!6!"

6!"6
,

,

8
*77.0
)/6)
:!7 )">!!(
( *!
!(
,
,
, .!6!"

!(
.!6!"

:!77)<!!(
>):!*)
6:"7==
74#21#
1096

Pallet Pick Sheet Report Sample
Pallet Pick Sheet Report Sample

For more information about this report, refer to the Pallet Pick Sheet section.
&
'(
)*($+",$)-)./0

!"#$ %
*"
((
1.

&(66,@)./*(-..A)

&'()*+,@-../0123045
2

&
&# (

4##

"

&
6'
.3/ 45678 93,

;!
&# (

4
5

/
& 75

/
06&;75
<

/
4*675
,.

/

/

764
,.
:'

/

";!
21(
9-$
.
Operations Guide
1097
Pick Sheet Report Sample
Pick Sheet Report Sample

For more information about this report, refer to the Pick Sheet section.
+8 9$7=8*7=*B)7:7

7)8*=>=8
7 0 :
,-./
*#+
" #$%&'()"#

!
"'
0"($
-1
0"($#(
(
1
'*#"2
3/+44''15
651')+7489:5;&&
3
<
=+( , >
=>
.+
&',,87
,
#
/
=>
&?' 4@87
,
#
/
=>
&;6')+A487
,
#
/
1
876,.4
1
=1>
;6'-84.,+
,
#
/
1

4

(4"$%
*#+
1098

Prebuild Orders Customer Invoice Report Sample
Prebuild Orders Customer Invoice Report Sample

For more information about this report, refer to the Prebuild Orders Customer Invoice section.
@;:<=;B,3*8-B3.8.:+

!"#$ %)%

&'(! )&!(*!!

( +% ,-.%/012+34%,
( %2'$5!$)!6
$ 1$
9
%% +-.%
(%
(8

(5'
3 ,)
1 &$
!2$
1!2$!
% ;+ ,
7"1
:;+ ,
7"1
:;+ ,
7"1
:;+ ,

"(+.%
<+ ;+ ,
$ =1$)!$6

(
%% +-.% 0
(%
(8

(5'
3 ,)
1 &#>&
/1>&
% ;+ ,

"(+.%
<+ ;+ ,
$ 1

9!'($6!$&'(!(
%% +-.%0=
(%
(8
(5'
3 ,)

1 &#&$
5&
1
&5&
0
1 $!!2$
1!2$!
% ;+ ,

"(+.%
<+ ;+ ,
Operations Guide
1099
Prebuilt Pallet Pick Sheet Report Sample
Prebuilt Pallet Pick Sheet Report Sample

For more information about this report, refer to the Prebuilt Pallet Pick Sheet section.

; !
77< (
,?,-

!"#
! ($%!(!+&'(((
* &
)*
! "#
'* +,--./*0,
' *(1( 2
'3
,
(

/ 5+6!&+5
#

#
/ 5+6768+5
9.
+4
'&%
! "#
!+&( 5'

+((+&( 1( +65
1100

Prebuilt Pick Sheet Report Sample
Prebuilt Pick Sheet Report Sample

For more information about this report, refer to the Prebuilt Pick Sheet section.
*)! -,,

!, "#$%&" '$()

%*#
+%

*
(
%
*,

-..//001 %
2
-
(
*%&3
"
5
(4

(#,
/6
0 $"'/#"$
/6
/"#"$

0/ $"''7"$

'7"$
81

*
"#$ (*

")"#&" '$*
Operations Guide
1101
Route Pallet Pick Sheet Report Sample
Route Pallet Pick Sheet Report Sample

For more information about this report, refer to the Route Pallet Pick Sheet section.
%
9 +

*; --:/09/*C*

! "#$%

*
+(,

&'())
$
+
(-

'!**,,))./$

$
(+ 0 1
$2

'

%
"
3
$#
,
,
)/4"!,#"!4

)/4 ,#"!4
7)
&'())
$4*56
(
"# 4 !$(

"% "# 0 "! 4(
1102

Route Pick Sheet Report Sample
Route Pick Sheet Report Sample

For more information about this report, refer to the Route Pick Sheet section.
+
8 5

($* '',)8,(9(

+;$

! "#
$
+'!(
%&

)
0
-

* ++ ,% +*
-)
-
* . ,% +*
/
)
,+% +*

1 *23
,+% *
++% "4++*
Operations Guide
1103
Re-Route Analysis Report Sample
Re-Route Analysis Report Sample

For more information about this report, refer to the Re-Route Analysis section.
5 2 , 7 /*

!
"#$%"&'&()**"$
* +,
-. &'.
'-1,&'..
*1(.2&3
0/
(.

('4
($-&$'
*
&+,5
$
.
-/
1,
.
$
.
1,
.
7 6
7 6
7 6
7 6
7 6
7 6
7 6
7 6
7 6
7 6
"
6 1
-('$'. 7
($-&$'
*
-5
67(9*/
7
+.
77
($-&$'
*
5&/1
89
&0/
:0. 9
($-&$' 7
*
51-4
6775 .0
4/4. 67
($-&$' 8
*
51/-$
5;+
$+.

($-&$'
*

-*/

$+.

($-&$'
*

-*/

$+.

($-&$'
*
7
7-*/

$+.

($-&$' 9
*
8
7-*/
7
$+.

($-&$' 6
*

-*/
7
$+.

1104

<<A
<?<A
7
7
=
= D
= D
= < 9
+
D <

=> > < ?@A

= 8

<?<A ??C
<<A ?A
?<<A ??
<?<A ??A
= 6

<<A 7 <:<A
6 = @
8+ 6 +
8 D
@@
C?
?A

2
@A
@CCC

D
?:?+
?A

' 6
8

Resource Route By Day Report Sample
Resource Route By Day Report Sample
For more information about this report, refer to Working with the Resource Route By Day Report.
Operations Guide
1105

"
$

#

# !

"

!

/

9 D
<
<

B8+&6B 8
+ $8
9 "
!+
B
D <
89
<

' 6

Resource Stop List Report Sample
Resource Stop List Report Sample
For more information about this report, refer to Working with the Resource Stop List Report.
1106
Operations Guide
A
%D D
%%
%A"D
% %
3
DA"
%33
AA
%A
3%"
A"
% 3
8
3A

8%
3 " 3 =
3 "
9 ' (

%A%
3 %
3A
%%
D%"%
"%A
8%
C

; % %% % """;
3
%3 3
""
%A
%33
D D

A A3
A
"3%"
D"3
"3

%333D
%D%
3 3
%33%"
A"33
"
% %3
%
%%%
%
D%3

8
%D% %% %
"8,"" ,
&

3A33
D
"
333D
% D
"
3

D3
"3
%%3

%%D
"3

3
"
3
33
%3
"A
"
%%3
"
A
"D
%33
% 3
"3A
%

A
%3%
%
%%"
A"

"""

D3
3

"

8%
A
"3
D3D
%3A
33%
8
%A
"
33
3

8
% C %
Resource Utilization Report Sample
Resource Utilization Report Sample
Used with: Roadnet
For more information about this report, refer to the Resource Utilization section.
1107
+4
*1;+<

(4&4 2$-

-!$( $2#$. #
-$
)*+,-.-/01,-2304+,56--/78395*:-),

$
" 1$,*$&23
$
+9 725$#+! 2'5$8-( $2
" 1$,*$&23
$
7# :8
7 ":8
*1;+<,- 2
$
(/- 9$1$(0

+4$,- $7* &8
25$7+! 2'5$8
2$-,-5"6 +
$4
$460,7+
+(15<
$%&
$ #
',(()(!'*+,'

!"
Route Exceptions Report Sample
Route Exceptions Report Sample
For more information about this report, refer to the Route Exceptions section.
1108
Operations Guide
&1$ 2$%& &
&1$ 2$%& &
&
%5
&&(%0( 5
54&%
13
014

(
' !
(
.* * !(
.*)
")(
.*)
(
.* * )

(
%5
) *
(
"!!/
)

%2
%5

) /) *
&
8
!,
-

!,
-8

44+
%2
!,
-
99, !-
-

$
!"
! !-
-!
&&&+
44+
&&+
+
0
+
+

&&+
5+

!,
-

4+
+
&&+
&+
0+

&
&
0
%+
+
0
!,
-
2

!,
-
!,
- 6-7
&
&
%

' !

!
"#

$ %$%& &' %$ %$%& &
!,
- 6/7
2
&

%

) *

9. */

-" * ! ! "/
* !
"(3&&

")
&1$ 2$%& &

")

( -
$ -4

4;
<;; ;</
&
&
&
-
&&( 2(3
&&(% (34
&&(%3(0%

!
* !,
-
- !,
-
+ !,
-

- !,
-
+ !,
-

2&&0
150
14%1

)
!
.*
*
!,
-
!
/

*
%2$%5
%2$%5
0$%5
%&02
014
001
)
.*
44+
44+
+
2&&0
24
31

)
%&02
%40
0%4

)
*
.*

Route Metrics Report Sample
Route Metrics Report Sample
For more information about this report, refer to the Route Metrics section.
1109

"

%&

$

4
!
#
"
"
"
4
4
"$

4

=
$ $
>
= >>
#
"

$

#$

$
#

$#

""

#$
"

#

#
#
"
"
$
#

'

"#

$
$$

""
"#

#

$
"
"

#

Roadnet Route Summary Statistics Report Sample
Roadnet Route Summary Statistics Report Sample
Used with: Roadnet
For more information about this report, refer to the Route Summary Statistics section.
1110

#

4
%&

"$

4

"
"

$
"
"
"
4
4
!
#$
$#
""

#$
"

$

"
#

$
#

#

#
#
"
"
$
#

(

"#

$
$$

""
"#

#

$
"
"

#

'
MobileCast Route Summary Statistics Report Sample
MobileCast Route Summary Statistics Report Sample
For more information about this report, refer to the Route Summary Statistics section.
Operations Guide
1111
3
$3>$%/&
."1
1112
/77
#
)
#4!786
#47""
#
*!!!!
*!!!!
.# 1

.1
! !6
!""6
!8!86
9
26;
7 2
!68
!!69
(#
*67"
*6"!8
* ; 9
* 86;
* 6 ;
*!8
6;67
7""
7""
7""
7""
7""
7"8
#4
"62

.#
*
1
.1
!786
!"76
!"876
!6"96
8
266
7
7"8
#4
#4
!667
#

*!!!!
*!!!!
!!"* !!"
.# 1
$>

>
3 (
/"62

3/*45,6-7,895/:/+

$%&'##(&&$
( ?@@?A+ ?4

? 5

#&$>&#3>
(&<&#
8
#($
>$%/&
6
"
<$=(
7
,&/,%:

/
455
&3$(&*
2 !!"
+,$&
! !"#
#
(#
*67"7
*6"!9
* ;68
* 886
* 666
*!82

.#
*
1
7""
!786
7""
7""
7""
7""
7"8
7"8
77

9
;7
87
88
7;6
!
788
97

#
6
!!

!
6
!!
9;
76
!
!!
!
!!
!
!!
!
!!
!
!!
!
!!
!
!!

6!
29
2;
;6
98
7
)*+,--.-/0--.12
*;
!
* 6!
29
*2;
;6
*98
7
*9
;7
*87
88
*7;6
!
*788
97

.#
*
1
-&.%/01

77
"62

Route Variance Report Sample
Route Variance Report Sample
For more information about this report, refer to the Route Variance section.
Selection Summary Report Sample
Selection Summary Report Sample

For more information about this report, refer to the Selection Summary section.
)$ ! ("// %%& $4(

!("(#$%!&'($
! () *
+$)
-

!,
-

! . /
$
!

#
0
!,
(
1
1
(
11
111(
1111

2

0(
0
1
1
1(
13
11011
1111

4 *

1

1
1
1 3
1 3
11
1111

0
(
1
1
(
11
111(
1111

. /
1
1
1
1
111
1111
111111
1111
4 *

0
(
1
1
(
11
111(
1111

0
(
1
1
(
11
111(
1111

2

1
!,
0(
0
1
1
1(
13
11011
1111
4 *

1

1
1
1 3
1 3
11
1111

0
(
1
1
(
11
111(
1111

1
2

1
1
1
111
1111
111111
1111
4 *3

0
(
1
1
(
11
111(
1111

0
(
1
1
(
11
111(
1111

2

1
0(
0
1
1
1(
13
11011
1111
4 *0

1

1
1
1 3
1 3
11
1111

0
(
1
1
(
11
111(
1111

1
2

1
1
1
111
1111
111111
1111
4 *

0
(
1
1
(
11
111(
1111

0
(
1
1
(
11
111(
1111

2

1
0(
0
1
1
1(
13
11011
1111
4 *5

1

1
1
1 3
1 3
11
1111

0
(
1
1
(
11
111(
1111

1
1
1
111
1111
111111
1111
1
(
1
1
(
11
111(
1111

3
1
1
35(3(
00
1 10 (
1111
2

2

4 *(

1
0
(3(

$ 2 6

*)

. + 2
+ 2 /
Operations Guide
1113

!' !
&&
() 67 -
'&
&&
() ' !"*&&
,

%&
!"
&
&
&
&

-
7/ ,
.
7-9.
&
&
&
&

&#
&+#%
&+#%
#$

&
&
%

'
&
&
'

!9
Session Analysis Report Sample
Session Analysis Report Sample
For more information about this report, refer to the Session Analysis section.
1114
Session Summary Report Sample
Session Summary Report Sample

For more information about this report, refer to the Session Summary section.
. / 0# 1002 2 & / # #'
0 3-4
*
2 -
4 5

!"
%&
&
&
#$
%
'
() ' !"*&&
&&
&
&
&+#%
&
&
() 67 -
&&
&
&
&+#%
&
&
'&
&
&
&#
'
,
Operations Guide
1115

4+$6

6
-(
$5
(
4+$6

8
8
:

4+$6

8,
6
9-:5;+&7
8

!0
5&)()!"#
7+(
$

7+)(
:5;+&7
7+5&:5;+&7
7++5&"+&7
7+5&"+&7
)
!)(/(%
!)*&++ ,-).
!"#$%&+"&'(
%(

6
-&+"+&7
!"#
(2+ 3$&%-4&$&%

#+"
+
0. >05? -5#5

!0
++*
,8
,8
,
1

8,
8
++*
,
1
+ ?
SKU by Package Type Report Sample
SKU by Package Type Report Sample
For more information about this report, refer to the SKU by Package Type section.
1116
'

:):*60,.
5:
:;
:7
0 '
%

(
:)*6004"(
7)(*60$,8490"6
0"6
)(*604"8490"6
0"6
!
)*604"(
4"$,$
:7
7
."#
,1'2
$

$,-,#
."#
,1'2
&
$

$
%

&"''(())*$
+
&
!!"#

(5
3
/'&
./<=<0#10022&/#
/"."#!0
$

SKU Summary Sheet Report Sample
SKU Summary Sheet Report Sample
For more information about this report, refer to the SKU Summary Sheet section.
Operations Guide
1117

"

" &
' ,
"

", *

",

", ,

,) ),"

-- *,

" *,
1118

* & *

& "

)*

" ", *
"
+
& ", *
"
+
& ", *
"

(( &" "" ", * +
"
(
(
,'
", * +
"
(
" ", ", * +
"
(
)," ", * +
"
+
+ )," ", * +
"
+
)) " ", * +
"
++
+ )) " ", * +
"
+(
(( ", )

", *
#
"

,

#
$
%

,
,

!

!
!
#

Standard Route Driver Survey Report Sample
Standard Route Driver Survey Report Sample
Used with: Roadnet
For more information about this report, refer to the Standard Route Driver Survey section.
Operations Guide
'!
'!
''
''
')
')
:
:
#
#

$ 9
#))
&,'
#))
&,'
#))
&,'<'
#))
&,'<'
#))
&,'<)
#))
&,'<)
#))
&,':
#))
&,':
#))
&,')
#))
&,')
#))
&,'!
#))
&,'!
3
&

$

012
-'
$
&78
* !
* '+%,--'!
* " 3

5 ')-12

$
$
$
$
$
$
$
$
$
$
$
$
'))
'))
'))
'))
'))
'))
'))
'))
'))
'))
'))
'))
0
./0123245612785901:;22<1:91=:/>?2/>2?2()2322(;
#))
#))
1 3
#))
#))
&$>>
&$>>
#))
#))
#))
6.,
#))
6.,
#))
,2,=&
#))
,2,=&
.,=8.$
.,=8.$
#))
&1.%$
#))
&1.%$
+
+
, 3
&

3
6%&
$
'())
1! 3
'!))
'())
'())
'())
'())
'())
'())
'())
'())
'())
'())
'())
'!))
'())
<<<++,&%+.1!')
'!))
<<<++,&%+.1!')
'!))
##)$2+&7,&%+.1!')
'!))
##)$2+&7,&%+.1!')
'!))
:))$17=18,&%+.1!')
'!))
:))$17=18,&%+.1!')
'!))
:))$17=18,&%+.1!')
'!))
:))$17=18,&%+.1!')
'!))
)=&&&$,&%+.1!')<
'!))
)=&&&$,&%+.1!')<
'!))
:)%;1$,&%+.1!')<
'))
'))
'))
'))
'))
'))
'))
'))
'))
'))
'))
'))
1!, 3
:)%;1$,&%+.1!')<
1', 3
&

.
453 0

453
$%$&$

$

/%!

! "#
Standard Route Stop List Report Sample
Standard Route Stop List Report Sample
Used with: Roadnet
For more information about this report, refer to the Standard Route Stop List section.
1119
' 0

1&0

.
'' ## /
1120
'( 7/!
$%& 5

&

"
"
'( 7/
'( 7/"
"
'( 723
'( 72=
'( 727
'( 728

"
"
"
"
&
*

$ '
7""

7""

7""

$
7""

7""

7""

7""

0
! ""
! ""
,9 ; (::
! ""
($ <;9
! ""
< > :'*

''
, (
0
,! (
0
= 4
7"7
44/
4 =
/ 2
227
!2=
"!
.
? .
@
+

0
? .
@
+
0
@&
.
=
A
@
0
( ? .
+

'

8!= , ,- '' :' !
4 " , ,- '' :' !
2"= , ,- '' :' !
=/3 0& .
= ! !"4
"=!/ , ,- '' :' !
"7!/ , ,- '' :' !
"/" , ,- '' :' !
,!
0
"282 , ,- '' :' !
,
0

B ? .
=
+

.
0
==
0 ? .
&
+

.
0
==
C ? 5

$'9 )$ ,-
! ""
< :- (<
! ""
,- '' ;'
! ""
'(9 '
(
0
'

&
(0

0
" 4

&

&
0
""2"
$
#&
0
""2"
$#&
0
""2"
&
0
"""
1&0

$()*$
&
. 0
"3/4

$ # !
.
!

$ '

! !" " # $%& &

.
+ 0
&
,- #

?3 1
0
0''!)''?!'!
=4=
= "
7"
4!3
///
/"=
2!3
!22

.
""
""/2""
" "2""
" "7""
""
""2 ""
""2 ""
""4 ""
" 2 ""

"
/"
"
84
"
7"
"
!4
"
!4
"
4"
"
""
5
"
"
"
"
"
"
"
"
"
"
"
"
"
"
5
!
"
"
"
"
"
"
"
"
"
"
"
"
"
"
5
2
$
+ !
Roadnet Stop List Report Sample
Roadnet Stop List Report Sample
Used with: Roadnet
For more information about this report, refer to the Roadnet Stop List section.
FleetLoader Stop List Report Sample
FleetLoader Stop List Report Sample

For more information about this report, refer to the FleetLoader Stop List section.

D 0
$
,

!"
D !"$
$

8

$

$8

8:
0

.
#$% "
$'*
$++#)
&#'($
&#'($'

!"
)'$
'
,-#( . . .
01
)'$
.5.
$'*
2. 3!!14+
$+.+#).
!-#(
/
$)
)

+,

$

$'6,$

!-#(
/
$)
)
+,
$
$'6,$
!-#(
/
$)
)
+,

$

$'6,$

!-#(
/
$)
)
+,

$

$'6,$

!-#(
/
$)
)
+,

$

$'6,$

'
,-#( . 7 7
01
)'$
5
2 !!!1 8
$'*5
$+ +#)
'
,-#( 5 .
01
)'$
.
$'*
2..34"-!14+
$+5+#)5
'
,-#(55 ..
01
)'$
. .
2 34"-!14+6+
$'*
,-#(5
$+ +#)
'
01
)'$
. .
2 34"-!14+6+
Operations Guide
1121
Territory Location Report Sample
Territory Location Report Sample

For more information about this report, refer to the Territory Location section.
$2($,8,),9
2
/ /9

&& &!&

"#$%
"&'
()
*
+

(

& &!###
"

!/
$% 1

!/0

"
",
",.
",-
7#
#
#
7#
#
#
7#
#
#
7#
#
#
7#
#
#
7#
#
#
7#
#
#
7#
#
#
7#
#
#
7#
#
#
##
#
#
##
#
#
##
#
#
##
#
#
##
#
#
##
#
#
##
#
#
##
#
#
##
#
#
##
#
#
7##
#
#
2#34
! &!5(.#6-3
& &!##
"
1
27-0"-##
$5(.--
& &!##.
"
1 &
89.3 :

;:5(.#69
& &!##-
"
1&/
2--1 (:
//5(.#2-
& &!##8
"
1& &
71<$
&$ 55(.6
& &!##3
"
5
.3".##
&$ 55(.6
& &!##7
"
5.
.".##
&$ 55(.6
& &!##6
"
5-
.-"##
&$ 55(.6
& &!##9
"
58
.-"-##
&$ 55(.6
& &!##2
"
53
."-##
&$ 55(.6
& &!##
"
1/
7-##"
;:5(.#693
& &!#
"
1/
7-#3"
;:5(.#693
& &!#.
"
1/.
78#."
;:5(.#693
& &!#-
"
1/-
38##"
;:5(.#693
& &!#8
"
1/8
--##"
;:5(.#693
& &!#3
"
1(
(
#7-4
%"

%5(.6#.
& &!#7
"
1(
(
2#%; $

$5(.#8#
& &!#6
"
1=
9-3>:&:
;:5(.#69-
& &!#9
"
1=
(/ :
1 ;"&>15(.#966
& &!#2
"
1=
.891 :

":" 5(.#2#.
'.#
1122

)"
!
%$&##
#####
%$&##

%$&##
#####
!
'
.2%!
$%$&
))
$%$&
%).'
'&
!"##### $%$&
(? /'45.#?'8'8#5

!
1
*
*
*
*
*

#
#
#
#
#
#

#
#
#
#
#
#

:;<
**,0
#,0#
#,0#
1,/+
1,/+
+,#-
+,#-
'
#"#*
##"+
##"+
##"
##"
##"
##"
()

+"#
##"1#"00
##"#*"
##"#*"
##"#*"
*"
##"#*"
-"1
##"#*"
('
/"01
/"
$()
;
Territory Stop List Report Sample
Territory Stop List Report Sample
For more information about this report, refer to the Territory Stop List section.
Operations Guide
1123
Territory Summary Report Sample
Territory Summary Report Sample

For more information about this report, refer to the Territory Summary section.
3
"#3"1C"

'4)5',

)!
56
&

&'(

!
!
"$!%
!# !
!
! "3
!! !!

)
3

3
&'(

3%
!
!
%*$%
"
"
! !"
!! !!

)%
"&'

3%
!
!
3$
! !"
!! !!
% %!

)
3&+
!!
!
!
""$
"
! !! !!
!! !!

)*3
%
3"3
!
!

)3#$3
" !
!
"
!! !!
3! "
3)
3
%
,-9)))&,)-&,$
-,.,/,/$
1124

"
%%
& '
Operations Guide

"*
*
!

!
#

*

& + ,
,
#*
"

"*

*

#*

* )

%
%
!
"

4 25

!!

$
!!

)

)

*

*

"

""

(

0 ; %% %% %11;

!

"#

!"
""!

! #
! #
" #

2
3
"*
"*
#*
"

"
!
9
!"

% %
MobileCast Time Window Exception Report Sample
MobileCast Time Window Exception Report Sample
For more information about this report, refer to the Time Window Exception section.
1125
"
1126

*

& + ,
,

"*
*

!
"*

#*
"

*

#*

* )

%
%

!
"

%%
& '

'

!!

$
!!

)

)

*

*

"

""

(

!

"#

!"
""!

! #
! #
" #

"*
"*
#*
"

"
!
9
!"

)
Roadnet Time Window Exception Report Sample
Roadnet Time Window Exception Report Sample
Used with: Roadnet
For more information about this report, refer to the Time Window Exception section.
))0#<60%6*)
7%7#<7
%#0)1
;)%#'#<)#%%)
(#
*$?$%%;)
**67%<61')
**67)))
**;)01
*07(%%&#
*07%&)7#::
*91#%%$
*91#%%$
*91#%%$
*91#%%$
*9)1#%%&
*9)1#%%&
8
5
3
2

4
8

5
3
2

7)9>#0
5 4
))$10##:$
9#*%%6)6
83
4
=6#09#
58
)0)#)#)0%
<6)%:
888
6%)#
60%07%#)
88

7*
4 4

;)
3
??;)
*<0&

#<0&
7<0&
3
2
7#%%*(<)
25
2 8
)1)
4
#)011#%#
1:#;)%0
2
07;)
%&*#*91)0
4
53
7#%%%
8 5
5244
&0*&#)
')(%%&)
%!-
%!#
7.80191:;<01-=;>80?@11A0?>0B?.CD1

Operations Guide

)#
)#
)#
)#
)#
)#
)#
)#
)#
)#
)#
)#
)#
)#
)#
)#
)#
)#
)#
)#
)#
)#
)#
)#
)#
)#
)#
)#
)#
)#
)#
)#
)#
)#
)#
)#
)#
)#
)#
)#

%#(&
%#(&
%#(&
%#(&
%#(&
%#(&
%#(&
%#(&
%#(&
%#(&
%#(&
%#(&
%#(&
%#(&
%#(&
%#(&
%#(&
%#(&
%#(&
%#(&
%#(&
%#(&
%#(&
%#(&
%#(&
%#(&
%#(&
%#(&
%#(&
%#(&
%#(&
%#(&
%#(&
%#(&
%#(&
%#(&
%#(&
%#(&
%#(&
%#(&
)!
2

2

2

2

2

2

2

2

2

2

2

2

2

2

2

2

2
3
2
3
2
3
2
3
2
3
2
3
2
3
2
3
2
3
2
3
2
3
2
3
2
3
2
3
2
3
2
3

2

2

2
3
2
3
2

2
3
2

2

2
3
2
3
2

2
3
2

2

2
3
2

2

2
3
2
3
2

2
3
2
3
2

2
3
2

2

2
3
2

2

2
3
2
3
2

2
3
2
3
2

2
3
2

2

2
3
2

2

2
3
2
3
2

2

2
3
2
3
'
%!!-'!."

0"
2
3

4

4
1
'
)*%!#+"! ,
#%&#'#'(#
!"#$
4
3
4
3
4
3
4
3
4
3
4
3
4
3
4
3
4
3
4
3
4
3
4
3
4
3
4
3
4
3
4
3
4
3
4
3
4
3
4
3
4
3
4
3
4
3
4
3
4
3
4
3
4
3
4
3
4
3
4
3
4
3
4
3
4
3
4
3
4
3
4
3
4
3
4
3
4
3
4
3
'
'1)6
'1)6
'1)6
'1)6
'1)6
'1)6
'1)6
'1)6
'1)6
'1)6
'1)6
'1)6
'1)6
'1)6
'1)6
'1)6
'1)6
'1)6
'1)6
'1)6
'1)6
'1)6
'1)6
'1)6
'1)6
'1)6
'1)6
'1)6
'1)6
'1)6
'1)6
'1)6
'1)6
'1)6
'1)6
'1)6
'1)6
'1)6
'1)6
'1)6
!/"

3
3
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5

5

5

5

5

5

2
4

5
5

5

3

5

5

5

5

5

2

8
4
3
4

5

4
2
4

4
24

2

8
4
2

'
!-'!./!"

0"
8

4
5
44

44
5
84
5
4
5
5
3
'
-./011213411256
Time Window Override Report Sample
Time Window Override Report Sample
Used with: Roadnet
For more information about this report, refer to the Time Window Override section.
1127
"1
&&/ 0
..&
&&
&&
*$*/ % 0
$,
,(
$//+-%%
.+
,$&/ %+-%%
&*+
$&/&%%"%%
$&/ %%+-%%
*+
*$/ %%%&"%%

$$
#
!
-
@)

$)
$)
$
$)
$
'+)
*
$
'()

% %% %%
$/ %%&"%%
"
6@7@- 8--)(
)!
6

5 57(
$
$
$

$

$)
$)
$)
,)
$)
$
$
$

&
!
$)
$)
$)
)
&)

All Loads Report Sample
All Loads Report Sample
For more information about this report, refer to the All Loads section.
1128
Week Summary Report Sample

For more information about this report, refer to the Week Summary section.
!6!'47!6$
23!1! 45 4&$2&1515
!!
' 8
@55 # @

@!4
1$$$$$4 @@ % 5 <@
?6!19
1 *= 9

3
@0
@0&
@0
!6
93
@963
@
3
%
5!
@

6
$
$
75$56
$159
$$1$61
& 1$$
&81$
7&

,

&5
$
$
$$5&
$&1$$
$$151$$
& 1$$
&81&$
7

!

$
$
$
$$$$
$$1$$
$$1$$1$$
$$1$$
$$1$$
$
$
,

$
$
$
$$$$
$$1$$
$$1$$1$$
$$1$$
$$1$$
$
$
E

$
$
$
$$$$
$$1$$
$$1$$1$$
$$1$$
$$1$$
$
$
@,

$
$
$
$$$$
$$1$$
$$1$$1$$
$$1$$
$$1$$
$
$
@,!

$
$
$
$$$$
$$1$$
$$1$$1$$
$$1$$
$$1$$
$
$
$
$
7$$
$155
$$1&1
591$$
5616
4&&8
&
5!
&
6
$
$
75$56
$159
$$1$61
& 1$$
&81$
7&

,
&
$
$
$
$$$$
$$1$$
$$1$$1$$
$$1$$
$$1$$
$
$
!
&
$
$
$
$$$$
$$1$$
$$1$$1$$
$$1$$
$$1$$
$
$
,
&
$
$
$
$$$$
$$1$$
$$1$$1$$
$$1$$
$$1$$
$
$
E
&
$
$
$
$$$$
$$1$$
$$1$$1$$
$$1$$
$$1$$
$
$
@,
&
$
$
$
$$$$
$$1$$
$$1$$1$$
$$1$$
$$1$$
$
$
@,!
&
$
$
$
$$$$
$$1$$
$$1$$1$$
$$1$$
$$1$$
$
$
6
$
$
75$56
$159
$$1$61
& 1$$
&81$&
7&

9
$
$
&$$76
$5198
$$11&&
61$$
6 1&$
469
3
3&

@!6,:34;4 94*,4!*,3$

3,!3,<3,<633$
Operations Guide
1129
1130

Using Windows
Using Roadnet Transportation Suite Maps and Windows
Using Roadnet Transportation Suite Maps and Windows

Throughout the Roadnet Transportation Suite there are several types of windows that are
commonly used to display and maintain the data. This section of the manual explains in
detail how to use these different types of windows throughout the Roadnet Transportation
Suite. In some instances, especially with the maps, there may be additional functionality
in a particular portion of the suite; this additional functionality is described in that portion
of the Operations Guide, rather than here.
In this section you can find instructions on how to:
Set up list and maintenance windows the way you want
Search list and maintenance windows for specific entries
Set up the map the way you want
Add streets to the map
Add landmarks to the map
Edit the map network
Evaluate the map network
Identify stop types and their associated icons
Operations Guide
1131
Using List Windows
Using List Windows

List windows are used extensively in Roadnet Technologies products to present data.
The presentation of information in these windows can be altered, but the information itself
cannot be changed.
The Employees window is an example of a list window.
The number of entries in each list window is totaled at the bottom of a column (usually
the ID column). Totals for appropriate columns are shown at the bottom of that column.
To see the totals for selected items only, right-click on the total at the bottom of the
column and choose Selected Only from the menu that pops up.
In addition, an indented column header indicates that the window is sorted on that column.
If the window is sorted on multiple columns, each indented column header name is
followed by () containing the sort sequence.
Note: To unsort the columns, hold the [Ctrl] button and left-click on the column header
All list windows contain the same set of icons as shown below. For more information, see
Maintenance Windows or Arranging List and Maintenance Windows.
Icon
Description
Size the List Icon
Sizes the window to fit the number of rows in the list. This feature helps you to
conserve space onscreen or quickly view all entries that fit on the screen.
Font Icon
Opens a window to select the type style and size used to display information.
Column Manager Icon
Opens the Column Manager, which is used to sort the columns, hide and
retrieve hidden columns, and choose the sort criteria.
Printer Icon
Opens a window to print all, selected, or visible entries in the window.
1132

Using List Windows
Icon
Description
Setup and Execute a Search Icon
Opens the Search Manager, which is used to find specific items in the window.
Save Font and Attributes Icon
Saves the window set up as it appears.
Operations Guide
1133
Using Maintenance Windows

Maintenance windows are used to present, add, edit, and delete data used in Roadnet
Technologies products. Maintenance windows are presented similarly to list windows;
however, the main function of the maintenance windows is to manipulate data.
The Equipment Type window is an example of a maintenance window.
Maintenance windows can provide you with information about the data presented in the
window. The number of entries in the window is totaled at the bottom of a column
(usually the ID column). Totals for appropriate columns are shown at the bottom of that
column. To see the totals only for selected items, right-click on the total at the bottom of
the column and choose Selected Only from the menu that pops up.
In addition, an indented column header indicates the window is sorted on that column. If
the window is sorted on multiple columns, each indented column header name is followed
by a () containing the sort sequence.
Most of the maintenance icons are the same as the icons on a list window, but there are
two icons that are unique to maintenance windows. For more information, see List
Windows or Arranging List and Maintenance Windows.
Icon
Description
Add Icon
Opens a window to add an additional item.
Delete Icon
Deletes any selected item(s) in the maintenance window.
Searching the Database

A few windows, such as the Equipment window in the Maintenance module, will open
with no items shown in the window. These windows have a special search ability that
1134

allows you to display only those items you need to see, instead of seeing all possible items
in the list.
You can toggle to have the query portion of the Locations or Equipment window
visible by clicking the arrow at the bottom of the vertical scroll bar.
Each of the windows that have the query feature operate similarly. You can search by any
or all of the criteria listed. Click the box next to the search criteria you want to use and
enter the appropriate value in the field. You can use wildcards (*, ?, and !) in the search.
The more criteria you specify, the narrower your search will become.
After you have entered the criteria, click the Execute Query Using Criteria icon, or press
the [Enter] key to execute the search. If you want to run multiple searches and retain the
results of each search, check the Retain Results box.
Operations Guide
1135
Arranging List and Maintenance Windows

List and maintenance windows are used throughout Roadnet Technologies software to
present and manipulate data. You can change the appearance of the list and maintenance
windows so that it is easy to find the information you need. Described below are several
options for arranging the appearance and presentation of data in list or maintenance
windows.
To change the font in a window, click the Font icon or right-click on a column header
and select Change Font from the menu that pops up. The Font window opens. You can
change the size and style of the type in the maintenance or list window.
The Font window

allows you to change
the size and style of the
type in the list and
maintenance windows.
Note: If you click the Save Attributes icon the font changes will be reflected in all similar
windows.
To change the position of a column in the window, click on the column header and drag
the column to the desired position in the window.
OR
Right-click on the column header and select Move Column To from the menu that
appears. You can choose to move the column forward one position, back one position, to
the beginning of the window, to the last position, or to the position before or after the
freeze bar.
To change the width of a column(s), right-click in the column header and select Fit from
the menu that pops up. You can choose to size the column to fit only the data, or the data
and the title.
OR
Hold the mouse cursor over the right border of the column header; when a double-ended
arrow appears, click and drag the border to the proper position.
To change the width of all the columns simultaneously, right-click in a column header
and select Fit All from the menu that pops up. You can choose to size the columns to fit
the data only, or the data and the column header.
1136

To remove a column from the window, or hide the column, right-click on the column
header and select Hide from the menu that pops up. The column will no longer be visible
in the window.
Note: The information in that column is still stored in the database; you are simply
choosing not to view the information.
To restore a hidden column, right-click on the column header and select Restore, then
the column from the menu that pops up.
To choose the column the window is sorted on, click on the column header for that item.
The column header will be indented, indicating the window is sorted on that item.
To sort the window on multiple columns, click on the Column Manager icon. Drag the
column name to the Sort area of the window. Drag up and down within that list to
determine the sort order. See Changing Columns with the Column Manager for more
information.
OR
Hold down the [Ctrl] key on the keyboard and click on the column header. The columns
will be sorted in the order that the headers are clicked.
To find specific entries within in the list, use the Search Manager. See Using the Search
Manager for more information. Or, click in the column the window is sorted on and start
typing that entrys information; as you type the first entry that matches the typing will be
highlighted.
To select entries within the list, click on the entry.
To select a consecutive group of entries, hold down the [Shift] key and select the first
and last entry in the group, or click on the Select bar (the first column in the window) you
want to select and swipe down to the last entry.
To select multiple entries that are not consecutive, hold down the [Ctrl] key and click
on each entry.
To select all the entries in the window, right-click on a column header and choose Select
All from the menu that appears, or click on the column header for the Select bar (the first
column in the window).
To deselect an entry, click on another entry; the newly clicked entry will be selected.
To deselect all selected entries, right-click on a column header and select Deselect All
from the menu that appears.
To view a list of all selected items, press [F9] to open the Selected Items list on the list
window. This window, which will open automatically when you execute a search, lists all
items that are selected in the list window. From here, you can use the same options to work
with the item as you can in the list window. To have the list window move so that a
selected item is visible, click on the item in the Selected Items list.
To print the list:
Operations Guide
1137
Step 1: Click on the Printer icon, or right-click on a column header and select Print from
Step 2: Choose to send your output to the default printer or to a fixed or variable length
file. Selecting Fixed Length File will print the window contents to an ASCII file
with fixed column widths; selecting Variable Length File will print to an ASCII
file with variable column widths separated by semicolons.
Note: If you send your output to a fixed or variable length file and would like column
headers to be included, check Include Column Headers as First Row under Rows
to Output.
Step 3: Choose to print all, selected, or visible items.
Step 4: Check Include Column Headers as First Row, if you send your output to a fixed
or variable length file and would like column headers to be included. Column
headers make it easier to to identify the information in your file.
Step 5: In the Heading field, enter the name of the printout if it is different from the
window title, and click on the Print button.
Note: If you are printing to a file, the Heading field will turn to a Filename field in which
you can browse to select your file.
The List Print Settings window allows
you to print all, selected, or visible rows
in a list or maintenance window. You
can print this information to a printer or
to an ASCII file. You can also type in a
header for the printout.
Hint: The printing and Search Manager features can be used together to create reports
of the data in the windows.
To export the contents of the window to an Excel spreadsheet or ODBC datasource:
1138

Step 1: Right-click on a column header and choose Export from the menu that pops up.
The Export Data window opens.
You can export your data to

another database or Excel using
the Export Data window.
Step 2: To export to a Microsoft Excel spreadsheet, click Microsoft Excel. Enter the
path and name of where the spreadsheet exists, or you want it to be created, or
click the [...] button and browse to the location. Enter the name of the sheet you
want the information stored on. To have Excel automatically open when the
export is complete, check Launch Excel After Export.
To export to an ODBC data source, click ODBC Data Source and enter the table
name.
Step 3: Click the [Export] button.
If you chose Microsoft Excel, the data is exported to the designated spreadsheet.
If you checked Launch Excel After Export, Excel opens to the spreadsheet once
the export is complete.
If you chose ODBC Data Source, the Microsoft Select Data Source window
opens. Specify the ODBC data source you want the information exported to and
To save the window as it currently appears, click on the Save Font and Attributes icon.
Changing Columns with the Column Manager
The list and maintenance windows used throughout Roadnet Technologies software can
be customized to look the way you want. This can be done directly on the window, or by
using the Column Manager.
Operations Guide
1139
Although you can edit the appearance and order of the columns directly in a list or
maintenance window, you can also use the Column Manager.
The Column Manager window

allows you to change the
order of columns, hide
columns, and determine how
information in a window will
be sorted.
To open the Column Manager, click on the Column Manager icon.

OR
Right-click on a column header and select Edit from the menu that pops up.
To change the order of the columns, click and hold on the column name you want to
move in the Visible Columns box, then drag and drop the column to the desired location
in the list.
To hide a column, click and hold on the column you want to hide, then drag and drop it
in the Hidden Columns window.
To sort on a column, click and hold on the column you want to sort on, then drag and
drop it in the Sort Columns window. You can sort on more than one column; the order in
which the columns appear in the Sort Columns window is the sort order. Click on the Z
A box if you want to sort that column in descending order.
1140

Using the Search Manager

The list and maintenance windows used throughout Roadnet Technologies software
include a very powerful search feature that allows you to search for specific entries in the
window. You can use this feature to find entries that need to be edited, or to find entries
that can then be printed to create a report.
You can search for all entries that meet a single condition, such as all driver named Smith,
or all entries meeting multiple conditions.
Searching for entries meeting a single condition
When using the Search Manager to look for entries in list or maintenance windows that
meet certain conditions, you can search for entries that meet only one condition or entries
that meet multiple conditions.
The list and maintenance windows include a very powerful search feature that allows you
to search for specific entries in the window. You can use this feature to find entries that
need to be edited, or to find entries that can then be printed to create a report.
You can search for all entries that meet a single condition, such as all driver named Smith,
or all entries meeting multiple conditions.
Step 1: Click on the Setup and Execute a Search icon, or right-click on a column header
and select Search from the menu that pops up. The Search Manager window
opens.
Note: If you have saved previous searches, a menu will display when you click on the
Search Manager icon. You can select New to begin a new search, or you can select
any previously saved search.
The Search Manager window allows you to enter conditions to find

specific items in a list or maintenance window.
Step 2: Double-click in the column to search on. The Search Condition window opens.
Step 3: Enter the desired condition and click on the [OK] button. See Entering Search
Conditions for more information on completing these windows.
Step 4: Click on the Execute Search icon. The items that meet the selected search
condition are highlighted in the list window, and the list of selected items opens
in the list window. The total number of items that match the search is indicated in
the bottom right corner of the Search Manager window.
Operations Guide
1141
Searching for entries meeting multiple conditions
You can use the Search Manager to look for entries in a list or maintenance window that
meet a single condition or multiple conditions. When using the Search Manager to look
for multiple entries, you can require that the entries meet all the specified conditions
(AND search) or only one of the specified conditions (OR search).
Step 1: Click on the Setup and Execute a Search icon, or right-click on a column header
and choose Search from the menu that pops up. The Search Manager window
opens.
Step 2: Double-click on the column to search on. The Search Condition window opens.
Step 3: Enter the desired condition and click on the [OK] button. See Entering Search
Conditions for more information.
Step 4: To create a search where the entries must meet all the conditions (an AND
search), double-click the next column on the same line and enter the condition.
To create a search where the entries must meet one of the conditions (an OR
search), click on the Add Filter icon. A new line appears in the Search Manager
window; double click in the column to be queried on and enter the search
condition.
To remove an existing filter from a set of search conditions, right-click on the
line and select Remove Filter from the menu that pops up.
Step 5: Repeat Step 4 as needed to create all the needed conditions. When all the search
conditions are established, click on the Execute Search icon. The items that meet
the selected search condition are highlighted in the list window, and the list of
selected items opens in the list window. The total number of items that match the
search is indicated in the bottom right corner of the Search Manager window.
To keep the results from the previous search, click on Clear Results; it will
change to say Append Results. Click on it again to have previous results cleared
when performing a search.
To save a search to run later, click on the Save Font and Attributes icon and
enter the search name. When you want to rerun the search, click on the Search
Manager icon and select the search from the menu.
To retrieve a saved search so you can edit it, on the Search Manager window,
click on the Open Search Criteria icon and select the desired search (filename.ser)
from the window that opens.
To delete a saved search, click the Open Search Criteria icon on the Search
Manager window; the Open Search Criteria window opens. Select the search you
want to delete and click the [Delete] button; click [Yes] to confirm you want to
delete the search. To delete all the saved searches, click the [Delete All] button.
1142

Entering Search Conditions
need to be edited, or to find entries that can then be printed to create a report.You can
search for all entries that meet a single condition, such as all driver named Smith, or all
entries meeting multiple conditions.
There are four types of search conditions that can be entered in Roadnet Technologies
products. Each type of condition window has slightly different information presented for
defining the condition. The information needed for each type of condition is outlined
below.
Numeric Search ConditionsEnter the desired number and select the proper
operation. For instance, to search for all entries equal to 24, enter 24 in the entry field
and select the = operation. To search for a consecutive range of numbers, enter the
high and low end of the range in the entry fields and select Inclusive or Exclusive. To
search for a group of entries that are not consecutive, select In as the operation and
enter the numbers in the field. Click the [+] to add the number to the box. To search
for all entries that dont match the entered criteria, click on the Not box.
This search would find

all drivers who are paid
at least $1.25 per minute.
Date Time Search ConditionsEnter the desired date and time to search for. To
select a date, enter the date in the field, or click on the down arrow and select the date
from the calendar. Enter the desired time in the field and select the appropriate
operation (ex. to search for anything that occurred after 12 noon, enter 12:00 in the
time field and click the < operation). If you are searching for a time, select the time
zone the times should reflect; for instance if you are searching for all routes with a
start time of 6:00 AM Eastern time, choose Eastern Time as the time zone. To search
a range of dates/times, enter the starting and ending information and select Inclusive
Operations Guide
1143
or Exclusive. To search for entries that do not match the criteria, click on the Not
box.
This search would find all

routes that occurred on
October 16, 2009.
Running Time Search ConditionsEnter the desired total time to search for and
select the appropriate operation (ex. to choose all times greater than 8 hours, enter
8:00 in the entry field and choose < as the operation). Enter the desired time in the
field. To select a range of times, enter the starting and ending information and select
Inclusive or Exclusive. To search for entries that do not match the criteria, click on
the Not box.
This search window allows you to

search for total time.
String Search ConditionsEnter the condition in the Criteria field. To search for
entries that match the criteria, select Compare; to search for blank entries click on
Empty. To search for those entries that match the case of the condition click on Case
Sensitive; to search for entries that do not match the condition click on the Not box.
This condition would
find all drivers named
Smith, bit only if the
capitalization matches
that entered here.
1144

Search Manager Icons
need to be edited, or to find entries that can then be printed to create a report. There are
several icons across the top of the Search Manager window. The purpose of each icon is
outlined below.
Icon
Description
Open Search Criteria Icon
Opens a window to select a previously saved set of search conditions.
Save the Current Search Criteria Icon
Saves the existing set of search conditions to use later on other data.
Add a New Filter Icon
Adds a new line to the Search Manager window to allow a new filter.
Execute the Search Icon
Searches the window using the selected conditions and highlights the entries
meeting those conditions.
Size the List Icon
Sizes the window to fit the number of rows in the list. This feature helps
conserve space on the screen or quickly view all entries that fit on the screen.
Operations Guide
1145
Maps and RouteNet

Maps are a powerful feature of Roadnet Technologies products. The position of locations
can be viewed, the quickest distance between points determined, directions can be viewed
and printed, and the map itself edited. The map actions are started either by selecting the
icon from the menu bar across the top, or by right-clicking on the map and selecting the
option from the popup menu that appears.
The maps pop-up menu allows you to quickly and easily customize the maps
appearance. You can turn options on or off, or access any of the RouteNet features.
1146

Setting Up the Map
Setting Up the Map

The maps in Roadnet Technologies software can be customized to look the way you want.
You can change the color of the background, select the identifiers for the cities,
landmarks, and zip codes, as well as the amount of road detail that will be visible on the
map. You can also determine road thickness for any level of road.
To select the items that will be visible on the map, click on the Map Options icon and
select Properties from the menu that appears. The Map Properties notebook opens.
The Map Properties notebook contains several pages that are used to define how
locations, roads, and landmarks will be displayed on the map, as well as other overall map
appearance options. The pages vary depending on which product you are using, and even
where in the product you are, but there are several pages that are common to all maps. See
the Map Properties Notebook for a brief description of each pages function.
You can also select the attributes visibility using the pop-up menu. Right-click anywhere
on the map and select View from the menu that pops up; a sub-menu appears. A check
mark next to an item indicates that it will be displayed on the map; simply select the menu
item to toggle from visible to not visible.
Checkmarks next to an
item indicate that it will
appear on the map. Click
the item to toggle from on
to off.
To fade the roads and other background features of the map so that individual
locations are easier to see, select Fade from the Options menu. Use the slider bar to adjust
the colors as desired; click on the [Apply] button to test the new setting and the [Set]
button to accept the setting for this map session only. To restore the original colors, or
readjust them, move the slider bar as necessary.
Fade streets and the background
of the map to make your routes
and locations easier to see.
Once you have the settings the way you want, you can save them by selecting Save Option
Set from the Options menu. Previously saved settings can be restored by selecting Restore
Option Set from the menu.
Operations Guide
1147
Map Properties Notebook

The Map Properties notebook, opened by clicking on the Map Options icon and selecting
Properties from the menu, allows you to customize the appearance of the map. You can
choose the color and thickness of the streets, the colors of landmarks and labels, as well
as which items will appear on the map. To accept your choices for the current instance
only, click on the [Apply] button; to accept your choices for future instances with the map,
click on the [Save] button. Changes you make on one map will appear on all the maps.
The Map Properties notebook may contain additional pages that are specific to the
software or individual module within the software; these pages are discussed in the
appropriate section. For more information on the pages in the Map Properties notebook,
see Map Attributes, Road Colors, Landmark Information, City Information, Zip Code
Information, Rush Hour Information, Time of Day Restriction, or Landmark Colors.
Map Properties Notebook - Map Attributes
To specify the attributes that appear on the map, as well as the background color and road
detail that is visible, click on the Map tab.
To change the font for the street names, click on the down arrow and select the font,
size, and style.
To select the maps background color or the street name colors, click on the down
arrow next to the appropriate color block and select the color from the palette that appears.
To specify which attributes appear on the map, verify that a check is present in the
appropriate box.
1148

To set the detail level, determining the road classes that appear, slide the bar in the Detail
Level area.
The Map page of the Map Properties

notebook allows you to change the
maps appearance. You can establish
font type, color schemes, detail level,
etc.
Map Properties Notebook - Road Colors

To specify how the roads are displayed on the map, click on the Levels tab of the Map
Properties notebook. The roads displayed on the map are separated into five categories:
limited access interstates, primary roads, secondary roads, local roads, and ramps. For
each classification you can specify the color, or even the width, of the roads, making them
easy to distinguish on the map.
To choose a road color, click on the arrow next to the color block and select the desired
color from the palette that appears.
Operations Guide
1149
To change the road or border width, enter the desired thickness, in pixels, in the
appropriate field.
The Levels page of the Map Properties

notebook allows you to identify
various road types by using different
colors, widths, and borders.
Map Properties Notebook - Landmark Information

To define whether landmarks will appear on the map, and whether they will be labeled,
click on the Landmarks tab. The colors of the landmarks can be specified on the Misc.
page of the notebook.
To change the label font, click on the down arrow and select the desired font, size, and
style.
1150

To have landmarks displayed on the map, place a check in the box in the Attributes
section. The Display box must be checked for landmarks to appear on the map.
The Landmarks page of the Map

Properties notebook allows you to
indicate whether you want to use
landmarks, whether you want to label
the landmarks, and how you want the
labels to look.
Map Properties Notebook - City Information

To specify whether city names will appear on the map, and how the names will look, click
on the City tab. The cities are categorized by population; cities in each category can have
different label fonts and sizes, making them easy to differentiate on the map.
To change the font for the city names, click on the down arrow and select the font, size,
and characteristics.
To change the color of the city names, click on the down arrow next to the color block
and select the desired color from the palette that appears.
Operations Guide
1151
To have city names appear on the map, verify that the Display box is checked.
Use the City page of the Map

Properties notebook to specify
whether city names will appear
on the map and, if so, how they
will look.
Map Properties Notebook - Zip Code Information

To specify the appearance of zip codes on the map, click on the Zip Code tab of the
notebook.
To change the font for the zip code, click on the down arrow and select the font, size,
and characteristics.
To change the color of the zip codes, click on the down arrow next to the color block
and select the desired color from the palette that appears.
1152

To have the zip codes appear on the map, check the Display box.
Use the Zip Code page of the Map

Properties notebook to indicate
whether you want zip codes to appear
on the map and, if so, how they will
look.
Map Properties Notebook - Rush Hour Information

The Rush Hour page of the Map Properties notebook lets you define how the rush hour
model will appear on the map. You can choose which model will be displayed, the colors
used to display the model, and whether or not the model is displayed all the time.
To choose the rush hour model that will be displayed, click the Current Rush Hour
Model arrow; the Rush Hour Models window opens. Double-click on the model you want
to work with, or click on the model and then on the Process icon. To add a rush hour
model, click on the Add icon; the Add Rush Hour Model window opens.
To choose the color the borders of the rush hour areas will be displayed, click on the
Rush Hour Areas arrow; a color palette opens. Click on the color you want to use. To
change the width of the line, enter the width in the Width field. The width is measured in
pixels.
To choose the color the rush hour paths will be displayed, click on the Rush Hour
Paths arrow; a color palette opens. Click on the color you want to use. To change the width
of the line, enter the width in the Width field. The width is measured in pixels.
Operations Guide
1153
To always display the rush hour areas and paths on the map, check Display Rush
Hour Areas and Paths. If this option is not selected, the rush hour areas and paths will only
be displayed when you are in Rush Hour Mode.
The Rush Hour page is where you

choose which rush hour model to
display, and how you want it to
appear on the map.
Map Properties Notebook - Time of Day Restriction Information

The Time of Day Restriction page of the Map Properties notebook lets you define how
the time of day restriction model will appear on the map. You can choose which model
will be displayed, the colors used to display the model, and whether or not the model is
displayed all the time.
To choose the time of day restriction model that will be displayed, click the Current
Time of Day Restriction Model arrow; the Time of Day Restriction Models window
opens. Double-click on the model you want to work with, or click on the model and then
on the Process icon. To add a time of day restriction model, click on the Add icon; the
Add Time of Day Restriction Model window opens.
To choose the color the borders of the time of day restriction areas will be displayed,
click on the Time of Day Restriction Areas arrow; a color palette opens. Click on the color
you want to use. to change the width of the line, enter the width in the Width field. The
width is measured in pixels.
To choose the color the time of day restriction paths will be displayed, click on the
Time of Day Restriction Paths arrow; a color palette opens. To change the width of the
line, enter the width in the Width field. The width is measured in pixels.
To always display the time of day restriction areas and paths on the map, check
Display Time of Day Restriction Areas and Paths. If this option is not selected, the time
1154

of day restriction areas and paths will only be displayed when you are in Time of Day
Restriction mode.
The Time of Day Restriction page is where

you choose time of day restriction model to
display, and how you want it to appear on the
map.
Map Properties Notebook - Landmark Colors

To specify the colors of the various types of landmarks, click on the Misc. tab. You can
use this feature to easily distinguish the type of landmark being shown on the map. The
color and width of the streets selected when working with RouteNet can also be specified.
To change the color of a landmark, click on the down arrow next to the color block and
select the desired color from the palette that appears.
Operations Guide
1155
To change the width of selected streets, click in the Width box and enter the desired
thickness.
Use this page to easily

distinguish the type of
landmark being shown on
the map.
1156

Map Icons
Map Icons
The maps used in Roadnet Technologies software all contain a toolbar across the top.
The icons located on the toolbar can be used for many things, including moving around
the map, zooming the map, or establishing how the map should look. In addition to these
common icons, which appear on all the maps, some maps may contain additional icons
specific to that maps use. To start an action, click on the icon; to end an action press the
[Esc] key or right-click on the map and select Cancel Mode from the menu that pops up.
Icon
Description
Zoom In Icon
Zooms the map in on an area. Click on the icon then draw a box around the area
to be zoomed in on. The area you zoom in on will be centered on the map. You
can also click on the icon and then on the map; the map will zoom in 10% on
the area clicked.
Note: The place on the map you have clicked will remain in the same relative
position on your screen as you zoom in by clicking your mouse button or by
scrolling your mouse wheel towards the screen.
Zoom Out Icon
Zooms the map out from an area. Click on the icon then draw a box around the
area to be zoomed out. The area you zoom out on will be centered on the map.
You can click on the icon and then on the map; the map will zoom out 10%
from the area clicked.
Note: The place on the map you have clicked will remain in the same relative
position on your screen as you zoom out by clicking your mouse button or by
scrolling your mouse wheel away from the screen.
Center Icon
Centers the map on the selected area. Click on the icon then on the location to
be the new center of the map.
Fit Icon
Zooms the map so that all pertinent items are visible.
Map Options Icon
Opens a menu that offers alternatives for setting up the map and customizing
the appearance to fit your needs. The menu choices are described below.
Propertiesopens a notebook that allows you to define the appearance of the
map.
Save Option Setlets you save the currently selected options.
Restore Option Setlets you restore previously saved map options.
Fadeopens a slider bar that fades the maps background and street colors,
making it easier to see routes and locations.
Save Zoomlets you save the current zoom level and location.
Restore Zoomlets you restore a previously saved zoom level and location.
Operations Guide
1157
Map Icons
Icon
Description
Ruler Icon
Measures the selected distance. Click on the icon; then use the mouse to draw
along the area to be measured. Click to end each segment; right-click to end the
measuring. Segment and total distances appear in the Measure Mode window.
Lasso Icon
Selects a group of locations. Click on the icon; then use the mouse to draw a
lasso around the locations you would like to select.
Landmark Icon
Opens a menu that allows landmarks to be added, edited, deleted, listed, or
shown.
Query by Address Icon
Opens the Query by Address window, which can be used to locate a specific
address.
Edit Rush Hour Model Icon
Places the map in rush hour mode, where you can add and edit rush hour areas
and paths.
Edit Time of Day Restriction Model Icon
Places the map in time of day restriction mode, where you can add and edit time
of day restriction areas and paths.
Printer Icon
Prints the visible portion of the map.
Decrease Displayed Detail Icon
Decreases the detail level shown on the map. This setting will last until the map
is zoomed or centered again.
Increase Displayed Detail Icon
Increases the detail level shown on the map. This setting will last until the map
is zoomed or centered again.
1158

Map Navigation Options

The maps used in Roadnet Technologies software can cover a large amount of area, more
than can be seen on the screen at one time. So, when using the map to geocode a location
or evaluate your routes, you may need to move around the map to find specific places.
The navigation aids that let you traverse the map can be started either by clicking the
appropriate icon or by right-clicking on the map and choosing the desired mode from the
popup menu that appears. To end each mode, press the [Esc] key, or select Cancel Mode
from the popup menu.
To see an area more closely, click on the Zoom In icon, or select Zoom In Mode from
the popup menu. Draw a box around the desired area on the map. The smaller the box
drawn, the closer the zoom will be. The area you zoom in on will be centered on the map.
A single click on the map, pressing the [Page Down] key, or scrolling the mouse wheel
up towards the screen, causes a +10% zoom on the area clicked.
Hint: The place on the map you have clicked will remain in the same relative position on
your screen as you zoom in by clicking your mouse button or by scrolling your
mouse wheel towards the screen.
To view a larger area, click on the Zoom Out icon or select Zoom Out Mode from the
popup menu. Draw a box around the desired area on the map. The smaller the box drawn,
the farther out the zoom will be. The area you zoom out on will be centered on the map.
A single click on the map, pressing the [Page Up] key, or scrolling the mouse wheel down
away from the screen, causes a -10% zoom on the area clicked.
Hint: The place on the map you have clicked will remain in the same relative position on
your screen as you zoom out by clicking your mouse button or by scrolling your
mouse wheel away from the screen.
To move to a different location on the map, while retaining the same zoom level, click
on the Center icon or select Center Mode from the popup menu. Click on the position to
be the new center of the map. The map will move to the new area, retaining the same zoom
level.
To move incrementally around on the screen, use the arrow keys on the keyboard.
Pressing an arrow key will move the map half of the display area in that direction; for
instance pressing the [] moves the map up half the display area.
The zoom and center icons can be used together to move to different areas of the map,
such as when trying to determine the shortest path between locations.
Notes: If the Increase Map Detail or Decrease Map Detail icons were used to increase or
decrease the detail level, the detail level will revert to the level set in the Properties
notebook when the map is moved or zoomed.
To undo any of the zoom or center moves, such as if you zoom in too far, click the
Restore Last Zoom icon in the lower right corner of the map.
Zoom levels and locations can be saved and restored using the Options menu.
To save the zoom levels and locations, select Save Zoom from the Options menu.
Operations Guide
1159
Options icon Save Zoom
To restore previously saved zoom levels and locations, select Restore Zoom from the
Options menu.
Options icon Restore Zoom
1160

Map Hotkey Shortcuts
Map Hotkey Shortcuts

There are many actions you can perform on the maps in USP Logistics Technologies
software, such as zooming the map, moving around to display a different area, and saving
the map. The actions can all be performed using either the icons and menus, or the hot
keys listed below.
Once you have a map open, there are several hotkey shortcuts you can use to perform
various tasks, including many of those represented by the map icons. The following list
explains each shortcut and its respective function.
Hotkey
Combination
Action
[Shift] + [S]
Saves current display area to be used by default. You must exit the
current module for this to take effect.
[Ctrl]+ [Shift]
+ [M]
Generates an email with the current map image that can be sent to a
map vendor.
[Shift] + [I]
Saves the current map image to disk as .png or .jpg file.
[Backspace]
Undoes the change made to the display area.
[ ]
Move up half of the display area.
[]
Move down half of the display area.
[]
Move left half of the display area.
Move right half of the display area.
[Page Up]
Zoom out
[Page Down]
Zoom in
[-]
Zoom out
[+]
Zoom in
Mouse Wheel
Towards
Screen
Zoom In
Mouse Wheel
Away from
Screen
Zoom Out
[Insert]
More detail
[Delete]
Less detail
[Shift]+[U]
Removes the most recent segment when using Multi-Shortest Path

Mode.
Operations Guide
1161
Finding a Location on the Map

One of the most useful features of Roadnet Technologies maps is that you can easily
locate specific cities, zip/postal codes, addresses, or customer locations. This ability is
especially helpful when you are geocoding locations or just trying to find an already
geocoded location.
As you move the mouse across the map, the latitude and longitude of the mouses position
is indicated on the bottom right corner of the map. The bottom left corner contains
information about the street segment the mouse is pointing to, including the address
range, street name, city, state, zip code, and country. This information can be very helpful
when determining the location of a landmark or location, or just to help you get your
bearings on the map.
The map also gives you the ability to zoom to a specific street segment, city, or zip code
area. These options are started by right-clicking on the map and selecting the desired
action.
Zoom to Zip/City
especially helpful when you are geocoding locations or just trying to locate an already
geocoded location.
The Zoom to Zip or City menu option, opened by right-clicking on the map and selecting
it from the popup menu, allows you to quickly zoom the map to a specific zip code or city.
Enter the zip code or city and state or province abbreviation, and select the country, then
click the [OK] button. The map zooms to the selected area. If you know the name of the
city you are looking for, you can use this feature to quickly move the map to that area.
Note: This dialog will not accept wildcard characters.
Query by Address
especially helpful when you are geocoding locations or just trying to locate an already
geocoded location.
The Street Query feature allows you to search for a specific address and then move to it
on the map. This feature can be used when geocoding a location, or editing the network.
Note: Once you have opened the Query by Address window, you can click anywhere on
the map to display the address information at that point.
Step 1: Click on the Query by Address icon. The Query by Address window opens.
Note: The Query by Address window can also be opened by right-clicking on the map
and selecting Query by Address from the pop-up menu.
1162

Step 2: Enter the portion(s) of the address to query. The options are: street number,
street prefix, street name, street type, street suffix, city, state, zip code, and
country. At a minimum, the street name and either the city, state, or zip code, plus
the country, must be entered.
Notes: The fields in this dialog will accept wildcard characters. Use a [?] for a single
character wildcard, a [*] for a multiple character wildcard, and a [!] to exclude
results containing the characters that you enter.
When entering the city name, be sure to enter the complete name, or use a wildcard
character to expand the query.
To limit the search to only those roads visible on the map, verify that a check is
present in the Limit to map view check box.
To maintain previously selected segments, verify that a check is present in the
Retain results check box.
To set the maximum number of possible matches that will be listed when you do
a search, select a number in the Max results fieldeither 100, 200, 400, or 800.
Step 3: Click the [Query] button to begin the search.
Note: If a query initiated takes too long, click the [Cancel] button.
Step 4: Possible matches for your query are listed in the window. Clicking on a match
causes it to be highlighted on the map. Right-clicking on a segment pops up a
menu with several choices, which are discussed below.
Option
Description
Fit
Zooms the map to the selected item.
Center
Centers the map on the selected item while

maintaining the current zoom level.
Mark Address
Allows you to place a landmark at the selected

location on the map.
Edit Attributes
Opens the Edit Street Attributes window so that you

can edit the speed, distance, time, and other
attributes of the street segment.
Remove From
List
Removes the suggested match from the list.
Fit All
Zooms the map so that all segments are visible.
Edit All
Attributes
Opens the Edit Street Attributes window so that you

can edit all the segments simultaneously.
Operations Guide
1163
Working with Landmarks
Working with Landmarks

The maps used in Roadnet Technologies software serve several purposes, including
geocoding your locations. Often, it makes it easier to find the proper place for a location
if you know a local landmark that it is near, such as a mall. You can place markers on the
map to indicate local landmarks, making it easier to find an area, geocode nearby
locations, or determine the correct street attributes.
To add a landmark, click on the Landmark icon and select Add Landmarks from the
menu that appears. Enter the name of the landmark and choose the graphic that will mark
the location. To make the landmark permanent so that it appears on all instances of the
map, not just the current viewing, verify that a check is present in the Permanent check
box. Click on the [Add] button to add the landmark.
To edit an existing landmark, click the Landmark icon and select List Landmarks from
the menu that appears, or right-click on the landmark and select Edit from the menu that
pops up. Select the landmark in the resulting list and click on the [Edit] button. The name
and icon associated with the landmark can be changed.
To delete a landmark, click on the Landmark icon and select List Landmarks from the
menu that appears, or right-click on the landmark and select Delete from the menu that
pops up. Select the landmark in the resulting list and click the [Delete] button.
To locate an existing landmark, click on the Landmark icon and select List Landmarks
from the menu that appears. Select the landmark from the resulting list and click on the
[Locate] button; the map zooms to that landmark.
To toggle landmarks on or off, right-click on the map. Scroll to Map Display and select
User Defined Landmarks from the pop-up menu.
1164

Editing the Network
Editing the Network

One of the key functions of the maps is to provide Roadnet Technologies software with
the ability to create routes or sequence existing routes using the information contained in
the street network. If you purchased RouteNet, a street network was shipped with your
system; you may need to update or modify that network periodically to account for
changing road conditions. Any changes you make to the street network can be used
immediately for geocoding and routing.
The street network is composed of street segments that are connected by intersections or
other points. New street segments can be added or even deleted, and the speed and
distance of existing segments can be edited to reflect changing road conditions. All
network options are started by right-clicking on the map, scrolling to Network, and
selecting the desired option.
Notes: Many of the features of the map, such as locating an area or a specific address,
can be used to help with editing the network.
If you were not granted permission to edit maps in the Administration module,
you will not be able to perform any of these functions.
Warning: Any changes made to the network are effective immediately and cannot be
undone. Before making any changes to the network, such as adding street
segments or changing the attributes of an existing segment, verify that the
information is accurate.
Once you edit the network, you can test the accuracy of your edits by checking the path
the network takes when traveling between two points.
Adding Street Segments
The street network displayed on the map is composed of many street segments that are
connected by intersections or other points. If you purchased RouteNet, you can add street
segments as needed to account for new road construction in your area.
Step 1: Right-click on the map. Scroll to Network and select Add Streets Mode from the
menu that pops up.
Network Add Street Mode
Step 2: Click on the map where you want the street segment to start.
Step 3: Click again where the segment turns, curves, or ends. Continue clicking to draw
the entire street segment.
Note: To prevent the segment from snapping to a nearby road when drawn, hold down
the [Alt] key while drawing that portion of the segment. If you draw a segment
Operations Guide
1165
Editing the Network
incorrectly, click the [Undo] button on the Add Streets Mode window to remove
the most recent portion of the segment.
Step 4: When the complete segment is drawn, click on the [Add] button. The Edit
Street Attributes window opens.
Step 5: Enter the address range, streets local name, city, state, zip code, and country for
the segment, the alternate route names and shields, as well as the speed limit and
any restrictions on the segment. Click the [Add] button to add the segment. See
Edit Street Attributes window for more information.
Note: When entering the address range, a black dot appears on the map to indicate which
part of the segment you are defining (left high, left low, etc.).
Editing Street Segments
The street network is composed of street segments and intersections that connect the
segments. Each segment has specific attributes associated with it, including the name,
address range, speed, and time needed to cover the distance, all of which can be modified.
Step 1: Right-click on the map and choose Query by Address from the popup menu. The
Query by Address window opens.
Step 2: If you know where the street is on the map, click on a street segment; the
segment is highlighted, indicating that it is selected and is listed in the Query by
Address window. Continue selecting street segments as desired.
If you know the address for the street segment, enter it in the Query by Address
window; street segments with matching addresses will be listed at the top of the
window.
Step 3: When all desired segments have been selected, right-click on the first segment
and select Edit Attributes from the menu that appears. The Edit Street Attributes
window opens.
Note: The Edit Street Attributes window can also be opened by right-clicking on a
selected street segment when a path has been created on the map.
Step 4: Edit the street segment(s) as desired.
To change the address, speed limit, or height or weight limit for the segment,
enter the new information in the Edit Street Attributes window.
To disable a street segment, make it loadable or one way, verify that a check is
present in the appropriate check box.
To change the shape of a segment, such as to add a curve to the road, click on
the [Change Shape] button and use the map in the Edit Street Attributes window
to redraw the segment.
To delete an existing street segment, verify that the desired segment is specified
in the Edit Street Attributes window, and click on the [Delete] button. Click [Yes]
to confirm you want to delete the segment.
1166

Editing the Network
See Edit Street Attributes window for more information.

Step 5: After all desired changes have been made, click on the [Update] button.
Edit Street Attributes Notebook
The Edit Street Attributes window allows you to edit the address information, speed, and
other attributes associated with the street segment. This information is used to calculate
travel times and distances, so make it as accurate as possible. The bottom portion of the
window contains a map showing the segment. This map can be used to change the shape
of the segment and also see what street segment you are working on.There are several
icons that can be used to traverse the map in the Edit Street Attributes window. The Zoom
In, Zoom Out, and Fit icons can be used to change the zoom level of the map, while the
Center icon can be used to move across the map without changing the zoom level. The
window can also be resized as necessary.
Step 1: Right-click on a selected street segment in the Query by Address window and
select Edit Attributes from the menu that pops up. The Edit Street Attributes
notebook opens.
The Edit Street Attributes page allows you to edit address, speed, and other
attributes of a street segment on the map.
Step 2: Enter the final street number for that end of the segment in the Address Range 1
and Address Range 2 fields.
Operations Guide
1167
Editing the Network
Note: You can determine which portion of the segment the address range is for by seeing
where the black dot displays on the map at the bottom of the window.
Step 3: If a street segment has a prefix, enter it in the Prefix field. The prefix is the
directional portion of the address between the street number and name, for
example 12344 N. Charles St.
Step 4: Enter the name of the street the segment is part of in the Name field.
Step 5: Enter the type of road the street segment is in the Type field. For example, RD
is for road.
Step 6: Click on the Road Class arrow to open a list of available road classes. Select the
appropriate road class for the street segment. The available road classes are:
limited access interstate, primary road, secondary road, local road, and ramp.
Note: The distance and time are automatically calculated based on other information
entered on the window. The Distance field displays the length of the street
segment, in miles or kilometers. You cannot edit this field; it is calculated from
the shape and length of the street segment. The Time field displays the amount of
time needed to traverse the street segment. The time is calculated using the
distance and the speed, you cannot edit this field.
Step 7: If a street segment has a suffix, enter in the Suffix field. The suffix is the
directional portion of the address between the street type and city. For example,
1234 M St. NW Washington.
Step 8: Enter the speed limit on the street segment in the Speed field.
Step 9: If you are using alternate route name, complete the following information in the
Route 1, Route2, and/or Route 3 sections.
Route Nameenter the streets federal, state, or local street name/number. The
highest level of government, such as federal, would be entered as Route 1, state as
Route 2, and local as Route 3. If a segment is part of an interstate, enter the
interstate number; for example I-95.
Shieldclick on the arrow to select the proper shield to display with the road
name. This option is only available if a number is entered as part of the Route
Name.
Directionclick on the arrow to open a list of directions, and choose the direction
that the street signs indicate the road is traveling on this segment. In other words,
if the street sign says I-95 N, choose North here. These directions will then be used
when driver directions are printed.
Step 10: If the street segment has a weight limit, enter it in the Weight field. If the street
segment doesnt have a weight limit, enter zero. If you are using height and
weight road restrictions and the weight limit is less than the weight restriction
specified on the General page of the Maintenance Options notebook, the street
segment will be restricted. You can specify whether each equipment type is
permitted to travel on height and weight restricted roads when working with
equipment types.
1168

Editing the Network
Step 11: If the street segment has a height limit, enter it in the Height field. If the street
segment doesnt have a height limit, enter zero. If you are using height and
weight road restrictions and the height limit is less than the height restriction
specified on the General page of the Maintenance Options notebook, the street
segment will be restricted. You can specify whether each equipment type is
permitted to travel on height and weight restricted roads when working with
equipment types.
Note: All street segments that have a height or weight limit other than zero will appear
as a dotted line on a map.
Step 12: Check Restrict Commercial Vehicles to prevent commercial equipment types
from being routed on this road.
Note: This restriction does not apply to shortest path routes.
Step 13: If needed, check one of the following boxes for the street segment.
Loadablecheck the box as long as the street segment is not part of a ramp or
expressway that can only be accessed by a ramp.
Disabledcheck the box if the street segment should not be used. The network
will not use this segment when creating routes. Disabled roads appear as dotted
line on the map.
One Waycheck if traffic only travels one way on the street segment. To change
the direction, click the [Change Direction] button. The arrow on the map at the
bottom of the window indicates the direction of the traffic flow.
Step 14: To change the shape of the segment, click on the [Change Shape] button; make
the changes in the map at the bottom of the window.
Step 15: In the City Address 1 and City Address 2 sections, complete the City, State,
Zip, and Country fields. Make sure you enter information that corresponds to
Address Range 1 in the City Address 1 fields and information that corresponds to
Address Range 2 in the City Address 2 fields.
Step 16: If you are using historical travel speeds, click the Edit Historical Travel
Speeds tab.
Editing Historical Travel Speeds
Note: The Historical Travel Speeds tab will only appear if you have purchased Historical
Travel Speeds.
You can edit the speeds that will used by the historical travel speeds. On the Edit
Historical Travel Speeds tab, you can see the following:
the actual historical travel speeds being used
Operations Guide
1169
Editing the Network
OR
the map vendor speed altered by the information supplied in the Options notebook is
the calculated speed highlighted in red
Step 1: Right-click on the map and select Network, then Edit Street Mode from the menu
that pops up. Double-click on a street segment.
Step 2: Click on the Edit Historical Travel Speeds tab.
Step 3: Review/edit the appropriate travel speed day/time periods as necessary.
Step 4: Click the [Update] button.
Working with Impasses
Impasses are barriers you create on a single street segment that prevents traffic from
proceeding down the street. If you are creating an impasse on a split road, such as an
interstate, the impasse only affects the direction you place it on; traffic in the opposite
direction can proceed unimpeded. When routes are created, if an impasse is encountered
the route will not pass through the impasse; it will use alternate street segments to avoid
the impasse. Impasses can be used to compensate for construction or other temporary road
closings, as well as more permanent problems.
Step 1: Right-click on a map and select Network then Add Impasse Mode. The cursor
changes to indicate you are now in impasse mode and any existing impasses
appear on the map.
Step 2: Double-click on the street segment where you want to create the impasse. The
Add Impasse window opens. The Add Impasse window displays information
about the street segment, such as the name, address range, and whether the
segment is disabled or a one way.
Step 3: Click the [Add Impasse] button to add the impasse.
To remove an existing impasse, right-click on the impasse and select Remove Impasses
from the menu that pops up. The Impasse is removed.
Editing Nodes
Nodes connect the segments, and to travel from one street segment to another, traffic must
pass through a node. Nodes can be edited to restrict traffic from passing from one node to
the next, or, if the node represents an intersection, assess a time penalty for traveling
through the node. The nodes appear on the map in various colors, depending on the
characteristics associated with them.
Black nodesindicate that turns are allowed and no restrictions have been applied.
Grey nodesindicate that no turn is possible, such as when a node occurs but there
is no cross street, the street simply changes names.
Blue nodesindicate an overpass, underpass, or other physical restriction.
1170

Editing the Network
Red nodesindicate that a turn restriction has been applied, such as applying a time
restriction or disabling a turn.
Notes: A node at the end of a dead-end street will not be displayed.

If you want to assess a penalty for a specific kind of turn, such as a left turn from
a local road onto a secondary road, see Setting the Global Penalties.
Step 1: Right-click on the map. Scroll to Network and select Show Nodes from the menu
that appears. The nodes will appear as colored squares on the map.
Network Show Nodes
You can edit intersections (nodes) on the map and restrict turns
or assign a time penalty.
Step 2: Right-click on the node you want to edit and select Edit Penalties from the popup menu; the Penalty Editor opens. The street segments that pass through the
node are listed in the top of the window; the FromTo segments that are
highlighted in the list are shown on the map in the Penalty Editor.
Step 3: Select whether to make the path through the node accessible, restricted, or
assign a penalty. If a penalty is associated with the node, enter the delay in
minutes. See Penalty Editor for more information.
Note: If a global penalty is associated with that direction through the node, it will appear
in the Global Penalty area. If you want a specific penalty for this node, instead of
using the global penalty, remove the check from the Use Global Penalty box and
enter the specific penalty for the node.
Step 4: Click on the [Update] button when all paths through the node have been edited.
Operations Guide
1171
Editing the Network
Penalty Editor
The Penalty Editor, opened by right-clicking on a displayed node and selecting Edit
Penalties from the menu that pops up, allows you to modify nodes that are part of the
maps street network. Nodes control the ability of traffic to pass from one segment to
another. The Penalty Editor allows you to restrict this access, assess a time penalty for
passing through the node, or indicate various levels of elevation, such as an overpass,
underpass, tunnel, etc.
The top portion of the Penalty Editor window lists all segment combinations that pass
through the node. The combination currently being displayed at the bottom of the window
is highlighted in the list. To select the desired combination to edit, scroll through the list
and highlight the desired combination or click on the segments on the Penalty Editor map.
Make sure the segment combination you select goes in the proper direction.
The Penalty Editor lets you control how traffic flows through an individual
node.
Below the list is a map showing the highlighted segments with arrows indicating the path
through the node. To the left of the map are the options to control the flow from one
segment to another through the node. Click on the desired option to control traffic through
the node on that path.
Restrictedtraffic cannot pass through the node from the first segment to the second
segment.
Penaltytraffic can pass through the node, but there is a time penalty associated with
going through the node. Enter the delay time as H:MM:SS.
Accessibletraffic can pass unimpeded through the node.
1172

Editing the Network
If a global penalty has been applied to that direction through the node, it will appear in the
Global Penalty area. To assign a different penalty to this node, instead of using the global
penalty, remove the check from the Use Global Penalty box and enter the specific penalty.
In addition to the options explained above, you can choose to associate different levels of
elevation with street segments. For example, you might want to indicate the location of
overpasses or underpasses so that it is clear when routes are created that turns cannot be
made through nodes that occur where there is a bridge or tunnel. Simply click on an arc
in the list or on the map to select the segment you want to change, then click in the
Elevation field and select the appropriate elevation from the menu. Any change in
elevation (above or below ground level) will restrict turns on the selected street segment.
You will decide the best way to assign numeric values to various elevations, but keep in
mind that any intersecting roads with elevation differences should have different values.
There are several icons that can be used to traverse the map in the Penalty Editor window.
The Zoom In, Zoom Out, and Zoom to Fit icons can be used to change the zoom level of
the map, while the Center icon can be used to move across the map without changing the
zoom level. The window can also be resized as necessary.
Click on the [Update] button when all changes have been made.
Setting the Global Penalties
If you have situations involving turns that you want to avoid, you can create global
penalties to cover those circumstances. For instance, if you would like to avoid making
left turns out of neighborhoods onto busy secondary roads, you could create a global
penalty that would discourage these turns. You can create global penalties between each
type of road class, and any penalty you create will be used on all nodes that involve those
road classes. In the example above you could create a left turn penalty from a local road
to a secondary road; once this penalty was created all left turns from local roads onto
secondary roads would have the penalty applied. However, if there are specific places you
do not want the penalty applied, such as a turn that has a traffic light, you can turn off the
global penalty for that node and apply a different penalty.
Global penalties are specific to the direction you are passing through the node. This means
that you can have a global penalty for a left turn from a local road to a secondary road, but
no penalty to make a left turn from the secondary road to the local road.
If you want to assess a penalty for an individual turn or node, see Editing Nodes.
Step 1: On a map, right-click and select Network, then Update Global Penalty from the
menu that pops up. The Global Penalty Editor opens.
The Global Penalty Editor shows all the possible road class combinations you can
create global penalties for, as well as any global penalties that exist.
Step 2: Click on the From Type arrow and select the road class the traffic approaches
the node from.
Step 3: Click the To Type arrow and select the road class the node goes onto.
Operations Guide
1173
Editing the Network
Step 4: In the Left Penalty, Right Penalty, or Straight Penalty fields, enter the time
penalty associated with taking that action through the node. The penalty should
be entered in seconds, so enter a 1 minute penalty as 60 seconds.
Step 5: Continue choosing the road classes and entering penalties as needed. When all
penalties have been entered, click the [Update] button.
Updating by Road Class
The street network displayed on your map categorizes all roads into five types: interstate,
primary roads, secondary roads, local roads, and ramps. You can update the speed limit
on a whole category of roads simultaneously using Update by Road Class. This option can
be used to reflect new speed limits, or more temporary changes affecting a smaller area,
such as road construction.
Step 1: Right-click on the map. Scroll to Network and select Update by Road Class from
the menu that pops up. The Update by Road Class window opens.
Network Update by Road Class
Step 2: Click on the arrow and select the desired road class from the list that appears.
You can use the

Update by Road Class
feature to globally
Step 3: In the New Speed area, enter the new speed for the roads. If you are changing
all the roads to an absolute speed, click Set as new speed and enter the new speed
in the box. If you are changing all the roads by a percentage, click % Increase or
% Decrease and enter the percentage change in the box.
Step 4: In the Units area, indicate whether the new speed is Non-metric (miles per
hour) or Metric (kilometers per hour).
Step 5: In the Limit to area, choose which roads will be affected by the change.
Choose whether to have the change encompass the area displayed on the map
(Map View), all roads in a specified state (State), or all roads in your street
network (All Streets). If you choose State, enter the state or province in the box,
then click the arrow and choose the country. If you choose All Streets, any new
1174

Editing the Network
streets of the same road class you add will use the updated speed limit; if you
choose State or Map View, new streets will use the original speed limit.
To only have roads with specific speeds updated, check Current Speed Range and
enter the lowest and highest current speeds the roads should have for the update
to affect them. If this option is not selected, all roads of the selected class in the
chosen view will be updated.
Step 6: Click on the [Update] button when all changes are complete.
Operations Guide
1175
Evaluating the Network

One of the key functions of the maps is to provide Roadnet Technologies software with
the ability to create routes or sequence existing routes using the information contained in
the street network.
The street network shipped with your RouteNet system can be easily edited from a map.
Once you have edited the network, you can also use the map to evaluate its accuracy in
determining the best path between two points, such as a delivery location and depot. You
can determine the path between two addresses, two points on the map, or multiple points
on the map. To select a method, right-click on the map, scroll to Network and select the
desired option. The choices are described below.
If you know the address of both the beginning and ending point of the route, select
Address Path Mode from the Network menu. Enter the address information for the
Origin and Destination in the appropriate areas. The street number, name, and state
or zip code, and country, must be entered. If either address is marked with a
landmark, click on the As Landmark box and choose the correct landmark. Once the
origin and destination addresses are entered, click the [Generate] button. The
quickest route between the two addresses will be calculated and drawn on the map.
Network Address Path Mode
If you can find the source and destination on the map, or are just checking a path
from a general area to another area, select Shortest Path Mode from the Network
menu. Click on the starting point for the path; a pushpin appears on the map to
indicate the starting location. Click on the ending point of the path; a pushpin appears
on the map to indicate the ending location. The quickest route between the two points
will be generated and drawn on the map.
Network Shortest Path Mode
Note: While in the Shortest Path Mode, the map can be zoomed and moved as necessary
to find the origin and destination locations. Simply choose the needed zoom or
center option from the popup menu or from the icons. Press the [Esc] key to exit
the navigation mode and return to the Shortest Path Mode.
Shortest Path Mode will accept only one ending point of a path; if multiple points are
selected it will display a path from the original source point to the last selected
destination point. To determine a path with multiple points, select Multi Shortest
Path Mode. The path will be extended as necessary as each new point is selected. If
you make a mistake while drawing the path, press [Ctrl] + [Shift]+[U] to remove the
last segment drawn.
Network Multi-Shortest Path Mode
Once the path is drawn it can be analyzed and edited as needed.

To zoom the map on the path, making sure the entire path is visible on the screen, rightclick on the path. Select Fit from the menu that appears. The map will be redrawn to show
the entire path.
1176

To see the directions for the path, right-click on the path. Select Show Directions from
the menu that appears. The directions from the source to the destination will appear,
including distances and times for each street segment. If you choose to print these
directions, three maps will also print. The first map shows the entire path; the other two
maps zoom in on the origin and destination for the path.
To edit the any of the segments on the path, right-click on the path. Select Edit
Attributes to edit a single segment, or Edit All Attributes to edit multiple segments, from
the menu that appears. The Edit Street Attributes window opens.
Note: As you evaluate and use the map, if there are areas where you find the roads are
incorrect, you can take a screen shot of the area and e-mail it Roadnet
Technologies. We will collect e-mails and forward them to the appropriate map
vendor so that they can correct the error.
Operations Guide
1177
Explaining Stop Type Icons
Explaining Stop Type Icons

The Roadnet Transportation Suite uses icons to represent the different kinds of stops that
are scheduled during routes. Stop type icons appear in the stop lists in the Roadnet
Routing Editor, the Territory Planner Planning Editor, and the MobileCast Dispatcher.
The following chart shows the stop type icons used by Roadnet, Territory Planner, and
MobileCast.
Stop Type
Roadnet/Territory
Planner Icon
MobileCast Icon
Break
Wait
Layover
Mid-route Depot
Paid Break
Paid Layover
Paid Wait
Stop
Origin
Destination
Pre-route/Post-route
Canceled Stop
(MobileCast only)
Redeliverable Stop
(MobileCast Only)
1178

Menu Options
Menu Options
Menu Options
Many of the functions of the Roadnet Transportation Suite are accessed from the menu
bar that appears across the top of each module.
Maintenance Module Menu Options
The following menus appear in the Maintenance module, opened by clicking on the
Maintenance icon.
File
Mapopens a map, from which you can create and edit cells and barriers, as well as
edit the street network.
Print Setuplets you specify the printer that will be used, as well as the quantity to
be printed.
Exitcloses the Maintenance module.
List
User Defined Fieldslets you add and maintain user-defined field headers. The
content of the user-defined fields is associated with each location extension.
Service Ruleslets you add and maintain service information, such as scenarios,
service time types, time window types, service patterns, and service pattern sets. The
options that are available depend upon the modules you have purchased. Service
patterns and service pattern sets are only available if you are running Territory
Planner.
Loading Ruleslets you add and maintain loading information, such as mix rules and
stack rules. These options are only available if you are running FleetLoader.
Productlets you add and maintain product information, such as package types, SKU
brands, SKUs, and orders.
Travel Modelslets you add and maintain travel time models, as well as maintaining
the distance model.
Equipmentlets you add and maintain equipment information, such as bay types (if
using FleetLoader), equipment types, and equipment.
Employeeslets you add and maintain employee information, such as employee
types, employees, skill sets, and drivers.
Activitieslets you add and maintain information about the activities that can be
included on your order.
Account Typeslets you add and maintain account types.
Operations Guide
1179
Menu Options
Planning Sessionslets you add and maintain planning sessions used by Territory
Planner. This option is only available if you have Territory Planner.
Zoneslets you add and maintain zones.
Onboard Codeslets you add and maintain onboard codes used with an onboard
computer.
Routeslets you add and maintain information concerning your routes, including
route statuses, and route types.
Locationslets you add and maintain location information, including location types,
locations, location overrides, location substitutions, void locations, and loading
preferences. The options that are available depend on the modules that you have
purchased.
Dispatchlets you add and maintain MobileCast information, including containers,
container types, cancel stop codes, undeliverable stop codes, stop signature codes,
reason codes, order financial detail codes, delay types, track types, canned text
messages, driver alerts, wireless devices, and exception rules.
Loadthis menu will only appear if you have purchased the load option. From this
menu option, you can enter information for customers, common carriers, load
locations, types, customer commodities, STCC codes, and freight classes.
Schedulethis menu is only used with netScheduler. From this menu option, you can
enter information for the business calendar, delivery areas, delivery waves, delivery
windows, filters, and order classifications.
Tools
Update Service Timeslets you update the service times used with actual
information. You can update the service times by location or service time type, or
view the actual service time information on an interactive graph.
Database Maintenancelets you maintain the database, either by archiving items or
deleting older entries. You can also configure options to have older items deleted
automatically during the order import process. If you have deleted several items, or
have not compressed the database in some time, you can choose the Compact
Database option to compact the database, reducing its size.
Data Transportlets you create export files containing only the data needed to
troubleshoot a problem, so that a Roadnet Technologies support technician can work
with the data. This feature is only available if you are using an Oracle or SQL Server
database; it cannot be used with an Access database.
Combine Routing Sessionslets you combine routing sessions from one or more
databases into a single routing session. This can be used to add an archived session to
another routing session.
Optionslets you establish the defaults that are used when creating routing or
planning sessions, routes, locations, aliases, and other pertinent information such as
service time, wireless devices, route exceptions, detail levels, and travel time. You can
1180

Menu Options
also specify the default country for your locations. If you are exporting the routes into
MobileCast, you can specify which version of MobileCast you are using from here. It
also includes general setup information for Roadnet, Territory Planner, MobileCast,
and FleetLoader.
Actual Data Entry
Actual vs. Planned Commentslets you add and maintain actual vs. planned
comments.
Actual Route/Stoplets you manually enter actual route and stop information. This
information can be used by Service Time Maintenance to provide more accurate
service times when creating routes.
Driver Productivitylets you enter the amount of time the driver required to deliver
the product. This information is used for the Driver Productivity report. This option is
only available if you are running FleetLoader.
Load Productivitylets you enter the amount of time the warehouse personnel
needed to load the truck. This information is used for the Load Productivity report.
This option is only available if you are running FleetLoader.
Duty Period Historylets you view or edit the work time information for a particular
duty period. You can also add and delete duty periods.
Areaslets you add and maintain areas.
Area Distanceslets you enter the actual distance traveled in each region by each
piece of equipment.
Window
Close Allcloses all open windows.
Cascadestacks the open windows so that the title bar of each window is visible.
Tile Horizontallyarranges the open windows so that the most information is visible
horizontally.
Tile Verticallyarranges the open windows so that the most information is visible
vertically.
Save Window Positionssaves the size and position of open windows so that they
open in the same place in the future. You can overwrite or append saved window
positions.
Favoritessaves the size and position of open windows so that the next time you
enter the module they automatically open in the same place. You can save or restore
favorite window positions.
Help
Help Topicsopens the Roadnet Transportation Suite help file.
Roadnet Technologies Websiteautomatically connects you to the Roadnet
Technologies website.
Operations Guide
1181
Menu Options
Aboutprovides version information about Roadnet Transportation Suite.

Import Module Menu Options
The following menus appear in the Import module, opened by clicking the Import icon.
File
be printed.
Exitcloses the module.
Import
Orderslets you import orders into Roadnet.
Combine from Archivelets you import an archived routing session and combine it
with an existing session. This option is only available if you are using a Microsoft
Access database.
OnBoardlets you import information from the onboard computer into Roadnet.
Routed Solutionlets you import routes into Roadnet or FleetLoader.
Maintenance
Equipmentcontrols importing equipment information.
Equipment Typescontrols importing equipment type information.
Employeescontrols importing employee information.
Drivers controls importing driver information.
Locationscontrols importing location information.
Location Extensionslets you import location extension information into
Territory Planner. This option is only available if you are running Territory
Planner.
Containerscontrols importing container information. This menu option may be
called something else, depending on the alias selected in the Preferences
notebook.
SKUscontrols importing information for SKUs.
SKU Brandscontrols importing SKU Brand information.
Package Typescontrols importing information for package types.
Activitiescontrols importing Activities information.
Skill Setscontrols importing Skill Sets information.
Skill Set-Activitiescontrols importing Skill Set-Activities information.
Dispatch
1182

Menu Options
Static
Route Setholds a collection of static routes.
Routelists a collection of stops run on a continual or regular basis.
Daily
Fullcontrols importing a particular days route information.
Container Assignmentscontrols importing container assignments for a
days routes.
Setupcontrols editing the layouts for files to be imported.
Help
Territory Planner Planning Editor Menu Options
The following menu options appear in the Territory Planner Planning Editor.
File
Planning Sessionsopens the Planning Sessions window.
Close Planning Sessioncloses the current planning session. If necessary, you will
be prompted to save before closing the session.
Territory Scoreboardopens the Territory Scoreboard, which provides summary
information about the territories, as well as a score on how closely they met the
guidelines established in the Make Territories Options notebook.
Route Summaryopens the Route Summary, which provides summary information
about the routes.
Account Type Summaryopens the Account Type Summary which provides
information about how the account types are dispersed throughout the territories.
Location Origin Summaryopens the Location Origin Summary which provides
information about each location extension and each location extensions depot.
Mapopens a map, showing all selected territories or routes. You can also add and
maintain barriers, or drag a route or territory to a map to view it.
Savesaves the territories and routes as they currently exist.
Backup Savesaves the territories and routes as they currently exist in case of an
unexpected exit from the editor, such as if you lose power. To permanently save the
changes, you will need to do a complete save before exiting the editor.
Operations Guide
1183
Menu Options
Save Session Ascreates an exact copy of the current session that includes the
reloads, breaks and waits.
be printed.
Exitcloses the Planning Editor. If necessary, you will be given the option to save
your work.
List
Territoriesopens a window listing all existing territories. You can add and edit
territories from this window.
Routesopens a window listing all existing routes. You can add and edit routes from
this window.
Unassignedopens a window listing all location extensions not assigned to a
territory.
Stopsopens a window listing all stops.
Location Extensionsopens a window showing all location extensions.
Exceptionsopens windows showing stops that meet exceptions as established in the
Options notebook for off day deliveries, missed time windows, missed time window
factors, priority, or geocode.
Depotsopens a window listing all depots.
Driversopens a window listing all drivers. You can add and maintain drivers from
this window.
Equipmentopens a window listing all equipment. You can add and maintain
equipment from this window.
Service Patternsopens a window listing all available service patterns. You can add
and maintain service patterns from this window. You can assign service patterns to
location extensions/stops by dragging them to this window.
Service Pattern Setsopens a window listing all available service pattern sets. You
can add and maintain service pattern sets from this window. You can assign service
pattern sets to location extensions/stops by dragging them to this window.
Account Typesopens a window listing all account types. You can assign account
types to locations/stops by dragging them to this window.
Employeesopens windows listing employees types, employee statuses, employees,
driver types, skill sets, or drivers. You can add and maintain employee information in
these windows.
Equipmentopens windows listing equipment types, equipment statuses, or
equipment. You can add and maintain equipment information in these windows.
Service Rulesopens windows listing scenarios, service time types, time window
types, service patterns, and service pattern sets. You can add and maintain service rule
information from these windows.
1184

Menu Options
Travel Modelsopens windows displaying the distance, travel time, or rush hour
models. You can add and maintain travel model information from these windows.
User Defined Fieldsopens a window listing all existing user-defined fields. You can
add and maintain user-defined fields from this window.
Locationsopens window listing location types, locations, and location overrides.
You can add and maintain location information from these windows.
Tools
Optionsopens the Options notebook, from which you can specify how exceptions
will be displayed, the parameters to be used when time windowing routes, the colors
used to display weeks and days on the map, and the default actions when a stop is
dragged to a route.
Make All Territoriesopens the Make Territories window, from which you can
create territories using all location extensions or set up the options that will be used to
make the territories.
Assign Days to Allopens the Assign Days window, from which you can create
routes using all location extensions on the territories or set up the options that will be
used to create the routes.
Anchoringopens the Anchoring window, from which you can assign an anchor
range to all of the location extensions in the planning session at once.
Update Previous Days And Weeksupdates all Previous Days and Weeks in the
planning session to the current delivery days and weeks. If you use anchoring, the
Previous Days and Weeks are the days and weeks the location extensions will be
anchored to.
Session Transferlets you transfer selected location extensions to another planning
session. You can select the location extensions that will be transferred to a different
session, as well as set up the parameters used when transferring.
Update Roadnet Daily Routeslets you export selected routes to Roadnet 5000. You
can select the routes, as well as set up the parameters used when exporting.
Update MobileCastlets you export selected routes to MobileCast. You can select
the routes, as well as set up the parameters used when exporting.
Seed NetSchedulerlets you copy selected routes directly to netScheduler, where
they will form the basis for your netScheduler routes.
User Uploadlets you export information about selected routes to a mainframe,
network, or another computer. You can select the routes, as well as set up the
parameters used when exporting.
Shift Dayslets you move selected stops a specified number of days. You can select
the routes containing the stops, as well as set up the parameters for the shift.
Update Delivery Dayslets you update the locations delivery days, so that in
Roadnet the locations valid delivery days reflect the new information from Territory
Planner.
Operations Guide
1185
Menu Options
Locateopens a window from which you can find the territories, weeks, routes,
stops, or location extensions for a location, driver, or equipment.
Depot Planneropens the Depot Planner, a tool used to plan the best location for
future depots. This option is only available if Depot Planner was purchased.
Toolbarslets you open the General, Territory, Routing, or Location toolbars.
Reports
Groupslets you configure or print groups of reports.
Listopens a window listing all existing reports. You can add or maintain reports
from this window.
Window
horizontally.
vertically.
positions.
Help
Roadnet Routing Editor Menu Options
Used with: Roadnet
The following menu options are available in the Routing Editor, opened by clicking the
Routing icon.
File
Routing Sessionsopens the Routing Sessions window.
Close Routing Sessionlets you close the current routing session. If necessary, you
will be prompted to save your routes before closing the session.
1186

Menu Options
Summaryopens a summary of all routes, including minimums, maximums, and

averages for various criteria, such as run time and service time, quantities, distance,
and cost.
Weekly Summaryopens a summary showing all routes for the next 7 days. You can
choose to view the totals, averages, minimums, or maximums for each day.
Mapopens a map, showing all selected routes. You can also add and maintain cells
and barriers, or drag a route to a map to view it.
Savesaves all daily and standard routes as they currently exist.
Save Session Assaves the session as a new routing session. You can choose which
orders are included in the new session. This option can be used to try what-if
scenarios without destroying your current routes.
Save Standard Routessaves the standard route sets, standard routes, and standard
route stops as they currently exist.
Combine Routing Sessionslets you combine routing sessions from one or more
databases into a single routing session. This can be used to add an archived session to
another routing session.
Prepare for Merchandisinguses the selected orders to create a new session to route
a merchandiser. This option is only available if Prepare for Merchandiser was
purchased.
Prepare for Next Daymoves all unbuilt routes and unassigneds into a new session
that is created for the next business day.
Save All Routes Area Attributessaves the attributes for all the routes, including the
driver, equipment, route ID, depot, start time, description, and load priority. If the
option is selected, these attributes can automatically be assigned to future routes in the
same geographic area.
be printed.
Exitcloses the module. If necessary, you will be given the opportunity to save the
session before the module closes.
List
Routesopens windows showing all, active, or built routes. You can add and
maintain routes from these windows.
Unassignedopens a window showing all unassigned stops.
Not Consideredsopens a window showing all not considered orders, or orders with
no geocodes.
Stopsopens a window showing all the stops.
Ordersopens a window showing all the orders and which route they are on.
Line Itemsopens a window showing all the line items.
Operations Guide
1187
Menu Options
Order Activitiesopens a window showing all order activities.

Voidsopens a window listing all orders for void locations.
Locations with Ordersopens a window showing all locations with orders.
Futuresopens a window showing all future stops or all future orders.
Exceptionsopens windows showing stops that meet exceptions as established in the
Options notebook for off day deliveries, missed time windows, missed time window
factors, priority, geocode, skill sets, or preferred route IDs.
Selectorsopens windows showing orders with all or individual selectors.
Preferred Route Propertiesopens a window showing all preferred route properties.
You can add or maintain preferred route properties from this window.
Depotsopens a window listing all depots. You can add or maintain depots from this
window.
Driversopens a window listing all drivers. You can add or maintain drivers from
this window.
Equipmentopens a window listing all equipment. You can add or maintain
equipment from this window.
Account Typesopens a window listing all account types. You can add or maintain
account types from this window.
Activitiesopens a window listing all activities. You can add or maintain activities
from this window.
Employeesopens windows listing all employees types, employee statuses,
employees, driver types, skill sets, or drivers. You can add or maintain employee
Productopens windows listing all package types, SKU brands, SKUs, or Product
Types. You can add or maintain product information from these windows.
Equipmentopens windows listing all bay types, equipment types, equipment
statuses, equipment, and compartments. You can add or maintain equipment
Service Rulesopens windows listing all scenarios, service times types, and time
window types. You can add or maintain service rule information from these windows.
Travel Modelsopens windows listing all travel time models and rush hour models,
or showing the distance model. You can add or maintain travel time models and rush
hour models, or maintain the distance model, from these windows.
Areasopens a window listing all areas. You can add or maintain areas from this
window.
Zonesopens a window listing all zones. You can add or maintain zones from this
window.
1188

Menu Options
Locationsopens windows listing all locations, location overrides, and location

types. You can add or maintain location information from these windows.
Standard Routes
Setsopens a window listing all standard route sets. You can add or maintain
standard route sets from this window.
Routesopens a window listing all standard routes. You can add or maintain standard
routes from this window.
Unassignedopens a window listing all unassigned standard stops. You can assign
stops to standard routes from this window.
Add Stopsopens a window letting you add stops to standard routes.
Tools
Optionsopens the Options notebook, from which you can specify how exceptions
will be displayed, the parameters to be used when time windowing routes, how orders
are split and delivery costs are calculated, and the default actions when a stop is
dragged to a route or standard route.
Route All Available Ordersopens the Route Creation Process window from which
you can create routes from all unassigned orders and orders on active routes, as well
as creating and defining routing passes.
Speed Assign Active Routesopens the Speed Assign window, from which you can
assign drivers, equipment, and IDs to all active routes.
Send All Ordersopens the Send Orders window from which you can export all
orders to the host computer, or specify the layout for the export file.
Export All Routesopens the Send Stops window, from which you can export stop
information for use with an onboard computer, or specify the layout of the export file.
Locateopens a window from which you can find the routes, stops, or orders for a
location, driver, or equipment.
Toolbarsopens the General, Route, Stop, or Std. Route toolbars which can be
arranged in the module for easy use.
Reports
from this window.
Window
horizontally.
Operations Guide
1189
Menu Options
vertically.
positions.
Help
FleetLoader Loading Editor Menu Options
The following menus appear in the FleetLoader module, opened by clicking on the
FleetLoader icon.
File
Routing Sessionsopens the Routing Sessions window, listing all existing sessions.
Close Routing Sessionscloses the routing session that is currently open.
Savesaves the truck as it is currently loaded. If you save a truck, and subsequently
choose to load all trucks, any edits you made to the truck will be wiped out.
Save and Locksaves the truck as it is currently loaded and locks it. If you lock a
truck and subsequently choose to load all trucks, the truck will not be reloaded so your
edits will not be changed.
Optionsopens a window where you can select the options you want to use during
the routing session. These options include warnings you want to appear, and how
information is displayed in the windows.
be printed.
Exitcloses the FleetLoader module.
Load
Load Selected Route(s)opens the Load Trucks window from which you can load
the selected routes or change the load options.
Load All Available Routesopens the Load Trucks window from which you can load
all routes or change the load options.
1190

Menu Options
Loading Optionsopens the Loading Options window for which you can change the
load options without having an open session.
View
Routesopens the Routes window for the session.
Layersopens the Layers window, which shows each layer of product and the layers
placement on a pallet.
Bay Contentsopens the Bay Contents window, which displays the contents of each
bay.
Truck Profileopens the Truck Profile, which shows how full each bay is.
SKUsopens the SKUs window, which lists each SKU and they bay it is in, the order
number, and stop information.
Unassigned SKUsopens the Unassigned SKU window, which lists the SKUs that
have not been loaded.
SKU Tree Viewopens the SKU Tree View, which shows which bay the SKU is
loaded into and the quantity in each bay.
Split SKU Tree Viewopens the Split SKU Tree View which lists only those SKUs
that are in multiple bays, and the bays they are in.
Stop Tree Viewopens the Stop Tree View which lists all the stops, and where the
product for each stop is loaded.
Bay Tree Viewopens the Bay Tree View which lists all the bays and the product
loaded in each bay.
Condensedshows the condensed information in the Bay Contents and Unassigned
SKU windows. Condensed information does not include the order and stop
information.
Detailedshows the detailed information in the Bay Contents and Unassigned SKU
windows. Detailed information includes the order and stop information.
Reports
from this window.
Tools
Delete Prebuilt Solutionif you import stops or orders to be pre-built by warehouse
personnel, you can delete the prebuilt solution for that session if the wrong routing
session was built.
Export All Routeslet you export all loaded routes.
Window
Operations Guide
1191
Menu Options
horizontally.
vertically.
positions.
Help
MobileCast Dispatcher Menu Options
The following menus appear in the Dispatcher module, opened by clicking on the
Dispatcher icon.
File
Print Setupallows you to select a printer and set up printer properties.
Exitcloses all windows and exits from the Dispatcher module.
View
Equipment Mapdisplays a map of the delivery area in which to pinpoint the current
location of a piece(s) of equipment.
Position Historydisplays a map of the delivery area in which to pinpoint and view
the position history of selected route(s) and pieces of equipment.
Message Centeropens the message center, where unacknowledged notes, including
those from the server and the driver, can be viewed.
Route Overviewlists all Not Completed and Not Assigned Routes.
Route Watchopens the Route Watch window, where a dispatcher has a live view
of all unacknowledged exceptions occurring throughout the progress of a route.
Route Watch Mapopens the Route Watch Map, which displays a live view of all
unacknowledged exceptions occurring on all of the routes, at the locations where they
are occurring.
1192

Menu Options
My Routes Onlylists only the routes that are assigned to you.

Mapdisplays a map of the delivery area for the highlighted route in the Not
Completed and Not Assigned windows.
Routes
Not Completedlists, by planned start date and ID, routes that are either currently
being run or haven't been started.
Not Assignedlists, by route date and route ID, any routes that do not have drivers
and equipment assigned. To work with a route in the Unassigned Routes window,
right-click on it to open a pop-up menu of options. To work with a route's stops,
double-click on the route, then right-click on a stop in the resulting window.
Summaryopens the Route Summary window, which can be used to determine the
status of routes within a selected range of dates. For instance, you can easily determine
which routes have had drivers or equipment assigned, or have been started or
completed.
Queryopens the Route Query Results window, which allows you to locate a route
if you know the driver, a location on the route, or other piece of information.
Newopens the Add new Route window, from which you can add new routes and
stops and orders to the route. Choose whether to create a dedicated or non-dedicated
route.
LoadsThis option is available only if you have load rights.
Availablelists all loads available that can be claimed.
Active lists all loads that have been claimed or assigned.
Query opens a Route Query window to query for loads.
Customerlists all load customers. Load customers can be used as the Bill To or
Shipper. Load customers cannot be changed in the Dispatcher; they are maintained in
Maintenance.
Common Carrierslists all common carriers available for loads. Common carriers
cannot be changed in the Dispatcher; they are maintained in Maintenance.
Locationsin response to a search, lists all locations available for load pick ups,
deliveries, or meeting points. Load locations cannot be changed in the Dispatcher
module; they are maintained in the Maintenance module.
Typeslists the possible types of loads. Load types cannot be changed in the
Dispatcher; they are maintained in Maintenance.
Customer Commoditieslists the commodity types created for the region. Customer
commodities, which are specific to each MobileCast region, cannot be changed in the
STCC Codeslists the STCC codes that can be assigned to the loads. STCC Codes,
which are available to all MobileCast regions, cannot be changed in the Dispatcher;
they are maintained in Maintenance.
Operations Guide
1193
Menu Options
Freight Classeslists the freight classes that can be assigned to the loads. Freight
classes, which are available to all MobileCast regions, cannot be changed in the
List
Employeeslists all employees for the current region, including name and status;
checkboxes that indicate whether they're active and available; employee type; ADP
file number, address, and phone numbers; and birth, start, and termination dates.
Employee information cannot be changed in the Dispatcher; it is maintained in
Maintenance.
Driverslists all drivers for the current region, including status, name, driver type (if
any), license information, date of last physical, and date of last drug test. Driver
information cannot be changed in the Dispatcher; it is maintained in Maintenance.
Equipmentin response to a search, lists equipment for the current region, including
description, inspection date, current status, route and route assignments, location, and
load capacities. Equipment information cannot be changed in the Dispatcher; it is
maintained in Maintenance.
Locationsin response to a search, lists locations for the current region, including
longitude and latitude, address, phone and fax numbers, general contact information,
and contact information in case of a service failure. Locations cannot be maintained
in the Dispatcher, although new ones can be added here. Changes to existing locations
are made in Maintenance.
Containerslists any containers that have been created in Maintenance, including the
type and the location type and ID of the location at which each container was last
dropped.
Codes
Route Statuseslists any statuses that have been created in Maintenance.
Route Typeslists any types of routes that were created in Maintenance.
Delay Typeslists the possible types of delays.
Reason Codeslists any reason codes that have been created in Maintenance.
Cancel Stop Codeslists any cancel stop codes that have been created in
Maintenance.
Undeliverable Stop Codeslists any undeliverable stop codes that have been
created in Maintenance.
Stop Signature Codeslists any stop signature codes that have been created in
Maintenance.
Order Financial Detail Codeslists any financial codes that have been created in
Maintenance.
Order Status Codeslists any order status codes that have been created in
Maintenance.
1194

Menu Options
User Notesopens a window from which you can add a note for another user, or
search for existing user notes.
Canned Text Messageslists any canned text messages that have been created in
Maintenance.
Unassignedsopens a window listing all unassigneds stops.
Distance by Jurisdictionopens a window where you can retrieve the distances
routes traveled in each jurisdiction. Once the information has been gathered, you can
print reports or export the data.
Skill Setsopens a window listing activities that an employee is able to perform.
User Defined Datalists the user-defined tables that have been created in the Roadnet
Transportation Suite database; choose the appropriate table to view the data.
Wireless Eventslists all wireless events for the region that have occurred. The
events can be edited.
Event Receiptslists all events that are sent back and forth between the server and a
wireless device.
Window
Tile Horizontallyarranges all open windows in rows so they cover the length of the
module window.
Tile Verticallyarranges all open windows side by side so they cover the height of
the module window.
Save Window Positionssaves the position of open windows on the screen so that
they will reopen in the same place. You can choose to append existing saves or
overwrite existing saves.
Favoritessaves all open windows, and their size and position, so that they will
appear as arranged when the module opens. You can also restore saved open windows
that were closed.
Change Refresh Rateopens a window that allows you to set how frequently the
windows in Dispatcher will be updated with information from the database.
Help
Help Topicsdisplays the on-line help system for MobileCast.
Roadnet Technologies Websiteopens the Roadnet Technologies web site.
Aboutdisplays information about MobileCast, including version and copyright
date.
Operations Guide
1195
Menu Options
Administration Module Menu Options

The following menus appear in the Administration module, opened by clicking on the
Administration icon.
File
be printed.
Exitcloses the Administration module.
List
Usersopens a window listing all existing users. You can add or maintain users from
this window.
User Groupsopens a window listing all existing user groups. You can add or
maintain user groups from this window.
Notification Recipientsopens a window listing all existing notification recipients.
You can add or maintain notification recipients from this window.
Privilegesopens a window listing all existing privileges. You can add or maintain
privileges from this window.
Organization Unitsopens a window listing all organization units. You can add or
maintain organization units from this window.
Regionslets you add and maintain region information, such as the regions and the
rush hour and time of day restriction models used by each region.
Aliasesopens the Aliases window. You can enter the region aliases for up to three
user-defined fields containing information for each region. The headers are common
to all regions. You can also enter a description for your organization units, which will
appear wherever organization units are referenced.
Tools
Optionsopens a window from which you can specify some of the options used for
setting up users, user groups, and privileges with RIC, or enter existing database user
information so that the user can create user-defined tables in the Roadnet
Update Configuration Keyopens a window from which you can browse to an
updated config.key file.
Securitylets you edit the authentication policy as well as perform security related
features on a global level, such as locking out all non-super users.
Window
1196

Menu Options

horizontally.
vertically.
positions.
Help
Reports Module Menu Options
The following menus appear in the Reports module, opened by clicking on the Reports
icon.
File
be printed.
Exitcloses the Reports module.
List
Reportsopens a window listing all existing reports. You can add or maintain reports
from this window.
Groups
Configureopens a window from which you can create or edit report groups.
Printprints the selected report group.
Window
Cascadetacks the open windows so that the title bar of each window is visible.
Operations Guide
1197
Menu Options
horizontally.
vertically.
positions.
Help
1198

Route History
Using Route History
Using Route History

Used with: Route History
Note: If you are using Route History, it should have been installed when the Roadnet
Transportation Suite was installed. When Route History is installed, you can
choose to have it as a separate schema within the Transportation Suite database or
as a separate database. Roadnet Technologies recommends that you use a separate
database for Route History.
Route History is a portion of the Roadnet Transportation Suite where historical routing
data is saved. Because not as much data is needed for historical purposes, the database
grows more slowly and Route History data can be stored for a longer time. In addition,
the database is not as complex as the full Transportation Suite database, making it easier
to query and write reports against.
The Route History database is comprised of tables containing route and stop information,
and views that combine this information into a more usable format. You should be able
to perform almost all of your SQL queries against the views rather than the tables. In
addition, performing your queries against the views, rather than against the tables, will
reduce the amount you will need to change your queries if the tables change. There are
several views for both routes and stops, each with specific information. There are six
views that contain routing information:
RH_ROUTE_BASE_VIEWcontains the basic information about the route, such as the
ID, date, origin, destination, etc. This view does not contain any route totals, such as times
or cost.
RH_ROUTE_PLANNED_VIEWcontains the planned information about the route,
such as the planned times, distances, and number of stops.
RH_ROUTE_ACTUAL_VIEWcontains the actual information about the route. This
information can come from MobileCast or manually entered into Roadnet or imported
from a onboard computer.
RH_ROUTE_PLAN_VS_ACTUAL_VIEWcontains both the planned and actual route
information.
RH_ROUTE_BEST_DATA_VIEWcontains the most accurate information possible
about the route. In many cases this will be the actual data, but when no actual data exists
the planned data will be used.
RH_ROUTE_VIEWcontains all the information about the route, such as the origin,
destination, duration, costs, times, and quantities. Most times, this will be the view you
want to use.
There are four views that contain stop information:
RH_STOP_BASE_VIEWcontains the basic information about the stop, such as the
location ID and address.
RH_STOP_PLANNED_VIEWcontains planned information about the stops, such as
the planned quantities and times.
Operations Guide
1199
RH_STOP_ACTUAL_VIEWcontains the actual information about the stops. If you

are using MobileCast and have actual data, you will probably want to use this view most
often.
RH_STOP_PLAN_VS_ACTUAL_VIEWcontains both the planned and actual stop
information.
1200

Retrieving Information from Route History

The benefit of storing your routing data in Route History is that it is easy to retrieve the
information, such as to create your own reports. Since the information is stored in a
database, you can use SQL statements to retrieve the information. Some example SQL
statements follow; these examples provide only a small sample of the type of information
you can retrieve from Route History. See the specific information on the route and stop
views to determine which views will be best for your purposes.
To determine the total cost of all routes in the Baltimore region between September
1, 2004 and September 30, 2004;
select sum(COST_TOTAL) from RH_ROUTE_VIEW where ROUTE_DATE between 01-SEP-2004
and 30-SEP-30, 2004 and REGION_ID=Baltimore;
To determine the number of routes in the Baltimore region between September 1,

2004 and September 30, 2004;
select count(*) from RH_ROUTE_VIEW where ROUTE_DATE between 01-SEP-2004 and 30-SEP2004 and REGION_ID=Baltimore;
To determine the total number of stops in the Baltimore region between September
1, 2004 and September 30, 2004;
select sum(STOP_COUNT_TOTAL) from RH_ROUTE_VIEW where ROUTE_DATE between 01SEP-2004 and 30-SEP-2004 and REGION_ID=Baltimore;
To determine the planned and actual total costs of all routes in the Baltimore region
between September 1, 2004 and September 30, 2004;
SELECT
sum(RH_ROUTE_PLANNED_VIEW.COST_TOTAL) as COST_TOTAL_PLANNED,
sum(RH_ROUTE_ACTUAL_VIEW.COST_TOTAL) as COST_TOTAL_ACTUAL
FROM
RH_ROUTE_PLANNED_VIEW,
RH_ROUTE_ACTUAL_VIEW
WHERE
RH_ROUTE_PLANNED_VIEW.PKEY=RH_ROUTE_ACTUAL_VIEW.PKEY(+) and
(RH_ROUTE_PLANNED_VIEW.ROUTE_DATE between 01-SEP-2004 and 30-SEP-2004) and
RH_ROUTE_PLANNED_VIEW.REGION_ID = BALTIMORE;
Operations Guide
1201
To determine the planned vs. actual total time for driver John Smith in the
Baltimore region between September 1, 2004 and September 30, 2004:
select
sum(RH_ROUTE_PLANNED_VIEW.TIME_TOTAL) as TIME_TOTAL_PLANNED,
sum (RH_ROUTE_ACTUAL_VIEW.TIME_TOTAL) as TIME_TOTAL_ACTUAL,
from RH_ROUTE_PLANNED_VIEW, RH_ROUTE_ACTUAL_VIEW
where
RH_ROUTE_PLANNED_VIEW.PKEY=RH_ROUTE_ACTUAL_VIEW.PKEY(+)
and
RH_ROUTE_PLANNED_VIEW.DRIVER1_LAST_NAME=Smith
and
RH_ROUTE_PLANNED_VIEW.DRIVER1_FIRST_NAME=John
and
RH_ROUTE_PLANNED_VIEW.ROUTE_DATE between 01-SEP-2004 and 30-SEP-2004
and
RH_ROUTE_PLANNED_VIEW.REGION_ID=Baltimore;
1202

Route Views
Route Views
Route History includes both route and stop views to provide easy, stable access to the
information in the database. It is strongly suggested you use the views to retrieve
information from Route History, rather that using the tables themselves. There are six
route views and four stop views you can use.
The route view that you will most likely use is RH_ROUTE_VIEW. This view contains
all the available information about the route, such as quantity delivered and picked up,
costs, distances, stops, etc. When available, actual data from MobileCast is used,
otherwise actual or planned data from Roadnet is used.
The following views contain route information:
RH_ROUTE_BASE_VIEWcontains the basic information about the route, such as the
ID, date, origin, destination, etc. This view does not contain any route totals, such as times
or cost.
RH_ROUTE_PLANNED_VIEWcontains the planned information about the route,
such as the planned times, distances, and number of stops.
RH_ROUTE_ACTUAL_VIEWcontains the actual information about the route. This
information can come from MobileCast or manually entered into Roadnet or imported
from a onboard computer.
RH_ROUTE_PLAN_VS_ACTUAL_VIEWcontains both the planned and actual route
information.
RH_ROUTE_BEST_DATA_VIEWcontains the most accurate information possible
about the route. In many cases this will be the actual data, but when no actual data exists
the planned data will be used.
RH_ROUTE_VIEWcontains all the information about the route, such as the origin,
destination, duration, costs, times, and quantities. Most times, this will be the view you
want to use.
See Route Views ERD for a visual display of how the route views are related.
RH_ROUTE_VIEW
The table below details the information available from RH_ROUTE_VIEW. This view
contains all the information about the route, such as the origin, destination, duration,
costs, times, and quantities. If actual data is available it will be used, otherwise planned
data will be used. Most times, this will be the view you want to use.
Column Name
PKEY
ORG_UNIT_ID
ORG_UNIT_NAME
REGION_ID
REGION_NAME
ROUTE_ID
Data Type
Not
Description
Null?
INTEGER
Y
Primary key from RH_ROUTE_MASTER
VARCHAR2(15) Y
The ID for the organization unit.
VARCHAR2(30) Y
The name of the organization unit.
NVARCHAR2(18) Y
Unique ID for the region.
VARCHAR2(255) Y
The name of the region.
NVARCHAR2(30) Y
The routes ID.
Operations Guide
1203
Route Views
Column Name
ROUTE_DATE
DESCRIPTION
SCENARIO
HELPER
ORIGIN_ID
ORIGIN_TYPE
ORIGIN_DESCRIPTION
ORIGIN_TIME_ZONE
DESTINATION_ID
DESTINATION_TYPE
DESTINATION_DESCRI
PTION
DESTINATION_TIME_Z
ONE
DRIVER1_REGION_ID
DRIVER1_ID
DRIVER1_LAST_NAME
DRIVER1_FIRST_NAME
DRIVER1_MIDDLE_NA
ME
DRIVER2_REGION_ID
DRIVER2_ID
DRIVER2_LAST_NAME
DRIVER2_FIRST_NAME
DRIVER2_MIDDLE_NA
ME
EQUIP1_REGION_ID
EQUIP1_TYPE_ID
EQUIP1_ID
EQUIP1_DESCRIPTION
Data Type
Not
Description
Null?
DATE
Y
The identifying date for the route. If the data is
from Roadnet, it is the session date; if the data is
from MobileCast it is the route date. This date
may not match the routes start date.
NVARCHAR2(128
Route description
)
NVARCHAR2(30)
The scenario used for the route.
INTEGER
Indicates whether the route had a helper or not. 0
= no helper on route, 1 = helper on route
NVARCHAR2(30)
Unique location ID of the routes origin, usually
the depot.
NVARCHAR2(6)
Location type of the routes origin, usually DPT.
NVARCHAR2(120
Description of origin
)
INTEGER
Numeric code for the origins time zone. The
North America options are: 8 Eastern Time; 9
Indiana; 10 Central Time; 13 Arizona; 14
Mountain Time; 15 Pacific Time.
NVARCHAR2(30)
Unique location ID of the routes destination,
usually the depot.
NVARCHAR2(6)
Location type of the routes destination, usually
DPT.
NVARCHAR2(120
Description of destination
)
INTEGER
Numeric code for the destinations time zone.
The North America options are: 8 Eastern Time;
9 Indiana; 10 Central Time; 13 Arizona; 14
NVARCHAR2(18)
Region ID of the region that controls driver 1.
NVARCHAR2(30)
Unique employee ID for driver 1.
NVARCHAR2(70)
Last name of driver 1
NVARCHAR2(70)
First name of driver 1
NVARCHAR2(70)
Middle name of driver 1
NVARCHAR2(18)
NVARCHAR2(30)
NVARCHAR2(70)
NVARCHAR2(70)
NVARCHAR2(70)
NVARCHAR2(18)
NVARCHAR2(30)
NVARCHAR2(40)
NVARCHAR2(510
)
EQUIP1_TYPE_DESCRIP NVARCHAR2(510
TION
)
EQUIP1_BULK_LOAD
NVARCHAR2(2)
1204

Unique employee ID of driver 2.
Last name for driver 2
First name for driver 2
Middle name for driver 2
Region ID of the region that controls equipment 1
Unique ID of the equipment type for equipment 1
Unique ID for equipment 1
Description of equipment 1
Description of equipment 1 type
Indicates whether the first piece of equipment

assigned to the route carries a bulk load, such as
pallets. This information is only pertinent if you
are using FleetLoader. (T or F)
EQUIP2_REGION_ID
NVARCHAR2(18)
Region ID of the region that controls equipment 2
Route Views
Column Name
Data Type
EQUIP2_TYPE_ID
NVARCHAR2(30)
EQUIP2_ID
NVARCHAR2(40)
EQUIP2_DESCRIPTION NVARCHAR2(510
)
TION
)
EQUIP2_BULK_LOAD
NVARCHAR2(2)
CAPACITY_SIZE1
CAPACITY_SIZE2
CAPACITY_SIZE3
DATA_SOURCE
FLOAT(126)
FLOAT(126)
FLOAT(126)
NVARCHAR2(4)
START_TIME
DATE
COMPLETE_TIME
DATE
DEPARTURE
DATE
ARRIVAL
DATE
DISTANCE_TOTAL_MI
NUMBER
DISTANCE_TOTAL_KM NUMBER
DISTANCE_STEM_OUT_ NUMBER
MI
KM
DISTANCE_STEM_IN_M NUMBER
I
DISTANCE_STEM_IN_K NUMBER
M
TIME_TOTAL
NUMBER
TIME_STEM_OUT
NUMBER
TIME_STEM_IN
NUMBER
TIME_PAID
NUMBER
TIME_SERVICE
NUMBER
TIME_TRAVEL
NUMBER
Not
Null?
Description
Unique ID of the equipment type for equipment 2
Unique ID for equipment 2
Description of equipment 2
Description of equipment 2 type
Indicates whether the second piece of equipment
Routes total capacity for size 1
The source of the route data. RN = Roadnet, MC
= MobileCast
The date and time the route started (GMT). The
best available data will be used.
The date and time the route was completed
(GMT). The best available data will be used.
The date and time the driver left the origin
(GMT). The best available data will be used.
The date and time the driver reached the
destination (GMT). The best available data will
be used.
The total distance for the route in miles. The best
available data will be used.
The total distance for the route in kilometers. The
The distance from the origin to the first stop in
miles. The best available data will be used.
The distance from the origin to the first stop in
kilometers. The best available data will be used.
The distance from the last stop to the destination
in miles. The best available data will be used.
The distance from the last stop to the destination
in kilometers. The best available data will be
used.
The total time (travel + service) of the route in
seconds. The best available data will be used.
The time it took to travel from the origin to the
first stop in seconds. The best available data will
be used.
The time it took to travel from the last stop to the
destination in seconds. The best available data
will be used.
The amount of time the driver is paid for in
seconds. The best available data will be used.
The total amount of time the driver spent
servicing customers in seconds. The best
The total amount of time the driver spent driving
in seconds. The best available data will be used.
Operations Guide
1205
Route Views
Column Name
Data Type
TIME_WAIT
NUMBER
TIME_BREAK
NUMBER
TIME_LAYOVER
NUMBER
QTY_DELV_SIZE1
NUMBER
QTY_DELV_SIZE2
NUMBER
QTY_DELV_SIZE3
NUMBER
QTY_PICKUP_SIZE1
NUMBER
QTY_PICKUP_SIZE2
NUMBER
QTY_PICKUP_SIZE3
NUMBER
QTY_OVER_SIZE1
FLOAT(126)
QTY_OVER_SIZE2
FLOAT(126)
QTY_OVER_SIZE3
FLOAT(126)
QTY_SHORT_SIZE1
FLOAT(126)
QTY_SHORT_SIZE2
FLOAT(126)
QTY_SHORT_SIZE3
FLOAT(126)
QTY_DAMAGED_SIZE1 FLOAT(126)
Not
Null?
Description
The total time the driver spent on waits (paid and
unpaid) in seconds. The best available data will
be used.
The total time the driver spent on breaks (paid
and unpaid) in seconds. The best available data
will be used.
The total time the driver spent on layovers (paid
and unpaid) in seconds. The best available data
will be used.
The total quantity of size 1 delivered. The best
The total quantity of size 1 picked up. The best
The quantity of size 1 delivered or picked up in
addition to the planned quantity. This
information is only available if MobileCast is
used.
used.
used.
The amount the quantity of size 1 was less than
the planned quantity. This information is only
available if MobileCast is used.
The quantity of size 1 that was marked as
damaged. This information is only available if
MobileCast is used.
MobileCast is used.
MobileCast is used.
1206

Route Views
Column Name
Data Type
MAX_PERCENT_FULL_ NUMBER
SIZE1
SIZE2
SIZE3
STOP_COUNT_TOTAL
NUMBER
STOP_COUNT_DELVS
NUMBER
STOP_COUNT_PICKUPS NUMBER
STOP_COUNT_PICKUPS
_DELVS
STOP_COUNT_MISSED_
TW
STOP_COUNT_OFFDAY
_DELVS
STOP_COUNT_CANCEL
ED
NUMBER
NUMBER
NUMBER
INTEGER
STOP_COUNT_DELV_Q INTEGER
TY_EXCPT
STOP_COUNT_EARLY INTEGER
STOP_COUNT_LATE
INTEGER
STOP_COUNT_ROUTE_ INTEGER
EXCPT
ORDER_COUNT_TOTAL NUMBER
ORDER_COUNT_DELVS NUMBER
ORDER_COUNT_PICKU NUMBER
PS
LINE_ITEM_COUNT_TO NUMBER
TAL
LINE_ITEM_COUNT_DE NUMBER
LVS
LINE_ITEM_COUNT_PIC NUMBER
KUPS
STOPS_OUT_OF_SEQ
NVARCHAR2(2)
COST_TOTAL
NUMBER
COST_OVERTIME
NUMBER
Not
Null?
Description
The highest percentage of its total capacity as
size 1 the equipment was during the course of the
route. The best available data will be used.
The total number of stops on the route. The best
The total number of stops with deliveries. The
The total number of stops with pickups. The best
The total number of stops with both deliveries
and pickups. The best available data will be used.
The total number of stops with missed time
windows. The best available data will be used.
The total number of stops with off day deliveries.
The best available data will be used.
The total number of stops that were canceled.
This information is only available if MobileCast
is used.
The total number of stops with exceptions related
to quantity delivered. This information is only
The total number of stops that were early.
The total number of stops that were late.
The total number of stops with route exceptions.
is used.
The total number of orders (delivery and pickup)
on the route. The best available data will be used.
The total number of delivery orders on the route.
The total number of pickup orders on the route.
The total number of line items (delivery and
pickup) on the route. The best available data will
be used.
The total number of delivery line items on the
The total number of pickup line item on the route.
A T or F indicating the stops were not delivered
in the planned order.
The total cost for the route. The best available
data will be used.
The total overtime cost for the route. The best
Operations Guide
1207
Route Views
Table Summary
Table Name
RH_ROUTE_MASTER
RH_LOCATION
RH_EMPLOYEE
RH_EQUIPMENT
RH_EQUIPMENT_TYPE
RH_ROUTE_PLAN_VS_ACTUAL_VIEW
The RH_ROUTE_PLAN_VS_ACTUAL_VIEW is useful when you want to compare the

planned route versus how the route was actually run. The actual information will either
come from MobileCast, or if MobileCast is not used, from an onboard computer
information imported into Roadnet or actual information manually entered into Roadnet.
Column Name
Data Type
PKEY
ORG_UNIT_ID
ORG_UNIT_NAME
REGION_ID
REGION_NAME
ROUTE_ID
ROUTE_DATE
DESCRIPTION
Not
Null?
INTEGER
Y
VARCHAR2(15) Y
VARCHAR2(30) Y
NVARCHAR2(18) Y
VARCHAR2(255) Y
NVARCHAR2(30) Y
DATE
Y
NVARCHAR2(128
)
NVARCHAR2(30)
INTEGER
SCENARIO
HELPER
ORIGIN_ID
NVARCHAR2(30)
ORIGIN_TYPE
NVARCHAR2(6)
ORIGIN_DESCRIPTION NVARCHAR2(120
)
ORIGIN_TIME_ZONE
INTEGER
DESTINATION_ID
DESTINATION_TYPE
NVARCHAR2(30)
NVARCHAR2(6)
DESTINATION_DESCRI NVARCHAR2(120
PTION
)
Comment
Unique ID for the route.
Route description
Indicates whether or not the route has a helper. 0
= no helper, 1 = helper
The unique location ID for the origin.
The location type for the origin, usually DPT.
The location description or name for the origin.
The unique location ID for the destination.
The location type for the destination, usually
DPT.
The location description or name for the
destination.
1208

Route Views
Column Name
Data Type
DESTINATION_TIME_Z INTEGER
ONE
DRIVER1_REGION_ID
NVARCHAR2(18)
DRIVER1_ID
NVARCHAR2(30)
DRIVER1_LAST_NAME NVARCHAR2(70)
DRIVER1_FIRST_NAME NVARCHAR2(70)
DRIVER1_MIDDLE_NA NVARCHAR2(70)
ME
DRIVER2_REGION_ID NVARCHAR2(18)
DRIVER2_ID
NVARCHAR2(30)
ME
EQUIP1_REGION_ID
NVARCHAR2(18)
EQUIP1_TYPE_ID
NVARCHAR2(30)
EQUIP1_ID
NVARCHAR2(40)
EQUIP1_DESCRIPTION
NVARCHAR2(510
)
TION
)
EQUIP1_BULK_LOAD
NVARCHAR2(2)
EQUIP2_REGION_ID
NVARCHAR2(18)
EQUIP2_TYPE_ID
NVARCHAR2(30)
EQUIP2_ID
NVARCHAR2(40)
EQUIP2_DESCRIPTION
NVARCHAR2(510
)
TION
)
EQUIP2_BULK_LOAD
NVARCHAR2(2)
Not Comment
Null?
The unique ID for the region that controls the first
driver assigned to the route.
The employee ID for the first driver assigned to
the route.
The last name of the first driver assigned to the
route.
The first name of the first driver assigned to the
route.
The middle name of the first driver assigned to
the route.
The unique ID for the region that controls driver
2.
The employee ID for the second driver assigned
to the route.
The last name the second driver assigned to the
route.
The first name of the second driver assigned to
the route.
The middle name of the second driver assigned to
the route.
The unique ID for the region that controls the first
piece of equipment assigned to the route.
The equipment type ID for the first piece of
equipment assigned to the route.
The unique ID of the first piece of equipment
The description of the first piece of equipment
The equipment type description for the first piece
of equipment assigned to the route.
The unique ID for the region that controls the
second piece of equipment assigned to the route.
The equipment type ID for the second piece of
The unique ID of the second piece of equipment
The description of the second piece of equipment
The equipment type description for the second
Operations Guide
1209
Route Views
Column Name
Data Type
CAPACITY_SIZE1
FLOAT(126)
CAPACITY_SIZE2
FLOAT(126)
CAPACITY_SIZE3
FLOAT(126)
PLANNED_DATA_SOUR NVARCHAR2(4)
CE
ACTUAL_DATA_SOURC NVARCHAR2(4)
E
PLANNED_START_TIM DATE
E
ACTUAL_START_TIME DATE
PLANNED_COMPLETE_ DATE
TIME
ACTUAL_COMPLETE_T DATE
IME
PLANNED_DEPARTURE DATE
ACTUAL_DEPARTURE
DATE
PLANNED_ARRIVAL
DATE
ACTUAL_ARRIVAL
DATE
PLANNED_DISTANCE_T FLOAT(126)
OTAL_MI
ACTUAL_DISTANCE_T FLOAT(126)
OTAL_MI
PLANNED_DISTANCE_T NUMBER
OTAL_KM
ACTUAL_DISTANCE_T NUMBER
OTAL_KM
PLANNED_DISTANCE_S FLOAT(126)
TEM_OUT_MI
ACTUAL_DISTANCE_ST FLOAT(126)
EM_OUT_MI
PLANNED_DISTANCE_S NUMBER
TEM_OUT_KM
ACTUAL_DISTANCE_ST NUMBER
EM_OUT_KM
PLANNED_DISTANCE_S FLOAT(126)
TEM_IN_MI
ACTUAL_DISTANCE_ST FLOAT(126)
EM_IN_MI
PLANNED_DISTANCE_S NUMBER
TEM_IN_KM
ACTUAL_DISTANCE_ST NUMBER
EM_IN_KM
PLANNED_TIME_TOTA INTEGER
L
ACTUAL_TIME_TOTAL INTEGER
1210
Not Comment
Null?
The equipments total capacity measured as size
1.
2.
3.
The source for the planned data. RN = Roadnet,
MC = MobileCast
The source for the actual data. RN = Roadnet,
MC = MobileCast
The routes planned start date/time (GMT)
The routes actual start date/time (GMT)
The planned date/time (GMT) the route ends.
The actual date/time (GMT) the route ends.
The planned date/time (GMT) the route leaves
the depot.
The actual date/time (GMT) the route leaves the
depot.
The planned date/time (GMT) the driver returns
to the depot.
The actual date/time (GMT) the driver returns to
the depot.
The total planned distance, in miles.
The total actual distance, in miles.
The total planned distance, in kilometers.
The total actual distance, in kilometers.
The planned distance from the origin to the first

stop, in miles.
The actual distance from the origin to the first
stop, in miles.
stop, in kilometers.
The planned distance from the last stop to the
destination, in miles.
The actual distance from the last stop to the
destination, in kilometers.
The planned total run time for the route, in
seconds.
The actual total run time for the route, in seconds.
Route Views
Column Name
Data Type
PLANNED_TIME_STEM
_OUT
ACTUAL_TIME_STEM_
OUT
PLANNED_TIME_STEM
_IN
ACTUAL_TIME_STEM_I
N
PLANNED_TIME_PAID
INTEGER
INTEGER
ACTUAL_TIME_PAID
INTEGER
PLANNED_TIME_SERVI
CE
ACTUAL_TIME_SERVIC
E
PLANNED_TIME_TRAV
EL
ACTUAL_TIME_TRAVE
L
PLANNED_TIME_WAIT
INTEGER
INTEGER
The actual amount of drive time, in seconds.
INTEGER
ACTUAL_TIME_WAIT
INTEGER
The planned amount of time the driver spends

waiting for the stops open time or time window,
in seconds. This includes both paid and unpaid
waits.
The actual amount of time the driver spends
waiting for the stops open time or time window,
in seconds. This includes both paid and unpaid
waits.
The planned amount of time the driver spends on
break, in seconds. This includes both paid and
unpaid breaks.
The actual amount of time the driver spends on
break, in seconds. This includes both paid and
unpaid breaks.
layovers, in seconds. This includes both paid and
unpaid layovers.
layovers, in seconds. This includes both paid and
unpaid layovers.
The planned quantity of size 1 delivered.
INTEGER
INTEGER
INTEGER
INTEGER
INTEGER
PLANNED_TIME_BREA INTEGER
K
ACTUAL_TIME_BREAK INTEGER
PLANNED_TIME_LAYO INTEGER
VER
ACTUAL_TIME_LAYOV INTEGER
ER
PLANNED_QTY_DELV_ FLOAT(126)
SIZE1
SIZE2
SIZE3
ACTUAL_QTY_DELV_SI FLOAT(126)
ZE1
ZE2
ZE3
Not Comment
Null?
The planned time from the origin to the first stop,
in seconds.
The actual time from the origin to the first stop,
in seconds.
The planned time from the last stop to the
destination, in seconds.
The actual time from the last stop to the
The planned amount of time the driver was paid
for, in seconds.
The actual amount of time the driver was paid for,
in seconds.
The planned amount of time the driver spent at
stops, in seconds.
The actual amount of time the diver spent at
stops, in seconds.
The planned amount of drive time, in seconds.

The actual quantity of size 1 delivered.
Operations Guide
1211
Route Views
Column Name
Data Type
PLANNED_QTY_PICKU FLOAT(126)
P_SIZE1
P_SIZE2
P_SIZE3
ACTUAL_QTY_PICKUP_ FLOAT(126)
SIZE1
SIZE2
SIZE3
PLANNED_MAX_PERCE FLOAT(126)
NT_FULL_SIZE1
NT_FULL_SIZE2
NT_FULL_SIZE3
ACTUAL_MAX_PERCEN FLOAT(126)
T_FULL_SIZE1
T_FULL_SIZE2
T_FULL_SIZE3
PLANNED_STOP_CNT_T INTEGER
OTAL
ACTUAL_STOP_CNT_T INTEGER
OTAL
PLANNED_STOP_CNT_ INTEGER
DELVS
ACTUAL_STOP_CNT_D INTEGER
ELVS
PLANNED_STOP_CNT_P INTEGER
ICKUPS
ACTUAL_STOP_CNT_PI INTEGER
CKUPS
PLANNED_STOP_CNT_P INTEGER
ICKUPS_DELVS
ACTUAL_STOP_CNT_PI INTEGER
CKUPS_DELVS
MISSED_TW
ACTUAL_STOP_CNT_MI INTEGER
SSED_TW
OFFDAY_DELVS
ACTUAL_STOP_CNT_O INTEGER
FFDAY_DELVS
PLANNED_ORDER_CNT INTEGER
_TOTAL
ACTUAL_ORDER_CNT_ INTEGER
TOTAL
Not Comment
Null?
The planned quantity of size 1 picked up.
The actual quantity of size 1 picked up.
The highest capacity for size 1 the equipment
reached according to the planned route.
The highest capacity for size 1the equipment
reached according to the actual route.
The highest capacity for size 2the equipment
The planned total number of stops on the route.
The actual total number of stops on the route.
The planned number of stops with deliveries.
The actual number of stops with deliveries.
The planned number of stops with pickups.
The actual number of stops with pickups.
The planned number of stops that had both
The actual number of stops that had both
The planned number of stops with missed time
windows
The actual number of stops with missed time
windows
The planned number of stops with off day
deliveries
The actual number of stops with off day
deliveries
The planned total number of orders on the route.
The actual total number of orders on the route.
1212

Route Views
Column Name
Data Type
_DELVS
DELVS
_PICKUPS
PICKUPS
PLANNED_LINE_ITEM_ INTEGER
CNT_TOTAL
ACTUAL_LINE_ITEM_C INTEGER
NT_TOTAL
CNT_DELVS
NT_DELVS
CNT_PICKUPS
NT_PICKUPS
PLANNED_COST_TOTA INTEGER
L
ACTUAL_COST_TOTAL INTEGER
PLANNED_COST_OVER INTEGER
TIME
ACTUAL_COST_OVERT INTEGER
IME
ACTUAL_QTY_OVER_SI FLOAT(126)
ZE1
ZE2
ZE3
ACTUAL_QTY_SHORT_ FLOAT(126)
SIZE1
SIZE2
SIZE3
ACTUAL_QTY_DAMAG FLOAT(126)
ED_SIZE1
ED_SIZE2
Not Comment
Null?
The planned number of delivery orders on the
route.
The actual number of delivery orders on the
route.
The planned number of pickup orders on the
route.
The actual number of pickup orders on the route.
The planned total number of line items.
The actual total number of line items.
The planned number of delivery line items.
The actual number of delivery line items.
The planned number of pickup line items.
The actual number of pickup line items.
The planned total cost to run the route.
The actual total cost to run the route.
The planned amount of overtime paid to the
driver(s).
The actual amount of overtime paid to the
driver(s).
The actual quantity of size 1 that was marked
over. This information is only available if
MobileCast is used.
MobileCast is used.
MobileCast is used.
short. This information is only available if
MobileCast is used.
MobileCast is used.
MobileCast is used.
MobileCast is used.
MobileCast is used.
Operations Guide
1213
Route Views
Column Name
Data Type
ED_SIZE3
ACTUAL_STOP_CNT_C INTEGER
ANCELED
ACTUAL_STOP_CNT_D INTEGER
ELV_QTY_EXCPT
ACTUAL_STOP_CNT_E INTEGER
ARLY
ACTUAL_STOP_CNT_L INTEGER
ATE
ACTUAL_STOP_CNT_R INTEGER
OUTE_EXCPT
ACTUAL_STOPS_OUT_ NVARCHAR2(2)
OF_SEQ
Not Comment
Null?
MobileCast is used.
The actual number of stops that were marked
cancelled. This information is only available if
MobileCast is used.
The actual number of stops that had route
exceptions related to the delivery quantity. This
used.
The actual number of stops that were delivered
early.
The actual number of stops that were delivered
late.
The actual number of stops with route
exceptions. This information is only available if
MobileCast is used.
Table Summary
Table Name
RH_ROUTE_ACTUAL
RH_ROUTE_PLANNED
RH_ROUTE_BASE_VIEW
If you simply want to gather actual information about the route, you can use
RH_ROUTE_ACTUAL_VIEW. The actual information will either come from
MobileCast, or if MobileCast is not used, from an onboard computer information
imported into Roadnet or actual information manually entered into Roadnet.
Column Name
Data Type
PKEY
ORG_UNIT_ID
ORG_UNIT_NAME
REGION_ID
REGION_NAME
ROUTE_ID
ROUTE_DATE
DESCRIPTION
SCENARIO
1214
Not
Null?
INTEGER
Y
VARCHAR2(15) Y
VARCHAR2(30) Y
NVARCHAR2(18) Y
VARCHAR2(255) Y
NVARCHAR2(30) Y
DATE
Y
NVARCHAR2(128
)
NVARCHAR2(30)
Comments
The unique ID for the region.
The ID for the route.
The description for the route.

Route Views
Column Name
Data Type
Not Comments
Null?
HELPER
INTEGER
Indicates whether or not there is a helper on the
route. 0 = no helper, 1 = helper
ORIGIN_ID
NVARCHAR2(30)
The unique location ID of the origin.
ORIGIN_TYPE
NVARCHAR2(6)
The location type for the origin, usually DPT.
The name of description of the origin.
)
ORIGIN_TIME_ZONE
INTEGER
DESTINATION_ID
NVARCHAR2(30)
The unique location ID for the destination.
DESTINATION_TYPE
NVARCHAR2(6)
DPT.
The name or description of the destination.
PTION
)
ONE
DRIVER1_ID
NVARCHAR2(30)
The unique employee ID for driver 1.
ME
DRIVER2_ID
NVARCHAR2(30)
The unique employee ID for driver 2.
ME
EQUIP1_REGION_ID
NVARCHAR2(18)
The ID of the region that controls the first piece
EQUIP1_TYPE_ID
NVARCHAR2(30)
The equipment type ID for the first piece of
EQUIP1_ID
NVARCHAR2(40)
The unique ID of the first piece of equipment
)
The description for the type of the first piece of
TION
)
EQUIP1_BULK_LOAD
NVARCHAR2(2)
are using FleetLoader. (T or F).
EQUIP2_REGION_ID
NVARCHAR2(18)
The ID of the region that controls the second
EQUIP2_TYPE_ID
NVARCHAR2(30)
The equipment type ID for the second piece of
EQUIP2_ID
NVARCHAR2(40)
The unique ID for the second piece of equipment
Operations Guide
1215
Route Views
Column Name
1216
Data Type
Not Comments
Null?
The description for the second piece of
)
The description for the type of the second piece
TION
)
EQUIP2_BULK_LOAD
NVARCHAR2(2)
CAPACITY_SIZE1
FLOAT(126)
The routes total capacity when measured as size
1.
CAPACITY_SIZE2
FLOAT(126)
2.
CAPACITY_SIZE3
FLOAT(126)
3.
DATA_SOURCE
NVARCHAR2(4) Y
Indicates where the route data is from: RN =
Roadnet, MC = MobileCast
START_TIME
DATE
The actual date and time the route was started.
(GMT).
COMPLETE_TIME
DATE
The actual date and time the route was
completed. (GMT)
DEPARTURE
DATE
The actual date and time the driver left the origin.
(GMT)
ARRIVAL
DATE
The actual date and time the driver reached the
destination. (GMT)
DISTANCE_TOTAL_MI FLOAT(126)
The actual total distance, in miles.
The actual total distance, in (kilometers.
DISTANCE_STEM_OUT_ FLOAT(126)
MI
stop, in miles.
KM
DISTANCE_STEM_IN_M FLOAT(126)
I
M
TIME_TOTAL
INTEGER
The actual total run time, in seconds.
TIME_STEM_OUT
INTEGER
in seconds.
TIME_STEM_IN
INTEGER
TIME_PAID
INTEGER
The actual amount of time the driver is paid for,
in seconds.
TIME_SERVICE
INTEGER
The actual amount of time the driver spent at the
stops, in seconds.
TIME_TRAVEL
INTEGER
The actual amount of time the driver spent
driving, in seconds.
TIME_WAIT
INTEGER
The actual amount of time the driver spent on
waits, in seconds.
TIME_BREAK
INTEGER
break, in seconds.
TIME_LAYOVER
INTEGER
layovers, in seconds.
QTY_DELV_SIZE1
FLOAT(126)
Route Views
Column Name
Data Type
QTY_DELV_SIZE2
QTY_DELV_SIZE3
QTY_PICKUP_SIZE1
QTY_PICKUP_SIZE2
QTY_PICKUP_SIZE3
QTY_OVER_SIZE1
FLOAT(126)
FLOAT(126)
FLOAT(126)
FLOAT(126)
FLOAT(126)
FLOAT(126)
QTY_OVER_SIZE2
FLOAT(126)
QTY_OVER_SIZE3
FLOAT(126)
QTY_SHORT_SIZE1
FLOAT(126)
QTY_SHORT_SIZE2
FLOAT(126)
QTY_SHORT_SIZE3
FLOAT(126)
MAX_PERCENT_FULL_
SIZE1
MAX_PERCENT_FULL_
SIZE2
MAX_PERCENT_FULL_
SIZE3
STOP_COUNT_TOTAL
STOP_COUNT_DELVS
STOP_COUNT_PICKUPS
STOP_COUNT_PICKUPS
_DELVS
STOP_COUNT_MISSED_
TW
STOP_COUNT_OFFDAY
_DELVS
STOP_COUNT_CANCEL
ED
FLOAT(126)
FLOAT(126)
FLOAT(126)
INTEGER
INTEGER
INTEGER
INTEGER
INTEGER
INTEGER
INTEGER
Not Comments
Null?
The actual quantity of size 1 that was marked as
MobileCast was used.
The actual maximum amount of equipment
capacity measured as size 1 used during the route.
The actual number of stops on the route.
The actual number of stops with deliveries.
The actual number of stops with pickups.
The actual number of stops with both deliveries
and pickups.
The actual number of stops with missed time
windows.
The actual number of stops with off day
deliveries.
The actual number of stops that were canceled.
was used.
Operations Guide
1217
Route Views
Column Name
Data Type
TY_EXCPT
STOP_COUNT_EARLY INTEGER
STOP_COUNT_LATE
INTEGER
EXCPT
ORDER_COUNT_TOTAL INTEGER
ORDER_COUNT_DELVS INTEGER
ORDER_COUNT_PICKU INTEGER
PS
LINE_ITEM_COUNT_TO INTEGER
TAL
LINE_ITEM_COUNT_DE INTEGER
LVS
LINE_ITEM_COUNT_PIC INTEGER
KUPS
STOPS_OUT_OF_SEQ
NVARCHAR2(2)
COST_TOTAL
COST_OVERTIME
Not Comments
Null?
The actual number of stops with exceptions
related to quantity delivered. This information is
only available if MobileCast was used.
The actual number of stops that were early.
The actual number of stops that were late.
The actual number of stops with route
The actual total number of orders.
The actual number of orders delivered.
The actual number of orders picked up.
INTEGER
INTEGER
The actual total number of line items.

The actual number of line items delivered.
The actual number of line items picked up.
The actual total cost of running the route.
The actual amount the driver was paid in
overtime.
Table Summary
Table Name
RH_ROUTE_ACTUAL
RH_ROUTE_BASE_VIEW
RH_ROUTE_PLANNED_VIEW
If you are not using actual route information, or simply want to see the planned
information, you can use the RH_ROUTE_PLANNED_VIEW. IF MobileCast data is
available, the information will be from there. Otherwise, the information will be from
Roadnet.
Column Name
Data Type
PKEY
ORG_UNIT_ID
ORG_UNIT_NAME
REGION_ID
REGION_NAME
ROUTE_ID
ROUTE_DATE
Not
Null?
INTEGER
Y
VARCHAR2(15) Y
VARCHAR2(30) Y
NVARCHAR2(18) Y
VARCHAR2(255) Y
NVARCHAR2(30) Y
DATE
Y
Comments
The route ID.
1218

Route Views
Column Name
Data Type
DESCRIPTION
SCENARIO
HELPER
ORIGIN_ID
ORIGIN_TYPE
ORIGIN_DESCRIPTION
ORIGIN_TIME_ZONE
DESTINATION_ID
DESTINATION_TYPE
DESTINATION_DESCRI
PTION
DESTINATION_TIME_Z
ONE
DRIVER1_REGION_ID
DRIVER1_ID
DRIVER1_LAST_NAME
DRIVER1_FIRST_NAME
DRIVER1_MIDDLE_NA
ME
DRIVER2_REGION_ID
DRIVER2_ID
DRIVER2_LAST_NAME
DRIVER2_FIRST_NAME
DRIVER2_MIDDLE_NA
ME
EQUIP1_REGION_ID
Not Comments
Null?
NVARCHAR2(128
The description or name for the route.
)
NVARCHAR2(30)
The scenario the route used.
INTEGER
Indicates if there is a helper on the route or not. 0
= no helper, 1 = helper on route
NVARCHAR2(30)
The location ID of the origin.
NVARCHAR2(6)
The location type of the origin, usually DPT.
NVARCHAR2(120
The name or description of the origin.
)
INTEGER
NVARCHAR2(30)
The location ID for the destination.
NVARCHAR2(6)
DPT.
NVARCHAR2(120
The name or description of the destination.
)
INTEGER
NVARCHAR2(18)
The ID of the region that controls driver 1.
NVARCHAR2(30)
The employee ID for driver 1.
NVARCHAR2(70)
NVARCHAR2(70)
NVARCHAR2(70)
NVARCHAR2(18)
NVARCHAR2(30)
NVARCHAR2(70)
NVARCHAR2(70)
NVARCHAR2(70)
The ID of the region that controls driver 2.

NVARCHAR2(18)

The ID of the equipment type for the first piece of
The ID of the first piece of equipment assigned to
the route.
The type description of the first piece of
piece if equipment assigned to the route.
The type ID of the second piece of equipment
EQUIP1_TYPE_ID
NVARCHAR2(30)
EQUIP1_ID
NVARCHAR2(40)
EQUIP1_DESCRIPTION
NVARCHAR2(510
)
TION
)
EQUIP1_BULK_LOAD
NVARCHAR2(2)
EQUIP2_REGION_ID
NVARCHAR2(18)
EQUIP2_TYPE_ID
NVARCHAR2(30)
Operations Guide
1219
Route Views
Column Name
1220
Data Type
Not Comments
Null?
EQUIP2_ID
NVARCHAR2(40)
The ID of the second piece of equipment
)
The type description for the second piece of
TION
)
EQUIP2_BULK_LOAD
NVARCHAR2(2)
CAPACITY_SIZE1
FLOAT(126)
The routes total capacity measured as size 1.
CAPACITY_SIZE2
FLOAT(126)
CAPACITY_SIZE3
FLOAT(126)
DATA_SOURCE
NVARCHAR2(4) Y
Indicates the source of the route data. RN =
START_TIME
DATE
The planned starting date and time for the route.
(GMT)
COMPLETE_TIME
DATE
The planned finishing date and time for the route.
(GMT)
DEPARTURE
DATE
The planned date and time the route left the
origin. (GMT)
ARRIVAL
DATE
The planned date and time the route arrived at the
destination. (GMT)
DISTANCE_TOTAL_MI FLOAT(126)
The planned total distance for the route, in miles.
The planned total distance for the route, in
kilometers.
DISTANCE_STEM_OUT_ FLOAT(126)
MI
stop, in miles.
KM
DISTANCE_STEM_IN_M FLOAT(126)
I
M
TIME_TOTAL
INTEGER
The total planned time for the route, in seconds.
TIME_STEM_OUT
INTEGER
in seconds.
TIME_STEM_IN
INTEGER
TIME_PAID
INTEGER
The planned amount of time the driver is paid for,
in seconds.
TIME_SERVICE
INTEGER
servicing the stops, in seconds.
TIME_TRAVEL
INTEGER
TIME_WAIT
INTEGER
waiting at the stops to meet the open time or time
windows, in seconds.
TIME_BREAK
INTEGER
break, in seconds.
TIME_LAYOVER
INTEGER
Route Views
Column Name
Data Type
QTY_DELV_SIZE1
QTY_DELV_SIZE2
QTY_DELV_SIZE3
QTY_PICKUP_SIZE1
QTY_PICKUP_SIZE2
QTY_PICKUP_SIZE3
MAX_PERCENT_FULL_
SIZE1
MAX_PERCENT_FULL_
SIZE2
MAX_PERCENT_FULL_
SIZE3
STOP_COUNT_TOTAL
STOP_COUNT_DELVS
FLOAT(126)
FLOAT(126)
FLOAT(126)
FLOAT(126)
FLOAT(126)
FLOAT(126)
FLOAT(126)
FLOAT(126)
FLOAT(126)
INTEGER
INTEGER
STOP_COUNT_PICKUPS INTEGER
_DELVS
STOP_COUNT_MISSED_ INTEGER
TW
STOP_COUNT_OFFDAY INTEGER
_DELVS
PS
TAL
LVS
KUPS
COST_TOTAL
INTEGER
COST_OVERTIME
INTEGER
Not Comments
Null?
The amount of size 1 planned to be delivered.
The amount of size 1 planned to be picked up.
The planned maximum percentage of the routes
capacity measured as size 1.
The planned number of stops on the route.
The planned number of stops with deliveries on
the route.
The planned number of stops with pickups on the
route.
The planned number of stops with both deliveries
and pickups on the route.
The planned number of stops where the delivery
occurred outside the stops time windows on the
route.
The planned number of stops that were not
delivered on valid delivery days on the route.
The planned number of order on the route.
The planned number of delivery orders on the
route.
The planned number of pick up orders on the
route.
The planned number of line items on the route.
The planned number of delivery line items on the
route.
The planned number of pickup line items on the
route.
The planned cost for the route.
The planned amount the driver will be paid in
overtime for the route.
Table Summary
Table Name
RH_ROUTE_PLANNED
RH_ROUTE_BASE_VIEW
RH_ROUTE_BEST_DATA_VIEW
The RH_ROUTE_BEST_DATA_VIEW provides the best available data about the

routes. If available the best data is actual data from MobileCast, if that is not available
Operations Guide
1221
Route Views
then actual data from Roadnet will be used, and if no actual data is available planned data
will be used.
Column Name
Data Type
PKEY
DATA_SOURCE
INTEGER
NVARCHAR2(4)
START_TIME
DATE
COMPLETE_TIME
DATE
DEPARTURE
DATE
ARRIVAL
DATE
DISTANCE_TOTAL_MI
NUMBER
MI
KM
DISTANCE_STEM_IN_M NUMBER
I
M
TIME_TOTAL
NUMBER
TIME_STEM_OUT
NUMBER
TIME_STEM_IN
NUMBER
TIME_PAID
NUMBER
TIME_SERVICE
NUMBER
TIME_TRAVEL
NUMBER
TIME_WAIT
NUMBER
TIME_BREAK
NUMBER
TIME_LAYOVER
NUMBER
QTY_DELV_SIZE1
NUMBER
Not Comments
Null?
Y
The date and time the route started in GMT. This
will use the best available data.
The date and time the route was finished in GTM.
This will use the best available data.
The date and time the driver left the routes origin
in GMT. This will use the best available data.
The date and time the driver reached the routes
destination in GTM. This will use the best
available data.
The total route distance, in miles. This will use
the best available data.
The total route distance, in kilometers. This will
use the best available data.
The distance from the routes origin to the first
stop, in miles. This will use the best available
data.
The distance from the routes origin to the first
stop, in kilometers. This will use the best
available data.
The distance from the last stop to the routes
destination, in miles. This will use the best
available data.
The distance from the last stop to the routes
destination, in kilometers. This will use the best
available data.
The routes total run time, in seconds. This will
The time from the routes origin to the first stop,
in seconds. This will use the best available data.
The time from the last stop to the routes
destination. This will use the best available data.
The amount of time the driver is paid for, in
seconds. This will use the best available data.
The amount of time the driver spends at the stops,
in seconds. This will use the best available data.
The amount of time the driver spends driving, in
The amount of time the driver spends waiting at
the stops to meet the stops open time or time
windows. This will use the best available data.
The amount of time the driver spends on break, in
The amount of time the driver spends on
layovers. This will use the best available data.
The total quantity of size 1 delivered. This will
1222

Route Views
Column Name
Data Type
QTY_DELV_SIZE2
NUMBER
QTY_DELV_SIZE3
NUMBER
QTY_PICKUP_SIZE1
NUMBER
QTY_PICKUP_SIZE2
NUMBER
QTY_PICKUP_SIZE3
NUMBER
QTY_OVER_SIZE1
FLOAT(126)
QTY_OVER_SIZE2
FLOAT(126)
QTY_OVER_SIZE3
FLOAT(126)
QTY_SHORT_SIZE1
FLOAT(126)
QTY_SHORT_SIZE2
FLOAT(126)
QTY_SHORT_SIZE3
FLOAT(126)
SIZE1
SIZE2
SIZE3
STOP_COUNT_TOTAL
NUMBER
STOP_COUNT_DELVS
NUMBER
Not Comments
Null?
The total quantity of size 1 picked up. This will
The total quantity of size 1 marked as over. This
used.
used.
used.
The total quantity of size 1 marked as short. This
used.
used.
used.
The total quantity of size 1 marked as damaged.
is used.
is used.
is used.
The highest percentage of the capacity measured
as size 1 the route reached.
as size 2 the route reached. The best available
data will be used.
as size 3 the route reached. The best available
data will be used.
The total number of stops on the route. The best
The total number of stops with deliveries. The
Operations Guide
1223
Route Views
Column Name
Data Type
_DELVS
STOP_COUNT_MISSED_ NUMBER
TW
STOP_COUNT_OFFDAY NUMBER
_DELVS
STOP_COUNT_CANCEL INTEGER
ED
TY_EXCPT
STOP_COUNT_EARLY
INTEGER
STOP_COUNT_LATE
INTEGER
EXCPT
ORDER_COUNT_TOTAL NUMBER
ORDER_COUNT_DELVS NUMBER
ORDER_COUNT_PICKU NUMBER
PS
LINE_ITEM_COUNT_TO NUMBER
TAL
LINE_ITEM_COUNT_DE NUMBER
LVS
LINE_ITEM_COUNT_PIC NUMBER
KUPS
STOPS_OUT_OF_SEQ
NVARCHAR2(2)
COST_TOTAL
NUMBER
COST_OVERTIME
NUMBER
Not Comments
Null?
The total number of stops with pickups. The best
The total number of stops with both deliveries
and pickups. The best available data will be used.
The total number of stops where the driver
missed the stops time windows. The best
The total number of stops that were not delivered
on valid delivery days. The best available data
will be used.
The number of stops that were canceled. This
used.
The number of stops with exceptions related to
deliveries. This information is only available if
MobileCast is used.
The number of stops where the driver arrived
before the planned time.
The number of stops where the driver arrived
after the planned time.
The number of stops with route exceptions. This
used.
The total number of orders on the route. The best
The total number of delivery orders. The best
The total number of pickup orders. The best
The total number of line items. The best available
data will be used.
The total number of delivery line items. The best
The total number of line items picked up. The
A T or F indicating if the stops were not visited in
the planned order.
The total cost of running the route. The best
The amount the driver is paid in overtime. The
Table Summary
Table Name
RH_ROUTE_MASTER
RH_ROUTE_ACTUAL
RH_ROUTE_PLANNED
1224

Route Views
RH_ROUTE_BASE_VIEW
The RH_ROUTE_BASE_VIEW contains basic information about the route, such as the
addresses for the stops. This information is easily accessible through other views; this
view is simply used as a gathering place.
Column Name
Data Type
PKEY
ORG_UNIT_ID
ORG_UNIT_NAME
REGION_ID
REGION_NAME
INTEGER
NVARCHAR2(15)
NVARCHAR2(30)
NVARCHAR2(18)
NVARCHAR2(255
)
NVARCHAR2(30) Y
DATE
Y
ROUTE_ID
ROUTE_DATE
DESCRIPTION
SCENARIO
HELPER
NVARCHAR2(128
)
NVARCHAR2(30)
INTEGER
ORIGIN_ID
ORIGIN_TYPE
NVARCHAR2(30)
NVARCHAR2(6)
)
ORIGIN_TIME_ZONE
INTEGER
DESTINATION_ID
DESTINATION_TYPE
Comments
Organization unit identifier.

The unique ID for the region.
The unique ID for the route.
The description for the route.
The scenario the route uses.
route. 0 = no helper, 1 = helper
The location ID of the routes origin.
The location type for the routes origin, usually
DPT.
The name or description of the routes origin.
NVARCHAR2(18)
NVARCHAR2(30)
NVARCHAR2(70)
NVARCHAR2(70)
NVARCHAR2(70)

The location ID for the routes destination.
The location type for the routes destination,
usually DPT.
The name or description of the routes
destination.
The ID for the region that controls driver 1.
The last name of driver 1.
The first name of driver 1.
The middle name of driver 1.
NVARCHAR2(18)
NVARCHAR2(30)
NVARCHAR2(70)
NVARCHAR2(70)
NVARCHAR2(70)
The ID for the region that controls driver 2.

The last name of driver 2.
The first name of driver 2.
The middle name of driver 2.
NVARCHAR2(30)
NVARCHAR2(6)
PTION
)
ONE
DRIVER1_REGION_ID
DRIVER1_ID
DRIVER1_LAST_NAME
DRIVER1_FIRST_NAME
DRIVER1_MIDDLE_NA
ME
DRIVER2_REGION_ID
DRIVER2_ID
DRIVER2_LAST_NAME
DRIVER2_FIRST_NAME
DRIVER2_MIDDLE_NA
ME
Not
Null?
Y
Y
Y
Y
Y
Operations Guide
1225
Route Views
Column Name
Data Type
EQUIP1_REGION_ID
NVARCHAR2(18)
EQUIP1_TYPE_ID
NVARCHAR2(30)
EQUIP1_ID
NVARCHAR2(40)
EQUIP1_DESCRIPTION
NVARCHAR2(510
)
TION
)
EQUIP1_BULK_LOAD
NVARCHAR2(2)
EQUIP2_REGION_ID
NVARCHAR2(18)
EQUIP2_TYPE_ID
NVARCHAR2(30)
EQUIP2_ID
NVARCHAR2(40)
EQUIP2_DESCRIPTION
NVARCHAR2(510
)
TION
)
EQUIP2_BULK_LOAD
NVARCHAR2(2)
CAPACITY_SIZE1
CAPACITY_SIZE2
CAPACITY_SIZE3
FLOAT(126)
FLOAT(126)
FLOAT(126)
Not Comments
Null?
The ID of the equipment type of the first piece of
The ID of the first piece of equipment assigned
to the route.
The type description of the first piece of
The ID of the equipment type for the second
The ID of the second piece of equipment
The total capacity of the route measured as size 1.
Table Summary
Table Name
RH_ROUTE_MASTER
RH_LOCATION
RH_EMPLOYEE
RH_EQUIPMENT
RH_EQUIPMENT_TYPE
1226

Stop Views
Stop Views
Route History includes both route and stop views to provide easy, stable access to the
information in the database. It is strongly suggested you use the views to retrieve
information from Route History, rather that using the tables themselves. There are six
route views and four stop views you can use.
Route History includes four stop views, containing specific information about the stops.
You can gather planned or actual information, or compare the two. The stop views are:
RH_STOP_BASE_VIEW contains the basic information about the stop, such as the
location ID and address.
RH_STOP_PLANNED_VIEW contains planned information about the stops, such as
the planned quantities and times.
RH_STOP_ACTUAL_VIEW contains the actual information about the stops. If you
are using MobileCast and have actual data, you will probably want to use this view most
often.
RH_STOP_PLAN_VS_ACTUAL_VIEW contains both the planned and actual stop
information.
See Stop Views ERD for a visual display of how the stop views are related.
RH_STOP_ACTUAL_VIEW
RH_STOP_BASE_VIEW
RH_STOP_ACTUAL_VIEW
RH_STOP_PLANNED_VIEW
RH_STOP_PLAN_VS_ACTUAL_VIEW
The RH_STOP_ACTUAL_VIEW lets you gather actual information about the stops.
This information is gathered from MobileCast, or if MobileCast is not available, imported
into Roadnet from an onboard computer or entered manually. If MobileCast data is
available, it will be used.
Column Name
Data Type
PKEY
ORG_UNIT_ID
ORG_UNIT_NAME
REGION_ID
REGION_NAME
ROUTE_ID
ROUTE_DATE
ROUTE_DESCRIPTION
SCENARIO
LOCATION_ID
LOCATION_TYPE
Not
Null?
INTEGER
Y
VARCHAR2(15) Y
VARCHAR2(30) Y
NVARCHAR2(18) Y
VARCHAR2(255) Y
NVARCHAR2(30) Y
DATE
Y
NVARCHAR2(128
)
NVARCHAR2(30)
NVARCHAR2(30) Y
NVARCHAR2(6) Y
Comments
Primary key from RH_STOP_MASTER
The ID of the region.
The ID of the route the stop is on.
The description of the route.
The location ID of the stop.
The location type of the stop.
Operations Guide
1227
Stop Views
Column Name
Data Type
Not Comments
Null?
LOCATION_DESCRIPTI NVARCHAR2(120
The name or description of the location.
ON
)
STORE_NUMBER
NVARCHAR2(20)
The store number of the location.
LONGITUDE
INTEGER
The locations longitude, in millionths of
degrees.
LATITUDE
INTEGER
The locations latitude, in millionths of degrees.
POSTAL_CODE
NVARCHAR2(30)
The locations zip code.
REGION3
NVARCHAR2(40)
The locations state.
COUNTRY
NVARCHAR2(10)
The locations country.
SALESPERSON_EMPLO NVARCHAR2(30)
The employee ID of the first sales person
YEE_ID
assigned to the location.
SALESPERSON_LAST_N NVARCHAR2(70)
The last name of the first sales person assigned to
AME
the location.
SALESPERSON_FIRST_ NVARCHAR2(70)
The first name of the first sales person assigned
NAME
to the location.
The employee type of the first sales person
YEE_TYPE
SALESPERSON_REGION NVARCHAR2(18)
The ID of the region that controls the first sales
_ID
person assigned to the route.
ARRIVAL
DATE
The actual date and time the driver arrived at the
stop, (GMT).
ARRIVAL_VARIANCE INTEGER
The difference between actual and planned
arrival time, in seconds.
DEPARTURE
DATE
The actual date and time the driver left the stop
(GMT).
TIME_SERVICE
INTEGER
The actual amount of time the driver spent
servicing the stop, in seconds.
TIME_WINDOW_VARIA INTEGER
The actual difference between the actual arrival
NCE
time and the stops time window, in seconds.
OUT_OF_SEQUENCE
NVARCHAR2(2)
OFF_DAY
NVARCHAR2(2)
A T or F indicating if the stop occurred on a valid
delivery day (T = not a valid delivery day).
UNDELIVERABLE
NVARCHAR2(2)
A T or F indicating if the stop was marked as
undeliverable. This information is only available
if MobileCast is used.
QTY_DELV_SIZE1
FLOAT(126)
QTY_DELV_SIZE2
FLOAT(126)
QTY_DELV_SIZE3
FLOAT(126)
QTY_PICKUP_SIZE1
FLOAT(126)
QTY_PICKUP_SIZE2
FLOAT(126)
QTY_PICKUP_SIZE3
FLOAT(126)
QTY_OVER_SIZE1
FLOAT(126)
The actual quantity of size 1 marked as over. This
used.
QTY_OVER_SIZE2
FLOAT(126)
used.
QTY_OVER_SIZE3
FLOAT(126)
used.
1228

Stop Views
Column Name
Data Type
QTY_SHORT_SIZE1
QTY_SHORT_SIZE2
QTY_SHORT_SIZE3
QTY_DAMAGED_SIZE1
QTY_DAMAGED_SIZE2
QTY_DAMAGED_SIZE3
COST_TRANSPORTATI
ON
COST_NON_TRANSPOR
TATION
REVENUE
CONSIGNEE
SIGNATURE_DATA
Not Comments
Null?
FLOAT(126)
The actual quantity of size 1 marked as short.
is used.
FLOAT(126)
is used.
FLOAT(126)
is used.
FLOAT(126)
The actual quantity of size 1 marked as damaged.
is used.
FLOAT(126)
is used.
FLOAT(126)
is used.
INTEGER
The actual transportation cost of the stop. This
includes all equipment costs.
INTEGER
The actual non-transportation cost of the stop.
This includes all location and driver costs.
INTEGER
This information is not currently available.
NVARCHAR2(128
The name of the person who accepted the
)
delivery at the stop. This information is only
available if MobileCast is being used.
BLOB
The image of the person who accepted the
delivery at the stop. This information is only
Table Summary
Table Name
RH_STOP_ACTUAL
RH_STOP_SIGNATURE
RH_STOP_BASE_VIEW
If you do not have actual data available, or are interested in the planned data, use the
RH_STOP_PLANNED_VIEW.
Column Name
Data Type
PKEY
ORG_UNIT_ID
ORG_UNIT_NAME
REGION_ID
REGION_NAME
Not
Null?
INTEGER
Y
VARCHAR2(15) Y
VARCHAR2(30) Y
NVARCHAR2(18) Y
VARCHAR2(255) Y
Comments
Operations Guide
1229
Stop Views
Column Name
Data Type
Not Comments
Null?
ROUTE_ID
NVARCHAR2(30) Y
ROUTE_DATE
DATE
Y
ROUTE_DESCRIPTION NVARCHAR2(128
)
SCENARIO
NVARCHAR2(30)
LOCATION_ID
NVARCHAR2(30) Y
LOCATION_TYPE
NVARCHAR2(6) Y
The location type for the stop.
The locations name or description.
ON
)
STORE_NUMBER
NVARCHAR2(20)
The locations store number.
LONGITUDE
INTEGER
The locations longitude, in millionths of a
degree.
LATITUDE
INTEGER
The locations latitude, in millionths of a degree.
POSTAL_CODE
NVARCHAR2(30)
REGION3
NVARCHAR2(40)
The locations state.
COUNTRY
NVARCHAR2(10)
The locations county.
YEE_ID
AME
the location.
NAME
to the location.
YEE_TYPE
_ID
person assigned to the location.
ARRIVAL
DATE
The date and time the driver is planned to arrive
at the stop (GMT).
DEPARTURE
DATE
The date and time the driver is planned to leave
the stop (GMT).
TIME_SERVICE
INTEGER
The amount of time the driver is planned to stay
at the stop, in seconds.
The difference between the planned arrival time
NCE
and the stops time window, in seconds.
OFF_DAY
NVARCHAR2(2)
A T or F indicating if the stop is planned for a
valid delivery day (T = not a valid delivery day).
QTY_DELV_SIZE1
FLOAT(126)
QTY_DELV_SIZE2
FLOAT(126)
QTY_DELV_SIZE3
FLOAT(126)
QTY_PICKUP_SIZE1
FLOAT(126)
QTY_PICKUP_SIZE2
FLOAT(126)
QTY_PICKUP_SIZE3
FLOAT(126)
COST_TRANSPORTATI NUMBER
The planned transportation cost of stop. This
ON
includes the equipment costs.
COST_NON_TRANSPOR INTEGER
The planned non-transportation cost of the stop.
TATION
This includes the driver and location costs.
REVENUE
INTEGER
1230

Stop Views
Table Summary
Table Name
RH_STOP_PLANNED
RH_STOP_BASE_VIEW
The RH_STOP_PLAN_VS_ACTUAL_VIEW lets you easily compare the planned stops

to how the stops actually occurred. If MobileCast data is available it will be used;
otherwise data from Roadnet will be used.
Column Name
Date Type
PKEY
ORG_UNIT_ID
ORG_UNIT_NAME
REGION_ID
REGION_NAME
ROUTE_ID
ROUTE_DATE
Not
Null?
INTEGER
Y
VARCHAR2(15) Y
VARCHAR2(30) Y
NVARCHAR2(18) Y
VARCHAR2(255) Y
NVARCHAR2(30) Y
DATE
Y
ROUTE_DESCRIPTION
NVARCHAR2(128
)
SCENARIO
NVARCHAR2(30)
LOCATION_ID
NVARCHAR2(30) Y
LOCATION_TYPE
NVARCHAR2(6) Y
ON
)
STORE_NUMBER
NVARCHAR2(20)
LONGITUDE
INTEGER
LATITUDE
INTEGER
POSTAL_CODE
NVARCHAR2(30)
REGION3
NVARCHAR2(40)
COUNTRY
NVARCHAR2(10)
YEE_ID
AME
NAME
YEE_TYPE
_ID
PLANNED_ARRIVAL
DATE
Comments
The description of the route the stop is on.
The location type for the stop.
The name or description of the location.
The store number of the location.
degrees.
The state the location is in.
The country the location is in.
the location.
to the location.
The planned date and time the driver should
arrive at the stop, (GMT).
Operations Guide
1231
Stop Views
Column Name
Date Type
ACTUAL_ARRIVAL
DATE
ACTUAL_DEPARTURE
DATE
PLANED_DEPARTURE
DATE
PLANNED_TIME_SERVI INTEGER
CE
ACTUAL_TIME_SERVIC INTEGER
E
PLANNED_TIME_WIND INTEGER
OW_VARIANCE
ACTUAL_TIME_WINDO INTEGER
W_VARIANCE
PLANNED_OFF_DAY
NVARCHAR2(2)
ACTUAL_OFF_DAY
NVARCHAR2(2)
SIZE1
SIZE2
SIZE3
ZE1
ZE2
ZE3
P_SIZE1
P_SIZE2
P_SIZE3
SIZE1
SIZE2
SIZE3
PLANNED_COST_TRAN NUMBER
SPORT
ACTUAL_COST_TRANS INTEGER
PORT
PLANNED_COST_NON_ INTEGER
TRANSPORT
Not Comments
Null?
stop, (GMT).
The actual date and time the driver left the stop,
(GMT).
The planned date and time the driver should leave
the stop (GMT).
The planned amount of time the driver spends at
the stop, in seconds.
stop, in seconds.
The difference between the planned time the
driver arrived at the stop and the stops time
window, in seconds.
The difference between the drivers actual arrival
time and the stops time window, in seconds.
A T or F indicating if the stop is planned for a
valid delivery day or not (T =not a valid delivery
day).
A T or F indicating if the stop was actually
delivered on a valid delivery day or not (T = not
a valid delivery day).
The planned amount of size 1 to be delivered.
The actual amount of size 1 delivered.
The planned amount of size 1 picked up.
The actual amount of size 1 picked up.
The planned transportation cost of the stop. This
The actual transportation cost of the stop. This
The planned non-transportation cost of the stop.
This includes the location and driver costs.
1232

Stop Views
Column Name
Date Type
ACTUAL_COST_NON_T
RANSPORT
PLANNED_REVENUE
ACTUAL_REVENUE
ACTUAL_ARRIVAL_VA
RIANCE
INTEGER
INTEGER
INTEGER
INTEGER
ACTUAL_OUT_OF_SEQ NVARCHAR2(2)
UENCE
ACTUAL_UNDELIVERA NVARCHAR2(2)
BLE
ZE1
ZE2
ZE3
SIZE1
SIZE2
SIZE3
ED_SIZE1
ED_SIZE2
ED_SIZE3
CONSIGNEE
NVARCHAR2(128
)
SIGNATURE_DATA
BLOB
Not Comments
Null?
The actual non-transportation cost of the stop.
This includes the location and driver costs.
The difference between the time the driver was
planned to arrive and the stop and the actual
arrival time, in seconds.
A T or F indicating if the stop was marked
undeliverable. (T =stop was undeliverable) This
used.
The actual amount if size 1 marked as over. This
used.
The actual amount of size 2 marked as over. This
used.
The actual amount of size 3 marked as over.
is used.
The actual amount of size 1 marked as short. This
used.
used.
used.
The actual amount of size 1 marked as damaged.
is used.
is used.
The actual amount of size3 marked as damaged.
is used.
The name of the person who accepted the
delivery. This information is only available if
MobileCast is used.
An image of the signature of the person who
accepted the delivery. This information is only
Operations Guide
1233
Stop Views
Table Summary
Table Name
RH_STOP_SIGNATURE
RH_STOP_BASE_VIEW
RH_STOP_ACTUAL_VIEW
RH_STOP_BASE_VIEW
The RH_STOP_BASE_VIEW contains some basic information about the stops, such as
the address. This information is available through the other views, this view is simply
used as a gathering place.
Column Name
Data Type
PKEY
ORG_UNIT_ID
ORG_UNIT_NAME
REGION_ID
REGION_NAME
ROUTE_ID
ROUTE_DATE
Not
Null?
INTEGER
Y
VARCHAR2(15) Y
VARCHAR2(30) Y
NVARCHAR2(18) Y
NVARCHAR2(255 Y
)
NVARCHAR2(30) Y
DATE
Y
ROUTE_DESCRIPTION
NVARCHAR2(128
)
SCENARIO
NVARCHAR2(30)
LOCATION_ID
NVARCHAR2(30) Y
LOCATION_TYPE
NVARCHAR2(6) Y
ON
)
STORE_NUMBER
NVARCHAR2(20)
LONGITUDE
INTEGER
LATITUDE
POSTAL_CODE
REGION3
COUNTRY
SALESPERSON_EMPLO
YEE_ID
SALESPERSON_LAST_N
AME
SALESPERSON_FIRST_
NAME
SALESPERSON_EMPLO
YEE_TYPE
INTEGER
NVARCHAR2(30)
NVARCHAR2(40)
NVARCHAR2(10)
NVARCHAR2(30)
NVARCHAR2(70)
NVARCHAR2(70)
NVARCHAR2(6)
Comments
The ID of the organization unit.
The description of the route the stop is on.
The location ID of the stop.
The location type of the stop.
The name or description of the stop.
The store number of the stop.
degrees.
The employee ID of the first salesperson assigned
to the location.
the route.
to the route.
The employee type of the first salesperson
1234

Stop Views
Column Name
Data Type
Not Comments
Null?
_ID
Table Summary
Table Name
RH_STOP_MASTER
RH_ROUTE_MASTER
RH_LOCATION
RH_EMPLOYEE
Operations Guide
1235
Route History Tables

The following tables are available in Route History. You will usually be able to gather the
information you need directly from the views, but if you need to use the tables to gather
information or create your own views, they are described below.
The following tables are available in Route History:
Employee Table
Equipment Table
Equipment Type Table
Location Table
Organization Unit Table
Region Table
Route Actual Table
Route Planned Table
Route Master Table
Stop Actual Table
Stop Planned Table
Stop Master Table
Stop Signature Table
See Route History Tables ERD for a display of how the tables are related.
RH_EMPLOYEE Table
The RH_EMPLOYEE table contains the basic information about the employees, such as
the employee ID and name.
Column Name
Data Type
Comments
PKEY
REGION_ID
EMPLOYEE_ID
LAST_NAME
FIRST_NAME
MIDDLE_NAME
TYPE
Not
Null?
INTEGER
Y
NVARCHAR2(9) Y
NVARCHAR2(15) Y
NVARCHAR2(35)
NVARCHAR2(35)
NVARCHAR2(35)
NVARCHAR2(3)
USER_MODIFIED
DATE_MODIFIED
READ_ONLY
NVARCHAR2(12)
DATE
INTEGER
Primary key from sequence generator

The unique ID of the employee.
Employees last name.
Employees first name.
Employees middle name,
The ID for the employee type (ex. DRV for
driver).
User who last modified
Date of last modification
0 = unrestricted, 1 = modify only, 2 = read only
1236

Index Summary
Name
Columns
Unique?
PK_RH_EMPLOYEE
PKEY
Yes
RH_EQUIPMENT Table
The RH_EQUIPMENT table contains the basic information about the equipment used to
run the routes.
Column Name
Data Type
PKEY
REGION_ID
EQUIPMENT_TYPE_ID
EQUIPMENT_ID
DESCRIPTION
USER_MODIFIED
DATE_MODIFIED
READ_ONLY
Not
Null?
INTEGER
Y
NVARCHAR2(9) Y
NVARCHAR2(15) Y
NVARCHAR2(20) Y
NVARCHAR2(255
)
NVARCHAR2(12)
DATE
INTEGER
Comments
The ID for the region.
The unique ID for the equipment type (ex. 16
bay).
The unique ID for this piece of equipment.
The description of the equipment.
Index Summary
Name
Columns
Unique?
PK_RH_EQUIPMENT
PKEY
Yes
RH_EQUIPMENT_TYPE Table
The RH_EQUIPMENT_TYPE table contains basic information about the types of

equipment used.
Column Name
Data Type
BULK_LOAD
Not
Null?
INTEGER
Y
NVARCHAR2(9) Y
NVARCHAR2(15) Y
NVARCHAR2(255
)
NVARCHAR2(1)
USER_MODIFIED
DATE_MODIFIED
READ_ONLY
NVARCHAR2(12)
DATE
INTEGER
PKEY
REGION_ID
EQUIPMENT_TYPE_ID
DESCRIPTION
Comments
The unique ID for the equipment type.
The description of the equipment type.
A T or F indicating if the truck can carry a bulk
load. This information is only pertinent if you are
using FleetLoader.
Operations Guide
1237
Index Summary
Name
Columns
Unique?
PK_RH_EQUIPMENT_TYPE
PKEY
Yes
RH_LOCATION Table
The RH_LOCATION table contains basic information about the customer locations, such
as address information.
Column Name
Data Type
PKEY
REGION_ID
LOCATION_ID
LOCATION_TYPE
Not
Null?
INTEGER
Y
NVARCHAR2(9) Y
NVARCHAR2(15) Y
NVARCHAR2(3) Y
DESCRIPTION
STORE_NUMBER
POSTAL_CODE
NVARCHAR2(60)
NVARCHAR2(10)
NVARCHAR2(15)
REGION3
COUNTRY
LONGITUDE
NVARCHAR2(20)
NVARCHAR2(5)
INTEGER
LATITUDE
INTEGER
TIME_ZONE
INTEGER
ACCOUNT_TYPE_ID
NVARCHAR2(5)
SERVICE_TIME_TYPE_I NVARCHAR2(5)
D
DELIVERY_DAYS
NVARCHAR2(7)
SALESMAN_ID
NVARCHAR2(15)
SALESMAN_REGION_ID NVARCHAR2(9)
USER_MODIFIED
DATE_MODIFIED
READ_ONLY
NVARCHAR2(12)
DATE
INTEGER
Comments
The unique ID of the location.
The type for the location, such as DPT for depot
or SIT for customer location.
The name of the location.
The store number.
The zip code or postal code for the locations
delivery address.
The longitude of the location, in millionths of
degrees.
The latitude of the location, in millionths of
degrees.
The account type assigned to the location.
The service time type assigned to the location.
The service time type is used to calculate how
long the driver needs to deliver product.
The valid delivery days for the location. The
options are UMTWRFS.
Index Summary
Name
Columns
Unique?
PK_RH_LOCATION
PKEY
Yes
1238

RH_ORGANIZATION _UNIT Table
The RH_ORGANIZATION_UNIT table contains basic information about the

organization units, such as name information.
Column Name
Data Type
ORG_UNIT_ID
NAME
USER_MODIFIED
DATE_MODIFIED
READ_ONLY
Not
Null?
NVARCHAR2(15) Y
NVARCHAR2(30) Y
NVARCHAR2(12) Y
DATE
Y
NUMBER
Comments
Organization unit identifier
The name of the organization unit
Timestamp of last modification
0 = unrestricted, 1 = read only
Index Summary
Name
Columns
Unique?
PK_RH_ORGANIZATION_UNIT
ORG_UNIT_ID
RH_REGION Table
The RH_REGION table contains basic information about the region, such as the ID.
Column Name
Data Type
Not Comments
Null?
Y
Region identifier
Timestamp of last history update
REGION_ID
NVARCHAR2(9)
LAST_HISTORY_UPDAT DATE
E
USER_MODIFIED
NVARCHAR2(12)
DATE_MODIFIED
DATE
READ_ONLY
NUMBER
ORG_UNIT_ID
NVARCHAR2(15) Y

Organization unit identifier
Index Summary
Name
Columns
Unique?
PK_RH_REGION
REGION_ID
Yes
RH_ROUTE_ACTUAL Table
The route tables store data about the routes. This information can also be gathered using
the route views. The RH_ROUTE_ACTUAL table stores actual route information. If
MobileCast data is available it will be used; otherwise information imported into Roadnet
from an onboard computer or entered manually will be used.
Column Name
Data Type
PKEY
INTEGER
DATA_SOURCE
NVARCHAR2(2)
START_TIME
DATE
Not Comment
Null
Y
Primary Key. Matches PKEY in
RH_ROUTE_MASTER table.
Y
Indicates the source of the data. RN = Roadnet,
MC = MobileCast
The actual date and time the route started (GMT).
Operations Guide
1239
Column Name
1240
Data Type
Not Comment
Null
COMPLETE_TIME
DATE
The actual date and time the route was finished
(GMT).
DEPARTURE
DATE
The actual date and time the driver departed the
routes origin (GMT).
ARRIVAL
DATE
The actual date and time the driver reached the
stops destination (GMT).
DISTANCE_TOTAL
FLOAT(126)
The actual total distance for the route, in miles.
DISTANCE_STEM_OUT FLOAT(126)
stop, in miles.
DISTANCE_STEM_IN
FLOAT(126)
TIME_TOTAL
INTEGER
The actual time of the route, in seconds.
TIME_STEM_OUT
INTEGER
in seconds.
TIME_STEM_IN
INTEGER
TIME_PAID
INTEGER
The actual amount of time the driver is paid for,
in seconds.
TIME_SERVICE
INTEGER
The actual amount of time the driver spends at the
stops, in seconds.
TIME_TRAVEL
INTEGER
TIME_WAIT
INTEGER
waiting to make the stops time windows or open
times, in seconds.
TIME_BREAK
INTEGER
break, in seconds.
TIME_LAYOVER
INTEGER
TIME_WBL_SUM
INTEGER
breaks, waits, and layovers, in seconds.
QTY_DELV_SIZE1
FLOAT(126)
QTY_DELV_SIZE2
FLOAT(126)
QTY_DELV_SIZE3
FLOAT(126)
QTY_PICKUP_SIZE1
FLOAT(126)
QTY_PICKUP_SIZE2
FLOAT(126)
QTY_PICKUP_SIZE3
FLOAT(126)
QTY_OVER_SIZE1
FLOAT(126)
The actual quantity of size1 marked as over. This
used.
QTY_OVER_SIZE2
FLOAT(126)
used.
QTY_OVER_SIZE3
FLOAT(126)
used.
QTY_SHORT_SIZE1
FLOAT(126)
is used.
QTY_SHORT_SIZE2
FLOAT(126)
is used.
Column Name
Data Type
QTY_SHORT_SIZE3
FLOAT(126)
MAX_PERCENT_FULL_S
IZE1
MAX_PERCENT_FULL_S
IZE2
MAX_PERCENT_FULL_S
IZE3
STOP_COUNT_TOTAL
STOP_COUNT_DELVS
FLOAT(126)
FLOAT(126)
FLOAT(126)
INTEGER
INTEGER
STOP_COUNT_PICKUPS_ INTEGER
DELVS
STOP_COUNT_MISSED_ INTEGER
TW
STOP_COUNT_OFFDAY_ INTEGER
DELVS
STOP_COUNT_CANCELE INTEGER
D
STOP_COUNT_DELV_QT INTEGER
Y_EXCPT
STOP_COUNT_EARLY
INTEGER
STOP_COUNT_LATE
INTEGER
STOP_COUNT_ROUTE_E INTEGER
XCPT
ORDER_COUNT_PICKUP INTEGER
S
TAL
LVS
Not Comment
Null
is used.
is used.
is used.
is used.
The actual maximum percentage of the total
capacity measured as size 1 the route reaches.
capacity measured as size 2 the route reaches.
capacity measured as size 3 the route reached.
The actual number of stops on the route.
The actual number of stops on the route that
received deliveries.
The actual number of stops on the route that had
pick ups.
The actual number of stops on the route that had
both deliveries and pick ups.
The actual number of stops where the driver did
not make the preferred delivery time, or time
windows.
The actual number of stops that for which the day
was not a valid delivery day.
The actual number of stops that were cancelled.
is used.
The actual number of stops that had quantity type
MobileCast is used.
The actual number of stops where the driver
arrived early.
The actual number of stops where the driver
arrived late.
The actual number of stops that generated route
MobileCast is used.
The actual number of orders on the route.
The actual number of delivery orders on the
route.
The actual number of pickup orders on the route.
The actual number of line items on the route.
The actual number of line items that were
delivered on the route.
Operations Guide
1241
Column Name
Data Type
Not Comment
Null
The actual number of line items that were picked
KUPS
up on the route.
STOPS_OUT_OF_SEQ
NVARCHAR2(1)
COST_TOTAL
INTEGER
The actual cost of the route, including all driver,
equipment, and location costs.
COST_OVERTIME
INTEGER
The actual amount of overtime paid to the driver.
USER_MODIFIED
NVARCHAR2(12)
DATE_MODIFIED
DATE
READ_ONLY
INTEGER
Index Summary
Name
Columns
Unique?
PK_RH_ROUTE_ACTUAL
PKEY
Yes
RH_ROUTE_PLANNED Table
The route tables store data about the routes. This information can also be gathered using
the route views.The RH_ROUTE_PLANNED table contains planned information about
the routes. If MobileCast data is available it will be used, otherwise Roadnet data will be
used.
Column Name
Data Type
PKEY
INTEGER
DATA_SOURCE
NVARCHAR2(2)
START_TIME
DATE
COMPLETE_TIME
DATE
DEPARTURE
DATE
ARRIVAL
DATE
DISTANCE_TOTAL
FLOAT(126)
DISTANCE_STEM_OUT FLOAT(126)
DISTANCE_STEM_IN
FLOAT(126)
TIME_TOTAL
TIME_STEM_OUT
INTEGER
INTEGER
TIME_STEM_IN
INTEGER
TIME_PAID
INTEGER
Not Comments
Null?
Y
Primary key. Matches PKEY in
RH_ROUTE_MASTER table
Y
The planned date and time the route started
(GMT).
The planned date and time the route ended
(GMT).
The planned date and time the driver leaves the
origin (GMT).
The planned date and time the driver reaches the
routes destination (GTM).
The planned distance, in miles.
stop, in miles.
The planned time of the route, in seconds.
in seconds.
The planned amount of time the driver is paid for,
in seconds.
1242

Column Name
Data Type
TIME_SERVICE
INTEGER
TIME_TRAVEL
INTEGER
TIME_WAIT
INTEGER
TIME_BREAK
INTEGER
TIME_LAYOVER
INTEGER
TIME_WBL_SUM
INTEGER
QTY_DELV_SIZE1
QTY_DELV_SIZE2
QTY_DELV_SIZE3
QTY_PICKUP_SIZE1
QTY_PICKUP_SIZE2
QTY_PICKUP_SIZE3
MAX_PERCENT_FULL_
SIZE1
MAX_PERCENT_FULL_
SIZE2
MAX_PERCENT_FULL_
SIZE3
STOP_COUNT_TOTAL
STOP_COUNT_DELVS
FLOAT(126)
FLOAT(126)
FLOAT(126)
FLOAT(126)
FLOAT(126)
FLOAT(126)
FLOAT(126)
FLOAT(126)
FLOAT(126)
INTEGER
INTEGER
STOP_COUNT_PICKUPS
_DELVS
STOP_COUNT_MISSED_
TW
STOP_COUNT_OFFDAY
_DELVS
ORDER_COUNT_TOTAL
ORDER_COUNT_DELVS
INTEGER
INTEGER
INTEGER
INTEGER
INTEGER
PS
TAL
LVS
KUPS
COST_TOTAL
INTEGER
COST_OVERTIME
INTEGER
USER_MODIFIED
DATE_MODIFIED
NVARCHAR2(12)
DATE
Not Comments
Null?
the stops, in seconds.
waiting to meet the stops open time or time
windows, in seconds.
break, in seconds.
breaks, waits, and layovers, in seconds.
The planned amount of size 1 delivered.
The planned maximum percentage of capacity
measured as size 1 for the route.
The planned number of stops on the route.
The planned number of stops on the route with
deliveries.
pick ups.
both deliveries and pick ups.
The planned number of stops where the time
window is missed.
The planned number of stops being visited on a
day that is not a valid delivery day.
The planned number of orders on the route.
The planned number of orders that include
deliveries.
The planned number of orders that include
pickups.
The planned number of line items on the route.
The planned number of line items that are
deliveries.
The planned number of line items that are pick
ups.
The planned costs of the route.
The planned amount of overtime the driver will
be paid.
Operations Guide
1243
Column Name
Data Type
READ_ONLY
INTEGER
Not Comments
Null?
Index Summary
Name
Columns
Unique?
PK_RH_ROUTE_PLANNED
PKEY
Yes
RH_ROUTE_MASTER Table
The route tables stores very basic information about the routes that does not change; no
planned or actual type information is stored in this table. This table is simply used as a
gathering point, the information contained here can be accessed from other tables or route
views. The RH_ROUTE_MASTER table contains very basic information about the route.
Column Name
Data Type
Not
Null?
INTEGER
Y
NVARCHAR2(9) Y
NVARCHAR2(15) Y
DATE
Y
Comments
DESCRIPTION
SCENARIO
RH_LOCATION_ORIGIN
_PKEY
RH_LOCATION_DEST_P
KEY
RH_EMPLOYEE_DRV1_
PKEY
RH_EMPLOYEE_DRV2_
PKEY
RH_EQUIPMENT_EQUIP
1_PKEY
RH_EQUIPMENT_EQUIP
2_PKEY
RH_EQUIPTYPE_EQUIP
1_PKEY
RH_EQUIPTYPE_EQUIP
2_PKEY
CAPACITY_SIZE1
CAPACITY_SIZE2
CAPACITY_SIZE3
HELPER
NVARCHAR2(64)
NVARCHAR2(15)
INTEGER
Primary Key from sequence generator

The unique ID of the route.
Foreign key of location record for origin
INTEGER
Foreign key of location record for destination
INTEGER
Foreign key of employee record for driver 1
INTEGER
Foreign key of employee record for driver 2
INTEGER
Foreign key of equipment record for equipment 1
INTEGER
Foreign key of equipment record for equipment 2
INTEGER
USER_MODIFIED
DATE_MODIFIED
READ_ONLY
ORG_UNIT_ID
NVARCHAR2(12)
DATE
INTEGER
NVARCHAR2(15) Y
Foreign key of equipment type record for

equipment 1
Foreign key of equipment type record for
equipment 2
The routes capacity measured as size 1.
route. 0 = no helper on route, 1 = helper on route
The organization unit identifier.
PKEY
REGION_ID
ROUTE_ID
ROUTE_DATE
INTEGER
FLOAT(126)
FLOAT(126)
FLOAT(126)
INTEGER
1244

Index Summary
Name
Columns
Unique?
BC_RH_ROUTE
ROUTE_ID, ROUTE_DATE,
REGION_ID
Yes
IX_RH_ROUTE_MASTER_DEST_PKEY
RH_LOCATION_DEST_PKEY
No
IX_RH_ROUTE_MASTER_DRV1_PKE
Y
RH_EMPLOYEE_DRV1_PKEY
No
IX_RH_ROUTE_MASTER_DRV2_PKE
Y
No
IX_RH_ROUTE_MASTER_EQTYPE1_P
KEY
RH_EQUIPTYPE_EQUIP1_PKEY
No
IX_RH_ROUTE_MASTER_EQTYPE2_P
KEY
No
IX_RH_ROUTE_MASTER_EQUIP1_PK
EY
RH_EQUIPMENT_EQUIP1_PKEY
No
IX_RH_ROUTE_MASTER_EQUIP2_PK
EY
No
IX_RH_ROUTE_MASTER_ORIGIN_PK
EY
RH_LOCATION_ORIGIN_PKEY
No
PK_RH_ROUTE_MASTER
PKEY
Yes
RH_STOP_ACTUAL Table
The data stored in the stops tables can also be accessed through the stop views. The
RH_STOP_ACTUAL table contains actual information about the stops. This data will
come from MobileCast if available, otherwise it will come from onboard information
imported into Roadnet or entered manually.
Column Name
Data Type
PKEY
INTEGER
RH_ROUTE_PKEY
ARRIVAL
INTEGER
DATE
ARRIVAL_VARIANCE
INTEGER
DEPARTURE
DATE
NCE
TIME_SERVICE
INTEGER
Not Comments
Null?
Y
Primary key (matches primary key in
RH_STOP_MASTER)
Primary key of route containing this stop
stop (GMT).
The actual amount of time (late/early) the driver
missed the planned arrival time, in minutes.
The actual date and time the driver left the stop
(GMT).
The actual amount of time the driver missed the
time window, in minutes.
stop.
Operations Guide
1245
Column Name
Data Type
OUT_OF_SEQUENCE
NVARCHAR2(1)
OFF_DAY
NVARCHAR2(1)
UNDELIVERABLE
NVARCHAR2(1)
QTY_DELV_SIZE1
QTY_DELV_SIZE2
QTY_DELV_SIZE3
QTY_PICKUP_SIZE1
QTY_PICKUP_SIZE2
QTY_PICKUP_SIZE3
QTY_OVER_SIZE1
FLOAT(126)
FLOAT(126)
FLOAT(126)
FLOAT(126)
FLOAT(126)
FLOAT(126)
FLOAT(126)
QTY_OVER_SIZE2
FLOAT(126)
QTY_OVER_SIZE3
FLOAT(126)
QTY_SHORT_SIZE1
FLOAT(126)
QTY_SHORT_SIZE2
FLOAT(126)
QTY_SHORT_SIZE3
FLOAT(126)
COST_TRANSPORTATI
ON
COST_NON_TRANSPOR
TATION
REVENUE
USER_MODIFIED
DATE_MODIFIED
READ_ONLY
INTEGER
INTEGER
INTEGER
NVARCHAR2(12)
DATE
INTEGER
Not Comments
Null?
Indicates if the stop was delivered on a day that
was not a valid delivery day. T = off day delivery
Indicates if the stop was marked undeliverable.
was used. T = undeliverable
used.
used.
used.
used.
used.
used.
is used.
is used.
is used.
The actual equipment cost for the stop.
The actual non-equipment cost for the stop, such
as the employee and location costs.
1246

Index Summary
Name
Columns
Unique?
PK_RH_STOP_ACTUAL
PKEY
Yes
RH_STOP_ACTUAL_ROUTE_PKEY
RH_ROUTE_PKEY
No
RH_STOP_PLANNED Table
The data stored in the stops tables can also be accessed through the stop views.The
RH_STOP_PLANNED table contains planned information about the stops. If it is
available, MobileCast data will be used; otherwise Roadnet data will be used.
Column Name
Data Type
PKEY
INTEGER
RH_ROUTE_PKEY
ARRIVAL
INTEGER
DATE
TIME_SERVICE
INTEGER
DEPARTURE
DATE
Not Comments
Null?
Y
Primary key (matches primary key in
RH_STOP_MASTER)
The planned arrival date and time for the stop
(GTM).
the stop, in seconds.
The planned departure date and time the driver
should leave the stop (GMT).
The difference between the stops time window
and the planned arrival time, in minutes.
Indicates if the stop is planned to be delivered on
a day that is not a valid delivery day. T = off day
delivery
The planned equipment cost for the stop.
NCE
OFF_DAY
NVARCHAR2(1)
QTY_DELV_SIZE1
QTY_DELV_SIZE2
QTY_DELV_SIZE3
QTY_PICKUP_SIZE1
QTY_PICKUP_SIZE2
QTY_PICKUP_SIZE3
COST_TRANSPORTATI
ON
COST_NON_TRANSPOR
TATION
REVENUE
USER_MODIFIED
DATE_MODIFIED
READ_ONLY
FLOAT(126)
FLOAT(126)
FLOAT(126)
FLOAT(126)
FLOAT(126)
FLOAT(126)
INTEGER
INTEGER
INTEGER
NVARCHAR2(12)
DATE
INTEGER
The planned non-equipment cost for the stop,

such as driver and location cost.
Index Summary
Name
Columns
Unique?
PK_RH_STOP_PLANNED
PKEY
Yes
PH_STOP_PLANNED_ROUTE_PKEY
RH_ROUTE_PKEY
No
Operations Guide
1247
RH_STOP_MASTER Table
The data stored in the stops tables can also be accessed through the stop views.The
RH_STOP_MASTER table contains very basic information about the stops.
Column Name
Data Type
Not Comments
Null?
PKEY
INTEGER
Y
Primary key
REGION_ID
NVARCHAR2(9) Y
RH_ROUTE_PKEY
INTEGER
RH_LOCATION_PKEY INTEGER
Primary key of location of this stop
RH_EMPLOYEE_SALES INTEGER
Primary key of first salesperson associated with
_PKEY
stop
BULK_SERVICE
NVARCHAR2(1)
Indicates if the stop uses bulk service time. T =
uses bulk service time
USER_MODIFIED
NVARCHAR2(12)
DATE_MODIFIED
DATE
READ_ONLY
INTEGER
ORG_UNIT_ID
NVARCHAR2(15) Y
The organization unit identifier.
Index Summary
Name
Columns
Unique?
IX_RH_STOP_MASTER_REGION_ID
REGION_ID
No
IX_RH_STOP_MASTER_ROUTE_PKEY
RH_ROUTE_PKEY
No
PK_RH_STOP_MASTER
PKEY
Yes
RH_STOP_MASTER_LOCATION_PKE
Y
RH_LOCATION_PKEY
No
RH_STOP_SIGNATURE Table
The RH_STOP_SIGNATURE table contains information gathered in MobileCast about

customers who accepted deliveries, such as the consignee and an image of the consignees
signature. This information is only available if MobileCast is used.
Column Name
Data Type
PKEY
RH_ROUTE_PKEY
CONSIGNEE
DATE_MODIFIED
USER_MODIFIED
READ_ONLY
SIGNATURE_DATA
Not Comments
Null?
INTEGER
Y
Primary key of stop in RH_MASTER_STOP
table
INTEGER
NVARCHAR2(64)
The name of the person who signed to accept the
delivery.
DATE
NVARCHAR2(12)
INTEGER
BLOB
Consignee signature image for stop
1248

Index Summary
Name
Columns
Unique?
PK_RH_STOP_SIGNATURE
PKEY
Yes
RH_STOP_SIG_ROUTE_PKEY
RH_ROUTE_PKEY
No
Operations Guide
1249
Route History Entity Relationship Diagrams (ERD)

Entity relationship diagrams can be used to visually indicate how the tables and views in
a database are related. Three ERDs are provided for Route History. The first ERD shows
how the route views are related; the second ERD shows how the stop views relate to one
another and the third ERD shows the relationship between the tables. For more specific
information on the views or the tables see Route Views, Stop Views, and Route History
tables.
Stop Views ERD
1250

The stop views ERD shows how the stop views are related to each other. For more
information on how the stop views are related to the tables, see Stop Views.
RH_STOP_ACTUAL_VIEW
PKEY
ORG_UNIT_ID
ORG_UNIT_NAME
REGION_ID
REGION_NAME
ROUTE_ID
ROUTE_DATE
ROUTE_DESCRIPTION
SCENARIO
LOCATION_ID
LOCATION_TYPE
LOCATION_DESCRIPTION
STORE_NUMBER
LONGITUDE
LATITUDE
POSTAL_CODE
REGION3
COUNTRY
SALESPERSON_EMPLOYEE_ID
SALESPERSON_LAST_NAME
SALESPERSON_FIRST_NAME
SALESPERSON_EMPLOYEE_TYPE
SALESPERSON_REGION_ID
ARRIVAL
ARRIVAL_VARIANCE
TIME_SERVICE
DEPARTURE
TIME_WINDOW_VARIANCE
OUT_OF_SEQUENCE
OFF_DAY
UNDELIVERABLE
QTY_DELV_SIZE1
QTY_DELV_SIZE2
QTY_DELV_SIZE3
QTY_PICKUP_SIZE1
QTY_PICKUP_SIZE2
QTY_PICKUP_SIZE3
QTY_OVER_SIZE1
QTY_OVER_SIZE2
QTY_OVER_SIZE3
QTY_SHORT_SIZE1
QTY_SHORT_SIZE2
QTY_SHORT_SIZE3
QTY_DAMAGED_SIZE1
QTY_DAMAGED_SIZE2
QTY_DAMAGED_SIZE3
COST_TRANSPORTATION
COST_NON_TRANSPORTATION
REVENUE
CONSIGNEE
SIGNATURE_DATA
PKEY
ORG_UNIT_ID
ORG_UNIT_NAME
REGION_ID
REGION_NAME
ROUTE_ID
ROUTE_DATE
ROUTE_DESCRIPTION
SCENARIO
LOCATION_ID
LOCATION_TYPE
STORE_NUMBER
LONGITUDE
LATITUDE
POSTAL_CODE
REGION3
COUNTRY
PLANNED_ARRIVAL
ACTUAL_ARRIVAL
PLANNED_DEPARTURE
ACTUAL_DEPARTURE
PLANNED_TIME_SERVICE
ACTUAL_TIME_SERVICE
PLANNED_TIME_WINDOW_VARIANCE
ACTUAL_TIME_WINDOW_VARIANCE
PLANNED_OFF_DAY
ACTUAL_OFF_DAY
PLANNED_QTY_DELV_SIZE1
ACTUAL_QTY_DELV_SIZE1
PLANNED_QTY_PICKUP_SIZE1
ACTUAL_QTY_PICKUP_SIZE1
PLANNED_COST_TRANSPORT
ACTUAL_COST_TRANSPORT
PLANNED_COST_NON_TRANSPORT
ACTUAL_COST_NON_TRANSPORT
PLANNED_REVENUE
ACTUAL_REVENUE
ACTUAL_ARRIVAL_VARIANCE
ACTUAL_OUT_OF_SEQUENCE
ACTUAL_UNDELIVERABLE
ACTUAL_QTY_OVER_SIZE1
ACTUAL_QTY_SHORT_SIZE1
ACTUAL_QTY_DAMAGED_SIZE1
CONSIGNEE
SIGNATURE_DATA
RH_STOP_BASE_VIEW
PKEY
ORG_UNIT_ID
ORG_UNIT_NAME
REGION_ID
REGION_NAME
ROUTE_ID
ROUTE_DATE
ROUTE_DESCRIPTION
SCENARIO
LOCATION_ID
LOCATION_TYPE
STORE_NUMBER
LONGITUDE
LATITUDE
POSTAL_CODE
REGION3
COUNTRY
PKEY
ORG_UNIT_ID
ORG_UNIT_NAME
REGION_ID
REGION_NAME
ROUTE_ID
ROUTE_DATE
ROUTE_DESCRIPTION
SCENARIO
LOCATION_ID
LOCATION_TYPE
STORE_NUMBER
LONGITUDE
LATITUDE
POSTAL_CODE
REGION3
COUNTRY
ARRIVAL
TIME_SERVICE
DEPARTURE
OFF_DAY
QTY_DELV_SIZE1
QTY_DELV_SIZE2
QTY_DELV_SIZE3
QTY_PICKUP_SIZE1
QTY_PICKUP_SIZE2
QTY_PICKUP_SIZE3
COST_TRANSPORTATION
REVENUE
Route Views ERD

Operations Guide
1251
The route views ERD shows how the route views are related to each other. For more
information on how the route views are related to the tables, see Route Views
RH_ROUTE_VIEW
PKEY
ORG_UNIT_ID
ORG_UNIT_NAME
REGION_ID
REGION_NAME
ROUTE_ID
ROUTE_DATE
DESCRIPTION
SCENARIO
HELPER
ORIGIN_ID
ORIGIN_TYPE
ORIGIN_DESCRIPTION
ORIGIN_TIME_ZONE
DESTINATION_ID
DESTINATION_TYPE
DESTINATION_DESCRIPTION
DESTINATION_TIME_ZONE
DRIVER1_REGION_ID
DRIVER1_ID
DRIVER1_LAST_NAME
DRIVER1_FIRST_NAME
DRIVER1_MIDDLE_NAME
DRIVER2_REGION_ID
DRIVER2_ID
DRIVER2_LAST_NAME
DRIVER2_FIRST_NAME
DRIVER2_MIDDLE_NAME
EQUIP1_REGION_ID
EQUIP1_TYPE_ID
EQUIP1_ID
EQUIP1_DESCRIPTION
EQUIP1_TYPE_DESCRIPTION
EQUIP1_BULK_LOAD
EQUIP2_REGION_ID
EQUIP2_TYPE_ID
EQUIP2_ID
EQUIP2_DESCRIPTION
EQUIP2_BULK_LOAD
CAPACITY_SIZE1
CAPACITY_SIZE2
CAPACITY_SIZE3
DATA_SOURCE
START_TIME
COMPLETE_TIME
DEPARTURE
ARRIVAL
DISTANCE_TOTAL_MI
DISTANCE_TOTAL_KM
DISTANCE_STEM_OUT_MI
DISTANCE_STEM_OUT_KM
DISTANCE_STEM_IN_MI
DISTANCE_STEM_IN_KM
TIME_TOTAL
TIME_STEM_OUT
TIME_STEM_IN
TIME_PAID
TIME_SERVICE
TIME_TRAVEL
TIME_WAIT
TIME_BREAK
TIME_LAYOVER
QTY_DELV_SIZE1
QTY_DELV_SIZE2
QTY_DELV_SIZE3
QTY_PICKUP_SIZE1
QTY_PICKUP_SIZE2
QTY_PICKUP_SIZE3
QTY_OVER_SIZE1
QTY_OVER_SIZE2
QTY_OVER_SIZE3
QTY_SHORT_SIZE1
QTY_SHORT_SIZE2
QTY_SHORT_SIZE3
QTY_DAMAGED_SIZE1
QTY_DAMAGED_SIZE2
QTY_DAMAGED_SIZE3
MAX_PERCENT_FULL_SIZE1
STOP_COUNT_TOTAL
STOP_COUNT_DELVS
STOP_COUNT_PICKUPS
STOP_COUNT_PICKUPS_DELVS
STOP_COUNT_MISSED_TW
STOP_COUNT_OFFDAY_DELVS
STOP_COUNT_CANCELED
STOP_COUNT_DELV_QTY_EXCPT
STOP_COUNT_EARLY
STOP_COUNT_LATE
STOP_COUNT_ROUTE_EXCPT
ORDER_COUNT_TOTAL
ORDER_COUNT_DELVS
ORDER_COUNT_PICKUPS
LINE_ITEM_COUNT_TOTAL
LINE_ITEM_COUNT_DELVS
LINE_ITEM_COUNT_PICKUPS
STOPS_OUT_OF_SEQ
COST_TOTAL
COST_OVERTIME
RH_ROUTE_PLAN_VS_ACTUAL_VIEW
PKEY
ORG_UNIT_ID
ORG_UNIT_NAME
REGION_ID
REGION_NAME
ROUTE_ID
ROUTE_DATE
DESCRIPTION
SCENARIO
HELPER
ORIGIN_ID
ORIGIN_TYPE
ORIGIN_DESCRIPTION
ORIGIN_TIME_ZONE
DESTINATION_ID
DESTINATION_TYPE
DRIVER1_REGION_ID
DRIVER1_ID
DRIVER1_LAST_NAME
DRIVER1_FIRST_NAME
DRIVER1_MIDDLE_NAME
DRIVER2_REGION_ID
DRIVER2_ID
DRIVER2_LAST_NAME
DRIVER2_FIRST_NAME
DRIVER2_MIDDLE_NAME
EQUIP1_REGION_ID
EQUIP1_TYPE_ID
EQUIP1_ID
EQUIP1_DESCRIPTION
EQUIP1_BULK_LOAD
EQUIP2_REGION_ID
EQUIP2_TYPE_ID
EQUIP2_ID
EQUIP2_DESCRIPTION
EQUIP2_BULK_LOAD
CAPACITY_SIZE1
CAPACITY_SIZE2
CAPACITY_SIZE3
DATA_SOURCE
START_TIME
COMPLETE_TIME
DEPARTURE
ARRIVAL
DISTANCE_TOTAL_MI
DISTANCE_TOTAL_KM
DISTANCE_STEM_IN_MI
DISTANCE_STEM_IN_KM
TIME_TOTAL
TIME_STEM_OUT
TIME_STEM_IN
TIME_PAID
TIME_SERVICE
TIME_TRAVEL
TIME_WAIT
TIME_BREAK
TIME_LAYOVER
QTY_DELV_SIZE1
QTY_DELV_SIZE2
QTY_DELV_SIZE3
QTY_PICKUP_SIZE1
QTY_PICKUP_SIZE2
QTY_PICKUP_SIZE3
STOP_COUNT_TOTAL
STOP_COUNT_DELVS
STOP_COUNT_PICKUPS
ORDER_COUNT_TOTAL
ORDER_COUNT_DELVS
ORDER_COUNT_PICKUPS
COST_TOTAL
COST_OVERTIME
PKEY
DATA_SOURCE
START_TIME
COMPLETE_TIME
DEPARTURE
ARRIVAL
DISTANCE_TOTAL_MI
DISTANCE_TOTAL_KM
DISTANCE_STEM_IN_MI
DISTANCE_STEM_IN_KM
TIME_TOTAL
TIME_STEM_OUT
TIME_STEM_IN
TIME_PAID
TIME_SERVICE
TIME_TRAVEL
TIME_WAIT
TIME_BREAK
TIME_LAYOVER
QTY_DELV_SIZE1
QTY_DELV_SIZE2
QTY_DELV_SIZE3
QTY_PICKUP_SIZE1
QTY_PICKUP_SIZE2
QTY_PICKUP_SIZE3
QTY_OVER_SIZE1
QTY_OVER_SIZE2
QTY_OVER_SIZE3
QTY_SHORT_SIZE1
QTY_SHORT_SIZE2
QTY_SHORT_SIZE3
QTY_DAMAGED_SIZE1
QTY_DAMAGED_SIZE2
QTY_DAMAGED_SIZE3
STOP_COUNT_TOTAL
STOP_COUNT_DELVS
STOP_COUNT_PICKUPS
STOP_COUNT_CANCELED
STOP_COUNT_EARLY
STOP_COUNT_LATE
ORDER_COUNT_TOTAL
ORDER_COUNT_DELVS
ORDER_COUNT_PICKUPS
STOPS_OUT_OF_SEQ
COST_TOTAL
COST_OVERTIME
PKEY
ORG_UNIT_ID
ORG_UNIT_NAME
REGION_ID
REGION_NAME
ROUTE_ID
ROUTE_DATE
DESCRIPTION
SCENARIO
HELPER
ORIGIN_ID
ORIGIN_TYPE
ORIGIN_DESCRIPTION
ORIGIN_TIME_ZONE
DESTINATION_ID
DESTINATION_TYPE
DRIVER1_REGION_ID
DRIVER1_ID
DRIVER1_LAST_NAME
DRIVER1_FIRST_NAME
DRIVER1_MIDDLE_NAME
DRIVER2_REGION_ID
DRIVER2_ID
DRIVER2_LAST_NAME
DRIVER2_FIRST_NAME
DRIVER2_MIDDLE_NAME
EQUIP1_REGION_ID
EQUIP1_TYPE_ID
EQUIP1_ID
EQUIP1_DESCRIPTION
EQUIP1_BULK_LOAD
EQUIP2_REGION_ID
EQUIP2_TYPE_ID
EQUIP2_ID
EQUIP2_DESCRIPTION
EQUIP2_BULK_LOAD
CAPACITY_SIZE1
CAPACITY_SIZE2
CAPACITY_SIZE3
DATA_SOURCE
START_TIME
COMPLETE_TIME
DEPARTURE
ARRIVAL
DISTANCE_TOTAL_MI
DISTANCE_TOTAL_KM
DISTANCE_STEM_IN_MI
DISTANCE_STEM_IN_KM
TIME_TOTAL
TIME_STEM_OUT
TIME_STEM_IN
TIME_PAID
TIME_SERVICE
TIME_TRAVEL
TIME_WAIT
TIME_BREAK
TIME_LAYOVER
QTY_DELV_SIZE1
QTY_DELV_SIZE2
QTY_DELV_SIZE3
QTY_PICKUP_SIZE1
QTY_PICKUP_SIZE2
QTY_PICKUP_SIZE3
QTY_OVER_SIZE1
QTY_OVER_SIZE2
QTY_OVER_SIZE3
QTY_SHORT_SIZE1
QTY_SHORT_SIZE2
QTY_SHORT_SIZE3
QTY_DAMAGED_SIZE1
QTY_DAMAGED_SIZE2
QTY_DAMAGED_SIZE3
STOP_COUNT_TOTAL
STOP_COUNT_DELVS
STOP_COUNT_PICKUPS
STOP_COUNT_CANCELED
STOP_COUNT_EARLY
STOP_COUNT_LATE
ORDER_COUNT_TOTAL
ORDER_COUNT_DELVS
ORDER_COUNT_PICKUPS
STOPS_OUT_OF_SEQ
COST_TOTAL
COST_OVERTIME
PKEY
ORG_UNIT_ID
ORG_UNIT_NAME
REGION_ID
REGION_NAME
ROUTE_ID
ROUTE_DATE
DESCRIPTION
SCENARIO
HELPER
ORIGIN_ID
ORIGIN_TYPE
ORIGIN_DESCRIPTION
ORIGIN_TIME_ZONE
DESTINATION_ID
DESTINATION_TYPE
DRIVER1_REGION_ID
DRIVER1_ID
DRIVER1_LAST_NAME
DRIVER1_FIRST_NAME
DRIVER1_MIDDLE_NAME
DRIVER2_REGION_ID
DRIVER2_ID
DRIVER2_LAST_NAME
DRIVER2_FIRST_NAME
DRIVER2_MIDDLE_NAME
EQUIP1_REGION_ID
EQUIP1_TYPE_ID
EQUIP1_ID
EQUIP1_DESCRIPTION
EQUIP1_BULK_LOAD
EQUIP2_REGION_ID
EQUIP2_TYPE_ID
EQUIP2_ID
EQUIP2_DESCRIPTION
EQUIP2_BULK_LOAD
CAPACITY_SIZE1
CAPACITY_SIZE2
CAPACITY_SIZE3
PLANNED_DATA_SOURCE
ACTUAL_DATA_SOURCE
PLANNED_START_TIME
ACTUAL_START_TIME
PLANNED_COMPLETE_TIME
ACTUAL_COMPLETE_TIME
PLANNED_DEPARTURE
ACTUAL_DEPARTURE
PLANNED_ARRIVAL
ACTUAL_ARRIVAL
PLANNED_DISTANCE_TOTAL_MI
ACTUAL_DISTANCE_TOTAL_MI
PLANNED_DISTANCE_TOTAL_KM
ACTUAL_DISTANCE_TOTAL_KM
PLANNED_DISTANCE_STEM_OUT_MI
ACTUAL_DISTANCE_STEM_OUT_MI
PLANNED_DISTANCE_STEM_OUT_KM
ACTUAL_DISTANCE_STEM_OUT_KM
PLANNED_DISTANCE_STEM_IN_MI
ACTUAL_DISTANCE_STEM_IN_MI
PLANNED_DISTANCE_STEM_IN_KM
ACTUAL_DISTANCE_STEM_IN_KM
PLANNED_TIME_TOTAL
ACTUAL_TIME_TOTAL
PLANNED_TIME_STEM_OUT
ACTUAL_TIME_STEM_OUT
PLANNED_TIME_STEM_IN
ACTUAL_TIME_STEM_IN
PLANNED_TIME_PAID
ACTUAL_TIME_PAID
PLANNED_TIME_SERVICE
ACTUAL_TIME_SERVICE
PLANNED_TIME_TRAVEL
ACTUAL_TIME_TRAVEL
PLANNED_TIME_WAIT
ACTUAL_TIME_WAIT
PLANNED_TIME_BREAK
ACTUAL_TIME_BREAK
PLANNED_TIME_LAYOVER
ACTUAL_TIME_LAYOVER
PLANNED_MAX_PERCENT_FULL_SIZE1
ACTUAL_MAX_PERCENT_FULL_SIZE1
PLANNED_STOP_CNT_TOTAL
ACTUAL_STOP_CNT_TOTAL
PLANNED_STOP_CNT_DELVS
ACTUAL_STOP_CNT_DELVS
PLANNED_STOP_CNT_PICKUPS
ACTUAL_STOP_CNT_PICKUPS
PLANNED_STOP_CNT_PICKUPS_DELVS
ACTUAL_STOP_CNT_PICKUPS_DELVS
PLANNED_STOP_CNT_MISSED_TW
ACTUAL_STOP_CNT_MISSED_TW
PLANNED_STOP_CNT_OFFDAY_DELVS
ACTUAL_STOP_CNT_OFFDAY_DELVS
PLANNED_ORDER_CNT_TOTAL
ACTUAL_ORDER_CNT_TOTAL
PLANNED_ORDER_CNT_DELVS
ACTUAL_ORDER_CNT_DELVS
PLANNED_ORDER_CNT_PICKUPS
ACTUAL_ORDER_CNT_PICKUPS
PLANNED_LINE_ITEM_CNT_TOTAL
ACTUAL_LINE_ITEM_CNT_TOTAL
PLANNED_LINE_ITEM_CNT_DELVS
ACTUAL_LINE_ITEM_CNT_DELVS
PLANNED_LINE_ITEM_CNT_PICKUPS
ACTUAL_LINE_ITEM_CNT_PICKUPS
PLANNED_COST_TOTAL
ACTUAL_COST_TOTAL
PLANNED_COST_OVERTIME
ACTUAL_COST_OVERTIME
ACTUAL_STOP_CNT_CANCELED
ACTUAL_STOP_CNT_DELV_QTY_EXCPT
ACTUAL_STOP_CNT_EARLY
ACTUAL_STOP_CNT_LATE
ACTUAL_STOP_CNT_ROUTE_EXCPT
ACTUAL_STOPS_OUT_OF_SEQ
RH_ROUTE_BASE_VIEW
PKEY
ORG_UNIT_ID
ORG_UNIT_NAME
REGION_ID
REGION_NAME
ROUTE_ID
ROUTE_DATE
DESCRIPTION
SCENARIO
HELPER
ORIGIN_ID
ORIGIN_TYPE
ORIGIN_DESCRIPTION
ORIGIN_TIME_ZONE
DESTINATION_ID
DESTINATION_TYPE
DRIVER1_REGION_ID
DRIVER1_ID
DRIVER1_LAST_NAME
DRIVER1_FIRST_NAME
DRIVER1_MIDDLE_NAME
DRIVER2_REGION_ID
DRIVER2_ID
DRIVER2_LAST_NAME
DRIVER2_FIRST_NAME
DRIVER2_MIDDLE_NAME
EQUIP1_REGION_ID
EQUIP1_TYPE_ID
EQUIP1_ID
EQUIP1_DESCRIPTION
EQUIP1_BULK_LOAD
EQUIP2_REGION_ID
EQUIP2_TYPE_ID
EQUIP2_ID
EQUIP2_DESCRIPTION
EQUIP2_BULK_LOAD
CAPACITY_SIZE1
CAPACITY_SIZE2
CAPACITY_SIZE3
Route History Tables ERD

1252

The tables ERD shows how the Route History tables are related. For more information on
the tables, see Route History tables.
RH_ROUTE_ACTUAL
PK
DATA_SOURCE
START_TIME
COMPLETE_TIME
DEPARTURE
ARRIVAL
DISTANCE_TOTAL
DISTANCE_STEM_OUT
DISTANCE_STEM_IN
TIME_TOTAL
TIME_STEM_OUT
TIME_STEM_IN
TIME_PAID
TIME_SERVICE
TIME_TRAVEL
TIME_WAIT
TIME_BREAK
TIME_LAYOVER
TIME_WBL_SUM
QTY_DELV_SIZE1
QTY_DELV_SIZE2
QTY_DELV_SIZE3
QTY_PICKUP_SIZE1
QTY_PICKUP_SIZE2
QTY_PICKUP_SIZE3
QTY_OVER_SIZE1
QTY_OVER_SIZE2
QTY_OVER_SIZE3
QTY_SHORT_SIZE1
QTY_SHORT_SIZE2
QTY_SHORT_SIZE3
QTY_DAMAGED_SIZE1
QTY_DAMAGED_SIZE2
QTY_DAMAGED_SIZE3
STOP_COUNT_TOTAL
STOP_COUNT_DELVS
STOP_COUNT_PICKUPS
STOP_COUNT_CANCELED
STOP_COUNT_EARLY
STOP_COUNT_LATE
ORDER_COUNT_TOTAL
ORDER_COUNT_DELVS
ORDER_COUNT_PICKUPS
STOPS_OUT_OF_SEQ
COST_TOTAL
COST_OVERTIME
USER_MODIFIED
DATE_MODIFIED
READ_ONLY
RH_ROUTE_PLANNED
PK
PKEY
DATA_SOURCE
START_TIME
COMPLETE_TIME
DEPARTURE
ARRIVAL
DISTANCE_TOTAL
DISTANCE_STEM_OUT
DISTANCE_STEM_IN
TIME_TOTAL
TIME_STEM_OUT
TIME_STEM_IN
TIME_PAID
TIME_SERVICE
TIME_TRAVEL
TIME_WAIT
TIME_BREAK
TIME_LAYOVER
TIME_WBL_SUM
QTY_DELV_SIZE1
QTY_DELV_SIZE2
QTY_DELV_SIZE3
QTY_PICKUP_SIZE1
QTY_PICKUP_SIZE2
QTY_PICKUP_SIZE3
STOP_COUNT_TOTAL
STOP_COUNT_DELVS
STOP_COUNT_PICKUPS
ORDER_COUNT_TOTAL
ORDER_COUNT_DELVS
ORDER_COUNT_PICKUPS
COST_TOTAL
COST_OVERTIME
USER_MODIFIED
DATE_MODIFIED
READ_ONLY
RH_ROUTE_MASTER
PK
PKEY
PKEY
REGION_ID
ROUTE_ID
ROUTE_DATE
DESCRIPTION
SCENARIO
RH_LOCATION_ORIGIN_PKEY
RH_LOCATION_DEST_PKEY
CAPACITY_SIZE1
CAPACITY_SIZE2
CAPACITY_SIZE3
HELPER
USER_MODIFIED
DATE_MODIFIED
READ_ONLY
ORG_UNIT_ID
RH_STOP_PLANNED
PK
RH_LOCATION
PK
PKEY
REGION_ID
LOCATION_ID
LOCATION_TYPE
DESCRIPTION
STORE_NUMBER
POSTAL_CODE
REGION3
COUNTRY
LONGITUDE
LATITUDE
TIME_ZONE
ACCOUNT_TYPE_ID
SERVICE_TIME_TYPE_ID
DELIVERY_DAYS
SALESMAN_ID
SALESMAN_REGION_ID
USER_MODIFIED
DATE_MODIFIED
READ_ONLY
RH_EMPLOYEE
PK
PKEY
REGION_ID
EMPLOYEE_ID
LAST_NAME
FIRST_NAME
MIDDLE_NAME
TYPE
USER_MODIFIED
DATE_MODIFIED
READ_ONLY
PKEY
RH_ROUTE_PKEY
ARRIVAL
TIME_SERVICE
DEPARTURE
OFF_DAY
QTY_DELV_SIZE1
QTY_DELV_SIZE2
QTY_DELV_SIZE3
QTY_PICKUP_SIZE1
QTY_PICKUP_SIZE2
QTY_PICKUP_SIZE3
COST_TRANSPORTATION
REVENUE
USER_MODIFIED
DATE_MODIFIED
READ_ONLY
RH_STOP_ACTUAL
PK
PKEY
RH_ROUTE_PKEY
ARRIVAL
ARRIVAL_VARIANCE
TIME_SERVICE
DEPARTURE
OUT_OF_SEQUENCE
OFF_DAY
UNDELIVERABLE
QTY_DELV_SIZE1
QTY_DELV_SIZE2
QTY_DELV_SIZE3
QTY_PICKUP_SIZE1
QTY_PICKUP_SIZE2
QTY_PICKUP_SIZE3
QTY_OVER_SIZE1
QTY_OVER_SIZE2
QTY_OVER_SIZE3
QTY_SHORT_SIZE1
QTY_SHORT_SIZE2
QTY_SHORT_SIZE3
QTY_DAMAGED_SIZE1
QTY_DAMAGED_SIZE2
QTY_DAMAGED_SIZE3
COST_TRANSPORTATION
REVENUE
USER_MODIFIED
DATE_MODIFIED
READ_ONLY
RH_STOP_MASTER
PK
RH_STOP_SIGNATURE
PK
PKEY
RH_ROUTE_PKEY
CONSIGNEE
DATE_MODIFIED
USER_MODIFIED
READ_ONLY
SIGNATURE_DATA
PKEY
REGION_ID
RH_ROUTE_PKEY
RH_LOCATION_PKEY
RH_EMPLOYEE_SALES_PKEY
BULK_SERVICE
USER_MODIFIED
DATE_MODIFIED
READ_ONLY
ORG_UNIT_ID
RH_EQUIPMENT
PK
PKEY
REGION_ID
EQUIPMENT_TYPE_ID
EQUIPMENT_ID
DESCRIPTION
USER_MODIFIED
DATE_MODIFIED
READ_ONLY
RH_EQUIPMENT_TYPE
PK
PKEY
REGION_ID
EQUIPMENT_TYPE_ID
DESCRIPTION
BULK_LOAD
USER_MODIFIED
DATE_MODIFIED
READ_ONLY
Operations Guide
1253
1254

Introducing netScheduler
netScheduler is a portion of the Roadnet Transportation Suite that uses application

programming interfaces (API) to help control all aspects of the transportation segment of
your business. You can use netScheduler to power your application to validate addresses,
show maps and scheduled orders, and integrate with the remainder of the Roadnet
Transportation Suite. netScheduler consists of the following SOAP/XML Web Services
servers:
Roadnet Web Servicesschedules orders and answers the question What is the
feasibility of placing an order on a given date and requesting delivery time?. This server
also enables netScheduler to integrate with the rest of the Roadnet Transportation Suite.
RouteNet Web Servicesallows customers to geocode a location and generate maps to
display the location.
Although not all of the servers are required, using the complete netScheduler package
will allow your company to operate more efficiently while providing your customers
with the level of service they require. Throughout the day as your customers are placing
their orders, netScheduler is determining the feasibility of delivering each order based on
parameters you specified and the current orders that exist. This real-time unattended
functionality allows you to meet your customers needs while operating your business
efficiently.
In addition to the SOAP/XML server, netScheduler includes some supporting tools that
you can use. Day Commander is a separate module in the Roadnet Transportation Suite
where you can view the current orders for your delivery windows in netScheduler.
Another separate module is Cost Analyzer, a handy tool you can use to determine filter
limits or simulate orders.
Operations Guide
1255
Working with Day Commander

The Day Commander module works with netScheduler and allows you to view the current
orders for your delivery windows in netScheduler. You can also manually close a delivery
window if it has reached capacity, add a delivery window for just one day, delete a
delivery window for one day, or change the resources available for a delivery wave.
In addition to viewing the stops on the map, if you want detailed information about an
order, it can be found on the All Deliveries window. The All Deliveries window contains
information such as service time, quantity, location, and delivery time information about
the orders.
Day Commander relies on the Roadnet Web Services for the data that is displayed. Since
the information on the server is constantly changing, it may be necessary to update the
data you are viewing in Day Commander. To get the most recent information from the
server, simply click on the Refresh icon; Day Commander will be updated with the most
recent information.
Changing the Delivery Date or Customer in Day Commander
When Day Commander opens, the default regions routes for the next delivery day are
automatically displayed. You can change either the date or region to view a different set
of routes, or the delivery area you are viewing routes for.
To change the date or region, click on the [Date] button on the bottom of the module:
the Filter Data for Viewing window opens.
To change the delivery date, enter the date manually, or click on the arrow to open a
calendar in the Planned Date field. If you are using the calendar to change the month,
either use the arrows on top of the calendar to scroll through the months, or click on the
month and select it from the menu that pops up. To change the year, click on the year and
use the arrows to scroll to the correct year. Click on a date to select it.
Use the Filter Data for Viewing

window to change either the delivery
date, or delivery area that is displayed
in Day Commander.
To change the delivery area, click All to include all areas in the delivery area, or click
Specific. Then, click on the arrow to select the delivery area from the list that opens.
To change the region, click on the arrow next to the Region field. A list of all available
regions opens; click on a region to select it.
To refresh the data from the server, click on the Refresh icon.
1256

Viewing an Order, Delivery Wave, or Delivery Window
When you first enter Day Commander, you automatically see all orders for the selected
delivery area. If you want to see only those orders for a delivery wave, delivery window,
or only a selected order, you can do so.
To see a list of stops in a specific delivery window or wave, right-click on the delivery
window/delivery wave and select View, then Deliveries from the menu that pops up. A
window opens, listing all the stops for the selected delivery window/wave.
To see the stops for a specific delivery window/wave on a map, right-click on the
delivery window/delivery wave and select View, then Plot from the menu that pops up. A
map opens, displaying only those stops in the selected delivery window/delivery wave.
To see a summary of reserved/confirmed orders, either by delivery wave or by delivery
window, click on the List menu and select Order Summary. The Order Summary window
opens. See Using the Order Summary for more information.
To see the routes for a specific delivery wave, right-click on the wave and select View,
then Routes from the menu that pops up. The Routes for Delivery Wave window opens.
To color the orders on the map by delivery wave, click the Color Orders by Delivery
Wave icon.
To color the orders on the map by the delivery window, click the Color Orders by
Delivery Window icon.
To color the orders on the map by route, click the Color Orders by Routes icon.
To see an order on the map, right-click on the order in the All Deliveries window and
select Locate on Map from the menu that pops up. Or, right-click on a delivery window/
delivery wave and select View, then Deliveries from the menu that pops up. Right-click
on an order from the Stops for Delivery Wave/Stops for Delivery Window and select
Locate on Map from the menu that pops up. The map opens with the all the stops plotted
on the map.
To see a route on the map, right-click on an order in the All Deliveries window and
select Locate on Route Map from the menu that pops up. Or, right-click on a delivery
window/delivery wave and select View, then Deliveries from the menu that pops up.
Right-click on an order from the Stops for Delivery Wave/Stops for Delivery Window
Operations Guide
1257
and select Locate on a Route Map from the menu that pops up. The route map opens with
the order(s) plotted on the map.
The map allows you to see where the delivery customer for the order is located.
Updating an Order In Day Commander
There may be times when you need to update an orders information that has already been
placed in netScheduler. For example, you already have the orders in netScheduler and a
customer calls about an order that is to be delivered. The customer wants to change the
quantity to be delivered and also has items to be picked up. You can update the order
through Day Commander.
When you first enter Day Commander, you automatically see all orders for the selected
delivery area.
Step 1: Select Update Order from the menu that pops up. The Updating Order window
opens.
You are able to change some

information about an order once
it is in netScheduler.
Step 2: Enter the new information in the field for the attribute that you want to update.
For instance, to update an order number, check the Order Number box and then
enter the new order number in the field.
Step 3: Click the [Update] button to save the new order information.
Step 4: Click the Close box to close the Updating Order window.
1258

Cancel an Order on a Route
There may be times where you need to cancel an order after it has already been placed on
a route. You can cancel an order from the All Deliveries window, the Stop for Delivery
Wave window, or the Stop for Delivery Window window.
Step 1: Click on the Day Commander icon to open Day Commander. The Day
Commander window opens.
Step 2: Right-click on the order that you want to cancel on the All Deliveries window
and select Cancel Order from the menu that pops up.
You can cancel an order from the All Deliveries window.
Step 3: A message box is sent to say that it was successful. Click [OK].
Using the Order Summary
Day Commander includes an Order Summary window that displays a synopsis of the
existing reserved and confirmed orders for the delivery area. You can see the total orders
for each delivery wave or the total orders for each delivery window. There is also an
Average Cost Per Order that is updated throughout the day as orders are reserved or
confirmed, letting you keep track of the average cost of delivering each order.
To open the Order Summary, click on the List menu and select Order Summary.
You can use the Order Summary

window to keep track of vital
information, such as the
average cost per order and total
orders for each delivery wave
and delivery window.
To view the orders by delivery wave, click on the Delivery Wave icon.
To view the orders by delivery window, click on the Delivery Window icon.
Operations Guide
1259
Adding, Deleting, or Closing a Delivery Window in Day Commander
There may be times when extenuating circumstances require you to make changes to the
available delivery windows for a particular day. You can add, delete, or close a static
delivery window in Day Commander. Unlike delivery window changes made in the
Maintenance module, these changes only apply to the particular day you are viewing in
Day Commander. So, if you want to create an additional delivery window to
accommodate extra deliveries for this day, add the window in the Day Commander.
However, if you want to create an additional delivery window that will be available on
other days, use the Maintenance module.
You can delete and close static delivery windows, as well. Delivery windows closed in
the Day Commander are referred to as manually closed. If you manually close a delivery
window, no more orders can be added to it, but it remains part of the days plan. Closed
delivery windows appear in the Delivery Windows window with a line through them. A
deleted delivery window will be removed from the list, and from the days plan.
To add a delivery window, right-click on an existing delivery window and select Add
from the menu that pops up. The Add Delivery Window opens. Enter the starting and
ending time for the new delivery window. You can enter the time manually, or use the
arrows to scroll to the correct time. If entering the time manually, use the arrow keys to
move from the hour to minute field. If using the scroll arrows, click on the correct field
(hour or minute) before scrolling. Use a 24-hour clock when entering the time: for
example, enter 1:00 PM as 13:00. Then, click the [OK] button. The delivery windows
added here will be available to all potential delivery locations for this day only.
Day Commander icon Delivery Windows window Add
You can use the Add Delivery Window to add a
delivery window that will only be for the specified
day, not for all the days in the delivery window.
To close a delivery window, right-click on the delivery window and select Close from
the menu that pops up. A closed delivery window remains in the list, but has a line through
it, indicating it is closed. A closed delivery window will not be available when customers
choose their delivery options.
Day Commander icon Delivery Windows window Close
To delete a delivery window, right-click on the delivery window and select Delete from
the menu that pops up. Select Yes to the message Are you sure you want to delete
Delivery window. The window is deleted from all records for the day.
Day Commander icon Delivery Windows window Delete
Changing Properties for a Wave
Each delivery wave has a start time and a depot as well as other information associated
with it. There may be times when you need to change the information about a delivery
1260

wave. For example, you may need to change the number of vehicles available if a vehicle
breaks down.
Step 2: Select a wave from the Delivery Waves window.
Step 3: Right-click on the wave and select Change Properties from the menu that pops
up. The Change Wave Properties window opens.
You can change your

resources as well as
restrict equipment
types in the Change
Wave Properties
window.
Step 4: Enter the new time that you want the delivery wave to begin in the Start Time
field, if applicable. You can enter the time manually, or use arrows to scroll to the
correct time. You can enter the time manually, or use arrows keys to move from
the hour to minute field. If using the scroll arrows, click on the correct field (hour
to minute) before scrolling. Use a 24-hour clock when entering the time. For
example, enter 1:00 PM as 13:00.
Step 5: In the Delivery Window Metrics section, enter the Outbound Stem Time and the
Inbound Stem Time. You can enter the time manually. Click on the correct field
(hour to minute) before entering the time. Enter as HH:MM. For example, enter
if you want the outbound time to be 13 minutes, enter 00:13.
Step 6: In the Depot section, you can change the origin for the wave be selecting the
location type and entering the ID, if applicable. If you dont know the ID, enter as
much as you know followed by an asterick (*), such as 12*, and click the [Query]
button. Double-click the desired location from the Locations list that appears.
Operations Guide
1261
Note: If you need to add a depot, you can click the [New] button. The Add Location
window opens. See Working with Locations for more information.
Step 7: Click on the Equipment Type arrow to open the Lookup - Equipment Type
window in the Resources section. Double-click on the equipment type you want
to change for the delivery wave.
Step 8: Enter the new number of vehicles available for the delivery wave in the
Vehicles field in the Resources section.
Note: You must enter at least 1 vehicle for the wave. If you have locked orders, you must
enter enough vehicles to deliver each route with at least one locked order.
Step 9: Click on the Time of Day Restriction Model arrow to open the Time of Day
Restriction Model window. Double-click on a model to select it so you can use it
to restrict travel in defined areas during defined times for the delivery wave.
Step 10: In the Equipment Capacity Restrictions section, check the appropriate size
alias to have netScheduler check the equipments available capacity as that size.
speeds when creating routes.
creating routes. Select the rush hour model that the session should use from the
Rush Hour Model field.
click on the arrow to open the Lookup - Rush Hour Model window. Doubleclick on a model to select it, or click on the model and then on the Process icon.
If you are using RouteNet or SuperMatrix and want to use advanced rush hour
features, such as paths or travel restrictions, check Advanced Rush Hour
paths. If you want to impose travel restrictions or change the road direction
during a rush hour period, you must check Advanced Rush Hour (consider
alternative streets).
creating routes.
Note: In order to use the Advanced Rush Hour feature, it must be set up within the
Maintenance module as well as the Rush Hour Model feature.
Step 12: Enter the new preferred length of time that you would like the route to last in
the Preferred field of the Runtime section. A route may be longer than the
preferred runtime. Enter the time in the format HH:MM.
1262

Step 13: Enter the new maximum amount of time that the wave can last in the
Maximum field of the Runtime section.
Note: The Preferred and Maximum runtimes must be greater than 00:00.
Step 14: Enter the costs associated with the delivery wave. These costs are used to
calculate the effects of adding orders to a delivery window.
Hourly Wage Durationthe amount of time the driver is paid the hourly wage.
If the route extends beyond this time, any additional time, the driver will be paid
at the overtime wage.
Hourly Wagethe amount the driver is paid per hour.
OT Wagethe amount the driver is paid when working overtime. Once the
routes total runtime exceeds the hourly wage duration, the driver costs will be
calculated using this wage.
Step 15: Click the [Update] button to save the changes.
Step 16: If there are any existing orders that cannot be fulfilled due to the changes to
the delivery wave, they display in the Broken Commitments section. Click the
Force checkbox if you definitely want the changes made to the wave.
Step 17: Click the [Update] button. The broken commitments will be canceled from the
system.
Step 18: Click the Close box to close the window. You will receive a message that the
request has been sent to the scheduling server.
Day Commander icon Delivery Waves window Change Properties
Changing Skill Set Properties for a Wave
Day Commander allows you to view the current reserved and confirmed orders for your
delivery windows. You can also manually close a delivery window if it has reached
capacity, add a delivery window for just one day, delete a delivery window for one day,
or change the resources available for a delivery wave.
Each delivery wave has a number of resources associated with it. There may be times
when you need to change this number, such as if a driver with a skill set calls out sick,
you would need to decrease the number of resources with that skill set available for the
day.
You can easily change the number of resources available to a delivery wave in Day
Commander. You can change the number of drivers available that have a particular skill
set. Any changes made to the number of skill sets in Day Commander only applies to this
date; to make more permanent changes, use the Maintenance module.
Step 2: Select a wave from the Delivery Waves window.
Operations Guide
1263
Step 3: Right-click on the wave and select View, then Skill Sets. The Skill Sets for
Delivery Wave window opens.
Step 4: Right-click on the skill set that needs the number of resources changed and
select Change Properties. The Change Skill Set Properties window opens, listing
the current number of resources with that skill set available.
You can change the number of delivery
vehicles available for the wave, and therefore
the number of routes that can be created.
Step 5: Enter the new number in the Number of Vehicles field.

Step 6: Click the [OK] button. The message A request has been sent to the scheduling
server displays.
Step 8: Click the Close box to close the Skill Sets for Delivery Wave window.
Day Commander icon Delivery Waves window View Skill Sets Change Properties
Review Routes
or change various properties for a delivery wave.
When you first enter Day Commander, you automatically see all orders for all delivery
areas. If you want to see only those orders for a specific delivery wave or delivery
window, or only a selected order, you can do so.
To view a route for a specific area, click on the [Date] button at the bottom of the
module: the Filter Data for Viewing window opens. In the Areas section, click on
Specific, then click the arrow and select the desired delivery area and click [OK]. Click
List, then select Routes. The Routes window opens with any existing routes. If you do not
select a specific area, but leave it defaulted to All, the message Unable to view this
information when viewing all areas displays.
The Route window allows you to view routes for a specific area.
1264

To see the routes for a specific delivery wave, right-click on the Delivery Wave window
and select View, then Routes from the menu that pops up. The Routes for Delivery Wave
window opens.
The Routes for Delivery Wave window shows the different routes for that particular delivery
wave.
To plot one or more routes, select List then select Routes. The Routes window opens.
In the Routes window, highlight a route, right-click and select Plot from the menu that
pops up. The Plot Routes window opens.
The Plot Routes window allows you to view one or more routes.
Operations Guide
1265
To view the stops on a route, select List then Routes. The Routes window opens. Select
a route, right-click and select Stops. The Stops for Region list opens.
The Stops for Region window allows you to view stops on a route as well as locate the stops
on an order map or route map.
To plot one or more orders on a route, select List then Routes. The Routes window
opens. Select a route, right-click and select Stops. The Stops for Region window opens.
Select one or more stops; right-click and select Locate on Order Map or select Locate on
Route Map. You can also select an order(s) from the All Deliveries window and plot them.
Locking and Unlocking Orders in Day Commander
or change various properties for a delivery wave.
Order locking allows you to prevent orders that are on a route from being moved to a
different route. Orders that are locked will not be removed from their current route during
background optimization.
To lock/unlock all orders on a route from the All Deliveries window or from the
Routes window, right-click on an order and select Lock Order to Route or Allow Order
to Change Routes from the menu that pops up. The message A request has been sent to
the scheduling server displays. Click [OK].
You can lock and unlock orders on a route on the All Deliveries window.
Sending Routes to Roadnet
Once you have created your routes in netScheduler, you can transfer them directly into
Roadnets Routing Editor. Click on the File menu and select Send Routes to Roadnet.
1266

Click Yes when the message about being sure that you want to send all routes to Roadnet
for the area and region displays.
Note: netScheduler does not allow multiple orders to have the same order number for the
same location. If an existing route has duplicate order numbers and the route is sent
to the Roadnet Routing Editor, an error message displays. The error is written to the
Roadnet Web Services log stating the reason, the location, and the order number.
Columns for the Delivery Windows Window
The columns in the Delivery Windows window and a brief description of the contents of
the window are included in the table below.
Column
Description
Start Time
The start time for the delivery window.
End Time
The end time for the delivery window.
Color
The color indicating which orders are to be delivered during the delivery
window.
Orders
The total number of reserved and confirmed orders on the route.
Window Utilization
Displays the total working time for the delivery window in the form of an
outlined box and the amount of working time already used in the form of a
blue bar. For example, if the delivery window is 60 minutes and you have 50
trucks, you would have 3000 minutes available. So if you have 10 routes with
4 hours of travel time, that would be 240 minutes of travel and service time
per route for a total of 2400 minutes. In this example, you would be using
80% of the delivery window (Total Working Time/Allocated Working
Time).
Vehicles in Use
Displays the number of vehicles that are being used for the delivery window.
Vehicles Allocated
Displays the total number of vehicles for all delivery waves that could have
working time during the delivery window.
Reserved Orders
Displays the total number of orders that are reserved.
Reserved Pickup
Quantity Size 1 - Size 3
Displays the total pickup quantity of product for reserved orders for that size
alias. The column headers reflect the size aliases established in the Options
notebook.
Reserved Delivery
Displays the total delivery quantity of product reserved for orders for that size
notebook.
Reserved Service Time
Displays the total reserved service time.
Reserved Travel Time
Displays the total reserved travel time.
Reserved Working
Time
Displays the reserved travel time plus the reserved service time.
Confirmed Orders
Displays the total number of confirmed orders.
Operations Guide
1267
Column
Description
Confirmed Pickup
Displays the total pickup quantity of product for confirmed orders for that
size alias. The column headers reflect the size aliases established in the
Options notebook.
Confirmed Delivery
Displays the total delivery quantity of product for confirmed orders for that
Options notebook.
Total Pickup Quantity

Size 1 - Size 3
Displays the total confirmed and reserved pickup quantity of product for that
Options notebook.
Total Delivery Quantity

Size 1 - Size 3
Displays the total confirmed and reserved delivery quantity of product for
that size alias. The column headers reflect the size aliases established in the
Options notebook.
Confirmed Service
Time
Displays the total confirmed service time.
Confirmed Travel Time
Displays the total confirmed travel time.
Confirmed Working
Time
Displays the confirmed travel time plus the service time for the delivery
window.
Allocated Working
Time
Displays the total working time available for the delivery window.
Total Service Time
Displays the total service time. for the delivery window.
Total Travel Time
Displays the total travel time for the delivery window.
Total Working Time
Displays the total working time for the delivery window.
Columns for the Routes Window
netScheduler added a new window - Routes to Day Commander. The columns in the
Routes window and a brief description of the contents of the window are included in the
table below.
Column
Description
Route ID
Displays an identifier for the netScheduler route.
Time Summary (Graph)
Displays the routes preferred runtime, or the actual total time if it is over the
preferred time. The blue represents travel time plus service time, yellow
represents the percentage of wait time, and white represents available time.
Stops
Displays the number of stops on the route.
Reloads
Displays the number of reloads on the route.
Departure Time
Displays the time of day the driver departed the depot. Note: A 24-hour clock
is used to enter the time. For example, 1:00 PM displays as 13:00.
1268

Column
Description
Return Time
Displays the time of day the driver returns to the depot. Note: A 24-hour
clock is used to enter the time. For example, 1:00 PM displays as 13:00.
Depot ID
Displays the unique identifier for the routes origin.
Depot Type
Displays the type for the routes origin. Normally, this would be DPT.
Skill Set ID
Displays the unique ID of the skill set containing the activities the employee
can complete.
Color
Displays the color associated with the route. On the map, the route path will
be displayed with this color and in the List window.
Wave Start Time
Displays the time the delivery wave begins.
Cutoff
If the checkbox is marked, the time to add additional orders to the routes has
passed. If it isnt checked, no orders will be accepted after the specified time
on the previous day.
Travel Time
Displays the total amount of time the driver spends driving on the route.
Wait Time
Displays the total amount of time spent on waits for the route. In many
situations, a driver may actually arrive early at a specified location, but may
have to wait sometime before the delivery window begins.
Distance
Displays the total distance the driver drives on the route, measured as either
kilometers or miles.
Service Time
Displays the amount of time the driver needs to service the stop.
Run Time
Displays the amount of time the vehicle spends on the road. This will be equal
to the amount of time between the return and start time.
Displays the quantity of product delivered on the route for that size alias. The
column headers reflect the size aliases established in the Options notebook.
Pickup Quantity Size 1 Size 3
Displays the quantity of product picked up on the route for that size alias. The
Preferred Run Time
Displays the preferred runtime for the route established as a wave limit.
Max Run Time
Displays the maximum runtime for the route established as a wave limit.
Capacity Size 1 - Size 3
Displays the quantity of product that the vehicle can handle for that size alias.
The column headers reflect the size aliases established in the Options
notebook.
Cost
Displays the total cost for the route. The cost is calculated using the driver
and equipment costs.
Regular Hourly Wage
Displays the amount the driver is paid per hour.
Overtime Hourly Wage
Displays the amount the driver is paid when working overtime. Once the
routes total runtime exceeds the hourly wage duration, the driver costs will
be calculated using this wage.
Cost Per Mile
Displays the cost to drive the equipment one mile.
Operations Guide
1269
Column
Description
Setup Cost
Displays the fixed cost of the equipment.
Regular Wage Duration
Displays the amount of time the driver is paid the hourly wage. If the route
extends beyond this time, any additional time, the driver will be paid at the
overtime wage.
Columns for the All Deliveries Window
The columns in the All Deliveries window and a brief description of the contents of the
window are included in the table below.
Column
Description
Route ID
Displays an identifier for the netScheduler route.
Sequence
Displays the order in which the stops will be on the route.
TW Graph
Displays a graph showing whether or not the driver met the stops time
window. The solid blue rectangles indicate the stops time windows, and the
remaining colors used indicate how the time windows were missed (early,
late, etc.). The colors displayed are selected on the Stop Exceptions page of
the Options notebook. If the driver arrives within the specified time window,
but leaves after the time window, there is not a missed time window.
Order Number
Displays the orders unique ID.
Description
Displays a brief description of the order.
Reference Number
Displays a number that can be used to refer back to the order.
Order Type
Displays a single-character field used to designate orders that require special

treatment. The character must be one of two letters: O = Delivery and P =
Pickup. This field affects the way will process and route data.
Location Type
Displays the type of location (SIT, DPT, etc.). If a type is not specified, the
default type will be used.
Location ID
Displays the unique identifier for the location.
Displays the quantity of product delivered by the vehicle for that size alias.
notebook.
Displays the quantity of product picked up by the vehicle for that size alias.
notebook.
Window Start
Displays the starting time for the delivery window.
Window End
Displays the ending time for the delivery window.
Distance To
Displays the distance traveled to the stop.
Time To
Displays the amount of time to travel to the stop distance.
1270

Column
Description
Wait Time
Displays the total amount of time spent on waits for the route, both paid and
unpaid.
Arrival Time
Displays the time the driver arrived at the destination using the local time of
that location.
Service Time
Displays the amount of time the driver needs to service the stop. This
includes both the fixed and variable service time.
Departure Time
Displays the time the driver departed the location, using the local time of that
location.
Latitude
Displays the latitude of the location.
Longitude
Displays the longitude of the location.
Reserved Time
Displays the amount of time that order is reserved before it is canceled.
Locked to route
Displays the orders lock status. If there is a date and time listed, it indicates
when the order was locked. If the column is blank, the order is not locked.
Sequenced on route
If checked, the stop was sequenced in Territory Planner or another routing

tool, and locked in that sequence.
Confirmed
If a checkmark displays in the box, then the order has been confirmed and is
no longer reserved.
Stop Type
Displays a picture indicating the type of stop.
Operations Guide
1271
Working with the Cost Analyzer

netScheduler includes a Cost Analyzer tool that can be used to establish the filter limits
or simulate potential orders. When you select a location to analyze, Cost Analyzer lets you
know the overall costs associated with adding the order to each delivery window, as well
as the additional time and distance associated with delivering to that location. The
analysis results spell out how the netScheduler determines which delivery windows to
offer when an order is placed. You can use this information to determine the parameters
for the filters that are used to restrict order classifications from certain delivery windows,
as well as testing the effects of existing filters. For instance, if you want to make sure a
delivery at the end of the day is not costing a lot of money, you could create a filter to
exclude orders costing more than $30.00 when you reach 80% of capacity.
Cost Analyzer allows you to enter the orders individually, or import a group of orders you
have created in a database.
Note: If you are using Cost Analyzer to set up or determine the effects of filters, you
must start and stop the Roadnet Web Services for the filter change to take effect.
Entering Orders Individually in Cost Analyzer
Cost Analyzer allows you to enter the orders individually.

Step 1: Click on the Cost Analyzer icon. The Cost Analyzer opens with a map displaying
all the orders for the specified customer in the selected delivery area and date.
Step 2: Change the delivery date, area, or region as needed.
To change the delivery date, click on the [Date] button on the bottom of the
module: the Filter Data for Viewing window opens. To change the date, enter the
new date in the Planned Date field. You can type the date, or click on the arrow to
open a calendar. If you are using the calendar to change the month, either use the
arrows on top of the calendar to scroll through the months, or click on the month
and select it from the menu that pops up. To change the year, click on the year and
use the arrows to scroll to the correct year. Click on a date to select it.
To change the delivery area, click on the [Date] button on the bottom of the
Specific, then click the arrow and select the desired delivery area. To view the
orders for all delivery areas, click All.
To change the region, click on the arrow next to the Region field at the bottom
of the module. A list of all available regions opens; click on a region to select it.
Step 3: Double-click on an area on the map; an icon appears on the map and the Cost
Analysis window opens.
Step 4: Enter the Shopper Name, Order Classification, Quantity Size 1 - 3, Pickup
Quantity Size 1 - 3, and Service Time. All of this information is optional, but the
more accurate it is, the more accurate the analysis will be.
1272

Step 5: Click the [Analyze] button. The Cost Analysis window is updated with the new
information.
The Cost Analysis window lists all the delivery windows. It lets you know if the
delivery window is available for the order, why the delivery window is not
available (if its not), as well as the cost for adding the order, additional runtime,
and additional distance the order adds to the delivery window.
The Cost Analysis window provides information to help determine the best delivery window
to add an order to. You can use this feature to determine the effects of accepting certain type
of orders, as well as setting up filters.
Step 6: Click on the delivery window you want, then click the [Place] button. The order
is added for that delivery window.
To place another delivery wave with the same start time, click on the Wave and click
[Place].
To cancel an order, right-click on the order on the map and select Cancel from the menu
that pops up.
To transmit orders to Roadnet Routing Editor, select Action and then Send Routes to
Roadnet.
Operations Guide
1273
Columns in the Cost Analyzer Window

When Cost Analyzer returns an analysis for an order, it returns a lot of information. The
columns in the window, and a brief description of the contents of the window, are
included in the table below.
Column
Description
Start Time
Displays the start time for the delivery window.
End Time
Displays the end time for the delivery window.
Available
Displays a check indicating if the delivery window is available for the order.
Unavailability Reason
Displays a message indicating why the delivery window is not available.
Filtered
Displays a check indicating whether or not the order was filtered.
Vehicle Needed
Displays a check indicating whether or not a new vehicle had to be added to

accept the order.
Missed Window
Displays a check indicating whether or not the delivery window was made.
Addtl Stop Cost
Displays the cost of adding the stop to the window. This cost includes both
distance and runtime costs.
Total Cost
Displays the total cost for the vehicle during the wave. This includes both the
driver and vehicle costs.
Addtl Run Time
Displays the amount that total runtime has been increased as a result of adding
the order to the delivery window.
Total Travel Time
Displays the amount of driving time for the vehicle.
Total Wait Time
Displays the amount of time the driver spends waiting at a customers to make
the delivery window. In many situations, a driver may actually arrive early at
a specified location, but may have to wait some time before the delivery
window begins.
Total Service Time
Displays the total amount of time the driver spends servicing the stops.
Total Run Time
Displays the total amount of time the vehicle spends on the road. This will be
equal to the amount of time between the return time and start time. Total Run
Time is comprised of three components: travel time, wait time, and service
time.
Pref Run Time
Displays the preferred runtime established as a wave limit.
Max Run Time
Displays the maximum runtime for the route established as a wave limit.
Addtl Distance
Displays the amount that total distance has increased as a result of adding the
incoming order to the delivery window.
Total Distance
Displays the distance (in hundredths of miles) that is traveled by the vehicle.
This distance includes the distance from the depot to the first stop, and the
distance from the last stop back to the depot.
1274

Column
Description
Total Quantity Size 1 Size 3
Displays the total quantity of product delivered by the vehicle for that size
notebook.
Total Pickup Quantity

Size 1 - Size 3
Displays the total quantity of product picked up by the vehicle for that size
notebook.
Capacity Size 1 - Size

3
Displays the quantity of product that the vehicle can handle for that size alias.
notebook.
Wave Vehicles Used
Displays the number of vehicles in use for the wave.
Wave Vehicles
Displays the number of vehicles available for the wave.
Wave Orders Taken
Displays the total number of confirmed orders in the delivery wave.
Wave Qty Ordered

Size 1 - Size 3
Displays the total quantity for all confirmed orders in the delivery wave for
that size alias. The column headers reflect the size aliases established in the
Options notebook.
Importing Individual Orders into Cost Analyzer
If you are using Cost Analyzer to test your web application, to determine the feasibility
of moving into a new delivery area, or to determine the cost of delivering to a new area,
it may be easier to create orders in a database and then import them into Cost Analyzer.
Before importing the orders, Cost Analyzer purges all existing orders and deletes all
delivery wave and window instances, so you can rerun the import without having to delete
existing information. Before importing the orders, you must have created delivery areas,
waves, and windows for this customer, and established an ODBC connection for the
database containing the orders. When you import orders, it can include orders that are
locked or unlocked on a route.
Important: When creating orders for the same location, make sure you enter a unique
order number for each order. netScheduler does not allow multiple orders to have
the same order number for the same location.
Note: When you are creating the database of orders to be imported, the tables must
contain at least these pieces of information, with the columns named as shown
below.
Column Name
Description
Region_ID
The ID of the netScheduler region. This is a required piece of

information.
Import_Index
The order sequence when placing them on a route.
Order_Number
The orders unique ID. This is a required piece of information.
Operations Guide
1275
Column Name
Description
Description
The shoppers name or ID. This information is optional, but the

column must exist.
Location_ID
The unique identification of the location.
Location_Type
The type of location such as DPT for Depot or SIT for site.
Latitude
The latitude of the shoppers location. Enter in ten thousandths of

degrees without the decimals, include the negative, if appropriate.
This is a required piece of information.
Longitude
The longitude of the shoppers location. Enter in ten thousandths

of degrees without the decimals, include the negative, if
appropriate. This is a required piece of information.
Order_Quantity_Size 1, Size 2,
Size 3
The amount being delivered for that size alias. This is a required
piece of information.
Pickup_Quantity_Size 1, Size 2,
Size 3
The amount being oicked up for that size alias. This is a required
piece of information.
Service_Time
The amount of time required to make the delivery, in seconds.

This information is optional, but the column must exist.
Order_Type
The classification for the order; this information is used for

filtering orders. This information is optional but the column must
exist.
Import_Movable
The order will not be locked when imported.
Import_Set_All_Unmovable
This order, and all orders preceding it since the last

Import_Set_All_Unmovable, are locked in the first route they are
placed on. For example, if you import 10 orders that are unlocked,
but the 11th order imported is set to locked, then the 10 previous
orders are also set to locked.
Delivery_Window_Start
The starting time for the delivery window.
Delivery_Window_End
The ending time for the delivery window.
Import_Activities
The list of activities that must be completed for the order. If you
have multiple activities, place a comma between each one. This
information is optional, but the column must exist.
Step 1: Click on the Cost Analyzer icon. The Cost Analyzer opens with a map.
Step 2: To display all orders in a selected delivery area and date, do one of the
following as needed.
new date in the Planned Date field. You can type in the date, or click on the arrow
to open a calendar. If you are using the calendar to change the month, either use
the arrows on top of the calendar to scroll through the months, or click on the
1276

To change the delivery area, click on the [Date] button on bottom of the module:
the Filter Data for Viewing window opens. In the Areas section, click on Specific,
then click the arrow and select the desired delivery area. To view the orders for all
delivery areas, click All.
Step 3: Click on the Action menu and select Import Orders. The Import Orders window
opens.
Step 4: Click on the Input tab.
Step 5: Enter the ODBC connection name in the Data Source Name field, and the
name of the table containing the orders in the Table Name field. If necessary,
enter the user name and password to access the database.
You can import orders into Cost Analyzer to simulate order taking throughout the day.
Hint: If orders from the table have previously been imported, click on the arrow and
select the table name from the list that opens.
Step 6: Enter the percent of orders to reserve before running the route builder in the
Percent of Orders to Reserve before rebuilding routes field. The route builder
will run each time this percentage of orders is reserved. For instance, if you have
100 orders and set the percentage to 20, the route builder will run after every 20
orders are imported.
Operations Guide
1277
Step 7: Specify how the delivery windows should be assigned.

Check Random to have the delivery windows assigned randomly to the orders.
This option most closely simulates actual customer ordering.
OR
Check Supplied to have the delivery windows assigned the orders according to the
order they were supplied.
OR
Use the slider bar to specify whether to use assign the delivery windows using the
lowest possible cost (best), or highest possible cost (worst), or in-between.
Step 8: Check the Purge Orders Before Importing box if you want orders purged before
importing new orders.
Step 9: Check the Show Costs After Importing box to have the Costs page
automatically move to the front after the orders are imported, if desired.
Step 10: Click the [Import] button. The import process begins.
If any of the orders cannot be reserved, the Failed Order Reservation window
opens, listing why the order could not be included in each time window. Click the
[OK] button to continue importing the orders. To prevent this window from
appearing again during this import, uncheck the If another reservation fails, show
this dialog box.
Once the orders are imported, you can use the Costs page to determine the number of
vehicles used, the cost per order, and other information you may need.
Note: If you want to remove orders without importing new orders, select Purge Orders
from the Action menu. All order information, as well as the delivery windows and
instances, are removed.
Importing Batches of Orders into netScheduler
netScheduler includes a Cost Analyzer tool that can be used to establish the filter limits
or simulate potential orders. When you select a location to analyze, Cost Analyzer lets you
know the overall costs associated with adding the order to each delivery window, as well
as the additional time and distance associated with delivering to that location.
Before importing the orders, Cost Analyzer purges all existing orders and deletes all
delivery wave and window instances, so you can rerun the import without having to delete
existing information. Before importing the orders, you must have created delivery areas,
waves, and windows for this region, and established an ODBC connection for the
database containing the orders. When you import orders, it can include orders that are
locked or unlocked on a route.
1278

Important: When creating orders for the same location, make sure you enter a unique
order number for each order. netScheduler does not allow multiple orders to have
the same order number for the same location.
Note: If you do not use Cost Analyzer to import or purge your orders, you can use Web
Services. The calls are SchedulerBulkReserveOrders for importing and
SchedulerPurge for purging. Refer to the Web Services Reference Guide for more
information.
Step 1: Click on the Cost Analyzer icon. The Cost Analyzer opens with a map.
Step 2: To display all orders in a selected delivery area and date, do one of the
following as needed.
new date in the Planned Date field. You can type in the date, or click on the arrow
to open a calendar. If you are using the calendar to change the month, either use
the arrows on top of the calendar to scroll through the months, or click on the
To change the delivery area, click on the [Date] button on the bottom of the
Specific, then click the arrow and select the desired delivery area. To view the
orders for all delivery areas, click All.
Step 3: Click on the Action menu and select Import Orders. The Import Orders window
opens.
Step 4: Click on the Bulk Import tab.
Operations Guide
1279
Step 5: Enter the ODBC connection name in the Data Source Name field, and the name
of the table containing the orders in the Table Name field. If necessary, enter the
user name and password to access the database.
You can import a group of orders into Cost Analyzer that already has an established
delivery window.
Hint: If orders from the table have previously been imported, click on the arrow and
select the table name from the list that opens.
Step 6: Enter the Number of batches to send to the system. For example, if you have
100 orders and you enter 4 in the Number of batches to send field, the system will
send 4 batches of 25 orders each.
Step 7: Check the Purge Orders Before Importing box if you want orders purged before
importing new orders.
Step 8: Check the Show Costs After Importing box to have the Costs page
automatically move to the front after the orders are imported, if desired.
Step 9: Click the [Import] button. The import process begins.
Once the orders are imported, you can use the Costs page to determine the number of
vehicles used, the cost per order, and other information you may need.
Note: If you want to remove orders without importing new orders, select Purge Orders
from the Action menu, or if you use Web Services to purge your orders, enter
SchedulerPurge. Refer to the Web Services Reference Guide for more
information. All order information, as well as the delivery windows and instances,
are removed.
1280

Columns in the Import Orders Window

When you import orders for individual orders or batches, certain information may be
returned. These are orders that failed to make it on a route due to delivery vehicles not
being available, etc. The columns in the Input or Bulk Import window, and a brief
description of the contents of each window, are included in the table below.
Column
Description
Order Number
Displays the orders unique ID. This is a required piece of information.
Description
Displays the shoppers name or ID. This information is optional, but the
columns must exist.
Order Type
Displays the classification for the order; this information is used for filtering
orders.
Displays the amount of product being delivered for that size alias. The
Displays the quantity of product picked up by the vehicle for that size alias.
notebook.
Service Time
Displays the amount of time needed to service the stops.
Window Start
Displays the starting time for the delivery window.
Window End
Displays the ending time for the delivery window.
Reject Reason
Displays the reason why an order was rejected during the import process.
Below is a brief description of each column in the Costs tab of the Import Orders window.
The cost information on this window is associated with the orders that are on routes.
Column
Description
Start Time
Displays time the delivery waves start.
Color
Displays the color associated with the delivery wave. On the map, the route
path will be displayed with this color and in the List window.
Vehicles
Displays the number of vehicles used for the delivery wave.
Available Vehicles
Displays the number of vehicles left to be used for additional routes to be

created for the delivery wave.
Orders
Displays the number of orders associated with the delivery wave.
Total Cost
Displays the total cost for the route. The cost is calculated using the driver
and equipment costs.
Cut Off
If a date is displayed, it is the cutoff for the same day as the deliveries. If there
is no date, no orders will be accepted after the specified time on the previous
day.
Operations Guide
1281
Max Run Time
Displays the maximum runtime for the route established as a delivery wave
limit.
Preferred Run Time
Displays the preferred runtime established as a delivery wave limit.
Depot Type
Displays the type for the routes origin. Normally, this would be DPT.
Depot ID
Displays the unique identifier for the routes origin.
Hourly Wage
Displays the amount the driver is paid per hour.
OverTime Hourly
Wage
Displays the amount the driver is paid when working overtime. Once the
routes total runtime exceeds the hourly wage duration, the driver costs will
be calculated using this wage.
Regular Wage Duration
Displays the amount of time the driver is paid the hourly wage. If the route
extends beyond this time, any additional time, the driver will be paid at the
overtime wage.
Historical Travel
Speeds
If the checkbox is marked, then the historical traffic data is being used when
creating routes.
Rush Hour Model
Displays the rush hour model, if any, that is being used. The rush hour model
can affect the travel times that are calculated.
Advanced Rush Hour
If the checkbox is marked, then the advanced rush hour model can be used.
The advanced rush hour model can affect the calculated travel times.
Time of Day Restriction

Model
Displays the time of day restriction model, if any, that is being used. The time
of day restriction model can restrict travel in defined areas during defined
times.
Equipment Type
Displays the equipment type that is set up for the delivery wave.
Size 1 - Size 3
Displays the quantity of product for the delivery wave for that size alias. The
Outbound Stem Time
Displays the time it takes to travel from the depot to the first delivery stop.
Enter the time as HH:MM.
Inbound Stem Time
Displays the time it takes to travel from the last delivery stop back to the
depot. Enter the time as HH:MM.
1282

Glossary and Index

Glossary
Glossary
A
Absolute Calculation MethodFor billing, payroll, and variance reports, you can
customize how MobileCast calculates track types. For example, if your payroll
system is set to compute a 15 hour route at an even hourly basis, meaning the
driver would be paid one flat rate per hour, then you would use this method.
Account TypeA way to group locations by a common trait, such as a chain of fast-food
restaurants or locations that require COD payment.
Actual DataInformation, usually based on driver feedback and/or onboard computers,
that reflects service time history and comments pertaining to particular routes or
stops. This information is crucial when updating service times.
Actual TemperatureFor perishable loads, you can track four different temperatures by
typing them in the Actual Temperature area of the Add Load Stop and Edit Load
Stop windows:
Unit Set is the temperature set on the equipments thermostat.
Unit is the actual temperature inside the equipment.
Pulp Low is the lowest temperature measured when samples were taken in the load.
Pulp High is the highest temperature measured when samples were taken in the load.
Administrative RouteAn unplanned route in MobileCast that is typically used by sales

or merchandising teams. This type of route is automatically created as the
employee travels from location to location. The position data from each location
is stored and then sent from the Java-enabled phone to MobileCast. There are two
different types of Administrative Routes:
Passive Routes require little interaction with the Java-enabled phone. All the
employee needs to do is start and complete the route.
Non-Passive Routes require frequent interaction with the Java-enable phone. The
employee must arrive and depart from each location that they stop at as their route
progresses.
Advanced Rush Hour AreaA rush hour area that has a speed variation that depends
on road class. Advanced rush hour areas can only be used in a session if Advanced
Rush Hour is selected.
ADPShort for Automatic Data Processing Inc., a company that generates payroll. You
can use MobileCast to generate payroll information to send to ADP.
AliasA region-specific name for certain route data, such as the quantities carried on the
route.
Ambiguous Order PairA possible order pair, but there is a rule broken that is
preventing it from being considered an order pair. Usually, it means there are three
Operations Guide
1283
or more orders with the same order number, or there are two orders with the same
order number but the same order type (both pickups or both deliveries).
AreaAreas through which your equipment travels.
Area DistanceThe miles driven within a region.
AssignWhen you know what you want to do with a load, you are ready to assign it. You
can assign a load from either the Active list (if you have claimed it earlier), or
directly from the Available list. To assign a load, right-click it, click Assign to
from the pop-up menu, then select where you want to put the load: on an existing
route, on a new route, or with a common carrier.
AvailableA load is placed in the Available list when it is created. An available load can
be claimed or assigned by anyone who can see it. You can see a load in the
Available list if you created it, the region who created it gave you access to it, or
you have load admin rights.
B
Bay PreferencesIndicates which package types are preferred for an individual bay.
Bay TypeDefines the types of bays available on the trucks by determining the amount
and type of product that can fit into a given bay.
BarrierValid only when the XY routing method is being used. A barrier accounts for
any impediment between two points, such as a mountain, body of water, etc.
Bill ToBill Tos represent companies who will be billed for the loads. They are created
in the Setup module. You must have at least one Bill To set up before you can start
creating loads. Each region has its own list of Bill Tos, unless you choose to allow
other regions to use a Bill To when you create it.
BreakA period of time on a route when the driver and vehicle are stationary. A break
can be paid or unpaid.
Building Delivery SequenceA number indicating the sequence the location should be
delivered in relation to other locations on the same route with the same latitude
and longitude.
Bulk DeliveryA delivery in which the pieces delivered contain a quantity of smaller
pieces, i.e., a pallet.
Bulk Fixed Service TimeThe amount of time, independent of the quantity of product
delivered, that it takes to service a location when making a bulk delivery.
Bulk Variable Service TimeThe amount of time it takes to deliver one bulk item, such
as a pallet.
C
Calculate Percent EmptyThis feature helps you manage your loads by allowing you
to check how much space a piece of equipment has available at each stop during
a route.
1284

Cancel Stop CodesYou can set up these codes so your driver can easily relay a
message back to the dispatcher stating why the stop was canceled and is
undeliverable at the scheduled time. A canceled stop remains part of the planned
route.
CellA user-defined area used to divide a delivery area into smaller segments.
ClaimWhen you claim a load from the Available list by right-clicking it and clicking
Claim, you are taking responsibility for the load without putting it on a specific
route. The load is then removed from the Available list and shown in the Active
list for your region. If you want to select an available load and put it on a route
immediately, click Assign to from the pop-up menu, instead of Claim.
Close TimeThe latest possible time a location can accept a delivery.
Commodity TypeCommodity types refer to the kinds of products, such as FRUIT or
CATTLE, that make up loads. A commodity type is created by a load admin in the
Setup module, and can then be used by all regions.
Common CarrierA common carrier is an outside company to which a load can be
assigned, if you dont want to assign it to your own routes or transfer it to another
region. Information about common carriers, such as names and addresses, is
entered by a load admin in the Setup module. The common carrier can then be
used by all regions.
CompleteWhen a stop, route, or load is delivered, it is complete. Complete items are
removed from the Active list; to see a complete item, search for it by clicking
Query from the Dispatcher modules Route or Load menu.
Critical RouteA route with unacknowledged exceptions in the Dispatcher. If a route is
critical, a yellow light is displayed in the Route Summary window.
Cycle WeeksThe length of a planning session in Territory Planner. The maximum
number of cycle weeks is 24.
D
Database MaintenanceA way to archive and delete data to keep your database from
getting too large.
Delay TypeA reason the driver is late, such as traffic or weather. Delay types are used
for reporting purposes only.
Delivery AreaA conceptual grouping of orders for scheduling. The customer
determines what an area is and which area an order belongs to. Generally, an area
represents a geographic region based on zip code or latitude/longitude. This
applies to netScheduler only.
Delivery RouteA pre-planned route in MobileCast that is typically used by drivers for
delivery or pickups.
Delivery WaveA time range in which an order can be delivered. This applies to
netScheduler only.
Operations Guide
1285
Delivery Wave InstanceThe actual attributes that are used for routing after the first
order is placed for a specific date.
Detail LevelThe amount of detail being tracked for a route (stop, order, line item). The
detail level is set in the Options notebook.
Distance ModelUsed for the XY routing method, the distance model multiplies the
straight-line distance between two points by a factor that accounts for road
variations.
Download FileA text file containing the orders to be routed for delivery.
Driver AdjustmentDriver adjustments can be used if certain drivers are paid more or
less for a track type than the amount that would ordinarily apply. To use this
feature, you must already have driver types created. The driver adjustment is per
unit: mile, hour, pallet, day, or whatever the track type applies to. When that type
of driver runs a route, billing and payroll will be increased or decreased by the
appropriate dollar amount.
Driver AlertsIf you are using wireless communication, you can set up an alert to
remind the driver of a task that has been associated with a stop. For instance, if the
stop is a COD account, you can set up a COD driver alert and associate it with the
stop. And, you can set up alerts for specific items on an order. For instance, if the
driver is delivering alcohol, an alert can flash reminding the driver to check for ID.
Driver FriendlyA strategy in the Loading Editor that loads the truck by stop sequence.
The system sorts the orders by stop number and groups them together on the truck.
The last stop to be delivered will be loaded first. A high priority of this strategy is
keeping stops together on the truck; it will not split a stop unless the stop will not
fit in one bay. If the entire stop will not fit on the truck, the stop will not be loaded.
This method ignores the package type preferences specified in the Maintenance
module. If stack rules are selected, product that violates a stack rule will not be
loaded.
Driver ProductivityArea to enter actual information about how long it took for a
worker to deliver each route. This information is used for productivity reporting.
Driver ShiftThe European term for a drivers work shift. A driver shift may take place
over more than one calendar day and can include multiple duty periods.
Driver TypesDriver types are used to differentiate between levels of drivers for
payment purposes. For instance, you could have a driver type for a trainee and
another one for senior drivers.
Drop and HookA situation in which two routes meet to exchange some equipment,
usually a trailer. The routes must meet at a common location for the drop and hook
to occur.
Dropped OffMeans that a piece of equipment is left somewhere to be picked up at a
later date. MobileCast can track where equipment is dropped off so that it is not
inadvertently assigned to another route.
Duty PeriodA block of work time that is not interrupted by any time where the driver
is off duty. When a driver goes off duty for any reason, the duty period ends and
1286

a new on duty period will begin when they go back to work. There can be multiple
duty periods for each route or shift. For example, if a driver takes a lunch break
that is considered to be off duty, the driver will have one duty period for the time
worked before lunch and a separate duty period for the time worked after lunch.
You can specify whether or not time spent on activities such as breaks, waits, and
layovers is considered off duty on the Duty Period Monitor page of the
Dynamic RouteA route created based on geographic criteria as well as user-defined
parameters.
E
EmployeeAny worker tracked through Roadnet, such as drivers, helpers, etc.
Employee StatusA way to track the availability of employees. Employees could be
available, or they could be on vacation, or in training.
Employee TypeEmployee types allow you to classify the types of employees in an
organization, such as administrative or driver or dispatch. Employees can be
associated with types when they are added in the Setup module. Each employee
type you create is available to all your regions.
EmployeesEmployees are those workers who are tracked through and use MobileCast,
such as drivers and dispatchers. Employees can be shared between regions, and
employee types must be added before you can add any employees.
EquipmentTractors, trailers, and other vehicles used to transport product on the route.
Equipment OverrideA way to change the equipment assigned to the route. If a route
being downloaded has been assigned a piece of equipment with an override, the
equipment assigned to the route will be switched to the override equipment. The
override equipment is used for all instances of the route in FleetLoader.
Equipment StatusA way to track the availability of equipment. Equipment could be
ready or it could be in use.
Equipment TypeThe different types of equipment you have, such as tractors, trailers,
or refrigerated trucks.
EventWhen using wireless communication, an event is any message passed between
the driver and MobileCast.
F
Fixed FeeThe fixed fee is the fee for reloading or emptying at that particular location.
The total fee of the location is the fixed fee plus the variable fee, and it will be
applied to the route cost every time the location is used.
Fixed Service TimeThe amount of time, independent of the quantity of product
delivered, that it takes to service a location.
FleetLoaderA decision-making and reporting tool designed for managers, routers, and
others involved in the truck-loading process.
Operations Guide
1287
Freight ClassesFreight classes are used to group similar commodities to determine

things such as packing, shipping, pricing, and overall transportability. Freight
classes are only used with loads.
FuturesOrders that require products to be delivered at a future date. Futures are only
used with Roadnet.
G
GeocodeThe geocode assigns a latitude and longitude to a location, which is then used
place the location on the map. The geocode is based on the address information
you enter for the location.
Global PenaltyA penalty associated with the entire map. Global penalties are assessed
based on the selected road classes passing through the node, and can be removed
for individual nodes. Global penalties can be used if you want to assign a time
penalty to a specific type of turn.
GPS (Global Positioning System)GPS determines the specific latitude and longitude
for a location.
GPS PlaybackIf you are using a wireless device with GPS, and the device is sending
GPS information throughout the day, then you can play back the route and see
where the driver has been during the entire day. You can only use the GPS
Playback from the Position History window located in the Dispatcher.
Graduated Calculation MethodFor billing, payroll, and variance reports, you can
customize how MobileCast calculates track types. For example, if you have a 15
hour route and your payroll system requires the first 10 hours of a route to be paid
at one rate, and the last 5 hours to be paid at another, then you would use this
method.
H
Hours of Service RulesA set of rules used in North America that regulate the length
of time that drivers can work and how much rest they must get.
Hybrid (Driver First)A strategy that loads the truck by the Driver Friendly method
first, based on a user-defined quantity threshold for a location ID (stop) and/or the
specified selector. Stops whose total quantity exceed the threshold, and/or are
assigned that selector, will be loaded Driver Friendly; stops whose total quantity
is less than the threshold will be loaded Warehouse Friendly. The selector is
downloaded with the orders file.
Hybrid (Warehouse First)A strategy that defined the truck by the Warehouse
Friendly method first, based on a user-defined quantity threshold. Any SKUs with
a total quantity greater than the threshold will be loaded WareHouse Friendly;
SKUs with a total quantity less than the threshold will be loaded Driver Friendly.
1288

I
ImpasseA barrier placed on a single street segment, preventing traffic from proceeding
down the segment. When calculating the path between two points, Roadnet will
bypass the segment with the impasse.
Import LayoutLocation, location extension, order and onboard computer information
can be imported from a host or another computer into the Roadnet Transportation
Suite. This information is stored in separate tables, but the information can be
contained in just a few files. For the information to be accepted and placed where
it can be accessed and used, you must tell the Roadnet Transportation Suite where
to find the information in the import files. The table layouts are used to
communicate this information to the Roadnet Transportation Suite.
Import Layout SetsImport layout sets let you group your import layouts, allowing you
to create separate sets for various importing situations.
J
K
L
LayoverWhen the driver and vehicle are stationary for an extended amount of time. A
layover can be paid or unpaid.
Line ItemA delivery or pickup item, such as a case of soda.
LoadHow to put product into a truck.
Load AdminThis refers to a level of rights for MobileCasts load-management
features that is greater than those of a normal load user. Load rights are set for a
user in the Users module. In the Dispatcher module, a load admin can create new
loads and see all loads, no matter which regions might have claimed them. In the
Setup module, a load admin can add and change bill tos, commodity types,
common carriers, load locations, and load types.
Load Front to RearAn option in the Loading Editor that loads the truck starting from
the cab and working toward the rear of the truck.
Load IDWhen you create a load, MobileCast automatically creates a unique Load ID
for it. You also have the option to enter your own Reference ID for the load. You
cannot change the Load ID, but you can see it in the Load ID column of the Loads
- Active, Loads - Available, and Load Query lists. You can change or delete the
Reference ID.
Load LevelingAn option in the Loading Editor that tries to load the truck evenly from
side to side and front to back.
Load LocationLoad location are not the same as regular stops on a route, although they
are set up similarly, either in the Setup module or when you create a load. On a
load, a location is either a pickup point, a delivery point, or a meet point (where a
load is transferred to another route). The same load location can be a pickup point
for one load and, say, a delivery point on another load.
Operations Guide
1289
Load PhasesWhat you can do to a load depends, in part, on the phase it is in. The
phases are shown in the Phase column of the Loads - Active, Loads - Available,
and Load Query lists. Depending on the type of loads you have and the list
window you are looking at, you might see any of the following phases:
Assigned
Available
Claimed
Complete
Transferred
Loading PreferenceAllows you to restrict the area of a truck where a particular

locations orders will be loaded.
Load ProductivityArea to enter actual information about how long it took for a worker
to load each bay. This information is used for productivity reporting.
Load TypeA load type can be assigned to a load when it is created to help identify the
category of a load, for example, Ad Hoc. Load Types are created by a load admin
in the Setup module, and can then be used by all regions.
Load UserA level of rights set for a user in the Users module. In the Dispatcher
module, load users can create new loads and see (a) loads they have created, (b)
loads that others have created but they are allowed to claim, (c) loads they have
claimed, and (d) loads that have been transferred to their region from another
region. Unlike load admins, load users cannot see loads that others have claimed.
In the Setup module, a load user can add and change bill tos and load locations.
LocationAnywhere you might send a piece of equipment, such as the customers you
deliver to, the depots you use, the vendors from whom you purchase product, etc.
Location ExtensionAdditional information about a location that is specific to a
planning session. Each location extension has a delivery quantity and service
pattern set.
Location OverrideAllows you to override time windows and/or special instructions
for a location. This feature will nullify time window overrides and special
instructions established in the Add Location Notebook.
Location Preference LoadingAn option in the Loading Editor that loads the product
for defined locations into predetermined areas of the truck.
Location SubstitutionAllows you to assign one location address to two or more
locations.
Location TypeThe types of places the route stops, such as a depot or a site.
Lock OrderSetting an order to lock ensures that the order will not be moved from its
current route to another route.
1290

M
Meet PointA load location where two routes meet to pass on the load. Meet points are
added or changed by right-clicking an active load that has already been assigned
to a route, then clicking Edit Relays.
MerchandiserA person who visits locations on a route and sets up displays relevant to
product delivered.
Message CenterIf you are using wireless communications, the Message Center allows
you to easily know when a text message is received from the driver or if the system
is not functioning properly, so that you can respond quickly to any problems that
may have occurred.
Mix RulesUsed to prevent two SKU brands from being loaded in the same bays on the
equipment.
Mid-Route DepotThe location that is used to pickup additional product, or to drop off
product.
ModuleAn individual section of MobileCast. The modules can be run simultaneously.
N
netSchedulerTerm referring to the scheduling components of the Roadnet
Transportation Suite. Scheduling is implemented in the Transportation Suite Web
Service, Day Commander, and Cost Analyzer.
NodesA street network is composed of street segments that are then connected by
nodes. Nodes can be edited to restrict traffic from passing from one node to the
next, or, if the node represents an intersection, assess a time penalty for traveling
through the node. Nodes appear on the map in various colors, depending on the
characteristics associated with them.
Black nodesIndicates that there are no restrictions.
Grey nodesIndicates that no turn is possible.
Blue nodesIndicates an overpass, underpass, or other physical restriction.
Red nodesIndicates a turn restriction.
O
Obey No-Mix RulesAn option in the Loading Editor that follows the no-mix rules
specified in the Maintenance module.
Obey Stack RulesAn option in the Loading Editor that follows the stack rules
specified in the Maintenance module.
Open TimeThe earliest possible time a location can accept a delivery.
Optimization PassAn option in the Loading Editor that loads any product not already
loaded into the first available bay. A bay is considered available if loading product
into it does not violate any established rules.
Operations Guide
1291
OrderProduct that a location has ordered. An order can consist of a single or multiple
SKUs or line items, and a location may receive one or more orders.
Order PairThe two orders that represent the same shipment at the pickup and delivery
locations. One order must be a pickup and the second order must be a delivery.
Organization UnitA set of regions that define a companys organizational structure.
P
Package TypeDefines the various types of packages loaded on your equipment, such
as 12-ounce cans or 2-liter bottles.
Paired OrderAn order that is part of an order pair.
Pallet LoadingAn option in the Loading Editor that prevents a pallet worth of an
SKU from being split between bays.
PassA creation of routes based on criteria you select.
PenaltyA time associated with performing an action in a node, such as a turn.
PermissionA part of the Roadnet Transportation Suite the user can access.
PhaseWhat you can do to a load depends, in part, on the phase it is in. The phases are
shown in the Phase column of the Loads - Active, Loads - Available, and Load
Query lists. Depending on the type of loads you have and the list window you are
looking at, you might see any of the following phases:
Assigned
Available
Claimed
Complete
Transferred
PickupProduct you previously delivered to a location that they are returning. A pickup
is not the same as a load.
Planning SessionA complete routing problem in Territory Planner. Each routing
session has a list of location extensions to route, as well as a period of time it
covers.
Position History If you are using a wireless device with GPS, you can view on a map
the path and history of a route or piece of equipment.
Power UnitA self-propelled piece of equipment, such as a tractor. A power unit must
be assigned to each route.
Preference PassAn option in the Loading Editor that loads package types in bays with
preferences first.
PreprocessorA batch or command file run on a test file before the information is
imported into MobileCast.
PrivilegeA group of permissions. Users/user groups are granted privileges within each
region.
1292

Q
R
Rear BayA truck that can only be accessed from the back and not the sides.
Reason CodesYou can set up reason codes to relay information from the driver to the
dispatcher explaining why an actual delivery quantity does not match the planned
quantities. For example, if some of the merchandise is damaged and therefore
refused, the driver can select a reason code explaining why the delivery quantity
is less than planned.
Reference IDYou can enter an optional reference ID when you create a load to help
you identify it. The reference ID can be any combination of numbers, letters, and
spaces, up to 15 characters. In addition, MobileCast creates its own load ID for
each load that cannot be changed or deleted.
RegionA routing organization that has its own resources (drivers, equipment, etc.) and
manages its own routes. For instance, you may set up each of your depots as a
region. Within each region, users/user groups can have different privileges.
Regions can also be grouped into organization units.
RelayRelaying a load means passing it on to another route. To set up or change a relay,
right-click an assigned load in the Active list and click Edit Relays, to bring up the
Load Assignment window. Each route involved in relaying the load has a separate
tab in the Load Assignment window, and the places where relays occur are
indicated by the Meet Point symbol
in the Type column. You can change any
load location to a relay except for the first load location on a route.
ReloadA second loading of the truck at the depot, at which time the driver assumes a
new route to complete the days schedule.
Report WriterA tool, such as Crystal Reports, used to generate reports. Report writers
allow you to create your own reports for MobileCast.
Reserved OrderReserving an order ensures that no other order takes its time window
slot. The length of time the reservation is kept is set in Maintenance. This applies
to netScheduler only.
Restricted EquipmentEquipment types that are marked as restricted and that have to
obey the time of day travel restrictions.
ReturnIf you have claimed a load or had one transferred to you and you realize you
will be unable to work with it, you can return it back to the list of Available routes
or back to whoever transferred it to you. Returning a route lets someone else run
it. This is only used with MobileCast loads.
RevenueWhen you create a route, you have the option to enter the estimated amount
you are going to bill for the load in the Revenue text box. You can change the
amount later from the Edit Load window.
Reversed Order PairAn order pair that is sequenced so that the delivery occurs before
the pickup. In the Routing Editor, a reversed order pair will be considered a
Reversed Order Pair stop exception.
Operations Guide
1293
RouteA single route a driver makes to visit locations.

Route ExceptionAn exception that indicates if a route has met or exceeded the defined
guidelines.
Route Exception RuleDefines the conditions that will cause an exception; routes that
satisfy these conditions will trigger an exception and show in Dispatcher.
RouteNetA routing method that uses maps to reflect in detail the area being routed.
Routing SessionA complete routing problem that includes all the components
necessary for completing your routing. A routing session typically occurs once per
day.
Route StatusThe state of the route, such as delayed or on time.
Route TypeA way to classify the type of load on the route, such as refrigerated or
flammable.
Rush Hour AreaAn area drawn on the map which has unique speed variations during
the rush hour time periods.
Rush Hour ModelA feature that allows you to affect the travel times between two
points during defined times of day. You can create rush hour areas and rush hour
paths for the model that define any speed variations or road direction changes for
that area/path.
Rush Hour PathA path drawn between two points on the map which has unique speed
variations and/or road direction changes during the rush hour time periods.
S
ScenarioA way to globally alter service times and time windows for a routing session
based on any circumstance, such as a snow day, holiday, etc.
SealUsed if crossing borders; the unique number sealing the load.
Search ManagerThe Search Manager allows you to search for specific entries in a
window. You can use this feature to find entries that need to be edited, or to find
entries you want to include in a report.
SegmentAny of the lines on a map representing the roads on which the driver will be
traveling.
Separated Order PairAn order pair where the pickup and delivery are on different
routes. In the Routing Editor, a separated order pair will be considered a Separated
Order Pair stop exception.
Service FailureA way to notify the customer if the route is delayed beyond a certain
time specified when the location is set up. You can choose several methods for
MobileCast to notify the customer, including e-mail, fax, and pager.
Service MonitorThe Service Monitor is part of the Message Center, and provides you
with a list of service applications, allowing you to see whether or not a certain
application is responding at the current time.
Service PatternA single delivery option used in Territory Planner.
1294

Service Pattern SetA group of service patterns used to define delivery options for a
location extension in Territory Planner. You can specify different service patterns
for different delivery quantities.
Service TimeThe amount of time it takes to service a location.
Service Time MaintenanceA way to update service times based on actual data from
your delivery history.
Service Time OverrideA way to change the service time for a location on a specific
day(s) without affecting other days of the week or other locations.
Service Time TypeA way to group your locations according to service time.
Shuttle DistanceThe distance it takes to travel from the previous linked routes
destination to the current routes origin.
Shuttle TimeThe time it takes to travel from the previous linked routes destination to
the current routes origin.
Simple Rush Hour AreaA rush hour area that has speed variations that apply to all
streets in the area.
Size PrecisionThe number of digits to the right of the decimal point for quantities. For
example, if you want to enter a quantity of 9.0025, then enter the number 4 in the
Size Precision field on the Unit Reference Page of the Options Notebook. The
default is 0, but you can have as many as 6 digits after the decimal point.
SKUThe most specific way to define your products by combining an SKU brand and
package type.
SKU BrandThe name of any of the various products delivered.
Small SKU LoadingAn option in the Loading Editor that loads SKUS with userdefined small quantities into predefined bays.
Stack RulesRules that prohibit a specific package type from being stacked on another
package type. For example, a rule may prevent cans from being stacked on bottles.
Standard RouteA route that contains specific locations in a fixed sequential order.
Static RouteA route that is frequently run with the same stops can be made a static
route. This prevents you from having to import the route from the routing software
every time it needs to be run.
Static Route SetA collection of static routes.
Stop Quantity LoadingAn option in the Loading Editor that loads the truck from the
largest stop to the smallest stop, instead of in reverse order.
Stop TypesStop types are special variations of track types used when you are billing
and paying according to the type of stops (locations) on a route.
Street SegmentsThe street network displayed on a map is composed of street segments
that are then connected by nodes.
SuperMatrixA method used to calculate travel times and distances. Like RouteNet,
the SuperMatrix uses actual map data to calculate the travel times and distances,
Operations Guide
1295
but the times and distances are calculated ahead of time, instead of when entering
an editor.
T
TerritoryUsed in Territory Planner to group location extensions, usually
geographically. After the territories have been created, routes are created from the
location extensions within each territory.
Time of Day RestrictionA restriction placed on certain equipment types not allowing
them on certain paths or areas during a specified time of day.
Time WindowThe range(s) of time during which a customer prefers to receive
deliveries.
Time Window OverrideA way to change the time window(s) for a location on a
specific day(s) without affecting other days of the week or other locations.
Time Window TypeDefines the different types of time windows that can be associated
with a location.
Tour of Dutythe North American term for a drivers work shift. A tour of duty may
take place over more than one calendar day and can include more than one route.
TripIndividual segments on a route separated by a depot. If the route is a reload that is
being viewed as a single route, or a depot was inserted on the route, the number
will be 2 or greater. Most routes will have 1 trip.
TripIn netScheduler, a sequence of stops on a route that are delivered before returning
to the depot to pick up more quantity. A route can have multiple trips.
Track TypeTrack types are used to hold accounting and operational information such
as mileage rates and stop charges. This information is combined with details from
specific routes to produce accounting reports.
TransferIn MobileCast, transferring a load means handing it off to a different region
because you cannot complete it. A load must be assigned before it can be
transferred. You transfer a load by creating a relay point that connects to another
region instead of another route.
Travel Time ModelUsed for the XY routing method, the travel time model calculates
speed based on the distance traveled between two points.
U
UnassignedsA pickup or delivery that has not been assigned to a route.
Undeliverable Stop CodesYou can set up undeliverable stop codes that the driver can
apply to situations in which a stop cannot be delivered. For instance, if an order is
refused, damaged, incorrect, etc., the driver can select the appropriate
undeliverable stop code to send to the dispatcher.
Unlock Ordersetting an order to unlock enables the order to be moved from its current
route to another route.
1296
User Any person in your organization who uses RoadNet, such as a router, dispatcher
to track routes and the associated data. Dispatchers are typical users.
Glossary
Unlock OrderSetting an order to unlock enables the order to be moved from its current
route to another route.
UserAny person in your organization who uses RoadNet, such as a router, dispatcher
to track routes and the associated data. Dispatchers are typical users.
User GroupA group of users who have the same privileges within a region.
User Defined FieldAn empty field you can use to track information unique to your
organization. There are three user-defined fields each for routes, stops, orders, line
items, loads, regions, locations, and other items.
V
Variable FeeThe variable fee is based on quantity and is used by the location to control
cost. For example, if the variable fee is 10, then the unit of cost for that location is
multiplied by 10 and added to the fixed fee to equal the locations total fee. The
total fee will be applied to the route cost every time the location is used.
Variable Service TimeThe amount of time it takes to deliver one unit of product to a
location.
Void LocationAllows you to prevent a specified location from receiving orders,
without removing the location from the database.
W
WaitA period of time on a route when the driver and vehicle are stationary in order to
meet a time window. A wait can be paid or unpaid.
Warehouse FriendlyA strategy in the Loading Editor that loads the truck with the
same SKUs together.
Where FunctionThis feature allows you to enter a date and time, and MobileCast will
determine the location of the driver at that time bases on the current stop
information available for the route. The Where Function can be used to determine
when a driver will be near an area for a drop and hook or an unexpected pickup.
Wireless EventsEach individual wireless message is called an event. Once a wireless
device is associated with a route, messages received from the driver automatically
update MobileCast. You can view the messages as they are sent and received for
the route, and even edit them if necessary.
Working Time DirectivesA set of rules used in the European Union that regulate the
length of time that drivers can work and how much rest they must get.
XYZ
XYA routing method that uses a straight line to measure the distance between two
points. This method relies on the Distance and Travel Time models to account for
road changes and speed variation.
ZonesA way to group locations together in dynamic routing so that they fall on the
same route(s).
Operations Guide
1297
1298

Index
Index
Numerics
3-Column Pick Sheet report 1008
A
About
menu option 1182
About this manual 5
Absolute calculation method
defining 1283
Account Type Summary 619, 624
menu option 1183
Account types 193
adding 193
adding in the Routing Editor 444
checking distribution among territories
604
checking distribution between
territories 619
defining 1283
deleting 193
distributing among territories 614
distributing between territories 614
editing 48, 193
explaining 112, 193
menu option 1179, 1184, 1188
Accounting in MobileCast
routes 883
track types 883
Active
menu option 1193
Activities
adding 170
adding to an order 156
adding to an order in the Dispatcher
822
assigning a service time 170
assigning to skill sets 172
deleting 170
displaying in the Routing Editor 459
editing 170
import layout 439

importing 372
importing into MobileCast 424
introducing 170
marking as complete in the Dispatcher
822
menu option 1179, 1188
Actual data
defining 1283
Actual data entry
actual route/stop 300, 302
actual vs. planned comments 298
Actual Route/Stop 300
entering actual route information 300
entering actual stop information 302
explaining 300, 302
menu option 1181
Actual temperature
defining 1283
Actual vs Projected Route Summary
report. See Actual vs Planned Route
Summary report
Actual vs Projected Stop Detail report. See
Actual vs Planned Stop Detail report
Actual vs. planned comments 298
adding 298
deleting 298
editing 48, 298
explaining 298
menu option 1181
Actual vs. Planned Route Stop Detail
report 941
Actual vs. Planned Route Summary 938,
940
Actual vs. Planned Route Summary report
938, 940
Actual vs. Planned Stop Detail report 941
Actual vs. planned stops
adding 298
Actual vs. projected comments. See Actual
vs. planned comments
Operations Guide
1299
Index
Actual vs. Projected. See Actual vs.

Planned Comments
Add Filter icon 1142, 1145
Add Stops
menu option 1189
Add Street Mode
menu option 1165
Adding
a delivery window 1260
a pallet to a bay in FleetLoader 738
account types 112, 193
activities 170
activities to an order 156
activities to an order in the Dispatcher
822
actual vs. planned stops 298
an individual delivery window 341
an ODBC connection 10
barriers 287
bay types 112, 117
breaks to a daily route in the Routing
Editor 554
breaks to a route in the Dispatcher 825
breaks to a route in the Planning Editor
655
breaks to standard routes in the
Routing Editor 484
business calendar 345
cancel stop codes 211
canned text messages 222
cell patterns 290
cells 293
common carriers in MobileCast 897
container types 223
containers 225
customer commodities in MobileCast
897
delay types 116
delivery areas 330
delivery waves 333
delivery windows 341
depots in Depot Planner 688
depots onto a route in the Planning
Editor 657
depots to standard routes 485
distance by jurisdiction entries 878

driver types 116
drivers 179
dynamic route IDs in the Routing
Editor 543
employee statuses 116
employee types 174
employees 175
equipment 130
equipment overrides 136
equipment statuses 116
equipment types 122
filters for netScheduler 339
financial details to an order in the
Dispatcher 820
freight classes in MobileCast 897
future orders in maintenance 151
items in the Planning Editor 589
items in the Routing Editor 444
layovers to a route in the Dispatcher
825
layovers to standard routes in the
Routing Editor 484
line items in the Dispatcher 819
line items to an order 156
load locations in MobileCast 895
load related items in MobileCast 897
load rights in MobileCast 892
load to existing route in MobileCast
906
load to new route in MobileCast 907
load types in MobileCast 897
location extensions 237
location overrides 259
location substitutions 261
location types 235
locations 237
maintenance items 48
mid-route depot in the Dispatcher 828
mix rules methods 160
multiple delivery windows 342
notification recipients 32
onboard codes 191
order classifications 332
order financial detail codes 214
order status codes 216
1300

Index
orders 151
orders in the Dispatcher 819
organization units 44
overrides to an order 155
package types 141
pallet loading methods 167
pickups in maintenance 152
planning sessions 205
pre- and post-route stops to a route 536
pre- and post-route stops to a standard
route 477
preferred route properties 538
privileges 21
reason codes 209
region distances 308
regions 35, 188
reports 932
route exception rules 229
route statuses 116
route types 116
routes in the Dispatcher 811
routes in the Routing Editor 535
rush hour area 270
rush hour model 267
rush hour path 274
scenarios 194
scenarios to a route in the Dispatcher
812
service pattern sets 202
service patterns 200
service time types 195
skill sets 172
skill sets for netScheduler 340
SKU brands 140
SKUs 147
stack rules 165
stack rules methods 159
standard route sets in the Routing
Editor 474
standard routes to a set in the Routing
Editor 479
STCC codes in MobileCast 897
stop signature codes 213
stops to a route in the Dispatcher 813
stops to a standard route in the Routing
Editor 480
street segments 1165

survey questions 219
surveys 218
territories in the Planning Editor 625
time of day restriction area 281
time of day restriction mode 277
time of day restriction models 277
time window types 198
travel time models 186
unassigned stops in the Dispatcher 838
undeliverable stop codes 212
user defined landmarks 1164
user groups 26
users 28
void locations 262
waits to a route in the Dispatcher 825
waits to a route in the Planning Editor
655
waits to a route in the Routing Editor
554
warehouse zone pick order methods
162
warehouse zones 138
wireless devices 227
zones 189
Adding a route in the Routing Editor
setting the starting quantity 536
Adding a standard route in the Routing
Editor
setting the starting quantity 477
Address Path Mode
menu option 1176
Adjust radius
cancelled stops 794
adjust radius 794
Adjusting
a stops service time in the Routing
Editor 559
Administration 13
explaining the set up 13
setting the alias 46
working with organization units 44
working with privileges 21
working with regions 35
Operations Guide
1301
Index
working with the authentication policy

16
working with user groups 26
working with users 28
Administrative route
defining 1283
ADP
defining 1283
entering the ADP File Number 176
Advanced Rush Hour
setting the default for the Dispatcher
80
setting the default for the Planning
Editor 64, 1262
Session 207
setting the default for the Routing
Editor 57
Advanced rush hour area
defining 1283
Alias
defining 1283
options page 67
setting the default 67
Aliases
menu options 1196
All Loads report 1045
Allow SKUs to Split Between Pallets 715
Alternate route names 1167
Ambiguous order pair
defining 1283
Analyzing
equipment history in the Dispatcher
784
route history in the Dispatcher 784
routes in the Planning Editor 637
trucks in the Loading Editor 738
Analyzing delivery costs 1272
Anchor icon 1132, 1145
Anchoring
all location extensions in a planning
session 663
all location extensions in a territory
661
General 661
location extensions in Maintenance
250
menu option 1185
select location extensions 661
Setting the Previous Days and Weeks
664
Animate on Map in the Planning Editor
638
Archiving
the planning session 676
the routing session 572
Area attributes 451
Editing on map 550
editing on map 550
moving on map 452
viewing on map 451, 454
Area distances 308
adding 308
defining 1284
deleting 308
editing 48, 308
explaining 308
Areas
adding 188
defining 1284
deleting 188
editing 188
explaining 188
Arranging list and maintenance windows
1136
Arranging windows
in the Planning Editor 588
in the Routing Editor 443
Arrival time
data quality 757
Assign
defining 1284
Assign Days 630
1302

Index
limiting routes by time 633

limiting the load for a route 631
setting the advanced options
parameters 634
setting the time window options 633
specifying reload parameters 631
specifying the time parameters 633
Assign Days Options Notebook 630
Advanced 634
Load Params 631
Optimizations 633
Reloads 631
Score Params 630
Time 633
Time Windows 633
Assigning
a layover to a route(s) in the Dispatcher
825
a layover to a route(s) in the Planning
Editor 655
a layover to a route(s) in the Routing
Editor 554
account types to locations in the
Planning Editor 659
an ID to a route in the Dispatcher 811
an ID to a route in the Routing Editor
541
breaks to daily routes in the Routing
Editor 554
breaks to routes in the Dispatcher 825
breaks to routes in the Planning Editor
655
breaks to standard routes 484
depots to standard routes 485
dispatchers to routes in the Dispatcher
764
drivers to a route in the Routing Editor
541
drivers to a territory 622
drivers to routes in the Dispatcher 764
equipment to a preferred route in the
Routing Editor 540
equipment to a route in the Routing
Editor 537, 541, 543
equipment to a territory 622
equipment to routes in the Dispatcher
766
equipment types to a preferred route in
the Routing Editor 540
equipment types to a route in the
Routing Editor 537, 543
IDs to several territories 628
layovers to routes in the Dispatcher
825
layovers to routes in the Planning
Editor 655
layovers to standard routes 484
loads in MobileCast 906
location extensions to a territory 620
location extensions to depots in Depot
Planner 689
locations to employees 177
new account types in the Planning
Editor 659, 660
new service time types in the Planning
Editor 659, 660
new time window types in the Planning
Editor 659, 660
post-route surveys to a route in the
Dispatcher 812
pre-route surveys to a route in the
Dispatcher 812
properties to preferred routes 538
questions to surveys 220
resources to a route in the Planning
Editor 589, 652
resources to a route in the Routing
Editor 541
resources to depots in the Planning
Editor 614
resources to routes in the Dispatcher
763
route IDs when building routes in the
Routing Editor 463
scenarios to a route in the Dispatcher
812
sequential IDs to territories 628
sequential route IDs in the Planning
Editor 654
sequential route IDs in the Routing
Editor 545
Operations Guide
1303
Index
service pattern sets in the Planning

Editor 659
service time overrides in the Planning
Editor 660
SKUs to a depot 245
start times to routes in the Planning
Editor 653
start times to routes in the Routing
Editor 546
surveys to a stop in the Dispatcher 815
unassigned stops to routes in
Continuous Optimization 90
unassigned stops to routes in
Dispatcher 832
unassigned stops to routes in the
Routing Editor 523
upload selectors in the Routing Editor
553
waits to routes in the Dispatcher 825
waits to routes in the Planning Editor
655
waits to routes in the Routing Editor
554
wireless devices to routes in the
Dispatcher 768
Assigning loads in MobileCast
to common carriers 909
to existing routes 906
to new route 907
Assumed from projection
data quality 757
Authentication policy
ability to set user to bypass 29
about 16
creating 16
defining password policies 17
defining username policies 16
Auto Arrive and Depart
allowing a driver to use 181
enabling 103
Auto captured
data quality 757
Auto-delete config
applying 325
Automatically assigning stops in

Automatically reassigning stops in
Available
defining 1284
menu option 1193
Available loads in MobileCast
claiming 905
AvP Route Summary report 938
AvP Stop Detail report 939
B
Backup Save
menu option 1183
Balancing routes in the Planning Editor
630
by load 631
by time 633
Balancing routes in the Routing Editor 514
by % capacity 514
by load 514
by time 514
Barcode
entering for a line item in the
Dispatcher 819
entering for an order in the Dispatcher
819
Barriers 287
adding 287
defining 1284
deleting 289
displaying 287
editing 288
explaining 287
setting the default 55, 62, 79, 206
Batch import
explaining 378
Bay Contents 1191
Bay Contents View 724
Manual stack order 724
Package type stack order 724
Quantity stack order 724
SKU stack order 724
1304

Index
Bay Preference Maintenance notebook

132
Bay Preferences
defining 1284
Bay preferences
and package types 133
and SKUs 134
Define Bay Preferences window 132
Bay Tree View 1191
Bay truck maintenance items
equipment 695
equipment items 694
equipment types 695
loading information 696
loading preferences 696
loading rules 695
package types 694
SKUs 694
warehouse zones 694
pallet/bay mix rules 696
product items 694
SKU brands 694
stack rules 696
696
Bay type capacity
import layout 439
importing 372
setting 694
Bay Type Capacity Maintenance window
118
Bay types 117
adding 112, 117
calculating capacity 118
defining 1284
deleting 112, 117
editing 112, 117
entering dimensions 117
excluding pallet type from 118
explaining 112, 117
Max SKU 118

specifying the maximum number of
SKUs 118
Bays
and package type preferences 132
and SKU preferences 133
and small SKUs 132
assigning a type 128
counting 128
disabling 132
selecting the loading strategy 132
splitting 128
Best distance
considering in Continuous
Optimization 92
considering when suggesting routes in
the Dispatcher 832
Best time
Optimization 92
the Dispatcher 832
Best time window
Optimization 92
the Dispatcher 832
Bill To
changing for a load in MobileCast 920
defining 1284
Breaks
adding in the Planning Editor 655
adding to standard routes 484
assigning to daily routes in the Routing
Editor 554
assigning to routes in the Dispatcher
825
assigning to routes in the Planning
Operations Guide
1305
Index
Editor 655
automatically added in the Routing
Editor 460
defining 1284
deleting in the Dispatcher 827
designate unplanned breaks as paid 78
editing in the Dispatcher 827
enabling 78
general options in the Routing Editor
492
icon 1178
inserting onto daily routes 492
making breaks paid in the Planning
Editor 655
making breaks paid in the Routing
Editor 554
making paid in the Dispatcher 827
setting the options in the Routing
Editor 460
Buddy equipment 131
Building
territories 610
Building Delivery Sequence
defining 1284
Bulk delivery
defining 1284
Bulk fixed service time
defining 1284
Bulk threshold
Bulk truck maintenance items
equipment 701
equipment items 700
equipment types 701
loading rules 701
package types 700
pallet types 700
pallet/bay and mix layer rules 702
product items 700

SKU brands 700
SKUs 700
stack rules 701
701
warehouse zones 700
Bulk variable service time
defining 1284
Business calendar 345
adding 345
delete 345
edit 345
excluding delivery days 345
setting up 345
Business week
C
Calculate
percent empty in the Dispatcher 870
defining 1284
service time for SKUs 147
cancel an order on a route 1259
cancel order 1259
Cancel Stop Codes
menu option 1180
Cancel stop codes 211
adding 211
definition 211, 1285
deleting 211
editing 211
explaining 211
Cancelled Stop Analyzer 792
Cancelled stop icon 1178
Cancelled Stops
analyzer 792
re-geocode 794
set up options 792
Cancelling
a load in MobileCast 924
a stop in the Dispatcher 848
Canned Text Messages
1306

Index

Canned text messages 222
adding 222
definition 222
deleting 222
editing 222
explaining 222
Capacity violation 726
Carbon emissions information
choosing the measurement units 70
choosing the report options 943
entering information for an equipment
type 122
introducing the carbon emissions
report 943
printing the report 943
Carbon emissions report 943
printing the report 943
setting the options 943
Cascade
menu option 1181
Categories
Cell attributes
descriptions 296
editing 295
Cell patterns 290
adding 290
changing 292
deleting 293
editing 291
explaining 290
selecting the default 290
Cells 290
adding 293
defining 1285
deleting 297
displaying 290
editing 295
explaining 290
splitting 294
Center icon 1157
Centering the map on an area 1159
Change Skill Set 1263

Change Wave Properties 1260
Changing
a depots service time in the Routing
Editor 557
a mid-route source depots service
time in the Routing Editor 558
a routes attributes in the Routing
Editor 533
a routes depot in the Routing Editor
533
a routes destination in the Routing
Editor 536
a routes driver in the Routing Editor
533
a routes ID in the Dispatcher 811
a routes ID in the Planning Editor 652
a routes ID in the Routing Editor 533
a routes max time in the Planning
Editor 652
a routes max time in the Routing
Editor 533
a routes model in the Routing Editor
533
a routes preferred time in the Planning
Editor 652
a routes preferred time in the Routing
Editor 533
a routes properties in the Dispatcher
810
a routes properties in the Planning
Editor 652
a routes properties in the Routing
Editor 533
a routes start time in the Planning
Editor 652
a routes starting time in the Routing
Editor 533
cell patterns 292
delivery areas 330
delivery days in the Planning Editor
668
how location extensions are anchored
661, 663
Operations Guide
1307
Index
items in the Dispatcher 875

load rights in MobileCast 892
location extensions delivery days 668
location extensions Previous Days
and Weeks 664
pallet type in FleetLoader 738
stop order on a route in the Dispatcher
844
stops on a route in the Dispatcher 815
street elevations 1173
the customer being displayed 1256
the delivery area being viewed 1256
the delivery date being displayed 1256
the order of stops on a route in the
Dispatcher 844
Planning Editor 641
Routing Editor 528
your password 9
Checking
equipment position history in the
Dispatcher 784
route assignments in the Dispatcher
807
route position history in the Dispatcher
784
the capacity for a bay in the Loading
Editor 738
the preferences for a bay in the
Loading Editor 738
the properties for a bay in the Loading
Editor 738
Choosing
a default country 51
a planning session 588
a routing session 443
Assign Days options 630
database compact options in the
Planning Editor 592
database compact options in the
Routing Editor 467
default mouse actions in the Planning
Editor 592
default mouse actions in the Routing
Editor 463
default region 43
display options in the Planning Editor
591
display options in the Routing Editor
459
drag and drop actions in the Planning
Editor 592
drag and drop actions in the Routing
Editor 463
how route times, distances, and costs
are calculated in the Planning
Editor 590
how routes appear on the map in
MobileCast 1147
how routes appear on the map in the
Planning Editor 1147
how routes appear on the map in the
how routes on a territory appear on the
map 596
how territories appear on the map 601
location type to synchronize 67
locations appearance on the map in
the Planning Editor 602
route exceptions in the Planning Editor
594
route exceptions in the Routing Editor
468
rush hour options for netScheduler
1262
standard stop exceptions in the
Routing Editor 470
stop exceptions in the Routing Editor
469
the colors for the days and weeks in the
Planning Editor 592
the current rush hour model 269
the Make Territories options 611
the truck loading options 708
time zone display options 51
choosing a color for a Time of Day area
1154
choosing a color for a Time of Day path
1308

Index
1154
choosing a model to display 1154
Choosing the best route in Continuous
Optimization
by best distance 92
by best time 92
by best time window 92
Claim
a load in MobileCast 905
defining 1285
Cloning
regions 39
Cloning a region 39
Cloning maintenance items 48
Close All
menu option 1181
Close Routing Session
menu option 1186
Close time
defining 1285
Closing a delivery window 1260
Codes
menu option 1194
Colors
choosing for days in the Planning
Editor 592
choosing for exceptions in the
Planning Editor 593
choosing for exceptions in the Routing
Editor 468
choosing for routes in the Routing
Editor 451
choosing for weeks in the Planning
Editor 592
on the Equipment map 782
Column Manager 1139
changing column order 1140
hiding columns 1140
icon 1132, 1137, 1140
opening 1140
sorting on columns 1140
Columns
changing the width in list and
maintenance windows 1136

hiding in list and maintenance
windows 1137
in windows 1139
moving in list and maintenance
windows 1136
explaining 376
menu option 1182
Combine orders
Combine Routing Sessions 310
Combine Sessions 573
Combining
an archive with a current session in
Maintenance 310
an archive with a current session in the
Routing Editor 573
routing sessions in Maintenance 310
routing sessions in the Routing Editor
573
Combining routes in the Routing Editor
514
Commercial Vehicle Restrictions
enabling and disabling for the routing
session 56
enabling and disabling the planning
session 207
enabling for a new routing session 578
enabling for the routing session 584
Session 207
setting the default for the planning
session 63
Editor 56
Commodity type
defining 1285
Commodity types in MobileCast
creating 897
specifying for a load 901
Common Carriers
Operations Guide
1309
Index

Common carriers
defining 1285
Common carriers in MobileCast
adding 897
assigning loads to 909
transfer load to 916
using for a load 899
Communicating with external programs
32
Communicating with the drivers in the
Dispatcher 860
Compact Database
Compacting
database from the Planning Editor 592
database from the Routing Editor 467
database maintenance 326
Compartment Detail Report 946
Compartment restrictions
enforcing when suggesting routes in
Compartment routing
route exception 469
Compartment Summary Report 945
Compartment types 112
adding 120
definition 112
deleting 120
editing 120
explaining 120
Compartments
adding to an equipment type 124
restricting when assigning stops to
524
Complete
defining 1285
load, defined 1285
Complete time
data quality 757
Completing
all stops at once in the Dispatcher 774
individual stops in the Dispatcher 772

load stop in MobileCast 911
order activities in the Dispatcher 822
routes in the Dispatcher 775, 777
stops on a route in the Dispatcher 772
Condensed
menu option 1191
Configure
menu option 1197
Confirmation dialogs
disabling on the Java-enabled phone
96
Conflicts starting routes in the Dispatcher
771
Connecting to a database 10
Consider Before Next Arrival
setting in Continuous Optimization 93
Consignees
adding to locations 254
Container Types
menu option 1180
Container types 223
adding 223
definition 223
deleting 223
editing 223
explaining 223
Containers 225
adding 225
creating the alias 67
definition 225
deleting 225
editing 225
explaining 225
import layouts 429
importing 364
scan status 807
setting options 83
tracking in the Dispatcher 819, 841
Continuous Optimization
assigning stops that meet time window
limits 92, 93
automatically assigning stops to routes
1310

Index
90
automatically reassigning stops to
routes 91
choosing the best route by distance 92
choosing the best route by time 92
choosing the best route by time
window 92
considering not completed routes 92
considering not departed routes 92
considering not started routes 92
considering skill sets 92
considering todays routes only 92
enforcing equipment type restrictions
92
generating route notes when a stop
cannot be transferred 91
generating route notes when a stop is
successfully transferred 91
generating route notes when an
unassigned cannot be assigned
90
generating route notes when an
unassigned is successfully
assigned 90
reassigning stops that meet time
window limits 91
setting Consider Before Next Arrival
93
setting guidelines 90
setting maximum runtime 92
setting maximum stops per route 92
settings 90
time window threshold 91
Conventions used in this manual 5
Copy/Combine
See Archiving the Routing Session 572
Cost Analyzer 1272
analyzing the cost of an order 1272,
1277
changing the customer 1272, 1276
changing the delivery area 1272, 1276
changing the delivery date 1272, 1276
determining filters 1272, 1277
determining the cost of delivering an
order 1272
entering orders individually 1272

import batches of orders 1278
Import orders 1275
Costs
driver costs 180
fixed equipment costs 123
variable equipment costs 123
Create Helper Routes 499
Creating
a file from route information in the
a new routing session in the Routing
Editor 577
a route in the Dispatcher 811
a route in the Planning Editor 629
a route in the Routing Editor 535
a route that does not return to the depot
536
a rush hour area 270
a time of day restriction area 281
daily routes in the Routing Editor 488
driver surveys 218
dynamic routes in the Routing Editor
493
extended runs in the Routing Editor
507
load locations in MobileCast 895
multi-day runs in the Routing Editor
507
pallet types 168
pre- and post-route stops 494
reports from list and maintenance
windows 1138
route reloads in the Routing Editor
505, 520
routes from selected orders in the
Routing Editor 526
routes on the same side of the street 53
routing passes in the Routing Editor
490
standard route overrides in the Routing
Editor 478
standard routes from daily routes in the
Routing Editor 478
Operations Guide
1311
Index
standard routes in the Routing Editor

475
static routes 849
strategic routes in the Planning Editor
629
territories 610
territories from existing territories 610
territories from unassigneds 610
territories with balanced run time 613
the headers 67
time of day restriction models 277
Creating dynamic routes 493
assigning resources for routes 495
assigning the route ID when the route
is created 502
assigning the start time 494
selecting the strategy 497
setting route options 493
setting the minimum route size 494
setting the route restrictions 494
setting the run length 494
setting time window informations 502
Creating routes in the Dispatcher 811
adding activities to an order 822
adding stops 813
assigning a scenario 812
assigning drivers 764
assigning equipment 766
assigning resources 763
assigning wireless devices 768
entering line item detail 819
entering order detail 819
entering order financial details 820
viewing order financial details 822
Creating routes in the Planning Editor 629
determining the importance of
balanced load 630
evaluating the routes 637
indicating the importance of balanced
runtime 630
indicating the importance of cost 630
limiting by time 633
overriding how location extensions are
anchored 634
setting how location extensions are
anchored 661, 663

setting the advanced optimization
parameters for Assign Days
634
setting the optimization parameters
633
specifying preferred runtime by day
633
specifying starting time by day 633
specifying the load limits 631
specifying the time parameters 633
using time windows 633
Creating routes in the Routing Editor 488,
535
assigning sequential route IDs 545
assigning start times 546
choosing the options 490
Creating static routes 849
Creating territories 610
adding a territory manually 625
assigning resources to depots 614
choosing the optimization parameters
613
specifying how account types are to be
distributed 614
specifying the number of territories to
make 611
with balanced run time 613
Critical route
defining 1285
customer
changing in Day Commander 1256
Customer Commodities
Customer commodities in MobileCast
adding 897
Customer Delivery Cost report 993
Customers
Cycle weeks
defining 1285
1312

Index
D
Daily
menu option 1183
Daily import
calculation options 363
data path 363
definition 362
route date 363
starting ref. number 363
viewing errors 364
Daily orders import file layout
available fields 397
explaining 384
setting 384
Data quality 756
arrival time quality 757
assumed from projection 757
auto captured 757
complete time quality 757
departure time quality 757
dispatcher entered 757
distance data quality 757
driver entered 757
geo computed 757
geo computed cluster 757
Mixed 757
start time quality 757
Data Transport
menu option 1180
Database Maintenance
menu option 1180
Database maintenance 321
archive 321
auto-delete config 321
compressing the database 324
configuring automatic database
maintenance 325
defining 1285
delete 321
deleting actual information 324
deleting database information 323
deleting routing information 324
explaining 321
Date/time search conditions 1144
Day Commande
wave properties 1260
Day Commander 1256
adding a delivery window 1260
changing the customer 1256
changing the delivery area 1256
changing the delivery date 1256
closing a delivery window 1260
deleting a delivery window 1260
Delivery Window 1260
finding a delivery location 1257
Locking Orders 1266
refreshing the data 1256
Unlocking Orders 1266
updating orders 1258
viewing orders 1256
viewing orders for a specific delivery
wave 1257
viewing orders for a specific delivery
window 1257
Day Serviced report 949
Day Shift 668
Decrease Map Detail icon 1158
Default cell pattern 290
Defaults
selecting for maintenance items 50, 51
Define Bay Preferences
using the Bay Preference Maintenance
notebook to 132
Define Bay Preferences window 132
Definintions
Hub Depot 1288
Unlock Order 1296, 1297
Definitions
Absolute Calculation Method 1283
Account Type 1283
Actual Data 1283
Actual Temperature 1283
Administrative Route 1283
ADP 1283
Advanced Rush Hour Area 1283
Alias 1283
Ambiguous Order Pair 1283
Area 1284
Operations Guide
1313
Index
Area Definition 1284

Assign 1284
Available 1284
Barriers 1284
Bay Preferences 1284
Bay Types 1284
Bill To 1284
Breaks 1284
Bulk Delivery 1284
Bulk Fixed Service Time 1284
Bulk Variable Service Time 1284
Calculate Percent Empty 1284
Cancel Stop Codes 1285
Cells 1285
Claim 1285
Close Time 1285
Commodity Type 1285
Common Carrier 1285
Completed load 1285
Critical Route 1285
Cycle Weeks 1285
Database Maintenance 1285
Delay Type 1285
Delivery Area 1285
Delivery Route 1285
Delivery Wave 1285
Delivery Wave Instance 1286
Detail Level 1286
Distance Model 1286
Download File 1286
Driver Adjustment 1286
Driver Alerts 1286
Driver Friendly 1286
Driver Productivity 1286
Driver Shift 1286
Driver Types 1286
Drop and Hook 1286
Dropped Off 1286
Duty Period 1286
Dynamic Route 1287
Employee 1287
Employee Status 1287
Employee Type 1287
Employees 1287
Equipment 1287
Equipment Override 1287
Equipment Status 1287

Equipment Type 1287
Event 1287
Fixed Fee 1287
Fixed Service Time 1287
FleetLoader 1287
Freight Classes 1288
Futures 1288
Geocode 1288
Global Penalty 1288
GPS 1288
GPS Playback 1288
Graduated Calculation Method 1288
Hours of Service rules 1288
Hybrid (Driver First) 1288
Hybrid (Warehouse First) 1288
Impasse 1289
Import Layout 1289
Import Layout Sets 1289
Layovers 1289
Line Items 1289
Load 1289
Load Admin 1289
Load Front to Rear 1289
Load ID 1289
Load Leveling 1289
Load Location 1289
Load Phases 1290, 1292
Load Preferences 1290
Load productivity 1290
Load Relay 1293
Load Type 1290
Load User 1290
Location Extension 1290
Location Override 1290
Location Preference Loading 1290
Location Substitution 1290
Location Types 1290
Locations 1290
Lock Order 1290
Meet Point 1291
Merchandisers 1291
Message Center 1291
Mix Rules 1291
Mobile Depot 1291
Module 1291
1314

Index
Nodes 1291
Obey No-Mix Rules 1291
Obey Stack Rules 1291
Open Time 1291
Optimization Pass 1291
Order Pair 1292
Orders 1292
Organization unit 1292
Package Types 1292
Paired Order 1292
pallet capacities 142
Pallet Loading 1292
pallet types 168
Pass 1292
Penalty 1292
Pickup 1292
Planning Session 1292
Position History 1292
Power Unit 1292
Preference Pass 1292
preferred delivery pallet type 253
Preprocessor 1292
Rear Bay 1293
Reason Codes 1293
Reference ID 1293
Regions 1293
Reload 1293
Report Writer 1293
Reserved Order 1293
Return 1293
Revenue 1293
Reversed Order Pair 1293
Route 1294
Route Exception Rules 1294
Route Exceptions 1294
Route Status 1294
Route Type 1294
RouteNet 1294
Routing Sessions 1294
Rush Hour Area 1294
Rush Hour Models 1294
Rush Hour Path 1294
Scenarios 1294
Seal 1294
Search Manager 1294
Segment 1294
Separated Order Pair 1294

Service Failure 1294
Service Monitor 1294
Service Pattern 1294
Service Pattern Set 1295
Service Time 1295
Service Time Maintenance 1295
Service Time Overrides 1295
Service Time Types 1295
Shuttle Distance 1295
Shuttle Time 1295
Simple Rush Hour Area 1295
Size Precision 1295
SKU brands 1295
SKUs 1295
Small SKU Loading 1295
Stack Rules 1295
Standard Route 1295
Static Route 1295
Static Route Set 1295
Stop Quantity Loading 1295
Stop Types 1295
Street Segments 1295
SuperMatrix 1295
Territory 1296
Time Window 1296
Time Window Override 1296
Time Window Types 1296
Tour of Duty 1296
Track Type 1296
Transfer 1296
Travel Time Models 1296
Trip 1296
Unassigneds 1296
Undeliverable Stop Codes 1296
User Defined Fields 1296, 1297
Users 1296, 1297
Variable Fee 1296, 1297
Variable Service Time 1296, 1297
Void Locations 1296, 1297
Waits 1296, 1297
Warehouse Friendly 1296, 1297
Where Function 1296, 1297
Wireless Events 1296, 1297
Working Time Directives 1296, 1297
XY Routing Method 1296, 1297
Operations Guide
1315
Index
Zones 1296, 1297

Delay type 113
adding 116
defining 1285
definition 113
editing 116
Delay Types
menu option 1180
Deleting
account types 193
activities 170
barriers 289
bay types 117
breaks in the Dispatcher 827
cells 297
drivers 179
employee types 174
employees 175
equipment 130
equipment types 122
inactive stops from standard routes 482
items 49
layovers in the Dispatcher 827
location types 235
locations 237
mid-route depot 829
mix rules 164
multiple items 49
orders 151
package types 141
pallet types 168
prebuilt solution in Loading Editor 747
regions 40, 188
report groups 934
reports 932
routes in the Routing Editor 530, 534
rush hour path 276

scenarios 194
service time overrides 239
skill sets 172
SKU brands 140
SKUs 147
stops in the Dispatcher 817
time of day restriction path 285
time window overrides 239
unassigned orders in the Dispatcher
842
users 28
void locations 262
waits in the Dispatcher 827
162
warehouse zones 138
zones 189
Deleting delivery areas 330
Delivery area
defining 1285
Delivery areas 330
adding 330
changing 330
deleting 330
explaining 330
working with 330
delivery date
Delivery Detail report 950
Delivery Route
defining 1285
Delivery Wave
viewing 1257
Delivery wave
defining 1285
1316

Index
Delivery waves 333

adding 333
introducing 333
Delivery Window
adding in Day Commander 1260
closing in Day Commander 1260
deleting in Day Commander 1260
viewing 1257
Delivery Window in Day Commander
1260
Delivery windows 341
adding 341
adding in Day Commander 1260
adding individually 341
adding simultaneously 342
closing in Day Commander 1260
introducing 341
Departure time
data quality 757
Depot Planner
adding a depot 688
assigning location extensions to the
depots 689
choosing the location marker 603
choosing the unassigned location color
603
evaluating the results 690
geocoding a depot 689
introducing 688
starting 688
using the Location Origin Summary
window 690
working with 688
Depot SKUs
import layout 434
Depots
adding in Depot Planner 688
adding onto a route in the Planning
Editor 657
assigning to standard routes 485
changing the service time in the
Routing Editor 557
creating 237
displaying in the Stop list 459, 591

geocoding in Depot Planner 689
inserting mid-route in the Dispatcher
828
inserting onto a daily route in the
Routing Editor 556
menu option 1188
removing from a route in the Routing
Editor 557
specifying an MRS depot for an order
153
specifying for an order 153
Destination
icon 1178
Detail level
defining 1286
Detailed
menu option 1191
Determing the cost of an order 1272
Determining filters 1272
Device Diagnostics
activating for a driver 182
setting options 84
viewing 803
Dimensions of a bay type 117
Disable
bays 132
Disabled Bay used 726
Disabling the Route
See Disabling Wireless
Communication 866
Dispatcher 753
acknowledging a route exception 799,
800
acknowledging event receipts 863
adding a list in the Route Overview
window 754
adding breaks to a route 825
adding layovers to a route 825
adding waits to a route 825
calculating percent empty 870
cancelled stops 792
Operations Guide
1317
Index
changing the distance a driver traveled

in a state or province 878
checking space on equipment 870
choosing the SmartPhone options 97
choosing the Suggest Route options
832
completing a route 775, 777
completing a stop 772
creating a route 811
creating item notes 850
creating notes 850
creating route notes 850
creating static routes 849
creating user notes 855
deleting a list in the Route Overview
window 754
deleting route notes 851
deleting user notes 856
displaying pre and post route times 756
displaying the routes origin and
destination in the stop list 756
editing route notes 851
editing user notes 856
enabling automatic arrival and
departure mode 106
finding a route 778
having MobileCast automatically
assign unassigneds 90
having MobileCast automatically
transfer stops 90
importing unassigned stops 419
inserting a mid-route depot 828
map symbols 759
menu options 1192
options in the maintenance module 76,
103
refreshing information 885
reporting distance by jurisdiction 877
reporting distance by mile 877
reporting item notes 852
reporting notes 850
reporting route notes 852
Route Summary window 757
running a route 754
setting the allow additional stop types
option 78
setting the auto generate route ID

option 77
setting the auto generate unique DTR
numbers option 77
setting the automatically fixup
wireless events option 81
setting the automatically relocate
equipment option 81
setting the calculator option 79
setting the continuous optimization
options 90
setting the driver assignment required
option 78
setting the equipment assignment
required option 78
setting the Group Unloading options
84
setting the quantities are a ratio of size
1 option 77
setting the reason code options 81
setting the refresh rate 885
setting the send API notifications
option 81
setting the stop critical minutes option
79
setting the validate quantities option 81
Show Me 799, 800
skipping a stop 848
starting a route 762
Suggest Route 832
unassigning stops from a route 817
user-defined fields 858
using maps 759
using the Route List window 756
using the Route Overview window 754
using the where function 780
View Description 799, 800
viewing data for user-defined table 880
viewing detailed description of route
exception rule 799, 800
viewing event receipts 863
viewing item notes 852
viewing list items 875
viewing my routes only 876
viewing notes 850
viewing order activities for a stop 756,
1318

Index
822
viewing position history 784
viewing route exceptions in a list
window 797
viewing route exceptions on a map 797
viewing route notes 852
viewing stops for a route in an
overview window 754
viewing user notes 855
viewing user-defined data for specific
route 880
working with a route 754, 756
working with a stop 754, 756
working with an order 754
working with notes 850
working with OnTrack Routes 881
working with the message center 864,
866
working with unassigned stops 830
Dispatcher Concepts 753
Dispatcher entered
data quality 757
Dispatcher Module 1192
File menu 1192
Help menu 1195
List menu 1194
menu options 1192
Routes menu 1193
View menu 1192
Window menu 1195
Displaying
a route and surrounding locations on a
map in the Routing Editor 453
area attributes on the map 451
barriers 287
cells 290
cities on the map 1151
depot in the Stop list 459, 591
depots and unassigned stops on a map
information in list and maintenance
windows 1136
items on the map 1148
landmarks on the map 1150
location extensions assigned to a
territory 604
order activities in the Routing Editor
459
overlap between territories 604
roads on the map 1148
routes origin and destination in the
Dispatcher 756
routes on a map in the Planning Editor
637
routes on a map in the Routing Editor
450, 453
rush hour models on the map 1153
territories 604
territories on a map 604
time of day restriction models on the
map 1154
zip codes on the map 1152
Distance by Area report 952
menu option 1195
report 953
Distance data
data quality 757
Distance model 185
defining 1286
editing 48, 185
explaining 185
Do not Compute Travel Time and Distance
to and from Origin 590
Download file
defining 1286
Draft Daily report 954
Dragging stops to a standard route in the
Routing Editor 482
Driver adjustment
defining 1286
Driver Alerts
menu option 1180
Driver alerts 217
adding 217
deleting 217
Operations Guide
1319
Index
editing 217
explaining 217
Driver Checkout Sheet report 955
Driver directions 564, 666
pre-load driver directions 181
printing in the Dispatcher 868
printing to a file in the Planning Editor
666
printing turn by turn directions in the
Planning Editor 666
printing turn by turn directions in the
printing with maps in the Planning
Editor 666
printing with maps in the Routing
Editor 564
Driver entered
data quality 757
Driver Friendly 710, 716
defining 1286
loading bays according to capacity 717
loading by location preferences 717
loading largest stop first 717
loading product on alternating sides of
the truck 717
Driver Itinerary report 956
Driver Manifest report 958
Driver Performance for MobileCast 962
Driver Performance report 960, 962
Driver Productivity
defining 1286
Driver productivity
menu option 1181
Driver Productivity report 963
Driver Returns report 964
Driver Service Log report 966
Driver Shift
defining 1286
Driver Statistics report 965
Driver Survey report 967
Driver type 115
adding 116
defining 1286
definition 115
explaining 115
Driver Utilization report 969
Drivers 179
activating device diagnostics 182
adding 179
allow to add breaks and layovers on the
mobile device 99
allow to add notes to stops, orders, and
line items in MobileCast
SmartPhone 99
allow to add pictures to notes in
MobileCast SmartPhone 99
allow to add pictures to text messages
in MobileCast SmartPhone 100
allow to arrive and wait at a stop on the
mobile device 100
allow to call a location while in
allow to cancel all unvisited stops at
one time on the mobile device
100
allow to cancel stops on the mobile
device 100
allow to choose name from Consignee
History on the mobile device
99
allow to edit order and line item
quantities on the mobile device
100
allow to edit Over, Short, and
Damaged quantities on the
mobile device 101
allow to geocode on the mobile device
96
allow to redeliver a completed stop on
the mobile device 97
allow to resequence stops on the
mobile device 100
allow to see days stops on route before
starting 100
allow to see diagnostic information on
allow to see if a break, wait, or layover
1320

Index
is Paid or Unpaid on the mobile

device 99
allow to text message on the
"Proceeding to" screen on the
mobile device 96
allow to view quantities on the mobile
device 100
assigning to a route in the Routing
Editor 541
assigning to a territory in the Planning
Editor 622
764
choosing the SmartPhone options 97
deleting 179
determining the costs 180
disable confirmation dialogs on the
Java-enabled phone 96
display planned arrival times on the
Java-enabled phone
Mobile Options notebook
display planned arrival times to
drivers on the Java-enabled phone 103
editing 179
explaining 179
import layouts 426
importing 372
Java phones 103
messages to in the Dispatcher 867
pre-load driver directions 181
requesting position in the Dispatcher
780
require consignee 98
require signature 98
require to confirm actions on mobile
device 96
see column headers 98
show stops delivery and pickup
details on the Java-enabled
phone 103
SmartPhones 97
tracking in the Dispatcher 780
tracking productivity 183
using automatic arrive and depart

feature 181
Drop and hook
assigning equipment to be swapped
872
defining 1286
handling the swap at the stop 873
setting up 872
Dropped off
defining 1286
Duty Period
defining 1286
Duty Period History
editing 305
menu options 1181
updating in Roadnet 58, 579, 585
Duty Period Monitor
editing drivers duty period history 305
Duty Period Rules
the Dispatcher 835
setting 71
Duty Period Violation exception for
Roadnet 469
Dynamic route
defining 1287
Dynamic route IDs
adding 543
Dynamic routing
adjusting start time to meet time
windows 502
allowing waits to make time windows
502
assigning resources for routes 495
assigning the route ID 502
assigning the start time 494
creating a route description 502
creating extended runs 507
creating multi-day runs 507
creating route reloads 505
explaining 441
Operations Guide
1321
Index
limiting time spent backtracking 508

routing stranded stops 508
routing unassigned stops 508
setting route options 493
setting the minimum route size 494
setting the route restrictions 494
setting the run length 494
setting time window information 502
splitting orders 509
using assigned equipment types 495
using saved area attributes 502
using standard routes 509
E
Edit Street Attributes window 1170
alternate route names 1167
Editing
a distance by jurisdiction entry 878
activities 170
barriers 288
bay types 112, 117
cell attributes 295
cell patterns 291
cells 295
distance model 185
drivers 179
employee types 113, 174
employees 175
equipment 130
equipment types 113, 122
location types 114, 235, 236
locations 237
mid-route depot 829
mix rules 164
nodes 1170
notification recipients 32
order financial detail codes 214

order status codes 216
orders 151
package types 141
pallet types 168
regions 188
report groups 934
reports 932
saved attributes in the Routing Editor
550
scenarios 194
skill sets 172
SKU brands 140
SKUs 147
street segments 1166
the path 1176
the territories 620
users 28
void locations 262
162
warehouse zones 138
zones 189
Editing routes in the Dispatcher
adding breaks 825
adding layovers 825
adding stops 813
adding waits 825
automatically resequencing stops 844
changing line item detail 822
changing order detail 822
changing stops 815
deleting a line item 822
deleting a mid-route depot 829
1322

Index
deleting an order 822

deleting breaks 827
deleting layovers 827
deleting stops 817
deleting waits 827
editing a mid-route depot 829
editing breaks 827
editing layovers 827
editing waits 827
entering line item detail 819
entering order detail 819
manually resequencing stops 844
processing a line item 823
processing an order 823
unassigning stops 817
Editing routes in the Planning Editor 640
adding breaks 655
adding waits 655
flip 641
line sequence 641
moving stops from one route to another
640
removing stops 641
sequence 641
time window 641
Editing routes in the Routing Editor
adding breaks 554
adding waits 554
Adjust Mid-Route Sourcing 515
adjust mid-route sourcing 529
automatically sequencing the stops
528
balancing the routes 513
combining routes 514
flip 528
line sequence 529
removing stops 530
sequence 528
standard route sequence 529
swapping stops to make time windows
515
Time Window Swap 515
time window swap 515
time windows 502
Editing standard routes in the Routing

Editor 486
combine routes 486
flip 486
line sequence 486
removing inactive stops 482
sequence 486
Editing the status of a convertible bay 739
insert a shelf 739
editing the status of a convertible bay
remove a shelf 739
Editing trucks 737
assigning unassigneds to a bay/pallet
741
changing route status 746
changing the pallet type 743
moving multiple SKUs to another bay
741
moving part of an SKU to another bay
742
moving SKUs 741
moving SKUs between windows 744
moving SKUs to another bay 741
moving SKUs within a bay 743
save 746
save and lock 746
saving your work 746
Printing the report 971
Setting the options 970
Printing the report 973
Setting the options 972
Employee status 113
adding 116
defining 1287
definition 113
editing 116
explaining 113
Employee types 113, 174
adding 174
definition 1287
deleting 174
editing 174
Operations Guide
1323
Index
explaining 174
Employees 175
adding 175
assigning locations to 177
assigning skill sets 175
defining 1287
definition 1287
deleting 175
editing 48, 175
explaining 175
import layout 425
importing 372
menu option 1179, 1188, 1194
menu options 1184
Enabling a wireless device 227
Enlarging the map's area of view 1159
Entering
actual line item quantities in the
Dispatcher 823
actual order quantities in the
Dispatcher 823
edit mode in the Loading Editor 720
line item detail in the Dispatcher 819
order detail in the Dispatcher 819
productivity information 183
the Loading Editor 705
Entries
selecting in list or maintenance
windows 1137
Equipment 130
adding 130
adding overrides 136
assigning a preferred driver 131
assigning a wireless device 135
766
calculate percent empty in the
Dispatcher 870
capacitizing 123
defining 1287
deleting 130
editing 48, 130
explaining 130
import layouts 430
importing 372
menu option 1179, 1184, 1185, 1188,
1194
selecting a single piece in the
Dispatcher 767
selecting more than one piece in the
Dispatcher 767
sharing 131
starting and ending in the Dispatcher
767
swapping at a stop in the Dispatcher
872
Equipment Map
menu option 1192
Equipment map
colors 782
using to track equipment in the
Dispatcher 782
Equipment overrides 136
adding 136
defining 1287
deleting 136
editing 136
explaining 136
Equipment position history
See Position History 788
viewing 788
Equipment preferences
and bay preference 132, 133
and FleetLoader 132
and package types 132
and SKUs 133
defining 132
Equipment status 113
adding 116
defining 1287
definition 113
explaining 113
1324

Index
Equipment types 113

adding 122
adding compartments to 124
and FleetLoader 126
assigning a type to a bay 128
carbon emission information 122
configuring 126
defining 1287
deleting 122
editing 122
enforcing restrictions in Continuous
Optimization 92
enforcing restrictions when suggesting
enforcing restrictions when suggesting
525
explaining 113, 122
import layout 435
importing 372
restricting travel during rush hour 123
specifying dimensions and free space
for bulk type 127
specifying pallet types allowed 127
splitting bays 128
using locations types on a route in the
Routing Editor 495
varying travel time by 124
Equipment Utilization Metrics report 975
Equipment Utilization report 974
Establishing order of preference
for package types 133
for SKUs 134
Evaluating
results in Depot Planner 690
Evaluating routes in the Planning Editor
using list windows 637
using maps 637
using the Route Summary 638
Evaluating routes in the Routing Editor
512
displaying a summary of the routes 512
using the map 512
viewing routes and the vicinity 512

Evaluating the network 1176
Evaluating the territories 616
viewing account type information 619
viewing overlap between territories
618
Event
defining 1287
Event Receipts
acknowledging 863
menu option 1195
viewing for a route 808
viewing in the Dispatcher 863
Events
communicating to external programs
32
Exceeds Compartment Capacity route
exception 469
Exceeds Maximum Run Time route
exception 469
Exceeds Preferred Time route exception
469
Exceeds Size 1, 2, 3, Capacity route
exception 469
Exceptions
explaining routes in the Planning
Editor 594
explaining routes in the Routing Editor
468
explaining stop in the Planning Editor
594
see Route exception rules 229
see Route exceptions in the Dispatcher
797
Exceptions in the Planning Editor 593
route 594
setting 593
Exceptions in the Routing Editor 467
route 468
routing 522
setting 467
standard stop 470
Operations Guide
1325
Index
stop 469
tracking 468
Excluding delivery days 345
Execute Search icon 1141, 1145
Exit
menu options 1179
Exiting the Loading Editor 751
cancel 751
discard 751
save 751
save and lock 751
Explaining
actual route/stop 300, 302
actual vs. planned comments 298
authentication policy 16
barriers 287
bay types 112, 117
cell patterns 290
cells 290
combine from archive 376
daily orders import file layout 384
database maintenance 321
distance model 185
drivers 179
employee types 113, 174
employees 175
equipment 130
equipment types 113, 122
eRoadnet 1255
import layouts 383
import module 348
import orders options 360, 370
importing daily orders 357
importing locations 350
importing onboard data 374
interactive graph options 317
location import file layout 384
location types 114, 235
locations 237
non-passive routing 882

onboard import file layout 384
OnTrack Routes in MobileCast 881
orders in maintenance 151
organization units 44
package types 141
pallet types 168
passive routing 881, 882
position history in the Dispatcher 784
privileges
region distances 308
regions 35, 188
reports 928
route exceptions in the Dispatcher 797
rush hour models 266
scenarios 194
service time graph options 317
service time updating 312
setting the alias 46
SKU brands 140
SKUs 147
updating service times 312
users 28
void locations 262
162
warehouse zones 138
zones 189
Export Routes
menu option 1189
Exporting
data from list and maintenance
windows 1138
distance by jurisdiction 877
loaded routes 748
orders from Roadnet 570
1326

Index
orders from the Routing Editor 567

reports 936
routes from Roadnet 567
routes from the Planning Editor 677
routes from the Routing Editor 575
F
Favorites
menu option 1181
Filtering orders for netScheduler 339
Filtering orders for routes in the Routing
Editor 492
Filters 339
adding 339
introducing 339
Find Paired Orders 517
Find Paired Stops 517
Finding
a city 1162
a location extension in the Planning
Editor 650
a location on the map 1162
a stop in the Planning Editor 650
a stop in the Routing Editor 531
a territory 650
a zip code 1162
an address on the map 1162
an order in the Routing Editor 531
stops with the same geocode in the
Routing Editor 518
Finding a delivery location 1257
Fit icon 1157
Fitting all routes on the map
in the Planning Editor 604, 605
Fixed costs 123
Fixed fee
defining 1287
Fixed service time
defining 1287
Flashing routes on the map

FleetLoader
defining 1287
FleetLoader Options notebook 721
Bay Contents View page 724
General page 721
Truck Profile page 723
Warnings page 725
FleetLoader Stop List report 1038
Flipping routes
Font
changing 1136
icon 1132, 1136
Freight Classes
defining 1288
Freight Classes in MobileCast 897
Future orders
locking 151, 357, 527
routing in the Routing Editor 527
Futures
defining 1288
menu option 1188
G
General options
for the Dispatcher in the Maintenance
module 76
in the Maintenance module 51
General options (FleetLoader)
bulk percent full calculation 722
use layer limits 722
use pallet capacity 722
by loading method 721
save as prebuilt solution 722
show active routes 722
sideloader percent full calculation 721
use bay capacity 722
use layer limits 722
Operations Guide
1327
Index
use pallet capacity 722

when overfilled 721
Generating route notes in Continuous
Optimization
when a stop cannot be transferred 91
when a stop is successfully transferred
91
when an unassigned cannot be
assigned 90
when an unassigned is successfully
assigned 90
Geo computed
data quality 757
Geo computed cluster, data quality 757
Geocode
defining 1288
Geocoding 256
depots in Depot Planner 689
locations 256
Getting Started
with FleetLoader 2
with MobileCast 3
with Roadnet 1
with Territory Planner 2
Giving users permissions to 21
Global Itinerary report 978
Global Manifest report 979
Global penalty
definition 1288
Global Penalty Editor 1173
Global Time/Distance report 981
GPS
defining 1288
GPS playback
defining 1288
using in the Dispatcher 787
viewing a route in the Dispatcher 790
viewing equipment position history in
the Dispatcher 788
Graduated calculation method

defining 1288
Graph options
setting 317
Group Unloading 84
Grouping
reports 933
Groups
menu option 934, 1186, 1189, 1191
H
Height and Weight Limit Restrictions
enabling for the routing sessions 584
Height and Weight Road Restrictions
enabling and disabling for planning
sessions 63, 207
enabling and disabling for routing
sessions 56
enabling for a new routing session 578
in Dispatcher 79
preventing equipment types from
using restricted roads 124
Editor 63
Editor 56
setting the Height Restriction and
Weight Restriction 53
Height Restriction
setting 53
Help Topics
menu option 1181
Historical Travel Speeds
setting 89
80
Editor 64
Session 208
Editor 57
use in netScheduler 1262
use in planning session 675
use in routing session 579
1328

Index
use with merchandisers 584

Hours of Service rules
defining 1288
setting 71
Hub depot
defining 1288
Hybrid (Driver First) 710
defining 1288
Hybrid (Warehouse First) 710
defining 1288
Hybrid Driver First Options
For Quantity of Stop 711
loading only prebuilt stops driver
friendly 711
loading prebuilt stops driver friendly
711
Or Prebuilt Stops 711
Prebuilt Stops Only 711
using selectors as a threshold 711
Hybrid Warehouse First Options
For Full Pallets of SKU 710
For Quantity of SKU 710
selecting SKUs to load warehouse
friendly 710
I
IAM 488
Icon bar 759
Icons
add filter 1142, 1145
anchor 1132, 1145
breaks 1178
cancelled stop 1178
center 1157
column manager 1137, 1140
decrease map detail 1158
destination 1178
execute search 1141, 1145
fit 1157
font 1132, 1136
increase map detail 1158
landmark 1164
lasso 1158
layovers 1178
list windows 1132

map 1157
map navigation 1159
map options 1147, 1157
mid-route depot 1178
open 1142, 1145
options 1157
origin 1178
post-route 1178
pre-route 1178
print 1158
printer 1132, 1138
query by address 1158, 1162
redeliverable stop 1178
rush hour mode 1158
save attributes 1136, 1139
save search 1142, 1145
search manager 1133, 1141, 1145
stop types 1178
stops 1178
tape measure 1158
time of day mode 1158
user defined landmark 1158
waits 1178
zoom in 1157
zoom out 1157
Icons in the Route Summary window 758
Ignoring assigned location types 495
Images
package types 141
Impasse
definition 1289
Import 347
deleting locations 353
module 11
Import layout sets
defining 1289
Import layouts
activities 439
bay type capacity 439
case 386
constant text 386
containers 429
daily orders import file available fields
Operations Guide
1329
Index
397
daily routes 415
defining 1289
Depot SKUs 434
drivers 426
employees 425
equipment 430
equipment types 435
explaining 383
export routes available fields 409
file information 383
layout setup window 385
line item container assignments 422
line items in MobileCast 420
location extensions available fields
393
location import file available fields
387
onboard import file available fields
405
order activities for MobileCast 424
order container assignments 421
package types 431
pallet type capacity 440
preprocessor 385
product order 419
route driver 421
route equipment in MobileCast 424
routed solution available fields 400
send orders available fields 406
setting the daily orders import file
layout 384
setting the location import file layout
384
setting the onboard import file layout
384
skill set activities 439
skill sets 438
SKU 432
SKU brands 434
stops 417
user upload available fields 412
Import module
combine from archive 376
explaining 348
Import orders options
explained 360
Import routed solution options
explained 370
Importer Module
daily import 362
importing routes 362
importing static routes 367
maintenance import 372
Importing
activities 372
batch import process 378
bay type capacity 372
breaks into MobileCast 362
containers 364, 372
daily orders 357
drivers 372
employees 372
equipment 372
equipment types 372
layovers into MobileCast 362
locations 350
locations and location extensions 354
locking orders 357
mid-route depots into MobileCast 362
onboard data 374
order activities into MobileCast 424
pallet type capacity 372
routes 362
scenarios into MobileCast 362
skill set activities 372, 439
skill sets 372, 438
SKU brands 372
specifying default active weeks and
service pattern set 354
static routes 367
unassigned stops into Dispatcher 419
Unassigneds 362
waits into MobileCast 362
Importing location extensions
specifying default active weeks 354
specifying default service pattern set
354
with locations 354
Importing locations
1330

Index
explaining 350
importing latitudes and longitudes 351
latitudes and longitudes 351
with location extensions 354
Importing orders
by routing session 358
into a single routing session 358
into multiple routing sessions 358
setting order import options 359
setting routed solution import options
369
Importing routed solution
by routing session 369
into a single routing session 369
into multiple routing sessions 369
Inactive stops
removing from Standard Routes 482
Increase Map Detail icon 1158
Integration Platform Service 32
Interactive graph
data boxes 319
options 317
Introducing
activities 170
Administration module 13
Loading Editor 693
netScheduler 1255
Planning Editor 587
Route History 1199
Routing Editor 441
skill sets 172
standard routes 474
the Dispatcher Module 753
Item notes
creating 850
J
Java Phones
allowing a driver to use Auto Arrive
and Depart 181
disabling confirmation dialogs 96
GPS data collection frequency 95
message polling rate 95
K
Key Performance Indicators Detail report
982
report 983
L
Landmark icon 1164
Lasso icon 1158
Last Stop is Destination 536
Launch Bar
Dispatcher module 1192
Layers
menu option 1191
Layovers
assigning in the Dispatcher 825
defining 1289
designate unplanned layovers as paid
78
enabling 78
icon 1178
Less than Minimum Orders report 984
Less Than Minimum Stops report 986
Limiting
routes by time in the Planning Editor
633
the load for a route in the Planning
Editor 631
Line Items
menu option 1187
Line items
creating the user defined field headers
67
defining 1289
using to calculate order sizes 59
Line Items in the Dispatcher
viewing notes 852
Line items in the Dispatcher
Operations Guide
1331
Index
adding 819
entering 819
entering actual quantities 823
processing 823
Line sequencing routes
Linking routes in the Routing Editor 520
List
duplicate geocodes in the Routing
Editor 518
reports in the Routing Editor 563
List windows 7
arranging 1136
changing columns 1139
changing the column size 1136
changing the font 1136
Column Manager 1139
creating reports from 1138
explaining 1132
exporting data 1138
hiding columns 1137
icons 1132
moving columns 1136
printing the entries 1138
restoring columns 1137
searching for entries 1141, 1143, 1145
selecting entries 1137
sorting the windows 1137
totals 1132
using 1132
using to evaluate routes in the Planning
Editor 637
viewing selected items 1137
Load
defining 1289
Load Admin
defining 1289
Load Admin in MobileCast 887, 892
granting rights 892
Load Available Routes 1190
defining 1289
Load ID
defining 1289
Load leveling 712
defining 1289
Load locations
defining 1289
Load locations in MobileCast 895
creating 895
Load module
options 708
Load phases
defining 1290
Load phases in MobileCast
assigned 887
available 887
claimed 887
complete 888
explained 887
transferred 887
Load Priority 560
Load Productivity
menu options 1181
Load productivity
defining 1290
Load Productivity report 990
Load Query feature in MobileCast 922
Load rights in MobileCast 887
adding or changing 892
load admin 892
load user 892
Load Selected Route(s) 1190
Load stops in MobileCast 895
Load Truck Diagram 988
Load Trucks options
Base Loading 717
choosing the loading methods 715
choosing the loading order 714, 717
choosing the methods 718
Keep SKUs on Adjacent Layers 716
Obey Bay Capacities 716
Re-order Remaining SKUs for Each
Bay/Pallet 717
Load trucks options
1332

Index
Alternate Sides of Vehicle (for same

stop) 717
alternate sides of vehicle (for same
stop) 717
Apply Prebuilt Solution 718
defining the options 708
driver options 716
Exclude Pkgs 718
excluding package types from being
loaded driver friendly 718
global options 712
hybrid _ driver first 710
hybrid _ warehouse first 710
Limit to One Stop per Pallet 717
Load bays according to capacity 717
load front to rear 712
load leveling 712
Load Prebuilts First 718
loading prebuilt stops 718
optimization pass 714
pallet loading 713
preference pass 715
site preference loading 717
stop quantity loading 717
warehouse friendly 710
warehouse options 713
Load Tuck options
Load Full Layers of the Same SKU
716
Load types
defining 1290
Load types in MobileCast
adding 897
Load user
defining 1290
Load Users in MobileCast 887, 892
granting rights 892
Load Validation Diagram 991
Loading
bay trucks in the Loading Editor 694
bulk trucks in the Loading Editor 700
SKUs in more than one bay 715
SKUs with common package types
715
Loading Editor 693

adding a pallet to a bay 738
Allow SKUs to Split Between Pallets
715
analyzing the loaded truck 738
and package types 133, 141
and SKUs 134
Bay Contents Tree View 730
calculating the bays capacity 721
capacity 738
capacity violation 726
changing route status 746
checking the capacity for a bay 738
checking the preferences for a bay 738
checking the properties for a bay 738
choosing a bays loading strategy 132
choosing the bay colors 721
choosing the colors for the bays 721
choosing the options 721
condensed view 724, 725
convertible bays 739
deleting a prebuilt solution 747
detailed view 724, 725
disabled bay used 726
editing trucks 737
entering 705
entering edit mode 720
Existing Package Preference Loading
715
exiting 751
exporting 748
exporting loaded routes 748
Layer view 735
loading bay trucks 694
loading bulk trucks 700
loading full pallets warehouse friendly
710
moving multiple SKUs to another bay
741
moving part of an SKU to another bay
742
moving product on the truck 737
moving SKUs 741
Operations Guide
1333
Index
moving SKUs between windows 744

moving SKUs to another bay 741
no capacity defined 726
no mix violations 726
options 725
Options notebook 721
percent full calculation 721
preferences 738
preparing to edit trucks 720
printing reports 750
properties 738
reload individual bay/pallet 740
save 746
save and lock 746
saving the result as a prebuilt solution
721
saving your work 746
selecting the warning messages 725
setting the pick order for warehouse
zones 138
setting up equipment preferences 132
setting up equipment types 126
setting up the options 721
showing active routes 721
SKU 729
SKU Tree View 731
Split SKUs window 728
stack order 725
stack rule violation 726
Stops Tree View 731
swapping bay/pallet contents 745
tools for analyzing the truck 738
Truck Profile 732
Unassigned SKUs window 728
unassigning SKUs 744
viewing the percent full of each bay
732
viewing unassigned quantity on routes
720
warning messages 725
working with 693
Loading Editor Options 725
selecting the warning messages 726
Loading Editor Options Notebook
choosing a default view in the Bay
Contents View 724

choosing the display options 723
choosing the stack order 724
General page 721
Truck Profile 723
Loading Editor windows
Layer View 735
SKU 729
SKU Tree View 731
Stops Tree View 731
Truck Profile 732
Unassigned SKUs 728
Loading Options 1191
Loading options 717
Loading preferences 263
adding 263
defining 1290
deleting 263
editing 263
explaining 263
Loading rules
bulk trucks 719
menu option 1179
Loading trucks 706
Alternate Sides of Vehicle (for same
stop) 717
alternate sides of vehicle (for same
stop) 717
creating a loading pass 708
driver options 716
Full Pallet Loading 713
hybrid _ driver first 710
hybrid _ warehouse first 710
Load bays according to capacity 717
Load Leveling 712
options 708
Preference Pass 715
selecting options 709
1334

Index
Stop Quantity Loading 717

warehouse friendly 710
warehouse options 713
Load-related items in MobileCast
adding 897
explaining 897
Loads
assign, defined 1284
available, defined 1284
claiming 1285
complete, defined 1285
phases of 1290, 1292
Loads in MobileCast 887
adding load rights 892
assigning 906
assigning to common carriers 909
assigning to existing routes 906
assigning to new route 907
cancelling 924
changing load rights 892
claim, then assign 898
claiming 905
common carriers 897
completing stops 911
create, then assign 898
customer commodities 897
default customer commodity 891
Default Detail Consignee to Bill To
891
default reference ID and description
890
delivery location 887
editing 920
equipment handling 891
example 1 898
example 2 898
example 3 898
example 4 899
example 5 899
freight classes 897
load admin 887
load admin default access to all regions
891
load locations 895
load phases 887
load rights 887

load types 897
load users 887
managing 898
meet point 887
on multiple route 914
pickup location 887
relay to another route 898
relaying 914
returning 925
searching for 922
setting the defaults 890
setup 889
STCC Codes 897
summary window 906
transfer 887
transfer to a common carrier 899
transfer to another region 899
transferring to common carriers 916
transferring to other regions 918
user rights 892
working with 887
loadtruckoptions
minimize bay usage 712
Locate
menu option 1189
Locate on Map 638
Locating
a city on the map 1162
a location extension in the Planning
Editor 650
a territory in the Planning Editor 650
a week in the Planning Editor 650
an address on the map 1162
an order in the Routing Editor 531
items in list or maintenance windows
1141, 1143, 1145
routes on the map in the Planning
Editor 638
Location defaults page 65
Operations Guide
1335
Index
Location Delivery Cost report 993

Location delivery costs
determining 54
Location Depot Summary
menu option 1183
Location extensions 250
adding 250
adding user defined fields 265
anchoring 661
assigning new service pattern sets in
assigning service time overrides 660
assigning service time overrides in the
Planning Editor 660
assigning to a territory 620
265
defining 1290
entering 250
importing 354
location on the map 638
suggest routes for 641, 645
suggest territory for 620, 645
user defined fields 265
viewing for a territory 604
Location import file layout
available fields 387
explaining 384
setting 384
Location notebook 240
Attributes page 240
Attributes tab 240
Equipment Types page 244
Extended Attributes page 242
Extended Attributes tab 242
FleetLoader page 253
FleetLoader tab 253
Location Extension page 250
Location Extension tab 250
Map page 256
Map tab 256
pages 237
Service Time Overrides page 248
Service Time Overrides tab 248
SKUs page 245
Time Window Overrides page 247

Time Window Overrides tab 247
Location Origin Summary window 690
Location overrides 259
adding 259
defining 1290
deleting 259
editing 259
explaining 259
Location preference loading
defining 1290
Location Returns report 996
Location Statistics report 997
Location substitutions 261
adding 261
defining 1290
deleting 261
editing 261
entering in the location notebook 244
explaining 261
Location types 235
adding 235
defining 1290
deleting 235
editing 235, 236
explaining 114, 235
synchronizing 66
Locations 237
add location notebook 240
adding 237
adding consignees 254
assigning a preferred route ID 243
assigning to employees 177
creating preferences for loading trucks
263
67
default service time 248
defining 1290
deleting 237
deleting service time overrides 239
deleting time window overrides 239
1336

Index
deleting upon import 353

determining the delivery cost 458
editing 237
entering address information 240
entering attributes 240
entering depot SKUs 245
entering extended attributes 242
entering location extension
information 250
entering service time overrides 248
entering time window overrides 247
explaining 237
geocoding 256
importing 350, 372
importing with location extensions 354
loading preferences 253, 263
menu option 1180, 1193, 1194
replacing information 239
service failure notification 255
setting the default type 66
setting the synchronization 67
setting the user defined field headers
67
substituting locations 244
substituting one for another 261
updating delivery days 680
updating the preferred route ID
updating Preferred route IDs from
voiding orders 243
voiding orders for 262
Locations with Orders
menu option 1188
Lock order
defining 1290
Locked resources in the Dispatcher 762
Locking
orders in the routing editor 511
Locking Orders 1266
Locking Orders in Day Commander 1266
Logging in to the Roadnet Transportation
Suite 9
M
Maintaining 47
items in Maintenance 48
the database 321
Maintenance 47
combining an archived session with a
current session 310
combining routing sessions 310
explaining 47
menu option 1182
menu options 1179
merging routing sessions 310, 573
module 11
Maintenance Import 372
error 366, 373
replace 366, 373
update 366, 373
Maintenance items 48
adding 48
deleting 49
editing 48
selecting defaults 50, 51
Maintenance windows 7
arranging 1136
changing columns 1139
changing the column size 1136
changing the font 1136
Column Manager 1139
explaining 1134
exporting data 1138
hiding columns 1137
icons 1134
moving columns 1136
printing the entries 1138
restoring columns 1137
searching for entries 1141, 1143, 1145
selecting entries 1137
sorting the windows 1137
totals 1134
viewing selected items 1137
Make default 50, 51
Operations Guide
1337
Index
Make Territories Options Notebook 611

Account Guidelines 614
Depots 614
General page 611
Optimizations 613
Reloads 613
Managing loads in MobileCast 898
claim then assign a load 898
create then assign a load 898
example 1 898
example 2 898
example 3 898
example 4 899
example 5 899
relay to another route 898
transfer to a common carrier 899
transfer to another region 899
Map
Map Navigation icons 1159
Map Options icon 1147, 1157
Map Properties notebook 1148
choosing the map display options 1148
City page 1151
Landmarks page 1150
Levels page 1149
Map page 1148
Misc. page 1155
specifying city information 1151
specifying landmark information 1150
specifying rush hour information 1153
specifying the landmark colors 1155
specifying the road colors 1149
specifying time of day restriction
information 1154
specifying zip code information 1152
Zip Code page 1152
Map Properties notebook in Dispatcher
set to show the stops delivery radius
761
Map Properties notebook in the Dispatcher
set map refresh 760
set to show the routes actual path 761
set to show unassigned stops 761
setting user preferences 760

Map Properties notebook in the Planning
Editor
Routes Page 602
setting preferences 600
specifying route appearance 602
specifying territory appearance 601
Territories Page 601
Map Properties notebook in the Routing
Editor
daily routes page 450
specifying standard route appearance
450
specifying the daily route appearance
450
toggling display of unassigned stops
450
Maps 1146
adding street segments 1165
adding user defined landmarks 1164
address path mode 1176
alternate route names 1167
and RouteNet 1146
assessing penalties globally 1173
barriers 287
blocking individual street segments
1170
cells 290
Center icon 1157
centering on an area 1159
city information 1151
creating global penalties 1173
creating impasses 1170
creating turn penalties 1173
customizing the appearance of 1147
daily routes in the Routing Editor 450
Decrease Map Detail icon 1158
deleting user defined landmarks 1164
disabled street segments 1170
displaying impasses 1170
displaying user defined landmarks
1164
Edit Street Attributes window 1170
editing historical travel speeds 1169
editing nodes 1170
1338

Index
editing street segments 1166

editing the network 1165
editing user defined landmarks 1164
elevation 1173
enlarging the area of view 1159
evaluating the network 1176
fading roads and background features
1147
finding a city 1162
finding a location 1162
finding a zip code 1162
finding an address 1162
Fit icon 1157
geocoding in the Planning Editor 665
hotkey shortcuts 1161
icons 759, 1157
in the Dispatcher 759
in the Dispatcher module 759
Increase Map Detail icon 1158
landmark colors 1155
landmarks 1150
Lasso icon 1158
loadable street segments 1170
locating an address 1162
locating unassigned stops in the
Dispatcher 837
locating user defined landmarks 1164
Map Properties notebook 1147
moving the map 1159
multi shortest path mode 1176
navigating the map 1159
node colors explained 1170
one way street segments 1170
opening in the Planning Editor 596
opening in the Routing Editor 445
Options icon 1157
Penalty Editor 1173
Print icon 1158
printing in the Planning Editor 671
Query by Address icon 1158
removing impasses 1170
removing routes from in the Planning
Editor 605
removing routes from in the Routing
Editor 454
removing territories 596
removing territories from 596, 605

restore zoom 1160
restoring previously saved settings
1148
road attributes 1149
Rush Hour Mode icon 1158
Save Zoom 1159
saving the zoom level 1159
selecting the rush hour model
displayed 269
selecting the time of day restriction
model displayed 279
selecting visible items 1147
setting up the map 1147
shortest path mode 1176
specifying the attributes 1148
stops and 760
street query 1162
symbols in the Dispatcher module 759
Tape Measure icon 1158
Territory Overview 618
Time of Day Mode icon 1158
undoing a zoom 1159
Update by Road Class 1174
updating the street network 1165
User Defined Landmark icon 1158
user settings 760
using in the Planning Editor 596
using in the Routing Editor 445
using the selected items list in the
Planning Editor 599
using to evaluate routes in the Planning
Editor 637
viewing route exceptions 800
viewing route exceptions in the
Dispatcher 797
viewing Route Scroll mode in the
Routing Editor 448
viewing selected items in the Planning
Editor 599
viewing selected items in the Routing
Editor 447
viewing unassigned stops in the
Dispatcher 837
Operations Guide
1339
Index
window type 7
zip code information 1152
Zoom In icon 1157
zoom in mode 1159
Zoom Out icon 1157
zoom out mode 1159
Zoom to Zip/City 1162
zooming in on an area 1159
zooming out from an area 1159
zooming to a city 1162
zooming to a zip code 1162
Max SKU 118
Maximum number of routes
returning when suggesting routes in
the Dispatcher 833
Maximum runtime
suggesting routes that do not exceed in
when suggesting routes in the
Dispatcher 834
Maximum stops per route
suggesting in the Dispatcher 834
when suggesting routes in the Routing
Editor 524
Meet point
defining 1291
Menu Options
Aliases 1196
Delete Prebuilt Solutions 1191
Duty Period History 1181
Export All Routes 1191
Menu options
About 1182
Account Type Summary 1183
Account Types 1179, 1184, 1188
Active 1193
Activities 1179, 1188
Actual Route/Stop 1181
Actual vs. Planned Comments 1181
Add Stops 1189
Anchoring 1185
Areas 1181, 1188

Assign Days to All 1185
Available 1193
Back Save 1183
Bay Contents 1191
Bay Tree View 1191
Cancel Stop Codes 1180
Canned Text Messages 1180, 1195
Cascade 1181
Close All 1181
Close Routing Session 1186
Close Session 1183
Codes 1194
Combine from Archive 1182
Combine Routing Sessions 1180, 1187
Common Carriers 1180, 1193
Compact Database 1180
Condensed 1191
Configure 1197
Container Types 1180
Containers 1180, 1194
Customer Commodities 1180, 1193
Customers 1180, 1193
Daily 1183
Data Transport 1180
Database Maintenance 1180
Delay Types 1180
Depots 1184, 1188
Detailed 1191
Dispatcher module 1192
Distance by Jurisdiction 1195
Driver Alerts 1180
Drivers 1184, 1188, 1194
Employees 1179, 1184, 1188, 1194
Equipment 1179, 1184, 1188, 1194
equipment 1184, 1185
Equipment Map 1192
Event Receipts 1195
Exception Rules 1180
Exceptions 1184, 1188
Exit 1179
Export Routes 1189
Favorites 1181
Freight Classes 1180, 1194
Futures 1188
1340

Index
Groups 1186, 1189, 1191

Help Topics 1181
Import Location Extensions 1182
Layers 1191
Line Items 1187
List 1186, 1189, 1191
Load Available Routes 1190
Load Productivity 1181
Load Selected Route(s) 1190
Loading Options 1191
Loading Rules 1179
Locate 1186, 1189
Location Depot Summary 1183
Location Extensions 1184
Locations 1180, 1193, 1194
Locations with Orders 1188
Maintenance 1182
Maintenance module 1179
Make All Territories 1185
Map 1179, 1187
Message Center 1192
My Routes Only 1193
Not Assigned 1193
Not Completed 1193
Not Considereds 1187
Notification Recipients 1196
OnBoard 1182
Onboard Codes 1180
Options 1180, 1185, 1189, 1190, 1196
Order Activities 1188
Order Financial Detail Codes 1180
Orders 1182, 1187
Organization Units 1196
Planning Sessions 1180
Position History 1192
Preferences 1180
Preferred Route Properties 1188
Prepare for Merchandising 1187
Prepare for Next Day 581, 1187
Print 1197
Print Setup 1179
Privileges 1196
Product 1179, 1188
Query 1193
Reason Codes 1180
Region Distances 1181
Regions 1196
Reports 1197
Route All Available Orders 1189
Route Overview 1192
Route Statuses 1180
Route Summary 1183
Route Types 1180
Route Watch 1192
Route Watch Map 1192
Routed Solution 1182
Routes 1184, 1187, 1189, 1191
Routing Sessions 1186
Save 1187, 1190
Save All Routes Area Attributes 1187
save and Lock 1190
Save Session As 1187
Save Standard Routes 1187
Save Window Positions 1181
Security 1196
Seed NetSchedule 1185
Selectors 1188
Send All Orders 1189
Service Pattern Set 1184
Service Patterns 1184
Service Rules 1179
service rules 1184
Session Transfer 1185
Sessions 1183
Sets 1189
Setup 1183
Shift Days 1185
Skill Sets 1195
SKU Tree View 1191
SKUs 1191
Speed Assign Active Routes 1189
Split SKU Tree View 1191
Static 1183
STCC Codes 1180, 1193
Stop Signature Codes 1180
Stop Tree View 1191
Stops 1184, 1187
Summary 1187, 1193
Territories 1184
Territory Scoreboard 1183
Tile Horizontally 1181
Tile Vertically 1181
Operations Guide
1341
Index
Toolbars 1186, 1189

Track Types 1180
Travel Models 1179, 1185, 1188
Truck Profile 1191
Types 1180, 1193
Unassigned 1184, 1189
Unassigned SKUs 1191
Unassigneds 1187, 1195
Undeliverable Stop Codes 1180
Update Configuration Key 1196
Update MobileCast 1185
Update Previous Days And Weeks
1185
Update Roadnet Daily Routes 1185
Update Service Times 1180
User Defined Data 1195
User Defined Fields 1179, 1185
User Groups 1196
User Notes 1195
User Upload 1185
Users 1196
Voids 1188
Weekly Summary 1187
Wireless Devices 1180
Wireless Events 1195
Zones 1180, 1188
Merchandisers 582
choose a rush hour model 584
creating a session for 582
defining 1291
routing 582
Merging routing sessions 310, 573
Message Center
menu option 1192
Message center
defining 1291
opening 865
using 864, 866
viewing a message 865
Metric or non-metric
setting the unit system 70
Mid-route depot
icon 1178

inserting on a daily route in the
Routing Editor 556
Mid-Route Source Depot
changing the service time in the
Routing Editor 558
removing the depot from a route in the
Routing Editor 558
replacing a depot on a route in the
Routing Editor 558
working with a mid-route source depot
on a daily route in the Routing
Editor 558
Mid-Route Sourcing
action when an order pair is broken
472
Editor 58
setting the service time 504
specifying which SKUs can go to a
depot 245
Mix rules
creating the methods 163
defining 1291
deleting 164
editing 164
Mix rules methods
adding 160
deleting 160
editing 160
explaining 160
Mixed
data quality 757
Mobile depot
defining 1291
Mobile Options notebook
allow drivers to add breaks and
layovers on the mobile device
99
allow drivers to add notes to stops,
orders, and line items while in
allow drivers to add pictures to notes
while in MobileCast
1342

Index
SmartPhone 99
allow drivers to add pictures to text
messages while in MobileCast
SmartPhone 100
allow drivers to arrive and wait at a
stop on the mobile device 100
allow drivers to call a location while in
allow drivers to cancel all unvisited
stops at one time on the mobile
device 100
allow drivers to cancel stops on the
mobile device 100
allow drivers to choose name from
Consignee History on the
mobile device 99
allow drivers to edit order and line item
quantities on the mobile device
100
allow drivers to edit Over, Short, and
Damaged quantities on the
mobile device 101
allow drivers to exit application while
on route 97
allow drivers to geocode on the mobile
device 96
allow drivers to redeliver completed
stops on the mobile device 97
allow drivers to resequence stops on
allow drivers to see days stops on
route before starting 100
allow drivers to see diagnostic
information on the mobile
device 99
allow drivers to see if a break, wait, or
layover is Paid or Unpaid on
allow drivers to text message on the
"Proceeding to" screen on the
mobile device 96
allow drivers to view quantities on the
mobile device 100
allow navigation application to
automatically start on the
mobile device 97
Auto Arrive/Depart Mode option for

MobileCast 106
automatically log out of MobileCast
when route is complete 97
collecting GPS data in transit 97
Java Phone page 103
Java-enabled phone options 103
remind driver to contact dispatcher
before returning to depot 97
require drivers to confirm actions on
mobile device 96
return to MobileCast SmartPhone and
display notification on the
mobile device 97
send all messages about stop, order,
and line item changes 98
setting GPS Frequency 95
setting message polling rate 95
setting the auto-arrive depart options
105
setting the general options 95
setting the Handheld options 108
setting the smartphone options 97
show column headers 98
show location information on the At
Stop screen on the mobile
device 99
show orders and line items on the same
screen 99
show rolled up quantities 102
show stops delivery and pickup
details to drivers on the Javaenabled phone 103
SmartPhone options 97
Telematics page 109
MobileCast
importing scenarios 362
Modify Start Time 653
Module
defining 1291
Modules
Administration 11
Dispatcher 11
Operations Guide
1343
Index
FleetLoader 11
Import 11
Loading Editor 11
Maintenance 11
maintenance 11
MobileCast 11
Planning Editor 11
Regions 11
Reports 11
Roadnet 11
Routing Editor 11
Territory Planner 11
Moving
an SKU to another window in the
Loading Editor 744
an SKU within a bay in the Loading
Editor 743
multiple SKUs to another bay in the
Loading Editor 741
part of an SKU to another bay in the
Loading Editor 742
452
SKUs between layers 735
SKUs between pallets 735
SKUs in the Loading Editor 741
SKUs on the truck 741
SKUs to another bay in the Loading
Editor 741
SKUs to the Unassigned window 744
stops between routes in the Dispatcher
846
the map 1159
Moving routes and stops to a new session
Moving SKUs
changing pallet type 743
partial 742
placing unassigned SKUs 741
to another bay/pallet 741
to another window 744
unassigning SKUs 744, 745
within bay/pallet 743
Multiple Pallet Pick Sheet report 998,
1006
My Routes Only
menu option 1193
N
Navigating the map 1159
Navigation
automatically start on the mobile
device 97
netScheduler
adding individual delivery windows
341
choosing the rush hour option 1262
filtering orders by classification 339
setting up delivery times 341
setting up delivery waves 333
setting up delivery windows 341
setting up order classifications 332
setting up the work shifts 333
newlink enableordersourcing 52
No capacity defined 726
No Matching Compartment Type route
exception 469
No mix violations 726
No Rush Hour
80
Editor 64
Session 207
Editor 57
Nodes
colors explained 1170
defining 1291
editing 1170
explaining 1170
Non-Passive Route
definition 1283
Not Assigned
menu option 1193
Not assigned Routes in the Dispatcher 762
Not Completed
menu option 1193
1344

Index
Not completed routes in the Dispatcher

762
Not Considereds
menu option 1187
Not considereds
routing 527
Notes
adding to stops 760
report 1000
viewing item notes 852
viewing route notes 852
Notes report 1000
Notification Recipients
menu option 1196
Notification recipients 32
Notifications
return to MobileCast SmartPhone and
display on the mobile device 97
Numeric search conditions 1143
O
Obey no mix rules
defining 1291
Obey stack rules
defining 1291
Off-Day Delivery and Less than Minimum
Stops report 947
Off-Day Delivery report 1001
OnBoard
adding codes 191
explaining the import file layout 384
import file available fields 405
menu option 1182
setting the import file layout 384
Onboard codes 191
adding 191
deleting 191
editing 191
explaining 191
menu option 1180
Onboard Integration
setting the handheld options 108
OnTrack
assigning locations for employees 177

creating the default depot 177
Resource Route by Day report 1017
generating stops 882
non-passive routing 882
passive routing 881, 882
Open icon 1142, 1145
Open time
defining 1291
Open/Close Exception report 1002
Opening
Depot Planner 688
Optimization pass
defining 1291
Optimization pass in the Loading Editor
714
Options
menu option 1180, 1185, 1189
Options in the Loading Editor 725
Options notebook in Administration
module 14
about 14
adding new RIC users 14
entering database user information for
user-defined data 14
setting the options for RIC 14
Options notebook in the Maintenance
module 51, 95
Alias page 67
allow additional stop types option for
MobileCast 78
allow override of actual stop times and
quantities during route in
MobileCast 78
auto generate route ID option for
MobileCast 77
auto generate unique DRT numbers
option for MobileCast 77
automatically fixup wireless events 81
automatically relocate equipment
option for MobileCast 81
calculate distance traveled by
jurisdiction 78
Operations Guide
1345
Index
calculate service time for MobileCast

78
choosing the size aliases 67
choosing the unit of bulk service 69
choosing the unit of cost 69
choosing the unit of measure 69
choosing the unit of service 69
Continuous Optimization page 90
Detail Level page 82
Device Diagnostics page 84
Dispatch - Load page 890
Dispatching page 76, 103
driver assignment required option for
MobileCast 78
Duty Period Monitor page 71
Enable SuperMatrix update 87
entering carbon emissions information
70
equipment assignment required option
for MobileCast 78
explaining 51, 95
General page 51
Location page 65
Planning General page 61
quantities are a ratio of size 1 option
for MobileCast 77
Routing General page 54
scheduling Route History to run 86
send API notifications option for
MobileCast 81
setting general routing defaults 54
setting the calculator option for
MobileCast 79
setting the default detail level for
MobileCast 83
setting the device diagnostics options
for MobileCast 84
setting the general dispatching options
77
for MobileCast 84
setting the historical travel speeds 89
setting the location defaults 65
setting the location type 66
setting the MobileCast continuous

optimization options 90
setting the reason code options for
MobileCast 81
setting the Route History options 86
setting the Schedule options 93
setting the SKU service time options
70
setting the SuperMatrix options 87
setting the synchronization options 67
stop critical minutes option for
MobileCast 79
Unit Reference page 69
validate quantities option for
MobileCast 81
Options notebook in the Planning Editor
590
Colors 592
Database Compacting 592
Display page 591
Drag/Drop 592
General 590
Time Window 591
Options notebook in the Routing Editor
458
assigning route IDs 463
Breaks/Waits page 460
choosing the default mouse actions
463
choosing the drag and drop actions 463
choosing the exceptions 467
Compacting the database 467
Display page 459
Drag and Drop page 463
General page 458
Order Locking page 471
setting the options to automatically add
breaks 460
setting the options to automatically add
waits 460
Split Orders 462
Time Window 462
order
1346

Index
cancel order on route 1259

updating order in Day Commander
1258
Order Activities
menu option 1188
Order activities
See Activities
viewing for stop in Dispatcher 756,
822
Order classifications 332
adding 332
introducing 332
Order Financial Detail Codes
menu option 1180
Order Financials
detail codes 214
adding 214
editing 214
viewing in the Dispatcher 822
Order Import Options 359
Order Locking 511
locking and unlocking orders 511
Editor 471
Order pair
defining 1292
Order Sizes
using line items to calculate 59
Order sourcing
considering when suggesting a route in
Dispatcher 836
considering when suggesting a route in
Routing Editor 526
enabling 51
finding the other part of an order pair
517
Order Status Codes
adding 216
editing 216
Order Summary
using 1259
Order Summary report 1004
Orders 151
adding 151
adding activities in the Dispatcher 822
adding financial details in the
Dispatcher 820
adding in the Dispatcher 819
adding line items or activities 156
adding order status codes 216
and overrides 155
assigning a preferred route ID 156
creating order financial detail codes
214
67
defining 1292
deleting 151
editing 48, 151
editing order status codes 216
entering actual quantities in the
Dispatcher 823
entering in the Dispatcher 819
entering individually in Cost Analyzer
1272
entering user defined field information
151
explaining 151
forcing bulk service time 154
import batches in Cost Analyzer 1278
import individually 1275
locking and unlocking 511
processing in the Dispatcher 823
setting the user defined field headers
67
specifying how can be combined 59
specifying the depot the order comes
from 153
specifying the Preferred MRS depot
for an order 153
viewing financial details in the
Dispatcher 822
viewing in Day Commander 1256
viewing notes 852
working with activities 170
Organization unit
defining 1292
Operations Guide
1347
Index
Organization Units
menu option 1196
Organization units 44
adding 44
explaining 44
Origin icon 1178
P
Package type preferences 132
Package types 141
adding 141
calculating bay capacities 144
defining 1292
deleting 141
dimensions 142
editing 141
entering capacities for a bay 144
entering pallet capacities 142
establishing preferences in Loading
Editor 132
explaining 141
import layout 431
importing 372
selecting a bitmap 141
selecting an image 141
selecting preferred bays 132
Paired order
defining 1292
Pallet capacity
setting 700
Pallet layering options 715, 719
apply loading order to partial layers
715, 719
keep SKUs on adjacent layers 716, 719
load pallets with layers 715, 719
obey partial layer mix rules 715, 719
obey partial layer stack rules 715, 719
partial layers at top of pallet
(maximum) 719
Pallet loading 713
defining 1292
Pallet loading methods 167
deleting 167
editing 167
explaining 167
Pallet loading options 715
enable pallet loading 718
obey bay capacities 719
partial layers at top of pallet
(maximum) 715
Pallet Pick Sheet report 1006
Pallet type
adding to a bay or truck in FleetLoader
738
allow manufacturers 715, 718
changing 743
default 715, 718
removing from a truck in the Loading
Editor 745
Pallet type capacity
import layout 440
importing 372
Pallet types
adding 168
deleting 168
editing 168
explaining 168
working with 168
Pass
defining 1292
Passive Route
definition 1283
Password
changing 9
Penalty
definition 1292
Penalty Editor 1173
changing street elevations 1173
editing nodes 1171
permission
defining 1292
Permissions 21
Phase
defining 1292
Pick Sheet report 1008
Pickup
defining 1292
1348

Index
Planned times/distance
updating in the Dispatcher 82
Planning depot locations 688
Planning Editor 587
adding a territory 625
adding maintenance items 589
allow time window processing when
creating routes 633
anchoring all location extensions 663
anchoring all location extensions in a
territory 661
anchoring location extensions 661
anchoring select location extensions
661
animating routes on the map 638
archiving the planning session 676
arranging favorite windows 588
Assign Days Options Notebook 630
assign sequential route IDs 654
assigning breaks to routes 655
assigning drivers to a territory 622
assigning equipment to a territory 622
assigning IDs to several territories 628
assigning new account types to
locations 659
assigning new service pattern sets to
assigning new service time types to
location extensions 659, 660
assigning new service time types to
locations 660
assigning new time window types to
locations 659
assigning resources to depots to create
territories 614
assigning service time overrides to
assigning start times to routes 653
assigning waits to routes 655
changing a routes properties 652
choosing how locations appear on the
map 602
choosing how route times, distances,
and costs are calculated 590
choosing the colors for the days and
weeks 592
choosing the database compact options

592
choosing the default drag and drop
options 592
choosing the Make Territories options
611
choosing the number of territories to
create 611
choosing the optimization parameters
for making territories 613
choosing the route exceptions 594
choosing the stop exceptions 594
choosing the territory creation strategy
611
choosing the territory marker for the
map 601
compacting the database 592
creating a backup save 649
creating routes 629
creating territories 610
creating territories with balanced run
time 613
Depot Planner 688
displaying the territories 604
dragging stops between routes 640
editing routes 640
editing the territories 620
enabling reloads 631
entering 588
evaluating the territories 616
exporting the routes 677
finding a location extension 650
finding a route 650
finding a stop 650
finding a territory 650
finding a week 650
flashing location extensions on the
map 638
flashing routes on the map 638
flip the routes 641
geocoding a location on the map 665
inserting depots onto a route in the
Planning Editor 657
introducing 587
line sequence the routes 641
Operations Guide
1349
Index
Locate 650
locating location extensions on the
map 638
locating routes on the map 638
maintaining items 589
modifying maintenance items 589
moving location extensions onto a
territory 620
moving stops from one route to another
640
moving stops to new delivery days 668
opening a map 596
opening a routes map 596
opening a territorys map 596
opening a weeks map 596
Plot Info window 598
printing driver directions 666
removing routes from a map 605
removing stops from a route or
territory 641
removing territories from a map 596,
605
routing exceptions 640
routing unassigned location extensions
645
saving an exact copy of session 674
saving the routes 649
sending the routes to MobileCast 684
sending the routes to netScheduler 686
sequence the routes 641
setting the advanced optimization
parameters 634
setting the general options 590
setting the optimization parameters for
creating routes 633
setting the time window options 591
setting the weights when creating
routes 630
setting time window options 591
shifting delivery days 668
specifying how account types should
be distributed among the
territories 614
specifying how routes appear on the
map 602
specifying how territories are
displayed on the map 601
specifying load limits when creating
routes 631
specifying reload parameters 631
specifying the time parameters for
creating routes 633
suggest routes 641, 645
suggest territory 620, 645
Territory Overview 618
time window the routes 641
toolbars 606
tracking the route and stop exceptions
593
transferring data to a new session 672
update MobileCast 684
update netScheduler 686
updating maintenance items 589
updating Roadnet daily routes 682
updating the delivery days for the
Routing Editor
Preventing off-day deliveries 680
uploading the routes to a network or
mainframe 677
User Upload 677
using list windows to evaluate routes
637
using maps 596
using maps to evaluate routes 637
using suggest routes 641, 645
using suggest territory 620, 645
using the Account Type Summary 619
using the Plot Info window 598
using the Properties notebook to assign
a driver or equipment to a
territory 622
using the Route Summary to evaluate
routes 638
using the selected items list 599
using the Territory Scoreboard 616
viewing account type information for
the territories 624
viewing account type information for
the territory 619
viewing overlap between territories
1350

Index
618
viewing routes 605
viewing territories and routes 604
viewing the selected items on a map
599
working with 587
Planning Editor Options notebook 590
choosing the default mouse actions
592
choosing the drag and drop actions 592
choosing the exceptions 593
choosing the time window options 591
Colors 592
Drag and Drop 592
General 590
Stop Exceptions 594
Time Window 591
Planning session
defining 1292
Planning sessions 205
adding 205
deleting 205
editing 205
explaining 205
menu option 1180
Playing back a route 790
Plot Info window
customizing in the Planning Editor 598
customizing in the Routing Editor 446
Position History
menu option 1192
Position history
following a route 790
following equipment 788
setting the map options 785
using the Find feature 787
using the GPS Playback Player 787
using the map 784
viewing 784
viewing cross streets 790, 791
viewing proximity to nearest city 790,
791
Post-route icon 1178
Post-route stops
adding to a route 536
adding to a standard route 477
displaying in the Dispatcher 756
icon 1178
putting on routes in the Routing Editor
494
Post-route time
Power unit
defining 1292
Prebuild Orders Customer Invoice report
1009
Prebuilt Pallet Pick Sheet report 1011
Prebuilt Pick Sheet report 1013
Preference pass 715
defining 1292
Preferences
menu option 1180
package types 132
SKUs 133
Preferred driver 131
Preferred package types 132
Preferred route ID
adding for a location 243
assigning to an order 156
creating route properties 538
Preferred route ID routing
assigning properties 541
assigning properties to the routes 538
creating routes 500
Preferred Route Properties
menu option 1188
Preferred route properties 538
assigning using Speed Assign 541
Preferred run time
Preferred SKUs 133
Operations Guide
1351
Index
Prepare for Merchandising 1187

Prepare for Next Day 581
menu option 1187
Preparing to edit trucks 720
Preprocessor
defining 1292
Pre-route icon 1178
Pre-route stops
adding to a route 536
adding to a route standard route 477
icon 1178
putting on routes 494
Pre-route time
Preventing package types from being
stacked 165
Previewing
reports 930
reports in the Truck Editor 750
Previous Days and Weeks
updating 664
Print icon 1158
Print Setup
menu option 1179
Printer icon 1132, 1138
Printing 1017, 1018
driver directions in the Dispatcher 868
driver directions in the Planning Editor
666
driver directions in the Routing Editor
564
driver directions to a file in the
Planning Editor 666
driver directions to a file in the Routing
Editor 564, 869
extended driver directions in the
Planning Editor 666
extended driver directions in the
Routing Editor 564
list and maintenance windows 1138
maps in the Planning Editor 671
report groups 935
reports in the Loading Editor 750

reports in the Planning Editor 670
reports in the Routing Editor 563
reports to a file 936
turn by turn driver directions in the
Planning Editor 666
turn by turn driver directions in the
Privileges
adding 21
assigning in a region 35
defining 1292
explaining
explaining the permissions 21
menu option 1196
Processing
line items in the Dispatcher 823
orders in the Dispatcher 823
Product
Product types
adding 146
assigning to SKUs 147
creating 146
definition 114
deleting 146
editing 146
explaining 146
Productivity
defining
driver 1286
load 1290
driver 183
load 183
Proof of delivery
saving signature 807
viewing 807
Pulp High
definition 1283
Pulp Low
definition 1283
Q
Quantity per layer 142
1352

Index
Quantity per pallet 142

Query
menu option 1193
Query by Address 1162
icon 1158, 1162
menu option 1166
Querying for loads in MobileCast 922
R
Rear Bay
defining 1293
Reason Codes
definition 1293
menu option 1180
Reason codes 209
adding 209
damaged 81
definition 209
delivery 81
over 81
pickup 81
setting 81
short 81
Redeliverable stops icon 1178
Reducing database size 50
Reference ID
defining 1293
Refreshing information in Dispatcher 885
Refreshing the data 1256
Re-geocode
Cancelled Stops 794
Region distances
menu option 1181
Regions 35
adding 35
assigning privileges to users 35
Assigning route limits 36
changing 43
changing to a different 40, 43
choosing rush hour and time of day
restriction models for the
region 41
choosing the default 43
cloning 39
defining 1293
deleting 40
explaining 35
giving users access 35
menu option 1196
module 11
selecting a default 43
transferring loads from MobileCast
918
Regular time
Relay
defining 1293
Relaying
load to another route in MobileCast
914
Reload
defining 1293
Reload time
for a route 506, 537
Remove from View 454, 596, 605
Removing
a depot from a route 557
a mid-route source depot from a route
duplicate locations from standard
routes 482
inactive stops from standard routes 482
orders from the problem 570
reload depots from a route in the
Planning Editor 657
routes from the map in the Planning
Editor 605
routes from the map in the Routing
Editor 454
stops from a route in the Routing
Editor 530
stops from a route or territory in the
Planning Editor 641
territories from a map 596, 605
Removing a search condition 1135
Operations Guide
1353
Index
Replacing
a mid-route source depot on a route in
Replacing location information 239
Replacing SKU service times 150
Report groups
creating 933
deleting 934
editing 934
printing 935
printing from the Planning Editor 670
printing from the Routing Editor 563
Report samples 1047
3-Column Pick Sheet 1098
1051
Actual vs. Planned Stop Detail 1052
All Loads 1128
Consolidated Off-Day Delivery and
1056
Days Serviced 1057
Delivery Detail 1058
Distance by Area 1059
Draft Daily 1061
Driver Checkout Sheet 1062
Driver Itinerary 1063
Driver Manifest 1064
Driver Performance 1065
Driver Performance for MobileCast
1091
Driver Returns 1068
Driver Service Log 1067
Driver Statistics 1069
Driver Survey 1070
Driver Utilization 1071
Equipment Utilization 1074
Equipment Utilization Metrics 1075
FleetLoader Stop List 1121
Global Cost 1076
Global Itinerary 1077
Global Manifest 1078
Global Time/Distance 1079
1080
1081
Less Than Minimum Orders 1082
Less Than Minimum Stops 1083
Location Delivery Cost 1087, 1088
Location Returns 1089
Location Statistics 1090
Multiple Pallet Pick Sheet 1092
Notes 1093
Off-Day Delivery Exception 1094
Open/Close Exception 1095
Order Summary 1096
Pallet Pick Sheet 1097
Pick Sheet 1098
1099
Prebuilt Pallet Pick Sheet 1100
Prebuilt Pick Sheet 1101
Re-Route Analysis 1104
Resource Utilization 1107
Roadnet Stop List 1120
Route Metrics 1109
Route Pallet Pick Sheet 1102
Route Pick Sheet 1103
Route Summary Statistics 1110, 1111
Route Variance 1112
Selection Summary 1113
Session Analysis 1114
Session Summary 1115
SKU by Package Type 1116
SKU Summary Sheet 1117
Standard Route Driver Survey 1118
Standard Route Stop List 1119
Territory Location 1122
Territory Stop List 1123
Territory Summary 1124
Time Window Exception 1126
Week Summary 1129
Report writer
defining 1293
1354

Index
Reports 927
3-Column Pick Sheet 1008
printing 1008
report sample 1098
setting options 1008
938, 940
report sample 1051
Actual vs. Planned Stop Detail 941
printing 941
report sample 1052
setting options 941
Actual vs. Projected Route Summary
printing 938, 940
adding 932
All Loads 1045
printing 1045
All Loads Analysis
report sample 1128
AvP Route Summary 938
AvP Stop Detail 939
carbon emissions 943
Compartment Detail Report 946
Compartment Summary Report 945
Consolidated Off-Day Delivery and
report sample 1056
creating 1199
creating from Route History 1199
Customer Delivery Cost 993
Day Serviced 949
printing 949
report sample 1057
setting options 949
deleting 932
deleting a report group 934
Delivery Detail 950
printing 950
report sample 1058
setting options 950
Distance by Area 952
printing 952
report sample 1059
Distance by Jurisdiction 953
Draft Daily 954
printing 954
report sample 1061

Driver Checkout Sheet 955
printing 955
report sample 1062
Driver Itinerary 956
printing 957
report sample 1063
setting options 956
Driver Manifest 958
printing 959
report sample 1064
setting options 958
Driver Performance 960, 962
printing 961
report sample 1065
setting options 960
Driver Performance for MobileCast
962
printing 962
report sample 1091
printing 963
report sample 1066
Driver Returns 964
printing 964
report sample 1068
Driver Service Log 966
printing 966
report sample 1067
Driver Statistics 965
printing 965
report sample 1069
Driver Survey 967
printing 967
report sample 1070
setting options 967
Driver Utilization 969
printing 969
report sample 1071
editing 932
Equipment Utilization 974
printing 974
report sample 1074
setting options 974
Equipment Utilization Metrics 975
printing 975
Operations Guide
1355
Index
report sample 1075

setting options 975
explaining 928, 937
exporting 936
formats 936
to a file 936
FleetLoader Stop List 1038
printing 1038
report sample 1121
Generating Note 854
Global Cost
printing 977
report sample 1076
Global Itinerary 978
printing 978
report sample 1077
setting options 978
Global Manifest 979
printing 979
report sample 1078
setting options 979
Global Time/Distance 981
printing 981
report sample 1079
grouping 933
item note 854
982
printing 982
report sample 1080
983
printing 983
report sample 1081
Less Than Minimum Orders 984
printing 985
report sample 1082
setting options 984
Less Than Minimum Stops 986
printing 987
report sample 1083
setting options 986
line item note 854
listing 937
printing 990
report sample 1085

printing 989
report sample 1084
printing 992
report sample 1086
Location Delivery Cost 993
printing 994
report sample 1087, 1088
setting options 993
Location Returns 996
printing 996
report sample 1089
Location Statistics 997
printing 997
report sample 1090
menu option 1197
module 11
Multiple Pallet Pick Sheet 998, 1006
printing 999
report sample 1092
setting options 998
Notes 1000
printing 1000
report sample 1093
Off-Day Delivery 1001
printing 1001
report sample 1094
Off-Day Delivery and Less than
Minimum Stops 947
printing 948
setting options 947
Open/Close Exception 1002
printing 1002
report sample 1095
options 928
order note 854
Order Summary 1004
printing 1004
report sample 1096
Pallet Pick Sheet 1006
printing 1007
1356

Index
report sample 1097

Pick Sheet 1008
printing 1008
report sample 1098
1009
printing 1010
report sample 1099
Prebuilt Pallet Pick Sheet 1011
printing 1011
report sample 1100
Prebuilt Pick Sheet 1013
printing 1013
report sample 1101
previewing 930
in the Loading Editor 750
previewing in the Routing Editor 563
printing 929, 936
in the Loading Editor 750
to a file 936
printing in the Routing Editor 563
Reroute Analysis 1015
printing 1016
report sample 1104
Resource Route by Day 1017
Resource Utilization 1019
printing 1019
report sample 1107
retrieving information from Route
History 1201
Roadnet Stop List
report sample 1120
printing 1020
report sample 1108
Route Metrics 1021
printing 1021
report sample 1109

route note 854
Route Pallet Pick Sheet 1022
printing 1022
report sample 1102
Route Pick Sheet 1024
printing 1024
report sample 1103
Route Summary Statistics 1026
printing 1027
report sample 1110, 1111
Route Variance 1029
printing 1029
report sample 1112
samples 1047
Selection Summary 1030
printing 1030
report sample 1113
service time maintenance 314
Session Analysis 1031
printing 1031
report sample 1114
Session Summary 1032
printing 1032
report sample 1115
SKU By Package Type
report sample 1116
SKU by Package Type 1033
printing 1033
printing 1034
report sample 1117
Standard Route Driver Survey 1035
printing 1035
report sample 1118
Standard Route Stop List 1036
printing 1036
report sample 1119
Stop Delivery 855
Stop List 1037
printing 1037
stop note 854
Operations Guide
1357
Index
Territory Location 1039

printing 1039
report sample 1122
Territory Stop List 1040
printing 1040
report sample 1123
Territory Summary 1041
printing 1041
report sample 1124
Time Window Exception 1042
printing 1043
report sample 1126
printing 1044
report sample 1127
Week Summary 1046
printing 1046
report sample 1129
zooming 936
Requesting drivers position in the
Dispatcher 780
Reroute Analysis report 1015
Resequencing in the Dispatcher
automatically 844
manually 844
stops 844
Reserved order
defining 1293
Resolving duplicate route IDs 489
Resource Route by Day report 1017
printing 1017
Resource Stop List report 1018
printing 1018
Resource Utilization report 1019
Resources
sharing 129
Resources in the Dispatcher
locked 762
Restore Zoom
Restoring
columns in list and maintenance
windows 1137
the maps zoom level 1160
Restricted Equipment
defining 1293
Retrieving
information from Route History 1201
Return
defining 1293
Returning a load in MobileCast 925
Revenue
defining 1293
Reversed order pair
defining 1293
Review Routes 1264
RH_BEST_DATA_VIEW 1221
RH_EMPLOYEE table 1236
RH_EQUIPMENT table 1237
RH_EQUIPMENT_TYPE table 1237
RH_LOCATION table 1238
RH_ORGANIZATION_UNIT table 1239
RH_REGION table 1239
RH_ROUTE_ACTUAL table 1239
RH_ROUTE_ACTUAL_VIEW 1214
RH_ROUTE_BASE_VIEW 1225
RH_ROUTE_BEST_DATE_VIEW 1221
RH_ROUTE_MASTER table 1244
RH_ROUTE_PLAN_VS_ACTUAL_VIE
W 1208
RH_ROUTE_PLANNED table 1242
RH_ROUTE_PLANNED_VIEW 1218
RH_ROUTE_VIEW 1203
RH_STOP_ACTUAL table 1245
RH_STOP_ACTUAL_VIEW 1227
RH_STOP_BASE_VIEW 1234
RH_STOP_MASTER table 1248
1231
RH_STOP_PLANNED table 1247
1358

Index
RH_STOP_PLANNED_VIEW 1229
RH_STOP_SIGNATURE table 1248
RIC 14
about 14
setting options for 14
Roadnet
send routes 1266
Route
defining 1294
Route All Available Orders
menu option 1189
Route Completion
automatically log off 97
Route exception rules 229
about 229
acknowledging exceptions 229
cloning pre-existing route exception
rules to make new rules 234
creating 229
defining 1294
defining parameters for 229
enabling 229
using wizard to create 229
viewing exceptions in Dispatcher 797
viewing in Dispatcher 229
Route exceptions
defining 1294
Duty Period Violation (Roadnet) 469
Exceeds Compartment Capacity 469
Exceeds Maximum Run Time 469
Exceeds Preferred Time 469
Exceeds Size 1, 2, 3 Capacity 469
No Matching Compartment Type 469
Stop Exceptions 469
Route exceptions in the Dispatcher
acknowledging exceptions 799, 800
creating route exception rules in
Maintenance 229
using Route Watch 798
using the Route Watch Map 800
viewing 797
viewing on the maps 800
Route Exceptions report 1020
Route History 1199, 1201

ERDs 1250
introducing 1199
retrieving information 1201
RH_EQUIPMENT table 1237
RH_EQUIPMENT_TYPE table 1237
RH_LOCATION table 1238
RH_ORGANIZATION_UNIT table
1239
RH_REGION table 1239
RH_RMPLEOYEE table 1236
RH_ROUTE_ACTUAL table 1239
RH_ROUTE_ACTUAL_VIEW 1214
RH_ROUTE_BASE_VIEW 1225
1221
RH_ROUTE_MASTER table 1244
RH_ROUTE_PLAN_VS_ACTUAL_
VIEW 1208
RH_ROUTE_PLANNED table 1242
1218
RH_ROUTE_VIEW 1203
RH_STOP_ACTUAL table 1245
RH_STOP_ACTUAL_VIEW 1227
RH_STOP_BASE_VIEW 1234
RH_STOP_MASTER table 1248
RH_STOP_PLAN_VS_ACTUAL_VI
EW 1231
RH_STOP_PLANNED table 1247
RH_STOP_PLANNED_VIEW 1229
RH_STOP_SIGNATURE table 1248
route views 1203
scheduling to run 86
stop views 1227
tables 1236
using views to gather stop information
1227
Route IDs
resolving duplicate IDs 489
Route List Window
opening in the Dispatcher 762
viewing the route on a map in the
Dispatcher 756
viewing the stops in the Dispatcher 756
Operations Guide
1359
Index
working with a route in the Dispatcher

756
working with a stop in the Dispatcher
756
Route Metrics reports 1021
Route notes
creating 850
deleting 851
editing 851
Route Overview
menu option 1192
Route Overview window
adding a list 754
deleting a list 754
viewing stops for a route in the
Dispatcher 754
working with a route in the Dispatcher
754
working with a stop in the Dispatcher
754
working with an order in the
Dispatcher 754
Route Pallet Pick Sheet report 1022
Route Pick report options 1022, 1024
Route Pick Sheet report 1024
Route query
using detailed criteria in the Dispatcher
778
using driver criteria in the Dispatcher
778
using equipment criteria in the
Dispatcher 778
using general criteria in the Dispatcher
778
using load criteria in the Dispatcher
778
Route reloads 520
automatically creating in the Routing
Editor 503, 504
choosing the action taken at the reload
503, 504
limiting the number per route 506
limiting time to the reload depot 506

selecting the reload depots 503, 504
setting the guidelines in the Routing
Editor 503, 504
setting the limits 506
setting the reload time 503, 504
Route Scroll mode 448
Route Session
Route status 116
adding 116
changing 746
defining 1294
definition 115
Route Statuses
menu option 1180
Route Summary
menu option 1183
Route Summary Statistics report 1026
Route Summary window
explaining the icons in the Dispatcher
758
Route type 116
adding 116
defining 1294
definition 114
Route Types
menu option 1180
Route Variance report 1029
Route views 1203
Route Watch
acknowledging exceptions 799, 800
menu option 1192
using 798
Dispatcher 798
Route Watch Map
menu option 1192
using 800
1360

Index

Dispatcher 800
Routed Solution
menu option 1182
RouteNet
and maps 1146
defining 1294
editing the network 1165
evaluating 1176
including reload depots 63, 206
setting the default routing method 55,
62, 79
Routes
accounting in the Dispatcher 883
adding breaks in the Dispatcher 825
adding in the Dispatcher 811
adding layovers in the Dispatcher 825
adding pre- and post-route stops 536
adding scenarios in the Dispatcher 812
adding stops in the Dispatcher 813
adding waits in the Dispatcher 825
assign sequential IDs in the Planning
Editor 654
assigning a driver #2 in the Dispatcher
765
assigning dispatchers in the Dispatcher
764
assigning drivers in the Dispatcher 764
assigning equipment in the Dispatcher
766
assigning equipment in the Routing
Editor 543
assigning equipment types to in the
Routing Editor 543
assigning resources in the Dispatcher
763
assigning start times in the Planning
Editor 653
assigning start times in the Routing
Editor 546
assigning wireless devices in the
Dispatcher 768
automatic resequencing in the
Dispatcher 844
balancing in the Routing Editor 514
calculating the time, distance, and cost

changing stop order in the Dispatcher
844
changing stops in the Dispatcher 815
changing the ID in the Planning Editor
652
changing the properties in the Planning
Editor 652
changing the starting time in the
Planning Editor 652
checking the assignments in the
Dispatcher 807
completing in the Dispatcher 775, 777
completing stops in the Dispatcher 772
conflicts when starting in the
Dispatcher 771
creating in the Dispatcher 811
creating in the Planning Editor 629
creating in the Routing Editor 488
67
creating using preferred route IDs 500
deleting in the Routing Editor 530
deleting stops in the Dispatcher 817
editing in the Planning Editor 640
entering actual quantities in the
Dispatcher 823
entering seal information in the
Dispatcher 765
finding in the Dispatcher 778
finding loads in MobileCast 922
letting Planning Editor suggest routes
641, 645
limiting the load in the Planning Editor
631
linking in the Routing Editor 520
manually resequencing in the
Dispatcher 844
menu option 1187, 1189, 1191
not assigned in the Dispatcher 762
not completed in the Dispatcher 762
review 1264
running in the Dispatcher 754
Operations Guide
1361
Index
selecting a dispatcher 765

selecting a reference number in the
Dispatcher 765
selecting a route type in the Dispatcher
765
specifying how they appear on map in
specifying how they appear on map in
starting in the Dispatcher 762, 769
swapping equipment in the Dispatcher
872
unassigning stops in the Dispatcher
817
unlinking in the Routing Editor 520
viewing exceptions in the Dispatcher
797, 798, 800
viewing in Route Scroll mode 448
viewing my routes only in the
Dispatcher 876
viewing notes 852
viewing on the map in the Planning
Editor 596
viewing on the map in the Routing
Editor 512
viewing position history in the
Dispatcher 790
working with OnTrack Routes in
MobileCast 881
working with unassigned stops in the
Dispatcher 830
Routes to consider in Continuous
Optimization
not completed 92
not departed 92
not started 92
todays routes only 92
Routes to consider when suggesting in the
Dispatcher
not completed 835
not departed 835
not started 835
todays routes only 835
Routing
unassigned orders in the Routing
Editor 488, 522

Routing Editor 441
adding a route 535
adding breaks to standard routes 484
adding items 444
adding layovers to standard routes 484
analyzing a route in Route Scroll mode
448
assigning an ID to a route 541
assigning drivers to a route 541
assigning equipment to a preferred
route 540
assigning equipment to a route 537,
541
assigning equipment types to a
preferred route 540
assigning equipment types to a route
537
assigning resources to a route 541
assigning route IDs when building
routes 463
assigning start times to routes 546
assigning upload selectors 553
automatically adding breaks 460
balancing routes 514
building routes 566
changing a routes properties 533
changing the routes depot 533
changing the routes driver 533
changing the routes max time 533
changing the routes model 533
changing the routes preferred time
533
changing the routes starting time 533
choosing the database compact options
467
choosing the route exceptions 468
combining an archived session with a
current session 573
combining routes 514
combining routing sessions 573
compacting the database 467
creating a new routing session 577
creating a route 535
creating daily routes 488
1362

Index
creating pre-and post-route stops 494

creating routes for more than one day
492
creating routing passes 490
determining the location delivery cost
458
displaying a route and surrounding
locations and routes 512
displaying order activities 459
displaying routes on a map 453
displaying the depot in the Stop list
459, 591
editing items 444
entering 443
explaining the advanced routing
strategies 498
geocoding a stop 519
inserting a depot onto a daily route 556
introducing 441
module 11
moving routes and unassigneds to new
session 581
Options notebook 458
placing breaks on routes 492
Plot Vicinity 512
printing driver directions 564
printing extended driver directions 564
removing a depot from a route 557
removing inactive stops from Standard
Routes 482
removing routes from a map 454
resolving duplicate route IDs 489
rolling routes and unassigneds to a new
session 581
routing all orders 488
Routing Pass Options notebook 490
routing selected orders 488
routing unassigned orders 488, 522
routing with skill sets 496
saving the routes attributes 549
saving the routes 552
selecting equipment types assigned to
routes 495
sequencing stops on a route 528
setting the auto break options 460

setting the auto wait options 460
setting time window options 462
setting up the toolbars 455
splitting orders 547
suggesting routes in 523
temporary regeocode 519
time window swap 515
transferring stops to another route 522
updating the delivery days from the
Planning Editor 680
updating the locations preferred route
IDs 561
using Route Scroll mode 448
using the Selected Items list 447
viewing a summary for a weeks routes
513
viewing items selected on a map 447
viewing routes 453
viewing routes in a list window 453
viewing selected routes 454
viewing the route on a map 512
viewing the routes for a day of the
week 512
viewing the routes fro a range of dates
512
working with 441
working with a mid-route source depot
on a daily route 558
Routing future orders 527
Routing General defaults page 54
Routing in MobileCast
allow drivers to geocode on the mobile
device 96
setting the allow additional stop types
option 78
setting the auto generate route ID
option 77
setting the auto generate unique DTR
numbers option 77
setting the automatically relocate
Operations Guide
1363
Index
equipment option 81
setting the calculator option 79
setting the driver assignment required
option 78
setting the equipment assignment
required option 78
84
setting the quantities are a ratio of size
1 option 77
setting the reason code options 81
setting the send API notifications
option 81
setting the stop critical minutes option
79
setting the validate quantities option 81
Routing not considered orders 527
Routing on the same side of the street 53
Routing orders 488
Routing Pass Options notebook 490
Auto Assign 502
Backtracking 508
Breaks 492
choosing orders to be routed 492
creating daily standard routes 493
creating routing passes 490
Dynamic routing 493
Extended Runs 507
filtering orders 492
Filters 492
General options 491
Post Process 508
Preferred Route ID Routing page 500
Reload Limits 506
Reloads 505
Resources 495
Restrictions 494
setting breaks 492
Split Orders 509
Standard Sequencing 509
Strategies - Basic 497
Strategies-Advanced 498
Time Window 502
using skill sets when creating routes
496
Weekly Routing 492

Routing session
importing into a single routing session
358
Routing sessions
choosing 443
creating a new 577
defining 1294
explaining 441
importing orders into multiple sessions
358
importing routing solutions into a
single session 369
importing routing solutions into
multiple sessions 369
menu option 1186
Routing void orders 527
Rush hour
80
Editor 64
Session 207
Editor 57
Rush hour area 270
changing the shape 273
changing the speed restrictions 273
choosing simple or advanced 270
creating 270
defining 1294
defining the speed variations 270
drawing the area 270
restricting equipment types in an area
270
Rush hour model 266
adding a rush hour area 270
adding a rush hour path 274
changing a rush hour area 273
changing the speed for an area 270
choosing for a region 41
choosing how displayed on the map
269
choosing model displayed on map 269
1364

Index
creating 267
defining 1294
editing 48
establishing the time periods 267
introducing 266
selecting the current model 269
80
Editor 64
Session 207
Editor 57
specifying the direction for a street 274
speed variations on streets 274
use 57, 64, 80, 207
use in netScheduler 1262
use in routing session 578
use merchandisers 584
rush hour model
use in planning session 674
Rush Hour Models
select in netScheduler 1262
Rush Hour Options
use historical travel speeds in
netScheduler 1262
use historical travel speeds in planning
session 675
use no rush hour in netScheduler 1262
use no rush hour in planning session
674
use rush hour models in netScheduler
1262
use rush hour models in planning
session 674
Rush Hour options
select rush hour models in
netScheduler 1262
Rush hour options
use historical travel speed with
merchandisers 584
use historical travel speeds in routing
session 579
use no rush hour in routing session 578
use no rush hour with merchandisers

584
use rush hour model with
merchandisers 584
use rush hour models in routing session
578
Rush Hour page 1153
Rush hour path 274
changing the attributes 276
changing the length 276
changing the speed 274
creating 274
defining 1294
deleting 276
restricting equipment types 274
specifying direction on the path 274
S
Same side of street routing 53
sample SQL statements 1201
Save
Save All Routes Area Attributes
menu option 1187
Save and Lock 1190
Save Attributes icon 1133, 1136, 1139
Save Search icon 1142, 1145
Save Session As
menu option 1187
Save Standard Routes
menu option 1187
Save zoom
menu option 1160
Saving
a routing session 577
area attributes 549
backup saves in the Planning Editor
649
copy of the current session 674
the maps zoom level 1159
the routes attributes in the Routing
Editor 549
Operations Guide
1365
Index
your work in the Loading Editor 746

Scan
Quality 809
Scan status
containers 807
Scanning
on the SmartPhone 97
setting up check-off scanning 102
setting up increment scanning 101
Scenarios 194
adding 194
defining 1294
deleting 194
editing 194
explaining 194
Schedule
Scheduling Route History to run 86
Scheduling the SuperMatrix update 87
Seal
defining 1294
Search Manager
creating a condition 1141
creating an AND search 1142
creating an OR search 1142
date/time search conditions 1144
defining 1294
deleting a saved search 1142
editing a saved search 1142
icons 1133, 1141, 1145
numeric search conditions 1143
removing a filter 1142
removing a search condition 1135
retaining results of previous search
1142
running time search condition 1144
searching for entries meeting all
conditions 1142
searching for entries meeting multiple
criteria 1142
searching for entries meeting one of
multiple conditions 1142
string search conditions 1144
types of conditions 1143

using previously saved searches 1141
Searching for entries 1141, 1143, 1145
Searching for loads in MobileCast 922
completed loads 922
on routes 922
Security
menu option 1196
See Disabling Wireless
Communication 866
See Privileges modules
Security options
checking login credentials at next login
20
creating authentication policy 16
locking out all non-super users 19
requiring all users to change password
at next login 20
Segment
defining 1294
Selected Items list 447, 599
Selecting
Java-enabled phone options 103
SmartPhone options 97
the current time of day restriction
model 279
the default drag/drop options in the
Planning Editor 592
the warning messages in the Loading
Editor 725
selecting 715, 718
Selecting a default region 43
Selecting defaults
for maintenance items 50, 51
Selection Summary report 1030
Selectors
menu option 1188
Send All Orders
menu options 1189
send routes to Roadnet 1266
Sending
messages to drivers in the Dispatcher
867
1366

Index
orders from the Routing Editor 567

routes from Territory Planner to
Roadnet 682
routes from the Planning Editor 682
routes to MobileCast from Roadnet
569
routes to MobileCast from Territory
Planner 684
routes to netscheduler from Territory
Planner 686
stops from the Routing Editor 575
Separated order pair
defining 1294
Sequencing
standard routes in the Routing Editor
486
Sequential route IDs
Sequential Territory IDs 628
Service failure
defining 1294
Service Monitor
defining 1294
Service pattern sets 202
adding 202
defining 1295
deleting 202
editing 202
explaining 202
menu option 1184
Service patterns 200
adding 200
defining 1294
deleting 200
editing 200
explaining 200
menu option 1184
Service Rules
menu option 1184
Service rules
menu option 1179
Service time
adjusting for a stop in the Routing
Editor 559
adjusting for skill sets 172
defining 1295
establishing for a SKU 147
explaining 196
for an activity 170
forcing bulk service time 154
replacing for a group of SKUs 150
updating 312, 316
using SKU service time with bulk
orders 70
Service time maintenance 312
defining 1295
graph options 317
report 314
setting the variance 313
setting update criteria 312
using the graph 318
viewing the report 315
Service time maintenance graph 316
action buttons 320
by location 317
by service time type 317
changing actual service time 319
changing computed service time 319
changing service time variance 319
computed 319
data boxes 319
deliveries 319
explaining the options 317
previous 319
recompute service times 320
save actual stops 320
update service times 320
variance 319
Service time overrides
defining 1295
Service time types 195
adding 195
defining 1295
deleting 195
editing 195
Operations Guide
1367
Index
explaining 195
Session 1185
Session Analysis report 1031
Session Summary report 1032
Session Transfer 672
Sets
menu option 1189
Setting
a quantity threshold to load driver
friendly 711
Continuous Optimization to have
MobileCast assign unassigned
stops 90
Continuous Optimization to have
MobileCast transfer stops 90
options in the Planning Editor 590
options in the Routing Editor 458
options to automatically add breaks in
options to automatically add waits in
order import options 359
planning session defaults 61
route calculation options in the
Planning Editor 590
routed solution import options 369
service time graph options 317
the FleetLoader options 721
time window options in the Planning
Editor 591
time window options in the Routing
Editor 462
up the toolbars in the Planning Editor
606
up the toolbars in the Routing Editor
455
Setting the alias 46
explaining 46
Setup
menu option 1183
Sharing
employees 129, 176
equipment 129, 131
resources 129
undoing 129, 131, 176
Shifting delivery days in the Planning
Editor 668
Shortest Path Mode
menu option 1176
Show Nodes
menu option 1171
Shuttle Distance
defining 1295
Shuttle Time
defining 1295
Signatures
saving to file 807
Simple rush hour area
defining 1295
Site preference loading 717
Size precision
defining 1295
setting up 70
Sizes
naming 67
setting the decimal place 70
Skill Set
change 1263
change properties 1263
SKill sets
importing 372
Skill Sets
menu option 1195
Skill sets 340
adding 172, 340
adjusting the service time 172
assigning activities 172
assigning to employees 175
changing 340
Optimization 92
considering when creating routes 496
1368

Index
the Dispatcher 835

deleting 172, 340
editing 172
import layout 438
importing activities 439
introducing 172, 340
SKU brands 140
adding 140
defining 1295
deleting 140
editing 140
import layout 434
importing 372
SKU by Package Type report 1033
SKU preferences
setting in Loading Editor 133
SKU Summary Sheet report 1034
SKU Tree View 731, 1191
SKUs 147
adding 147
defining 1295
deleting 147
editing 147
establishing preferences in Loading
Editor 133
establishing service time for 147
explaining 147
ignoring service time on bulk orders 70
import layout 432
importing 372
menu option 1191
moving in the Loading Editor 737
replacing manufacturer pallet type for
a group 150
replacing service times for a group 150
replacing warehouse information for a
group 150
selecting preferred bays 134
selecting the warehouse zone 148
Small SKU loading

defining 1295
SmartPhones
adding breaks and layovers 99
adding orders and line items 99
arrive and wait 100
calling locations 100
canceling all unvisited stops at one
time 100
canceling stops 100
choose name from Consignee History
99
control stop, order, and line item
messages sent to mobile device
98
display notification when another
application is in use 97
displaying user defined fields 97
driver permissions 97
edit order and line item quantities 100
edit Over, Short, and Damaged
quantities 101
exit application while on route 97
GPS data collection frequency 95
GPS data collection in transit 97
log out of MobileCast automatically 97
message polling rate 95
reconciling orders 101
remind driver to contact dispatcher
before arriving at depot 97
resequencing stops 100
see if a break, wait, or layover is Paid
or Unpaid. 99
setting up scanning 97
show column headers 98
show location information at stop 99
show orders and line items on the same
screen 99
show rolled up quantities 102
start navigation application
automatically 97
view diagnostic information 99
view quantities 100
Operations Guide
1369
Index
Sorting
the list or maintenance window 1137
Specifying
how orders can be combined 59
how territories are created 611
number of territories to create 611
optimization parameters for Make
Territories 613
the depot the order originates from 153
the MRS depot for an order 153
which fields to synchronize 67
Speed Assign
using 541
Speed Assign Active Routes
menu option 1189
Split SKU Tree View 1191
Splitting cells 294
Splitting orders in the Routing Editor
automatically 509
manually 547
options 462
Split Orders page 509
Stack rules 165
creating the methods 165
defining 1295
establishing 165
explaining 165
violations 726
Stack rules methods
adding 159
deleting 159
editing 159
explaining 159
Standard Route Driver Survey report 1035
Standard route sequencing 509, 528
Standard route sets
deleting 475
editing 475
Standard Route Stop List report 1036
Standard routes
adding breaks 484
adding layovers 484
adding pre- and post-route stops 477

adding stops to a route 480, 482
adding to sets 479
combine 486
creating 474
creating daily standard routes 493
creating from daily routes 478
creating standard route overrides 478
defining 1295
deleting 478
deleting sets 475
dragging stops to a route 482
editing 478
editing sets 475
explaining 441, 474
flip 486
introducing 474
line sequence 486
locking 474
removing assigned locations from
Standard Unassigneds window
482
removing duplicate locations 482
removing from a set 479
removing inactive stops 482
saving 487
sequencing 486
specifying the day 477
using as the basis for daily routes 509
Start time
data quality 757
Starting
Starting Depot Planner 688
Starting Quantity
9
State
Static
1370

Index
menu option 1183

Static route sets
defining 1295
Static routes
creating in the Dispatcher 849
defining 1295
importing 367
Status bar 759
Statuses
Container 808
STCC Codes 897
adding 897
Stop Exceptions route exception 469
Stop List report 1037
Stop quantity loading
defining 1295
Stop Signature Codes
menu option 1180
Stop signature codes 213
adding 213
definition 213
deleting 213
editing 213
explaining 213
Stop Tree View
menu option 1191
Stop type
definition 1295
Stop type icons
breaks 1178
cancelled stops 1178
destination 1178
layovers 1178
mid-route depot 1178
origin 1178
post-route 1178
pre-route 1178
redeliverable stops 1178
stops 1178
waits 1178
Stops
adding to a route in the Dispatcher 813
automatic resequencing in the

Dispatcher 844
cancelling in the Dispatcher 848
changing arrival/departure dates/times
changing delivery info in the
Dispatcher 774
changing on a route in the Dispatcher
815
changing order on a route in the
Dispatcher 844
completing all at once in the
Dispatcher 774
completing in the Dispatcher 772
67
deleting from a route in the Dispatcher
817
Delivery Report 855
enforcing begin and end dates when
suggesting routes in the
Routing Editor 524
entering reason codes in the Dispatcher
774
icon 1178
manually resequencing in the
Dispatcher 844
menu option 1187
moving between routes in the
Dispatcher 846
putting pre- and post-route stops in
494
removing from a route or territory in
resequencing in the Dispatcher 844
setting the Group Unloading option for
MobileCast 84
swapping equipment in the Dispatcher
872
transferring between routes in the
Dispatcher 846
unassigning from a route in the
Dispatcher 817
viewing line item info in the
Dispatcher 774
Operations Guide
1371
Index
viewing notes 852

viewing order info in the Dispatcher
774
working with on a map 760
Stops Tree View 731
Street query 1162
Street segments
adding 1165
defining 1295
editing 1166
restricted 1173
String search conditions 1144
Suggest route
using in Dispatcher 832
using in Routing Editor 523
Suggest Territory/Routes in Planning
Editor 645
about 645
routing unassigned location extensions
645
setting score weighting factors 645
specifying criteria 645
specifying number of suggestions to
display 645
using suggest routes 641, 645
using suggest territory 620, 645
Suggesting routes in the Dispatcher 832
adjusting start time increments 833
Consider Before Next Arrival 835
considering best distance 832
considering best route criteria 832
considering best time 832
considering best time window 832
considering not completed routes 835
considering not departed routes 835
considering not started routes 835
considering todays routes only 835
enforcing duty period rules 835
835
making all time windows 832
maximum number of routes to return
833
maximum stops per route 834

permitting adjustment of minimum
start time 832
Placinng stops on current routes 835
selecting minimum route start time 833
setting maximum runtime 834
Suggesting routes in the Routing Editor
considering best distance 524
considering best route criteria 524
considering best time 524
considering best time window 524
enforcing capacity restrictions 524
enforcing compartment restrictions
524
enforcing duty period rules 525
525
enforcing stops begin and end dates
524
preferred route ID 525
stops per route 524
time restrictions 524
Summary
SuperMatrix
defining 1295
scheduling a daily update 87
scheduling to run the daily update 87,
93, 95, 105, 108
setting the default routing method 56,
63, 79, 207
Surveys
adding 218
assigning questions to the survey 220
assigning to a route in the Dispatcher
812
assigning to a stop in the Dispatcher
815
creating the questions 219
introducing 218
viewing post-route results 808, 810,
812
viewing pre-route results 808, 810, 812
1372

Index
viewing stop results 815

Swapping
SKUs between bays/pallets 745
Swapping equipment in the Dispatcher
872, 873
assigning equipment 872
Switching regions 40, 43
T
Tape Measure icon 1158
Territories
assigning sequential IDs 628
choosing the map marker 601
defining 1296
editing 620
estimating 616
estimating based on possible reloads
613
evaluating using the tools of the
Planning Editor 616
letting Planning Editor suggest
territory 620, 645
moving location extensions onto a
territory 620
specifying how they appear on map
601
viewing in the Planning Editor 604
viewing on the map 596
viewing the location extensions 604
Territory Location report 1039
Territory Scoreboard 616
menu option 1183
Territory Stop List report 1040
Territory Summary report 1041
Tile
Horizontally 1181
Vertically 1181
Time of Day page 1154
Time of Day Restriction
defining 1296
Time of day restriction
changing the shape 283
create a time of day area 277
create a time of day path 277
display on map 277

select a model 336
Time of day restriction area
changing a time of day restriction area
283
Time of day restriction model
adding 277
adding a time of day restriction area
281
adding a time of day restriction path
283
choosing for a region 41
creating 277
establishing the time periods 277
restricting a street 283
restricting equipment in an area 281
selecting how displayed on the map
279
selecting model displayed on the map
279
selecting the current model 279
setting the default for Planning Editor
64
80
Editor 57
Time of day restriction path
changing the attributes 285
deleting 285
Time of Day Restrictions
displaying on the map 1154
Time window
defining 1296
swapping routes in the Routing Editor
515
Time Window Exception report 1042
Time window factor
Time window override
defining 1296
Time Window Override report 1044
Time window threshold in Continuous
Optimization 91
Operations Guide
1373
Index
Time window types 198

adding 198
defining 1296
deleting 198
editing 198
explaining 198
Time windowing routes 515
Time windows
assigning stops that meet in
assigning stops that meet limits in
reassigning stops that meet limits in
Time windows in the Planning Editor
sequencing routes 641
setting for Assign Days 633
using when creating routes 633
Time windows in the Routing Editor
sequencing stops 528
Time zone
changing a stops in the Dispatcher 816
choosing display options 51
Toolbars
menu option 1189
Toolbars in the Planning Editor
General 606
Location 606
Routing 606
Territory 606
Toolbars in the Routing Editor
General 455
Route 455
setting up 455
Standard Route 455
Stop 455
Totals
for selected items only 1132
in list windows 1132
in maintenance windows 1134
Tour of Duty
defining 1296
Track Types
menu option 1180
Track types
defining 1296
definition 115, 883
Tracking
driver and loader productivity 183
drivers in the Dispatcher 780
drivers using GPS playback in the
Dispatcher 780, 790
equipment in the Dispatcher 782
route exceptions in the Planning Editor
593
route exceptions in the Routing Editor
468
stop exceptions in the Planning Editor
593
stop exceptions in the Routing Editor
469
Tracking distance by jurisdiction 877
Tracking distance by mile 877
Transferring
data to a new planning session 672
defining 1296
load to another region in MobileCast
918
loads to common carriers in
MobileCast 916
stops between routes in the Dispatcher
846
stops in Dispatcher using Continuous
Optimization 90
stops to another route in the Planning
Editor 640
stops to another route in the Routing
Editor 522
Transporting data to UPS Logistics
Technologies 327
Travel Models
Travel restrictions 123
1374

Index
Travel time models 186

adding 186
defining 1296
deleting 186
editing 186
explaining 186
Travel times
adjusting 124
Trip
defining 1296
Troubleshooting the wireless device 803
Truck Profile
menu option 1191
window 732
Truck profile options 723
bay numbers 723
cab 723
overloaded color 723
stop numbers 723
top-down view for sideloaders 723
Types
U
Unassigned orders in the Routing Editor
routing 522
Unassigned Quantity
viewing on routes 720
Unassigned SKUs
menu option 1191
window 728
Unassigned stops in the Dispatcher
adding 838
assigning to a route 830
combining with an existing stop 836
deleting 842
editing 838
importing 419
locating on a map 837
working with 830
Unassigneds
definition 1296
importing 362

Unassigning
SKUs from a truck in FleetLoader 744
stops in the Dispatcher 817
stops in the Routing Editor 530
Undeliverable Stop Codes
menu option 1180
Undeliverable stop codes 212
adding 212
deleting 212
editing 212
explaining 212
Undoing a zoom on the map 1159
Unit
definition 1283
Unit of bulk service
setting option 70
Unit of cost
setting option 70
Unit of loading
setting the option 70
Unit of measure
setting option 70
Unit of service
setting option 70
Unit reference
setting option 69
Unit set
definition 1283
Unit System
setting the option 70
Unlinking routes 520
Unlocak order
defining 1296, 1297
Unlocking
orders in the routing editor 511
Unlocking Orders 1266
Unlocking Orders in Day Commander
1266
Unrouteds
routing in the Planning Editor 640
Operations Guide
1375
Index
Update by Road Class

menu option 1174
Update Configuration Key
menu option 1196
Update criteria
in service time maintenance 312
setting the variance 313
Update Duty Period history option 58, 579,
585
update order in Day Commander 1258
Update Previous Days And Weeks
menu option 1185
Update Previous Days and Weeks
general 664
Update Service Times
menu option 1180
Updating
a locations delivery days 680
locations preferred route IDs 561
maintenance items in the Planning
Editor 589
MobileCast with Roadnet 5000 routes
569
MobileCast with Territory Planner
routes 684
netScheduler with Territory Planner
routes 686
planned times and distances in the
Dispatcher 82
Roadnet daily routes from Territory
Planner 682
speeds by road classification 1174
Updating service times 316
by service time type 312
explaining 312
Upload selector
assigning to a route 553
assigning to a stop 553
assigning to an order 553
Uploading
orders in the Routing Editor 567
routes to a network or mainframe from
User Defined Data 15

about 15
entering database user information 15
menu option 1195
User defined fields
creating the headers for location
extensions 265
defining 1296, 1297
displaying on the SmartPhone 102
User defined landmarks
adding 1164
deleting 1164
displaying 1164
editing 1164
locating 1164
User fields
entering order information 151
location notebook 67
User Groups
menu option 1196
User groups 26
adding 26
adding users 26
allowing to use Roadnet Performance
Dashboard 27
defining 1296, 1297
explaining 26
giving access to a region 35
User Notes
menu option 1195
User notes
creating 855
deleting 856
editing 856
viewing 855
User rights in MobileCast 892
User Upload 677
User-Defined Data
about 880
viewing data for user-defined table 880
viewing user-defined data for specific
1376

Index
route 880
Users 28
adding 28
adding to user groups 26, 28
allowing to bypass authentication
policy 29
allowing to use Roadnet Performance
Dashboard 30
checking login credentials at next login
20
defining 1296, 1297
deleting 28
disabling 29
editing 28
explaining 28
giving access to a region 35
granting full access to the suite 28
introducing 28
locked out 31
locking out all non-super users 19
menu option 1196
module 11
requiring to change password at next
login 29
setting load rights in MobileCast 892
Using
Layer view 735
list windows 1132
manual 1131
maps in Dispatcher 759
maps in the Routing Editor 445
Plot Info window in the Planning
Editor 598
Plot Info window in the Routing Editor
446
SKU and Stops Tree View 731
SKU Tree View 731
SKU window 729
standard route fragments 509
Suggest Route in Dispatcher 832
Suggest Route in the Routing Editor
523
Territory Scoreboard to evaluate the
territories 616
the Route List window in the
Dispatcher 756
the Route Overview window in the
Dispatcher 754
the Route Summary window in the
Dispatcher 757
the where function in the Dispatcher
780
Truck Profile 732
Unassigned SKUs window 728
using order summary 1259
V
Variable costs 123
Variable fee
defining 1296, 1297
Variable service time
defining 1296, 1297
setting the detail default 70
Variance 313, 319
Vehicle Road Restrictions
enabling and disabling for routing
sessions 79
View windows
bay/pallet contents 727
bay/pallet contents tree 730
layer 735
SKU tree 731
SKU window 729
split SKU 728
stops tree 731
truck profile 732
unassigned SKUs 728
Viewing 880
a message in the message center 865
account type distribution across
territories 619
account type information for the
territories 624
area attributes on a map in the Routing
Editor 451
daily routes in Route Scroll mode 448
Operations Guide
1377
Index
data for user-defined table 880

diagnostic information for the wireless
device 803
event receipts for a route 808
event receipts in the Dispatcher 863
line item detail in the Dispatcher 774
list items in the Dispatcher 875
my routes only in the Dispatcher 876
order activities in Dispatcher 756, 822
order detail in the Dispatcher 774
order financial details in the
Dispatcher 822
overlap between territories 618
position history 784
post-route survey results 808, 810, 812
pre-route survey results 808, 810, 812
route exceptions in the Dispatcher 797,
798, 800
routes for a day of the week in the
Routing Editor 512
routes for a range of dates in the
Routing Editor 512
routes in a list window in the Routing
Editor 453
routes on a map in the Routing Editor
512
saved area attributes in the Routing
Editor 451
454
selected items in list and maintenance
windows 1137
selected routes in the Routing Editor
454
stop survey results 815
stops for a route in the Dispatcher 754
stops on a route in the Routing Editor
454
summary of selected routes in the
Routing Editor 513
summary of the routes in the Routing
Editor 513
territories and routes in the Planning
Editor 604

the loaded truck in the Loading Editor
738
the stops for a route in the Dispatcher
756
unassigned quantity on routes 720
user-defined data 880
user-defined data for specific route 880
wireless events for a route 807
Viewing a delivery location 1257
Viewing Delivery Wave 1257
Viewing Delivery Window 1257
Viewing orders for a specific delivery
wave 1257
Void locations 262
adding 262
defining 1296, 1297
deleting 262
editing 262
explaining 262
Void orders
creating 154
routing 527
Voids
menu option 1188
W
Waits
adding in the Planning Editor 655
automatically added in the Routing
Editor 460
defining 1296, 1297
designate unplanned waits as paid 78
enabling 78
icon 1178
Editor 460
Warehouse Friendly 710
1378

Index
defining 1296, 1297

Warehouse zone pick order methods
adding 162
deleting 162
editing 162
explaining 162
Warehouse zones 138
adding 138
assigning to an SKU 148
choosing the pick order 139
deleting 138
editing 138
explaining 138
setting the pick order 138
setting up the methods 162
Warehouse-friendly loading options 713
Allow SKUs to split between bays/
pallets 714
existing package preference loading
714
full pallet loading for same SKU 713
load full pallets only 713
Package Type Preference Pass 714
SKU Preference Pass 714
small SKU pass for quantity of SKU
714
Warning messages
capacity violation 726
disabled bay used 726
no capacity defined 726
no mix violations 726
responses 737
Stack rule violation 726
Wave Properties
change 1260
Week Summary report 1046
Weekly Summary 513
menu option 1187
Weight Restriction
setting 53
Where function
defining 1296, 1297
Window column
Delivery Windows 1267
Routes Window 1268
Window columns
All Deliveries window 1270
Cost Analyzer window 1274
Import Orders window 1281
Windows
list 1132
maintenance 1134
managing 7
maps 1146
types 7
Wireless communication 860
disabling 866
explained 860
using the Message Center 864
Wireless Devices
menu option 1180
Wireless devices 227
acknowleding event receipts in the
Dispatcher 863
adding 227
assigning to equipment 135
assigning to routes 768
cloning 227
creating driver alerts 217
definition 227
enabling the device 227
events 860
setting the Java-enabled phone options
103
setting the options for diagnostic
information 84
setting the SmartPhone options 97
viewing diagnostic information 803
viewing event receipts in the
Dispatcher 863
Wireless Events
menu option 1195
setting the handheld options 108
Wireless events
cancel stop 861
defined 860, 1296, 1297
Operations Guide
1379
Index
delivery detail 861

drop and hook 861
GPS 861
redeliver 861
route complete 861
route start 861
stop complete 861
stop sequence 861
text message 861
viewing all events 861
viewing for a route 807, 860
Working Time Directives
defined 1296, 1297
Working time directives
setting 71
Working with
a daily route in the Routing Editor 488
a standard route in the Routing Editor
474
a stop in the Dispatcher 754
an order in the Dispatcher 754
batch imports 378
breaks on a daily route in the Routing
Editor 554
breaks on a route in the Planning
Editor 655
daily routes 488
Depot Planner 688
loads in MobileCast 887, 895
maps in the Dispatcher 759
maps in the Routing Editor 445
merchandisers 582
mid-route depots in the Routing Editor
556
position history in the Dispatcher 784
reports 927
route exceptions in the Dispatcher 797
route reloads 520
routing sessions 577
rush hour models 266
standard routes 474
territories 604, 610

the Assign Days Options Notebook
630
the Dispatcher 753
the Equipment Map 782
the GPS Playback Player 787
the Import module 347
the Load Trucks Options window 708
the Loading Editor 693
the Make Territories Options
Notebook 611
the Message Center 864
the Mobile Options notebook in the
the Options notebook in the
the Options notebook in the Planning
Editor 590
the Options notebook in the Routing
Editor 458
the Routing Pass Options Notebook
490
unassigned orders in the Routing
Editor 522
unassigning stops on a route in the
Routing Editor 530
waits on a daily route in the Routing
Editor 554
waits on a route in the Planning Editor
655
windows in the Dispatcher 754
windows in the Loading Editor 727
Working with Day Commander 1256
Working with the Cost Analyzer 1272
X
XY routing method
defining 1296, 1297
setting the default 55, 62, 79, 206
Z
Zones 189
adding 189
1380

Index

defining 1296, 1297
deleting 189, 192
editing 48, 189
explaining 189
Zoom Out icon 1157
Zoom to City 1162
Zooming out the map 1159
Zooming the map in on an area 1159
Zooming to a city 1162
Zooming to a city on the map 1162
Operations Guide
1381
Index
1382


RTS350OperationsGuide 85

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

RTS350OperationsGuide 85

Caricato da

Copyright:

Formati disponibili

version 3.

Working with Planned Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Roadnet Transportation Suite

Working with Location Substitutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2011 Roadnet Technologies, Inc. All rights reserved.

Roadnet Transportation Suite

Skill Set Available Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Assigning Sequential Route IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Territory Planner - Planning Editor

Roadnet Transportation Suite

Saving the Territories and Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2011 Roadnet Technologies, Inc. All rights reserved.

Deleting Pre-Built Loading Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Roadnet Transportation Suite

Inserting a Mid-Route Depot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Roadnet Transportation Suite

MobileCast Driver Performance Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 962

Roadnet Transportation Suite

Global Itinerary Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2011 Roadnet Technologies, Inc. All rights reserved.

Territory Stop List Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Roadnet Transportation Suite

Glossary and Index

Roadnet Transportation Suite

Getting Started with the Roadnet Transportation Suite

Getting Started with the Roadnet Transportation Suite

Roadnet, part of the Roadnet Transportation Suite, is a comprehensive routing program

Getting Started with the Roadnet Transportation Suite

Roadnet Transportation Suite

Getting Started with the Roadnet Transportation Suite

MobileCast, part of the Roadnet Transportation Suite, is a comprehensive routing

Getting Started with the Roadnet Transportation Suite

Roadnet Transportation Suite

About this Manual

About this Manual

Introducing the Roadnet Transportation Suitedescribes basic program operations

Maintaining the Roadnet Transportation Suitea section of detailed steps for

Creating Routes in the Routing Editorextensive instructions for performing the

Creating Routes in the Planning Editorextensive instructions for performing the

Dispatching in MobileCastextensive instructions for performing day-to-day

In addition, an index is included to help you locate information in the manual.

All references to keyboard keys are bracketed; for example:

All references to buttons on the screen are bracketed; for example:

Click on the [OK] button when all information is complete.

Roadnet Transportation Suite

Navigating through the Roadnet Transportation Suite

Navigating through the Roadnet Transportation Suite

Navigating through the Roadnet Transportation Suite

Choose Window Close All

Roadnet Transportation Suite

Starting the Roadnet Transportation Suite

Starting the Roadnet Transportation Suite

The database field may or may not

Starting the Roadnet Transportation Suite

Roadnet Transportation Suite

Roadnet Transportation Suite Modules

Roadnet Transportation Suite Modules

Roadnet Transportation Suite Modules

Roadnet Transportation Suite

Setting Up the Administration Module

Setting the Administration Options

Setting the Administration Options

If Allow adding new RIC user at