290935 - Revision history

Middletong: /* Manual Order Scheduling */

2012-10-18T09:59:36Z

Manual Order Scheduling

← Older revision		Revision as of 11:59, 18 October 2012
Line 376:		Line 376:

	When the scheduling engine process is run for a specific order, the scheduling engine will run the processes of the scheduling engine as defined in the Scheduling Engine Control screen.		When the scheduling engine process is run for a specific order, the scheduling engine will run the processes of the scheduling engine as defined in the Scheduling Engine Control screen.

			=REFERENCES=

			{\| Border="1"
			\| <center>'''Ref No'''</center>
			\| <center>'''Document Title & ID'''</center>
			\| <center>'''Version'''</center>
			\| <center>'''Date'''</center>

			\|-
			\| <center>1</center>
			\| EST-290935 NW-8KENH2 Create a New Scheduling Engine v1.0
			\| <center>1.0</center>
			\| <center>26/08/11</center>
			\|}


			=DOCUMENT HISTORY=

			{\| Border="1"
			\| <center>'''Version'''</center>
			\| <center>'''Date'''</center>
			\| <center>'''Status'''</center>
			\| <center>'''Reason'''</center>
			\| <center>'''Initials'''</center>

			\|-
			\| <center>0.1</center>
			\| <center>04/10/11</center>
			\| <center>Draft</center>
			\| Initial version
			\| <center>SEW</center>

			\|-
			\| <center>0.2</center>
			\| <center>05/10/11</center>
			\| <center>Draft</center>
			\| Revised
			\| <center>MJC</center>

			\|-
			\| <center>1.0</center>
			\| <center>05/10/11</center>
			\| <center>Issue</center>
			\| Issued
			\| <center>MJC</center>

			\|-
			\| <center>1.1</center>
			\| <center>06/10/11</center>
			\| <center>Review</center>
			\| Reviewed and commented
			\| <center>DJM</center>

			\|-
			\| <center>1.2</center>
			\| <center>31/10/11</center>
			\| <center>Revised</center>
			\| Revised following client review.
			\| <center>SEW</center>

			\|-
			\| <center>1.4</center>
			\| <center>04/11/11</center>
			\| <center>Review</center>
			\| Review updated specification
			\| <center>PJH</center>

			\|-
			\| <center>2.0</center>
			\| <center>04/11/11</center>
			\| <center>Issue</center>
			\| Issued to client
			\| <center>PJH</center>

			\|-
			\| <center>2.1</center>
			\| <center>17/11/11</center>
			\| <center>Revised</center>
			\| Revised to add Manual Order functionality
			\| <center>SEW</center>

			\|-
			\| <center>2.1</center>
			\| <center>17/11/11</center>
			\| <center>Review</center>
			\| Review of latest version
			\| <center>PJH</center>

			\|-
			\| <center>3.0</center>
			\| <center>17/11/11</center>
			\| <center>Issued</center>
			\| Issued to client
			\| <center>PJH</center>
			\|}


			=AUTHORISED BY=



			{\| Border="1"
			\| '''''Matt Crisford'''''
			\| Development Manager
			\|

			\|-
			\| '''''Peter Greer'''''
			\| TMSCC MTS Product Manager
			\|

			\|}

Middletong: /* Manual Order Scheduling */

2012-10-18T09:50:05Z

Manual Order Scheduling

← Older revision		Revision as of 11:50, 18 October 2012
Line 367:		Line 367:
	If the scheduling engine is currently running, a message will be displayed to inform the user. The user will wait a short length of time before trying the Pack Confirmation button again. While the scheduling engine is running, it would cause possible locking issues if the process is called again for a single order.		If the scheduling engine is currently running, a message will be displayed to inform the user. The user will wait a short length of time before trying the Pack Confirmation button again. While the scheduling engine is running, it would cause possible locking issues if the process is called again for a single order.

	Where the scheduling engine is running as the order is saved, the order may be scheduled onto a trip before the Pack Confirm button has been selected.		Where the scheduling engine is running as the order is saved, the order may be scheduled onto a trip before the Pack Confirm button has been selected.
	In this instance, when the user selects ‘Pack Confirm’, the system will check the status of the order and if the order is scheduled, the system will skip the auto scheduling process.		In this instance, when the user selects ‘Pack Confirm’, the system will check the status of the order and if the order is scheduled, the system will skip the auto scheduling process.
	The order may still display a status of UNSCHEDULED on screen until the record is refreshed.		The order may still display a status of UNSCHEDULED on screen until the record is refreshed.

