296870: Difference between revisions
Middletong (talk | contribs) (New page: {{Doc_Title|System=FUNCTIONAL SPECIFICATION|Title=Modify Child Location to use parent latlong|Reference=FS 296870 AK-8RPHMB|Version=0.1|Date=23/02/12|Sysver=10.7|Client=DHL C-TMS}}) |
Middletong (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
{{Doc_Title|System=FUNCTIONAL SPECIFICATION|Title=Modify Child Location to use parent latlong|Reference=FS 296870 AK-8RPHMB|Version=0.1|Date=23/02/12|Sysver=10.7|Client=DHL C-TMS}} | {{Doc_Title|System=FUNCTIONAL SPECIFICATION|Title=Modify Child Location to use parent latlong|Reference=FS 296870 AK-8RPHMB|Version=0.1|Date=23/02/12|Sysver=10.7|Client=DHL C-TMS}} | ||
=FUNCTIONAL OVERVIEW= | |||
==Client Requirement== | |||
DISC Interface – Modify Child Location Creation to use Parent Lat/Longs | |||
==Solution== | |||
During the creation of a Child Location the Parent Location’s Lat/Long data will be used to set the Child’s Lat/long data. | |||
A new tick box will be added to the Location’s Special Tab: ‘Fixed Lat/Longs’ this will be set to Y when creating Child locations. This will protect the Child’s Lat/Long from being updated should for example the Child address postcode be altered. When un-checked the Lat / Long could then be modified manually or automatically by changing town/postcode information using existing NAVTEQ calls. | |||
This change ensures that the distance calculated to deliver to Child locations is derived the same as per parent and hence rated consistently. This also solves issues regarding missing and invalid Child location postcodes. | |||
Furthermore, the provided Child address information received will be passed to Microlise for execution. It is envisaged that no geo-fence breaks will be provided in SystemEvent messages from Microlise and that debrief times will be sent in PODPOC/JourneySummary message only. | |||
Latest revision as of 12:47, 30 October 2012
DHL C-TMS
Modify Child Location to use parent latlong
FUNCTIONAL SPECIFICATION - 10.7
23/02/12 - 0.1
Reference: FS 296870 AK-8RPHMB
FUNCTIONAL OVERVIEW
Client Requirement
DISC Interface – Modify Child Location Creation to use Parent Lat/Longs
Solution
During the creation of a Child Location the Parent Location’s Lat/Long data will be used to set the Child’s Lat/long data.
A new tick box will be added to the Location’s Special Tab: ‘Fixed Lat/Longs’ this will be set to Y when creating Child locations. This will protect the Child’s Lat/Long from being updated should for example the Child address postcode be altered. When un-checked the Lat / Long could then be modified manually or automatically by changing town/postcode information using existing NAVTEQ calls.
This change ensures that the distance calculated to deliver to Child locations is derived the same as per parent and hence rated consistently. This also solves issues regarding missing and invalid Child location postcodes.
Furthermore, the provided Child address information received will be passed to Microlise for execution. It is envisaged that no geo-fence breaks will be provided in SystemEvent messages from Microlise and that debrief times will be sent in PODPOC/JourneySummary message only.
