EST 348745 Fleetmatics Tracking ETA - Revision history

Anw: Spelling

2018-01-29T08:37:04Z

Spelling

← Older revision		Revision as of 10:37, 29 January 2018
Line 12:		Line 12:
	\|Clients_Customer=		\|Clients_Customer=
	\|System_Version_being_changed=		\|System_Version_being_changed=
	\|Client_Request=Requirement: to utilise ~~Fleettrack~~ Webservices to update Portal TTM ETAs.		\|Client_Request=Requirement: to utilise Fleetmatics Webservices to update Portal TTM ETAs.
	\|OBS_Solution=The ''CALIDUS'' Portal TTM and TMS systems will be modified for this purpose.		\|OBS_Solution=The ''CALIDUS'' Portal TTM and TMS systems will be modified for this purpose.

Line 20:		Line 20:
	[[File:EST-348745-2.jpg]]		[[File:EST-348745-2.jpg]]

	A new process will be written within CTMS, to calculate the ETA based on the currently-processing trips (at status EN ROUTE). This will check the current vehicle location with ~~Fleetmatic~~ (where the vehicle is marked as being tracked by ~~Fleetmatic~~). The current location of the vehicle will be stored and compared with the location of the next stop on the trip. The ETA will be updated using the existing time and distance calculation. Each subsequent stop will have the ETA updated based on a delta difference (i.e. if the arrival at the next stop is delayed by 10 minutes, each subsequent stop will have an ETA of +10 minutes from the planned time).		A new process will be written within CTMS, to calculate the ETA based on the currently-processing trips (at status EN ROUTE). This will check the current vehicle location with Fleetmatics (where the vehicle is marked as being tracked by Fleetmatics). The current location of the vehicle will be stored and compared with the location of the next stop on the trip. The ETA will be updated using the existing time and distance calculation. Each subsequent stop will have the ETA updated based on a delta difference (i.e. if the arrival at the next stop is delayed by 10 minutes, each subsequent stop will have an ETA of +10 minutes from the planned time).

	C-TMS will be modified to send this information (when calculated) to Portal TTM, at the Trip and Stop level, along with the vehicle current location. Portal TTM will be modified to receive and store this information.		C-TMS will be modified to send this information (when calculated) to Portal TTM, at the Trip and Stop level, along with the vehicle current location. Portal TTM will be modified to receive and store this information.
Line 30:		Line 30:
	[[File:EST-348745-3.jpg]]		[[File:EST-348745-3.jpg]]

	The current vehicle location will be used on the Portal Customer Gateway screen to show the current vehicle location without requesting it directly from ~~Fleetmatic~~.		The current vehicle location will be used on the Portal Customer Gateway screen to show the current vehicle location without requesting it directly from Fleetmatics.

	[[File:EST-348745-4.jpg]]		[[File:EST-348745-4.jpg]]

Anw: v0.4 - All change - new draft

2018-01-26T17:43:50Z

v0.4 - All change - new draft

← Older revision		Revision as of 19:43, 26 January 2018
Line 5:		Line 5:
	\|Supimix_Client_Reference=		\|Supimix_Client_Reference=
	\|Supimix_Number=348745		\|Supimix_Number=348745
	\|The_version_of_the_document=0.3		\|The_version_of_the_document=0.4
	\|Your_Name=A N Walker		\|Your_Name=A N Walker
	\|Supimix_PO_Reference=		\|Supimix_PO_Reference=
