294044 - Revision history

Middletong at 15:10, 22 October 2012

2012-10-22T15:10:36Z

← Older revision		Revision as of 17:10, 22 October 2012
Line 244:		Line 244:

	N.B. The code to assess the time windows will need to be delayed until after the carrier and service level have been extracted from the file.		N.B. The code to assess the time windows will need to be delayed until after the carrier and service level have been extracted from the file.

			=REFERENCES=

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

			\|-
			\| <center>1</center>
			\| EST-294044 NW-8NMLSD Parcel Order Time Window Derivation v1.0.doc
			\| <center>1.0</center>
			\| <center>08/12/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>14/12/11</center>
			\| <center>Draft</center>
			\| Initial version
			\| <center>PDR</center>

			\|-
			\| <center>0.1</center>
			\| <center>16/12/11</center>
			\| <center>Draft</center>
			\| Review of the initial version
			\| <center>PJH</center>

			\|-
			\| <center>1.0</center>
			\| <center>16/12/11</center>
			\| <center>Issue</center>
			\| Issued to client
			\| <center>PJH</center>

			\|-
			\| <center>1.1</center>
			\| <center>30/12/11</center>
			\| <center>Draft</center>
			\| Changes for delivery type and service level validation.
			\| <center>PDR</center>

			\|-
			\| <center>1.1</center>
			\| <center>03/01/12</center>
			\| <center>Draft</center>
			\| Review of v1.1
			\| <center>PJH</center>

			\|-
			\| <center>2.0</center>
			\| <center>03/01/12</center>
			\| <center>Issue</center>
			\| Issued to client
			\| <center>PJH</center>
			\|}


			=AUTHORISED BY=



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

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

			\|}

Middletong at 14:59, 22 October 2012

2012-10-22T14:59:24Z

← Older revision		Revision as of 16:59, 22 October 2012
Line 219:		Line 219:

	'''N.B. The associated window refers to the ‘Schedule Rules’ tab page in the new ‘Order Window Offsets’ screen as created for RIO ‘NW-8KNCK4’:'''		'''N.B. The associated window refers to the ‘Schedule Rules’ tab page in the new ‘Order Window Offsets’ screen as created for RIO ‘NW-8KNCK4’:'''

			[[Image:294044_9.png]]

			N.B. A new column called ‘Service’ will be added to the ‘Schedule Rules’ tab page to store the delivery type for the rule.

			A new cost-centre-level system parameter called ‘AUTO_SET_DELIVERY_TYPES’ will be created to control the setting of delivery types based on the ‘Schedule Rules’ for the new development, however, the system parameter will not be active for Healthcare so the delivery type will not be calculated by this new method and will not contradict the logic required for the ‘PARCEL’ transport orders.

			'''See RIO ‘291358 MS-8KNFRL 2 Order Addresses & DU & Del Type’ for further information about the new ‘Service’ column.'''

			[[Image:294044_10.png]]

			N.B. The setup for Healthcare need only contain data in the following columns:

			[[Image:294044_11.png]]

			N.B. An independent offset of 2 days will be added for transport orders uploaded on a Friday.

			A new function called ‘F_ASSESS_SCHED_RULES’ will be created in the new ‘DP_SCHEDULING_ENGINE’ database package and this function will be called from the upload processes.

			The following functions will be changed to use the new ‘F_ASSESS_SCHED_RULES’ function for the time window derivation if the system parameter ‘MAINTAIN_SCHEDULE_DATES’ is set to ‘Y’ and the cost centre is ‘HUK’ (for other cost centres the existing functionality will be used):

			*IMP.PROCESS_TI_ORDER
			*INT_XML_IN.PROCESS_ORDER_XML_IN

			N.B. The code to assess the time windows will need to be delayed until after the carrier and service level have been extracted from the file.

Middletong: /* Parcel */

2012-10-22T14:55:18Z

Parcel

← Older revision		Revision as of 16:55, 22 October 2012
Line 218:		Line 218:
	#The delivery type for parcels will always be 'Same Day' or 'Next Day'.		#The delivery type for parcels will always be 'Same Day' or 'Next Day'.

	N.B. The associated window refers to the ‘Schedule Rules’ tab page in the new ‘Order Window Offsets’ screen as created for RIO ‘NW-8KNCK4’:		'''N.B. The associated window refers to the ‘Schedule Rules’ tab page in the new ‘Order Window Offsets’ screen as created for RIO ‘NW-8KNCK4’:'''

Middletong: /* Parcel */

2012-10-22T14:52:44Z

