Fixed Routes - Revision history

Anw: Minor correction

2025-04-16T09:05:38Z

Minor correction

← Older revision		Revision as of 11:05, 16 April 2025
Line 52:		Line 52:
	The "Max Trips" number defines the number of each particular route that can be generated, in the example below three trips could be generated provided that there were sufficient orders available. Routes can be allocated to individual days or all through the week.		The "Max Trips" number defines the number of each particular route that can be generated, in the example below three trips could be generated provided that there were sufficient orders available. Routes can be allocated to individual days or all through the week.

	The "Route End Time" defines the expected end time of the trips ~~crated~~ from the fixed route. For most scheduling purposes, this is for information only. The exception is fixed drop scheduling, which uses this to set the return to base time for the CL stop.		The "Route End Time" defines the expected end time of the trips created from the fixed route. For most scheduling purposes, this is for information only. The exception is fixed drop scheduling, which uses this to set the return to base time for the CL stop.

	The route should be set for the days of the week for which it is active and the "Shift Code" can be applied to each day and is stamped against the trip created.		The route should be set for the days of the week for which it is active and the "Shift Code" can be applied to each day and is stamped against the trip created.

Anw: Patch 48 SCR-CTMS-03557646-21 Non-working Days

2025-04-14T09:05:20Z

Patch 48 SCR-CTMS-03557646-21 Non-working Days

← Older revision		Revision as of 11:05, 14 April 2025
Line 60:		Line 60:
	The "Auto-Scheduling" check box determines whether this fixed route should be used by the Scheduling Engine process, or whether this route is used solely by the manual fixed route execution process.		The "Auto-Scheduling" check box determines whether this fixed route should be used by the Scheduling Engine process, or whether this route is used solely by the manual fixed route execution process.

			The route can be identified as a Bank Holiday route ONLY through the check box provided.

Anw: Patch 48 - Added route end time

2025-04-08T14:04:54Z

Patch 48 - Added route end time

← Older revision		Revision as of 16:04, 8 April 2025
Line 51:		Line 51:

	The "Max Trips" number defines the number of each particular route that can be generated, in the example below three trips could be generated provided that there were sufficient orders available. Routes can be allocated to individual days or all through the week.		The "Max Trips" number defines the number of each particular route that can be generated, in the example below three trips could be generated provided that there were sufficient orders available. Routes can be allocated to individual days or all through the week.

			The "Route End Time" defines the expected end time of the trips crated from the fixed route. For most scheduling purposes, this is for information only. The exception is fixed drop scheduling, which uses this to set the return to base time for the CL stop.

	The route should be set for the days of the week for which it is active and the "Shift Code" can be applied to each day and is stamped against the trip created.		The route should be set for the days of the week for which it is active and the "Shift Code" can be applied to each day and is stamped against the trip created.
Line 57:		Line 59:

	The "Auto-Scheduling" check box determines whether this fixed route should be used by the Scheduling Engine process, or whether this route is used solely by the manual fixed route execution process.		The "Auto-Scheduling" check box determines whether this fixed route should be used by the Scheduling Engine process, or whether this route is used solely by the manual fixed route execution process.

Anw: Updated

2024-09-05T07:34:12Z

Updated

