Trip Manipulation - Revision history

Anw: test

2024-05-17T06:22:23Z

test

← Older revision		Revision as of 08:22, 17 May 2024
Line 98:		Line 98:
	[[Category:C-TMS User Guide\|BB-120]]		[[Category:C-TMS User Guide\|BB-120]]
	[[Category:C-TMS_Key_Functionality\|140]]		[[Category:C-TMS_Key_Functionality\|140]]
	[[Category:TEST\|~~140~~]]		[[Category:TEST\|B-120]]

Anw: test

2024-05-14T12:54:08Z

test

← Older revision		Revision as of 14:54, 14 May 2024
Line 98:		Line 98:
	[[Category:C-TMS User Guide\|BB-120]]		[[Category:C-TMS User Guide\|BB-120]]
	[[Category:C-TMS_Key_Functionality\|140]]		[[Category:C-TMS_Key_Functionality\|140]]
	[[Category:TEST]]		[[Category:TEST\|140]]

Anw: test

2024-05-14T12:50:10Z

test

← Older revision		Revision as of 14:50, 14 May 2024
Line 98:		Line 98:
	[[Category:C-TMS User Guide\|BB-120]]		[[Category:C-TMS User Guide\|BB-120]]
	[[Category:C-TMS_Key_Functionality\|140]]		[[Category:C-TMS_Key_Functionality\|140]]
			[[Category:TEST]]

Middletong at 14:39, 9 August 2011

2011-08-09T14:39:30Z

← Older revision		Revision as of 16:39, 9 August 2011
Line 7:		Line 7:
	The following is an example of the Trip Manipulation Screen:		The following is an example of the Trip Manipulation Screen:

	[[Image:trip_1.jpg]]		<center>[[Image:trip_1.jpg]]</center>

	The Postal Region, Planning Region, Location, Weight, RPE and Volume filters allow a user to restrict which Unscheduled [[Orders]] they are able to see, this helps to speed up the planning process. The number of Unscheduled [[Orders]] displayed has also been increased to speed up the creation of manual [[trip]]s.		The Postal Region, Planning Region, Location, Weight, RPE and Volume filters allow a user to restrict which Unscheduled [[Orders]] they are able to see, this helps to speed up the planning process. The number of Unscheduled [[Orders]] displayed has also been increased to speed up the creation of manual [[trip]]s.

Anw at 12:28, 11 May 2011

2011-05-11T12:28:12Z

← Older revision		Revision as of 14:28, 11 May 2011
Line 97:		Line 97:
	[[Category:C-TMS Modules\|B-120]]		[[Category:C-TMS Modules\|B-120]]
	[[Category:C-TMS User Guide\|BB-120]]		[[Category:C-TMS User Guide\|BB-120]]
			[[Category:C-TMS_Key_Functionality\|140]]

Anw at 11:24, 11 May 2011

2011-05-11T11:24:41Z

← Older revision		Revision as of 13:24, 11 May 2011
Line 94:		Line 94:
	<li>[[249378]] (PA-7DDFH9) Check and enhance EFX data export </li>		<li>[[249378]] (PA-7DDFH9) Check and enhance EFX data export </li>
	</ul>		</ul>
			[[Category:Trip Management\|120]]
			[[Category:C-TMS Modules\|B-120]]
			[[Category:C-TMS User Guide\|BB-120]]

Admin at 11:52, 12 November 2010

2010-11-12T11:52:27Z

Middletong at 14:16, 21 October 2010

2010-10-21T14:16:41Z

← Older revision		Revision as of 16:16, 21 October 2010
Line 7:		Line 7:
	The following is an example of the Trip Manipulation Screen:		The following is an example of the Trip Manipulation Screen:

	~~<center>~~[[Image:trip_1.jpg]]~~</center>~~		[[Image:trip_1.jpg]]

	The Postal Region, Planning Region, Location, Weight, RPE and Volume filters allow a user to restrict which Unscheduled [[Orders]] they are able to see, this helps to speed up the planning process. The number of Unscheduled [[Orders]] displayed has also been increased to speed up the creation of manual [[trip]]s.		The Postal Region, Planning Region, Location, Weight, RPE and Volume filters allow a user to restrict which Unscheduled [[Orders]] they are able to see, this helps to speed up the planning process. The number of Unscheduled [[Orders]] displayed has also been increased to speed up the creation of manual [[trip]]s.

Crisfordm at 14:45, 11 May 2009

2009-05-11T14:45:39Z

