top of page
imageedit_2_3683317702.png

How does ROUTE work?

ROUTE is Event's scheduler 

Receiving orders, consolidating, packing and  allocating them...

but how do we get to a route...?

As Events scheduling application, ROUTES main focus is on the creation of routes, allocated to carriers.

To get an order allocated to a carrier requires many different processes...

route  /ruːt/

noun

  1. 1.

    a way or course taken in getting from a starting point to a destination.

    "the scenic route from Florence to Siena"

    synonyms:way, course, road, path, avenue, direction;

What does ROUTE do for you?

What does ROUTE actually do for you?

It's simple really,.. a route in Event...

 ...is the journey, linking Stops along the way.

To complete the Route you need a vehicle and driver to deliver the products that make up the orders that the Stops have bought

ROUTE has been developed to provide the user with different levels of detail, starting with the highest level and enabling them to drill down into increasing amounts of detail as is required.

  • Route - the journey from A -B

  • Stop - a delivery / collection point on a Route

  • Shipment - a collection of orders on a Stop

  • Order - a collection of orderlines (products) on a Shipment

  • Product - the item ordered by the Stop

The philosophy is simple, that in today's world, we expect the machine to do the majority of the ground work and for the human to check it and make any finite adjustments.

Why throw every peice of detail at a user when in most cases they don't need it....

But nothing worthwhile is ever simple is it...?

Our 'machine' is called AMI...

imageedit_2_3683317702.png

...is Event's 'digital worker'. Think of AMI as just another team member with a job to do, helping to increase productivity and driving better customer interactions through automation.

Getting orders into ROUTE

So how does ROUTE actually do it for me?

From receipt of new oderlines to on a route...

What does Route actually need to do?

From receipt of new oderlines to on a route...

What does Route actually need to do?

Allocate orders to carriers for delivery.....!

Getting orders into ROUTE

To create a route in ROUTE we need to get some orders entered.

Orders are received from either:

  • Manual entry from Create Order or

  • Integration from automated web services

  • Self serve Order data import.

  • Create Order

       In Create Order you can add manual orders and then decide on how to route these

           Make no decision - Add to unallocated and route manually

           Make a decision - Select the delivery type, equipment and carrier

           Let AMI select - AMI will make the optimum decision for you. 

  • Self Serve Order file or webservices

       In these processes, orderline data is received automatically into Event and                       processed through the functionality described below... 

         

These orders are processed through to Route. Where that process includes successfully allocating a carrier to action the route created then this route will show in the ROUTE control screen.

For more information on adding orders in Create Order see here

For more information on adding orders using Events Self Serve Order import file see here

For more information on adding orders using Events webservices see here

So when an order is added to Event to be planned, it is not always the correct.

Customer changes to dates, quantities, address, manufacturing end times for example mean that and order can be a moving beast.

So orders can receive tens of changes during its life span in Event.

Updating existing orderlines

Updating orders

These are the actions that affect the orderline in Event.

ACTIVE status

 

Update an ACTIVE route

1. We will need to identify the below if they are different to the current values to remove / update

  1. Planned date - remove orderline(s) affected and replan these though AMI. Leave plan in ACTIVE, remove orderline(s) from existing route(s) and replan orderline(s) in new route(s) using AMI and recost the existing route

  2. Manufacture date - update stored value and ROUTE2 UI. 

  3. manufacture time - update stored value and ROUTE2 UI. 

  4. Address - remove orderline(s) affected and replan these though AMI. Leave plan in ACTIVE, remove orderline(s) from existing route(s) and replan orderline(s) in new route(s) using AMI and recost the existing route

  5. Estimated pallets / Qty - update with new Estimated pallets. Recalulate load fill %

  6. Pallet dims - update with changed DIMS - recalculate load fill

 

 

 

PUBLISH status

Update a PUBLISHED route: 

If the route is accepted and a driver allocated to the route we cannot UNPUBLISH. So all the below must be done without affecting CONNECT / INCAB. Too late for the change to be made by the planner. / the planner is not available to make the change.

That is a different story.

 

If a route is accepted and a driver is NOT allocated to the route we can unupublish, as this will not affect CONNECT as carrier will receive a canx notification.

It is best to unpublish route and affect it correctly where possible.

 

  1. Planned date - remove orderline(s) affected and replan these though AMI. UnPublish to ACTIVE, remove orderline(s) from existing route(s) and replan orderline(s) in new route(s) using AMI and recost the existing route

  2. Manufacture date - update stored value and ROUTE2 UI. There will be a further story to automate this later.

  3. manufacture time - update stored value and ROUTE2 UI. There will be a further story to automate this later

  4. Address - unpublish route and remove orderline(s) affected and replan these though AMI. UnPublish to ACTIVE, remove orderline(s) from existing route(s) and replan orderline(s) in new route(s) using AMI and recost the existing route

  5. Estimated pallets Qty - update with new Estimated pallets. UnPublish to ACTIVE, recalculate load fill

  6. Pallet dims - update with changed DIMS - recalculate load fill

 

 

So, remove affected orderlines for UPDATE but leave route intacked. 

