version 3 - Encompass Technologiessupport.encompass8.com/Users/Support/Ads/RoadNet_RTS32... ·...

Preparing for the

version 3.20A step-by-step guide to prepare for the Roadnet Transportation Suite.

Roadnet, RouteNet, Territory Planner, FleetLoader, and MobileCast are registered trademarks of United Parcel Service of America, Inc.

United Parcel Service of America, Inc. assumes no liability for any real or consequential damages related to the use or misuse of Roadnet Transportation Suite software or documentation.

© Copyright 2006 by United Parcel Service of America, Inc. UPS Logistics Technologies, Inc. 849 Fairmount Avenue, Suite 400, Baltimore, MD 21286. All rights reserved.

This manual is the property of United Parcel Service of America, Inc. It may not be reproduced by any method, in whole or in part, without written permission of the publisher.

Computer Program Code and Screen Displays © Copyright 1988, 2001 by United Parcel Service of America, Inc. All Rights Reserved. Unpublished work under U.S. Copyright Laws. The contents of this material are confidential and proprietary to United Parcel Service of America, Inc. Unauthorized use, disclosure, or reproduction is strictly prohibited. Rights to use are governed and limited by a license agreement.

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 ContentsOverview of the Roadnet Transportation Suite® ......................................................................... 1

Introducing the Roadnet Transportation Suite.............................................................................. 5Where are the stops? ....................................................................................................... 5Sending Customer Files to UPS Logistics Technologies ............................................... 6GPS Devices ................................................................................................................... 6How long does it take to travel from one location to another? ...................................... 6How long does the driver spend at the location? ............................................................ 7When will the deliveries be made? ................................................................................. 9How often does a location receive a delivery? ............................................................. 10What does it cost to run the route? ............................................................................... 11How is the information organized? .............................................................................. 11How are the deliveries routed in Roadnet? ................................................................... 12How are routes created in Territory Planner? ............................................................... 13How are the trucks loaded in FleetLoader? .................................................................. 14How are routes tracked in MobileCast? ....................................................................... 18

Completing the Territory Planner Information Survey............................................................... 20

Completing the FleetLoader Information Survey ....................................................................... 24Loading Information ..................................................................................................... 25Bay Information ............................................................................................................ 28Pallet Information ......................................................................................................... 28Warehouse Information ................................................................................................ 29

Completing the MobileCast Information Survey........................................................................ 30Routing Information ..................................................................................................... 31Network Information .................................................................................................... 32Database Information ................................................................................................... 32CE Wireless Information .............................................................................................. 33Java-Enabled Phone Information ................................................................................. 34Misc. Information ......................................................................................................... 35

Configuring your Network for the Java-Enabled Phone............................................................. 37Roles and Responsibilities for Java-enabled Phone Customers ................................... 38Java-Enabled Configuration Setup ............................................................................... 39

Generating the Location File ...................................................................................................... 42Mandatory Fields for Location Information ................................................................. 43Additional Fields .......................................................................................................... 44Location File Record Layout ........................................................................................ 49Service Time Type Information ................................................................................... 52Time Window Type Information .................................................................................. 53Checklist: Creating Location Files ............................................................................... 54

Generating the Location Extension File ..................................................................................... 55

Roadnet Transportation Suite Preparations Guide i

© Copyright 2006 United Parcel Service of America, Inc. All rights reserved.

Table of Contents

Fields for Location Extension Information .................................................................. 57Location Extension File Record Layout ....................................................................... 60Delivery Information .................................................................................................... 62Service Pattern Set Information .................................................................................... 64Service Pattern Information .......................................................................................... 65Checklist: Creating Location Extension Files .............................................................. 66

Generating the SKU File............................................................................................................. 67SKU File Required Fields ............................................................................................ 69SKU File Optional Fields ............................................................................................. 70SKU Information .......................................................................................................... 71Checklist: Creating SKU Files ..................................................................................... 73

Generating the Standard Route File............................................................................................ 74Mandatory Fields for Standard Route Information ...................................................... 75Additional Fields for Standard Route Information ....................................................... 75Standard Route File Record Layout ............................................................................. 77Checklist: Creating Standard Route Files ..................................................................... 78

Developing a File Creation Program for Daily Orders............................................................... 79Daily Orders Record Layout ........................................................................................ 85

Developing a File Creation Program for Locations.................................................................... 87Location File Record Layout ........................................................................................ 93

Developing a File Creation Program for Location Extensions................................................... 96Location Extension File Record Layout ..................................................................... 101

Developing a File Creation Program for Routed Solutions ...................................................... 103Routed Solution Record Layout ................................................................................. 109

Developing a File Creation Program for Employees................................................................ 112Employee Table Layout Form .................................................................................... 114

Developing a File Creation Program for Drivers...................................................................... 115Driver Table Layout Form .......................................................................................... 118

Developing a File Creation Program for Equipment Types ..................................................... 120Equipment Type Table Layout Form ......................................................................... 122

Developing a File Creation Program for Equipment ................................................................ 124Equipment Table Layout Form .................................................................................. 126

Developing a File Creation Program for Containers ................................................................ 127Container Table Layout Form .................................................................................... 128

Developing a File Creation Program for SKUs ........................................................................ 129SKU Record Layout Form .......................................................................................... 132

Developing a File Creation Program for SKU Brands ............................................................. 133
Roadnet Transportation Suite Preparations Guide ii

Table of Contents

SKU Brand Record Layout Form ............................................................................... 134

Developing a File Creation Program for Package Types.......................................................... 135Package Type Record Layout Form ........................................................................... 136

Developing a File Creation Program for Skill Sets .................................................................. 137Skill Set Table Layout Form ...................................................................................... 138

Developing a File Creation Program for Skill Set Activities ................................................... 139Skill Set Activity Table Layout Form ........................................................................ 140

Developing a File Creation Program for Activities .................................................................. 141Activity Table Layout Form ....................................................................................... 142

Importing the Daily Routes for MobileCast ............................................................................. 143Route Table ................................................................................................................ 146Stop Table ................................................................................................................... 150Product Order Table ................................................................................................... 153Order Financial Details Table .................................................................................... 155Line Item Table .......................................................................................................... 157Route Driver Table ..................................................................................................... 159Order Container Assignments Table .......................................................................... 161Line Item Container Assignments Table .................................................................... 163Route Equipment Table .............................................................................................. 165

Installing and Testing the Communications Package and Programs........................................ 167

Using the Batch Import Process................................................................................................ 168

Export Routes File Available Fields ......................................................................................... 173

User Upload File Available Fields............................................................................................ 176

Completing Data Preparation Forms ........................................................................................ 178ADP Data .................................................................................................................... 179Establishing Units of Measure and Equipment Capacities ......................................... 180Equipment Type Costs ............................................................................................... 181Bay Type Information ................................................................................................ 182Employee Type Information ....................................................................................... 184Mix Rules ................................................................................................................... 186Stack Rules ................................................................................................................. 192Account Type Information ......................................................................................... 193Track Type Information ............................................................................................. 195Area Information ........................................................................................................ 197Zone Information ........................................................................................................ 199Scenario Information .................................................................................................. 201Warehouse Zones ....................................................................................................... 203Checklist: Completing Data Preparation Forms ......................................................... 205

Roadnet Transportation Suite Preparations Guide iii


Table of Contents

Glossary .................................................................................................................................... 206

Roadnet Transportation Suite Preparations Guide iv


Overview of the Roadnet Transportation Suite®

Overview of the Roadnet Transportation Suite®Product: Roadnet, Territory Planner, FleetLoader, MobileCast

The Roadnet Transportation Suite is a powerful collection of software programs that allow you to create strategic and daily routes, track drivers as they run their routes, and even determine the best way to load your truck. All parts of the suite share the same database, so you can easily transfer information between the various parts of the suite. The four parts of the suite are:

Territory Planner—helps you develop long-term or strategic routes

Roadnet—helps you develop daily routes

FleetLoader—helps you determine the best way to load product on your delivery vehicles

MobileCast—helps you track drivers throughout their routes.

The Roadnet Transportation Suite takes the information you provide about your equipment, drivers, and delivery locations, and uses it to assist you in determining the most cost- and time-efficient way to meet your customers’ needs. By assessing the specifics of your operation, the Roadnet Transportation Suite will reduce your transportation costs, improve customer service, improve driver performance, and save routing time.

Territory Planner’s clever algorithms consider the amount of product each customer location receives, how often you want to go there based on the quantity, as well as when the customer wants you to be there and how long you need to be there, to create strategic routes. You can use these strategic routes to make your deliveries, or as the basis for your standard routes in Roadnet.

When creating your daily routes, Roadnet’s intelligent algorithms will consider a multitude of factors that you choose, including available drivers and equipment, driver rate of pay, equipment capacity, preferred and maximum route duration, multiple depots, rush hour, fixed and variable service times, traffic patterns and speed limits, road construction, DOT requirements, delivery location, customer open/close times and multiple time windows, order size, delivery instructions, and use of merchandisers.

Once your routes have been created, FleetLoader’s algorithms will determine the best way to load product on your vehicles, based on parameters you specify. You can have the delivery vehicles loaded so that it is easier on the warehouse personnel loading the trucks, or on the driver making the deliveries, or a combination of the two. FleetLoader will even consider rules you have against loading competing brands in the same bay.

MobileCast is a dispatch and tracking system that allows you to monitor data for several regions or divisions simultaneously. For each region you can work with each day’s routes, tracking the progress of the route and adjusting times and costs for any unforeseen circumstances that may arise. For each route, stops can be modified or completed, and costs tracked. In addition, you can track and run your billing and payroll directly from MobileCast.

For the Roadnet Transportation Suite to perform most effectively, the system will require you to enter certain information. Some of the information can be imported into the system

Roadnet Transportation Suite Preparations Guide 1

© Copyright 2006 United Parcel Service of America, Inc.All rights reserved.


from files obtained from a host computer; other information will need to be entered manually. The process of gathering information and entering it into the Roadnet Transportation Suite involves multiple steps that may span several weeks and involve one or more departments within your organization. This manual, in conjunction with the UPS Logistics Technologies consultant, is intended to help guide you through the process.

Use the tables below to determine which portions of this manual are essential to your organization when gathering information.

Roadnet Territory Planner

Introducing the Roadnet Transportation Suite Introducing the Roadnet Transportation Suite

Generating the Location File Completing the Territory Planner Information Survey

Generating the Standard Route File Generating the Location File

Developing a File Creation Program for Daily Orders

Generating the Location Extension File

Developing a File Creation Program for Locations


Developing a File Creation Program for Employees

Developing a File Creation Program for Location Extensions

Developing a File Creation Program for Drivers


Developing a File Creation Program for Equipment Types


Developing a File Creation Program for Equipment


Developing a File Creation Program for SKU Brands


Developing a File Creation Program for SKUs

Installing and Testing the Communications Package and Programs

Developing a File Creation Program for Activities

Using the Batch Import Process

Developing a File Creation Program for Skill Sets

User Upload File Available Fields

Developing a File Creation Program for Skill Set Activities

Completing Data Preparation Forms

Developing a File Creation Program for Package Types






Export Routes File Available Fields


Roadnet Territory Planner

FleetLoader MobileCast

Introducing the Roadnet Transportation Suite Introducing the Roadnet Transportation Suite

Completing the FleetLoader Information Survey

Completing the MobileCast Information Survey

Generating the SKU File Configuring your Network for the WAP-Enabled Phone


Configuring your Network for the Java-Enabled Phone

Developing a File Creation Program for Routed Solutions

Roles and Responsibilities for Remote Domicile Customers


Generating the Location File







Developing a File Creation Program for SKUs Developing a File Creation Program for Equipment Types




Developing a File Creation Program for Containers

Using the Batch Import Process Developing a File Creation Program for Activities

Completing Data Preparation Forms Developing a File Creation Program for Skill Sets




Note: If you are have not purchased the entire product suite, you may want to consider creating the interfaces for all products at once, rather than having to create new interfaces at a future time. For instance, if you only purchased Roadnet, you may want to create the addition interfaces for Territory Planner (location extensions and user upload) so they will be available should you ever purchase Territory Planner.


Importing the Daily Routes




FleetLoader MobileCast



Introducing the Roadnet Transportation Suite

Introducing the Roadnet Transportation SuiteThis section explains how the Roadnet Transportation Suite uses all of the information entered into the system to produce cost-efficient, customer-friendly routes and load your trucks. This section also discusses several concepts that are vital to understanding how the Roadnet Transportation Suite works. Some of these concepts are specific to only one portion of the suite, while others are used by multiple portions of the suite.

Where are the stops?

The first step in the routing process is finding the locations, also known as geocoding. Geocoding is simply the process of assigning a latitude and longitude to a location. The Roadnet Transportation Suite uses the latitude and longitude of a location to determine its exact geographic position for routing precision. Geocoding can be accomplished in several ways: using a Global Positioning System (GPS) device, Roadnet Transportation Suite Geocoding, and sending files to UPS Logistics Technologies for geocoding.

Roadnet Transportation Suite Geocoding

The Roadnet Transportation Suite geocodes a location by matching its address with an address range or a previously geocoded address contained in the database. You can also manually geocode a location by displaying a map of your delivery area and clicking to place your new location or modify the position of an existing location.

The Roadnet Transportation Suite geocoding process is outlined below.

1. Enter a new customer location in the Maintenance module.

2. Roadnet Transportation Suite creates a new address record.

3. Roadnet Transportation Suite geocodes the location by assigning it an exact latitude and longitude using one of the following methods:

• Street Reference Database (RouteNet)

Street Reference Database geocodes locations most precisely by finding their exact positions on the map.

• Zip+4 Centroid

Zip+4 Centroid locates the geographic center point of each zip+4 area that will match any addresses that have zip+4 information. These locations will not be geocoded to an exact address; however, the zip+4 centroid places the location more precisely than simply using the zip or postal code.

• Zip Centroid Geocoding

Zip Geocoding pinpoints a location according to the central point of its zip code area. All new locations entered into the Roadnet Transportation Suite system are automatically Zip Geocoded, but these are considered temporary until the latitude and longitude points can be geocoded using another method.




Sending Customer Files to UPS Logistics Technologies

You can choose to send your customer files to UPS Logistics Technologies, where the locations can then be geocoded. For optimal accuracy, it is important that you send in as much information as possible regarding each location’s address. See Generating the Location File for more information.

GPS Devices

GPS devices use radio signals received from satellites in order to pinpoint a location. You can then enter this information directly into your host computer and import it into the Roadnet Transportation Suite, or you can enter it directly into the Roadnet Transportation Suite.

How long does it take to travel from one location to another?

Once the locations are geocoded, Roadnet Transportation Suite knows their exact position. The next step is to determine the distance and time needed to travel between locations. There are three methods Roadnet Transportation Suite can use to determine this information—the XY method, RouteNet and the SuperMatrix. Only one method can be used at a time, as decided by the user.

XY Method

XY is a 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. The distance model includes distance factors that compensate for the fact that most roads do not follow a straight line. The travel time model calculates the speed traveled between two points based on the distance traveled.

Example If x = 3 miles and y = 2 miles, then Distance = 1.37 * √ (9 + 4) = 4.93 miles.




RouteNet

RouteNet is a routing method that uses maps to reflect the area being routed and to replicate the actual road conditions, accounting for everything from stop signs and traffic lights to speed limits and road changes. The maps are comprised of lines called segments, which represent the roads on which a driver will be traveling. Located along these segments are nodes, which represent the end of a particular road segment. A node may be marked in real life by a stop sign, intersection, or other road change. RouteNet gives you the versatility to update any road segment or node as necessary.

SuperMatrix

Like RouteNet, the SuperMatrix is a routing method that uses maps to reflect the area being routed and to replicate the actual road conditions, accounting for everything from stop signs and traffic lights to speed limits and road changes. The advantage to the user of the SuperMatrix over RouteNet is that you can schedule the SuperMatrix to be built overnight, so you do not have to wait for the matrices to build before entering the editor. The SuperMatrix is not available for MobileCast.

How long does the driver spend at the location?

Once the Roadnet Transportation Suite knows how long it takes to provide service to a location, it can add this time to the travel time to determine how many sites can be serviced within a reasonable period of time. The system uses four time categories—Fixed Service Time and Variable Service Time or Bulk Fixed Service Time and Bulk Variable Service Time—to determine how long it will take to service a location.

Location B

Location A

← Node

← Segment

RouteNet uses maps comprised of segments and nodes that precisely represent the actual roads on which the driver will be traveling. All road segments can easily be updated as necessary.




• Fixed Service Time is 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 Time is the amount of time it takes to move one unit of product from the truck into the location receiving the delivery. The size selected as the Unit of Service in the Maintenance Options is used to calculate the variable service time. You can also associate a variable service time with SKUs.

• Bulk Fixed Service Time is the 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 Time is the amount of time it takes to deliver one bulk item, such as a pallet, when making a bulk delivery. The size selected as the Unit of Bulk in the Maintenance Options is used to calculate the bulk variable service time.

Service Time Example

Unit of measure = pieces

At location A, the driver spends 13 minutes delivering 10 pieces. Five minutes of that time is spent servicing the location regardless of the number of pieces delivered; for example, getting in and out of the truck and taking care of paperwork.

Therefore, at Location A:

Fixed Service Time = 5 minutes

Variable Service Time = .8 (8 tenths of a minute)

.8 x 10 pieces = 8 minutes + 5 minutes = 13 minutes

Both fixed and variable service time can be entered for the driver alone, or the driver with a helper.

Guidelines for Determining Service TimesThe Roadnet Transportation Suite allows you to classify service times by types, which are usually grouped according to industry. Service time types also 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. For example, grocery stores, taverns, fast food restaurants, home deliveries, locations with docks, locations with pallet jacks, and locations with forklifts, etc. would comprise separate service time types, each having its own service times. Your UPS Logistics Technologies consultant will help you with the following steps to determine service times.

Step 1: Begin with general service times determined according to industry standards,




which can be provided by your UPS Logistics Technologies consultant.

Step 2: Determine different types of locations with similar characteristics that influence service time. For example, locations that have a loading dock or that use palletized loads.

Step 3: Conduct a driver’s survey for each service time type and analyze the data to establish a fixed and variable service time for each.

Step 4: Determine more accurate service times by any of the following:

• Manually adjusting service times for each location using actual data from the drivers’ manifests,

• Entering actual data from the drivers’ manifests into the system and allowing the system to determine service times for each location, or

• Extracting actual data from an onboard vehicle system.

When will the deliveries be made?

Once travel and service times have been determined, the Roadnet Transportation Suite’s routing process can consider numerous combinations of stops before arriving at a solution that takes into account a location’s time window(s). A time window is a specified period of time during which a location prefers to receive deliveries. Like service times, time windows are classified by types, which are usually grouped according to industry. Time windows can be changed for any individual location.

Each location can have two time windows and you can assign time window factors to each location based on priority, depending on how important it is that you meet the specified time windows. In addition, you can create time window overrides for any location(s) whose time windows or open/close times change or differ from the associated time window type.

You can adjust service times for any individual location or you can use types to adjust the service time for several locations simultaneously.




Note: The maximum time window factor of 5 should be used sparingly – only when it is absolutely essential that the time window(s) be met.

Once time windows have been established, an order may be delivered at any time between a location’s open/close times, depending on many elements including the time window factor and location priority. Open/close times are the earliest and latest possible times a location can accept a delivery. All time window types have open/close times associated with them.

Guidelines for Establishing Time Windows

1. Enter only those time windows that you are concerned about meeting.

Note: Check the locations with the time windows. If a location is isolated, it may be more difficult to make that time window than others.

2. Make time windows as wide as possible.

3. Assign time window factors to your locations accordingly, taking care not to make all time windows high priority.

Missed Arrival Times

Due to unforeseen circumstances, such as a traffic jam or a problem at another customer that holds up the driver, this planned delivery time may not be able to be met. MobileCast adjusts the arrival times as necessary during the route; these new arrival times are called the projected arrival times. Finally, the time the driver arrives at the stop is referred to as the actual arrival time. All three times, and the corresponding departure times, are tracked for each stop in MobileCast.

How often does a location receive a delivery?

Because Territory Planner is creating routes for more than one day, a location may receive more than one visit during the time you are creating routes for. To help determine how often a location should be visited, and which days those visits should be made on, Territory Planner uses service patterns and service pattern sets. A service pattern set contains a list of possible delivery days and frequencies, called service patterns. For instance, a service pattern may dictate that a location receive its entire delivery on Monday, while another service pattern specifies the location receives its entire delivery

Time window types help you to group your locations by a common trait, but that common trait refers strictly to the times a location is available and prefers to receive deliveries. Time window types allow you to specify that a group of locations has the same open/close times and time windows.




on Tuesday. Both these service patterns can be included in a single service pattern set, so Territory Planner could select the one that allows the best routes to be created.

Service pattern sets allow you to specify service patterns based on the total quantity the location receives during the cycle. For instance, you may be willing to make multiple deliveries per week to a customer who orders 500 items, but only want to deliver once a week at a customer who orders 50 items.

Service pattern sets are specific to the planning session, and can have different patterns for different scenarios.

What does it cost to run the route?

Cost information for routing is primarily derived from equipment and driver costs. Equipment costs are broken down into fixed equipment costs and per distance equipment costs. Fixed equipment costs are those costs that accrue independently of the distance driven, such as lease or purchase price, insurance, depreciation, license fees, and highway use tax; these costs run on a per day, per truck basis. Per distance equipment costs can be such things as fuel, repairs, and maintenance supplies; these costs run on a per mile or kilometer basis.

Driver costs can be entered in many forms, reflecting how the driver is paid, whether per hour, per stop, per piece delivered, or according to the distance driven. Helper costs are associated with driver costs.

How is the information organized?

In the Roadnet Transportation Suite, there are several levels in which the routing information is organized. The first level is by region – each region contains locations, equipment, employees, and other resources that are used to create routes. Often, a region equates to a depot or distribution center. So, you can have routing information for several distribution centers, or regions, in the same Roadnet Transportation Suite database, instead of needing separate databases for each center.

The next level of organization is the session. In Roadnet and FleetLoader a routing session typically contains the orders and routes for a single day, while in Territory Planner a planning session contains the service pattern sets, location extensions, and delivery

Fixed Equipment Costs Per Distance Equipment Costs

Lease or Purchase Price Fuel

Insurance Repairs

Equipment Deprecation Replacement Parts

License Fees Oil

Highway Use Tax Tires




information for a span of time known as a cycle. In either case, sessions allow you to try various “what-if” scenarios without ruining your original routes.

How are the deliveries routed in Roadnet?

