Mission sequencing
This function is used to manage the mission sequencing codes of the current site.
The mission sequencing code is used within the mission sequencing process to determine the type of mission to link. It describes all the mission types by preferred search order.
This mission sequencing is associated with each resource who wishes to use this functionality.
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 sequencing codes supplied along with the various parameters associated with them.
Entry screen
Fields
The following fields are present on this tab :
Block number 1
| Code identifying a mission sequencing rule (defined by site). A mission sequencing code defines the search order of the mission types to follow each other. |
| Long description |
|
| 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. |
Block number 2
Grid Sequencing
| 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
Mission sequencing procedure
Prerequisites
- the mission type of the achieved mission must be authorize the sequencing (in mission setup)
- the resource must have a specific sequencing mode.
Principle
Once the resource has completed a task, and based on the setup (see above), the system can submit a sequencing mission to them.
In addition to the standard controls and authorizations, the system searches a mission taking place in the same mission area of the resource and having a mission type defined in the sequencing mode of the resource. Once the mission is know, the system generates a task and submits it to the resource:
- The resource either accepts this task. Once the task is dealt with, the resource returns to the initial mission submission screen.
- Or the resource refuses this mission, and returns to the initial mission submission screen.
For instance
Let us consider the STORING mission that authorizes mission sequencing.
And a resource having the following sequencing mode: TRFRPNN, TRFSTK
Let us assume that the resource has just completed a task on the STORING mission.
Let us also assume the following mission portfolio (all missions can be carried out by the resource):
mission no.1 TRFRPNN priority 4 - transfer mvt from A1 to A1
mission no.2 TRFRPNN priority 2 - transfer mvt from A2 to A1
mission no.3 TRFRPNN priority 8 - 1 transfer mvt from A1 to A2, 1 transfer mvt from A1 to A3
mission no.3 TRFSTK priority 1 - 1 transfer mvt from A1 to A2, 1 transfer mvt from A3 to A2
Case 1:the resource is located in area A1 at the end of the STORING mission.
The system searches a TRFRPNN mission location in A1 and submits mission no. 1 (mission no. 2 has a higher priority level but its mvt does not start in A1).
Case 2:the resource is located in area A2 at the end of the STORING mission.
The system searches a TRFRPNN mission location in A2 and submits mission no. 2.
Case 3:the resource is located in area A3 at the end of the STORING mission.
The system searches a TRFRPNN mission location in A3 It does not find any mission.
The system searches a TRFSTK mission location in A3 and submits mission no. 4 (the mission will then only consist in the transfer mvt from A3 to A2. The other transfer mvt is not taken into account since it starts with A1, not A3.