← Older revision		Revision as of 09:34, 5 September 2024
Line 11:		Line 11:
	<center>[[Image:fixed_routes_1.png\|600px]]</center>		<center>[[Image:fixed_routes_1.png\|600px]]</center>

			The screen automatically displays active routes for all depots your user has access to on all days, for fixed routes that can be manually run.

			{{Note}}The list of fixed routes will be automatically restricted to your user's accessible depot, set through [[Access Control]]. Your user will either show all depots, or will be restricted to a single depot.

			You can change what is displayed on this screen through the criteria at the top of the screen

			* ''Depot'' - you can select the depot from the drop-down list to filter the list of fixed routes shown.
			* ''Day'' - you can select the active day from the drop-down list - all routes that are active on at least that day are shown
			* ''Show Inactive Routes'' - you can check this box to show just routes that are currently inactive, so that you can re-enable them if required.
			* ''Auto Scheduled'' - you can check this box to show Auto-scheduled fixed routes, as opposed to manual run fixed routes.
			* ''Van Fleet'' - you can check this box to show just Van Fleet fixed routes.
			* ''Carrier Trunk'' - you can check this box to show just Carrier Trunk fixed routes.

			From here, you have the following buttons:

			* '''New''' - create a new fixed route - see [[Fixed Routes#New Route\|New Route]] below.
			* '''Edit''' - click an existing route in the list and then this button and you can edit an existing route - this will allow you to change fixed routes similarly as to when creating a new route.
			* '''Delete''' - click an existing route in the list and then this button and you can delete an existing route - you will be prompted for confirmation.
			* '''Close''' - close this form.

	=== New Route ===		=== New Route ===

Anw: Added

2024-06-07T06:51:18Z

Added

← Older revision		Revision as of 08:51, 7 June 2024
Line 191:		Line 191:

	You are able to filter this data in several ways using the different drop down boxes and free text boxes available. You could filter the data by fixed route ID (using the "Route" drop down box), the schedule, the log type, and perhaps most usefully of all, the messages between boxes. This is where you can enter the numbers that were given to you when you ran your fixed routes. After fixed routes execution has finished you are prompted with a note that details the messages between numbers that relate to that run of fixed routes. You should note those numbers and enter them into the messages between boxes within this screen. Whichever filter method you go for, you will be able to action it by pressing on the '''?''' button.		You are able to filter this data in several ways using the different drop down boxes and free text boxes available. You could filter the data by fixed route ID (using the "Route" drop down box), the schedule, the log type, and perhaps most usefully of all, the messages between boxes. This is where you can enter the numbers that were given to you when you ran your fixed routes. After fixed routes execution has finished you are prompted with a note that details the messages between numbers that relate to that run of fixed routes. You should note those numbers and enter them into the messages between boxes within this screen. Whichever filter method you go for, you will be able to action it by pressing on the '''?''' button.


			==Further Configuration==
			The following system parameters affect this functionality:
			{\| class="wikitable" border="1"
			\|- bgcolor="silver"
			!Parameter !! Description !! Level
			\|-
			\| RTE_LOG_DEL_DAYS \|\| Number of days that Fixed Routes log messages should be kept for \|\| SYSTEM
			\|-
			\| RTE_MAINT_RDC_ALL_USAGE \|\| Allow the values for the fixed route locations to include an RDC location when the depot has not been assigned to a customer or a customer group (Y/N) \|\| SYSTEM
			\|-
			\| RTE_ORDERS_ASC_OR_DESC \|\| Should orders be orders in Ascending or Descending order (ASC or DESC) \|\| SYSTEM
			\|-
			\| RTE_PLAN_BY_REGION \|\| Allow Fixed Routes to plan by Postal Region or Planning Region, values are PL and PO. \|\| SYSTEM
			\|-
			\| RTE_PRIORITISE_URG_LATE_ORDS \|\| Controls whether urgent and late orders are to prioritised in the Fixed Route process. \|\| SYSTEM
			\|-
			\| RTE_REGION_AND_ZONE \|\| Will fixed routes crossdock by planning region and location zone? (Y/N) \|\| SYSTEM
			\|-
			\| RTE_SCHED_OFFSET_HRS \|\| Fixed Routes Schedule Offset in hours \|\| SYSTEM
			\|-
			\| RTE_SEMI_FIXED_CAPACITY \|\| Determines whether capacity is checked by FILL or TRAILER capacity. \|\| SYSTEM
			\|-
			\| RTE_SEMI_FIXED_FUNCTION \|\| Should trips go to SEMI_FIXED if they are not optimum, Y or N. \|\| SYSTEM
			\|-
			\| RTE_STOPOVER_MINS \|\| Default number of minutes for a stopover for the network route. \|\| COST_CENTRE
			\|-
			\| RTE_TRIPS_DEL_DAYS \|\| Fixed Route RTE Trips in status DELETED on schedules older than this value will be deleted \|\| SYSTEM
			\|-
			\| RTE_TRIPS_FIN_STATUS \|\| Fixed Routes final status \|\| SYSTEM
			\|-
			\| RTE_TRIPS_TO_ACCEPTED \|\| Defines if ACCEPTED or PLANNED Trips are deleted in Rev TI, if yes then ACCEPTED, otherwise PLANNED - Y or N \|\| SYSTEM
			\|-
			\| RTE_USE_CROSSDOCK \|\| Should Fixed Routes allow crossdocks to be used. \|\| SYSTEM
			\|-
			\| SCH_SCHEDULE_ADV_DAYS \|\| Determines how many days in advance to generate fixed routes Schedule \|\| SYSTEM
			\|}

	<noinclude>		<noinclude>

Anw: Minor formatting change

2024-06-04T11:27:58Z

Minor formatting change

Anw: Added cross-reference to associated imports

2024-06-04T09:14:48Z

Added cross-reference to associated imports

← Older revision		Revision as of 11:14, 4 June 2024
Line 77:		Line 77:

	{{Note}} This function is only effective with the automatic fixed routes execution.		{{Note}} This function is only effective with the automatic fixed routes execution.


			=== Imports ===
			Fixed routes and stops may be imported through [[Imports]]:
			* [[Imports_Details#FIXED_ROUTE\|FIXED_ROUTE]]

Anw: Minor correction

2024-05-25T18:37:39Z

Minor correction

← Older revision		Revision as of 20:37, 25 May 2024
Line 80:		Line 80:

	== Fixed Routes Execution - Advanced Creation ==		== Fixed Routes Execution - Advanced Creation ==
	{{Note}} This is a bespoke process - this is not normally required for scheduling orders onto fixed routes - the normal process is covered in section "Order Scheduling" below.		{{Note}} This is a bespoke process - this is not normally required for scheduling orders onto fixed routes - the normal process is covered in section [[#Fixed Routes Execution - Order Scheduling Engine\|Fixed Routes Execution - Order Scheduling Engine]] below.

Anw: Minor correction

2024-05-25T18:34:26Z

Minor correction

← Older revision		Revision as of 20:34, 25 May 2024
Line 36:		Line 36:

	Each Route can be specified for any or all days of the week.		Each Route can be specified for any or all days of the week.

			The "Auto-Scheduling" check box determines whether this fixed route should be used by the Scheduling Engine process, or whether this route is used solely by the manual fixed route execution process.

Anw: Merged from training document

2024-05-25T18:23:38Z

Merged from training document

Show changes

← Older revision		Revision as of 13:27, 4 June 2024
Line 41:		Line 41:

	=== Route Stops ===		=== Route Stops ===
	Stops can be added, deleted or inserted and also moved up and down within the route if desired using the available U (up) D (down) buttons.		Stops can be added, deleted or inserted and also moved up and down within the route if desired using the available '''U''' (up) and '''D''' (down) buttons.

	<center>[[Image:fixed_routes_stops.png\|800px]]</center>		<center>[[Image:fixed_routes_stops.png\|800px]]</center>
Line 137:		Line 137:
	The aim of fixed routes is to speed up the planning process by anticipating trips that occur on a regular basis. These trips can be created automatically. Fixed routes are set up in the maintenance screen with certain criteria (such as delivery / collection times and trailer fill) which need to be adhered to before the fix route will be used.		The aim of fixed routes is to speed up the planning process by anticipating trips that occur on a regular basis. These trips can be created automatically. Fixed routes are set up in the maintenance screen with certain criteria (such as delivery / collection times and trailer fill) which need to be adhered to before the fix route will be used.

	C-TMS will create a trip from the fixed route and then proceed to find an order that matches its fixed route's criteria. If it ~~doesn’t~~ match the criteria it will disband the trip, if it does then C-TMS will keep the trip and it can be viewed from within the trip manipulation screen.		C-TMS will create a trip from the fixed route and then proceed to find an order that matches its fixed route's criteria. If it doesn't match the criteria it will disband the trip, if it does then C-TMS will keep the trip and it can be viewed from within the trip manipulation screen.

	Fixed routes Execution will generally be ran after all the orders for a day's plan have been created.		Fixed routes Execution will generally be ran after all the orders for a day's plan have been created.
Line 170:		Line 170:

	=== Viewing Generated Fixed Route Trips/Orders ===		=== Viewing Generated Fixed Route Trips/Orders ===
	Staying within the fixed routes execution screen you will notice that there are two further tabs, the middle of which is labelled ~~‘Route~~ Trips/~~Orders’~~. The ~~‘Route~~ Trips/~~Orders’~~ tab allows you to view the fixed routes that have successfully had trips created from them. It will detail information regarding the orders that have been placed onto those fixed routes, the C-TMS trip ID number, the collection and delivery locations and the RPE (roll pallet equivalent). The "Route Trips/Orders" tabs are displayed.		Staying within the fixed routes execution screen you will notice that there are two further tabs, the middle of which is labelled 'Route Trips/Orders'. The 'Route Trips/Orders' tab allows you to view the fixed routes that have successfully had trips created from them. It will detail information regarding the orders that have been placed onto those fixed routes, the C-TMS trip ID number, the collection and delivery locations and the RPE (roll pallet equivalent). The "Route Trips/Orders" tabs are displayed.

	<center>[[Image:fixed_routes_execution_trips.png\|800px]]</center>		<center>[[Image:fixed_routes_execution_trips.png\|800px]]</center>
Line 178:		Line 178:
	You then see the details of all the trips that have been created from a particular fixed route.		You then see the details of all the trips that have been created from a particular fixed route.

	The bottom box containing the ~~‘Order ID’~~ etc. is showing the order details pertaining to the highlighted trip in the top box.		The bottom box containing the 'Order ID' etc. is showing the order details pertaining to the highlighted trip in the top box.

	The other filter option is the schedule, which can be activated in the same way as you activate the route filter. This will detail the trips that have been created within the schedule provided.		The other filter option is the schedule, which can be activated in the same way as you activate the route filter. This will detail the trips that have been created within the schedule provided.