There are two methods for routing deliveries: standard routing and dynamic routing. In addition, you can make modifications to the standard routing process by creating standard route overrides. Your consultant will help you determine the best routing solution for your company. Each method is described below.

Standard Routing

Standard routing allows you to create routes with specific locations in a fixed sequential order. If you are using standard routing, when orders are received for any of the stops on a standard route, those stops are included in the route for the day. While different stops will receive orders on different days, the sequence of the stops does not change; stops on the standard route that do not have orders are simply not added to that day’s route. The benefits of standard routes are that they are more customer service oriented and they offer the router more control in establishing route structure. The table below is an example displaying four standard routes; each number on the lists represents a location, and locations marked with an asterisk indicate stops that are receiving orders.

According to the example above, the following is true for this day:

• Route 1001 has five stops.

• Route 1002 has four stops.

• Route 1003 has one stop.

Route #1001 Route #1002 Route #1003 Route #1004

323804 718008 * 139927 424489

012247 * 848712 219982 100723 *

432984 238584 * 521984 * 719294

901937 * 032858 * 127451 249031 *

231701 358744 840234 187212 *

690023 711452 * 903881 *

298123 405002 371197 *

847777 * 647458 *

001968 * 234750

626300 *

109842




• Route 1004 has six stops.

Dynamic Routing

Dynamic routing takes the main routing problem and breaks it down into smaller and simpler parts. For example, if a routing problem consists of 1,500 delivery locations, Roadnet groups the locations geographically and according to the proximity of locations to one another. Once the geographical data has been considered, Roadnet then creates the routes based on parameters that you enter into the system. These parameters could include the following:

Equipment Capacities, Depot(s), Drivers, Restrictions, Resources, Strategies, Time Windows, Auto-Assign, Reloads, Extended Runs, Backtracking, Standard, Sequencing, Split Orders, Post Process, or Route ID

More information on the criteria listed above can be found in the Roadnet Transportation Suite help system, which will accompany your software.

Each time you enter a new set of criteria and run the routing algorithm, the system completes a pass. Each pass filters out those locations that do not meet the criteria you selected. Typically, Roadnet assigns routes starting at the furthest point from the depot and working back so that an empty truck returns to the depot. The system will continue to assign stops to routes until one of several conditions is met: the route meets or exceeds the runtime; the equipment is full to capacity; or no more stops meet the specifications to be added to the route.

Dynamic routes are cost-effective routes to run; however, they require steady maintenance in order to keep location, equipment, and driver information current.

Note: Standard and dynamic routing can easily and effectively be used in conjunction with each other. For instance, for a day’s orders you may choose to run standard routing first so that all stops on standard routes are routed accordingly; you can then run dynamic routing for the remaining orders.

Standard Route Overrides

Roadnet allows you to take any route you’ve built and make it a standard route override. For instance, if on a particular day you add a few stops to a standard route and you would like to continue using the new route you created, you can create a standard route override. This allows you to use a route very similar to the original standard route, but without losing the original route. Any time you route, you can choose whether or not you want to use the standard route overrides you’ve created.

How are routes created in Territory Planner?

Once you have entered all the delivery and cost information into Territory Planner, the locations can be grouped into territories and finally delivery routes. Territory Planner defines a territory as a geographic area; normally the number of territories matches the number of available pieces of equipment. You can specify the number of territories you




want created, or how much of a specific criteria each territory should contain. You can also select the criteria (quantity of product, number of stops, number of locations, etc.) you want to use to balance the territories.

The final step is the creation of valid routes. Territory Planner looks at each territory individually when creating routes, and uses the cost and delivery information to create cost-efficient routes. When determining how to place each location extension on a route, Territory Planner looks at the delivery quantity and the service pattern set, then selects a valid service pattern. Service time information is used to determine how long the driver will spend at each stop on the route, allowing time-balanced routes to be created. The service pattern sets are used to determine valid delivery frequencies and days for each location.

How much product does the location receive during a cycle?

A planning session in Territory Planner covers a span of time known as the cycle, or a number of cycle weeks. The cycle must be long enough for each location in the session to receive at least one visit. Therefore, the number of cycle weeks is determined by the location that receives the least frequent deliveries; other locations will most likely receive multiple deliveries during the cycle.

During a cycle a customer receives a specific amount of merchandise; this quantity is known as the cycle quantity. The cycle quantity can be defined in terms of up to three types of units of measure, such as bottles, cans, pounds, etc., known as size aliases. The quantity for each size alias must cover the entire cycle, and must be evenly divisible by the number of stops to the location. For instance, if a location receives 25 of an item at per visit, and it is visited twice in the cycle, then the cycle quantity would be 50.

How are the trucks loaded in FleetLoader?

If you are using FleetLoader to load your trucks, there is a whole different set of questions that need to be answered.

What equipment do you have?

The first step in setting up the FleetLoader system is to determine what kinds of delivery vehicles are in your fleet. FleetLoader needs to know three main things about your vehicles:

• Bay Type: what are the kinds of bays on each piece of equipment (full bays, 2/3 bays, etc.) or what are the pallet positions on each piece of equipment?

• Equipment Type: what kinds of equipment do you have (12-bay, 16-bay, side-loader, bulk, etc.)?

• Equipment: what are the specific pieces of equipment in your fleet?

When a bay type is created, you can define the actual dimensions of the bay (height, width, depth), define the pallet positions, and define what amount of each type of package will fit in that bay type. You can also limit the number of different SKUs allowed on a bay/pallet. Because bay types are used only for determining capacity, it is not necessary




to create different types for bays with the same capacity; several bays of one type may have slightly different dimensions.

Note: Bay type defaults 1-4 are reserved by FleetLoader and cannot be deleted, although the information can be changed.

When an equipment type is created, you can define the body type of the equipment type (side loader or bulk truck), as well as the physical layout of the equipment type (how many bays/pallets and axles, and whether the bays/pallets are full-size, 2/3, 1/2, etc.). Equipment types are used to tell the system what kind of equipment you will be loading, including the number of bays/pallets and the layout of the delivery vehicle.

When a piece of equipment is created, you can define what types of packages you would like in each bay of that equipment. You can also disable individual bays on specific pieces of equipment, or designate specific bays as “small SKU” bays (bays reserved for SKUs with a small quantity).




What products do you have?

Once you have defined what kinds of equipment you have, the next step is to determine what SKUs will be loaded. FleetLoader needs to know three main things about each SKU, from general to more specific:

• Package Type: what kind of package or container does the SKU come in (24 twelve-ounce cans, 6 two-liter bottles, etc.)?

• SKU Brand: what brands of product do you carry (Diet RN Cola, Light RN Beer, etc.)?

• SKU: what is the SKU or product ID of each product?

When a package type is created, you define the actual dimensions of the package (height, width, depth, weight) and how much of that product will fit on a pallet. You can also define how many units of that package type will fit in each bay type.

When a SKU brand is created, you can specify the brand ID and an optional description (Roadnet Cola). The SKU brands are critical in determining what products should not be loaded together in a particular bay; all SKUs must have a SKU brand associated with them.

When a SKU is created, you must specify the package type and brand ID associated with the SKU and provide a description. You may provide a bitmap, or picture, of the SKU to display in FleetLoader. If you provide a bitmap, the bitmap must be 28 x 28 pixels and less than 256 colors. Also, if you plan to produce pick lists from the system, you can

The Edit Package Type window is used to help the system determine how much product will fit on the equipment. Package types are also used to prevent stacking errors. Some examples of package types are barrels, bottles, and cans.




specify the primary and secondary pallet zone, layer zone, and hand zone in the warehouse for each SKU.

How do you keep loading errors from occurring?

You may want to tell the system that certain brands should not be loaded with other brands in a single bay. Likewise, you may want to prevent one package type from loading on top of another package type. To prevent these kinds of loading errors, FleetLoader has two sets of rules:

• Mix Rules: what SKU brands, package types, and warehouse zones do you have that should not be loaded in the same bay/pallet or pallet layer with other SKU brands, package types, or warehouse zones (example, two brands of soft drink with similar packaging)?

• Stack Rules: what package types should not be loaded on top of other package types (example, barrels on top of bottles)?

How is this information used to load your fleet?

FleetLoader looks at the daily order and routing information provided by Roadnet and determines the best initial loading solution for your fleet, based on the settings you have selected. You may choose to load your fleet driver-friendly (loading by stop), warehouse-friendly (loading like products together), or a hybrid of the two strategies. There are also several other parameters in the system to help you configure FleetLoader’s loading strategy.

SKUs tell you what product is loaded where on the equipment. You can also print out pick lists that will tell your warehouse staff where to find the SKU.




Once your trucks are loaded initially, you can use the Loading Editor to examine the solution and make any necessary changes. There are several tools in the editor to help you, including a Bay Contents View window that shows the contents of each bay by individual SKU, and a truck profile that shows the percent full for each bay at a glance.

How are routes tracked in MobileCast?

MobileCast uses wireless technology to monitor and track routes throughout the day. Using a wireless device, the driver and dispatcher are able to let each other know about changes that are made to a route. In addition, 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 play back the GPS entries to see where the driver and/or the equipment has been for that day. The path that the wireless data follows changes, depending on whether you are using a CE-wireless device, a WAP-enabled wireless device, or a Java-enabled wireless device. See the appropriate section for the wireless device you are using.

Java-Enabled Wireless Device

If you are using Java-enabled wireless devices, such as phones, to allow the dispatcher and driver to communicate, a possible path the wireless messages follow is described below. The path followed at your organization may be slightly different depending upon the security procedures your organization decides to enact. See Roles and Responsibilities for Java-enabled Phone Customers for more information.

When the dispatcher working on the MobileCast Office Client sends a message to the driver, the first step is that the message is transferred to the MobileCast database, where it is read by the MobileCast Java Phone Communicator. Then, the message is sent to the Internet, where it is transferred to the Java-enabled phone via your selected network provider.

WAP-Enabled Wireless Device

If you are using WAP-enabled wireless devices, such as phones, to allow the dispatcher and driver to communicate, a possible path the wireless messages follow is described below. The path followed at your organization may be slightly different depending upon the security procedures your organization decides to enact. See Roles and Responsibilities for WAP-enabled Phone Customers for more information.

When the dispatcher working on the MobileCast Office Client sends a message to the driver, the first step is that the message is transferred to the MobileCast database, where it is read by the MobileCast WAP Notification Service, which is running on the external web server. Then, the message is sent to the Internet, where it is transferred to the WAP-enabled device via your selected network provider’s WAP-Gateway software.

Information requested by the driver, via the phone, is provided by a set of Active Server Pages (ASP) located on your web server. These pages retrieve the necessary information from the MobileCast NetTracker Service, also running on your web server.




CE-Wireless Device

MobileCast allows the dispatcher to monitor up-to-the-minute information about the routes as they are being run. If wireless communication is being used, the driver can update the route information from the road, freeing the dispatcher to concentrate on problems that arise during the day. If changes to the route arise during the day, the dispatcher can send the driver messages to make changes, or the driver can change the route as situations arise on the road and forward the information to MobileCast.



Completing the Territory Planner Information Survey

Completing the Territory Planner Information SurveyProduct: Territory Planner

This section contains a survey that must be completed by future Territory Planner customers before you meet with the UPS Logistics Technologies’ consultant. The information contained in the survey will allow the consultant to help you set up your system.

1. Rank the following goals of a re-route, starting with 1 as the most important goal. Enter 0 or NA for items that are not important to your organization.

2. What is the delivery frequency for the customer?

Level of Importance Goal

___________________ Reduce miles

___________________ Reduce cost

___________________ Increase load on vehicles

___________________ Reduce overtime

___________________ Arrive at customer location during requested time frame

___________________ Reduce load on vehicle

___________________ Group routes by Account Type

___________________ Balance load on vehicles

___________________ Balance total route run time

___________________ Decrease delivery cost per unit

___________________ Other ____________________________

_____ Once a week

_____ Once every other week

_____ Once every fourth week

_____ Once every 12th week

_____ Other ____________________________




3. Which of the following determines the number of times the sales representative visits the customer: (choose all the apply)

4. Which of the following determines the number of times the delivery driver visits the customer: (choose all that apply)

5. How many additional miles are you willing to travel to satisfy a customer’s delivery time window?

6. What is the most important factor in determining the additional miles that will be traveled to satisfy a customer’s delivery time window?

7. What is the most important factor in determining the delivery time at the customer’s site?

8. Choose the unit that will be used to calculate the amount of delivery time required to service a customer site.

___ Average Volume ___ Customer Request ___ Account Type

___ Storage Space ___ Other

___ Average Volume ___ Customer Request ___ Account Type

___ Storage Space ___ Other

1 5 10 15 20 25 30 40 50 60 No limit

_____ Customer’s order volume

_____ Customer’s account type

_____ All delivery times windows must be satisfied regardless of mileage incurred

_____ Other _____________________________________________________

_____ Customer’s order volume

_____ Customer’s account type

_____ Other _____________________________________________________

___ Cases ___ Bottles ___ Pounds

___ Pieces ___ Packages ___ Cubic Feet of Product

___ Minutes ___ Dollars ___ Other_____________




9. Choose up to 3 units that will be used to determine when a vehicle is loaded to the ideal capacity. One of the units must match the unit chosen in question 8.

10. What percentage of the ideal capacity is acceptable on a daily basis?

11. Choose the ideal total run time for the daily routes, or the amount of time the driver spends between leaving the depot and returning to the depot.

12. What is the ideal number of stops for a daily route? __________________

13. Select the primary focus of the re-route:

14. Choose the statement that best describes the re-route you desire:

___ Cases ___ Bottles ___ Pounds

___ Pieces ___ Packages ___ Cubic Feet of Product

___ Minutes ___ Dollars ___ Other_____________

100% 95% 90% 85% 80% 75% 70% 65% 60% 55% 50%

___ 10 hours ___ 9 1/2 hours ___ 9 hours

___ 8 1/2 hours ___ 8 hours ___ 7 1/2 hours

___ 7 hours ___ 6 1/2 hours ___ Other____________

_____ The redesign of the sales representatives’ territories and call days.

_____ The redesign of the current standard delivery route structure.

_____ Both of the above are of equal importance.

_____ Other _____________________________________________________

_____ A radical change from the current sales and delivery structure.

_____ A moderate change from the current sales and delivery structure.

_____ A limited change from the current sales and delivery structure.




15. The UPS Logistics Technologies consultant should be away of the following goals:

16. The UPS Logistics Technologies consultant should be aware of the following special circumstances and situations:




Completing the FleetLoader Information SurveyProduct: FleetLoader

This section contains a survey that must be completed by future FleetLoader customers before you meet with the UPS Logistics Technologies’ consultant. The information contained in the survey will allow the consultant to help you set up your system.

If you load bay trucks/sideloaders, complete the following sections:

• Loading Information

• Bay Information

• Warehouse Information

If you load pallets/bulk trucks, complete the following sections:

• Loading Information

• Pallet Information

• Warehouse Information

If you load both bays and pallets, complete the entire survey.




Loading Information

1. How many trucks do you load on a daily basis?

2. Place a check next the statement that best describes your loading preferences.

3. How many package types, SKUs, and SKU brands do you load on a daily basis?

4. List and describe the different package types you have.

5. Do you have specific package types that can’t be mixed on a pallet layer?

• Yes • No

If yes, list and describe each package type.

_____ Load products according to stop, making it easier for the driver to pull products off the truck while delivering.

_____ Load the same SKUs together, making it easier for the loader to pull products from the warehouse and load the truck.

_____ Both of the above statements apply to my organization.

_____ Package types

_____ SKUs

_____ SKU brands




6. Do you have specific package types that can’t be mixed on a bay/pallet?

• Yes • No


7. Do you have specific warehouse areas/zones that can’t be mixed on a pallet layer?

• Yes • No

If yes, list and describe each warehouse area/zone.

8. Do you have specific warehouse areas/zones that can’t be mixed on a bay/pallet?

• Yes • No

If yes, list and describe each warehouse area/zone.




9. Do you have specific SKU Brands that can’t be mixed on a pallet layer?

• Yes • No

If yes, list and describe each SKU Brand.

10. Do you have specific SKU brands that can’t be mixed on bay/pallet?

• Yes • No

If yes, list and describe each SKU brand.

11. Do you have specific package types that can not stack on other package types when loaded?

• Yes • No





Bay Information

1. Do your trucks have different types of bays (based on bay capacity not bay size)?• Yes • No

If yes, list and describe each type of bay.

Pallet Information

1. Do you have different pallet sizes?• Yes • No

If yes, list and describe each pallet size.

2. Do you have different pallet building methods? (i.e. Do you use a 7-way method for every day occasions and an 8-way method for holidays?)

• Yes • No

If yes, list and describe each pallet building method.




3. When building a pallet, what is most important to you?

Warehouse Information

1. Is your warehouse organized by specific areas/zones? • Yes • No

If yes, list and describe each area/zone.

2. If you have specific warehouse areas/zones, do you load certain warehouse areas/zones before others when loading pallets/bays?

• Yes • No

If yes, describe this order.

_____ To load warehouse areas/zones together

_____ To load package types together

_____ To load SKUs together




Completing the MobileCast Information Survey Product: MobileCast

This section contains a survey that must be completed by future MobileCast customers prior to the initial meeting. The information contained in the survey will allow the consultant to be able to help you set up your system.

If you are using a handheld wireless device, complete the following sections:

• Routing Information

• Network Information

• Database Information

• Wireless Information

• Miscellaneous Information

If you are using a Java-enabled wireless device, complete the following sections:

• Routing Information

• Network Information

• Database Information

• Java-Enabled Phone Information

• Miscellaneous Information

If you are using all of the wireless options, be sure to complete all sections of the questionnaire.




Routing Information

1. Does your organization use Roadnet to plan routes?• Yes • No

If yes, how many computers is Roadnet running on?

If yes, what version of Roadnet do you use?

2. Specify what form of time and distance calculations you plan to use:

3. Do you have any long haul routes?

• Yes • No

If yes, how many do you normally run?

4. What is your average number of stops per route?

5. What is maximum number of stop per route?

6. Do you want to allow pickp orders to be created?

• Yes • No

7. Do you want to allow drop and hooks to be created?

• Yes • No

_____ 7.0

_____ 7.1

_____ Roadnet Transportation Suite v2.0

_____ Roadnet Transportation Suite v3.0

_____ Other ______________________

_____ Point to Point

_____ RouteNet




Network Information

1. What is the external IP address of the MobileCast wireless communication server? _______________________________________________

2. Please provide contact information for your network/IT administrator.

Note: The network administrator must be present during the MobileCast installation.

3. What is the speed of your Internet connection to the MobileCast communication server?

Database Information

1. Do you want Oracle or SQL Server installed by UPS Logistics Technologies or will you install Oracle/SQL yourself on an existing Oracle/SQL server?

Name _________________________________________________

Title _________________________________________________

Phone _________________________________________________

Email _________________________________________________

_____ UPS Logistics Technologies Oracle/SQL Server Installations

_____ Existing Oracle/SQL Server

(Indicate Current OS and Oracle/SQL version______________)




2. Please provide contact information for your database administrator.

Note: The database administrator must be present during the MobileCast installation.

3. What are your plans for backing up the Transportation Suite database?

CE Wireless Information

Complete this section only if you are using CE-wireless devices.

1. 1.) Do you want UPS Logistics Technologies to coordinate the installation of vehicle hardware, or will you be handling it yourself?

2. How frequently do you require the odometer reading to be taken?:

3. Do you require customers to sign when they accept deliveries?

4. Do you require the person accepting the delivery be entered as the consignee?

Name _________________________________________________

Title _________________________________________________

Phone _________________________________________________

Email _________________________________________________

_____ UPS Logistics Technologies coordinates vehicle installation

_____ We will coordinate vehicle installation

_____ Never

_____ At each stop

_____ At the start and end of the route




5. If you are using barcode scanning, what barcode symbology is used?

Java-Enabled Phone Information

Complete this section only if you are using a Java-enabled wireless device.

1. What Internet service provider (ISP) are you using?

2. What type of connection are you using?

3. What is the connection speed?

4. Please complete the following information for the computer that will be used as the Java-enable phone server:

5. Please complete the following information for the computer that will serve as the MobileCast server:

6. Who is your local network contact?

Is this person responsible for maintaining your Internet connection?

7. Please provide information about the firewall hardware and software you are using.

Machine Name _____________________________________________

Machine Type (chip and speed) _____________________________________________

IP Address _____________________________________________

Operating System _____________________________________________

Machine Name _____________________________________________

Machine Type (chip and speed) _____________________________________________

IP Address _____________________________________________

Operating System _____________________________________________




8. Does the firewall support SQL*Net Traffic with dynamic port assignment?

Misc. Information

1. Indicate how many MobileCast clients will run the following operating systems:

2. Do you want to integrate/interface MobileCast to any of your other business systems?

• Yes • No

If yes, specify other systems

3. Where should the wireless devices and other hardware be shipped to?

4. When does your organization plan to be ready for the implementation visit?

5. Enter the make, model, and the number of each vehicle you have.

_____ Windows 2000

_____ Windows XP

_____ Other ________________

Name ________________________________________________

Title ________________________________________________

Address ________________________________________________

________________________________________________

Make Model #







Configuring your Network for the Java-Enabled PhoneProduct: MobileCast

If you are using MobileCast with the Java-enabled phones, you will need to configure your network to allow messages received from the phones to be processed by MobileCast, as well as for messages to be sent from MobileCast to the phone. This section shows some possible ways the system can be configured, as well as outlining the responsibilities of UPS Logistics Technologies and your organization.




Roles and Responsibilities for Java-enabled Phone CustomersIf you are using the Java-enabled phone option to allow your drivers and dispatchers to communicate, there are several hardware and software pieces that need to be setup and configured. Some of these pieces are the responsibility of UPS Logistics Technologies, while others are your organization’s responsibility. The responsibilities of each group are outlined below.

What UPS Logistics Technologies will provide:

UPS Logistics Technologies will provide a set of software components used to supply mobile client functionality to Java-enabled clients. These components will be installed and configured by UPSLT personnel. UPS Logistics Technologies will provide all future fixes and enhancements to this software.

UPS Logistics Technologies will provide technical information for the interaction between these components. This information is meant to give your organization the knowledge necessary to make the proper decisions regarding security and access to your network.

What your organization will provide:

Your organization is responsible for the installation and configuration of any firewall hardware or software. This includes the installation or configuration of any packet filtering or proxy type hardware or software, as well as deciding what vendors to use in providing the functionality.

Your organization is also responsible for the installation and configuration of any firewall hardware or software. This includes the installation or configuration of any packet filtering or proxy type hardware or software, as well as deciding what vendors to use in providing the functionality.

