Auto Planning - Revision history

Anw: Categorisation of document pages

2020-08-19T07:44:42Z

Categorisation of document pages

← Older revision		Revision as of 09:44, 19 August 2020
Line 1:		Line 1:
	{{~~Warning~~}} ~~This is an incomplete guide at present~~		{{Incomplete}}


	This process is controlled by a windows service that must be running on your server - check with your OBSL Support representatives that this is the case.		This process is controlled by a windows service that must be running on your server - check with your OBSL Support representatives that this is the case.
Line 40:		Line 41:


	~~[[Category:Incomplete]]~~
	[[Category:Guides]]		[[Category:Guides]]
	[[Category:Interface]]		[[Category:Interface]]

Anw: Minor correction

2020-06-22T14:43:28Z

Minor correction

← Older revision		Revision as of 16:43, 22 June 2020
Line 12:		Line 12:

	* [[Routes]] - fixed route templates determine the structure of the trips that will be created. Templates can be created for trunk routes (for moving the order through the trunk network) and collection/delivery routes.		* [[Routes]] - fixed route templates determine the structure of the trips that will be created. Templates can be created for trunk routes (for moving the order through the trunk network) and collection/delivery routes.
	* [[Service ~~Levels~~]] - service levels are used to automatically define the collection and delivery windows, which make orders available for auto-planning.		* [[Service Level]] - service levels are used to automatically define the collection and delivery windows, which make orders available for auto-planning.
	* [[Schedule Rules]] - schedule rules determine the collection and delivery windows, which make orders available for auto-planning. The rule selected when the order is created or amended also marks the order as available or unavailable for auto-planning.		* [[Schedule Rules]] - schedule rules determine the collection and delivery windows, which make orders available for auto-planning. The rule selected when the order is created or amended also marks the order as available or unavailable for auto-planning.
	* [[Zones]] - postcode zones define where the order will start or end, which is used by the schedule rules and the fixed route templates to determine whether the order can be planned onto this route.		* [[Location Zones]] - postcode zones define where the order will start or end, which is used by the schedule rules and the fixed route templates to determine whether the order can be planned onto this route.

Anw: Initial creation

2020-06-22T14:42:33Z

Initial creation

New page

{{Warning}} This is an incomplete guide at present

This process is controlled by a windows service that must be running on your server - check with your OBSL Support representatives that this is the case.

The auto-planning process (or scheduling engine) uses configuration in the system to automatically plan orders onto fixed routes.

The process is controlled by parameters that configure the interface.
* [[System]] - The parameters that control the running of the interface.
* [[Organisation]] - The parameters that control the configuration of the interface.

The orders are planned according to the schedule rules and onto the fixed route templates created in the system, through the zones that have been defined.

* [[Routes]] - fixed route templates determine the structure of the trips that will be created. Templates can be created for trunk routes (for moving the order through the trunk network) and collection/delivery routes.
* [[Service Levels]] - service levels are used to automatically define the collection and delivery windows, which make orders available for auto-planning.
* [[Schedule Rules]] - schedule rules determine the collection and delivery windows, which make orders available for auto-planning. The rule selected when the order is created or amended also marks the order as available or unavailable for auto-planning.
* [[Zones]] - postcode zones define where the order will start or end, which is used by the schedule rules and the fixed route templates to determine whether the order can be planned onto this route.

== System Parameters ==
The parameters that control the running of the interface are found on the [[System]] maintenance screen:
* ''Trunk Load Rate Zero'' - if enabled, loading rates are not applied in planning.
* ''Auto-planning is enabled'' - If ticked, auto-planning will run and attempt to plan orders onto fixed routes.
* ''Auto-planning sleep (seconds)'' - the number of seconds in between attempts to plan. Typically this should be set to 3 minutes or more (180+).

== Organisation Parameters ==
The parameters that control the configuration of the interface are found on the [[Organisation]] maintenance screen:
* ''Auto Plan Service Level'' - {{Warning}} Redundant - now uses the schedule rule selected when creating/amending the order to determine whether an order is to be auto-planned.
* ''Auto Plan Time Ahead (hours)'' - the number of hours ahead of current time that orders are valid to be picked up by the auto-planner. For example, if set to 1 hour, and the time is 15:00 only orders from 16:00 on this date and into the future will be selected, based on the late collection date and time of the order.

== Schedule Rules ==
{{Warning}} Brief description here

== Checking Processing ==
The order import interface success or failure can be audited through the [[EDI Log]] screen.

The imports will be marked as "AUTO_PLANNING".

[[Category:Incomplete]]
[[Category:Guides]]
[[Category:Interface]]