this function belongs to the optional module GEOMIPS
Refer to documentation Implementation
The setup function of the mission types contains one single grid used to set up each mission type.
Presentation
The priority of a mission is used to manage and sort the missions by urgency (the lower the priority, the higher the urgency). This is one of the main criteria of the mission search algoithm to be submitted to a resource.
The purpose of this function is to optimize the intervention of the resources by searching in priority for a given type of mission to be conducted in the mission area where the resource is located after having completed a previous mission. This sequencing of missions will depend on the mission type and resource.
For example, let us consider a resource mainly working on storing missions. Once this mission has been completed, they are located in a mission area within the warehouse. Instead of asking the resource to return to the receiving docks to handle a new storing mission, it is recommended to take advantage of the resource being located in this mission area to check that there are no other transfer/replenishment missions to perform.
Close
Fields
The following fields are present on this tab :
| 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.). |
| Select this check box to activate the current record. Disabled records keep their content and setup but cannot be used (by recalling their code) on other records (documents, settings ...), or for mass processes. The authorizations to a given function can prohibit the creation of an active record. In this case, the check box is disabled by default. It can only be modified by an authorized user or through a signature Workflow. |
| specifies if the missions of this type are created automatically following the creation of the corresponding GEODE entity. For example: Let us consider storing (STORING) type missions setup in auto creation. The creation of an SL on the site will generate the creation of an associated STORING mission. |
| specifies whether the missions are blocked by default upon being created (status "6-Blocked" instead of "1-Available"). A "blocked" mission will never be submitted to a resource. A manual action on the mission will be mandatory to unblock it and make it available. |
| the default priority that will be applied on creating missions with a certain type. upon the manual creation of a mission, its priority is initialized with the default one but it can be modified |
| specifies the maximum number of resources who can work simultaneously on the same mission. Missions of type PKOPRC et PKOSHP (SU and parcel picking) do not manage this parameter. In fact, in all cases, a parcel or SU will always be prepared by one resource at a time. |
| specifies if the mission sequencing is authorized on missions of this type. |
Close