Page History

Once ProTrack Warehouse has been configured to import data, configuring other key elements in the system comes next. Some of this is required, and some of it may remain optional until standards have been configured and productivity data is flowing through ProTrack. The required configuration is listed below:

Facilities

Activities

Schedules

Employees

...

Zones and Micro-zones
These are elements which can be passed via WMS file import which represent where the Activity was physically performed in the facility. Additionally Zones and Micro-Zones may be used for more granular reporting. There is no direct relationship between a Zone and a Micro-Zone.

[Activity Group]s and [Tasking Group]s

These are hierarchical groupings which provide you with the ability to group activities together for reporting purposes. An [Activity Group] is a group of\[ Activities\], and a [Tasking Group] is a group of [Activity Groups]. Each [Activity] may only belong to one\[ Activity Group\]; each [Activity Group] may only belong to one [Tasking Group].

Shifts
A Shift is simply a group of schedules. Shifts are often used in ProTrack to group schedules that start around the same time. For example a single Shift may contain three Schedules, which have associates on staggered start times (differing by perhaps 30 minutes).

...

Locations & Levels Locations are imported last and represent the various places an associate travels. Locations are specified as (x,y) coordinates. Levels are the various z heights within each location. A four-shelf rack with levels labeled as letters would typically have 5 levels: floor level (A), 1st shelf (B), 2nd shelf (C), 3rd shelf (D), and 4th shelf (E).

Caches - – Node & Location ProTrack Warehouse utilizes two types of caching techniques in order to improve optimal travel route determination while calculating standard times. Node caching stores optimal routes between every pair of nodes on a floor and is a required process before standard calculation can take place. Location caching stores optimal routes between pairs of locations and is typically built and grows "on-the-fly" as WMS data is being processed in the system. Location cache is not required, but is merely a performance optimization.

...