← Older revision		Revision as of 16:45, 11 May 2009
Line 9:		Line 9:
	<center>[[Image:trip_1.jpg]]</center>		<center>[[Image:trip_1.jpg]]</center>

	The Postal Region, Planning Region, Location, Weight, RPE and Volume filters allow a user to restrict which Unscheduled [[Orders]] they are able to see, this helps to speed up the planning process. The number of Unscheduled [[Orders]] displayed has also been increased to speed up the creation of manual ~~trips~~.		The Postal Region, Planning Region, Location, Weight, RPE and Volume filters allow a user to restrict which Unscheduled [[Orders]] they are able to see, this helps to speed up the planning process. The number of Unscheduled [[Orders]] displayed has also been increased to speed up the creation of manual [[trip]]s.

	Please note that distance and fuel units, displayed throughout [[MTS]], but specifically on the Trip Manipulation form, are now controlled within [[MTS]] via 2 system parameters: GEO_DT_DISTANCE_UNITS and RES_DT_FUEL_UNITS. These are initially setup to only be edited by the OBS Support team. They will default to 'Miles' and 'Litres' respectively if the operation does not request alternative units such as Kilometres and Gallons.		Please note that distance and fuel units, displayed throughout [[MTS]], but specifically on the Trip Manipulation form, are now controlled within [[MTS]] via 2 system parameters: GEO_DT_DISTANCE_UNITS and RES_DT_FUEL_UNITS. These are initially setup to only be edited by the OBS Support team. They will default to 'Miles' and 'Litres' respectively if the operation does not request alternative units such as Kilometres and Gallons.
Line 17:		Line 17:
	== Trip Filter ==		== Trip Filter ==

	The Trip Filter allows a user to control which ~~Trips~~ they can see.		The Trip Filter allows a user to control which [[Trip]]s they can see.

	The key functions are:		The key functions are:
Line 23:		Line 23:
	=== Apply Order to Trip ===		=== Apply Order to Trip ===

	Allows any Unscheduled [[Orders]] on that Schedule to be applied to a new or existing Trip. By default an Order will be automatically applied to what the system believes to be the most appropriate stops, it is also possible to apply an Order to a specific pair of stops to reduce the need for manual manipulation. When multiple orders are being applied to a trip, the system will try to minimize the number of stops required by selecting the largest trailer type available.		Allows any Unscheduled [[Orders]] on that Schedule to be applied to a new or existing [[Trip]]. By default an Order will be automatically applied to what the system believes to be the most appropriate stops, it is also possible to apply an Order to a specific pair of stops to reduce the need for manual manipulation. When multiple orders are being applied to a [[trip]], the system will try to minimize the number of stops required by selecting the largest trailer type available.

	=== X-dock Order ===		=== X-dock Order ===

	It is possible to [[crossdock]] an Order via one of many locations, for example an Order going from Loc1 to Loc2 can be x-docked via Loc3. An order can be x-docked on a single Trip or multiple ~~Trips~~. An Order can be x-docked in the [[TRIPSUM]] and [[ORDERS]] forms.		It is possible to [[crossdock]] an Order via one of many locations, for example an Order going from Loc1 to Loc2 can be x-docked via Loc3. An order can be x-docked on a single [[Trip]] or multiple [[Trip]]s. An Order can be x-docked in the [[TRIPSUM]] and [[ORDERS]] forms.

	=== Validate Trip ===		=== Validate Trip ===

	Performs validation checks on the selected Trip to ensure that the trip is valid and feasible. If the trip breaks any validation rules these will be reported back to the user.		Performs validation checks on the selected [[Trip]] to ensure that the [[trip]] is valid and feasible. If the [[trip]] breaks any validation rules these will be reported back to the user.

	These checks include:		These checks include:
	<ul>		<ul>
	<li>Ensure that the trip has at least 1 load and unload activity and these activities are in the correct order.</li>		<li>Ensure that the [[trip]] has at least 1 load and unload activity and these activities are in the correct order.</li>
	<li>Ensures that the trip complies with driving regulations such as Drivers Breaks.</li>		<li>Ensures that the [[trip]] complies with driving regulations such as Drivers Breaks.</li>
	<li>Checks whether the Trip will deliver within the delivery windows of the [[Orders]].</li>		<li>Checks whether the [[Trip]] will deliver within the delivery windows of the [[Orders]].</li>
	<li>Ensures that a valid Trailer Type is assigned to the Trip. If a Trailer has been ‘fixed’ onto a Trip (see Fixed Routes for more details) it will not be overwritten.</li>		<li>Ensures that a valid Trailer Type is assigned to the [[Trip]]. If a Trailer has been ‘fixed’ onto a [[Trip]] (see Fixed Routes for more details) it will not be overwritten.</li>
	</ul>		</ul>

	=== Recalculate Distance and Time ===		=== Recalculate Distance and Time ===

	Allows the times on a Trip to be recalculated, wait times will be optimised and Drivers Breaks included (this can include an overnight stopover), all departure times will be made unique. This may result in Delivery windows being breached, however, these failures will be reported during Trip Validation.		Allows the times on a [[Trip]] to be recalculated, wait times will be optimised and Drivers Breaks included (this can include an overnight stopover), all departure times will be made unique. This may result in Delivery windows being breached, however, these failures will be reported during [[Trip]] Validation.

	=== Set Trip Status ===		=== Set Trip Status ===

	Trip Statuses include ACCEPTED, TENDERED, DELETED, EN-ROUTE. This function allows the status to be changed to another status, there are restrictions to control the changes that are permitted. For instance it may not be valid to change a trip from EN-ROUTE to DELETED.		Trip Statuses include ACCEPTED, TENDERED, DELETED, EN-ROUTE. This function allows the status to be changed to another status, there are restrictions to control the changes that are permitted. For instance it may not be valid to change a [[trip]] from EN-ROUTE to DELETED.

	=== Split Trip ===		=== Split Trip ===

	Allows a trip to be split into 2 separate trips. Upon splitting a new trip will be created and Stops below the split point will be placed on the new Trip. Each Trip will then be validated to ensure that it has the relevant SU and CL activities.		Allows a [[trip]] to be split into 2 separate trips. Upon splitting a new trip will be created and Stops below the split point will be placed on the new Trip. Each Trip will then be validated to ensure that it has the relevant SU and CL activities.

	=== Merge Trip ===		=== Merge Trip ===

	Two ~~trips~~ can be selected and merged together to make 1 trip. Two configurable system options are now possible for this function. Either duplicate Stops will be removed and stops will be combined together where possible, or Stops will be appended onto the end of the resulting trip. Upon completion the first trip will remain and the second trip will be deleted.		Two [[trip]]s can be selected and merged together to make 1 trip. Two configurable system options are now possible for this function. Either duplicate Stops will be removed and stops will be combined together where possible, or Stops will be appended onto the end of the resulting trip. Upon completion the first trip will remain and the second trip will be deleted.

	=== Delete Trip ===		=== Delete Trip ===

	If a trip is no longer required it can be deleted, the trip will remain on the Database with a status of deleted, the stops will be removed and the [[Orders]] set back to Unscheduled.		If a [[trip]] is no longer required it can be deleted, the trip will remain on the Database with a status of deleted, the stops will be removed and the [[Orders]] set back to Unscheduled.

	=== Insert Stop ===		=== Insert Stop ===

	Allows a new stop to be manually added to a Trip after the selected Stop, an Activity Type, Location and Trailer Type are required.		Allows a new stop to be manually added to a [[Trip]] after the selected Stop, an Activity Type, Location and Trailer Type are required.

	=== Append Stop ===		=== Append Stop ===

	Allows a stop to be appended to the end of a Trip, an Activity Type, Location and Trailer Type are required.		Allows a stop to be appended to the end of a [[Trip]], an Activity Type, Location and Trailer Type are required.

	=== Delete Stop ===		=== Delete Stop ===

	Allows a stop to be deleted from a Trip, any [[Orders]] at that Stop will be Unscheduled.		Allows a stop to be deleted from a [[Trip]], any [[Orders]] at that Stop will be Unscheduled.

	=== Costs and Revenue ===		=== Costs and Revenue ===

	Cost and Revenue details are displayed for a Trip, costs can also be allocated to a Trip (see the Accounting documentation for more details as to how these costs are generated).		Cost and Revenue details are displayed for a [[Trip]], costs can also be allocated to a Trip (see the Accounting documentation for more details as to how these costs are generated).

	=== Assign Resources ===		=== Assign Resources ===

	Within the Trip Manipulation form it is possible to assign resources to a Trip. A Carrier can be selected from a list of valid Carriers. It is then possible to populate a Driver (and optionally 2 crew members), Vehicle and Trailer Id. Depending on the set up of the carrier (i.e. Fleet or Haulier) these values will either be selected from a list or entered as free text. If a Haulier is being used the details of all resources will not be stored in [[MTS]] so they will need to be entered manually. If selecting from a list the list will be restricted to those resources that are available to the Carrier that is assigned to the Trip.		Within the [[Trip]] Manipulation form it is possible to assign resources to a Trip. A Carrier can be selected from a list of valid Carriers. It is then possible to populate a Driver (and optionally 2 crew members), Vehicle and Trailer Id. Depending on the set up of the carrier (i.e. Fleet or Haulier) these values will either be selected from a list or entered as free text. If a Haulier is being used the details of all resources will not be stored in [[MTS]] so they will need to be entered manually. If selecting from a list the list will be restricted to those resources that are available to the Carrier that is assigned to the Trip.

	It is also possible to manually assign a Trailer Type to a Trip. If a trailer is manually assigned to a stop it is also assigned to all subsequent stops and is ‘Fixed’. The fact that it is fixed means it will not overwritten by validate trip and gives the user the ability to force a trip to use a particular trailer. A large number of Trips that are created from Fixed Routes will have a trailer ‘fixed’. A trailer can be ‘un-fixed’ by removing it from all stops, once this has happened validate trip will again try and assign the best fit trailer.		It is also possible to manually assign a Trailer Type to a Trip. If a trailer is manually assigned to a stop it is also assigned to all subsequent stops and is ‘Fixed’. The fact that it is fixed means it will not overwritten by validate trip and gives the user the ability to force a trip to use a particular trailer. A large number of Trips that are created from Fixed Routes will have a trailer ‘fixed’. A trailer can be ‘un-fixed’ by removing it from all stops, once this has happened validate trip will again try and assign the best fit trailer.