Periodically, Microsoft publishes patches for its operating system software. Your organization is responsible for monitoring for these updates and patches and installing those you deem necessary.




Java-Enabled Configuration Setup The diagram below shows the communication links between the different portions of the MobileCast setup when you are using the Java-enabled phone.

Customer Network Configurations for a Java-Enabled Setup

When architecting the communication between MobileCast and the Java-enabled mobile clients, you want to isolate communication between the customer’s internal network and the Internet to as few known points of entry as possible. By limiting the number of entry points and protocols used at these points, you can more precisely configure whatever security mechanisms (packet filtering, firewall software/hardware), etc. you have chosen.

If possible you should limit traffic to:

• TCP traffic: The Mobile Clients (phones) communicate with the MobileCast Java-enabled Phone Communications Adapter via TCP/IP on a user-defined fixed port.




As is typical of many company networks, traffic enters a segregated portion of the network, known as the demilitarized zone (DMZ). The DMZ further isolates communication with the Internet.

Traffic necessary to provide the data to these “external” services is limited to one protocol between two designated machines. The protocol is Oracle SQL*Net. This protocol must be allowed between the External Server and the MobileCast database. However, there is still some flexibility in the manner is which this communication is provided.

UPS Logistics Technologies suggests using a SQL *Net aware proxy server, which has the advantage of more precisely and intelligently limiting traffic between the internal and external networks. Several major firewall companies now offer this type of proxy support, including: Network Associates’ Gauntlet, CheckPoint Software’s FireWall-1, Milkway’s SecurIT, etc. Note that the proxy-away software is not a necessity. Some firewall software can be configured to allow Net8 traffic without the use of proxy software.

The table below lists some typical configuration rules to consider when establishing the firewall.

Direction Source Destination Protocol Port Notes

In Java Phone

Java- Phone Server

TCP 22011* Traffic to and from phones.

*Note: Upon a customer’s request, UPS Logistics Technologies will change the Port location.

Out Java Phone Server

Java-enabled Phone

TCP Any available

All outbound TCP ports need to be opened.

In/Out Java Phone Server

MobileCast/Oracle Server

TCP (SQL*Net)

Multiple* Oracle SQL*Net database traffic between Web Server and Oracle Server.

This is only required if the Java phone server is in the DMZ.

*Note: The traffic normally starts at port 1521, but is then dynamically reallocated during processing. This rule can be handled using a firewall that supports the SQL*Net protocol.







Generating the Location FileProduct: Roadnet, Territory Planner, MobileCast

In order to accurately track the routes and modify delivery times and travel distances when changes need to be made, the Roadnet Transportation Suite needs to know where the delivery locations are. A geocode, or the latitude and longitude of the location, is used to place the delivery location. If you are using another software package requiring latitudes and longitudes, your delivery locations may already be geocoded; if not the locations will need to be geocoded.

There are three ways a location can be geocoded. The first method is to send a file to UPS Logistics Technologies to have the locations geocoded. If you are sending a file to UPS Logistics Technologies, follow the instructions in this section. The second method is to use a GPS device and import or manually enter the geocodes into the system. A third method is to use a geocoding software package to generate the geocodes.

Note: Locations include depots as well as delivery locations, so all depot information must be entered.

Step 1: Verify that each location has a unique ID. The ID must be between 1 and 15 characters in length.

Step 2: Verify that the address for the location is a street address, not a PO box number or other mailing address. Verify that the zip code is valid. A street number is required for each delivery location.

Step 3: Verify that a phone number, including the area code, is included for each location in the file.

Step 4: Create a fixed-record-length ASCII data file of the location information. The location ID, location name, location address, city, state, and zip code must be included in the file.




Mandatory Fields for Location InformationIn order to geocode your locations properly, the information listed below must be entered for each location. Incomplete or incorrect information in any of these fields may cause an incorrect geocode.

*All fields are string (text) fields unless the data calls for a specific format (such as date, time, latitude, or longitude).Some other tips to remember when creating this file: • Create an individual record for each location, and place all information in that record.

Each record should occupy a separate line. • The columns for each piece of information (ID, street name, etc.) must be the same

length in each record. Left justify information in the column, leaving blank spaces after the entry if necessary; right justify numeric information in the column, leaving blank spaces prior to the entry if necessary.

• Do not place commas or other forms of punctuation between the columns.• Do not provide extraneous information (such as routing information) in this file.Step 5: After the file has been created, complete the Location File Record Layout,

indicating the starting position and length of each column.Step 6: Send the completed file and Location File Record Layout form to UPS

Logistics Technologies for geocoding. The file can be sent using any of the following methods:• Modem• 100 MB Zip disks• CD ROM• 3.5” high density disks• e-mail (zip the file and send as an attachment to [email protected];

3 MB limit)

Field* Max. Length Description

Location ID 15 characters Unique identifier for location.

Location Name 60 characters Name of the location (use name of the business — such as Simon’s Streudelhaus — not owner’s name or other).

Address Line 1 50 characters Complete street address, such as 123 E Main Street. No PO Box or RR #.

City 30 characters City.

State 20 characters State or Province.

Zip Code 10 characters Zip (or Zip+4) or Postal Code.

Phone Number 20 characters Area code and phone number (do not include dashes or parentheses).




Additional Fields Along with the mandatory location information, you can send additional location, route, and stop information to UPS Logistics Technologies. UPS Logistics Technologies will include that information in your location file.


Location Type 3 characters Location type ID (must exist in Location Type table), such as SIT.**

Address Line 2 20 characters Address line 2 (Suite #, P.O. #).

Cross Street 30 characters Cross street (closest intersecting street), such as Elm Avenue.

County 30 characters County.

Country 2 characters The two-character ISO code for the country, such as US for United States and IT for Italy. If not specified, uses the country specified in the Maintenance Options notebook.

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

Store Number 15 characters The store’s individual number if part of a chain, such as #10 for Giant #10.

Delivery Days 7 characters Location’s usual days for delivery (MTWRFSU, no spaces).

Account Type 5 characters Account type ID (must exist in Account Type table).**

Service Time Type ID 5 characters Service time type ID (must exist in Service Time Type table).**

Time Window Type ID 5 characters Time window type ID (must exist in Time Window Type table).**

User Field1, 2, 3 20 characters each

User-defined field.

Zone ID 15 characters Zone ID (must exist in Zone table).**

Latitude 11 digits In acceptable format that you specify (see Longitude).




Longitude 12 digits 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 characters 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 characters in length. 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 characters in length. For instance, a latitude of 0.032245 should be imported as 0032245, while a latitude of 51.122234 should be imported as 51122234.Decimal degrees—there 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 seconds—the latitude/ longitude must be formatted so that the minutes and whole portion of the seconds are two characters 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 minutes—the latitude/longitude must be formatted so that the whole number portion of the minutes is two characters. 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. Include negative.

Priority 1 digit Priority rating from 0 to 9 (lowest to highest) for stop; locations with a priority are placed first on a route in dynamic routing. This is only used with Roadnet.

Fixed Fee 9 digits The fee for servicing (delivering, reloading, or emptying) the location.

Variable Fee 9 digits The variable fee is based on cost per unit delivered. 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.

Minimum Bulk Quantity 1, 2, 3

9 digits each Minimum bulk quantity for size 1, 2, 3 value (if location’s order exceeds this size 1 value, the order is delivered as bulk).

Override Days 7 characters Days to apply time window and/or service time overrides (MTWRFSU, no spaces).





Open Time Time Location open time override (military time, such as 09:00, 13:00).**^

Close Time Time Location close time override (military time, such as 09:00, 13:00).**^

Time Window 1 Start Time Time window 1 start time override (military time, such as 09:00, 13:00).**^To delete an existing time window, enter –1.

Time Window 1 Stop Time Time window 1 end time override (military time, such as 09:00, 13:00).**^To delete an existing time window, enter –1.



Helper Fixed Service Time

9 digits Fixed service time with helper (in tenths of minutes). **

Helper Variable Service Time

11 digits Variable service time with helper (must be in acceptable format that you specify: 10 minute units to 0.000001 minute units). **

No Helper Fixed Time 9 digits Fixed service time with no helper (in tenths of minutes). **

No Helper Variable Time

11 digits Variable service time with no helper (must be in acceptable format that you specify). **

Bulk Helper Fixed Service Time

9 digits Bulk fixed service time with helper (in tenths of minutes). **

Bulk Helper Variable Service Time

11 digits Bulk variable service time with helper (must be in acceptable format that you specify: 10 minute units to 0.000001 minute units). **

Bulk No Helper Fixed Time

9 digits Bulk fixed service time with no helper (in tenths of minutes). **

Bulk No Helper Variable Time

11 digits Bulk variable service time with no helper (must be in acceptable format that you specify). **

Employee ID 9 characters The employee associated with the location.

Standard Instructions 255 characters Location-specific delivery instructions.

Contact 255 characters The name of the contact person for the location.

Alternate Contact 255 characters The name of the alternate contact person for the location.





Service Failure Notify Flag

1 character 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 Minutes

4 digits The number of minutes the stop should be delayed before a service failure notification is created. This information is only used with MobileCast.

Service Failure Notify Type

3 characters 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.

Service Failure Contact

64 characters The e-mail address of the location. This is only necessary if the Service Failure Notify Type is e-mail. This information is only used with MobileCast.

Delete Location 1 character If Y, 1, or T is entered in this field, any existing database record with a matching ID field will be deleted. If a N, 0, or F is entered the location will not be deleted. All other characters will cause the location not to be deleted.

Force Geocode 1 character If N, 0, or F is entered in this field, the imported location will not be geocoded. If Y, 1, or T is entered in this field, the imported location will be geocoded. All other characters cause the location to be geocoded. You can use this field to update address information for existing locations without re-geocoding.

Delete ST Override 1 character 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 an existing service time override will not be deleted. All other characters will not delete the service time override.

Equipment Type 15 characters The ID of the equipment type that should be used to delvier the location. This information is only used for Roadnet.

Time Window Factor 1 character A number from 0 (unimportant) to 5 (most important) indicating the importance of meeting the location’s time windows.

Delete TW Override 1 character 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 an existing time window override will not be deleted. All other characters will not delete the time window override.

Mark as Void 1 characters 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. This information is only used for Roadnet.





**If none is specified, default will be used.

^You must specify a mask indicating how the data is formatted. If no mask is specified, the Transportation Suite will assume your data is formatted according to the default mask. The default masks are:For date fields: YYYY-MM-DDFor time fields: HH:MIFor running time fields: HH:MMFor date/time fields: YYYY-MM-DD HH:MI:SS

Preferred Route ID 15 characters The unique ID of the route the location’s 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.





Location File Record LayoutCompany Name________________________________________________

File Name_____________________________________________________

Characters per Record________________Total Records_________________

Field Starting Position Length

Location ID (15 – A)

Location Name (60 – A)

Location Type (3 – A)

Address Information

Address Line 1 (50 – A)


Cross Street (30 – A)

City (30 – A)

State (20 – A)

County (30 – A)

Country (2 – A)

Zip Code (10 – A)

Latitude (11-N)

Longitude (12-N)

Phone Number (20 – A)

Fax Number (20 – A)

Store Number (15 – A)

Time Windows

Time Window Type (5 – A)

Time Window Factor (1-A)

Time Window Overrides

Open Time (Time)

Close Time (Time)

Time Window 1 Start (Time)

Time Window 1 Stop (Time)






Service Times

Service Time Type (5 – A)

No Helper Fixed (9 – N)

No Helper Variable (11 – N)

Bulk No Helper Fixed (9 – N)

Bulk No Helper Variable (11 – N)

Helper Fixed (9 – N)

Helper Variable (11 – N)

Bulk Helper Fixed (9 – N)

Bulk Helper Variable (11 – N)

Miscellaneous Info

Delivery Days (7 – A)

Equipment Typer (15-A)

Account Type (5 – A)

Zone (15 – A)

Employee ID (9 – A)

Std. Instructions (255 – A)

Delete Location (1-A)

Force Geocode (1-A)

Delete ST Override (1-A)

Delete TW Override (1-A)

Minimum Bulk Qty 1 (9 – N)



Fixed Fee (9 - N)

Variable Fee (9 - N)

Contact (255-A)

Alternate Contact (255-A)

Service Failure Notify (1-A)





Service Failure Notify Minutes (4-N)

Service Failure Notify Type (3-A)

Service Failure Notify Contact (64-A)

Mark as Void (1-A)

Preferred Route ID (15-A)





Service Time Type InformationCompany Name_______________________________________________

Service Time Types

Service Time Type ID (5 – A) ________________________________________________________

Name (30 – A) ___________________________________________________________________

Service Time No Helper Helper

Fixed (9 – N) ________________ __________________

Variable (9 – N) ________________ __________________

Bulk Fixed (9 – N) ________________ __________________

Bulk Variable (9 – N) ________________ __________________

Service Time Types

Service Time Type ID (5 – A) ________________________________________________________

Name (30 – A) ___________________________________________________________________

Service Time No Helper Helper

Fixed (9 – N) ________________ __________________

Variable (9 – N) ________________ __________________

Bulk Fixed (9 – N) ________________ __________________

Bulk Variable (9 – N) ________________ __________________




Time Window Type InformationCompany Name ________________________________________________

Time Window Types

Time Window Type ID (5 - A) ________________________________________________________

Name (30 – A) ___________________________________________________________________

Start Stop

Open/Close Time (5 - N) ________________ __________________

Time Window 1 (5 - N) ________________ __________________

Time Window 2 (5 - N) ________________ __________________

Time Window Types

Time Window Type ID (5 - A) ________________________________________________________

Name (30 – A) ___________________________________________________________________

Start Stop

Open/Close Time (5 - N) ________________ __________________

Time Window 1 (5 - N) ________________ __________________

Time Window 2 (5 - N) ________________ __________________




Checklist: Creating Location FilesBefore you send your location file information to UPS Logistics Technologies, use this checklist to make sure you have completed all the steps and included all the necessary information to geocode your locations.

_____Prepared the location file

• only those locations that need to be geocoded

• unique ID numbers for each location

• accurate location names, addresses, and phone numbers

• no PO Boxes or RFD numbers

• no “bill to” locations

• no “will calls”

• no vendor addresses (except for backhauls)

• no employee addresses

• additional information, as needed

_____Completed all the necessary forms

• Location File Record Layout

• Service Time Type Information

• Time Window Type Information

Sending Your Data to UPS Logistics Technologies

You are now ready to send your information to UPS Logistics Technologies using any of the following methods:

• Modem• 100 MB Zip disks• CD ROM• 3.5” high density disks• e-mail (zip the file and send as an attachment to [email protected];

3 MB limit)

Address: UPS Logistics Technologies, Inc. 849 Fairmount Avenue Suite 400 Baltimore, MD 21286 ATTN: Customer Service – Location File

If you have any questions about the data parameters, please contact UPS Logistics Technologies Customer Service at 1-800-762-3638.




Generating the Location Extension FileProduct: Territory Planner

The ultimate goal of Territory Planner is to create efficient, cost-effective routes. In order to create these routes, accurate current delivery information must be available. This information is given to Territory Planner in a location extension file. The location extension file contains specific information that builds on the location information, adding delivery quantities, acceptable delivery patterns (service pattern sets), and current routing information. If the current routing information is contained in the location extension file, a re-route can be done, and the time and cost savings evaluated within Territory Planner. Once you have created the location extension file, it must be sent to UPS Logistics Technologies to be incorporated into your Territory Planner software.

One very important concept in Territory Planner is the idea of planning sessions. A planning session is a group of locations that have a common denominator, such as they are all located in the same geographic area. But the real power of the planning session is that several sessions can contain the same locations, but have different extension information about the locations to allow for different routing schemes. For instance, one session may be routed for sales representatives to visit the location, while another session contains delivery information for the delivery driver, and routes based on that information. Or, one session can be used as a baseline, containing current routing information, while other sessions contain the same location but with different routing information.

Because of the flexibility planning sessions provide, information in Territory Planner is layered in a hierarchy. The location information (contained in the location import file) is on a global level, and can be used by all the planning sessions. The location extension information is specific to the planning session and can only be accessed by that session. If there is repetitious information between the location and location extension, such as delivery quantities, the more specific information for the location extension will be used.

See the instructions that follow for more information on generating the location extension file.

Step 1: Verify that each location has a unique ID. The ID must be between 1 and 15 characters in length and match the ID in the location file.

Step 2: Verify that each record only contains information for one location extension.

Step 3: If you are importing routing information, verify that each location extension includes a territory ID.

Step 4: Create a fixed-record-length ASCII data file of the location information. The location ID must be included in the file.

Note: For more information on creating the location extension file, refer to the Fields for Location Extension Information section.

Step 5: After the file has been created, complete the Location Extension File Record Layout, indicating the starting position and length of each column.




Step 6: Send the completed file and Location Extension File Record Layout form to UPS Logistics Technologies. The file can be sent using any of the following methods:


3 MB limit)

Some other tips to remember when creating this file:

• Create an individual record for each location extension, and place all information in that record. Each record should occupy a separate line.

• Verify that each location ID is unique, and that it already exists as a location.

• Verify that the delivery quantity is the total quantity for all deliveries to the extension during the cycle, not just for one stop during the cycle. For instance, if the customer receives 5 on Monday, but receives deliveries on two Mondays during the cycle, the total would be 10.

• Verify that the service pattern set contains valid delivery options for the extension. A service pattern set of 0 (Manual Load Distribution) can be assigned to all locations in the location extension file and then manually changed in Territory Planner once the information has been imported. This will assure the current routing information is not altered.

• To transfer the current routing information, verify the territory ID and delivery days are correct. The proper characters for the delivery days are MTWRFSU.

• The columns for each piece of information (ID, street name, etc.) must be the same length in each record. Left justify information in the column, leaving blank spaces after the entry if necessary; right justify numeric information in the column, leaving blank spaces prior to the entry if necessary.

• Do not place commas or other forms of punctuation between the columns.




Fields for Location Extension InformationYou can import current routing information in the location extension file, or simply the information necessary to create new routes. The only required piece of information is the location ID; the remaining information is optional.


Location ID 15 characters Unique identifier for the location.

Location Type 3 characters The type of location (SIT, DPT, etc.). If a type is not specified, the default will be used.

Territory ID 15 characters The ID of the territory the location is routed on. If the territory does not exist in the planning session, Territory Planner will add it.

Service Pattern Set 3 characters The service pattern set for the location extension. If one is not specified, the default service pattern set will assigned.

Size 1, 2, and 3 16 digits each (9.6)

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 characters to the right of the decimal is established in the Transportation Suite before the import.

Service Pattern 3 characters The service pattern assigned to the location extension. The stops will be routed based on the specified service pattern. If the service pattern is not part of the service pattern set, the service pattern will be used to route the stop.

Active Weeks 24 characters Indicates whether or not the location should be routed on that week. The active weeks field should equal the length of the cycle; an X in the space means that the stop is delivered that week, while a blank means no delivery that week. If the active weeks do not match the service pattern set, the stop will be routed on the active weeks. If the specified active weeks are invalid for the cycle, the default active weeks will be used.

Assign Days Flag 1 character Indicates whether or not the location extension should be included when routes are created using Assign Days. Enter a Y, 1, or T if the location extension should be considered for Assign Days; enter a N, 0, or F if the location should not be considered for Assign Days. If any other character is entered, the location will be flagged for Assign Days.




Day String 7 characters Indicates which days the extension should be routed. The location extension will be placed on routes on the specified days. The valid days are MTWRFSU. If the day string does not match the specified service pattern set, then the stop will be unassigned. If exporting the day string, Sunday is placed in the first position; the days are UMTWRFS.

Day Shift 1 digit The number of days the location extension should be shifted when Day Shift is run. Must be between 0 and 7.

Previous Depot ID 15 characters The unique identifier of the depot the extension was previously delivered from.

Previous Territory ID 15 characters The unique identifier of the territory the extension was previously routed on.

Previous Weeks 24 characters Indicates the weeks the extension was previously routed on. An X in the space means the stop is delivered that week, while a blank means no delivery for that week.

Previous Days 7 characters The day string indicating which days the extension was previously routed on.

Week 2 digits The number of the week the location extension should be delivered (ex. 2). The field is used when you are specifying the stop number by day.

Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, and Sunday Stop Numbers

3 digits each The number the stop is on that day’s route. If this does not match the specified 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.

Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, and Sunday Load

16 digits each (9.6)

The delivery quantity for all of that day in the cycle. If the load is defined, then the territory ID and active weeks must be specified; if the active weeks are not specified, the default active weeks will be used.

Service Time Type Override

5 characters The service time type to be used in the selected planning session(s). If no service time type is specified, the location’s service time will be used.

Delete Record 1 character 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 do not delete the record. All other characters will not delete the record.





*All fields are string (text) fields unless the data calls for a specific format.

Anchor Days Range 1 character 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 1 character 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, Any Day will be selected.

Anchor Days Wrap Flag

1 character 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 2 characters 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 session’s cycle. If no anchor weeks range is specified, 0 will be used.

Anchor Any Week Flag 1 character Specifies if Any Week will be selected for week anchoring. A Y, 1, or T means Any Week will not be selected. If no any week flag is specified, Any Week will be selected.

Anchor Weeks Wrap Flag

1 character 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 week wrap flag is specified, Allow Wrap will not be selected.





Location Extension File Record LayoutCompany Name ________________________________________________

File Name _____________________________________________________



Location ID (15 - A)

Location Type (3 - A)

Territory ID (15 - A)

Service Pattern Set (3 - A)

Size 1 (16 - N)

Size 2 (16 - N)

Size 3 (16 - N)

Service Pattern (3 - A)

Active Weeks (24 - A)

Assign Days Flag (1 - A)

Day String (7 - A)

Previous Depot (15 - A)

Previous Territory (15 - A)

Previous Weeks (24 - A)

Previous Days (7 - A)

Week (2 - N)

Monday Stop Number (3 - N)

Tuesday Stop Number (3 - N)

Wednesday Stop Number (3 - N)

Thursday Stop Number (3 - N)

Friday Stop Number (3 - N)

Saturday Stop Number (3 - N)

Sunday Stop Number (3 - N)

Monday Load (16 - N)

Tuesday Load (16 - N)




Wednesday Load (16 - N)

Thursday Load (16 - N)

Friday Load (16 - N)

Saturday Load (16 - N)

Sunday Load (16 - N)

Service Time Type Override (5-A)

Delete Record (1 - A)

Anchor Days Range (1 - N)

Anchor Any Day Flag (1 - A)

