Logistics


System Maintenance Menu -> Configure System Settings -> System -> Company & Divisions -> Company Parameters -> Software Integration -> Logistics

Texada Web is a mobile application that can be used for asset management that integrates with SRM to track delivery, pickup, rental return, and service of equipment in the field or in the shop.

TEXADA WEB INTEGRATION
Uncheck this box if your firm does not use Texada Web in any of its stores or divisions.

Check this box if your firm uses the Texada Web application.


Descartes offers two levels of their Delivery/Pickup route planning system that integrate with SRM software to help your firm to schedule the delivery/pickup orders.
The On Demand (Cube Route) application is a live scheduling app, that can be used with or without its counterpart WinRoute.
Basically Delivery & Pickup Tickets are submitted from SRM to On Demand if they need to go on the following day, and future tickets can be submitted to WinRoute for scheduling to minimize trips and so that everything is delivered on time and trucks do not come back empty.
  1. On Demand (without WinRoute):
    When the On Demand application is used with SRM software without WinRoute, SRM pushes the delivery and pickup orders directly to On Demand and then the dispatcher can manually schedule and track the delivery and pickup trucks and routes.
    Tickets must be closed manually when they are changed.

    The Texada SRM programs that supply information to the On Demand system include:

    These programs send information to On Demand from the delivery and pickup tickets created by the Delivery/Pickup Ticket Sub-system, including from the Document#, the time of Delivery/Pickup, the product numbers and the weight of the items to help determine load requirements.
    The Data Upload Interval set in the On Demand configuration can be used to define the frequency that updated data is automatically transmitted.
    On Demand completes all scheduling and reporting.
    The only information that is returned to Texada SRM is an email warning when a On Demand file transfer fails.

  2. On Demand with WinRoute:
    When On Demand is used with WinRoute, then WinRoute captures the pending delivery and pickup orders with product and site specifics from SRM, and automatically builds the routes and timetable to feed the On Demand scheduler for the next day.

    Planning is done one day at a time, one day in advance.
    Each day after the Reservations for the next day are converted to the Contracts, the delivery and pickup requirements are pushed to WinRoute by manually initiating the EXPORT action on the Delivery/Pickup Dispatch so WinRoute can generate a schedule with as many deliveries and pickups as possible until the drivers are at capacity.
    WinRoute optimizes each route to get the deliveries out on time and then to pickup returning equipment in the area so that trucks are not coming back empty.

    The WinRoute optimization is based on equipment dimensions (cubes), weight, truck capacity and driver availability.
    SRM tracks the weight and dimensions of the assets, and for optimizes tomorrow’s pickups by prioritizing pickups as follows:

    1. pickups for group items which are overbooked within the next few days
    2. pickups older than 5 days
    3. all other pickups

    Once the route plan has been completed, it is published from WinRoute to On Demand and the tickets are handled the same as ones generated directly from On Demand/SRM integration or as entered directly into On Demand.
    Because WinRoute builds the most efficient On Demand dispatch schedule, the dispatcher really only needs to monitor and add any additions manually to the On Demand schedule, and to close the completed tickets in SRM.

For more information on these Descartes applications refer to www.cuberoute.com

Note: The Descartes applications are based on the delivery and pickup tickets, so the Delivery/Pickup Ticket Sub-system must be activated in the divisional Divisional Delivery/Pickup Parameters for each division that is to use On Demand and WinRoute.

ON DEMAND:
To ensure system functionality only the SCS operator can set Descartes On Demand and Descartes Winroute command pathnames.
The On Demand parameters include:
DESCARTES ON DEMAND
Uncheck this box if your firm does not utilize the On Demand third-party software.

Check this box to activated On Demand and to setup the export parameters as follows:

Note: If both Texada Web and On Demand are activated, then the delivery/pickup ticket information will NOT be sent to Texada Web as On Demand will do the scheduling, and a warning the "Texada Web Ignores Tickets" is displayed.

WEB INTERFACE URL
Enter the address of the On Demand website login page.
e.g. https://cuberoute.com/yourname/winterface/

USER NAME
Enter the name assigned to your firm by On Demand.

PASSWORD
Enter the password assigned to your firm by On Demand.

DATA UPLOAD INTERVAL
Data is not transferred immediately to On Demand.
Enter the frequency in minutes for how often the data transfer between Texada SRM and On Demand should occur. This can not be more frequent than every 10 minutes.

COMMAND PATHNAME
This is the location of the cuberoute.py script.
The default value for Windows is c:\scsbin\cuberoute.exe
The default value for Linux is /usr/local/tsi/bin/cuberoute.py
This can be over-typed as required.

SEND CLOSED TICKETS
Check this box to send all deliveries and pickups to On Demand.
Uncheck this box to only send open deliveries and pickups to On Demand.

INTERFACE VERSION
Select the interface version from the drop-down box:
  • 1- Legacy Cube route
  • 2- On Demand 2016

VIEW INTERFACE LOG
Any On Demand transfer errors can be viewed in the View Application Log window.