Crisfordm at 14:42, 11 May 2009

2009-05-11T14:42:54Z

← Older revision		Revision as of 16:42, 11 May 2009
Line 1:		Line 1:
	The Trip Manipulation module provides users with a view of all the ~~trips~~ on a particular schedule. The unscheduled [[Orders]] on the Schedule chosen by the user are also displayed. ~~Trips~~ can be created directly within [[MTS]] Host from unscheduled [[Orders]] or can be created in a external scheduler and then transferred back to [[MTS]] Host (see the [[Interfaces]] for further details).		The Trip Manipulation module provides users with a view of all the [[trip]]s on a particular schedule. The unscheduled [[Orders]] on the Schedule chosen by the user are also displayed. [[Trip]]s can be created directly within [[MTS]] Host from unscheduled [[Orders]] or can be created in a external scheduler and then transferred back to [[MTS]] Host (see the [[Interfaces]] for further details).

	All key information relating to a trip is displayed on the Trip Manipulation form and a mechanism is provided to link back to the [[Orders]] that are delivered on the Trip. A number of manipulation functions can be accessed through Trip Manipulation and these are discussed below.		All key information relating to a [[trip]] is displayed on the Trip Manipulation form and a mechanism is provided to link back to the [[Orders]] that are delivered on the Trip. A number of manipulation functions can be accessed through Trip Manipulation and these are discussed below.

	A Trip Planning screen is also available in [[MTS]] and displays mostly the same information as is displayed in Trip Manipulation but shows more [[Orders]] to assist users in the planning process.		A Trip Planning screen is also available in [[MTS]] and displays mostly the same information as is displayed in Trip Manipulation but shows more [[Orders]] to assist users in the planning process.

← Older revision		Revision as of 08:22, 17 May 2024
Line 98:		Line 98:
	[[Category:C-TMS User Guide\|BB-120]]		[[Category:C-TMS User Guide\|BB-120]]
	[[Category:C-TMS_Key_Functionality\|140]]		[[Category:C-TMS_Key_Functionality\|140]]
	[[Category:TEST\|~~140~~]]		[[Category:TEST\|B-120]]

← Older revision		Revision as of 14:28, 11 May 2011
Line 97:		Line 97:
	[[Category:C-TMS Modules\|B-120]]		[[Category:C-TMS Modules\|B-120]]
	[[Category:C-TMS User Guide\|BB-120]]		[[Category:C-TMS User Guide\|BB-120]]
			[[Category:C-TMS_Key_Functionality\|140]]

← Older revision		Revision as of 13:52, 12 November 2010
Line 1:		Line 1:
	The Trip Manipulation module provides users with a view of all the [[trip]]s on a particular schedule. The unscheduled [[Orders]] on the Schedule chosen by the user are also displayed. [[Trip]]s can be created directly within [[~~MTS~~]] Host from unscheduled [[Orders]] or can be created in a external scheduler and then transferred back to [[~~MTS~~]] Host (see the [[Interfaces]] for further details).		The Trip Manipulation module provides users with a view of all the [[trip]]s on a particular schedule. The unscheduled [[Orders]] on the Schedule chosen by the user are also displayed. [[Trip]]s can be created directly within [[C-TMS]] Host from unscheduled [[Orders]] or can be created in a external scheduler and then transferred back to [[C-TMS]] Host (see the [[Interfaces]] for further details).

	All key information relating to a [[trip]] is displayed on the Trip Manipulation form and a mechanism is provided to link back to the [[Orders]] that are delivered on the Trip. A number of manipulation functions can be accessed through Trip Manipulation and these are discussed below.		All key information relating to a [[trip]] is displayed on the Trip Manipulation form and a mechanism is provided to link back to the [[Orders]] that are delivered on the Trip. A number of manipulation functions can be accessed through Trip Manipulation and these are discussed below.

	A Trip Planning screen is also available in [[~~MTS~~]] and displays mostly the same information as is displayed in Trip Manipulation but shows more [[Orders]] to assist users in the planning process.		A Trip Planning screen is also available in [[C-TMS]] and displays mostly the same information as is displayed in Trip Manipulation but shows more [[Orders]] to assist users in the planning process.

	The following is an example of the Trip Manipulation Screen:		The following is an example of the Trip Manipulation Screen:
