256287

From CTMS
Revision as of 18:47, 5 February 2009 by Kingj (talk | contribs) (New page: = 256287-NW-7KGE7N Fixed Routes to Run with Zip codes = Copyright OBS Logistics © 2007 The information contained herein is the property of OBS Logistics and is supplied without liabilit...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

256287-NW-7KGE7N Fixed Routes to Run with Zip codes

Copyright OBS Logistics © 2007

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied


FUNCTIONAL OVERVIEW

Client Requirement

Fixed Routes currently utilises either locations or regions at stop level, the postal regions work based on the first sector of the UK post code, for example B or CV whereas the planning region can be defined against these i.e. MID for Midlands comprising both B and CV. There are now possibilities of deploying MTS in the likes of Portugal and Poland where ZIP Codes are defined differently and so within MTS there will be a requirement to define Fixed Routes by ZIP region and hence there may be different sectors of the ZIP code that need to be referenced dependent on the country. The same code or translation will also need to be applied when defining planning regions.


Solution

The Fixed routes functionality should be able to handle any changes to the postal or planning regions. Providing the regions are set up correctly. However, the postal and planning regions currently will not work for post (zip) codes that are numeric or that use digits other than the first two digits of the post code. The logic behind the postal and planning regions will be changed to allow the use of numeric postcodes. Firstly the country code will be held against the postal \ planning region combinations on the table geo_plan_region. A new table, and maintenance screen will be created that will store the details of a country’s postcode and define which parts of the post code are relevant when defining the postal region The locations screen works out the postal region based on the post code entered. The new table will be used to determine which parts of the postcode should be used when working out the postal region. The postal region can then be used to determine the planning region based on the data in geo_plan_region.


Scope

This change will be applied to system version 10.6.


FUNCTIONAL DESCRIPTION

To make the maintenance of postal and planning regions easier, the country code will be held against the postal \ planning region combination in Static Data Maintenance.

IMAGE

A new tab will be added to the Country Code screen to allow the maintenance of the postal regions. Each country can have a postcode format assigned and within this format the relevant characters can be chosen.

IMAGE

The maintenance table will contain the Country code, the post code type and the relevant character of the postcode.

If more than one character of the postcode is relevant multiple entries can be made.


So for GB we would store

GB CHAR 1 GB CHAR 2

For Poland

PL NUM 1

This would indicate that the first 2 characters are relevant for the UK, if they are Letters. While the first character is relevant for Poland.

Within the Locations screen the postal region is calculated based on the postcode entered. Currently it will only look at the first two characters of the postcode if the characters are letters (i.e. for UK postcodes).

This will be changed to be dynamic. The postal region will be populated based on the format held against the country code.

IMAGE

References IMAGE

Glossary IMAGE

Document History IMAGE

Authorised By

IMAGE