292729 - Revision history

Middletong at 12:16, 1 October 2012

2012-10-01T12:16:35Z

← Older revision		Revision as of 14:16, 1 October 2012
Line 530:		Line 530:

	The tasks will be processed in the same way that MICROLISE tasks are currently processed. There will be no changes made to any of the screens.		The tasks will be processed in the same way that MICROLISE tasks are currently processed. There will be no changes made to any of the screens.


			=REFERENCES=

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

			\|-
			\| <center>1</center>
			\| EST-292729 BS-8MCHDK Enable Communication with Smartphone v1.0
			\| <center>1</center>
			\| <center>21/10/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>02/11/11</center>
			\| <center>Draft</center>
			\| Initial version
			\| <center>SEW</center>

			\|-
			\| <center>0.2</center>
			\| <center>03/11/11</center>
			\| <center>Draft</center>
			\| Reviewed
			\| <center>MJC</center>

			\|-
			\| <center>1.0</center>
			\| <center>03/11/11</center>
			\| <center>Issued</center>
			\| Issued
			\| <center>MJC</center>
			\|}

			=AUTHORISED BY=



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

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

			\|}

Middletong at 11:14, 1 October 2012

2012-10-01T11:14:22Z

← Older revision		Revision as of 13:14, 1 October 2012
Line 512:		Line 512:

	[[Image:292729_7.png]]		[[Image:292729_7.png]]

			The Weighbridge ticket will be displayed in the Orders screen under the Order Reference tab.

			A new tag will be added to the <ORDER_DETAIL> for the Actual weight. The data received in this field will be written back to the existing Order line Actual Weight field.

			[[Image:292729_8.png]]

			For the Microlise inbound flow a new level of data has been created called TASKS. Task information can relate to a trip or a stop on a trip. The task information is displayed on the Trip debrief screen.

			[[Image:292729_9.png]]

			The trip task functionality will be added to the Smartphone after the orders on the stop have been specified and before the end of the stop, an example of where the tasks are sent in the MICROLISE extract.

			[[Image:292729_10.png]]

			Two task records will be received in the DEL message for GROSS WEIGHT and TARE WEIGHT. The records will be visible in the trip debrief screen.

			The tasks will be processed in the same way that MICROLISE tasks are currently processed. There will be no changes made to any of the screens.

Middletong at 11:09, 1 October 2012

2012-10-01T11:09:19Z

← Older revision		Revision as of 13:09, 1 October 2012
Line 510:		Line 510:

	<U>An example of Sub References received from Tokairo</u>		<U>An example of Sub References received from Tokairo</u>

			[[Image:292729_7.png]]

Middletong at 11:04, 1 October 2012

2012-10-01T11:04:14Z