Line 11:		Line 11:
	The Postal Region, Planning Region, Location, Weight, RPE and Volume filters allow a user to restrict which Unscheduled [[Orders]] they are able to see, this helps to speed up the planning process. The number of Unscheduled [[Orders]] displayed has also been increased to speed up the creation of manual [[trip]]s.		The Postal Region, Planning Region, Location, Weight, RPE and Volume filters allow a user to restrict which Unscheduled [[Orders]] they are able to see, this helps to speed up the planning process. The number of Unscheduled [[Orders]] displayed has also been increased to speed up the creation of manual [[trip]]s.

	Please note that distance and fuel units, displayed throughout [[~~MTS~~]], but specifically on the Trip Manipulation form, are now controlled within [[~~MTS~~]] via 2 system parameters: GEO_DT_DISTANCE_UNITS and RES_DT_FUEL_UNITS. These are initially setup to only be edited by the OBS Support team. They will default to 'Miles' and 'Litres' respectively if the operation does not request alternative units such as Kilometres and Gallons.		Please note that distance and fuel units, displayed throughout [[C-TMS]], but specifically on the Trip Manipulation form, are now controlled within [[C-TMS]] via 2 system parameters: GEO_DT_DISTANCE_UNITS and RES_DT_FUEL_UNITS. These are initially setup to only be edited by the OBS Support team. They will default to 'Miles' and 'Litres' respectively if the operation does not request alternative units such as Kilometres and Gallons.

	It is assumed that any external system to [[~~MTS~~]] will be configured by to pass data using the correct units.		It is assumed that any external system to [[C-TMS]] will be configured by to pass data using the correct units.

	== Trip Filter ==		== Trip Filter ==
Line 79:		Line 79:
	=== Assign Resources ===		=== Assign Resources ===

	Within the [[Trip]] Manipulation form it is possible to assign resources to a Trip. A Carrier can be selected from a list of valid Carriers. It is then possible to populate a Driver (and optionally 2 crew members), Vehicle and Trailer Id. Depending on the set up of the carrier (i.e. Fleet or Haulier) these values will either be selected from a list or entered as free text. If a Haulier is being used the details of all resources will not be stored in [[~~MTS~~]] so they will need to be entered manually. If selecting from a list the list will be restricted to those resources that are available to the Carrier that is assigned to the Trip.		Within the [[Trip]] Manipulation form it is possible to assign resources to a Trip. A Carrier can be selected from a list of valid Carriers. It is then possible to populate a Driver (and optionally 2 crew members), Vehicle and Trailer Id. Depending on the set up of the carrier (i.e. Fleet or Haulier) these values will either be selected from a list or entered as free text. If a Haulier is being used the details of all resources will not be stored in [[C-TMS]] so they will need to be entered manually. If selecting from a list the list will be restricted to those resources that are available to the Carrier that is assigned to the Trip.

	It is also possible to manually assign a Trailer Type to a Trip. If a trailer is manually assigned to a stop it is also assigned to all subsequent stops and is ‘Fixed’. The fact that it is fixed means it will not overwritten by validate trip and gives the user the ability to force a trip to use a particular trailer. A large number of Trips that are created from Fixed Routes will have a trailer ‘fixed’. A trailer can be ‘un-fixed’ by removing it from all stops, once this has happened validate trip will again try and assign the best fit trailer.		It is also possible to manually assign a Trailer Type to a Trip. If a trailer is manually assigned to a stop it is also assigned to all subsequent stops and is ‘Fixed’. The fact that it is fixed means it will not overwritten by validate trip and gives the user the ability to force a trip to use a particular trailer. A large number of Trips that are created from Fixed Routes will have a trailer ‘fixed’. A trailer can be ‘un-fixed’ by removing it from all stops, once this has happened validate trip will again try and assign the best fit trailer.