WINROUTE:
To ensure system functionality only the SCS operator can set Descartes On Demand and Descartes Winroute command pathnames.
The WinRoute parameters include:
DESCARTES WINROUTE
Uncheck this box if your firm does not utilize the WinRoute third-party software.

Check this box to activated WinRoute and to setup the parameters as follows:

UPLOAD URL
Enter the address of the WinRoute upload site as supplies by Descartes.

USER NAME
Enter the name assigned to your firm by WinRoute.

PASSWORD
Enter the password assigned to your firm by WinRoute.

SUBMIT CUTOFF TIME
This the cutoff time for adding new stops to WinRoute for tomorrow's schedule.

e.g. If a division is open until 5pm, the cutoff time could be set to 4:00 PM, so any attempts to schedule a delivery or pickup for the next day after 4:00 PM would not be permitted, and the user would be warned that the delivery could not be scheduled.
Deliveries that cannot be scheduled for tomorrow via WinRoute will then have to be rescheduled with the customer or scheduled manually the next day on On Demand.


COMMAND PATHNAME
This is the location of the cuberoute.py script.
The default value for Windows is c:\scsbin\cuberoute.exe
The default value for Linux is /usr/local/tsi/bin/cuberoute.py
This can be over-typed as required.

LOOKAHEAD DAYS
This value is the number of days ahead that the WinRoute export will consider for pickup optimization.
It will check this many days AFTER tomorrow, and assign top priority to any pickups for groups which are overbooked during that time period, to try to minimize the need for off-rentals.
This can be any value from 0 through 7, where 0 disables the processing.

DRIVER START TIME / DRIVER END TIME
This is the time period in the day during which deliveries can be scheduled.
e.g. 6:00 am through 6:00 PM.

These times are used during the WinRoute export to set allowed and preferred times for stops.
If a specific stop does not have a fixed time window, then the stop is scheduled so that it fits into the time window when drivers are available.
For Deliveries, the time window would be from Driver Start Time through to the Delivery window end date, and for Pickups the time window would be from Pickup window start time through to end of the driver day.
If a fixed window is set for a single day, then that is the exact window sent to WinRoute.
If the fixed window spans multiple days, then the date out must start at the window start period, and cannot go past the window end period.
Intermediate days default to the entire time when drivers are working.


IGNORE GLOBAL SITES
Because WinRoute uses the ship to information for the stop locations including longitude/latitude where available, any Global Sites that should not apply need to be listed in this Ignore Address Information for these Global Sites window.
A search button is provided to display and select from Global Sites in the Site Search window.

Global sites listed in this "ignore" window will be totally ignored for address purposes.
This is useful for customers who do NOT fill in the site address information and instead have a default global site, such as "blank" that prints SAME in the ship to address, or NS for No Site.


STOP PROPERTIES
The Custom Stop Properties window is provided to defined additional properties in the form of text that can be used to trigger custom WinRoute optimization on stops.

VIEW INTERFACE LOG
Any WinRoute transfer errors can be viewed in the View Application Log window.

LOGISTICS - General:
ADMIN EMAIL ADDRESS
Enter the email address of the person on your staff who should be notified if there are any problems with the download of information to On Demand.

PURCHASING AGENT EMAIL
Enter the company level email for your firm's Purchasing Agent that will be used to receive parts purchasing requests from Texada Web tasks, so the Purchasing Agent can then create the appropriate Purchase Orders.
This company Purchasing Agent becomes the default for all divisions unless a specific agent email address is defined for a division or store in the Divisional Logistics Settings window.

Note: The Texada Web parts purchasing requests generally come from the Mechanic's Mobile device and are transmitted to Dispatch where the emails are generated to the company or division defined Purchasing Agent Email.


DIVISION SETTINGS
Window to view and update the Logistics Division settings as outlined in Divisional Logistics Settings.

Descartes Default Stop Lengths:
A default time for scheduling each stop on the route can be defined.
This default time allowance is displayed in the Descartes - Delivery and Pickup Time window when the Delivery or Pickup tickets are created, and can be over-typed as required.
This parameter does not apply if a delivery start/end time and a pickup start/end time have been entered with the job event information on the contract.
DELIVERY LENGTH
Enter the default delivery time allowance.
A window displaying the delivery time range prior to the contract 'Time Out' is triggered when the Delivery ticket is created, and can be over-typed as required.
PICKUP LENGTH
Enter the default pickup time allowance.
A window displaying the pickup time range following the 'Off Rental Time' is triggered, when the Pickup ticket is created, and can be over-typed as required.

DEBUG LOGGING
Check this box to also include all On Demand activity messages in the Interface Log.
Uncheck this box to restrict the Interface Log to only Error messages.

Include Current WinRoute Deliveries and Pickups:
The Set Deliveries and Pickups to be Sent to WinRoute window is triggered when WinRoute is initially activated, to allow the operator to flag whether existing 'Pickups', 'Future Deliveries' and/or 'Today's Deliveries' should be exported to WinRoute application for action.

Topic Keyword: GLCN90N (5838)
Converted from CHM to HTML with chm2web Pro 2.85 (unicode)