← Older revision		Revision as of 13:04, 1 October 2012
Line 420:		Line 420:

	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>

	<OBS_XML>		<OBS_XML>

	<EVENT>		<EVENT>

	<EVENT_HEADER>		<EVENT_HEADER>

	<EVENT_PROCESSED>N</EVENT_PROCESSED>		<EVENT_PROCESSED>N</EVENT_PROCESSED>

	<EVENT_SOURCE_TYPE>TRAK</EVENT_SOURCE_TYPE>		<EVENT_SOURCE_TYPE>TRAK</EVENT_SOURCE_TYPE>

	<EVENT_SOURCE_NAME>SMA</EVENT_SOURCE_NAME>		<EVENT_SOURCE_NAME>SMA</EVENT_SOURCE_NAME>

	<EVENT_DATE>2011-10-05T13:02:58</EVENT_DATE>		<EVENT_DATE>2011-10-05T13:02:58</EVENT_DATE>

	<EVENT_TYPE>ARR</EVENT_TYPE>		<EVENT_TYPE>ARR</EVENT_TYPE>

	<EVENT_ACTION>C</EVENT_ACTION>		<EVENT_ACTION>C</EVENT_ACTION>

	</EVENT_HEADER>		</EVENT_HEADER>

	<EVENT_DETAIL>		<EVENT_DETAIL>

	<TRIP_HEADER>		<TRIP_HEADER>

	<TRIP_IDENTIFIER>T</TRIP_IDENTIFIER>		<TRIP_IDENTIFIER>T</TRIP_IDENTIFIER>

	<TRIP_TRANSACTION_DATE>2011-10-05T13:02:58</TRIP_TRANSACTION_DATE>		<TRIP_TRANSACTION_DATE>2011-10-05T13:02:58</TRIP_TRANSACTION_DATE>

	<TRIP_ID>MAN-01090037</TRIP_ID>		<TRIP_ID>MAN-01090037</TRIP_ID>

	</TRIP_HEADER>		</TRIP_HEADER>

	<TRIP_DETAIL>		<TRIP_DETAIL>

	<TRACKING>Y</TRACKING>		<TRACKING>Y</TRACKING>

	<DRIVER>ALAN BALL</DRIVER>		<DRIVER>ALAN BALL</DRIVER>

	<TRACTOR>PO60HNG</TRACTOR>		<TRACTOR>PO60HNG</TRACTOR>

	<TRIP_TRAILER_ID>11702x</TRIP_TRAILER_ID>		<TRIP_TRAILER_ID>11702x</TRIP_TRAILER_ID>

	</TRIP_DETAIL>		</TRIP_DETAIL>

	<STOPS>		<STOPS>

	<STOP>		<STOP>

	<STOP_HEADER>		<STOP_HEADER>

	<STOP_IDENTIFIER>S</STOP_IDENTIFIER>		<STOP_IDENTIFIER>S</STOP_IDENTIFIER>

	<STOP_SEQ>2</STOP_SEQ>		<STOP_SEQ>2</STOP_SEQ>

	</STOP_HEADER>		</STOP_HEADER>

	<STOP_DETAIL>		<STOP_DETAIL>

	<STOP_LOCATION_ID>CHEZANT</STOP_LOCATION_ID>		<STOP_LOCATION_ID>CHEZANT</STOP_LOCATION_ID>

	<STOP_ACTUAL_ARRIVAL_DATE>2011-10-05T13:02:58</STOP_ACTUAL_ARRIVAL_DATE>		<STOP_ACTUAL_ARRIVAL_DATE>2011-10-05T13:02:58</STOP_ACTUAL_ARRIVAL_DATE>

	</STOP_DETAIL>		</STOP_DETAIL>

	</STOP>		</STOP>

	</STOPS>		</STOPS>

	</EVENT_DETAIL>		</EVENT_DETAIL>

	</EVENT>		</EVENT>

	</OBS_XML>		</OBS_XML>

	Based on the value of a new Cost centre parameter SMA_RESOURCE_UPDATE, information received in the inbound flow will over write any resource information currently stored against the trip in C-TMS.		Based on the value of a new Cost centre parameter SMA_RESOURCE_UPDATE, information received in the inbound flow will over write any resource information currently stored against the trip in C-TMS.

			===Inbound POD/POC -DEL Message===

			Four new fields will be introduced to the DEL message for Smartphones.

			*Weighbridge Ticket
			*Net Weight
			*Gross Weight
			*Tare Weight

			The Weighbridge Ticket will be received as part of the Order Sub References, this data level will be added to the inbound del message for Smartphone in the same format that the sub reference data is received from TOKAIRO, within the order header and before the order detail. Weigh bridge will be received with an identifier ‘99’


			<U>An example of Sub References received from Tokairo</u>

Middletong at 10:26, 1 October 2012

2012-10-01T10:26:51Z

← Older revision		Revision as of 12:26, 1 October 2012
Line 411:		Line 411:

	[[Image:292729_6.png]]		[[Image:292729_6.png]]

			The outbound code will be amended to include the driver id, name, contact number, tractor and the trailer id from the first stop on the trip

			===Inbound SysEvent - ARR Message===
			A new tag field will be added for the ARR inbound event to provide the Trailer id. This will be written back to the Trailer id against the Trip and trip stops. The tractor and trailer data will be processed without any validation against the C-TMS resource tables. Driver id must exist in C-TMS, and if C-TMS fails to find the id, a new record will be created in RES_PERSON before the driver id is updated on the trip.

			An example of an INBOUND message is displayed below with the additional field displayed in Red.

			<?xml version="1.0" encoding="UTF-8"?>
			<OBS_XML>
			<EVENT>
			<EVENT_HEADER>
			<EVENT_PROCESSED>N</EVENT_PROCESSED>
			<EVENT_SOURCE_TYPE>TRAK</EVENT_SOURCE_TYPE>
			<EVENT_SOURCE_NAME>SMA</EVENT_SOURCE_NAME>
			<EVENT_DATE>2011-10-05T13:02:58</EVENT_DATE>
			<EVENT_TYPE>ARR</EVENT_TYPE>
			<EVENT_ACTION>C</EVENT_ACTION>
			</EVENT_HEADER>
			<EVENT_DETAIL>
			<TRIP_HEADER>
			<TRIP_IDENTIFIER>T</TRIP_IDENTIFIER>
			<TRIP_TRANSACTION_DATE>2011-10-05T13:02:58</TRIP_TRANSACTION_DATE>
			<TRIP_ID>MAN-01090037</TRIP_ID>
			</TRIP_HEADER>
			<TRIP_DETAIL>
			<TRACKING>Y</TRACKING>
			<DRIVER>ALAN BALL</DRIVER>
			<TRACTOR>PO60HNG</TRACTOR>
			<TRIP_TRAILER_ID>11702x</TRIP_TRAILER_ID>
			</TRIP_DETAIL>
			<STOPS>
			<STOP>
			<STOP_HEADER>
			<STOP_IDENTIFIER>S</STOP_IDENTIFIER>
			<STOP_SEQ>2</STOP_SEQ>
			</STOP_HEADER>
			<STOP_DETAIL>
			<STOP_LOCATION_ID>CHEZANT</STOP_LOCATION_ID>
			<STOP_ACTUAL_ARRIVAL_DATE>2011-10-05T13:02:58</STOP_ACTUAL_ARRIVAL_DATE>
			</STOP_DETAIL>
			</STOP>
			</STOPS>
			</EVENT_DETAIL>
			</EVENT>
			</OBS_XML>

			Based on the value of a new Cost centre parameter SMA_RESOURCE_UPDATE, information received in the inbound flow will over write any resource information currently stored against the trip in C-TMS.

