Missions
This function is used to manage the missions on the current site. It makes it possible to:
- create missions
- modify the characteristics of the missions (priority, start and/or end area, maximum number of resources able to work on the same mission simulataneously, reservation made to a type of resource, reservation made to a resource)
- make tha mission available or not
- close a mission
- unlock locked operations.
It is also used to view the progress and history of a mission in terms of tasks/operations being performed, already performed or rejected.
this function belongs to the optional module GEOMIPS
Prerequisites
Refer to documentation Implementation
Screen management
The function contains a left list of the existing missions and 3 tabs (General, Detail and Rejections).
Header
Presentation
The header contains the information on the mission number, mission type and status.
Close
Fields
The following fields are present on this tab :
| specifies the number of the mission. This number is managed by the "MSN" counter. |
| specifies the mission status: |
| Code identifying the type of mission (defined by site). A mission type represents a logistical flow of the warehouse (like the receipt, the storage, etc.). |
Close
Tab General
Presentation
This tab contains the general information on the mission nd is sub-divied into 4 different fields.
Entity
it contains the entity linked to the mission and the mission start and end positions/areas.
Mission type | Description | Linked entity | Start area | End area |
RECEIVING | Receiving mission of an AR | AR | AR dock | AR dock |
STORING | Storing mission of a SL | SL | AR (*) dock | NO |
PKOMVT | Picking mission of a PO (without packing or declarative packing) | PO | NO | YES (**) |
PKOPRC | Picking mission for a prepacked parcel | Parcels | YES (**) | YES (**) |
PKOSHP | Picking mission for a prepacked SU | SU | YES (**) | YES (**) |
TRFFLC | Merging of flow transfer mission, 1st phase | TO | NO | NO |
TRFSTK | Transfer mission (normal type, merging with or without merging of flows, full container) | TO | NO | NO |
TRFRPNN | Stock-out replenishment mission | PO | NO | NO |
TRFRPNP | Preventive replenishment mission | PO | NO | NO |
TRFBOM | Transfer mission, 1st phase of the assembly | TO | NO | NO |
(*) if all the input movements of the SL originate from an AR for the same receiving dock
(**) field specified by the "picking location" function.
Piloting
it contains the mission sequencing parameters: unlock, priority, max no. of resources, reservation to a resource type, reservation to a resource.
A mission is unlocked by checking the corresponding flag.
Processing
the start and end dates of the mission are detailed here
Rejections
the number of tasks and operations rejected is specified here.
Close
Fields
The following fields are present on this tab :
Entity
| indicates the mission or operation entity type. |
| Code representing the depositor. In logistics terms, the concept of depositor makes it possible to process separate flows or traffics within the same site. It encompasses the concept of order-issuing customer for the service providers. After the site, the depositor is the second access key to the Product, Input and Delivery Order files. For the location, the depositor code is entered if the location is allocated to the depositor or to the product, and if the location is single-depositor or single-product or if it is not empty. |
| indique le numéro de l'entité de la mission. |
| Specifies the position (storage-address) of the mission start area. |
| Specifies the mission start area associated with the entered position. |
| Specifies the position (storage-address) of the mission end area. |
| indicates the end mission field assigned to the entered position. |
Piloting
| This flag specifies whether the mission is "to block". The initialization of this flag is carried out either manually by a resource wishing to block the mission, or automatically further to the blocking rejection of a task on this mission.
|
| Specifies the priority of the mission. This priority (vlaue from 1 to 99) is used in the mission search algorithm as an emergency criterion (1= the most urgent, 99 = the least urgent). |
|
|
|
|
|
| Specifies whether the mission is reserved for a given type of resource. If so, the mission can solely be processed by a resource of this type. |
| specifies whether the mission is reserved for a given resource. If so, the mission can solely be processed by the given resource. |
Processing
| Specifies the start time of the mission completion. It means the moment when the first task has been accepted and processed by a resource. |
|
|
| Specifies the end date and time of the mission completion. It means the moment when the processing of the last task has been completed by a resource.
|
|
|
Rejections
| Specifies the number of rejected tasks. |
| Specifies the number of blocked operations. |
Close
Tab Detail
Presentation
This tab lists all the tasks (including their associated operations) that have been carried out or that are being carried out.
Tasks
For each task, the following is mentioned: resource, materials (IT and handling) used, start and end areas of the task, start and end dates of the task.
Different colors applied to the Resource column specify whether the task is being performed or is completed:
- Blue: the task is being performed
- Normal (White): task completed
The icon in the first column is used to identify those tasks performed using the mission sequencing process. Via right-click on the task, the "Sequencing" option displays in a window the information relating to the task and mission starting from which the selected task was sequenced.
Operations
Depending on the selected task, the system displays its constituting operations Let us mention among ohers the information on the mission area of the operation, a reason why an operation has not been performed, etc.
Different colors on the Product column illustrate the status of the operation:
- Normal (White): operation performed
- Red: operation rejected or not performed
- Blue: operation under progress
- Bold black: operation ready for processing
Close
Fields
The following fields are present on this tab :
Grid Tasks
|
|
| Specifies the resource in charge of the task. |
| Specifies the IT material used for the task. |
| Specifies the handling material used for the task. |
| Specifies the start date of the task completion. |
| Specifies the position (store/address) where the resource has accepted this task. |
| Specifies the mission area associated with the indicated position (store/address). |
| Specifies the end date of the task completion. |
| Specifies the position (store/address) where the resource has completed this task. |
| Specifies the mission area associated with the indicated position (store/address). |
| Specifies the task status: |
| specifies the number of the task. This number is managed by the "MTK" counter. |
Grid Operations
| Specifies the operation type (Removal or Relocation). This type is only used for missions of storing type (STORING). |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| specifies the end mission area assigned to the operation position. |
| Specifies the operation status: |
| specifies the reason why an operation was rejected or not performed. |
| Specifies the number of the entity associated with the operation. |
| Specifies the number of the operation. |
Close
Action icon
Sequencing
In the event of a sequenced task, this button is used to specify the task and mission from which there was a sequencing with the selected task.
Close
Tab Tab Rejections
Presentation
This tab contains the rejected tasks, along with the locked operations relating to the selected mission.
Tasks
Information on the rejected tasks, such as the rejection time, rejection reason and resource having rejected the task, is mentioned here.
Locked operations
Information on the locked operations, such as as the reason for locking the operation, and the resource having locked it, is mentioned here.
It is also possible to unlock these operations by checking the first column "To unlock".
Close
Fields
The following fields are present on this tab :
Grid Tasks
| Specifies the rejection date and time of the task. |
| Specifies the rejection reason of the task. |
| Specifies the resource in charge of the task. |
| specifies the number of the task. This number is managed by the "MTK" counter. |
Grid Blocked operations
| Used to unlock an operation by checking it, then saving it. |
| specifies the date and time of the rejection of the operation. |
| specifies the resource having processed the operation. |
| specifies the reason why an operation was rejected or not performed. |
| Specifies the number of the entity associated with the operation. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| specifies the number of the task. This number is managed by the "MTK" counter. |
| Specifies the number of the operation. |
Close
Tab number 4
Fields
The following fields are present on this tab :
Grid
| Specifies the operation type (Removal or Relocation). This type is only used for missions of storing type (STORING). |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Specifies the start date and time of the operation processing. |
|
|
| Specifies the end date and time of the operation processing. |
|
|
| Specifies the operation status: |
| specifies the reason why an operation was rejected or not performed. |
| indicates the mission or operation entity type. |
|
|
| Specifies the number of the entity associated with the operation. |
| specifies the number of the task. This number is managed by the "MTK" counter. |
| Specifies the number of the operation. |
Close
Specific Buttons
This button is used to close a mission (it moves to the status '8-Processed').
|
Error messages
In addition to the generic error messages, the following messages can appear during the entry :
Information message: "Mission xxxx: Record already exists"
it is impossible to create the mission because there already is an "open" mission (status <> '8-Processed') on the Warehousing entity.