Workflow Engine. Version All rights reserved.

Transcription

1 Power Pick Global Power Pick Global Workflow Engine Version All rights reserved. Copyright by Kardex Software GmbH, D Wörth, Germany. This document - even partly - must not be printed and/or copied without the agreement of Kardex Software GmbH. Changing in format and content is subject to change without special announcement. All trademarks in this document are property of the respective owner, even though they are not extraordinarily marked.

2 Revision History Date Ver sion 24 March Release February Release March Release February Release 3.1 Description 4 April Transfert from GP.TechnicalHandbook sections Tab position control in Task processor View control in Task Processor Parameters mapping between version 2.3 and April Add additional information about task processor and parameters xx Author Rolf Wilhelm van den Berg Rolf Wilhelm van den Berg Nemrude Verzano Abbas Jamalian Guy Koenig Guy Koenig Page 2 of 38

3 Table of Contents 1. Task Workflow 1.1 Access the Configuration 1.2 List of main parameters 1.3 Label Printing 1.4 Barcode Check 1.5 Confirmation Sequence 1.6 Custom Order of Tasks 2. Area Handling 2.1 Sequence Number 2.2 Bands 2.3 Aisles 3. Operations 3.1 Quantity Confirmation and Discrepancy 3.2 Route Calculation and Optimization 3.3 Sequence Strategy 4. Task Workflow Process Diagrams 4.1 Drive 4.2 Process Single Pick Task 4.3 Process Single Put Task 4.4 Process Single Count Task 4.5 HoriOpt 4.6 Area Handling 5. Task processor 5.1 Default task processor 5.2 Task processor with other dockable panes organization 5.3 Task processor with change in tab sequence and tab name 5.4 Task processor and multiview 5.5 Task processor in single barcode input 6. Dockable panes in Task Processorr 6.1 How to process 6.2 Task Processor Parameter relative to dockable panes 7. Tab position control in Task processor 7.1 Tabs ordering without tab sequence 7.2 Tabs ordering with tab sequence 8. Task processor Parameters Parameters mapping between version 2.3 and Page 3 of 38

4 Workflow Engine 1. Task Workflow 1.1 Access the Configuration All the task workflow s configuration is saved centrally as Station-Based parameter in database and can be accessed in standard way via System Configurator of the software. The task workflow s configuration is available under the group number Page 4 of 38

5 1.2 List of main parameters Number Name Process count Combi picking Strict sequence Serial processing Drive direct on serial processing Sequence strategy step confirmation Confirmation sequence Depict input Hide unused handling units Process busy tasks Understocking pick Overstocking pick Understocking put Overstocking put Accept quantity discrepancy Default motive type pick Default motive type put List of reports Barcode checks Trace methods Trace categories Enable batch on put Custom order of tasks Access Type Description Optional restricts the number of concurrent Processes of the Workflow. The number of concurrent Processes are also limited by the HoriOpt option in the License. Enable or disable combi picking. This is applied only to Pick Tasks and is not supported for Put or Count Tasks. Sets the HoriOpt strategy, can be Parallel HoriOpt or Round Robin or Strict Round Robin. Please see the chapter: Sequence Strategy Unit drives after confirming quantity to next carrier (step 1) and confirmation of handling units is enforced (step 2) Sequence of confirmations. Defaults to Barcode, Quantity, Motive Type, Reason Code Lot, Serialnumber, Expirydate, Productiondate, Releasedate, Qualification, HandlingRank The Fields Near Zero, Motive Type and Reason Code get higher Priority if they are activated based on the value provided in Quantity. Enable or disable depicting the next input expected at unit's last display line(s) Allows understocking for pick Allows overstocking for pick Allows understocking for put Allows overstocking for put Accept quantity discrepancy without further inquiry Motive type defaults to this value if this value differs from NotSet and understocking in a pick occured Motive type defaults to this value if this value differs from NotSet and understocking in a put occured Defines list of available reports List of barcode checks to perform Enables batchlights on storing Comma separated list of items which can be used to order the Tasks. Currently supported the values: Linenumber, Priority, Deadline, Shelfnumber, StorageunitName. Each value can be followed by ASC or DESC for sort direction. Example: Linenumber, Priority, Deadline DESC Specifies how the different dialogs in the software can access the Workflow. Possible values are Exclusive, ExclusiveAndManualHot and Share. Exclusive: Only one dialog can start an order Page 5 of 38