Parcel

← Older revision		Revision as of 16:52, 22 October 2012
Line 212:		Line 212:
	#*Set the delivery date based on the window associated to the service level (e.g. rule ‘Pre 9’ would be for next day between times ‘07:00’ to ‘09:00’). This is based on the assumption that all parcels will be next day unless otherwise dated.		#*Set the delivery date based on the window associated to the service level (e.g. rule ‘Pre 9’ would be for next day between times ‘07:00’ to ‘09:00’). This is based on the assumption that all parcels will be next day unless otherwise dated.
	#If the service level is provided and a delivery date provided:		#If the service level is provided and a delivery date provided:
	--Set the delivery date based on the window associated to the service level provided.		#*Set the delivery date based on the window associated to the service level provided.
	#If the service level is not provided:		#If the service level is not provided:
	--Default to ‘S24’ (based on the new cost-centre-level system parameter called ‘OMS_DEFAULT_SERVICE_LEVEL’) and follow the rules in points ‘1’ and ‘2’ for the delivery date (e.g. ‘S24’ will be set to times between ‘09:00’ to ‘17:00’).		#*Default to ‘S24’ (based on the new cost-centre-level system parameter called ‘OMS_DEFAULT_SERVICE_LEVEL’) and follow the rules in points ‘1’ and ‘2’ for the delivery date (e.g. ‘S24’ will be set to times between ‘09:00’ to ‘17:00’).
	#Always work to the delivery date being correct but still hold the service level against the order and, in the instance where the delivery date is earlier than the system date, keep the delivery date and create the order on the relevant schedule but leave it as unscheduled (as it is likely that these will be back orders and as such will be managed manually). If the delivery date is later than the system date, keep the service level but maintain the delivery date so it will go out on the required date.		#Always work to the delivery date being correct but still hold the service level against the order and, in the instance where the delivery date is earlier than the system date, keep the delivery date and create the order on the relevant schedule but leave it as unscheduled (as it is likely that these will be back orders and as such will be managed manually). If the delivery date is later than the system date, keep the service level but maintain the delivery date so it will go out on the required date.
	#The delivery type for parcels will always be 'Same Day' or 'Next Day'.		#The delivery type for parcels will always be 'Same Day' or 'Next Day'.

	N.B. The associated window refers to the ‘Schedule Rules’ tab page in the new ‘Order Window Offsets’ screen as created for RIO ‘NW-8KNCK4’:		N.B. The associated window refers to the ‘Schedule Rules’ tab page in the new ‘Order Window Offsets’ screen as created for RIO ‘NW-8KNCK4’:

Middletong: /* Parcel */

2012-10-22T14:52:13Z

Parcel

← Older revision		Revision as of 16:52, 22 October 2012
Line 210:		Line 210:

	#If the service level is provided and a delivery date is not provided:		#If the service level is provided and a delivery date is not provided:
	--Set the delivery date based on the window associated to the service level (e.g. rule ‘Pre 9’ would be for next day between times ‘07:00’ to ‘09:00’). This is based on the assumption that all parcels will be next day unless otherwise dated.		#*Set the delivery date based on the window associated to the service level (e.g. rule ‘Pre 9’ would be for next day between times ‘07:00’ to ‘09:00’). This is based on the assumption that all parcels will be next day unless otherwise dated.
	#If the service level is provided and a delivery date provided:		#If the service level is provided and a delivery date provided:
	--Set the delivery date based on the window associated to the service level provided.		--Set the delivery date based on the window associated to the service level provided.

Middletong: /* Parcel */

2012-10-22T14:51:46Z

Parcel