Anchor Days Wrap Flag (1 - A)

Anchor Weeks Range (2 - N)

Anchor Any Week Flag (1 - A)

Anchor Weeks Wrap Flag (1 - A)





Delivery InformationIf you are using Territory Planner you need to determine the possible delivery options, or service patterns and service pattern sets. Use the following charts to determine the service patterns you will need. The first chart is for deliveries made at least once a week. Common entries include delivering 100% of the quantity on each day of the week, and splitting deliveries among two, three, or more days of the week. The total for each week must be 100%.

Note: For more information on service patterns and service pattern sets, see the Overview section of this manual.

ID Percent Delivered On Total (%)

Monday Tuesday Wednesday Thursday Friday Saturday Sunday

100

100

100

100

100

100

100

100

100

100

100

100

100

100

100

100

100

100

100




The second chart is for deliveries that occur less than once a week, such as every second, third, or fourth week. Locations that receive deliveries less than once a week must receive the total delivery all at once, so the delivery percent for each delivery will be 100%.

Once you have created all your service patterns, you need to group them together in service pattern sets, which give Territory Planner several options for routing each location. Service pattern sets allow different service patterns to be considered based on the delivery quantity. For instance, if a location receives only small quantities, you may only want to deliver one day a week, while you may agree to deliver a location with a larger delivery quantity several times a week. The delivery quantity is based on the item chosen as size 1, identified in the User Defaults. You can specify an unlimited number of service patterns for each quantity level, and an unlimited number of quantity levels. The final quantity level must have a maximum quantity of 9,999,999.

ID Frequency Percent Delivered On Total (%)

Mon Tues Wed Thurs Fri Sat Sun

100

100

100

100

100

100

100

100

100

100

100

100

100

100

100

100

100

100

100




Service Pattern Set InformationCompany Name ________________________________________________

Service Pattern Sets

Service Pattern Set ID (3 - A) _______________________________________________________

Name (30 - A) ___________________________________________________________________

Max. Qty 1 2 3 4 5 6 7

Service Pattern Sets

Service Pattern Set ID (3 - A) _______________________________________________________

Name (30 - A) ___________________________________________________________________

Max. Qty 1 2 3 4 5 6 7




Service Pattern InformationCompany Name ______________________________________________

Service Pattern

Service Pattern ID (3 - A) ___________________________________________________________

Name (30 - A) ____________________________________________________________________

Monday

Tuesday

Wednesday

Thursday

Friday

Saturday

Sunday

Weeks Between Deliveries

Service Pattern

Service Pattern ID (3 - A) ___________________________________________________________

Name (30 - A) ____________________________________________________________________

Monday

Tuesday

Wednesday

Thursday

Friday

Saturday

Sunday

Weeks Between Deliveries




Checklist: Creating Location Extension Files Before you send your location extension file information to UPS Logistics Technologies, use this checklist to make sure you have completed all the steps and included all the necessary information.

_____Prepared the location extension file

• unique ID numbers for each location

• ID numbers match IDs in the location file


_____Completed all the necessary forms

• Location Extension File Record Layout

• Service Pattern Set Information

• Service Pattern Information




3 MB limit)

Address: UPS Logistics Technologies, Inc. 849 Fairmount Avenue Suite 400 Baltimore, MD 21286 ATTN: Customer Service – Location Extension File




Generating the SKU File

Generating the SKU File Product: FleetLoader

In order for FleetLoader to load your equipment, the program must know information about all of your SKUs. FleetLoader receives this information by downloading a SKU file, which is used to build the SKU table in your FleetLoader database. This SKU information includes the product ID or SKU; a description; a package type ID; a brand ID; service time to deliver the SKU; and stock, layer, and hand primary and secondary zones.

Note: UPS Logistics Technologies strongly recommends that this file be created and sent to UPS Logistics Technologies as soon as possible. Because most companies deliver a multitude of SKUs, sending this data ahead of time will result in decreased training time since the users will not have to input this information manually.

All data files must be in ASCII format with defined, precise column lengths between the fields. Character (text) entries should be left justified with blank spaces after the entry to fill the field; numeric entries should be right justified with blank spaces preceding the entry to fill the field. Do not place any punctuation between the fields. Each line should contain all the information for a unique record; do not place information for an individual product (SKU) on multiple lines. Each SKU must have a unique SKU ID.

Step 1: Verify that each SKU has a unique SKU ID. The SKU ID must be between 1 and 32 characters.

Step 2: Verify that the description is as complete as possible (example, 12OZ CN ROADNET COLA 1/24). The description must be between 1 and 128 characters.

Step 3: Verify that the package type ID for each SKU is a valid package type (example, 12OZ CN 1/24). The package type ID must be between 1 and 15 characters.

Step 4: Verify that the SKU brand ID for each SKU is a valid brand.

Step 5: Verify that you have included the service time and warehouse location information, as appropriate.

Step 6: Create an ASCII data file of the product (SKU) information. The SKU ID, description, package type ID, and brand ID must be included in this file.

Step 7: Send the file to UPS Logistics Technologies as soon as possible after the initial meeting.

The tables on the following pages provide information about each of the possible entries in the SKU file, including the maximum length and a description of the type of information.

Some tips to remember when creating the SKU file:

• Create an individual record for each SKU, and place all information in that record.




• The columns for each piece of information (SKU ID, description, etc.) must be the same length in each record: left justify character information in the column, leaving blank spaces after the entry if necessary; right justify numeric information in the column, leaving blank spaces preceding the entry if necessary.


• Do not provide extraneous information in this file.

A sample data file, containing the minimum amount of information required in the SKU file, is shown below:

SKU Description Pkg Type Brand

123456 12 OZ CAN CF DT ROADNET 1 1909756 16 OZ CAN CF DT ROADNET 2 1123774 12 OZ CAN CF FLEET COLA 1 2909770 16 OZ CAN CF DT FLEET 2 2




SKU File Required FieldsThe SKU is the most specific category when identifying products; it defines both the package type and brand name, such as 24 twelve-ounce cans of Roadnet Cola. The following fields are required by FleetLoader.

Field Max. Length Notes

ID 32 characters The unique ID of the SKU.

Package Type ID 15 characters The unique ID of the package type.

Brand ID 15 characters The unique ID of the brand.




SKU File Optional FieldsThe following fields are optional in FleetLoader.

Field Max. Length Notes

Bitmap 255 characters The path and filename of the bitmap that will be used o represent the SKU in the Loading Editor.

Description 128 characters The description of the SKU, such as 12 oz. bottles.

Pallet Primary Zone 15 characters Area of warehouse where full pallets are stored.

Pallet Secondary Zone 15 characters Area of warehouse where full pallets are stored.

Layer Primary Zone 15 characters Area of warehouse where layers are stored.

Layer Secondary Zone 15 characters Area of warehouse where layers are stored.

Hand Primary Zone 15 characters Area of warehouse where individual items are stored.

Hand Secondary Zone 15 characters Area of warehouse where individual items are stored.

Non Helper Size 1, 2, 3 Service Time

11 digits each The amount of time needed to deliver one unit of the SKU measured as size 1, 2, or 3 without a helper.

Helper Size 1, 2, 3 Service Time

11 digits each The amount of time needed to deliver one unit of the SKU measured as size 1, 2 or 3 with a helper.

Warehouse Zone 15 characters The zone where the SKU is located. This information is used when building pallets in the Loading Editor.




SKU InformationUse the charts on the below to gather SKU information, or extract and download the information from your host computer to diskette. Feel free to copy the charts as needed for additional SKUs. The required fields are bold.

SKU

SKU SKU Brand ID

Package Type ID Bitmap

Description Warehouse Zone

Pallet Primary Zone Pallet Secondary Zone

Layer Primary Zone Layer Secondary Zone

Hand Primary Zone Hand Secondary Zone

Size 1 Variable Service Time

Size 1 Helper Variable Service Time





SKU

SKU SKU Brand ID

Package Type ID Bitmap

Description Warehouse Zone

Pallet Primary Zone Pallet Secondary Zone

Layer Primary Zone Layer Secondary Zone

Hand Primary Zone Hand Secondary Zone










SKU File Record Layout Company Name ________________________________________________

Field Length Position

ID (32-A)

Package Type ID (15-A)

SKU Brand ID (15-A)

Description (128-A)

Stock Primary Zone (15-A)

Stock Secondary Zone (15-A)

Layer Primary Zone (15-A)

Layer Secondary Zone (15-A)

Hand Primary Zone (15-A)

Hand Secondary Zone (15-A)

Size 1 Variable Service Time (11-N)



Size 1 Helper Variable Service Time (11-N)



Warehouse Zone (15-A)

Bitmap (255-A)




Checklist: Creating SKU FilesBefore you send your SKU file information to UPS Logistics Technologies, use this checklist to make sure you have completed all the steps and included all the information needed to import your SKUs.

_____Prepared the SKU file

• unique ID numbers for each SKU


_____Completed the SKU information charts

• SKU Information Chart

• SKU Layout Record form




3 MB limit)

Address: UPS Logistics Technologies, Inc. 849 Fairmount Avenue Suite 400 Baltimore, MD 21286 ATTN: Customer Service – SKU File




Generating the Standard Route File

Generating the Standard Route FileProgram: Roadnet

Using Roadnet’s standard routing offers you and your locations reliable, consistent service. In order to do this, Roadnet needs access to your current routes. This section explains how to create your standard route files. UPS Logistics Technologies will use this information to create a routing file for Roadnet.

Step 1: Verify that each route has a unique ID. The ID must be between 1 and 15 characters in length.

Step 2: Create a fixed-record-length ASCII data file of the standard route information. The route ID, stop number, and location ID must be included in the file.

Note: For more information on creating a standard route file, refer to the Mandatory Fields for Standard Route Information section.

Step 3: Send the completed file and Standard Route File Record Layout form to UPS Logistics Technologies. The file can be sent using any of the following methods:


3 MB limit)

Some other tips to remember when creating this file:

• Each record should occupy a separate line.

• The columns for each piece of information (ID, stop number, etc.) must be the same length in each record. Left justify information in the column, leaving blank spaces after the entry if necessary; right justify numeric information in the column, leaving blank spaces prior to the entry if necessary.






Mandatory Fields for Standard Route InformationThe fields in the table below are mandatory when importing standard routes into Roadnet.

Additional Fields for Standard Route InformationAlong with the mandatory standard route information, you can send additional route information to UPS Logistics Technologies.

Field Max. Length Description

Route ID 15 characters Unique identifier for the route.

Stop Number 3 digits The sequence number of the stop on the route.



Route Number 20 digits The name of the route.

Start Time Time The time the route begins (military time, such as 09:00, 13:00).^

Depot ID 15 characters Unique ID of the depot associated with the route.

Model ID 2 characters The travel time model associated with the route.

Equipment ID 20 characters Unique identifier for the equipment associated with the route.

Driver 1 ID 15 characters The first driver associated with the route.

Helper 1 character Indicates if a helper is associated with the route. Enter a 0 if there in no helper, any other value is read as a helper.

Driver 2 ID 15 characters The second driver associated with the route.

Description 30 characters A brief description of the route, such as East Baltimore City.

Team Split 1 character Y or N to indicate whether or not the drivers split the pay equally.

Load Priority 1 digit Priority rating from 0 to 9 (lowest to highest) for loading the standard route. Roadnet does not use this field.

Preferred Time 5 digits The length of time you want the route to be.

Maximum Time 5 digits The route can not be longer than this amount of time.

Regular Time 5 digits The amount of time the driver can work before generating overtime.




*All fields are string (text) fields unless the data calls for a specific format (such as date, time, longitude and latitude).

Standard Days 7 characters The day(s) the route is valid. Valid days are MTWRFSU.

Destination Location Type

3 characters Location type ID for the route’s destination, such as DPT. This ID must exist in the Location Type table.

Destination Location ID

15 characters Unique identifier for the route’s destination.

Last Stop is Destination

1 character Y or N to indicate whether or not the last stop on the route is the final destination.

Origin is Destination 1 character Y or N to indicate whether or not the route’s origin is the final destination.





Standard Route File Record LayoutCompany Name ______________________________________________

File Name ___________________________________________________

Characters per Record_________________Total Records______________


Route ID (15 - A)

Stop Number (3 - N)


Route Name (20 - A)

Start Time (Time)

Depot ID (15 - A)

Model ID (2 - A)

Equipment ID (20 - A)

Driver (10 - A)

Helper (1 - A)

Description (30 - A)

Team Split (1 - A)

Load Priority (1)

Preferred Time (5 - N)

Maximum Time (5 - N)

Regular Time (5 - N)

Standard Days (7 - A)

Destination Location Type (3 - A)

Destination Location ID (15 - A)

Last Stop is Destination (1 - A)

Origin is Destination (1 - A)




Checklist: Creating Standard Route FilesBefore you send your standard route file information to UPS Logistics Technologies, use this checklist to make sure you have completed all the steps and included all the information needed to import your standard routes.

_____Prepared the standard route file

• unique ID numbers for each route


_____Completed the Standard Route Layout Record form




3 MB limit)

Address: UPS Logistics Technologies, Inc. 849 Fairmount Avenue Suite 400 Baltimore, MD 21286 ATTN: Customer Service – Std. Route File





Developing a File Creation Program for Daily OrdersProduct: Roadnet, FleetLoader

When you write a program to format the daily order file on your host computer, you will need to format it according to UPS Logistics Technologies’ specifications, as listed below.

• The daily order file should include orders for delivery locations.

• The daily order file should not include orders for “bill to” only deliveries or “will call” orders, unless you are going to place them on a route.

Note: If you are using the order locking feature and are sending multiple waves of order files, your host system must be able to accept the same route ID multiple times.

Step 1: Make sure the file includes all mandatory fields, listed in the table below.

*All fields are string (text) fields unless the data calls for a specific format (such as date, time, longitude, and latitude).

Step 2: Include any of the optional fields listed in the following table, if desired.



Order Number 15 characters Unique identifier for each order. You may have multiple orders for each location.

Size 1, 2, and 3 16 digits each (9.6) Total quantity of the size measurement (such as the number in pieces). The number of characters to the right of the decimal is established in the Transportation Suite before the import.


Location Type 3 characters Location type ID (must exist in the Location Type table), such as SIT.**

Order Selector

1 character Single-character field used to designate orders that require special treatment. This field does not affect the way Roadnet will process or route data.

Order Type 1 character Single-character field used to designate orders that require special treatment. Character must be one of four letters: F = Future, O = Deliver, P = Pickup, R = Return. This field affects the way Roadnet will process and route data.**

Void Order 1 character An order that has been voided. Enter Y, 1, T, or V for an order that should be marked void; enter N, O, or F for an order not marked void. Any other characters will not mark the order as void.




Size 1, Category 1, 2, 3

16 digits each (9.6) Quantity of the size 1/category 1, 2 or 3 measurement (such as the number of frozen pieces). The number of characters to the right of the decimal is established in the Transportation Suite before the import.**

Size 2, Category 1, 2 or 3

16 digits each (9.6) Quantity of the size 2/category 1, 2 or 3 measurement (such as the number of frozen cube). The number of characters to the right of the decimal is established in the Transportation Suite before the import.


16 digits each (9.6) Quantity of the size 3/category 1, 2 or 3 measurement (such as the number of frozen pounds). The number of characters to the right of the decimal is established in the Transportation Suite before the import.

Add Fixed Service Time

6 digits Amount of extra service time added to a delivery (for merchandising, customer service, etc.) in minutes.

Special Instructions

255 characters Additional delivery instructions for the order or location.

Date Added Date The date and time the order was entered.^

Taken By 9 characters ID of the employee who entered the order.

Open Time Time Location open time override (military time, such as 09:00 or 13:00).+^

Close Time Time Location close time override (military time, such as 09:00 or 13:00).+^

TW 1 Start Time Time window 1 start time override (military time, such as 09:00 or 13:00).+^To delete an existing time window, enter -1.

TW 1 Stop Time Time window 1 end time override (military time, such as 09:00 or 13:00).+^To delete an existing time window, enter -1.

TW 2 Start Time Time window 2 start time override (military time, such as 09:00 or 13:00). +^To delete an existing time window, enter –1.

TW 2 Stop Time Time window 2 end time override (military time, such as 09:00 or 13:00). +^To delete an existing time window, enter –1.

Session Date Date The date for the session you want the order added to. If a date is not specified, the order will be added to the session(s) selected on the Import Orders window. ^

Preferred Origin ID

15 characters The unique ID of the location you want to be the origin for the route.

Preferred Origin Type

3 characters The type of location you want to be the origin for the route. This will usually be DPT.






**If none is specified, the default will be used.

+ Overrides in the order import file are temporary overrides (for that delivery session only). For permanent overrides, use location maintenance.

Preferred Route ID

15 characters The unique ID of the route the order should be placed on. If a preferred route ID is specified, the order will be placed on that route during preferred route ID routing in the Routing Editor.

Force Bulk Service Time

1 character Indicates whether the order should use bulk service times, even if the quantity does not meet the location’s bulk threshold. Enter Y, 1, or T to force bulk service times; enter N, O, or F if the order should not be bulk. Any other character will not mark the order as bulk.

Order User Defined Field 1, 2, 3

20 characters each The contents of the first, second, or third user defined field for the order.

Order Begin Date

Date The first date the order can be delivered. ^

Order End Date

Date The last possible date the order can be delivered, ^

Daily Increase Size 1, 2, 3

16 digits each (9.6) The amount the quantity for each size increases each day between the begin date and when the order is delivered.

Urgency Factor

3 digits A number between 0 and 100 indicating the importance of delivering the order on the begin date. 0=not important; 100=must be delivered today.

Daily Urgency Factor Increase

3 digits The amount the urgency factor increases each day after the order’s begin date.

Item ID 32 characters The unique identifier of the activity associated with the order or an SKU. This field is only used if importing order activities or line-item level detail. If you are importing item IDs, you need to import the item type as well.

Item Type 1 character A S or A indicating whether the item ID refers to an SKU or order activity.

Total SKU Size 1, 2, 3

16 digits each (9.6) Quantity of the size 1, 2 or 3 measurement for the SKU. The number of characters to the right of the decimal is established in the Transportation Suite before the import.++

Line Item User Defined Field 1, 2, 3

20 characters each The contents of the first, second, or third user defined field for the line item.






++The item related fields and line item user defined fields must always be the last fields in each record. The 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 IDThe 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.

Step 3: Verify that all characters are ASCII printable, except for the record terminator.

Step 4: Verify that all fields adhere to the maximum length specified.

Step 5: Verify that each record ends with a consistent record terminator.

Step 6: Verify that all numeric fields are right justified and that all alphanumeric fields are left justified.

Step 7: Verify that no field exceeds the maximum number of characters allowed. Any field exceeding the maximum number of characters will be truncated.

Step 8: Return the following information to the host computer.

Note: In order to return the information to the host computer, you need to allocate space in the download file. Roadnet will automatically enter the information in the appropriate positions.

Field Justification Length

Route ID Right 15 characters

Stop Number Right 3 characters

Stop Arrival Time Right 8 characters

Stop Arrival Date Right 8 characters

Stop Departure Time Right 4 characters

Stop Departure Date Right 8 characters

Internal ID Right 5 digits




Route Name Left 30 characters

Route Start Time Right 8 characters

Route Start Date Right 8 characters

Route End Right 4 characters

Driver 1 ID Left 15 characters

Driver 2 ID Left 15 characters

Equipment 1 ID Left 15 characters

Equipment 2 ID Left 15 characters

Equipment 1 Owner ID Left 15 characters

Equipment 2 Owner ID Left 15 characters

Equipment 1 Type Left 15 characters

Equipment 2 Type Left 15 characters

Equipment 1 Description Left 255 characters

Equipment 2 Description Left 255 characters

Depot ID Left 15 characters

Depot Type Left 3 characters

Previous Distance Right 5 characters

Previous Travel Time Right 5 characters

Stop Service Time Right 5 characters

Stop Type Left 80 characters

Description Left 30 characters

Address Line 1 Left 50 characters

Address Line 2 Left 50 characters

City Left 30 characters

State Left 30 characters

Zip Left 10 characters

Latitude Right 10 characters

Longitude Right 10 characters

Geocode Quality Left 80 characters

Total Distance Right 5 characters

Total Travel Time Right 5 characters





Total Service Time Right 4 characters

Open/Close Time Left 8 characters

Time Windows Left 16 characters

Route Priority Right 1 character

Session Date Right 8 characters

Upload Selector Left 1 character

Location User Field 1 Left 20 characters



Trip Number Right 15 characters

Fixed Service Time Right 9 characters

Variable Service Time Right 9 characters

Current Size 1 Right 16 digits each (9.6)

Current Urgency Right 3 digits





Daily Orders Record LayoutCompany Name ________________________________________________

File Name _____________________________________________________

Characters per Record ______________ Total Records __________________




Order Number (15 – A)

Selector (1 – A)

Order Type (1 – A)

Void Order (1 – A)

Total of Size 1 (16– N)

Subtotal of Size 1, Category 1 (16 – N)



Total of Size 2 (16 – N)








Add Fixed Service Time (6 – N)

Special Instructions (255 – A)

Open Time (5 – N)




Close Time (5 – N)

TW1 Start (5 – N)

TW1 Stop (5 – N)

TW2 Start (5 – N)

TW2 Stop (5 – N)

Force Bulk Service Time (1- A)

Preferred Origin ID (15-A)

Preferred Origin Type (3-A)


Session Date (Date)

Order User Defined Field 1 (20-A)



Order Begin Date (Date)

Order End Date (Date)

Daily Increase Size 1 (16-N)



Urgency (3-N)

Daily Increase Urgency (3-N)

Item Type (1-A)

Item ID (32 – A)

Total SKU Size 1 (16 – N)


Total SKU Size 3 (16– N)

Line Item User Defined Field 1 (20-A)

Taken By (9 – A)





Developing a File Creation Program for LocationsProduct: Roadnet, Territory Planner, MobileCast

When you write a program to format the location file on your host computer, you will need to format it according to UPS Logistics Technologies’ specifications, as listed below.

• The location file should include information for delivery locations.

• The location file should not include information for “bill to” only locations.





Location ID 15 characters Unique identifier for location.

Location Name 60 characters Name of the location (use name of the business — such as Simon’s Streudelhaus — not owner’s name or other).

Address Line 1 50 characters Complete street address, such as 123 E Main Street. No PO Box or RR #.

City 30 characters City.

State 20 characters State or Province.

Zip Code 20 characters Zip (or Zip+4) or Postal Code.


Location Type 3 characters Location type ID (must exist in Location Type table), such as SIT.**

