Zoning

From UG

(Difference between revisions)

Jump to: navigation, search

Current revision as of 23:35, 13 May 2010

[edit] Concept

Zone is a set of locations that are "not too far from each other" on the map.

Pick Up Zone is a set of Ct#Pick_Up locations that are "not too far from each other" on the map.

[edit] Version 1 limitations

One Zone would contain only locations for one Client Company.
They would be entered manually by operator

[edit] Ideas for future versions

Zone size: Max radius or max path should be defined. If locations are too spread out they can not be considered in one zone
Zone members (locations) could be automatically added by system based on new CT entered and max radius defined
Multi client: One Zone would contain locations for many Client Company - this would allow consolidation

[edit] Interface

[edit] Zones Control

Zones control is carried out in section Admin - Geography (see Figure 1).
Zones can be added, edited or deleted. Also archived/restored (TBD).

[edit] Zones Use

Different Zones may contain the same Pick-Up Locations for different Clients, but each Pick-Up Location may be used for each Client only in one Zone.
- Z1 = {Client A, {PULocX , ... }} and Z2 = {Client B, {PULocX, ... }

[edit] Figures

[edit] Figure 1. Zones Table (version 1)

[edit] Figure 2. Edit Zone Window (version 1)

[edit] History

[edit] Version 1 from Tira

see version 8818

@@ Line 1: / Line 1: @@
-== Zoning ==
+[[Category:NATP Optimization]]
-=== One Client vs many (consolidation) ===
+== Concept ==
-* option 1) One Zone can contain only locations for one client
+'''Zone''' is a set of locations that are "not too far from each other" on the map.
-* option 2) One Zone can contain locations for multiple clients
+'''Pick Up Zone''' is a set of [[Ct#Pick_Up]] locations that are "not too far from each other" on the map.
-** consolidating freight from multiple companies (this would optimize loads using economy of scale)
-=== Zone size ===
+=== Version 1 limitations ===
-Max radius or max path should be defined. If locations are too spread out they can not be considered in one zone.
+* One Zone would contain only locations for one Client Company.
+* They would be entered manually by operator
-=== Static zone vs dynamic ===
+=== Ideas for future versions ===
-Assume you have a uniform distribution of pick up locations  stretching over a long distance along same road. Then it make sense to consider "dynamic" zones - they would form based on current state of freight located in each location.
+* Zone size: Max radius or max path should be defined. If locations are too spread out they can not be considered in one zone
+* Zone members (locations) could be automatically added by system based on new CT entered and max radius defined
+* Multi client: One Zone would contain locations for many Client Company - this would allow consolidation
-== Intro ==
+== Interface ==
-== Summary ==
+=== Zones Control ===
+* Zones control is carried out in section Admin - Geography (see [[#Figure 1. Zones Table (version 1) | Figure 1]]).
+* Zones can be added, edited or deleted. Also archived/restored ([[TBD]]).
+=== Zones Use ===
+* Different Zones may contain the same Pick-Up Locations for different Clients, but each Pick-Up Location may be used for each Client only in one Zone.
+** Z1 = {Client A, {PULocX , ... }} and  Z2 = {Client B, {PULocX, ...  }
-== Design ==
 == Figures ==
-=== Figure 1. Create a zone ===
-[[File:AddDomesticZone.JPG]]
-=== Figure 2. Assign Location to zone ===
+=== Figure 1. Zones Table (version 1) ===
-[[]]
+[[File:ZonesTable.GIF]]
-[[File:AssignZoneAdd.JPG]]
+=== Figure 2. Edit Zone Window (version 1) ===
+[[File:EditZoneWindow.GIF]]
-=== Figure 3. Assign / Edit Zone Pop-up ===
+== History ==
-[[]]
-[[File:AssignLocationToZonePopUp.JPG]]
-=== Figure 4. View Zone Location ===
+=== Version 1 from Tira ===
-[[File:ViewZoneLocations.JPG]]
+see [http://mantis.jaguarfreight.com/mediawiki-1.15.0/index.php?title=Zoning&oldid=8818 version 8818]