← Older revision		Revision as of 16:51, 22 October 2012
Line 210:		Line 210:

	#If the service level is provided and a delivery date is not provided:		#If the service level is provided and a delivery date is not provided:
	*Set the delivery date based on the window associated to the service level (e.g. rule ‘Pre 9’ would be for next day between times ‘07:00’ to ‘09:00’). This is based on the assumption that all parcels will be next day unless otherwise dated.		--Set the delivery date based on the window associated to the service level (e.g. rule ‘Pre 9’ would be for next day between times ‘07:00’ to ‘09:00’). This is based on the assumption that all parcels will be next day unless otherwise dated.
	#If the service level is provided and a delivery date provided:		#If the service level is provided and a delivery date provided:
	*Set the delivery date based on the window associated to the service level provided.		--Set the delivery date based on the window associated to the service level provided.
	#If the service level is not provided:		#If the service level is not provided:
	*Default to ‘S24’ (based on the new cost-centre-level system parameter called ‘OMS_DEFAULT_SERVICE_LEVEL’) and follow the rules in points ‘1’ and ‘2’ for the delivery date (e.g. ‘S24’ will be set to times between ‘09:00’ to ‘17:00’).		--Default to ‘S24’ (based on the new cost-centre-level system parameter called ‘OMS_DEFAULT_SERVICE_LEVEL’) and follow the rules in points ‘1’ and ‘2’ for the delivery date (e.g. ‘S24’ will be set to times between ‘09:00’ to ‘17:00’).
	#Always work to the delivery date being correct but still hold the service level against the order and, in the instance where the delivery date is earlier than the system date, keep the delivery date and create the order on the relevant schedule but leave it as unscheduled (as it is likely that these will be back orders and as such will be managed manually). If the delivery date is later than the system date, keep the service level but maintain the delivery date so it will go out on the required date.		#Always work to the delivery date being correct but still hold the service level against the order and, in the instance where the delivery date is earlier than the system date, keep the delivery date and create the order on the relevant schedule but leave it as unscheduled (as it is likely that these will be back orders and as such will be managed manually). If the delivery date is later than the system date, keep the service level but maintain the delivery date so it will go out on the required date.
	#The delivery type for parcels will always be 'Same Day' or 'Next Day'.		#The delivery type for parcels will always be 'Same Day' or 'Next Day'.

	N.B. The associated window refers to the ‘Schedule Rules’ tab page in the new ‘Order Window Offsets’ screen as created for RIO ‘NW-8KNCK4’:		N.B. The associated window refers to the ‘Schedule Rules’ tab page in the new ‘Order Window Offsets’ screen as created for RIO ‘NW-8KNCK4’:

Middletong: /* Parcel */

2012-10-22T14:51:07Z

Parcel

← Older revision		Revision as of 16:51, 22 October 2012
Line 210:		Line 210:

	#If the service level is provided and a delivery date is not provided:		#If the service level is provided and a delivery date is not provided:
	**Set the delivery date based on the window associated to the service level (e.g. rule ‘Pre 9’ would be for next day between times ‘07:00’ to ‘09:00’). This is based on the assumption that all parcels will be next day unless otherwise dated.		*Set the delivery date based on the window associated to the service level (e.g. rule ‘Pre 9’ would be for next day between times ‘07:00’ to ‘09:00’). This is based on the assumption that all parcels will be next day unless otherwise dated.
	#If the service level is provided and a delivery date provided:		#If the service level is provided and a delivery date provided:
	**Set the delivery date based on the window associated to the service level provided.		*Set the delivery date based on the window associated to the service level provided.
	#If the service level is not provided:		#If the service level is not provided:
	**Default to ‘S24’ (based on the new cost-centre-level system parameter called ‘OMS_DEFAULT_SERVICE_LEVEL’) and follow the rules in points ‘1’ and ‘2’ for the delivery date (e.g. ‘S24’ will be set to times between ‘09:00’ to ‘17:00’).		*Default to ‘S24’ (based on the new cost-centre-level system parameter called ‘OMS_DEFAULT_SERVICE_LEVEL’) and follow the rules in points ‘1’ and ‘2’ for the delivery date (e.g. ‘S24’ will be set to times between ‘09:00’ to ‘17:00’).
	#Always work to the delivery date being correct but still hold the service level against the order and, in the instance where the delivery date is earlier than the system date, keep the delivery date and create the order on the relevant schedule but leave it as unscheduled (as it is likely that these will be back orders and as such will be managed manually). If the delivery date is later than the system date, keep the service level but maintain the delivery date so it will go out on the required date.		#Always work to the delivery date being correct but still hold the service level against the order and, in the instance where the delivery date is earlier than the system date, keep the delivery date and create the order on the relevant schedule but leave it as unscheduled (as it is likely that these will be back orders and as such will be managed manually). If the delivery date is later than the system date, keep the service level but maintain the delivery date so it will go out on the required date.
	#The delivery type for parcels will always be 'Same Day' or 'Next Day'.		#The delivery type for parcels will always be 'Same Day' or 'Next Day'.

	N.B. The associated window refers to the ‘Schedule Rules’ tab page in the new ‘Order Window Offsets’ screen as created for RIO ‘NW-8KNCK4’:		N.B. The associated window refers to the ‘Schedule Rules’ tab page in the new ‘Order Window Offsets’ screen as created for RIO ‘NW-8KNCK4’:

Middletong at 14:48, 22 October 2012