Middletong: /* Scheduling Engine Audit */

2012-10-18T09:49:34Z

Scheduling Engine Audit

← Older revision		Revision as of 11:49, 18 October 2012
Line 358:		Line 358:

	A new system parameter will be created called ENGINE_RUNNING. The value of the system parameter will be set to Y at the start of the scheduling engine code and will be set to N at the end.		A new system parameter will be created called ENGINE_RUNNING. The value of the system parameter will be set to Y at the start of the scheduling engine code and will be set to N at the end.

			==Manual Order Scheduling==

			When an order is manually entered via the Orders screen, the user will be able to select the Pack Confirmation button to auto schedule the single order.
			The order will be scheduled using the scheduling engine code, however the scheduling engine will only process that specific order.

			If the order fails to be scheduled onto a trip by the scheduling engine, a message will be displayed on screen to inform the user. The orders will only be auto scheduled if the scheduling engine is not currently running. This will be determined by the value of the system parameter ENGINE_RUNNING
			If the scheduling engine is currently running, a message will be displayed to inform the user. The user will wait a short length of time before trying the Pack Confirmation button again. While the scheduling engine is running, it would cause possible locking issues if the process is called again for a single order.

			Where the scheduling engine is running as the order is saved, the order may be scheduled onto a trip before the Pack Confirm button has been selected.
			In this instance, when the user selects ‘Pack Confirm’, the system will check the status of the order and if the order is scheduled, the system will skip the auto scheduling process.
			The order may still display a status of UNSCHEDULED on screen until the record is refreshed.

			The scheduling engine will be overloaded to allow the function to accept no parameters or a specific order parameter (OMS_REF). Where the scheduling engine is run without parameters, the code will process all relevant orders in the order well. (Relevant orders refer to orders which have not previously been processed by the scheduling engine and failed to schedule).

			[[Image:290935_20.png]]

			When the scheduling engine process is run for a specific order, the scheduling engine will run the processes of the scheduling engine as defined in the Scheduling Engine Control screen.

Middletong at 08:43, 18 October 2012

2012-10-18T08:43:02Z

← Older revision		Revision as of 10:43, 18 October 2012
Line 343:		Line 343:

	[[Image:290935_18.png]]		[[Image:290935_18.png]]

			In the instance where the scheduling engine fails to allocate an order/ shipment to a trip, the order/ shipment will remain in the order well unscheduled and will be manually planned or sent to Paragon for planning.

			==Scheduling Engine Audit==

			The scheduling engine is split into 5 distinct processes which are run as five distinct procedures. If a procedure has completed successfully, a record will be written to a new table SCH_SCHEDULING_AUDIT. The record will store the name of the process which has run with a status SUCCESS and the run time. If a process is run successfully, the error message field will be blank.

			Exceptions will be written in the code to deal with errors, as part of any exception a record will be added to the audit table listing the process which failed and the error message. If a process fails, the processes which are set up to run after the failed process will not run. This will prevent trips being scheduled by a process which should only run after the successful completion of the previous process.

			[[Image:290935_19.png]]


			A job will run daily to remove audit records from the table which are over 2 weeks old.

			A new system parameter will be created called ENGINE_RUNNING. The value of the system parameter will be set to Y at the start of the scheduling engine code and will be set to N at the end.

Middletong at 08:40, 18 October 2012

2012-10-18T08:40:43Z