Middletong at 09:19, 1 October 2012

2012-10-01T09:19:19Z

← Older revision		Revision as of 11:19, 1 October 2012
Line 405:		Line 405:

	If there is more than one resource assigned to the carrier, the resource will not be populated on the trip.		If there is more than one resource assigned to the carrier, the resource will not be populated on the trip.

			===Outbound Smartphone Message===

			Outbound messages are sent from C-TMS to Smartphone and the triggers which send the message will be the same as the existing functionality. The content of the message will be changed to include the existing XML tag fields;

			[[Image:292729_6.png]]

Middletong at 09:15, 1 October 2012

2012-10-01T09:15:52Z

← Older revision		Revision as of 11:15, 1 October 2012
Line 393:		Line 393:

	===Automatic Trip Resources===		===Automatic Trip Resources===

			As part of trip creation and amendment, when a carrier is assigned to a trip, the resources assigned to the carrier will be checked. Carriers are assigned to Drivers and Tractors.

			[[Image:292729_4.png]]

			Where a single resource has been assigned to a carrier, the resource on the trip will be automatically populated. Where a tractor has been automatically assigned to a trip, the system will also check if a single trailer has been assigned to the tractor and auto populate the trailer. The trailer is populated at stop level.

			[[Image:292729_5.png]]

			If a carrier is removed from a trip, the trailer, tractor and driver assigned to the trip will also be removed. The removal and auto population of resources will be controlled by the value of the new cost centre parameter TMS_AUTO_DEFAULT_RESOURCE.

			If there is more than one resource assigned to the carrier, the resource will not be populated on the trip.

Middletong at 09:13, 1 October 2012

2012-10-01T09:13:37Z

← Older revision		Revision as of 11:13, 1 October 2012
Line 377:		Line 377:

	[[Image:292729_3.png]]		[[Image:292729_3.png]]

			Inbound messages will be expected in the same format as MICROLISE and will cover the following event types

			STA – Departure date/time from first stop

			DEP – Departure date/time from a stop

			ARR – Arrival date/time at a stop

			END – Arrival date/time at the last stop

			SUM – Summary of all trip resource and stop information

			DEL – Order quantity debrief at delivery stop

			===Automatic Trip Resources===

Middletong at 09:11, 1 October 2012

2012-10-01T09:11:46Z

← Older revision		Revision as of 11:11, 1 October 2012
Line 375:		Line 375:

	The trigger points for sending an outbound message to a smart phone are listed below, where a trip has been assigned a SMARTPHONE enables resource.		The trigger points for sending an outbound message to a smart phone are listed below, where a trip has been assigned a SMARTPHONE enables resource.

			[[Image:292729_3.png]]

Middletong at 09:02, 1 October 2012

2012-10-01T09:02:32Z

← Older revision		Revision as of 11:02, 1 October 2012
Line 368:		Line 368:
	<br/>		<br/>
	<br/>		<br/>
			<br/>

	To send or receive smartphone messages for a trip, the trip must be assigned a smart phone enabled carrier or driver. Drivers and Carriers are set up as smartphone enabled in the Resources maintenance screen.		To send or receive smartphone messages for a trip, the trip must be assigned a smart phone enabled carrier or driver. Drivers and Carriers are set up as smartphone enabled in the Resources maintenance screen.