2012-10-22T14:48:30Z

← Older revision		Revision as of 16:48, 22 October 2012
Line 202:		Line 202:

	An example of the fixed routes may be seen below:		An example of the fixed routes may be seen below:

			[[Image:294044_8.png]]

			===Parcel===

			‘PARCEL’ transport orders will assess the delivery date and service level provided instead of the wholesale schedule as described below:

			#If the service level is provided and a delivery date is not provided:
			**Set the delivery date based on the window associated to the service level (e.g. rule ‘Pre 9’ would be for next day between times ‘07:00’ to ‘09:00’). This is based on the assumption that all parcels will be next day unless otherwise dated.
			#If the service level is provided and a delivery date provided:
			**Set the delivery date based on the window associated to the service level provided.
			#If the service level is not provided:
			**Default to ‘S24’ (based on the new cost-centre-level system parameter called ‘OMS_DEFAULT_SERVICE_LEVEL’) and follow the rules in points ‘1’ and ‘2’ for the delivery date (e.g. ‘S24’ will be set to times between ‘09:00’ to ‘17:00’).
			#Always work to the delivery date being correct but still hold the service level against the order and, in the instance where the delivery date is earlier than the system date, keep the delivery date and create the order on the relevant schedule but leave it as unscheduled (as it is likely that these will be back orders and as such will be managed manually). If the delivery date is later than the system date, keep the service level but maintain the delivery date so it will go out on the required date.
			#The delivery type for parcels will always be 'Same Day' or 'Next Day'.

			N.B. The associated window refers to the ‘Schedule Rules’ tab page in the new ‘Order Window Offsets’ screen as created for RIO ‘NW-8KNCK4’:

Middletong: /* Pallet */

2012-10-22T14:44:11Z

Pallet

← Older revision		Revision as of 16:44, 22 October 2012
Line 166:		Line 166:
	##If the order matches the wholesale schedule move to the next available slot, set the delivery type to ‘On Sched’, set the service level to ‘Standard’,		##If the order matches the wholesale schedule move to the next available slot, set the delivery type to ‘On Sched’, set the service level to ‘Standard’,
	##Otherwise follow the off schedule rule in point ‘4’.		##Otherwise follow the off schedule rule in point ‘4’.
	##If the delivery date is in the past:		#If the delivery date is in the past:
	##Keep the date and create the order on the relevant schedule but leave it as unscheduled as it is likely that these will be back orders and as such will be managed manually, set the delivery type to ‘Off Sched’, set the service level to ‘Standard’.		##Keep the date and create the order on the relevant schedule but leave it as unscheduled as it is likely that these will be back orders and as such will be managed manually, set the delivery type to ‘Off Sched’, set the service level to ‘Standard’.

	N.B. The wholesale schedule must not have delivery times in the past as regards the system time for it to be ‘On Sched’. For example, this will prevent a route being accepted if the delivery date is for today but time of the route is now in the past.		'''N.B. The wholesale schedule must not have delivery times in the past as regards the system time for it to be ‘On Sched’. For example, this will prevent a route being accepted if the delivery date is for today but time of the route is now in the past.'''

	The wholesale schedule may be assessed for the transport order using the new functions available in the new ‘DP_SCHEDULING_ENGINE’ database package developed for RIO ‘290935 NW-8KEMH2 Create a New Scheduling Engine’.		The wholesale schedule may be assessed for the transport order using the new functions available in the new ‘DP_SCHEDULING_ENGINE’ database package developed for RIO ‘290935 NW-8KEMH2 Create a New Scheduling Engine’.
Line 177:		Line 177:
	The following functions will be changed to use the new ‘F_ASSESS_AVAIL_ROUTE’ function for the time window derivation if the system parameter ‘MAINTAIN_SCHEDULE_DATES’ is set to ‘Y’ and the cost centre is ‘HUK’ (for other cost centres the existing functionality will be used):		The following functions will be changed to use the new ‘F_ASSESS_AVAIL_ROUTE’ function for the time window derivation if the system parameter ‘MAINTAIN_SCHEDULE_DATES’ is set to ‘Y’ and the cost centre is ‘HUK’ (for other cost centres the existing functionality will be used):

	• IMP.PROCESS_TI_ORDER		*IMP.PROCESS_TI_ORDER
	• INT_XML_IN.PROCESS_ORDER_XML_IN		*INT_XML_IN.PROCESS_ORDER_XML_IN

	N.B. The code to assess the time windows will need to be delayed until after the carrier and service level have been extracted from the file.		N.B. The code to assess the time windows will need to be delayed until after the carrier and service level have been extracted from the file.