Address Line 2 20 characters Address line 2 (Suite #, P.O. #).

Cross Street 30 characters Cross street (closest intersecting street), such as Elm Avenue.

County 30 characters County.

Country 2 characters The two-character ISO code for the country, such as US for United States and IT for Italy. If no country is specified here, the one set in the Maintenance Options notebook will be used.

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

Phone 20 characters Area code and phone number (do not include dashes or parentheses).




Store Number 15 characters The store’s individual number if part of a chain, such as #10 for Giant #10.

Delivery Days 7 characters Location’s usual days for delivery (MTWRFSU, no spaces).

Account Type 5 characters Account type ID (must exist in Account Type table).**

Service Time Type ID 5 characters Service time type ID (must exist in Service Time Type table).**

Time Window Type ID 5 characters Time window type ID (must exist in Time Window Type table).**

User Field1, 2, 3 20 characters each

User-defined field.

Zone ID 15 characters Zone ID (must exist in Zone table).**

Latitude 11 digits In acceptable format that you specify (see Longitude).

Longitude 12 digits 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 characters 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 characters in length. 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 characters in length. For instance, a latitude of 0.032245 should be imported as 0032245, while a latitude of 51.122234 should be imported as 51122234.Decimal degrees—there 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 seconds—the latitude/ longitude must be formatted so that the minutes and whole portion of the seconds are two characters 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 minutes—the latitude/longitude must be formatted so that the whole number portion of the minutes is two characters. 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. Include negative.





Priority 1 digit Priority rating from 0 to 9 (lowest to highest) for stop; locations with a priority are placed first on a route in dynamic routing.

Fixed Fee 9 digits The fee for servicing (delivering, reloading, or emptying) the location.

Variable Fee 9 digits The variable fee is based on cost per unit delivered. 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.

Minimum Bulk Quantity 1, 2, 3

9 digits each ) Minimum bulk quantity for size 1, 2 or 3 value (if location’s order exceeds this size value, the order is delivered as bulk).

Override Days 7 characters Days to apply time window and/or service time overrides (MTWRFSU, no spaces).

Open Time Time Location open time override (military time, such as 09:00, 13:00).**^

Close Time Time Location close time override (military time, such as 09:00, 13:00).**^




Time Window 2 Stop Tim Time window 2 end time override (military time, such as 09:00, 13:00).**^To delete an existing time window, enter –1.

Helper Fixed Service Time

9 digits Fixed service time with helper (in tenths of minutes). **

Helper Variable Service Time

11 digits Variable service time with helper (must be in acceptable format that you specify: 10 minute units to 0.000001 minute units). **

No Helper Fixed Time 9 digits Fixed service time with no helper (in tenths of minutes). **

No Helper Variable Time

11 digits Variable service time with no helper (must be in acceptable format that you specify). **

Bulk Helper Fixed Service Time

9 digits Bulk fixed service time with helper (in tenths of minutes). **





Bulk Helper Variable Service Time

11 digits Bulk variable service time with helper (must be in acceptable format that you specify: 10 minute units to 0.000001 minute units). **

Bulk No Helper Fixed Time

9 digits Bulk fixed service time with no helper (in tenths of minutes). **

Bulk No Helper Variable Time

11 digits Bulk variable service time with no helper (must be in acceptable format that you specify). **

Employee ID 9 characters The employee associated with the location.

Standard Instructions 255 characters Location-specific delivery instructions.

Contact 255 characters The name of the contact person for the location.

Alternate Contact 255 characters The name of the alternate contact person for the location.

Service Failure Notify 1 character 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 Minutes

4 digits The number of minutes the stop should be delayed before a service failure notification is created. This information is only used with MobileCast.

Service Failure Notify Type

3 characters 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.

Service Failure Contact

64 characters The e-mail address of the location. This is only necessary if the Service Failure Notify Type is e-mail. This information is only used with MobileCast.

Delete Location 1 character If Y, 1, or T is entered in this field, any existing database record with a matching ID field will be deleted. If a N, 0, or F is entered the location will not be deleted. All other characters will cause the location not to be deleted.

Force Geocode 1 character If N, 0, or F is entered in this field, the imported location will not be geocoded. If Y, 1, or T is entered in this field, the imported location will be geocoded. All other characters cause the location to be geocoded. You can use this field to update address information for existing locations without re-geocoding.

Delete ST Override 1 character 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 an existing service time override will not be deleted. All other characters will not delete the service time override.





**If none is specified, default will be used.



Step 4: Verify that all records adhere to the maximum length specified.




Notes: If you want to edit an existing record, the Location ID in the file must match a Location ID within the Roadnet Transportation Suite system.

If a new Location ID matches an existing Location ID, the record is replaced with the new data.

When making edits, download only the updates that are relevant; blank items remain unchanged.

Delete TW Override 1 character 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 an existing time window override will not be deleted. All other characters will not delete the time window override.

Equipment Type 15 characters The equipment type that should deliver to the location. This information is only used in Roadnet.

Time Window Factor 1 character A number from 0 (least important) to 5 (most important) indicating the importance of meeting the location’s time windows.

Mark as Void 1 character 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 15 characters The unique ID of the route the location’s 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.





You can delete a location by sending the Location ID only or by entering a Y in the Delete column.

You can delete a time window by entering –1 in the Time Window field.




Location File Record LayoutCompany Name ________________________________________________

File Name _____________________________________________________




Location Name (60 – A)


Address Information



Cross Street (30 – A)

City (30 – A)

State (20 – A)

County (30 – A)

Country (2 – A)

Zip Code (10 – A)

Latitude (11-N)

Longitude (12-N)

Phone Number (20 – A)

Fax Number (20 – A)

Store Number (15 – A)

Time Windows

Time Window Type (5 – A)

Time Window Overrides

Open Time (Time)

Close Time (Time)








Service Times

Service Time Type (5 – N)

No Helper Fixed (9 – N)

No Helper Variable (11 – N)

Bulk No Helper Fixed (9 – N)

Bulk No Helper Variable (11 – N)

Helper Fixed (9 – N)

Helper Variable (11 – N)

Bulk Helper Fixed (9 – N)

Bulk Helper Variable (11 – N)

Miscellaneous Info

Delivery Days (7 – A)

Account Type (5 – A)

Zone (15 – A)

Employee ID (9 – A)

Std. Instructions (255 – A)

Contact (255-A)

Alternate Contact (255-A)

Service Failure Notify (1-A)

Service Failure Notify Minutes (4-N)

Service Failure Notify Type (3-A)

Service Failure Notify Contact (64-A)

Delete Location (1-A)

Force Geocode (1-A)

Delete ST Override (1-A)

Delete TW Override (1-A)







Notes: When counting the starting position of the fields, remember that MobileCast starts counting at position 0.

Required fields are bold on the form.


Fixed Fee (9 - N)

Variable Fee (9 - N)

Mark as Void (1-A)






Developing a File Creation Program for Location ExtensionsProduct: Territory Planner

If you are using Territory Planner to create strategic routes, you will need to create a program that will format your location extension information on your host computer. The table below lists the fields that can be included in the location extension file.

When you are creating the program that generates the location extension file, keep the following in mind:

The characters must be ASCII printable, except for the record terminator.

• An individual record must exist for every location ID. The record terminator must be consistent.

• The columns for each piece of information must be the same length in each record. Left justify character information in the column, leaving spaces after the entry if necessary; right justify numeric information in the column, leaving spaces before the entry if necessary.


You will need to create a second program that can receive a fixed-column length ASCII file from Territory Planner and parse the information to the proper place in the mainframe. Territory Planner will place each field in the same location it was in the location and location extension files, plus some additional fields.



Location Type 3 characters The type of location (SIT, DPT, etc.). If a type is not specified, the default will be used.

Territory ID 15 characters The ID of the territory the location is routed on. If the territory does not exist in the planning session, Territory Planner will add it.

Service Pattern Set 3 characters The service pattern set for the location extension. If one is not specified, the default service pattern set will assigned.

Size 1, 2, and 3 16 characters 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 characters to the right of the decimal is established in the Transportation Suite before the import.

ROADNET TRANSPORTATION SUITE Preparations Guide 96



Service Pattern 3 characters The service pattern assigned to the location extension. The stops will be routed based on the specified service pattern. If the service pattern is not part of the service pattern set, the service pattern will be used to route the stop.

Active Weeks 12 characters Indicates whether or not the location should be routed on that week. The active weeks field should equal the length of the cycle; an X in the space means that the stop is delivered that week, while a blank means no delivery that week. If the active weeks do not match the service pattern set, the stop will be routed on the active weeks. If the specified active weeks are invalid for the cycle, the default active weeks will be used.

Assign Days Flag 1 character Indicates whether or not the location extension should be included when routes are created using Assign Days. Enter a Y, 1, or T if the location extension should be considered for Assign Days; enter a N, 0, or F if the location should not be considered for Assign Days. If any other character is entered, the location will be flagged for Assign Days.

Day String 7 characters Indicates which days the extension should be routed. The location extension will be placed on routes on the specified days. The valid days are MTWRFSU. If the day string does not match the specified service pattern set, then the stop will be unassigned. If exporting the day string, Sunday is placed in the first position; the days are UMTWRFS.

Day Shift 1 character The number of days the location extension should be shifted when Day Shift is run. Must be between 0 and 7.

Previous Depot 15 characters The unique identifier of the depot the extension was previously delivered from.

Previous Territory 15 characters The unique identifier of the territory the extension was previously routed on.

Previous Weeks 12 characters Indicates the weeks the extension was previously routed on. An X in the space means the stop is delivered that week, while a blank means no delivery for that week.

Previous Days 7 characters The day string indicating which days the extension was previously routed on.

Week Delivered 2 characters The number of the week the location extension should be delivered (ex. 2). The field is used when you are specifying the stop number by day.





Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, and Sunday Stop Numbers

3 characters each The number the stop is on that day’s route. If this does not match the specified 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.

Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, and Sunday Load

16 characters each

The delivery quantity for all of that day in the cycle. If the load is defined, then the territory ID and active weeks must be specified; if the active weeks are not specified, the default active weeks will be used.

Service Time Type Override

5 characters The service time type to be used in the selected planning session(s). If no service time type override is specified, the location’s service time will be used.

Delete Record 1 character 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 do not delete the record. All other characters will not delete the record.

Anchor Days Range 1 character 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 1 character 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, Any Day will be selected.

Anchor Days Wrap Flag

1 character 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 2 characters 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 session’s cycle. If no anchor weeks range is specified, 0 will be used.

Anchor Any Week Flag 1 character Specifies if Any Week will be selected for week anchoring. A Y, 1, or T means Any Week will not be selected. If no any week flag is specified, Any Week will be selected.





Note: Once you have created your new routes in Territory Planner, you can upload the routing information to your host computer. To add this information directly to the location extension download file, you should allocate space in the download file. You can specify where you want the information placed in the upload file. The following fields can be uploaded from Territory Planner.

Anchor Weeks Wrap Flag

1 character 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 week wrap flag is specified, Allow Wrap will not be selected.



Open Left 5 characters

Close Left 5 characters

TW1 Start Left 5 characters

TW1 Stop Left 5 characters

TW2 Start Left 5 characters

TW2 Stop Left 5 characters

No Helper Fixed Right 9 characters

No Helper Variable Right 9 characters

Helper Fixed Right 9 characters

Helper Variable Right 9 characters

Geocode Status Left 64 characters

Session Description Left 64 characters

Stop Number Right 3 characters

Day Left 1 character

Arrival Time Right 5 characters

Travel Time Right 5 characters

Distance Right 5 characters

Service Time Right 5 characters

Stop Size 1 Right 15 characters(9.6 characters each)






Depot ID Left 15 characters

Depot Type Left 3 characters

Equipment ID Left 15 characters

Equipment Type Left 3 characters

Driver ID Left 15 characters

Helper Left 1 character

Route ID Left 15 characters





Location Extension File Record LayoutCompany Name ________________________________________________

File Name _____________________________________________________




Location Type (3 - A)

Territory ID (15 - A)

Service Pattern Set (3 - A)

Size 1 (16 - N)

Size 2 (16 - N)

Size 3 (16 - N)

Service Pattern (3 - A)

Active Weeks (12 - A)

Assign Days Flag (1 - A)

Day String (7 - A)

Previous Depot (15 - A)

Previous Territory (15 - A)

Previous Weeks (12 - A)

Previous Days (7 - A)

Week (2 - N)

Monday Stop Number (3 - N)

Tuesday Stop Number (3 - N)

Wednesday Stop Number (3 - N)

Thursday Stop Number (3 - N)

Friday Stop Number (3 - N)

Saturday Stop Number (3 - N)

Sunday Stop Number (3 - N)

Monday Load (16 - N)

Tuesday Load (16 - N)




Wednesday Load (16 - N)

Thursday Load (16 - N)

Friday Load (16 - N)

Saturday Load (16 - N)

Sunday Load (16 - N)

Service Time Type Override (5-A)

Delete Record (1 - A)

Anchor Days Range (1 - N)

Anchor Any Day Flag (1 - A)

Anchor Days Wrap Flag (1 - A)

Anchor Weeks Range (2 - N)

Anchor Any Week Flag (1 - A)

Anchor Weeks Wrap Flag (1 - A)





Developing a File Creation Program for Routed SolutionsProduct: Roadnet, FleetLoader

If you are using FleetLoader but not Roadnet, you will need to import the routes into FleetLoader so they can be loaded. When you write a program to format the routed solution file on your host computer, you will need to format it according to UPS Logistics Technologies’ specifications, as listed below.

You can import routes created in eRoadnet or another web-based management tool into Roadnet to evaluate the routes and edit them as necessary. The Import Routed Solution option is also used if you are using FleetLoader without Roadnet. When you write a program to format the routed solution file on your host computer, you will need to format it according to UPS Logistics Technologies’ specifications, as listed below.

If you are using Roadnet and it is integrated with FleetLoader, you do not need to import the routes into FleetLoader.

• The routed solution file should include orders for delivery locations.

• The daily order file should not include orders for “bill to” only deliveries or “will call” orders, unless they are placed on routes.

• Any order without a route ID will be unassigned in Roadnet.

• If you are including waits, breaks, or layovers, associate the break with the stop preceding it, and a wait or layover with the stop following it.


*All fields are string (text) fields unless the data calls for a specific format (such as date, time, longitude or latitude).




Order Number 15 characters Unique identifier for each order. You may have multiple orders for each location.

Size 1, 2, and 3 15 digits each (9.6) Total quantity of the size measurement (such as the number in pieces). The number of characters to the right of the decimal is established in the Transportation Suite before the import.

Route ID 15 characters The unique ID of the route. If the route ID is not included, the order will be unassigned. If performing subsequent transmissions, include the route ID.


Route Description 30 characters The description for the route, such as the city name.




Route Start Date Date The starting date for the route.^ If the route start date is not specified, the session date will be used.

Route Start Time Time The starting time for the route. ^ If the route start time is not specified, the default start time is used.

Location Type 3 characters Location type ID (must exist in the Location Type table), such as SIT.**

Stop Sequence 4 digits The sequence number of the stop on the route. This field is single-character based. If doing subsequent transmission, include the stop sequence number.

Order Selector 1 character Single-character field used to designate orders that require special treatment. This field does not affect the way Roadnet will process or route data.

Order Type 1 character Single-character field used to designate orders that require special treatment. Character must be one of four letters: F = Future, O = Delivery, P = Pickup, R = Return. This field affects the way Roadnet will process and route data.

Void Order 1 character An order that has been voided. Enter Y, 1, T, or V for an order that should be marked void; enter N, O, or F for an order not marked void. Any other characters will not mark the order as void.


16 digits each (9.6) Quantity of the size 1/category 1, 2 or 3 measurement (such as the number of frozen pieces).**


16 digits each (9.6) Quantity of the size 2/category 1, 2, or 3 measurement (such as the number of frozen cube). The number of characters to the right of the decimal is established in the Transportation Suite before the import.**


16 digits each (9.6) Quantity of the size 3/category 1, 2 or 3 measurement (such as the number of frozen pounds). The number of characters to the right of the decimal is established in the Transportation Suite before the import.**

Add Fixed Service Time

6 digits Amount of extra service time added to a delivery (for merchandising, customer service, etc.) in minutes.**

Special Instruction 255 characters Additional delivery instructions for the order or location.

Date Added Date/Time The date and time the order was entered.^

Taken By 9 characters Name of the employee who entered the order.

Open Time Time Location open time override (military time, such as 09:00 or 13:00).+^





Close Time Time Location close time override (military time, such as 09:00 or 13:00).+^

TW 1 Start Time Time window 1 start time override (military time, such as 09:00 or 13:00).+^To delete an existing time window, enter –1.


TW 2 Start Time Time window 2 start time override (military time, such as 09:00 or 13:00).+^To delete an existing time window, enter –1.


Paid Break 6 digits The length of the break, in minutes.

Unpaid Break 6 digits The length of the break, in minutes.

Paid Wait 6 digits The length of the wait, in minutes.

Unpaid Wait 6 digits The length of the wait, in minutes.

Paid Layover 6 digits The length of the layover, in minutes.

Unpaid Layover 6 digits The length of the layover, in minutes.

Planned Delivery Date

Date The date you want the order to be delivered. If no date is specified, the order will be routed on the Preferred Delivery Date.^

Preferred Origin ID 15 characters The unique ID of the location you want the order to come from, usually the depot. This does not need to match the route’s origin, and will only be used if routes are created in the Routing Editor.

Preferred Origin Type

3 characters 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 route’s origin and will only be used if routes are created in the Routing Editor

Origin Depot ID 15 characters The depot the route starts at.

Destination Depot ID

15 characters The depot the route ends at.


1 character Indicates whether or not the last stop is the destination, or if the route returns to a depot.

Session Date Date The date of associated with the routing session. Normally, this would also be the route’s start date.^





Preferred Route ID 15 characters 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.

Post Route Time 6 digits The amount of time, in minutes, that the driver needs at the depot to complete paperwork before the route is considered complete. Since the driver is paid for this time, it is considered part of the total route time.

Pre Route Time 6 digits The amount of time, in minutes, that the driver needs at the depot before departing to start the route. Since the driver is paid for this time, it is considered part of the total route time.

Preferred Skill Set 15 characters 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.

Force Bulk Service Time

1 character Indicates whether the order should use bulk service times, even if the quantity does not meet the location’s bulk threshold. Enter Y, 1, or T to force bulk service times; enter N, O, or F if the order should not be bulk. Any other character will not mark the order as bulk.

Driver 1, 2 ID 15 characters each The unique identifier for the driver(s) assigned to the route.

Equipment ID 20 characters The unique identifier for the equipment assigned to the route.

Equipment Type 15 characters The type of equipment assigned to the route.

Order User Defined Field 1, 2, 3

20 characters each The contents of the user defined field(s) associated with the order.

Order Begin Date Date The first date the order can be delivered.^

Order End Date Date The last possible date the order can be delivered,^

Daily Increase Size 1, 2, 3

16 digits each (9.6) The amount the quantity for each size increases each day between the begin date and when the order is delivered.

Urgency Factor 3 digits A number between 0 and 100 indicating the importance of delivering the order on the begin date. 0=not important; 100=must be delivered today

Daily Urgency Factor Increase

3 digits The amount the urgency factor increases each day after the order’s begin date.





*All fields are string (text) fields unless the data calls for a specific format (such as date, time, longitude or latitude).

**If none is specified, the default will be used.

+ Overrides in the order import file are temporary overrides (for that delivery session only). For permanent overrides, use location maintenance.


++ The item related fields and line item user defined fields must always be the last fields in each record. The 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 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.

Verify that all characters are ASCII printable, except for the record terminator.Step 3: Verify that all records adhere to the maximum length specified.

Item ID 32 characters The unique identifier of the activity associated with the order or an SKU. This field is only used if importing order activities or line-item level detail. If you are importing item IDs, you need to import the item type as well.

Item Type 1 character A S or A indicating whether the item ID is an SKU or order activity.

Total SKU Size 1, 2, 3

16 digtis each (9.6) Quantity of the size 1, 2 or 3 measurement for the SKU. The number of characters to the right of the decimal is established in the Transportation Suite before the import.++

SKU User Defined Field 1, 2, 3

20 characters each The contents of the user defined field(s) associated with the SKU.









Routed Solution Record LayoutCompany Name ________________________________________________

File Name _____________________________________________________





Route ID (15-A)

Route Description (30-A)

Route Start Date (Date)

Route Start Time (Time)

Stop Sequence (3-N)

Order Number (15 – A)

Selector (1 – A)

Order Type (1 – A)

Void Order (1 – A)
















Add Fixed Service Time (6 – N)

Special Instructions (255-A)

Open Time (Time)

Close Time (Time)

TW1 Start (Time)

TW1 Stop (Time)

TW2 Start (Time)

TW2 Stop (Time)

Paid Break (6-N)

Unpaid Break (6-N)

Paid Wait (6-N)

Unpaid Wait (6-N)

Paid Layover (6-N)

Unpaid Layover (6-N)

Force Bulk Service Time (1- A)

Preferred Origin ID (15-A)

Preferred Origin Type (3-A)

Planned Delivery Date (Date)

Preferred Skill Set (15-A)





Order Begin Date (Date)

Order End Date (Date)








Urgency (3-N)

Daily Increase Urgency (3-N)

Item ID (32-A)

Item Type (1-A)




SKU User Defined Field 1 (20-A)



Equipment Type ID (15-A)

Equipment ID (20-A)

Driver 1 ID (15-A)

Driver 2 ID (15-A)

Origin Depot ID (15-A)

Destination Depot ID (15-A)

Last Stop is Destination (1-A)

Session Date (Date)

Post Route Time (6-N)

Pre Route Time (6-N)





Developing a File Creation Program for EmployeesProduct: Roadnet, Territory Planner, FleetLoader, MobileCast

When you write a program to format the employee file on your host computer, you will need to format it according to UPS Logistics Technologies’ specifications, as listed below.




Employee ID 15 characters The employee’s unique identification. This is usually the social security number.

Employee Type 3 characters The employee’s type, such as DRV for Driver.


First Name 35 characters The employee’s first name, as it should appear on payroll reports; not a nickname.

Middle Name 35 characters The employee’s middle name.

Last Name 35 characters The employee’s last name.

Active 1 character A Y or N indicating if the employee is available to be assigned to a route.

Address Line 1 50 characters The employee’s home address; use the street address, such as 849 Fairmount Ave.

Address Line 2 20 characters Any portion of the employee’s home address that did not fit on the first line, such as an apartment or suite number.

City 30 characters The city where the employee lives.

County 30 characters The county where the employee lives.