← Older revision		Revision as of 10:40, 18 October 2012
Line 341:		Line 341:

	The diagram below shows the scheduling engine decisions when the scheduling engine has been set up to run the Mandated carriers, then the Wholesale schedule, Parcel carriers and finally 3PL carriers.		The diagram below shows the scheduling engine decisions when the scheduling engine has been set up to run the Mandated carriers, then the Wholesale schedule, Parcel carriers and finally 3PL carriers.

			[[Image:290935_18.png]]

Middletong at 08:38, 18 October 2012

2012-10-18T08:38:40Z

← Older revision		Revision as of 10:38, 18 October 2012
Line 326:		Line 326:
	Developing the scheduling engine in this way will allow users to control the order in which the procedures are run and even exclude a procedure from the scheduling engine.		Developing the scheduling engine in this way will allow users to control the order in which the procedures are run and even exclude a procedure from the scheduling engine.
	A new maintenance screen will be available to allow users to include or exclude procedures and a numeric field will allow users to control the order in which the procedures are run.		A new maintenance screen will be available to allow users to include or exclude procedures and a numeric field will allow users to control the order in which the procedures are run.

			[[Image:290935_17.png]]

			A function will be created to control who is able to set the scheduling engine properties.
			Only users who have been assigned the function will be able to edit the data. The Scheduling process and Procedure name fields will not be editable, only the included and run order can be changed.

			If a process is excluded, it will automatically be set a run order of 0.

			A flag will be created at Carrier level which will allow users to exclude carriers from the auto_scheduling. The flag will be called AUTO_SCHEDULING and any carriers with this flag not set to ‘Y’ will be ignored during carrier selection.

			Buttons will be available on the screen to stop and start the scheduling engine.

			An additional tab will also be available within this screen to view audit information for up to 2 weeks after each run.

			The diagram below shows the scheduling engine decisions when the scheduling engine has been set up to run the Mandated carriers, then the Wholesale schedule, Parcel carriers and finally 3PL carriers.

Middletong at 08:36, 18 October 2012

2012-10-18T08:36:16Z

← Older revision		Revision as of 10:36, 18 October 2012
Line 269:		Line 269:

	[[Image:290935_15.png]]		[[Image:290935_15.png]]

			The wholesale schedule will not be used for scheduling the following shipments:

			*Shipments with a mandated Carrier
			*Shipments with hazardous goods
			*Baxter Orders

			The system currently allows users to assign a trailer type to a Fixed Route and this will be used to control the capacity on each trip. The trailer type will also control which product types can be assigned to a trip.

			==Manual Intervention==

			Users will still have the ability to manually schedule shipments onto trips and to remove shipments which have been scheduled by the scheduling engine.
			A new flag will be held at shipment order level called ‘Manual Scheduling’. If a shipment is removed from a trip or manually applied to a trip, this field will be set to Y.

			Developer Notes, the system must be able to differentiate when a shipment has been scheduled by the scheduling engine or scheduled manually.

			When the scheduling engine runs, any shipments which have this flag set to Y will be ignored and not scheduled. This functionality will ensure that any manual actions carried out by a user are not overwritten by the next run of the scheduling engine.

			For shipments, the Manual Scheduling flag will be set against the shipment order and not the detail orders.

			A new status of OPEN/CLOSED will be held at shipment level and will indicate if a shipment is still available to new orders.


			==Radial Trips==

			When a shipment has been allocated to a 3PL or Parcel carrier, the system will generate trip to the delivery location without times being calculated.

			For some carriers, the scheduling engine may also be required to schedule the radial trip. A flag will be added to the Carrier Maintenance screen called ‘AUTO_PLAN_RADIALS’

			[[Image:290935_16.png]]

			When this flag is set, orders allocated to the carrier will be cross-docked at the carries hub location and the radial leg will also be planned from the hub location to the delivery point. The routes table for these carriers should include a route to the carrier hub and a route out of the carrier hub to the delivery locations.

			==Overspill Pallets==

			Multiple shipments of multiple service levels may be scheduled onto a trip. If a trip from the WHOLESALE schedule is identified as able to deliver a shipment, the shipment should be scheduled onto the trip even if this exceeds the maximum capacity of the vehicle assigned to the trip.

			If the maximum capacity of the trip has been exceeded, the system should then order the shipments by service level and delivery date, un-scheduling the shipment with the latest service level. The service level will be stored in the delivery type of each order and only orders which are the same service level can be consolidated to a shipment.

			If the shipments on the trip are the same service level, the smallest shipment which can be removed to keep the trip within the vehicle capacity should be unscheduled.

			The unscheduled shipment will be available in the order well for planning onto another trip. If a shipment is unscheduled through the overspill process, a new field on the trip table called ‘OVERSPILL_TRIP’ will store the trip id of the trunk trip the shipment was unscheduled from. If this field is populated, the system will check if the route can generate more than one trip and generate a new trip to schedule the shipment onto.

			Overspill pallets much take account of the cross docking. If a shipment is selected based on service type to be unscheduled from a trunk trip, it must first be unscheduled from the delivery trip.

			==Scheduling Engine Control==

			The scheduling engine will be created as 5 separate procedures,

			#Allocating mandated carriers
			#Allocating parcel carriers
			#Allocating to the Wholesale schedule
			#Allocating 3PL carriers
			#Baxter Trunk Scheduling

			Developing the scheduling engine in this way will allow users to control the order in which the procedures are run and even exclude a procedure from the scheduling engine.
			A new maintenance screen will be available to allow users to include or exclude procedures and a numeric field will allow users to control the order in which the procedures are run.