If update means the route has no orderlines left on it then CANX the route. See below.

 

Unallocated / Recycle status

 

Update orderline in UNALLOCATED / Recycle

We will need to identify the below if they are different to the current values to remove:

  1. Planned date - Update with new address. Re-route if possible

  2. Manufacture date - update stored value and ROUTE2 UI

  3. manufacture time - update stored value and ROUTE2 UI

  4. Address - Update with new address. Re-route if possible

  5. Estimated pallets / Qty - update with new Estimated pallets. Re-route if possible

  6. Pallet dims - update with changed DIMS - recalculate load fill and attempt replan

During the update of orderline process in Event CONNECT, sometimes this update results in the complete removal of the Stop or the Route.

  • The removal of the Stop can result in a cancellation charge from the carrier.

  • The removal of the route can result in a cancellation charge from the carrier.

 

So what...?

The carrier will want to be able to add a cost for the cancellation.

If there is no Stop or Route the carrier cannot and the log for this cost cannot be kept accurate. 

We need to leave a 'GHOST' image of the Route / Stop behind and remove the actual order for reporcessing.

So the carrier will still have the route or Stop visible to add a cost adjustment.

Thr actual order can be removed and updated as required and replanned.

 

 

What do we do?

  1. Create a CANX status for any FULL Stop or Route that is updated and removed from CONNECT. That BIP can use in reporting.

  2. Make the Stop or Route visible to the carrier in CONNECT so they can add a cancellation cost to it .

  3. Remove the actual orderline update so it can be replanned

  4. Create a configuration to configure when this CANX process kicks in from. (for example, delivery day -1 from16:00, delivery day 0 from 00:00, 

Configuration


How do we know when a route or Stop should be left in CONNECT as a CANX?
We cannot leave any route / stop that has been canx in CONNECT as they carrier may not be entitled to a canx cost.
Therefore we need to create a configuration for the Account to decide on this time.

The logic is:
A number of hrs before the colection date and time of the Route.
If it is within this period then create the canx 'Ghost' iem so the carrier can be paid for it.

If it is outside of this period then just remove the Route / Stop. 

A carrier can be excluded from this process, so not all carrier son an Account have to be included.

Example 1:
Configuration for ALL CARRIERS on Account A is set to 12hrs before the collection date / time of the route for both Route and Stop canx.

ROUTE 12345_345R has 1 Stop and has a collection date and time of 11th October @07:00. It is in ACCEPTED status.
Route canx at 23:00 10th October.
Canx is approved as accepted and within set time

Example 2:
Configuration for ALL CARRIERS on Account A is set to 12hrs before the collection date / time of the route for both Route and Stop canx.

ROUTE 12345_345R has 1 Stop and has a collection date and time of 11th October @07:00. The Route has not been accepted at the time of the canx
Route canx at 23:00 10th October.
Canx is not approved as not inAccepted status

Example 3:
Configuration for ALL CARRIERS on Account A is set to 12hrs before the collection date / time of the route for both Route and Stop canx.

ROUTE 12345_345R has 1 Stop and has a collection date and time of 11th October @07:00. The route is in ACCEPTED status
Route canx at 14:00 10th October.
Canx is not approved as outside of time window.

Example 4:
Configuration for ALL CARRIERS on Account A is set to 12hrs before the collection date / time of the route for both Route and Stop canx.

ROUTE 12345_345R has 2 Stops and has a collection date and time of 11th October @07:00. The route is in ACCEPTED status
Route Stop 2 canx at 05:00 11th October.
Canx for Stop 2 is approved as accepted and within window. Route is recost and stays in Accepted

Where do we add this configuration?
It will be added to reCONNECT

Packing

Packing

Event has its own built in 'packing' service.

The Packing service uses the DIMS (length x width x height) and stacking characteristics of the product to find the most efficient and effective way to pack together the products that are allocated to a truck.

Like a game of Tetris, Event will give the Packing service a combination of 'units', boxes, pallets, cages with their measurements. Packing will then try all possible configurations to get to the best possible pack, usig the least possible space.

We are able to send complete, multi Stop routes as Packing identifies the need for Stop separation and Stop sequence, providing a 'map' of how the vehicle should be loaded.

Then we have a map of loading including any information on overloading so we can calculate volume fill and provide the user with an accurate 'Route load fill %

When do we repack?

  • Creating a new route

  • Adding to an existing route

  • Moving orders between routes

  • Moving orders between Unallocated / Recycle

  • Splitting routes

  • Changing the carrier allocated to a route

imageedit_2_3683317702.png

Events 3D Load viewer and 3D Augmented Reality load viewer will be available later this year...

Consolidation

Consolidation

When we have received a set of orderlines through one of our integration services we look to consolidate these to existing shipments using the below matches:

  • same carrier

  • same delivery type (groupage, FTL, parcel, Fleet)

  • same Mode

  • same collection date, 

  • same delivery date, 

  • same source / Account, 

  • same destination, 

  • ROUTE status = ACTIVE

Where we can consolidate, the orderlines are added and the shipment pushed back througupdated including all the totals on the Route.

Route Assist rules

Route Assit rules

So we now have a shipment, a 'to' and 'from' address and a size. How do we know how to route it?

Sounds simple right?

Route Assist is a rule engine designed to enable an Account to dictate how to route out their orders.

When a shipment needs to be routed, Route Assist rules tell AMI how to do it.

They can be extremely complex for parcel services, based around weights, DIMS, carrier services, incoterms and 3rd party rules to very simple cheapest cost.

Route Assist can be used to actually select a predefined carrier, equipment and service by working through a number of different rules to actually just letting AMI define cheapest answer for example, from all the options available to you.

As your available options change over time, letting the system define the optimum can be more cost effective that having to remember to keep updating your rules.

As an example the simplest rule being: 

  • Any shipment for delivery in the UK, that is between 0 - 99999 m3, please route out on the cheapest delivery option.

Here AMI will make the decision if parcel, groupage, LTL, FTL, which carrier and the equipment to use.

Please find more detailed information on Route Assist rules here

Examples are easier to understand

Lets use an example to explain the process:

Rules: Always try and keep the same order number together. 

We start with a Route that has an equipment type allocated that can take upto 10 plts

The current orders on the route are as below:

Stop    Shipment           Order         Orderline   Qty   

1          000000004        123456      1.00           5 plts

1          000000004        123456      2.00           2 plts

1          000000004        123499      1.00           2 plts

1          000000004        123499      2.00           1 plts

 

The below NEW orderlines are then received for consolidation from webservice, Order import file or manually. 

At 1st glance we would consolidate these new orderlines to those on the route above. We cannot add to the above shipment as it would pack to 12 plts and this will exceed 

So we will keep the order numbers together, 

Stop    Shipment          Order          Orderline    Qty   

??        ??                      123456       3.00            1 plts

??        ??                      123456       4.00            1 plts

 

So, Route will now look like this:

Stop   Shipment           Order         Orderline    Qty   

1         000000005        123456      1.00            5 plts

1         000000005        123456      2.00            2 plts

1         000000005        123456      3.00            1 plts

1         000000005        123456      4.00            1 plts

 

Order 123499 will be 'split from the shipment 00000004.

We will look for consolidation again through matching.

If none can be found we will give it a new shipment number and push it through ROUTE ASSIST Rules for routing.

 

RULE: Always keep same order numbers together

 

What if the additional quantity exceeds the equipment capacity?

 

If we get the below situation.

After adding the additional 'matching' orderlines

Stop   Shipment           Order         Orderline    Qty   

1         000000005        123456      1.00            5 plts

1         000000005        123456      2.00            2 plts

1         000000005        123456      3.00            1 plts

1         000000005        123456      4.00            1 plts

1         000000005        123456      4.00            2 plts

 

The total is now 11 plts and the equipment currently on the route can only hold 10 plts.

In this situation for 'Semi assist routing' we will consolidate the additional orderlines on the same Route, leave the equipment as it is and inform the user that the Route is 'over capacity' using ROUTES 'Route load fill %'.

The user can then decide how to re-route.

What if there are 2 stops on a route and the additional consolidation is over capacity?

 

We add and put the route to over capacity. The Route load fill % will inform the user. We do not re-route based on capacity in 'Semi assist routing'

 

What if adding more orderlines to a shipment means it is cheaper ?

 

A shipment may be defined as GROUPAGE to start with. Through additional 'matching' consolidation, the shipment may become so big that it is actually cheaper to move it to a different delivery type, for example a 7.5t Rigid vehicle. Each time a shipment gets consolidated it is pushed back through the ROUTE ASSIST rules to always find 

I have attached rules added.

Where does the ROUTE equipment come from anyway?

 

When a shipment goes through Route Assist, depending on the rules, it provides ROUTE with directions on how the user wants the shipment to route. For example the delivery type.

Based on the volume we will identify an equipment type with capacity, select a carrier with this equipment type and allocate to the route.

Types of routing

Manual routing

ROUTE has the full ability for a user, at any time in the process to manually override any automated decision. To take back control and change things.

Please find more detailed information on manual routing here

AMI - Semi assisted routing

Everything but multi Stop routing...

AMI will process orders received and route them out as instructed with a end game of creating a Route with a carrier allocated.

This function will not combine Stops to create effective and efficient routes.

Semi-assisted routing is a 'helping hand' for users that prefer to control their scheduling.

It will build PARCEL and GROUPAGE, creating multi Stop routes for the carrier you defined, either through Route Assist rules or manually and to the capacity of the equipment set. (default is a Curtain 13.6 trailer)

LTL or FTL will be routed out as individual Stops per route for the carrier you defined in Route Assist rules or manually and to the capacity you defined when selecting the carrier or by the size of the Stop.

Semi assisted routing will ignore ​Route load fill  requiring a manual split or reallocation of an over capacity route

Fully autonomous, multi stop, multi account routing.

Using AMI, we have developed our own in-house multi carrier heuristics to seamlessly and quickly route your orders for you.

coming Q3 2019...

AMI - fully autonomous routing

Show me more

Select the screen you want to learn more about:

The Event Team

designed by humans : built with machines

bottom of page