6 Area Change Method Enable Pick And Pass Pass Message Done Message New Message ExclusiveAndManualHot: Only one dialog can start an order, but it is possible to start a manual Hot trannsaction without stopping the workflow. Share: It is possible to start and add orders to the running Workflow. Set the way the Areas are changed. In automatic mode, the Workflow automatically changes the Areas based on their sequence number. In Prompt mode the user will be prompted to choose the Active Area, even if there is only one Area available. It is possible to define Access Points which do not belong to any area, such access points are grouped under default Area or No Area. Enables the Pick and Pass. In Pick and Pass mode a message is displayed on PC and on the last access point showing the storage units for the rest of the order(s) under process. A direct Text or Template used by Pass or Done option. This message will be displayed on Batch Light or Handling Unit Visualizer if the current Handling Unit is finished but the related order has still some positions in other stations. If this Parameter is Empty, the check for the pass is deactivated. Like Pass Message, but it indicates that the current Handling Unit is finished and Order has no more allocated Positions. A direct Text or template which will be sent to batch lights or handling units when a new order starts for the given handling rank. Page 6 of 38

7 1.3 Label Printing Use the Label Printing Dialog under Reporting menu to configure the Workflow printing, or as an alternative use the workflow Parameters directly to configure the reports Report Binding Parameters When selecting 17 List of reports a button appears on the right side. Clicking the button opens a dialog to add, remove or change a report binding. The following example comprises 2 reports: a task list and a material label Activating Remove removes the selected binding, activating Add creates a new report binding. The details of the selected report binding are displayed right hand and may be edited there. GPWorkflow_Parameter_ ReportBindings_Copies ReportBindings_DataReference ReportBindings_Printer ReportBindings_PrintOnState ReportBindings_Report ReportBindings_ReportTag ReportBindings_Sort Name Copies Data reference Printerr Print at Report name Report tag Sort Description Number of copies to print (default 1). If negative the quantities of all tasks involved are multiplied by this value (absolute). Specifies data reference to the report's query (default: TblTask.TaskId=TaskId). Format: <query column name>=<task data field>{,<query column name>=<task data field>}*. Examples: Materialbase.MaterialId=Material.Id History.HandlingUnit=HandlingUnit, HistoryMasterorder.MasterorderName=Masterorder.Name Print with a specific printer with logical binding Defines when to print Report bindings name in workflow Referes to a report's name or tag Specifies sort to apply to the reports query. Example: MasterorderName asc, Linenumber, Quantity desc Page 7 of 38

