Mission areas
This function is used to manage the missionareas on the current site.
A mission area is a part of a store where the locations comply with the same rules:
- Accessibility by a type of material or a type of resource to this mission area
- Authorization to carry out a type of mission by a given type of resource in this mission area.
A mission area is usually:
- all or part of the travel sequences within a store of Main or Allocation type.
- the store itself if it is of dock, buffer or single-address type.
There a 4 types of mission areas:
- Receiving dock: it characterizes a mission area devoted to receiving stock (possible for stores of dock, cross-dock or single-address type only).
- Shipment dock: it characterizes a mission area devoted to shipping stock (possible for stores of dock, cross-dock or single-address type only).
- Buffer area: it characterizes a mission area devoted to a buffer store (this functionality is not available for the moment)
- Travel sequence: it characterizes a mission area devoted to a main or allocation store.
The mission area type is given for information only.
this function belongs to the optional module GEOMIPS
Prerequisites
Refer to documentation Implementation
Screen management
In the left part of the screen, this function lists the mission types supplied along with the various parameters associated to them.
Header
Fields
The following fields are present on this tab :
| Code identifying a mission area (defined by site). A mission area is a part of a store. For the main and allocation stores: the area is a group of aisles (travel sequences) (1 store = n areas). For the other types of stores: the area is a full store (1 store = 1 area) |
|
|
Close
Tab General
Presentation
This tab makes it possible to configure the mission areas.
Creation principle of a mission area:
- Select the store
- Select the mission area type (only for information purposes)
- Select the location types to be taken into account (picking and/or reserve) in the area.
- Select the travel sequences in the event of main and allocation stores.
A location can only belong to a single mission area. Several mission areas cannot overlap (checks have been set up each time an area is created or modified).
Close
Fields
The following fields are present on this tab :
Block number 1
|
|
| Code used to identify the store. This code is controlled in the store table. |
|
|
|
|
Type
| Specifies the mission area type. |
Block number 3
|
|
|
|
Type of location
|
|
|
|
Aisles
|
|
|
|
|
|
|
|
Close
Tab Sequencing
Presentation
THis tab is used to define the sequencing of the mission areas.
The objective is twofold:
- define the relative proximity of the other mission areas with respect to the current area. This criterion will be important when sorting missions to be conducted by a given resource (from the closest to the furthest away from the area where the resource is currently located)
- Authorize the completion of missions that are not located in the area where the resource is currently located.
It is therefore recommended to ensure that each area of the site is systematically sequenced to all the other areas of the site. Otherwise only those missions located in the area where the resource is to be found.
Close
Fields
The following fields are present on this tab :
Grid
| Indicates the mission sequencing field. |
Close