Line 186:		Line 186:
	Equivalent functions to the following functions in the new ‘DP_SCHEDULING_ENGINE’ database will be used to find a suitable active wholesale schedule route for the unscheduled transport order being uploaded:		Equivalent functions to the following functions in the new ‘DP_SCHEDULING_ENGINE’ database will be used to find a suitable active wholesale schedule route for the unscheduled transport order being uploaded:

	• IDENTIFY_ROUTE_UNSCHEDULED		*IDENTIFY_ROUTE_UNSCHEDULED
	o Finds a direct route for the ‘from’ and ‘to’ locations or a trunk route for the ‘from’ location and ‘to’ zone.		**Finds a direct route for the ‘from’ and ‘to’ locations or a trunk route for the ‘from’ location and ‘to’ zone.
	• WEEKDAY_WS		*WEEKDAY_WS
	o Checks that the route found is active for the day of the early available (i.e. collection) date.		**Checks that the route found is active for the day of the early available (i.e. collection) date.
	• TIME_WINDOWS		*TIME_WINDOWS
	o Checks that the route found has a stop for collection and delivery within the time window required.		**Checks that the route found has a stop for collection and delivery within the time window required.
	• GET_MINUTES		*GET_MINUTES
	o Gets the number of minutes in the day for the appropriate time.		**Gets the number of minutes in the day for the appropriate time.

	N.B. Equivalent functions will need to be used because the transport order will not be present on the database tables during the upload process. These equivalent functions will need to use the dates received in the file as parameters.		N.B. Equivalent functions will need to be used because the transport order will not be present on the database tables during the upload process. These equivalent functions will need to use the dates received in the file as parameters.

Middletong: /* Pallet */

2012-10-22T14:41:03Z

Pallet

← Older revision		Revision as of 16:41, 22 October 2012
Line 154:		Line 154:
	##Set the service level to ‘Standard’.		##Set the service level to ‘Standard’.
	#If the delivery date is not provided:		#If the delivery date is not provided:
	a. Match to the next available day in the wholesale schedule,		##Match to the next available day in the wholesale schedule,
	b. Set the delivery date and time window according to the wholesale schedule,		##Set the delivery date and time window according to the wholesale schedule,
	c. Set delivery type to ‘On Sched’,		##Set delivery type to ‘On Sched’,
	d. Set the service level to ‘Standard’.		##Set the service level to ‘Standard’.
	4. If the delivery date is not provided and no match could be found in the wholesale schedule for point ‘3’:		#If the delivery date is not provided and no match could be found in the wholesale schedule for point ‘3’:
	a. Set the delivery date to 72 hours forward from the system date,		##Set the delivery date to 72 hours forward from the system date,
	b. Set the delivery time window to ‘08:00’ to ‘17:00’,		##Set the delivery time window to ‘08:00’ to ‘17:00’,
	c. Set the delivery type to ‘Off Sched’,		##Set the delivery type to ‘Off Sched’,
	d. Set the service level to ‘Standard’.		##Set the service level to ‘Standard’.
	5. If the delivery date is provided and it is for today’s system date:		#If the delivery date is provided and it is for today’s system date:
	a. If the order matches the wholesale schedule move to the next available slot, set the delivery type to ‘On Sched’, set the service level to ‘Standard’,		##If the order matches the wholesale schedule move to the next available slot, set the delivery type to ‘On Sched’, set the service level to ‘Standard’,
	b. Otherwise follow the off schedule rule in point ‘4’.		##Otherwise follow the off schedule rule in point ‘4’.
	6. If the delivery date is in the past:		##If the delivery date is in the past:
	a. Keep the date and create the order on the relevant schedule but leave it as unscheduled as it is likely that these will be back orders and as such will be managed manually, set the delivery type to ‘Off Sched’, set the service level to ‘Standard’.		##Keep the date and create the order on the relevant schedule but leave it as unscheduled as it is likely that these will be back orders and as such will be managed manually, set the delivery type to ‘Off Sched’, set the service level to ‘Standard’.

	N.B. The wholesale schedule must not have delivery times in the past as regards the system time for it to be ‘On Sched’. For example, this will prevent a route being accepted if the delivery date is for today but time of the route is now in the past.		N.B. The wholesale schedule must not have delivery times in the past as regards the system time for it to be ‘On Sched’. For example, this will prevent a route being accepted if the delivery date is for today but time of the route is now in the past.