8 Scope Scope Restricts the scope. Lookup the enumeration values Printing State Print at None Activate Initial TaskStarted Confirming FinishTask Error Stopped FinishHandlingUnit Finished When Data for list Data for label Never None None At activation of an access All tasks to be processed at None point this access point Task has been started (Unit All tasks to be processed at The current task(s) is driving) this access point Task s confirmation has All tasks to be processed at The current task(s) been started (Unit stopped) this access point Current Task is finished All finished Tasks The last Finished Task An error has been All tasks to be processed at The current tasks(s) encountered this access point if available Processing is finished All tasks stopped All tasks stopped Processing of a handling All tasks confirmed for this All tasks confirmed unit has finished handling unit for this handling unit Processing finished All tasks finished All tasks finished Note: For printing on FinishHandlingUnit state, the printer must be chosen in the Report Binding definition. The parameter Scope restricts printing to the orders type. The following entries are currently available: All print always Put print only on order put or manual put Pick print only on order pick or manual pick Return print only on order return or manual return PutOrPick print only on order put, order pick, manual put or manual pick Count print only on count orders Manual print only on manual transactions Order print only on order transactions ManualPick print only on manual pick ManualPut print only on manual put ManualReturn print only on manual return ManualPutOrPick print only on manual put or manual pick ManualCount print only on manual count OrderPick print only on order pick OrderPut print only on order put OrderReturn print only on order return OrderPutOrPick print only on order put or order pick You may specify a printer to use (a logical binding to this printer has to exist) at parameter Printer At parameter Copies you may specify if you want more than one copy. If you set this value to 0 actual printing is prevented. This may be useful if you only want to setup printings If you choose a negative value the absolute value of this parameter is multiplied by the the quantities of all tasks involved. Page 8 of 38

9 1.3.2 Label Printing Dialog Choose a name for the configuration, then choose the Report Name from the list. After selecting a report, all the report fields will be listed. Choose the desired matching field from Task Fields list and add it to the criteria list. Choose the scope and state to identify when and in which condition this report must be printed. Optionally choose a printer, otherwise the matching printer will be chosen based on the bindings. Set the number of copies, which can be also negative value to print n copies for each piece picked. This Dialog is only the UI for the parameters described in the previous section. Page 9 of 38

10 1.4 Barcode Check Barcodes are defined using the Barcode Form under Management Menu. The Barcodes may be assigned to Material Properties for a specific Scope, or can be assigned to Workflow for specificc Scope and zone. In each case, the priority is with the Material Property and if no match is found, the settings from Workflow is used. When selecting 18 Barcode checks a button appears on the right side. Clicking the button opens a dialog to add, remove or change a barcode check. Activating Remove removes the selected barcode check, activating Add creates a new barcode check. The details of the selected barcode check are displayed right hand and may be editedd there. Parameter Name Scope Zone Name Barcode name Scope Zone Description Barcode binding's name as defined in Barcode Management Form. Restricts the scope. Lookup the enumeration values Restricts to a specific zone (all if not specified) Barcode Check for qualification fields In the case of using Barcode check for the fields like Lot, Serial number, etc. the special care must be done for the Barcode check definitions. The first point to consider is that the Barcode check does not collect the data, it only checks the available data for validation. Now for example if a Barcode check is defined for the Lot field and we do a Put and the user is supposed to provide the Lot field on the confirmationn screen, the order of Page 10 of 38

11 confirmation must be set in a way that the user provides first the Lot number, and then scans the Barcode in the Barcode check field. Also the definition of the Barcode is important. The Lot field is available on LocBreakdown as well as Task. In this case, the field Task.Lot must be used for Barcode check definition. Now if we consider the Put, the Lot number is always available during the allocation, means before the confirmation screen. In this case the Barcode Check definition must use LocBreakdown.Lot field. If the Barcode check contains multiple fields in one scan, all the fields must match the input. For example, if the Barcode check is Material-Lot, then both Material name and Lot field must match the data and as described above, the lot number must be provided before scanning the Barcode. Page 11 of 38

12 1.5 Confirmation Sequence The sequence of a confirming process can be defined in the setting and looks like as following: Figure 1: Confirmation Sequence The exact field names as appear in the list shown in the picture must be typed in. 1.6 Custom Order of Tasks It is possible to set the order in which the tasks are processes, the best example for is is to order the tasks on LineNumber. The Custom Order of Tasks is always done in an Scope. As an Example the Line Number is used in the scope of an Order. See the Example below: Order 1, Line 1, Material A Order 1, Line 2, Material B Order 1, Line 3, Material C Order 2, Line 1, Material D Order 2, Line 2, Material E Page 12 of 38