Line 15:		Line 15:
	\|OBS_Solution=The ''CALIDUS'' Portal TTM and TMS systems will be modified for this purpose.		\|OBS_Solution=The ''CALIDUS'' Portal TTM and TMS systems will be modified for this purpose.

	The current location of the vehicle will be stored and compared with the location of ~~each~~ stop on the trip. The ETA will be updated using the existing time and distance calculation.		In order to achieve this, C-TMS must be modified to identify vehicles as tracking through Fleetmatics, and store the Fleetmatics Vehicle reference. The Vehicles and Tractors screens will be modified for this purpose.

			[[File:EST-348745-1.jpg]]
			[[File:EST-348745-2.jpg]]

			A new process will be written within CTMS, to calculate the ETA based on the currently-processing trips (at status EN ROUTE). This will check the current vehicle location with Fleetmatic (where the vehicle is marked as being tracked by Fleetmatic). The current location of the vehicle will be stored and compared with the location of the next stop on the trip. The ETA will be updated using the existing time and distance calculation. Each subsequent stop will have the ETA updated based on a delta difference (i.e. if the arrival at the next stop is delayed by 10 minutes, each subsequent stop will have an ETA of +10 minutes from the planned time).

	~~In order to achieve this,~~ C-TMS ~~must~~ be modified to ~~identify vehicles as tracking through Fleetmatics~~, and ~~store~~ the ~~Fleetmatics Vehicle reference~~. ~~The Vehicles and Tractors screens~~ will be modified ~~for~~ this ~~purpose~~.		C-TMS will be modified to send this information (when calculated) to Portal TTM, at the Trip and Stop level, along with the vehicle current location. Portal TTM will be modified to receive and store this information.

			This information will be displayed in C-TMS and C-Portal in the current screens where ETA is displayed.

			[[File:EST-348745-2.jpg]]

			[[File:EST-348745-3.jpg]]

	The ~~Portal TTM inbound interface~~ will be ~~modified to receive~~ the ~~External Tracking System and External Vehicle Reference stored by C-TMS above. This will stored and used~~ to ~~determine~~ the ~~ETA~~.		The current vehicle location will be used on the Portal Customer Gateway screen to show the current vehicle location without requesting it directly from Fleetmatic.

	~~The Portal process to receive data will be modified to check the current location of vehicles associated with En~~-~~Route Trips with Fleetmatics, using the provided Vehicle Update webservice API~~.		[[File:EST-348745-4.jpg]]

	\|Requirements_Days=		\|Requirements_Days=
	\|Estimation_Days=0.5		\|Estimation_Days=0.75
	\|Functional_Specification_Days=0.75		\|Functional_Specification_Days=2.25
	\|Technical_Specification_Days=0		\|Technical_Specification_Days=0
	\|Development_Days=~~4.25~~		\|Development_Days=7
	\|Testing_and_Release_Days=1.0		\|Testing_and_Release_Days=1.50
	\|Implementation_Days=0.75		\|Implementation_Days=0.75
	\|Project_Management_Days=0.25		\|Project_Management_Days=0.5
	\|Year=2018		\|Year=2018
	\|Free_Of_Charge=N		\|Free_Of_Charge=N

Anw: v0.3 - Changed estimate

2018-01-26T11:47:42Z

v0.3 - Changed estimate

← Older revision		Revision as of 13:47, 26 January 2018
Line 5:		Line 5:
	\|Supimix_Client_Reference=		\|Supimix_Client_Reference=
	\|Supimix_Number=348745		\|Supimix_Number=348745
	\|The_version_of_the_document=0.1		\|The_version_of_the_document=0.3
	\|Your_Name=A N Walker		\|Your_Name=A N Walker
	\|Supimix_PO_Reference=		\|Supimix_PO_Reference=
Line 27:		Line 27:
	\|Functional_Specification_Days=0.75		\|Functional_Specification_Days=0.75
	\|Technical_Specification_Days=0		\|Technical_Specification_Days=0
	\|Development_Days=5.0		\|Development_Days=4.25
	\|Testing_and_Release_Days=1.0		\|Testing_and_Release_Days=1.0
	\|Implementation_Days=0.75		\|Implementation_Days=0.75
	\|Project_Management_Days=0.5		\|Project_Management_Days=0.25
	\|Year=2018		\|Year=2018
	\|Free_Of_Charge=N		\|Free_Of_Charge=N

Anw: v0.2 - Changed estimate

2018-01-26T11:39:44Z

v0.2 - Changed estimate