Middletong at 08:33, 18 October 2012

2012-10-18T08:33:12Z

← Older revision		Revision as of 10:33, 18 October 2012
Line 267:		Line 267:

	A second route will be created to deliver the radial leg; users will be able to select a new stop type called Zone which will allow routes to be created to a zone.		A second route will be created to deliver the radial leg; users will be able to select a new stop type called Zone which will allow routes to be created to a zone.

			[[Image:290935_15.png]]

Middletong at 08:29, 18 October 2012

2012-10-18T08:29:53Z

← Older revision		Revision as of 10:29, 18 October 2012
Line 249:		Line 249:
	The existing Fixed Routes functionality will be amended to provide the Wholesale Schedule.		The existing Fixed Routes functionality will be amended to provide the Wholesale Schedule.

	[[Image:~~290935_11~~.png]]		[[Image:290935_12.png]]

	Current functionality will allow users to define cut off times and Fill factors are each stop. A new stop type will be created called Cross dock, when a stop is defined as a cross dock stop, the Region will be populated with the relevant Zone. Users will be able to select a Zone from a list of values. The location id will be used to define the Cross dock location.		Current functionality will allow users to define cut off times and Fill factors are each stop. A new stop type will be created called Cross dock, when a stop is defined as a cross dock stop, the Region will be populated with the relevant Zone. Users will be able to select a Zone from a list of values. The location id will be used to define the Cross dock location.

	[[Image:~~290935_12~~.png]]		[[Image:290935_13.png]]

	Any orders which are collected at DHLCHER1 and delivered within ZONE 2 will be trunked to DHLTRAFF.		Any orders which are collected at DHLCHER1 and delivered within ZONE 2 will be trunked to DHLTRAFF.
	A second route will be created to deliver the radial leg; users will be able to select a new stop type called Zone which will allow routes to be created to a zone.		A second route will be created to deliver the radial leg; users will be able to select a new stop type called Zone which will allow routes to be created to a zone.

	[[Image:~~290935_13~~.png]]		[[Image:290935_14.png]]

	Users may create multiple stops, linking to zones and specific locations. Current functionality generates trips for every route, including all stops on the trip. Stops which are not required are removed later.		Users may create multiple stops, linking to zones and specific locations. Current functionality generates trips for every route, including all stops on the trip. Stops which are not required are removed later.

Middletong at 08:23, 18 October 2012

2012-10-18T08:23:34Z

Show changes