13 In the above example and using the order of Line Number, at the beginning the user may pick either Material A or Material D. Now if the user picks the Material A, immediately it will be possible to pick either Material B or still Material D. Although Material B has Line number 2 which is greater than line number of Material D, but the calculation is done in the scope of the order. There are however other variables which use different scopes. For example Order Deadline has a global scope. Following Table lists all possible sort values with their scopes Variable Linenumber Priority Deadline ShelfNumber StorageunitName Scope Master Order Global Global Storage Unit Global In addition to the values in the above Table, there is a value which will be always considered and it is the Tasksequence which may be internally set by RuleEngine and is not configurable. Page 13 of 38

14 2. Area Handling It is possible to define one or more Areas for each Warehouse. Every Area contains one or more Aisle, and each Aisle contains one or more Access Points. Using the Areas, the processing of the tasks will be done only within one Area at a time. When the processing of Tasks in one Area is finished, user can choose another Area, or system chooses the next Area automatically and process continues in the second Area. Important Note: If a Storage Unit has more than one Access Point, and if there is a station which has logical bindings to more than one Access point of that storage unit, all of those access points must be defined in the same Aisle to be able to use Optimization strategies and Area Handling. 2.1 Sequence Number An Area has a sequence number which can be used to choose the Areas automatically. This will be set using the Settings Area Change Method. If the Settings is set to Prompt, the user will be prompted to choose the current Area, even if there is only one Area for the current Task Processing session. The Access Point which do not belong to Any Area are grouped under a Default Area or also called No Area or Null Area. The Default Area is also treated as an Area and in prompt mode the user must explicitly choose that Area. If the Areas are used, it is recommended to define the Areas for all the access points. 2.2 Bands It is possible to define one or more Band Heights for each Area. If at least one Band is defined, the Pick Banding Option will be activated. Using this features, the Tasks will be sorted based on their Z-Coordinate of their Shelves. It is possible to define up to three Bands. Each Band starts from the point where the previous Band is ended. If a Band is not defined, the higher Bands are not considered. In this way is possible to define only Band1, or Band1 and Band2 or Band1 and Band2 and Band3. Example: Band1 = 1000, Band2 = 2000, Band3 = 1000 Now, first the Tasks which their Shelf s Z-Coordinate are between 0 and 1000 are processed. Then the ones with Z- Coordinate between 1000 and 3000 (Band1 + Band2). Then come the Tasks with Z-Coordinate between 3000 and 4000, and finally the Tasks with Z-Coordinates higher than Aisles An Aisle contains one or more Access Point. Each Access Point in an Aisle has an Orientationn which can be Left or Right, and has a Sequence Number. The Route Optimization can be configured for an Aisle. There are two optimization methods, U-Turn and Zig Zag. The Aisle can have either Front to Back or Back to Front directions. The Direction affects the route optimization. Page 14 of 38

15 2.3.1 Aisle Topology In the following examples, there are four storage units in one Aisle. Each storage unit has an access point in the Aisle. There are three shelves side by side on each level of the storage units. The Shelves are numbered in the shape based on their x-coordinates, since the coordinates start from left. The definition of the Aisle and Access Points must match the physical location of the storage units. This is specified by the sequence number of the Access Points inside an Aisle, as well as their orientation. The Access Points which are nearer to the front side of an Aisle should have less sequence number than the others. In this example the sequence numbers are indicated in the red circles. Storage Storage Unit #3 Unit # Storage Storage Unit #1 Unit #2 Left Aisle Front Right Page 15 of 38