← Older revision		Revision as of 13:39, 26 January 2018
Line 25:		Line 25:
	\|Requirements_Days=		\|Requirements_Days=
	\|Estimation_Days=0.5		\|Estimation_Days=0.5
	\|Functional_Specification_Days=1.25		\|Functional_Specification_Days=0.75
	\|Technical_Specification_Days=0		\|Technical_Specification_Days=0
	\|Development_Days=6.0		\|Development_Days=5.0
	\|Testing_and_Release_Days=1.0		\|Testing_and_Release_Days=1.0
	\|Implementation_Days=0.75		\|Implementation_Days=0.75

Anw: v0.1 - Initial Version

2018-01-26T11:33:53Z

v0.1 - Initial Version

← Older revision		Revision as of 13:33, 26 January 2018
Line 13:		Line 13:
	\|System_Version_being_changed=		\|System_Version_being_changed=
	\|Client_Request=Requirement: to utilise Fleettrack Webservices to update Portal TTM ETAs.		\|Client_Request=Requirement: to utilise Fleettrack Webservices to update Portal TTM ETAs.
	\|OBS_Solution=~~ ~~		\|OBS_Solution=The ''CALIDUS'' Portal TTM and TMS systems will be modified for this purpose.
	\|Requirements_Days=0
	\|Estimation_Days=0		The current location of the vehicle will be stored and compared with the location of each stop on the trip. The ETA will be updated using the existing time and distance calculation.
	\|Functional_Specification_Days=0
			In order to achieve this, C-TMS must be modified to identify vehicles as tracking through Fleetmatics, and store the Fleetmatics Vehicle reference. The Vehicles and Tractors screens will be modified for this purpose.

			The Portal TTM inbound interface will be modified to receive the External Tracking System and External Vehicle Reference stored by C-TMS above. This will stored and used to determine the ETA.

			The Portal process to receive data will be modified to check the current location of vehicles associated with En-Route Trips with Fleetmatics, using the provided Vehicle Update webservice API.

			\|Requirements_Days=
			\|Estimation_Days=0.5
			\|Functional_Specification_Days=1.25
	\|Technical_Specification_Days=0		\|Technical_Specification_Days=0
	\|Development_Days=0		\|Development_Days=6.0
	\|Testing_and_Release_Days=0		\|Testing_and_Release_Days=1.0
	\|Implementation_Days=0		\|Implementation_Days=0.75
	\|Project_Management_Days\|X=0		\|Project_Management_Days=0.5
	\|Year=2018		\|Year=2018
	\|Free_Of_Charge\|N=N		\|Free_Of_Charge=N
	\|~~DiscountPerc\|0~~=		\|Supimix_Client_Code=TDL
	\|~~DiscountText\|Discount~~=		\|ExpiryDays=60
	~~\|Supimix_Client_Code\|TEMPLATE=TDL~~}}		}}

Anw: EST 348745 Fleetmatics Tracking ETA

2018-01-26T10:55:30Z

EST 348745 Fleetmatics Tracking ETA

New page

{{Template:Estimate
|Supimix_Client_Code=TDL
|Supimix_Project_Code=DEV
|Supimix_Site_Code=TDL-SKEM
|Supimix_Client_Reference= 
|Supimix_Number=348745
|The_version_of_the_document=0.1
|Your_Name=A N Walker
|Supimix_PO_Reference= 
|Supimix_Priority=3
|Date_(DD/MM/YY)=26/01/18
|Clients_Customer= 
|System_Version_being_changed= 
|Client_Request=Requirement: to utilise Fleettrack Webservices to update Portal TTM ETAs.
|OBS_Solution= 
|Requirements_Days=0
|Estimation_Days=0
|Functional_Specification_Days=0
|Technical_Specification_Days=0
|Development_Days=0
|Testing_and_Release_Days=0
|Implementation_Days=0
|Project_Management_Days|X=0
|Year=2018
|Free_Of_Charge|N=N
|DiscountPerc|0=
|DiscountText|Discount=
|Supimix_Client_Code|TEMPLATE=TDL}}