top of page

The Oasis

Integration simplified...

How does Event deal with The OASIS..?

How does Event deal with updates to order and how do these changes affect the logistics process?

How is an order updated through the different Event order status?

Active Status

Update an ACTIVE route

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. Estimated product / Qty - update with new Estimated pallets. Recalulate load fill %

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

PUBLISH Status

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

  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. 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. Estimated product Qty - update with new Estimated pallets. UnPublish to ACTIVE, recalculate load fill

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

UNALLOCATED Status

Update orderline in UNALLOCATED

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

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

  3. Manufacture date - update stored value and ROUTE2 UI

  4. manufacture time - update stored value and ROUTE2 UI

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

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

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

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

RECYCLE Status

Update orderline in RECYCLE

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

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

  3. Manufacture date - update stored value and ROUTE2 UI

  4. manufacture time - update stored value and ROUTE2 UI

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

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

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

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

ACCEPTED Status 

During the update of orderline process in Event CONNECT, sometimes this update results in the complete removal of the Stop or the Route. (the above publish status)

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.

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

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

We 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.

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

  1. Planned date - unpublish route / Stop affected. Leave a 'ghost' in CONNECT and remove the original order back to ROUTE2 to be re-routed.

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

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

  4. Address - unpublish route / Stop affected. Leave a 'ghost' in CONNECT and remove the original order back to ROUTE2 to be re-routed.

  5. Estimated pallets Qty - update with new Estimated pallets. Leave in ACCEPTED

  6. Estimated product Qty - update with new Estimated pallets. Leave in ACCEPTED

  7. Pallet dims - update with changed DIMS - Leave in ACCEPTED

The functionality for this is configurable and can be found in the reCONNECT product configuration.

The configuration allows, by carrier to set the hrs before collection that is considered a chargeable cancellation:

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.

Contact details for OASIS support

The Event Team

designed by humans : built with machines

bottom of page