16 2.3.2 U-Turn it starts the Tasks from Lowest sequencee on Left and goes to the higher sequences on the Left. If no more task are available on Left side, it goes to highest sequence on Right and moves toward the lowest sequence. If the Aisle direction is Back to Front, it starts on highest sequence on right side. The Back to front direction of the Aisle is the same process but from the opposite side. The X-Coordinates of the shelves are also considered Zig Zag Using Zig Zag optimization, the processs starts by the lowest access point sequence on the left side and then the opposite access point. If there are no tasks for the opposite Access point on the right, the process continues whit the next access point on the left side. The X-Coordinate of the shelves are also considered. If the direction of the Aisle is Back to front, the same process will be done in reversed direction Sequence Number of Aisless Within an Area, the process will be done Aisle by Aisle using the sequence number of the Aisles. It is possible to configure each aisles separately, hence it is possible to set an Aisle as Back-to-front and the side Aisle as Front to back etc. to configure the whole route within the Area. Page 16 of 38

17 2.3.5 Modeling the Static Shelves To Model the Static Shelves in the software, a Storage Unit must be defined with one access point. The Best practice is to define one carrier and define all the shelves using x-coordinate and z-coordinate. Consider that carriers do not have offsets and they are always the same width as storage units. 3. Operations 3.1 Quantity Confirmation and Discrepancy There are four sources which can be used to confirm the quantity or to change the quantity. Not all the sources can be used to complete the whole process of the quantity discrepancy Main Quantity field Confirming on this field will confirm all the current task and all the tasks chained to the current task in the case of Combi Picking. In the case of two step confirmation, this field can be used to confirm first and second step. Changing the quantity in this field will cause the new distribution of the quantity to Handling Units and Batch Lights. In the case of under-stocking, the software displayss two additional fields for reason code and motive type Machine Panel It is designed for C2000 and C3000 controls and on other hardware types or controllers may work limited due to the hardware restrictions. It is possible to confirm the quantity and change the quantity. Confirming the Motive Type is only possible if the Depict Input is active. Confirming the Reason Code is not possible since this field is optional Batch Lights and Handling Unit Visualizer It s possible to confirm the quantity for each Handling unit. Changing the Quantity is possible for Handling Unit, but it is not possible to complete the quantity discrepancy process on Batch Lights or HU Visualizer. The User must follow the process on either Machine Panel in the case of Depict input or on Task Processor screen to confirm the motive type. After confirming the motive type, the Handling Unit is still not confirmed and must be confirmed once more Motive Types In the case of data entry on machine panel, the numeric values of the motive types must be entered. On Pc it is possible to choose a motive from drop down list. Following Table lists the available motive codes Pick Motive Types NotSet 0 Shortage 1 ConsecutiveAction 2 Reallocate 3 Trim 4 Put Motive Types NotSet 0 Shortage 1 SpaceFull 2 ConsecutiveAction 3 Reallocate 4 Following diagram shows the effects of each Motive Type. Page 17 of 38

18 Shortage Set Location Quantity to zero Order Line is shortned and finished ConsecutiveAction New task for the remaining quantity for the same location will be generated Pick Reallocate Set Location Quantity to zero Allocate remaining quantity Trim Order Line is shortned and finished n Shortage Order Line is shortned and finished Put SpaceFull Set Location to Full Order Line is shortned and finished ConsecutiveAction New task for the remaining quantity for the same location will be generated Reallocate Set Location to Full Allocate remaining quantity 3.2 Route Calculation and Optimization There is a fixed sequence or priority in which the tasks are grouped and sequenced as illustrated below: Sequence Optimization 1 Hot Orders 2 Task.Tasksequencee The Task sequence number which may be set by RuleEngine 3 Custom Sorts. Since it is possible to specify more than one sort item, the priority is by the first item, then second etc. 4 Pick Banding 5 U-Turn or ZigZag The generated sequence from all the above optimizations is considered as a Rule. It is not possible to process a Task with higher sequence if the lower sequenced Tasks are not processed. It is however possible that the Storeg Units drive for two or more Taks with different sequences, however the confirmation is possible only for the lowest sequence. The only exception to this is when during the processing some new orders are inducted to the Workflow (e.g. starting Hot Transactions, or Automatic order processing). In such a cases, the current Task for each storage unit can be processed, even if the storage unit contains the tasks with less sequence than the current Tasks. Page 18 of 38