State 20 characters The state where the employee lives.

Postal Code 15 characters The five or nine digit zip code, or postal code.

Country 3 characters The three letter abbreviation for the country where the employee lives, such as USA.

ADP File Number 10 characters If you use ADP to process payroll, the employee’s unique ADP number. See your ADP software for more information.

Date of Birth Date The employee’s date of birth.^

Start Date Date The date the employee started employment.^

Termination Date Date The employee’s final date of employment.^










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

Status 3 characters The employee’s status, such as RDY for available.

Work Phone Number 20 characters The phone number the employee can be contacted at while at work; include the area code. Do not include dashes or parantheses.

Skill Set ID 15 characters The unique identifier of the skill set containing the activities the employee can complete.





Employee Table Layout FormFile Name: _____________________________________________________

Region: _______________________________________________________

Notes: When counting the starting position of the fields, remember that the Roadnet Transportation Suite starts counting at position 0.



Employee ID (15-A)

Employee Type (3-A)

Active (1-A)

Address Line 1 (50-A)

Address Line 2 (20-A)

ADP File Number (10-A)

Country (3-A)

Date of Birth (Date)

Start Date (Date)

Termination Date (Date)

First Name (35-A)

Home Phone Number (20-A)

Last Name (35-A)

Middle Name (35-A)

Postal Code (15-A)

City (30-A)

State (20-A)

County (30-A)

Status (3-A)

Work Phone Number (20-A)

Skill Set ID (15-A)




Developing a File Creation Program for DriversProduct: Roadnet, Territory Planner, MobileCast

When you write a program to format the driver file on your host computer, you will need to format it according to UPS Logistics Technologies’ specifications, as listed below.




Driver ID 15 characters The driver’s unique identification. This must match the driver’s employee ID.


Date of Last Drug Test Dater The date of the driver’s last drug test.^

Date of Last Physical Date The date of the driver’s last physical.^

Date of License Expiration

Date The date the driver’s license expires. If a driver with an expired license is assigned to a route, a warning appears in MobileCast.^

Driver Type 3 characters The type of driver, such as TRN for trainee.

License Number 30 characters The driver’s license number.

Wireless ID 24 characters If the driver is assigned a wireless device, the unique identification of the device.

Wireless Provider 2 characters The number indicating the wireless provider being used. Use the following guidelines: 0=None;1=Qualcomm ;2=RNMobile; 3=WAP; 4=JavaMobile; 5=Broadbeam; 6=ITrak; 7=Custom

DOT Period 11 digits Number of consecutive days in driver’s work period.

DOT Max Time 11 digits Maximum number of consecutive days in a driver’s work period.

Helper Regular Rate 9 digits Amount paid per minute, if driver and are paid by the hour.

Helper Overtime Rate 9 digits Amount paid per minute when driver and helper are working overtime.

Helper Minimum Time 11 digits Minimum number of hours the driver and helper are guaranteed to get paid for, if they are paid by the hour (military time, such as 0900, 1300).

Helper Overtime Hrs Begin

11 digits Number of hours the driver and helper need to work before overtime hours begin (military time, such as 0900, 1300).




Helper Per Stop Rate 9 digits Amount driver and helper are paid per stop.

Helper Minimum Stops 11 digits Minimum number of stops the driver and helper are guaranteed to get paid for, if they are paid per stop.

Helper Per Distance Rate

9 digits Amount the driver and helper are paid per mile/kilometer driven.

Helper Minimum Distance

11 digits Minimum distance the driver and helper are guaranteed to get paid for, if driver is paid per distance.

Helper Per Piece Over Min

9 digits Amount the driver and helper are paid per piece over established minimum.

Helper Minimum Piece 11 digits Minimum number of pieces the driver and helper are guaranteed to be paid for, if the driver is paid per piece.

Helper Fixed Daily Cost 9 digits Any driver and helper fixed costs that are not associated with the route.

Non-Helper Regular Rate

9 digits Amount driver is paid per minute, if driver is paid by the hour.

Non-Helper Overtime Rate

9 digits Amount driver is paid per minute when working overtime.

Non-Helper Minimum Time

11 digits Minimum number of hours driver is guaranteed to get paid for, if driver is paid by the hour (military time, such as 0900, 1300).

Non-Helper Overtime Hrs Begin

11 digits Number of hours driver needs to work before overtime hours begin (military time, such as 0900, 1300).

Non-Helper Per Stop Rate

9 digits Amount driver is paid per stop.

Non-Helper Minimum Stops

11 digits Minimum number of stops driver is guaranteed to get paid for, if driver is paid per stop.

Non-Helper Per Distance Rate

9 digits Amount driver is paid per mile/kilometer driven.

Non-Helper Minimum Distance

11 digits Minimum distance the driver is guaranteed to get paid for, if driver is paid per distance.

Non-Helper Per Piece Over Min

9 digits Amount driver is paid per piece over established minimum.

Non-Helper Minimum Piece

11 digits Minimum number of pieces the driver is guaranteed to be paid for, if the driver is paid per piece.











Non-Helper Fixed Daily Cost

9 digits Any fixed driver costs not associated with the route.

Password 9 characters A password used by the driver to login to the MobileCast application on the wireless device.

Driver Directions 1 character Y or N to indicate whether or not driver directions are downloaded automatically to the wireless device. Only used by MobileCast.

Preferred Location ID 15 characters The unique identifier for the depot the driver works out of.

Preferred Lcoation Type 3 characters The type for the depot; usually DPT.

Preferred Equipment Type

15 characters The type of equipment the driver uses.

Preferred Equipment ID 20 characters The equipment the driver prefers to use. This can automatically be assigned to the driver’s route in the Routing Editor.

Preferred Equipment Owner

9 characters The ID of the region that owns the preferred equipment.

Preferred Route ID 15 characters The ID for the route the driver prefers. The ID can automatically be assigned to the driver’s route in the Routing Editor.





Driver Table Layout FormFile Name: _____________________________________________________

Region: _______________________________________________________


Driver ID (15-A)

Date of Last Drug Test (Date)

Date of Last Physical (Date)

Date of License Expiration (Date)

Driver Type (3-A)

License Number (30-A)

Wireless ID (24-A)

Wireless Provider (2-A)

DOT Period (11-N)

DOT Max Time (11-N)

Helper Regular Rate (9-N)

Helper Overtime Rate (9-N)

Helper Minimum Time (11-N)

Helper Overtime Hrs Begin (11-N)

Helper Per Stop Rate (9-N)

Helper Minimum Stops (11-N)

Helper Per Distance Rate (9-N)

Helper Minimum Distance (11-N)

Helper Per Piece Over Min (9-N)

Helper Minimum Piece (11-N)

Helper Fixed Daily Cost (9-N)

Non-Helper Regular Rate (9-N)

Non-Helper Overtime Rate (9-N)






Non-Helper Minimum Time (11-N)

Non-Helper Overtime Hrs Begin (11-N)

Non-Helper Per Stop Rate (9-N)

Non-Helper Minimum Stops (11-N)

Non-Helper Per Distance Rate (9-N)

Non-Helper Minimum Distance (11-N)

Non-Helper Per Piece Over Min (9-N)

Non-Helper Minimum Piece (11-N)

Non-Helper Fixed Daily Cost (9-N)

Password (9-A)

Driver Directions (1-A)

Preferred Depot ID (15-A)

Preferred Depot Type (3-A)

Preferred Equipment (20-A)

Preferred Equipment Type (15-A)

Preferred Equipment Owner (9-A)






Developing a File Creation Program for Equipment TypesProduct: Roadnet, Territory Planner, FleetLoader, MobileCast

When you write a program to format the equipment type file on your host computer, you will need to format it according to UPS Logistics Technologies’ specifications, as listed below.




Equipment Type ID 15 characters The unique identifier for the equipment type.


Description 255 characters A description of the equipment type.

Body Type 15 digits The type for the equipment. Use 0 for a sideloader, 1 for a straight truck, and 10 for a trailer. This information is only used for FleetLoader.

Carries Load 1 character 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.

Fixed Cost 11 characters The cost for running the equipment regardless of the distance traveled. This includes costs such as insurance, license fees, etc.

Height 11 digits The height of the equipment.

Full Bays Behind Rear Wheels

5 digits The number of bays behind the rear wheels on the driver’s 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 Wheels

5 digits The number of full bays between the front and rear wheels on the driver’s 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.

Front Wheel Bays 5 digits The number of bays over the front wheels on the driver’s 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.









Pallet Positions 5 digits The number of pallets that can fit on the driver’s 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 Axles 5 digits The number of rear axles on the equipment. This information is only used for FleetLoader.

Rear Bays 5 digtis 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 Wheel Bays 5 digits The number of bays over the rear wheels on the driver’s 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.

Power Unit 1 character Indicates whether or no 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.

Total of Size 1, 2, 3 11 digits 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

11 digtiseach The amount of product the equipment can hold when measured as size 1, category 1, 2 or 3.

Travel Restriction 1 character 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.

Variable Cost 11 digits The total operating cost per mile/kilometer for the equipment type. This cost includes things such as wear and tear, gasoline, and oil.

Weight 11 digits The weight of the equipment.





Equipment Type Table Layout FormFile Name: _____________________________________________________

Region: _______________________________________________________


Equipment Type ID (15-A)

Body Type (1-A)

Carries Load (1-A)

Description (255-A)

Fixed Cost (11-N)

Height (11-N)

Full Bays Behind Rear Wheel Bays (5-N)

Full Bays Between Wheel Bays (5-N)

Front Wheel Bays (5-N)

Pallet Positions (5-N)

Rear Axles (5-N)

Rear Bays (5-N)

Rear Wheel Bays (5-N)

Power Unit (1-A)

Total of Size 1 (11-N)



Total of Size 1 Category 1 (11-N)














Travel Restrictions (1-A)

Variable Cost (11-N)

Weight (11-N)





Developing a File Creation Program for EquipmentProduct: Roadnet, Territory Planner, FleetLoader, MobileCast

When you write a program to format the equipment file on your host computer, you will need to format it according to UPS Logistics Technologies’ specifications, as listed below.

Step 1: Make sure the file includes all mandatory fields, listed in the table below



Equipment ID 20 characters The unique identifier for the equipment.

Equipment Type 15 characters The type of equipment, such as TRC for tractor or TRL for trailer.


Date Dropped Off Date The date the equipment was dropped at the location where it is currently.^

Date of Inspection Date The date of the equipment’s most recent inspection.^

Description 255 characters A description of the equipment.

Location ID 15 characters The unique identification of the location where the equipment currently is.

Location Type 3 characters The type of location where the equipment is, such as DPT for depot.

Status 3 characters The equipment’s status, such as RDY for ready/available.

Wireless ID 24 characters If the equipment is assigned a wireless device, the unique identification for the device.

Wireless Provider 2 digits The two digits for the appropriate wireless provider.Use the following guidelines: 0=None;1=Qualcomm ;2=RNMobile; 3=WAP; 4=JavaMobile; 5=Broadbeam; 6=ITrak; 7=Custom

Buddy Equipment ID 20 characters Unique identifier of the piece of equipment paired with this piece of equipment.

Buddy Equipment Type ID

15 characters Unique identifier of the type of equipment (trailer, tractor, etc.) paired with this piece of equipment.










Onboard Computer 1 character Y or N to indicate whether or not this piece of equipment uses Tripmaster. Ths is only used with MobileCast.

Preferred Driver 15 characters The driver who prefers to use the equipment.

Preferred Driver Owner 9 characters The ID of the region the driver is assigned to.





Equipment Table Layout FormFile Name: _____________________________________________________

Region: _______________________________________________________




Equipment ID (20-A)

Equipment Type (15-A)

Date Dropped Off (25-A)

Date of Inspection (25-A)

Equipment Description (255-A)

Location ID (15-A)

Location Type (3-A)

Status (3-A)

Wireless ID (24-A)

Wireless Provider (2-N)

Buddy Equipment ID (20-A)

Buddy Equipment Type ID (15-A)

Onboard Computer (1-A)

Preferred Driver (15-A)

Preferred Driver Owner (9-A)




Developing a File Creation Program for ContainersProduct: MobileCast

When you write a program to format the container file on your host computer, you will need to format it according to UPS Logistics Technologies’ specifications, as listed below.

Step 1: Make sure the file includes all mandatory fields, listed in the table below








Container ID 32 characters The unique identifier for the container.

Last Dropped at Location ID

15 characters The unique identifier for the location where the container is currently located.

Last Dropped at Location Type

3 characters The type of location where the container is currently located.


Type 3 characters The type of the container.




Container Table Layout FormFile Name: _____________________________________________________

Region: _______________________________________________________




Container ID (32-A)

Last Dropped at Location ID (15-A)

Last Dropped at Location Type (3-A)

Type Code (3-A)




Developing a File Creation Program for SKUsProduct: Roadnet, FleetLoader

In order for FleetLoader to load your equipment, the program must know information about all of your SKUs. FleetLoader receives this information by downloading a SKU file, which is used to build the SKU table in your FleetLoader database. This SKU information includes the product ID or SKU; a description; a package type ID; a brand ID; service time to deliver the SKU; and stock, layer, and hand primary and secondary zones.

If you are using Roadnet and your orders contain line items, then all SKU information needs to be downloaded.

Notes: All data files must be in ASCII format with defined, precise column lengths between the fields. Character (text) entries should be left justified with blank spaces after the entry to fill the field; numeric entries should be right justified with blank spaces preceding the entry to fill the field. Do not place any punctuation between the fields. Each line should contain all the information for a unique record; do not place information for an individual product (SKU) on multiple lines. Each SKU must have a unique SKU ID.

Step 1: Verify that each SKU has a unique SKU ID. The SKU ID must be between 1 and 32 characters.

Step 2: Verify that the description is as complete as possible (example, 12OZ CN ROADNET COLA 1/24). The description must be between 1 and 128 characters.

Step 3: Verify that the package type ID for each SKU is a valid package type (example, 12OZ CN 1/24).

Note: Because package types are used for determining capacity, stack rules, and bay preference loading, you should use only enough package types to cover all unique dimensions, but still allow for variation for stack rules and preferences. Your consultant will help you determine how many package types you will need.

Step 4: Verify that the SKU brand ID for each SKU is a valid brand.

Step 5: Verify that you have included the service time and warehouse location information, as appropriate.

Step 6: Create an ASCII data file of the product (SKU) information. The SKU ID, description, package type ID, and brand ID must be included in this file.

The tables on the following pages provide information about each of the possible entries in the SKU file, including the maximum length and a description of the type of information.

Some tips to remember when creating the SKU file:

• Create an individual record for each SKU, and place all information in that record.

• The columns for each piece of information (SKU ID, description, etc.) must be the same length in each record: left justify character information in the column, leaving




blank spaces after the entry if necessary; right justify numeric information in the column, leaving blank spaces preceding the entry if necessary.



A sample data file, containing the minimum amount of information required in the SKU file, is shown below:

The SKU is the most specific category when identifying products; it defines both the package type and brand name, such as 24 twelve-ounce cans of Roadnet Cola.

The following fields are required.

The following fields are optional in FleetLoader.

SKU Description PKG Type Brand

123456 12 OZ CAN CF DT ROADNET 1 1909756 16 OZ CAN CF DT ROADNET 2 1123774 12 OZ CAN CF FLEET COLA 1 2909770 16 OZ CAN CF DT FLEET 2 2


ID 32 characters The unique ID of the SKU.

Package Type ID 15 characters The unique ID of the package type.

Brand ID 15 characters The unique ID of the brand.


Bitmap 255 character The path and filename of the bitmap that will be used o represent the SKU in the Loading Editor.

Description 128 characters The description of the SKU, such as 12 oz. bottles.

Pallet Primary Zone 15 characters Area of warehouse where full pallets are stored.

Pallet Secondary Zone 15 characters Area of warehouse where full pallets are stored.

Layer Primary Zone 15 characters Area of warehouse where layers are stored.

Layer Secondary Zone 15 characters Area of warehouse where layers are stored.

Hand Primary Zone 15 characters Area of warehouse where individual items are stored.




Hand Secondary Zone 15 characters Area of warehouse where individual items are stored.

Non Helper Size 1, 2, 3 Service Time

11 digits each The amount of time needed to deliver one unit of the SKU measured as size 1, 2 or 3 without a helper.

Helper Size 1, 2, 3 Service Time

11 digits each The amount of time needed to deliver one unit of the SKU measured as size 1, 2 or 3 with a helper.

Warehouse Zone ID 15 characters The warehouse zone’s ID where the SKU is located. This information is used when building pallets in the Loading Editor.





SKU Record Layout FormCompany Name ________________________________________________

File Name _____________________________________________________



ID (32-A)

Description (128-A)


SKU Brand ID (15-A)

Stock Primary Zone (15-A)

Stock Secondary Zone (15-A)

Layer Primary Zone (15-A)

Layer Secondary Zone (15-A)

Hand Primary Zone (15-A)

Hand Secondary Zone (15-A)







Warehouse Zone (15-A)

Bitmap (255-A)




Developing a File Creation Program for SKU BrandsProduct: Roadnet, FleetLoader

SKU brands are the brand names of the various products delivered, such as RN Cola or RN Lite. You will need to use SKU Brands only if you have purchased FleetLoader or if you intend to import SKU level detail in your order file.


Brand ID 15 characters The unique identification for the SKU brand.

Description 30 characters A description of the SKU brand.




SKU Brand Record Layout FormCompany Name ________________________________________________

File Name _____________________________________________________



Brand ID (15-A)

Description (30-A)




Developing a File Creation Program for Package TypesProduct: Roadnet, FleetLoader

Package types define the various types of packages loaded on your equipment, such as 12-ounce cans or 2-liter bottles. Package types are used to define the capacity of a pallet or a layer on a pallet. You will need to use package types only if you intend to import SKU-level detail into your import file or if you have purchased Roadnet or FleetLoader.


Package Type ID 15 characters The package type’s unique identification. Mandatory field.

Description 30 characters A description of the package type.

Bitmap 255 characters The path and filename of the bitmap that will be used to represent the package type in the Loading Editor.

Depth 15 digits The depth of the package type.

Equivalency 15 digits The equivalency factor the package type quantity is multiplied by to even out the package type sizes, service times, etc.

Height 15 digits The height of the package type.

Weight 15 digits The weight of the package type.

Width 15 digits The width of the package type.




Package Type Record Layout FormCompany Name ________________________________________________

File Name _____________________________________________________




Region ID (9-A)

Description (30-A)

Bitmap (255-A)

Depth (15-N)

Equivalency (15-N)

Height (15-N)

Weight (15-N)

Width (15-N)




Developing a File Creation Program for Skill SetsProduct: Roadnet, MobileCast

When you write a program to format the skill set file on your host computer, you will need to format it according to UPS Logistics Technologies’ specifications, as listed below.









Skill Set ID 15 characters The unique identifier for the skill set.


Description 60 characters A description of the skill set.

Service Time Factor 11 digits The factor to multiply the activities’s service time by to determine the amount of time employees with this skill set need to perform the activity. The service time factor can be used to compensate for the difference between the amount of time it takes a senior technician and a trainee to perform an activity.




Skill Set Table Layout FormFile Name: _____________________________________________________

Region: _______________________________________________________




Skill Set ID (15-A)

Description (60-A)

Service Time Factor (11-N)




Developing a File Creation Program for Skill Set ActivitiesProduct: Roadnet, MobileCast

When you write a program to format the skill set activities file on your host computer, you will need to format it according to UPS Logistics Technologies’ specifications, as listed below.








Skill Set ID 15 characters The unique identifier for the skill set.

Activity ID 32 characters The unique identifier for the activity.




Skill Set Activity Table Layout FormFile Name: _____________________________________________________

Region: _______________________________________________________




Skill Set ID (15-A)

Activity ID (32-A)




Developing a File Creation Program for ActivitiesProduct: Roadnet, MobileCast

When you write a program to format the activity file on your host computer, you will need to format it according to UPS Logistics Technologies’ specifications, as listed below.









Activity ID 32 characters The unique identifier for the activity.


Description 255 characters A description of the activity.

Service Time 11 digits The number of minutes it should take an employee to complete the activity.




Activity Table Layout FormFile Name: _____________________________________________________

Region: _______________________________________________________




Activity ID (32-A)

Description (255-A)

Service Time (11-N)



Importing the Daily Routes for MobileCast

Importing the Daily Routes for MobileCastProduct: MobileCast

If you are using Roadnet or Territory Planner to create your routes, it has a built-in feature that you can use to push the routes directly into MobileCast. However, if you are using another routing package to create your daily routes, you must verify that the file containing the daily routes is in a form that MobileCast can read.

MobileCast stores the routing information in various tables, but you can create one or multiple files to transfer the information. UPS Logistics Technologies recommends that if you are importing complex data, such as line items or containers for the orders, then you should create separate files for the import, not a single file. The Import module allows you to specify which file the information is located in, and where in the file it is located.

The possible contents of each table are outlined in the following charts. Route and stop data is required; the remaining tables are optional, depending on the level of detail you are tracking in MobileCast. Each chart specifies which information is required if that table is being filled. After the charts are forms you can complete to specify where the information for each table is located.

Step 1: Verify that each route has a unique ID.

Note: The route ID must be UNASSIGN or blank if the stop is an Unassigned.

All route IDs must be uppercase for importing purposes.

Step 2: Verify that information for at least the route and stops is available, as well as any other routing information you want to have tracked.

Step 3: Create ASCII files of the routing information. You can create one file with all the information, or an individual file for each table. If creating multiple files,

All of the tables that are part of the daily import are listed in this window.




make sure that all the necessary information, such as the route date and ID, is contained in each file.




Some tips to remember when creating these files:

• Create an individual record for each ID, and place all information in that record.

• The columns for each piece of information (ID, date, etc.) must be the same length in each record. Left justify information in the column, leaving blank spaces after the entry if necessary; right justify numeric information in the column, leaving blank spaces prior to the entry if necessary.


Notes: If a single file is being created with all the information, information used in more than one table, such as the Route Date and ID, only needs to be entered once for each record.

If all the dates are the same as the route date, you will only need to supply the times.

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 times as HH:MI or HH:MI:SS. The only requirement is that the year must be a four-digit number. Specify the format being used to enter these fields in the Importer module of MobileCast.

Step 4: Complete the Layout Forms at the end of this section for each table you are importing data for.

Note: When counting the starting position of the fields, remember that MobileCast starts counting at position 0.




Route TableRoute information must be imported into MobileCast for each route being tracked. The required information is bold in the table below.


Route ID 9 characters The unique ID of the route. The route ID must be uppercase.

Route Date Date The date the route will occur.

