EST 348745 Fleetmatics Tracking ETA: Difference between revisions
(EST 348745 Fleetmatics Tracking ETA) |
(Spelling) |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 5: | Line 5: | ||
|Supimix_Client_Reference= | |Supimix_Client_Reference= | ||
|Supimix_Number=348745 | |Supimix_Number=348745 | ||
|The_version_of_the_document=0. | |The_version_of_the_document=0.4 | ||
|Your_Name=A N Walker | |Your_Name=A N Walker | ||
|Supimix_PO_Reference= | |Supimix_PO_Reference= | ||
| Line 12: | Line 12: | ||
|Clients_Customer= | |Clients_Customer= | ||
|System_Version_being_changed= | |System_Version_being_changed= | ||
|Client_Request=Requirement: to utilise | |Client_Request=Requirement: to utilise Fleetmatics 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= | |||
|Estimation_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. | ||
|Functional_Specification_Days= | |||
[[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 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. | |||
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 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]] | |||
|Requirements_Days= | |||
|Estimation_Days=0.75 | |||
|Functional_Specification_Days=2.25 | |||
|Technical_Specification_Days=0 | |Technical_Specification_Days=0 | ||
|Development_Days= | |Development_Days=7 | ||
|Testing_and_Release_Days= | |Testing_and_Release_Days=1.50 | ||
|Implementation_Days=0 | |Implementation_Days=0.75 | ||
|Project_Management_Days | |Project_Management_Days=0.5 | ||
|Year=2018 | |Year=2018 | ||
|Free_Of_Charge | |Free_Of_Charge=N | ||
| | |Supimix_Client_Code=TDL | ||
| | |ExpiryDays=60 | ||
}} | |||
Latest revision as of 10:37, 29 January 2018
 |
CHANGE REQUEST ESTIMATE |
| Client | TDL | Project | DEV | Site | TDL-SKEM |
| Client Reference | Aptean Reference | 348745 | Estimate Version | 0.4 | |
| Prepared By | A N Walker | Estimate Date | 26/01/18 | ||
| Invoice Reference | Priority | 3 | |||
| Customer | System Version | ||||
| Client Request |
| Requirement: to utilise Fleetmatics Webservices to update Portal TTM ETAs. |
| Aptean Solution |
| The CALIDUS Portal TTM and TMS systems will be modified for this purpose.
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 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. This information will be displayed in C-TMS and C-Portal in the current screens where ETA is displayed. 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 |
 Warning: | Unknown costs for client/year (TDL/2018) |
| Cost Details | |||
| Activity | Hours | Rate per hour (£) | Cost (£ Exc. VAT) |
| Requirements | 0.00 | £First argument to "number_format" must be a number. | |
| Change Request Evaluation | 0.75 | 0.00 | £0.00 |
| Functional Specification | 2.25 | 0.00 | £0.00 |
| Technical Specification | 0.00 | 0.00 | £0.00 |
| Development | 7.00 | 0.00 | £0.00 |
| Testing and Release | 1.50 | 0.00 | £0.00 |
| Implementation | 0.75 | 0.00 | £0.00 |
| Project Management | 0.50 | 0.00 | £0.00 |
| TOTAL | 12.75 | £First argument to "number_format" must be a number. | |
| Estimate excludes training, release to live and go live support. |
|
Copyright © Aptean 2018. |