19 3.3 Sequence Strategy The currently implemented strategies for processing orders are Round Robin and Strict Round Robin and can be configured using Parameter To describe these strategies assume the following scenario shown in Figure 2: four Shuttles with one access point each. Figure 2: Sceneario with four Shuttles Parallel HoriOpt In this case the sequencing of access points are not controlled. Software activates as much access points as possible. However if any Hardware like Batch Light is shared between the access points, only one access point can be activated at any time. But there will be no rule to activate specific access point or follow any specific order. In ParallelHoriOpt mode, the display of machines will be activated at the beginning when the drive command is sent. If the Depict Input option is activated, the name of the expected input will be displayed on the last line of the display. If due to resource sharing only one access point can be activated, the active access point shows the expected input field and other access points only show the text. This is of course depending to the Depict Input setting. In such a cases, the active asccess points are indicated with green Tabs and the other access points are orange. By confirming on a non-active access point, the access point will be activated. The shared resources will be allocated to the newly activated access point. There are cases when an access point cannot be activated, for example when there are rules defined (Hot Orders, Custom Sort, Zig Zag, etc) Round Robin Round Round allows to process the orders in a sequential order based on the name of the access points of the machines. In this case the access points are referred to their machines by using the Each machine has just one access point whereby their names are used to control the sequence. The order of the access point names defines how the sequence of the machines is to be processed. Assume that the user starts to process the orders at the access point AP@S02. The next machine will be AP@S03 if it is available. If not it will be skipped and the next machine in the sequence that is available has to be used by the user. An unavailable machine means in this context that it is busy or has an error. Round Robin is a Directed HoriOpt mode, which means the software leads the user to work with specific machine. In such a case, only the display of one access point is active and all other access points are blank. Confirming Page 19 of 38

20 on blank access points does not activate the corresponding process. However, it is possible to activate those access points directly from PC by clicking on the proper Tab. Like ParallelHoriOpt, it won t be possible to activate an access point if the rules (Hot orders, custom sort, etc.) does not allow it Strict Round Robin This strategy is comparable to but has the difference that the sequence has to be followed. Independently from the status of the next machine in the sequence it is the next machine and will not be skipped. The sequence of the machines has to be processed strictly. Page 20 of 38

21 4. Task Workflow Process Diagrams 4.1 Drive START Find Task best Task for start - Current Tray in Access Point - Next near Carrier for Carousels - Dual Tray - Consider Sequence Number Send drive command (No Text in the case of Blind Drive) Wait Status Change Busy? Yes Notify UI Error? Yes Enable User Input for Confirm / Cancel Ready? Yes END User Input Confirm / Cancel Send Command to Machine Page 21 of 38

22 4.2 Process Single Pick Task START Wait for Resources DRIVE Signal and Wait for Process Activation Update UI Update Machine Panel Update Display Devices Update Pick Light Two Step? Yes Wait for Quantity Confirmation on Machine, PickLight or UI Update Batch Light Wait for Confirmation (Quantity, Lot, Barcode, etc.) Set TASK Ready Page 22 of 38

23 4.3 Process Single Put Task START Wait for Resources Update Batch Light (No Confirmation) DRIVE Signal and Wait for Process Activation Update UI Update Machine Panel Update Display Devices Update Put Light Wait for Confirmation (Quantity, Lot, Barcode, etc.) Set TASK Ready Page 23 of 38

24 4.4 Process Single Count Task START Wait for Resources DRIVE Signal and Wait for Process Activation Update UI (No Quantity Info) Update Machine Panel (No Quantity Info) Update Display Devices (No Quantity Info) Update Put/Pick Light (No Quantity Info) Wait for Quantity Confirmation Warning / Additional Confirmation if Quantity differs than expected value Set TASK Ready Page 24 of 38