Origin ID 15 characters The unique identification of the place the route starts, such as the depot’s ID.

Origin Type 3 characters The type of location where the route starts, such as DPT for depot.

Planned Start TimeStamp The date and time when the route is expected to start; the time the driver clocks in. If the date is not supplied, it will default to the route date. If date is supplied, time must also be supplied. If MobileCast is calculating the route, planned start date must not be less than route date. Must always be specified.

Planned Complete TimeStamp The date and time when the route is expected to be finished; the time the driver clocks out. If the date is not supplied, it will default to the planned arrival date. If date is supplied, time must also be supplied. Planned complete time must be greater than planned arrival time.

(Not required if MobileCast is calculating the route.)

Planned Arrival TimeStamp The date and time when the route is expected to reach the destination. If the date is not supplied, it will default to the planned departure date. If date is supplied, time must also be supplied. Planned arrival time must be greater than planned departure time.


Planned Departure TimeStamp The date and time when the route is expected to leave the origin. If the date is not supplied, it will default to the planned start date. If date is supplied, time must also be supplied. Planned departure time must be greater than planned start time.


Planned Distance 20 digits The total number of distance the route is expected to cover.





Note: 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 times as HH:MI or HH:MI:SS. Specify the format being used to enter these fields in the Importer module of MobileCast.

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.

Description 255 characters A description of the route, such as the area it covers.

Common Carrier 15 characters The ID of the common carrier transporting the route.

Destination ID 15 characters The unique identification of the place the route ends, such as the depot’s ID.

Destination Type 3 characters The type of location where the route ends, such as DPT for depot.

Route Type 3 characters The type of product the route carries, such as flammable (FLM).


1 character A Y or N indicating whether the last stop on the route is the end of the route or not. The default is N.

Dispatcher ID 9 characters The unique identification of the dispatcher who will be tracking the route.

Reference # 15 characters The DTR number for the route. The name of this field can be changed in MobileCast.

Group 64 characters The group the route belongs to (if the routes are grouped together).

Seal 32 characters The unique number of the seal (if the route goes through customs). You can have up to three seals per route.

User Defined Fields 1, 2, and 3

30 characters each User defined fields contain information to be tracked that is not contained elsewhere in the file.

Scenario 15 characters The scenario associated with this route.

Post Route Survey Code

3 characters The code of the survey the driver needs to finish before the route can be completed.

Pre Route Survey Code

3 characters The code of the survey the driver needs to finish before the route can be started.





Route Table Layout Form File Name: ____________________________________________________

Region: _______________________________________________________


Route Date (20-A)

Route ID (Date)

Origin ID (15-A)

Origin Type (3-A)

Planned Start (Date)

Planned Complete (Date)

Planned Arrival (Date)

Planned Departure (Date)

Planned Distance (20-A)

Description (255-A)

Destination ID (15-A)

Destination Type (3-A)

Group (64-A)

Last Stop is Destination (1-A)

Dispatcher ID (9-A)

Reference Number (15-A)

Route Type (3-A)

Common Carrier (15-A)

Seal (32-A)

User Defined Field 1 (30-A)



Driver Required (1-A)

Common Carrier ID (15-A)

Scenario (15-A)

Post Route Survey Code (3-A)




Date Mask: ___________________________________________________Notes: When counting the starting position of the fields, remember that MobileCast starts

counting at position 0. Required fields are bold on the form.

Pre Route Survey Code (3-A)





Stop TableStop information must be imported for every route being tracked in MobileCast. The required fields are bold in the table below.



Route Date Date The date of the route the stop is on.

Location ID 15 characters The unique identification of the location.

Location Type 3 characters The type of location, such as DPT for depot or SIT for site.

Sequence # 5 digits The stop number for the route.

Planned Arrival TimeStamp The date and time the driver should arrive at the stop.

Planned Departure TimeStamp The date and time the driver should leave the stop.

Planned Distance 12 digits The distance between the previous stop and the current stop.

Type 2 characters 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.

Open Time Time The earliest possible time the driver can deliver the stop (military time, such as 0900, 1300).

Close Time Time The latest possible time the driver can deliver the stop (military time, such as 0900, 1300).

Additional Service Time

11 digits Any additional service time that may be needed for this stop.

Planned Pickup Size 1, 2, and 3

22 digits each (15.6) If a product is being picked up at the stop, the amount planned for pick up in size 1, size 2, and size 3. The number of characters to the right of the decimal is established in MobileCast before the import.

Planned Size 1, 2, and 3

22 digits each (15.6) If a product is being delivered to the stop, the amount planned for delivery in size 1, size 2, and size 3. The number of characters to the right of the decimal is established in MobileCast before the import.

Time Window 1, 2 Open/Close

Time The starting and ending times for the preferred delivery times at the stop (military time, such as 0900, 1300).




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 stop’s planned arrival date will be used as the time window’s 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 times as HH:MI or HH:MI:SS. 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. Specify the format being used to enter these fields in the Importer module of MobileCast.

All Unassigneds must have the Route ID as either UNASSIGN or left blank.

Instructions 255 characters Any instructions associated with the stop. If wireless communication is used, the instructions will appear to the driver on the wireless device.

Stop Survey Code 3 characters The ID of the survey to be used at the stop. The survey will appear on the wireless device for the driver to answer the questions.


30 characters each User defined fields contain information to be tracked that is not contained elsewhere in the file.





Stop Table Layout FormFile Name: ____________________________________________________Region: ______________________________________________________

Date/Time Mask: _______________________________________________Notes: When counting the starting position of the fields, remember that MobileCast starts

counting at position 0. Required fields are bold on the form.


Route Date (Date)

Route ID (9-A)

Sequence # (5-N)

Location Type (3-A)

Location ID (15-A)

Planned Arrival (Date)

Planned Departure (Date)

Planned Distance (12-A)

Type (2-N)

Instructions (255-A)

Open Time (Time)

Close Time (Time)

Additional Service Time (11-N)

Planned Pickup Size 1 (22-N)



Planned Size 1 (15-N)



Time Window 1 Open (Time)

Time Window 1 Close (Time)

Time Window 2 Open (Time)

Time Window 2 Close (Time)

Stop Survey Code (3-A)







Product Order TableOrder information needs to be imported if you are tracking routes at the order or line item level of detail in MobileCast. Required fields are bold in the table below.

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. Specify the format being used to enter these fields in the Importer module of MobileCast.



Order Number 15 characters The unique ID for the order.

Route Date Dates The date of the route.

Route ID 9 characters The unique ID for the route. The route ID must be uppercase.

Sequence # 5 digits The unique stop number where the order is being delivered.

Reference Number 32 characters The unique reference for the order.

Planned Sizes 1, 2, and 3

22 digits each (15.6) The delivery quantity measured as that size. The number of characters to the right of the decimal is established in MobileCast before the import.

Planned Pickup Sizes 1, 2, and 3

22 digits each (15.6) The pickup quantity measured as that size. The number of characters to the right of the decimal is established in MobileCast before the import.


30 characters each User fields contain information not found elsewhere in the file.

Special Instructions 255 characters Additional delivery instructions for the order.




Product Order Table Layout FormFile Name:_____________________________________________________

Region: _______________________________________________________

Date Mask: ____________________________________________________




Order Number (15-A)

Route Date (Date)

Route ID (9-A)

Sequence # (5-A)

Barcode (32-A)

Reference Number (32-A)










Special Instructions (255-A)




Order Financial Details TableOrder financial details need to be imported if you are tracking financial information about your orders in MobileCast. Required fields are bold in the table below.




Order Number 15 characters The unique identification number for the order.

Route Date Date The date of the route.


Sequence Number 5 digits The unique stop number where the order is being delivered.

Code 3 characters The financial code associated with the order’s financial detail.

Detail Amount 16 digits The amount, in dollars and cents, associated with the financial information. If negative, then a negative sign before the number is required.

Detail ID 32 characters 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 Date The date associated with the financial detail.

Detail Description 32 characters The description of the financial detail.




Order Financial Details Table Layout FormFile Name:_____________________________________________________

Region: _______________________________________________________

Date Mask: ____________________________________________________




Order Number (15-A)

Route Date (Date)

Route ID (9-A)

Sequence Number (5-A)

Code (3-A)

Detail Amount (16-A)

Detail ID (32-A)

Detail Date (Date)

Detail Description (32-A)




Line Item TableLine item information needs to be imported if you are tracking at the line item level of detail in MobileCast. Required fields are bold in the table below.

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. Specify the format being used to enter these fields in the Import module.



Line Item ID 32 characters The unique ID of the item on the order.

Order Number 15 characters The unique ID for the order.



Stop Sequence Number

5 digits The number for the stop the order is delivered to.

Description 128 characters The name or other description of the line item.

Planned Sizes 1, 2, and 3

22 digits each (15.6) The planned delivery quantity measured as that size. The number of characters to the right of the decimal is established in MobileCast before the import.

Planned Pickup Sizes 1, 2, and 3

22 digits each (15.6) The planned pickup quantity measured as that size. The number of characters to the right of the decimal is established in MobileCast before the import.


30 characters each User fields contain information not found elsewhere in the file.




Line Item Table Layout FormFile Name: ____________________________________________________

Region: _______________________________________________________

Date Mask: ___________________________________________________




Line Item ID (32-A)

Order Number (15-A)

Route Date (Date)

Route ID (9-A)

Stop Sequence # (5-A)

Description (128-A)













Route Driver TableDriver information can be imported into MobileCast or assigned manually in the Dispatcher module. All route driver fields are required.



Driver ID 15 characters The driver’s unique ID. Normally this is the driver’s social security number.



Sequence 5 digits The number 1 or 2 which refers to driver 1 or 2 on the route. The default is 1.

Owner ID 9 characters ID of the region that “owns” the driver.




Route Driver Table Layout FormFile Name: ____________________________________________________

Region: _______________________________________________________

Date Mask: ___________________________________________________




Driver ID (15-A)

Route Date (Date)

Route ID (9-A)

Sequence (5-A)

Owner ID (9-A)




Order Container Assignments TableInformation associating containers with orders can be imported into MobileCast or assigned manually in the Dispatcher module. All order container assignment fields are required, except for the container type.




Barcode 32 characters The barcode of the container.


Dropped off 1 character A T or F indicating whether the container is supposed to be dropped off at the stop.

Sequence Number 5 digits The number for the stop the container is delivered to.

Order Number 15 characters The order number the container is being associated with.

Service Type 1 character A single character whether the stop is a drop off (0) or pickup (1). The default is 0 (drop off).



Container Type 3 characters The type of container.




Order Container Table Layout FormFile Name: _____________________________________________________

Region: _______________________________________________________

Date Mask: ___________________________________________________




Barcode (32-A)

Container ID (32-A)

Dropped Off (1-A)

Sequence number (5-A)

Order Number (15-A)

Service Type (1-A)

Route Date (Date)

Route ID (9-A)

Container Type (3-A)




Line Item Container Assignments TableInformation associating line items with containers can be imported into MobileCast or assigned manually in the Dispatcher module. All line item container assignment fields are required.







Sequence Number 5 digits The number for the stop the line item is delivered to.

Line Item ID 32 characters The unique identifier for the line item.

Order Number 15 characters The order number the line item is being associated with.

Planned Size 1 22 digits (15.6) The planned delivery quantity measured as that size. The number of characters to the right of the decimal is established in MobileCast before the import.

Planned Pickup Size 1

22 digits (15.6) The planned pickup quantity measured as that size. The number of characters to the right of the decimal is established in MobileCast before the import.




Line Item Container Table Layout FormFile Name: _____________________________________________________

Region: _______________________________________________________

Date Mask: ___________________________________________________




Container ID (32-A)

Route Date (Date)

Route ID (9-A)

Sequence Number (5-A)

Line Item ID (32-A)

Order Number (15-A)






Route Equipment TableEquipment information for a route can be imported into MobileCast or assigned manually in the Dispatcher module. All route equipment fields are required.



Equipment ID 20 characters The unique ID for the piece of equipment.

Equipment Type 15 characters The type of equipment. Equipment types must be established in MobileCast before the import.



Starting Sequence # 5 digits The stop number where the equipment joins the route. If using the same equipment for the entire route, enter -1 in the Constant Text field when importing.

Ending Sequence # 5 digits The stop number where the equipment leaves the route. If using the same equipment for the entire route, enter -1 in the Constant Text field when importing.




Route Equipment Table Layout FormFile Name: _____________________________________________________

Region: _______________________________________________________

Date Mask: ____________________________________________________




Equipment ID (20-A)

Equipment Type (15-A)

Route Date (Date)

Route ID (9-A)

Starting Sequence (5-A)

Ending Sequence (5-A)

Owner ID (9-A)






Installing and Testing the Communications Package and ProgramsProduct: Roadnet, Territory Planner, FleetLoader, MobileCast

Once you purchase a communications package, you will be responsible for installing and testing it. You will also need to install and test the file creation programs you develop. When doing this, follow the guidelines below.

Step 1: Follow the manufacturer’s instructions for installing the communications package.

Step 2: Create a directory on your hard drive called \COMMUN.

Step 3: If your communication package requires you to establish parameters for the file transfer from the host computer to the Roadnet Transportation Suite and from the Roadnet Transportation Suite back to the host computer, follow the conventions outlined below.

• The destination file for orders should be called orders.r.

• The destination file for locations should be called tmpsites.

• The completed routing file should be called orders.s.

• The orders.r, tmpsites, and orders.slocation extension files should be transferred to/from a directory called \COMMUN.

• Write a script that can be used to move the orders from the host computer into Roadnet.

• Write a script that can be used to move the location extensions from the host computer into Territory Planner.

• Write a script that can be used to move the locations from the host computer into Roadnet, Territory Planner, and MobileCast.

• Write scripts that can be used to move data from Roadnet and Territory Planner back to the host computer.

• Write scripts that can be used to move daily routes information from the host computer into MobileCast.

• Write scripts that can be used to move maintenance information (SKUs, package types, containers, employees, drivers, equipment) from the host computer into Roadnet Transportation Suite.


Using the Batch Import ProcessProduct: Roadnet, Territory Planner, FleetLoader, MobileCastIf 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.Notes: Combine from archive and onboard data can not be imported using the batch

import process.

If you are using the Order Locking feature and are sending multiple waves of order files, your host system must be able to accept the same route ID.

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 examples below to create your configuration files for the various import items. 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.

Note: The examples contain all possible fields for that specific configuration file; however, you do not need to use all of the fields.

File Name: batchImpContainerAssignments.cfgREGION ID=DLOYDIMPORT TYPE=CONTAINER ASSIGNMENTLAYOUT SET=CONTAINERSLAYOUT SET IS GLOBAL=FALSEROUTE DATE=##TODAY##DATA PATH=F:\TMP\IMPORT\CALCULATE TYPE=SEQUENCETIME ZONE=8




File Name: batchImpContainers.cfgREGION ID=DLOYD

IMPORT TYPE=CONTAINER

DATA PATH=F:\TMP\IMPORT\

LAYOUT SET=MAINTENANCE

LAYOUT SET IS GLOBAL=FALSE

File Name: batchImpDailyFull.cfgREGION ID=DLOYD

IMPORT TYPE=DAILY FULL

LAYOUT SET=FULL

LAYOUT SET IS GLOBAL=FALSEROUTE DATE=##TODAY##


CALCULATE TYPE=1

TIME ZONE=8

File Name: batchImpDrivers.cfgREGION ID=DLOYD

IMPORT TYPE=DRIVER




File Name: batchImpEmployees.cfgREGION ID=DLOYD

IMPORT TYPE=EMPLOYEE




File Name: batchImpEquipment.cfgREGION ID=DLOYD

IMPORT TYPE=EQUIPMENT







File Name: batchImpPackageType.cfgREGION ID=DLOYD

IMPORT TYPE=PACKAGE TYPE




File Name: batchImpSku.cfgREGION ID=DLOYD

IMPORT TYPE=SKU




File Name: batchImpLocationExt.cfgREGION ID=DLOYD

IMPORT TYPE=LOCATION EXTENSION

SESSION DESCRIPTION=4 WEEK CYCLE

SESSION SCENARIO=DELIVERY

File Name: batchImpLocations.cfgREGION ID=DLOYD

IMPORT TYPE=LOCATION

SCENARIO=DELIVERY

UPDATE ONLY=FALSE

NO GEOCODE=TRUE

LAYOUT SET=MD LOCATIONS

File Name: batchImpOrders.cfgREGION 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.cfgREGION 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.cfgREGION ID=DLOYD

IMPORT TYPE=STATIC

ROUTE ID=UPS001

ROUTE SET ID=UPS078

ROUTE DATE=020603

File Name: batchImpStaticRouteSet.cfgREGION ID=DLOYD

IMPORT TYPE=STATIC

ROUTE SET ID=UPS078

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 no spaces.• ##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




The acceptable Calculate Types are:

•No Sequence=0

•Calculate time and distance=1

•Auto sequence=2

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

Important: If you have the environment variables set correctly for your username and password, then you do not need to use the /d parameter.

For more information on importing, see Importing into the Roadnet Transportation Suite in the Roadnet Transportation Suite Operations Guide.

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




Export Routes File Available FieldsProduct: 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. The fields that can be included in the data file are outlined in the table below.

Field Length DescriptionRoute ID 9 characters The route’s ID.


Session Date Date The session date. Use a mask to indicate the date format.

Arrival Date Date The date the route is scheduled to arrive at the stop. Use a mask to indicate the date format.

Route Start Time Time The time the route is scheduled to start. If exporting seconds, use SS as the mask.

Route Start Date Date The date the route is scheduled to start. Use a mask to indicate the date format.

Previous Location 15 characters The location ID for the previous stop.

Stop Location 15 characters The location ID for the stop.

Address Line 1 50 characters The street address for the stop.

Address Line 2 20 characters Any address information that could not fit on the first line, such as a suite number.

City 30 characters The city the stop is located in.

State 20 characters The abbreviation for the state or province the stop is located in.

Zip Code 15 characters The zip or postal code for the location.

Phone Number 20 characters The phone number for the location.

Latitude 80 digits The latitude for the stop’s location, in millionths of degrees.

Longitude 80 digits The longitude for the stop’s location, in millionths of degrees.

Open/Close Time Time The defining hours for when a delivery can be made to the location.

Time Windows Time The starting and ending times of the location’s time windows.

Location Description 30 characters The description of the location, usually the store name.

Route Equipment ID 20 characters The ID of the equipment assigned to the route.




Route Equipment Type 3 characters The type of equipment assigned to the route.

Route Equipment Owner ID 9 characters The ID of the region that owns the equipment assigned

to the route.

Route Description 30 characters The route’s description; often the area the route services.

Depot ID 15 characters The unique ID for the depot; its location ID.

Depot Type 3 characters The type for the depot, normally this is DPT.

Travel Time Time Amount of time needed to travel from the previous stop to this stop.

Distance 7 characters Distance from the previous stop to this stop.

Arrival Time TimeThe planned arrival time at the stop; formatted using a 24-hour 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 digits each The delivery quantity for each size.

Driver 1,2 ID 15 characters The unique identifier of the driver(s) assigned to the route.

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

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

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

Trip Number 2 digitsThe number the trip containing the stop is on the route. This information is only useful if route reloads is being used; therefore there is more than one trip on a route.

Fixed Service Time Time The amount of time needed at the stop without delivering any product.

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 zappear as 50. A service time of four-tenths of a minute, or 0:00.4, will appear in the export as 4.

Field Length Description




Route Complete Time Date and Time The date and time when the route is expected to be finished; the time the driver clocks out.

Route Arrival Time Date and Time The date and time when the route is expected to reach the destination.

Route Departure Time Date and Time The date and time when the route is expected to leave the origin.

Pre-Route Time Time

The time from when the driver clocks in to when he departs from the depot/origin. The driver is paid for the pre-route time; therefore, it is included when calculating the total time of the route.

Post-Route Time Time

The time from when the driver finishes all of the stops on the route to when he returns to the depot/final destination. The driver is paid for the post-route time; therefore, it is included when calculating the total time of the route.





User Upload File Available FieldsProduct: Territory Planner

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 Length DescriptionOpen 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 stop’s first time window.

TW2 Start/Stop Time The beginning and ending times for the stop’s second time window.

TW Factor 1 digit A number indicating the importance of meeting the location’s time windows. 1=least importance, 5=most important

No Helper Fixed Time The amount of time needed at the stop without delivering anything, without a helper.

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

Helper Fixed Time The amount of time needed at the stop without delivering anything, with a helper.

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

Geo Status 80 characters The method used to geocode the location.

Session Description 64 characters The description used to identify the planning session.


Day 7 characters A number indicating the stop’s delivery day. Monday=0, Tuesday=1, 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 7 digits 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 digtis each The amount delivered based on each of the size aliases.




Depot ID 15 characters The unique identifier for the route’s origin.

Depot Type 3 characters The type for the route’s origin. Normally, this will be DPT.

Equipment ID 20 characters The unique identifier for the equipment assigned to the route.

Equipment Type 15 characters The ID for the type of equipment assigned to the route.

Driver ID 15 characters The unique identifier for the driver assigned to the route.

Helper 1 character Indicates whether or not a helper has been assigned to the route.

Route ID 9 character The unique identifier for the route. All route IDs must be uppercase.





Completing Data Preparation FormsProduct: Roadnet, Territory Planner, FleetLoader, MobileCast

The final step in preparing for your Roadnet Transportation Suite installation is gathering the data that will be used to develop and track the route and loading information. This data includes information about the drivers and equipment available, the types of product you deliver, the level of detail that will be tracked, and the people who will use the system. This information must be entered before Roadnet Transportation Suite can create effective routes or load your trucks.

The following pages contain forms for each piece of information needed. Feel free to copy the forms as needed to provide all the data. A table outlining maximum field lengths and descriptions precedes each form.

Important: Once you have completed the forms in this section, keep them for your visit with your UPS Logistics Technologies consultant.

Note: Maximum field lengths and types are displayed in parentheses next to the applicable fields in each form. An N denotes a numeric field; an A denotes an alphanumeric field.




ADP DataProduct: MobileCast

If you are using ADP to process your payroll, you need to provide MobileCast with specific ADP codes. See your ADP software for these codes.

Region: _______________________________________________________

Note: MobileCast creates export files that conform to ADP’s External Paydata File Specifications.

Field Entry

Company Code

Export Path

ADP Pay Codes




Establishing Units of Measure and Equipment CapacitiesProduct: Roadnet, Territory Planner, FleetLoader, MobileCastBefore Roadnet can assign equipment to your routes to assign the proper equipment to run your routes, you need to determine your units of measure, product categories, and the capacity of your equipment. FleetLoader also needs to know some of this information to properly load your trucks. This section is designed to help you establish these important items. Once you have determined these factors, you will be ready to set up the equipment types that are used in all three products.