25 4.5 HoriOpt START Limit Max Concurrent Processes by chacking License and Settings Dispatch Tasks and drive all the machines in Parallel Wait for Machine Ready Parallel HoriOpt Type? Directed Activate any Task Process on Machine Ready Signal Decide which process may be activated (e.g. based on Round Robin, etc.) Yes More Tasks? END Page 25 of 38

26 4.6 Area Handling START Group the Tasks for Areas Yes More than one Area? Prompt Area Selection HORIOPT Tasks remaining? Yes END Page 26 of 38

27 5. Task processor 5.1 Default task processor For more information about Command bar Dockable panes Tab with storage unit access point See parameter to parameters Use the same dockable pane layout for each direction Parameters , to Task processor with change in tab sequence Section Tab position control in Task processor Page 27 of 38

28 5.2 Task processor with other dockable panes organization 5.3 Task processor with change in tab sequence and tab name Parameters to obtain the previous tab sequence : Parameter and then parameters to Page 28 of 38

29 Tab color Tab color Gray Orange Red Green Signification No task for this access point Task is not started yet Task is finished Access point is busy Error on access point Access point is ready 5.4 Task processor and multiview Page 29 of 38

30 Parameters to obtain the multiview : Parameter and then parameters to Page 30 of 38

31 5.5 Task processor in single barcode input Single barcode input is available for single view or multiview The focus is set in the single barcode input as long as the user does not click in any dockable panes To put the focus again on the single barcode input Click in single barcode textboxx Click on the button in the single barcode input Scanner input is processing only when the focus is set on the single barcode input Parameters to obtain the single barcode input : Parameter and then parameters At least the parameter must be true to use the single barcode input All other parameters from to are linked with the single barcode input 6. Dockable panes in Task Processor Information in Task Processor is spit in many dockable panes. It s possible to hidden, to resize, to move, to pin each dockable pane. Thus the lock of Task Processor can be adapted in a simple and easy manner. 6.1 How to process Right mouse click in Task Processor and choose in the pop-up menu Edit dockable panes Apply the changes (move, hide, resize, regroup the dockage windows) Right mouse click in task Processor and choose in the pop-up menu Save dockable panes Right mouse click in task Processor and choose in the pop-up menu Reset : will return to the default layout Page 31 of 38

32 6.2 Task Processor Parameter relative to dockable panes Parameter Name Use the same dockable pane layout for each direction Description If true all directions have the same dockable pane layout 7. Tab position control in Task processor The couple storage unit access point is the name that appears by default in the Task Processor tab 7.1 Tabs ordering without tab sequence By default Task Processor tabs are sorted by name in each view. With 2 or more views the software first finds the view with the fewest created tabs and adds this new access point. The access point belongs to the view until the last Task Processor client is closed or the area is changed 7.2 Tabs ordering with tab sequence (see parameters to ) Select the access point to consider Define which view hosts the previous selected access point May affect on F-Key to the access point May give the access point a new name to display on the tab Click Keep sequence to add the sequence The order is defined by the tab sequence Select a row and then use arrow up or down to change the tab sequence Page 32 of 38

33 When a new access point must be created and it is not defined in the tab sequence, the software finds the view with the fewest created tabs and adds it to the last position. This access point is included in the view until the last Task Processor client is closed or the area is changed 8. Task processor Parameters Parameter 01 Command bar position 02 Command bar width 03 Command bar Auto Hide 04 Big button in Command bar 05 Show text in Button from Command bar 06 Use the same dockable pane layout for each direction Task Processor Organization Description Command Bar Display: on one side of main windows Width of the Command bar Command bar will be hidden if not active Display large button in command bar Show text in Button from Command bar If true all directions have the same dockable pane layout Read only field for dockable pane layout. Define multiview, tab content, tab visibility, tab sequence, scanner and barcode for the Task Processor dialog Sub parameters under Parameter Description # views in the X direction # views in the Y direction Tab content is hidden during driving Only focused tab has its content visible Concerns only pick order and 2 step confirmation At the first step the application tries to show Default (nothing will change) The dockable pane with the Shelfviewer The dockable pane with the Handling unit Concerns only pick order and 2 step confirmation At the second step the application tries to show Default (nothing will change) The dockablepane with the Shelfviewer The dockable pane with the Handling unit All available access points are displayed at the process start Page 33 of 38