Determining the Unit(s) of Measure

First, you need to determine how many units of measure you will need, or how many different ways you will measure your product. You can use up to three units of measure, such as pieces, cases, cube, etc., and you do not need to use the same unit of measure for loading equipment, determining variable service time, determining bulk variable service time, or determining cost.

Determining Product Categories

In addition to establishing units of measure, you can also define up to three product categories, such as dry, refrigerated, frozen, etc. For example, a truck might deliver only refrigerated product, so when determining its capacity you would consider that product category only.

Determining SKU and other Product Information

Product information in the Roadnet Transportation Suite comprises SKUs, SKU brands, and package types. A SKU is composed of an SKU brand and a package type. The SKU brands are the actual brands of the SKUs you deliver. When you list the brands you distribute, you can be as specific as necessary, such as Caffeine-Free Diet Roadnet Cola, or more general, such as Roadnet Cola. All SKUs must have a brand ID. Package types are designed to indicate the dimensions of a particular package, such as 24 twelve-ounce cans, as well as how many units of that particular package type will fit in a bay or on a pallet in FleetLoader.

Determining Equipment and other Equipment Information

Equipment information in the Roadnet Transportation Suite is composed of bay types, equipment types, and equipment. Bay types, which are used in FleetLoader, include information on the dimensions of bays, as well as how many units of each package type will fit in that type of bay. Equipment types define the capacity of the equipment, as well as the cost to run the equipment. When creating equipment types, consider function as well as the capacity of the equipment. For instance, if you have two pieces of equipment that are the same size, and one can carry frozen food but the other cannot, you should assign two different equipment types. Individual pieces of equipment can be associated with a driver or another piece of equipment. If you are using FleetLoader to load the equipment you can have establish specific package type preferences for each bay, as well as if certain bays are “small SKU” bays or disabled bays.




Equipment Type CostsProduct: Roadnet, Territory Planner, FleetLoader, MobileCast

Company Name _________________________________________________

Equipment Type _________________________________________________

Complete the form below to determine your fixed and variable equipment type costs. Fixed equipment costs are those costs that accrue independently of the distance driven, such as lease or purchase price, insurance, depreciation, license fees etc.; these costs run on a per day, per truck basis. Per distance equipment costs can be such things as fuel, repairs, and maintenance supplies; these costs run on a per mile or kilometer basis. Keep in mind that the lists below are simply examples; you may want to exclude some and include others.

Prepare a separate form for each equipment type. Once you have determined your fixed and variable equipment type costs, complete the Data Collection: Equipment Types form for each equipment type you have established.

Fixed Equipment Type Costs Variable Equipment Type Costs

Depreciation: Fuel:

Leasing Equipment: Road Service :

License Fees: Oil:

Federal Highway Usage Tax:

Grease:

Mileage Tax Bonds: Tires and Tubes:

Fuel Permits, Fuel: Repairs and Replacement Parts:

Fire, Theft, Collision Insurance:

Repairs Done Outside Company Shop:

Liability and Property Damage Insurance:

Repairs Done Within Company Shop:

Special Equipment (tarpaulins, heaters, etc.):

Anti-Freeze:

Refrigerant:

Administrative Costs: Other:

Washing Equipment:

Painting Equipment (signs, lettering, etc.):

Other:

Total Fixed Costs: Total Variable Costs:




Bay Type InformationProduct: Roadnet, FleetLoader

Bay types are used in the beverage industry to define the types of bays available on the equipment, and are used 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. If you have purchased FleetLoader, bay types must be added before the equipment types can be added. If you haven’t purchased FleetLoader, bay types are not necessary. Use the Data Collection: Bay Types form to enter each bay type. Copy the form as many times as necessary to accommodate all of your bay types.


Bay Type ID 15 characters The bay type’s unique identification. Mandatory field.

Description 30 characters A description of the bay type.

Height Decimal Height of bay type.

Width Decimal Width of bay type.

Depth Decimal Depth of bay type.




Data Collection: Bay Types

Bay Type

Bay Type ID (15 - A):

Description (30 - A):

Height: ____________________Width:______________________ Depth: __________________

Bay Type




Bay Type




Bay Type







Employee Type InformationProduct: Roadnet, Territory Planner, FleetLoader, MobileCast

Employee types allow you to classify the types of employees in your organization. An employee type may be a driver, a dispatcher, a helper, or other. Employees can be associated with types when they are added in the Maintenance module. Use the Data Collection: Employee Type form to enter each employee type. Copy the form as many times as necessary to accommodate all of your employee types.


Employee Type 3 characters The employee type’s unique identification. Mandatory field.

Description 255 characters A description of the employee type.




Data Collection: Employee Types

Employee Type

Employee Type (3 - A):


Employee Type



Employee Type



Employee Type



Employee Type






Mix RulesProduct: FleetLoader

Mix rules allow you to tell FleetLoader not to mix different SKU brands, package types, or warehouse zones on the same bay, pallet, or layer. This information itself is optional, although both fields are required if used. The table below outlines the fields that define a mix rule.

List SKU Brands that cannot be mixed on a bay or pallet in the chart below. Copy the chart if necessary to create more mix rules. Use the brand IDs to identify the brands.

Field Max. Length

Do Not Mix with ID 15 characters

Mix Rule Type 15 characters

Mix Rule Item Type 15 characters

Target ID 15 characters

Bay/Pallet

SKU Brand Do not mix with (SKU Brand)




List Package Types that cannot be mixed on a bay or pallet in the chart below. Copy the chart if necessary to create more mix rules. Use the Package Type IDs to identify the package types.

Bay/Pallet

Package Type Do not mix with (Package Type)




List Warehouse Zones that cannot be mixed on a bay or pallet in the chart below. Copy the chart if necessary to create more mix rules. Use the Warehouse Zone IDs to identify the warehouse zones.

Bay/Pallet

Warehouse Zone Do not mix with (Warehouse Zone)




List SKU Brands that cannot be mixed on the same layer in the chart below. Copy the chart if necessary to create more mix rules. Use the brand IDs to identify the brands.

Layer

SKU Brand Do not mix with (SKU Brand)




List Package Types that cannot be mixed on the same layer in the chart below. Copy the chart if necessary to create more mix rules. Use the Package Type IDs to identify the package types.

Layer

Package Type Do not mix with (Package Type)




List Warehouse Zones that cannot be mixed on the same layer in the chart below. Copy the chart if necessary to create more mix rules. Use the Warehouse Zone IDs to identify the warehouse zones.

Layer

Warehouse Zone Do not mix with (Warehouse Zone)




Stack RulesProduct: FleetLoader

Stack rules prevent one package type from being placed on top of another when a bay is loaded. Unlike mix rules, which work both ways, stack rules invoke a one-way rule; for instance, a stack rule that says 12-ounce cans cannot be placed on top of 16-ounce bottles does not prevent 16-ounce bottles from being placed on top of 12-ounce cans. This information itself is optional, although both fields are required if used. The table below outlines the fields that define a stack rule.

The following chart can be used to gather information about stack rules. Feel free to copy the chart as needed for additional stack rules. If stack rules are used, both fields are required.

Field Max. Length

Package Type ID 15 characters

Do Not Stack on Package Type ID 15 characters

Package Type ID Do Not Stack on Package Type ID




Account Type InformationProduct: Roadnet, Territory Planner, MobileCast

Account types help you to group your locations by a common trait, such as a chain of fast-food 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. Use the Data Collection: Account Types form to enter each account type. Copy the form as many times as necessary to accommodate all of your account types.


Account Type ID 5 characters The account type’s unique identification. Mandatory field.

Description 30 characters A description of the account type.




Data Collection: Account Types

Account Type

Account Type ID (5 - A):


Account Type



Account Type



Account Type



Account Type






Track Type InformationProduct: MobileCast

Track types are a very powerful feature of MobileCast that you can use to help track costs for billing and payroll purposes. For instance, you could use track types to bill a customer based on the number of distance the route used.

Field Description

ID Unique identifier for the track type, such as RMILES for regular miles. You can use up to 5 characters.

Driver Adjustment Check if the track type is affected by the driver type. Choose the adjustment for each type of driver.

Description A name of description of the track type. You can use up to 255 characters.

Autocreate Track types can be automatically created for billed, paid, or tracked information when reports are run.

Pre-fill on Autocreate Tracked information can automatically be entered for billed, paid, and/or tracked information. For each item being filled, choose the type of information to be entered.

Classification Choose whether the track type is a rate per unit charge, a special charge, or associated with a stop type.

Calculation Method When values are calculated, are they a flat rate for the entire route (Absolute) or varying (Graduated).

Unit Label The label that will appear on the report for each unit, such as hours or miles. You can use up to 32 characters.

Constant Qty If there is a constant amount for the track type, enter the number here.

Ranges Enter the ranges and the rates at the different ranges. This is only needed if the calculation method is Graduated.

Minimum Qty If there is a minimum amount that will always be applied to the track type, enter the number here.




Data Collection: Track Type Table

Field Entry

ID (5)

Description (255)

Driver Adjustment (Y or N)

Auto Create Billed Paid Tracked

Pre-Fill Values (choose one each for planned, actual, billed, and paid)

Hours (Planned) Hours (Actual) Stops – All (Actual) Stops – Payable (Actual)

Stops – Billable (Actual)

Distance (Planned) Distance (Actual) Size 1 (Planned)

Size 1 (Actual) Size 2 (Planned) Size 2 (Actual) Size 3 (Planned)

Size 3 (Actual) Size 1 (Planned Pickup)

Size 1 (Actual Pickup) Size 2 (Planned Pickup)

Size 2 (Actual Pickup) Size 3 (Planned Pickup)

Size 3 (Actual Pickup) Size 1 (Over)

Size 2 (Over) Size 3 (Over) Size 1 (Short) Size 2 (Short)

Size 3 (Short) Size 1 (Damaged) Size 2 (Damaged) Size 3 (Damaged)

Delay Minutes Route User Defined Field 1

Route User Defined Field 2

Route User Defined Field 3

Stop User Defined Field 1



Rate Information

Classification (choose one) Rate per unit Special Charges Stop Type

Calculation Method (choose one)

Graduated Absolute

Unite Label

Constant Qty

Minimum Qty

Ranges




Area InformationProduct: Roadnet

Areas in Roadnet are simply the regions — states, provinces, etc. — through which your equipment travels. Their purpose in Roadnet is to allow you to track and report on the distance all of your equipment travels in each area. Use the Data Collection: Area form to enter each area. Copy the form as many times as necessary to accommodate all of your areas.


Area ID 3 characters The area’s unique identification. This is a mandatory field.

Description 30 characters A description of the area.




Data Collection: Areas

Area

Area ID (3 - A):


Area

Area ID (3 - A):


Area

Area ID (3 - A):


Area

Area ID (3 - A):


Area

Area ID (3 - A):





Zone InformationProduct: Roadnet

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 in the Maintenance module and then assigned to your locations if necessary. In dynamic routing, you can run what is referred to as a zone pass, in which you create routes for those locations of a particular zone(s).

Although the name zone implies that the locations 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 vehicle. Use the Data Collection: Zones form to enter each zone. Copy the form as many times as necessary to accommodate all of your zones.


Zone ID 15 characters The zone’s unique identification. This is a mandatory field.

Description 30 characters A description of the zone.




Data Collection: Zones

Zone

Zone ID (15 - A):


Zone

Zone ID (15 - A):


Zone

Zone ID (15 - A):


Zone

Zone ID (15 - A):


Zone

Zone ID (15 - A):





Scenario InformationProduct: Roadnet, Territory Planner, MobileCast

Scenarios are an easy way to apply changes to time windows and service times on a global level during a routing session. Roadnet Transportation Suite comes with one default scenario, which you can use for general routing. If you use only this scenario, you don’t have to do anything. But if you need to globally alter the service times and/or time windows for a routing session — to account for weather or holidays or for any reason — you can create a new scenario to instantly update the service times and/or time windows for every location in that routing session. The scenario will be there for you to use when you need it, but the update will occur for that session only; subsequent routing sessions will revert to your default scenario. For example, suppose time windows and service times are affected by snow days in your area. You could create a scenario that includes increased service times and altered time windows to take the snow into consideration. Use the Data Collection: Scenarios form to enter each scenario. Copy the form as many times as necessary to accommodate all of your scenarios.


Scenario ID 15 characters The scenario’s unique identification. This is a mandatory field.

Description 255 characters A description of the scenario.




Data Collection: Scenarios

Scenario

Scenario ID (15 - A):


Scenario



Scenario



Scenario



Scenario






Warehouse ZonesProduct: FleetLoader

In FleetLoader, warehouse zones let you organize your SKUs into different areas in your warehouse, and then specify the order in which the warehouse 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.


Warehouse Zone ID 15 characters The warehouse zone’s unique identification. This is a mandatory field.

Description 30 characters A description of the zone.

Sort Order Number The zones priority when loaded onto a pallet (1 is the highest).




Data Collection: Warehouse Zones

Warehouse Zone

Warehouse Zone ID (15 - A):


Sort Order:

Warehouse Zone



Sort Order:

Warehouse Zone



Sort Order:

Warehouse Zone



Sort Order:




Checklist: Completing Data Preparation FormsUse this checklist to verify that you have completed all the steps in this section.

_____Determined unit(s) of measure

_____Determined product categories

_____Determined equipment type costs

_____Completed Data Collection forms

• Equipment Types

• Employee Types

• SKU Brands

• Mix Rules

• Stack Rules

• Bay Types

• Account Types

• Areas

• Zones

• Scenarios

• Warehouse Zones



Glossary

GlossaryAADP— short for Automatic Data Processing Inc., a company that generates payroll. You can use MobileCast to generate payroll information to send to ADP.

Alias— a region-specific name for certain route data, such as the quantities carried on the route.

BBay Preferences—allow you to specify which package types you prefer to have loaded in a bay. You can define several preferences for a bay, and the order of the preferences.

Bay Type— defines the types of bays available on the trucks by determining the amount and type of product that can fit into a given bay.

Bill To—Bill To’s 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 To’s, unless you choose to allow other regions to use a Bill To when you create it.

Bulk Delivery— a delivery in which the pieces delivered contain a quantity of smaller pieces, i.e., a pallet.

Bulk Fixed Service Time— the 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 Time— the amount of time it takes to deliver one bulk item, such as a pallet.

CCanned Text Message—if you have a message that is commonly sent between the dispatcher and driver, you can enter it as a canned text message, so that it does not need to be typed each time it is sent.

Cancel Stop Code—a code used to track why the driver needs to cancel a stop.

Capacity Calculator—allows you to use the defined dimensions of the package types and bay types to calculate how much of each package type will fit in a bay. You can specify how full you want the bay to be.

Close Time—the latest possible time a location can accept a delivery.

Commodity Type—Commodity 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 Carrier—A common carrier is an outside company to which a load can be assigned, if you don’t 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.



Glossary

Container—a tote, pallet, or other item used to hold product that is being delivered. You can associate a container with an order, or line items with a container.

Cycle Weeks—the number of weeks it takes to deliver to each location extension within the planning session at least once.

DDelay Type— a reason the driver is late, such as traffic or weather. Delay types are used for reporting purposes only.

Detail Level— the amount of detail being tracked for a route (stop, order, line item). The detail level is set in the Preferences notebook.

Driver Friendly—an approach to truck loading that loads the equipment by stop, so that all products for a stop will be loaded together.

Driver Types— driver 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.

Dropped Off— if 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.

Dynamic Route— a route created based on geographic criteria as well as user-defined parameters.

EEmployee— any worker tracked through the Roadnet Transportation Suite, such as drivers, helpers, etc.

Employee Status— a way to track the availability of employees. Employees could be available, or they could be on vacation, or in training.

Employee Type— the different types of employees you have, such as drivers, helpers, etc.,

Equipment— tractors, trailers, and other vehicles used to transport product on the route.

Equipment Status— a way to track the availability of equipment. Equipment could be ready or it could be in use.

Equipment Type— the different types of equipment you have, such as tractors, trailers, or refrigerated trucks.

FFreight Classes—used to classify the type of loads in the railroad industry.

Fixed Service Time— the amount of time, independent of the quantity of product delivered, that it takes to service a location.

GGeocode— the assignment of latitude and longitude to a location.



Glossary

HHybrid (Driver First)—an approach to truck loading that loads all stops that meet a quantity threshold in a driver friendly manner. Remaining products are loaded warehouse friendly.

Hybrid (Warehouse First)—an approach to truck loading that loads all stops that meet a defined quantity threshold in a warehouse friendly manner. Remaining products are loaded driver friendly.

I

J

K

LLoad—In MobileCast, a load consists of at least a pickup location, a delivery location, and a Bill To. The load is added to one or more routes, possibly across one or more regions, or to a common carrier.

Load Admin—This refers to a level of rights for MobileCast’s load-management features that is greater than those of a normal load user. Load rights to 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 Load Customers, Customer Commodities, ST Commodity Codes, Freight Classes, Common Carriers, Load Locations, and Load Types.

Load Location—Load locations 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.

Load Type—A 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 User—A 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 Load Customers and Load Locations.

Location— anywhere 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 Extension—additional information about the location that is used to create routes in Territory Planner. Location extension information is specific to a planning session.



Glossary

Location Type— the types of places the route stops, such as a depot or a site.

MModule— an individual section of MobileCast. The modules can be run simultaneously.

MobileCast Mobile Client—the wireless device or WAP-enabled device used by a driver to communicate with MobileCast.

MobileCast server—the term used to describe the set of application services including database, event processing, etc. provided as part of the MobileCast installation.

MobileCast Database—the relational database used to store all the information used by the MobileCast application. This data is accessed by many sources, including MobileCast’s server processes and the MobileCast Office Client software.

MobileCast Office Clients—the machines running the MobileCast client software. This aftware provides the functionality used by dispatchers, customer service personnel, as well as other members of the organization who need to access the data provided by MobileCast.

MobileCast WAP ASP Application—the application that provides the communication between the MobileCast Server and the MobileCast Clients using WAP-enabled devices. It consists of a set of MicroSoft’s Active Server Pages and needs to run on a web server using MicroSoft’s IIS Web Server software. This application communicates with the MobileCast Server through the MobileCast NetTracker Service.

MobileCast WAP Notification Service—the application that “pushes” any changes or messages created by the dispatcher to Mobile Clients using WAP-enabled devices. It communicates with the MobileCast database through an ODBC connection. It communicates with the Mobile Clients by sending data via TCP/IP (port 3356) to the network provider’s WAP Gateway software.

MobileCast iTRAK Adapter Service—this service provides the communication with the iTRAK units attached to each of the WAP-enabled Mobile Clients. These are the units that provide the GPS data used to track a unit’s location. The information obtained by this service is communicated to MobileCast through the WAP ASP application.

MobileCast NetTracker Service—this service provides the communication between the MobileCast server and the WAP ASP application. It communicates with the WAP ASP application through the use of MicroSoft’s COM technology. Communication to the MobileCast server is provided by an ODBC connection to the MobileCast database.

NNode— represents the end of a particular road segment on a map.

OOpen Time—the earliest possible time a location can accept a delivery.

PPackage Type— defines the various types of packages loaded on your equipment, such as 12-ounce cans or 2-liter bottles.



Glossary

Pickup— product you previously delivered to a location that they are returning. A pickup is not the same as a load.

Planning Session—a period of time used in Territory Planner that you are creating routes for. A planning session contains all the necessary information to create routes for that period of time.

Power Unit— a self-propelled piece of equipment, such as a tractor. A power unit must be assigned to each route.

Preprocessor – a batch or command file run on a test file before the information is imported into MobileCast.

Q

RReason Codes—codes used to track why the actual quantity transferred at a stop does not match the planned quantity. You can choose the which reason codes are available for discrepancies in delivery, pickup, over, short, and damaged quantities.

Reference ID—You 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.

Region— a routing organization that has its own resources (drivers, equipment, etc.) and manages its own routes.

Remote Domicile— a location that does not have a connection to the company’s internal LAN.

Route— a single route a driver makes to visit locations.

RouteNet—UPS Logistics Technologies’ unique road mapping capabilities. RouteNet is used to generate accurate travel distances and times for a route.

Route Status— the state of the route, such as delayed or on time.

Route Type— a way to classify the type of load on the route, such as refrigerated or flammable.

Routing Session— a complete routing problem that includes all the components necessary for completing your routing in Roadnet. A routing session typically occurs once per day.

SScenario— a way to globally alter service times and time windows for a routing session based on any circumstance, such as a snow day, holiday, etc.

Seal— used if crossing borders; the unique number sealing the load.

Segment— any of the lines on a map representing the roads on which the driver will be traveling.



Glossary

Selector—a one-letter designator that can be used to designate an order for specific treatment. There are several places throughout the Roadnet Transportation Suite where you can choose orders based on an assigned selector.

Service Failure— a way to notify the customer if the route is delayed beyond a certain the 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 Pattern—a possible delivery option for a location extension in Territory Planner.

Service Pattern Set—a group of possible delivery options for a location extension in Territory Planner.

Service Time— the amount of time it takes to service a location.

Service Time Type— a way to group locations according to service time.

SKU— the most specific way to define your products by combining an SKU brand and package type.

SKU Brand— the name of any of the various products delivered.

Small SKU Bay—a bay designated to hold SKUs whose quantity falls below a user-defined threshold.

Standard Route— a route that contains specific locations in a fixed sequential order.

Static Route— a 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 Set— a collection of static routes.

STCC Code—Standard Transportation Commodity Code; used to classify the type of product carried on a load.

TTime Window— the range(s) of time during which a location prefers to receive deliveries.

Time Window Type— defines the different types of time windows that can be associated with a location.

Track Type— track 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.

Travel Time Model— a way to calculate the amount of time needed to travel specific distances. The travel time models are based on time studies.

UUndeliverable Stop Code—codes used to track why the driver was not able to deliver the stop.



Glossary

User— any person in your organization who uses the Roadnet Transportation Suite, such as a router or dispatcher to track routes and the associated data.

User Defined Field— an 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.

VVariable Service Time— the amount of time it takes to deliver one unit of product to a location.

WWarehouse Friendly—an approach to truck loading that loads the equipment so all like SKUs will be loaded together.

XYZ



Date post:	15-Mar-2020
Category:	Documents
Upload:	others
View:	0 times
Download:	0 times

version 3 - Encompass Technologiessupport.encompass8.com/Users/Support/Ads/RoadNet_RTS32... ·...

Documents