34 Thus all access point binding to the current station are displayed. It does not matter if tasks exist or not for these access point These parameters cannot be used at the same time the parameter The tab is hidden at the end of process. When all task for an access point are finished then this access point is hidden As long as not all task processor client are closed, or area is not change this access point will be displayed at the same place next time it is used This parameters can t be used at the same time the parameter Input fields can be confirmed all at once Per default each mandatory field must be confirmed individually With this option it s possible to confirm all mandatory fields all at once This option is disabled with single barcode input ( ) Concern tab sequence Select the access point to consider Concern tab sequence Define which view hosts the previous selected access point Concern tab sequence May affect a F-Key to the access point The same F-Key can be assigned to a different accesss point Concern tab sequence May give to the access point a new name to display on the tab The new name cannot be empty Sub parameters under relative to single barcode input Parameter Description Use single barcode input It s the minimal setting for using the single barcode input. Each mandatory field must be confirmed individually. The option is disabled Scan at first the access point F-key or its barcode The single barcode input can be used in two ways. First possibility : Scanner is linked to access point Page 34 of 38

35 Scanners are linked to an access point: It can be a strong link (with parameter and ) or a weak link (with parameter ). In this case barcodes are available, quantity discrepancy is allowed Second possibility : Lazy mode Scanners are not linked to an access point The application tries to find the access point which is waiting for this input If no access point is found, or more than one, error provider is displayed in the single barcode input If only one access point is found, the input will be linked to this access point Barcode are not available. Quantity discrepancy is not allowed Scanner Prefix Cannot be empty May select the access point which is linked with this scanner Each time this scanner is used the background color of the single barcode input will have this setting Each time this scanner is used the background color2 of the single barcode input will have this setting Barcode concern only scanner linked with access point Barcode for abort current transaction Barcode concern only scanner linked with access point Barcode for abort all Barcode concern only scanner linked with access point Barcode for skip current transaction Barcode concern only scanner linked with access point Barcode for abort transaction in area Barcode concern only scanner linked with access point Barcode for restart task Barcode concern only scanner linked with access point Barcode for confirm location To change a location, scan first the barcode Confirm location, then scan the new location Barcode concern only scanner linked with access point Barcode for Print Barcode concern only scanner linked with access point Barcode for Confirm Quantity Page 35 of 38

36 In this case no need to scan the exactly expected quantity. Scanning this barcode will confirm the current quantity Barcode concern only scanner linked with access point Select an access point Barcode concern only scanner linked with access point Assign a barcode for the selected access point The application does not check if this barcode is unique 9. Parameters mapping between version 2.3 and Task processor and Task processor Parameters are no more used. Some of them have an equivalent in Task Processor parameters Parameter Description Equivalent in Task Processor 2 parameters Command bar position See Command bar width See Command bar Auto Hide See Big button in Command bar See Show text in button from Command bar Show Material Alias Show Material Information 1 Show Material Information 2 Show Material Information 3 Show Material Information 4 Show Material Information 5 See Page 36 of 38

37 Show Orderline Info 1 Show Orderline Info 2 Show Orderline Info 3 Show Orderline Info 4 Show Orderline Info 5 Show Material Image Grid layout for free locations grid Shelf viewer mode Views X See Views Y See Handling Units Grid Layout of task processor 30 Selected tab for pick Hide display on drive See Selected tab for put Define the storage unit and access point sequence at the screen Show tabs always See See See Page 37 of 38

38 Number of handling units per lane Parameter Description Equivalent in HandlingUnit Rank Parameters Number of handling units per See lane Page 38 of 38