power pick global -...

-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- © 2011 All rights reserved. Copyright by Kardex Software GmbH, D-This document - even partly - must not be printed and/or copied without the agreement of format and content is subject to change without special announcement.All trademarks in this document are property of the respective

Power Pick Global

Power Pick GlobalWorkflow Engine

-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-

-76744 Wörth, Germany. must not be printed and/or copied without the agreement of Kardex Software GmbH

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.

Power Pick Global

Power Pick Global

Workflow Engine

Version 3.1

Kardex Software GmbH. Changing in

owner, even though they are not extraordinarily marked.

Title:

Power Pick Global - Workflow Engine

KARDEX Software GmbH., 2012

Date Ver

sion

24 March 2010 2.1 Release 2.1

11 February 2011 2.3 Release 2.3

28 March 2011 2.3 Release 2.3

21 February 2012 3.1 Release 3.1

4 April 2012 3.1 Transfert from GP.TechnicalHandbook sections

and 3.1

5 April 2012 3.1 Add additional information about task processor and

parameters 200137

Rev:

145

Rev. Date:

07.05.2012

Revision History

Description

Release 2.1 Rolf Wilhelm van den Berg

Release 2.3 Rolf Wilhelm van den Berg

Release 2.3 Nemrude Verzano

Release 3.1 Abbas Jamalian

Transfert from GP.TechnicalHandbook sections

Tab position control in Task processor

View control in Task Processor

Parameters mapping between version 2.3

and 3.1

Guy Koenig

Add additional information about task processor and

parameters 200137-xx

Guy Koenig

Rev. Date:

07.05.2012

of 38

Author

Rolf Wilhelm van den Berg

Rolf Wilhelm van den Berg

Nemrude Verzano

Abbas Jamalian

Guy Koenig

Guy Koenig

Title:



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 Processor

6.1 How to process

6.2 Task Processor Parameter 200137 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 200137

9. Parameters mapping between version 2.3 and 3.1

Rev:

145

Rev. Date:

07.05.2012

Table of Contents

Quantity Confirmation and Discrepancy

Route Calculation and Optimization

Task Workflow Process Diagrams

Task processor with other dockable panes organization

Task processor with change in tab sequence and tab name

processor and multiview

Task processor in single barcode input

Dockable panes in Task Processor

Task Processor Parameter 200137 relative to dockable panes

processor

Tabs ordering without tab sequence

ring with tab sequence

Task processor Parameters 200137

rameters mapping between version 2.3 and 3.1

Rev. Date:

07.05.2012

of 38

4

4 5 7

10 12 12

14

14 14 14

17

17 18 19

21

21 22 23 24 25 26

27

27 28 28 29 31

31

31 32

32

32 32

33

36

Title:



1. Task Workflow

1.1 Access the Configuration

All the task workflow’s configuration is saved centrally as Station

accessed in standard way via System Configurator of the software. The task workflow’s configuration is

available under the group number

Rev:

145

Rev. Date:

07.05.2012

Workflow Engine

All the task workflow’s configuration is saved centrally as Station-Based parameter in database and can be


available under the group number 820101

Rev. Date:

07.05.2012

of 38

Based parameter in database and can be


Title:



1.2 List of main parameters

Number Name

820101-01 Process count

820101-02 Combi picking

820101-03 Strict sequence

820101-04 Serial processing

820101-05 Drive direct on serial

processing

820101-06 Sequence strategy

820101-07 2 step confirmation

820101-08 Confirmation sequence

820101-09 Depict input

820101-10 Hide unused handling units

820101-11 Process busy tasks

820101-12 Understocking pick

820101-13 Overstocking pick

820101-14 Understocking put

820101-15 Overstocking put

820101-16 Accept quantity discrepancy

820101-17 Default motive type pick

820101-18 Default motive type put

820101-19 List of reports

820101-20 Barcode checks

820101-21 Trace methods

820101-22 Trace categories

820101-23 Enable batch on put

820101-24 Custom order of tasks

820101-25 Access Type

Rev:

145

Rev. Date:

07.05.2012

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.

Obsolete

Obsolete

Obsolete

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)

confirmation of handling units is enforced (step 2)

Sequence of confirmations. Defaults to Barcode, Quantity,

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)

Hide unused handling units Obsolete

Obsolete

Allows understocking for pick

Allows overstocking for pick

Allows understocking for put

Allows overstocking for put

Accept quantity discrepancy Accept quantity discrepancy without further inquiry

Motive type defaults to this value if this value differs from NotSet

and understocking in a pick occured


and understocking in a put occured

Defines list of available reports

List of barcode checks to perform

Obsolete

Obsolete

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

Rev. Date:

07.05.2012

of 38

concurrent Processes of the

Workflow. The number of concurrent Processes are also limited by

This is applied only to Pick Tasks

Sets the HoriOpt strategy, can be Parallel HoriOpt or Round Robin or

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

Lot, Serialnumber, Expirydate, Productiondate,

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

Accept quantity discrepancy without further inquiry



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

Specifies how the different dialogs in the software can access the

Workflow. Possible values are Exclusive, ExclusiveAndManualHot

Title:



820101-26 Area Change Method

820101-27 Enable Pick And Pass

820101-28 Pass Message

820101-29 Done Message

820101-30 New Message

Rev:

145

Rev. Date:

07.05.2012

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.

Rev. Date:

07.05.2012

of 38

one dialog can start an order, but it is

possible to start a manual Hot trannsaction without stopping the

Share: It is possible to start and add orders to the running Workflow.

utomatic 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

long to any area, such access points are

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

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

still some positions in other stations. If this Parameter is

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.

Title:



1.3 Label Printing

Use the Label Printing Dialog under Reporting menu to configure the Workflow

use the workflow Parameters directly to configure the reports

1.3.1 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 ha

GPWorkflow_Parameter_ Name

ReportBindings_Copies Copies

ReportBindings_DataReference Data

reference

ReportBindings_Printer Printer

ReportBindings_PrintOnState Print at

ReportBindings_Report Report

name

ReportBindings_ReportTag Report tag

ReportBindings_Sort Sort

Rev:

145

Rev. Date:

07.05.2012

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


eport binding.

The following example comprises 2 reports: a task list and a material label


The details of the selected report binding are displayed right hand and may be edited there.

Description

Copies Number of copies to print (default 1). If negative the quantities of all

tasks involved are multiplied by this value (absolute)

reference

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

Printer Print with a specific printer with logical binding

Print at Defines when to print

Report

Report bindings name in workflow

Report tag Referes to a report's name or tag

Specifies sort to apply to the reports query.

Example: MasterorderName asc, Linenumber, Quantity desc

Rev. Date:

07.05.2012

of 38

printing, or as an alternative



nd and may be edited there.

Number of copies to print (default 1). If negative the quantities of all

tasks involved are multiplied by this value (absolute).

<query column name>=<task data field>{,<query column

History.HandlingUnit=HandlingUnit,

HistoryMasterorder.MasterorderName=Masterorder.Name

Print with a specific printer with logical binding

Linenumber, Quantity desc

Title:



Scope Scope

Printing State

Print at When

None Never

Activate

Initial

At activation of an access

point

TaskStarted Task has been started (Unit

is driving)

Confirming Task’s confirmation has

been started (Unit stopped)

FinishTask Current Task is finished

Error An error has been

encountered

Stopped Processing is

FinishHandlingUnit Processing of a handling

unit has finished

Finished Processing finished

Note: For printing on FinishHandlingUnit

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 thi

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

tasks involved.

Rev:

145

Rev. Date:

07.05.2012

Restricts the scope. Lookup the enumeration values

Data for list Data for label

None None

At activation of an access All tasks to be processed at

this access point

None

Task has been started (Unit

is driving)

All tasks to be processed at

this access point

The current task(s)

Task’s confirmation has

been started (Unit stopped)


this access point

The current task(s)

Current Task is finished All finished Tasks The

Task

An error has been

encountered


this access point

The current tasks(s)

if available

Processing is finished All tasks stopped All tasks stopped

Processing of a handling

unit has finished

All tasks confirmed for this

handling unit

All tasks confirmed

for this handling unit

Processing finished All tasks finished All tasks

FinishHandlingUnit state, the printer must be chosen in the Report Binding definition.


print always

nt only on order put or manual put

print only on order pick or manual pick

print only on order return or manual return

print only on order put, order pick, manual put or manual pick

print only on count orders

print only on manual transactions

print only on order transactions

print only on manual pick

print only on manual put

print only on manual return

print only on manual put or manual pick

print only on manual count

print only on order pick

print only on order put

print only on order return

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.


the absolute value of this parameter is multiplied by the

Rev. Date:

07.05.2012

of 38


Data for label

None

None

The current task(s)

The current task(s)

The last Finished

Task

The current tasks(s)

if available

All tasks stopped

All tasks confirmed

for this handling unit

All tasks finished

state, the printer must be chosen in the Report Binding definition.


print only on order put, order pick, manual put or manual pick

s printer has to exist) at parameter Printer


the absolute value of this parameter is multiplied by the the quantities of all

Title:



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 pr

copies, which can be also negative value to print ‘n’ copies for each piece picked.

for the parameters described in the previous section.

Rev:

145

Rev. Date:

07.05.2012


will be listed. Choose the desired matching field from Task Fields list and add it to the criteria


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.

Rev. Date:

07.05.2012

of 38


will be listed. Choose the desired matching field from Task Fields list and add it to the criteria


inter will be chosen based on the bindings. Set the number of

This Dialog is only the UI

Title:



1.4 Barcode Check

Barcodes are defined using the Barcode Form under Management Menu.

Material Properties for a specific Scope, or can be assigned to Workflow for specific Scope and zone. In each

case, the priority is with the Material Property and i

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 edited there.

Parameter Name

Name Barcode name

Scope Scope

Zone Zone

1.4.1 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 confirmation screen, the order of

Rev:

145

Rev. Date:

07.05.2012

s are defined using the Barcode Form under Management Menu. The Barcodes may be assigned to


case, the priority is with the Material Property and if no match is found, the settings from Workflow is used.


add, remove or change a barcode check.


the selected barcode check are displayed right hand and may be edited there.

Description

Barcode name Barcode binding's name as defined in Barcode

Management Form.


Restricts to a specific zone (all if not specified)

Barcode Check for qualification fields



ata for validation. Now for example if a Barcode check is defined for the Lot field


Rev. Date:

07.05.2012

of 38

The Barcodes may be assigned to


f no match is found, the settings from Workflow is used.



the selected barcode check are displayed right hand and may be edited there.

as defined in Barcode


Restricts to a specific zone (all if not specified)



ata for validation. Now for example if a Barcode check is defined for the Lot field


Title:



confirmation must be set in a way that the user provides first th

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

the Barcode check is “Material

described above, the lot number must be provided before scanning the Barcode.

Rev:

145

Rev. Date:

07.05.2012

confirmation must be set in a way that the user provides first the Lot number, and then scans the Barcode in the



w if we consider the Put, the Lot number is always available during the allocation, means before the


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.

Rev. Date:

07.05.2012

of 38

e Lot number, and then scans the Barcode in the



w if we consider the Put, the Lot number is always available during the allocation, means before the


, all the fields must match the input. For example, if

Lot”, then both Material name and Lot field must match the data and as

Title:



1.5 Confirmation Sequence

The sequence of a confirming process can be defined in the setting 820101

The exact field names as appear in the list shown in the picture must be typed

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

Rev:

145

Rev. Date:

07.05.2012

The sequence of a confirming process can be defined in the setting 820101-08 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.



scope of an Order. See the Example below:

Rev. Date:

07.05.2012

of 38

and looks like as following:



Title:



In the above example and using the order of Line Number, at the beginni

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

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

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.

Rev:

145

Rev. Date:

07.05.2012

In the above example and using the order of Line Number, at the beginning the user may pick either Material A or


Material D. Although Material B has Line number 2 which is greater than line number of Material D


Deadline has a global scope. Following Table lists all possible sort values with their scopes

Scope

Master Order

Global

Global

Storage Unit

Global


RuleEngine and is not configurable.

Rev. Date:

07.05.2012

of 38

ng the user may pick either Material A or


Material D. Although Material B has Line number 2 which is greater than line number of Material D, but the calculation



Title:



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

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,

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

820101-26 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.

will be activated. Using this features, the Tasks will be sorted based on their “Z

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 between 1000 and 3000 (Band1 + Band2). Then come the Tasks with Z

and finally the Tasks with Z-Coordinates higher than 4000

2.3 Aisles

An Aisle contains one or more Access Point. Each Access Point in an Aisle has an Orientation 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

affects the route optimization.

Rev:

145

Rev. Date:

07.05.2012


contains one or more Access Points. Using the Areas, the processing of the tasks will be done only within one Area at a


Area automatically and process continues in the second Area.

e than one Access Point, and if there is a station which has logical bindings to more than one


Optimization strategies and Area Handling.


26 Area Change Method. If the Settings is set to Prompt, the user will be prompted to choose the current Area,

if there is only one Area for the current Task Processing session. The Access Point which do not belong to Any


the user must explicitly choose that Area. If the Areas are used, it is recommended to

define the Areas for all the access points.

It is possible to define one or more Band Heights for each Area. If at least one Band is defined, the Pick Banding Op

Using this features, the Tasks will be sorted based on their “Z-Coordinate” of their Shelves.


the higher Bands are not considered. In this way is possible to define only Band1, or Band1 and Band2 or

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,

Coordinates higher than 4000

Point. Each Access Point in an Aisle has an Orientation which can be Left or

The Route Optimization can be configured for an Aisle. There are two optimization

Turn and Zig Zag. The Aisle can have either Front to Back or Back to Front directions. The Direction

Rev. Date:

07.05.2012

of 38


be done only within one Area at a


and if there is a station which has logical bindings to more than one



26 Area Change Method. If the Settings is set to Prompt, the user will be prompted to choose the current Area,

if there is only one Area for the current Task Processing session. The Access Point which do not belong to Any


the user must explicitly choose that Area. If the Areas are used, it is recommended to

If at least one Band is defined, the Pick Banding Option

Coordinate” of their Shelves. It is


the higher Bands are not considered. In this way is possible to define only Band1, or Band1 and Band2 or

1000 are processed. Then the ones with Z-

Coordinate between 3000 and 4000,

Point. Each Access Point in an Aisle has an Orientation which can be Left or

The Route Optimization can be configured for an Aisle. There are two optimization

Back or Back to Front directions. The Direction

Title:



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

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

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

1

2

3

3

2

1

Aisle F

ront

3

2

1

Storage

Unit #1

1

2

3

Storage

Unit #2

Storage

Unit #3

Storage

Unit #4

Right Left

1

3

Rev:

145

Rev. Date:

07.05.2012


Aisle. There are three shelves side by side on each level of the storage units. The Shelves are numbered in the

coordinates, since the coordinates start from left.


pecified by the sequence number of the Access Points inside an Aisle, as well as their orientation. The Access


example the sequence numbers are indicated in the red circles.

Storage

Unit #2

Storage

Unit #4

2

4

Rev. Date:

07.05.2012

of 38


on each level of the storage units. The Shelves are numbered in the


Access Points inside an Aisle, as well as their orientation. The Access


Title:



2.3.2 U-Turn

it starts the Tasks from Lowest sequence 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

but from the opposite side. The X-Coordinates of the shelves are also considered.

2.3.3 Zig Zag

Using Zig Zag optimization, the process 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.

2.3.4 Sequence Number of Aisles

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

etc. to configure the whole route within the Area.

Rev:

145

Rev. Date:

07.05.2012



ck to Front, it starts on highest sequence on right side. The Back to front direction of the Aisle

Coordinates of the shelves are also considered.

optimization, the process starts by the lowest access point sequence on the left side and then the opposite


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 Aisles

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.

Rev. Date:

07.05.2012

of 38



ck to Front, it starts on highest sequence on right side. The Back to front direction of the Aisle is the same process

optimization, the process starts by the lowest access point sequence on the left side and then the opposite


Coordinate of the shelves are also considered. If the direction of the Aisle is Back to front,

done Aisle by Aisle using the sequence number of the Aisles. It is possible to

front and the side Aisle as Front to back

Title:



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

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.

3.1.1 Main Quantity field

Confirming on this field will confirm all the curre

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 qu

of under-stocking, the software displays two additional fields for reason code and motive type.

3.1.2 Machine Panel

It is designed for C2000 and C3000 controls and on other hardware types or controllers ma

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 optio

3.1.3 Batch Lights and Handling Unit Visualiz

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 V

the process on either Machine Panel in the case of Depict inp

After confirming the motive type, the Handling Unit is still not confirmed and must be confirmed once mo

3.1.4 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

Following diagram shows the effects of each Motive Type.

Rev:

145

Rev. Date:

07.05.2012

Modeling the Static Shelves


to define one carrier and define all the shelves using x-Coordinate and z-Coordinate. Consider that carriers

offsets and they are always the same width as storage units.

Quantity Confirmation and Discrepancy


used to complete the whole process of the quantity discrepancy.

Confirming on this field will confirm all the current task and all the tasks chained to the current task in the case of


the quantity in this field will cause the new distribution of the quantity to Handling Units and Batch Lights. In the case

, the software displays two additional fields for reason code and motive type.

It is designed for C2000 and C3000 controls and on other hardware types or controllers may work limited due to the


possible if the Depict Input is active. Confirming the Reason Code is not possible since this field is optio

ights and Handling Unit Visualizer


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 mo


to choose a motive from drop down list. Following Table lists the available motive codes

Put Motive Types

NotSet 0

Shortage 1

SpaceFull 2

ConsecutiveAction 3

Reallocate 4

Following diagram shows the effects of each Motive Type.

Rev. Date:

07.05.2012

of 38


Coordinate. Consider that carriers do not have


nt task and all the tasks chained to the current task in the case of


antity to Handling Units and Batch Lights. In the case

, the software displays two additional fields for reason code and motive type.

work limited due to the


possible if the Depict Input is active. Confirming the Reason Code is not possible since this field is optional.


isualizer. The User must follow

ut 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.


0

1

2

3

4

Title:



Pick

Shortage

ConsecutiveAction

Reallocate

Trim

Put

Shortage

ConsecutiveAction

SpaceFull

Reallocate

n

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.Tasksequence

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 proces

even if the storage unit contains the tasks with less sequence

Rev:

145

Rev. Date:

07.05.2012

Set Location Quantity to zero

Set Location Quantity to zero

Allocate remaining quantity

Order Line is shortned and

finished


finished

New task for the remaining quantity for the same location will be generated


finished

Set Location to FullOrder Line is shortned and

finished

New task for the remaining quantity for the same location will be generated

Set Location to FullAllocate remaining

quantity

Optimization


Task.Tasksequence – The Task sequence number which may be set by RuleEngine

ce it is possible to specify more than one sort item, the priority is by the first

item, then second etc.



ks with different sequences, however the confirmation is possible only for the lowest sequence. The


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.

Rev. Date:

07.05.2012

of 38


The Task sequence number which may be set by RuleEngine

ce it is possible to specify more than one sort item, the priority is by the first



ks with different sequences, however the confirmation is possible only for the lowest sequence. The


sing). In such a cases, the current Task for each storage unit can be processed,

Title:



3.3 Sequence Strategy

The currently implemented strategies for processing orders are Round

configured using Parameter 82010106. To describe these strategies assume the following scenario shown in

four Shuttles with one access point each.

AP@S01

3.3.1 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.

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 depend

points are indicated with green Tabs and the other access points are orange. By confirming on a non

the access point will be activated. The shared resources will be a

cases when an access point cannot be activated, for example when there are rules defined (Hot Orders, Custom Sort, Zig

Zag, etc).

3.3.2 Round Robin

Round Round allows to process the orders in a sequential

In this case the access points are referred to their machines by using the postfix @MachineName. Each machine has just

one access point whereby their names are used to control the sequence. The

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 th

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

Rev:

145

Rev. Date:

07.05.2012

The currently implemented strategies for processing orders are Round Robin and Strict Round Robin

. To describe these strategies assume the following scenario shown in

s with one access point each.

AP@S02 AP@S03

Figure 2: Sceneario with four Shuttles



re will be no rule to activate specific access point or follow any specific order.


expected input will be displayed on the last line of the display. If due to resource


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

the access point will be activated. The shared resources will be allocated to the newly activated access point. There are


process the orders in a sequential order based on the name of the access points of the machines.


one access point whereby their names are used to control the sequence. The order of the access point names defines how


AP@S02. The next machine will be AP@S03 if it is available. If not it will be skipped and th


Round Robin is a Directed HoriOpt mode, which means the software leads the user to work with specific


Rev. Date:

07.05.2012

of 38

Strict Round Robin and can be

. To describe these strategies assume the following scenario shown in Figure 2:

AP@S04



re will be no rule to activate specific access point or follow any specific order. In ParallelHoriOpt


expected input will be displayed on the last line of the display. If due to resource


ing 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,

llocated to the newly activated access point. There are


order based on the name of the access points of the machines.


order of the access point names defines how


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


Round Robin is a Directed HoriOpt mode, which means the software leads the user to work with specific


Title:



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.

3.3.3 Strict Round Robin

This strategy is comparable to 3.3.1 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

has to be processed strictly.

Rev:

145

Rev. Date:

07.05.2012


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.

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

Rev. Date:

07.05.2012

of 38


from PC by clicking on the proper Tab. Like ParallelHoriOpt, it won’t be possible to activate an access

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

Title:



4. Task Workflow Process Diagrams

4.1 Drive

START

Find Task best Task for start

Busy?

Send drive command (No

Text in the case of Blind

Drive)

Wait Status Change

Error?

Ready?

Rev:

145

Rev. Date:

07.05.2012

Task Workflow Process Diagrams

Yes

- Current Tray in Access Point

- Next near Carrier for Carousels

- Dual Tray

- Consider Sequence Number

Notify UI

Enable User Input for

Confirm / Cancel

Yes

END

Yes User Input

Confirm / Cancel

Send Command to

Machine

Rev. Date:

07.05.2012

of 38

Confirm / Cancel

Send Command to

Title:



4.2 Process Single Pick Task

Update Machine Panel

Two Step?

Update Batch Light

Wait for Confirmation

(Quantity, Lot, Barcode, etc.)

Wait for Quantity Confirmation on

Machine, PickLight or UI

Set TASK Ready

Yes

Update UI

Rev:

145

Rev. Date:

07.05.2012

START

Wait for Resources

Update Display Devices Update Machine Panel

Wait for Quantity Confirmation on

Machine, PickLight or UI

Update Pick Light

Signal and Wait for Process

Activation

DRIVE

Rev. Date:

07.05.2012

of 38

Update Pick Light

Title:



4.3 Process Single Put Task

Wait for Resources


Update Batch Light

(No Confirmation)

Wait for Confirmation

(Quantity, Lot, Barcode, etc.)

Set TASK Ready

Update UI


Activation

Rev:

145

Rev. Date:

07.05.2012

START

Wait for Resources

Update Display Devices Update Machine Panel Update Put Light


Activation

DRIVE

Rev. Date:

07.05.2012

of 38

Update Put Light

Title:



4.4 Process Single Count Task

Wait for Resources


(No Quantity Info)

Wait for Quantity Confirmation

Set TASK Ready

Update UI

(No Quantity Info)


Activation

Warning / Additional

Confirmation if Quantity differs

than expected value

Rev:

145

Rev. Date:

07.05.2012

START

Wait for Resources

Update Display Devices

(No Quantity Info)


(No Quantity Info)

Confirmation

Set TASK Ready

Update Put/Pick Light

(No Quantity Info)


Activation

DRIVE

Confirmation if Quantity differs

Rev. Date:

07.05.2012

of 38

Update Put/Pick Light

(No Quantity Info)

Title:



4.5 HoriOpt

Limit Max Concurrent Processes

by chacking License and Settings

Wait for

Dispatch Tasks and

machines in Parallel

Parallel

Activate any Task Process on

Machine Ready Signal

Rev:

145

Rev. Date:

07.05.2012

START

Limit Max Concurrent Processes

by chacking License and Settings

END

Wait for Machine Ready

Decide which process may be

activated (e.g. based on Round

Robin, etc.)

Dispatch Tasks and drive all the

machines in Parallel

HoriOpt

Type?

Directed

More

Tasks?

Rev. Date:

07.05.2012

of 38

Yes

Title:



4.6 Area Handling

START

Group the Tasks for Areas

More than

one Area?

Yes

Rev:

145

Rev. Date:

07.05.2012

END

Yes

Prompt Area Selection

HORIOPT

Tasks

remaining?

Yes

Rev. Date:

07.05.2012

of 38

Title:



5. Task processor

5.1 Default task processor

For more information about

Command bar

Dockable panes

Tab with storage unit –access point

Rev:

145

Rev. Date:

07.05.2012

See

parameter 200137-01 to 200137

parameters 200137-06

Use the same dockable pane layout for each direction

Parameters 20137-12

200137-220, 200137-221

200137-230 to 200137

Task processor with change in tab sequence

Section Tab position control in Task processor

Rev. Date:

07.05.2012

of 38

01 to 200137-05

layout for each direction

221

230 to 200137-230

Task processor with change in tab sequence


Title:



5.2 Task processor with other dock

5.3 Task processor with change in tab sequence

Parameters to obtain the previous tab sequence : Parameter 200137

Rev:

145

Rev. Date:

07.05.2012

Task processor with other dockable panes organization

Task processor with change in tab sequence and tab name

Parameters to obtain the previous tab sequence : Parameter 200137-12 and then parameters 200137

Rev. Date:

07.05.2012

of 38

12 and then parameters 200137-230 to 200137-233

Title:



Tab color

Tab color

Gray

Orange

Red

Green

5.4 Task processor and multiview

Rev:

145

Rev. Date:

07.05.2012

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

Task processor and multiview

Rev. Date:

07.05.2012

of 38

Title:



Parameters to obtain the multiview : Parameter 200137

Rev:

145

Rev. Date:

07.05.2012

Parameters to obtain the multiview : Parameter 200137-12 and then parameters 200137-200 to 200137

Rev. Date:

07.05.2012

of 38

200 to 200137-201

Title:



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 no

To put the focus again on the single barcode input

• Click in single barcode textbox

• 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 inp

At least the parameter 200137-240 must be true to use the single barcode input

All other parameters from 200137-241 to 20137

6. Dockable panes in Task Processor

Information in Task Processor is spit

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

• Apply the changes (move, hide, resize, regroup the dockage windows)

• Right mouse click in task Processor and choose in the pop

•

• Right mouse click in task Processor and choose in the pop

Rev:

145

Rev. Date:

07.05.2012

Task processor in single barcode input

Single barcode input is available for single view or multiview

input as long as the user does not click in any dockable panes

t the focus again on the single barcode input

Click in single barcode textbox

Click on the button in the single barcode input

processing only when the focus is set on the single barcode input

Parameters to obtain the single barcode input : Parameter 200137-12 and then parameters 200137

240 must be true to use the single barcode input

241 to 20137-261 are linked with the single barcode input

in Task Processor

on in Task Processor is spit in many dockable panes. It’s possible to hidden, to resize, to move, to pin


e 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”

task Processor and choose in the pop-up menu Reset : will return

Rev. Date:

07.05.2012

of 38

t click in any dockable panes

12 and then parameters 200137-240

in many dockable panes. It’s possible to hidden, to resize, to move, to pin


up menu “Edit dockable panes”

up menu “Save dockable panes”

return to the default layout

Title:



6.2 Task Processor Parameter 200137 relative to dockable panes

Parameter Name

200137-

06

Use the same dockable pane


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

point.

The access point belongs to the view until the last Task Processor client is closed o

7.2 Tabs ordering with tab sequence

(see parameters 200137-230 to 200137

Select the access point to consider

Define which view hosts the previous selected access point 200137

May affect

May give the access point a new name to display on the tab 200137

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

Rev:

145

Rev. Date:

07.05.2012

Task Processor Parameter 200137 relative to dockable panes

Description

Use the same dockable pane


If true all directions have the

same dockable pane layout


access point is the name that appears by default in the Task Processor tab

ithout tab sequence

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

The access point belongs to the view until the last Task Processor client is closed or the area is changed

ith tab sequence

230 to 200137-233)

Select the access point to consider 200137-230

Define which view hosts the previous selected access point 200137

affect on F-Key to the access point 200137-232

give the access point a new name to display on the tab 200137

Click “Keep sequence” to add the sequence

The order is defined by the tab sequence

a row and then use arrow up or down to change the tab

Rev. Date:

07.05.2012

of 38

If true all directions have the

same dockable pane layout

access point is the name that appears by default in the Task Processor tab

created tabs and adds this new access

r the area is changed

Define which view hosts the previous selected access point 200137-231

give the access point a new name to display on the tab 200137-233

a row and then use arrow up or down to change the tab sequence

Title:



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

last Task Processor client is closed or the area is changed

8. Task processor Parameters 200137

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


07-11

12 Task Processor Organization

Sub parameters under 200137-

Parameter

200137-200

200137-201

200137-210

200137-211

200137-213

200137-214

200137-220

Rev:

145

Rev. Date:

07.05.2012


created tabs and adds it to the last position. This access point is included

client is closed or the area is changed

Task processor Parameters 200137

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

-12

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

Rev. Date:

07.05.2012

of 38


is included in the view until the

Command Bar Display: on one side of main windows

have the same dockable pane layout

Define multiview, tab content, tab visibility, tab sequence, scanner and

ed at the process start

Title:



200137-221

200137-222

200137-230

200137-231

200137-232

200137-233

Sub parameters under 200137-

Parameter

200137-240

200137-241

Rev:

145

Rev. Date:

07.05.2012

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

200137-221

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

used

This parameters can’t be used at the same time the parameter 200137

220

Input fields can be confirmed all at once

Per default each mandatory field must be confirmed

With this option it’s possible to confirm all mandatory fields

once

This option is disabled with single barcode input (200137

Concern tab sequence

Select the access point to consider


Define which view hosts the previous selected access point


May affect a F-Key to the access point

The same F-Key can be assigned to a different access point


May give to the access point a new name to display on the tab

The new name cannot be empty

-12 relative to single barcode input

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

200137-22 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

Rev. Date:

07.05.2012

of 38

Thus all access point binding to the current station are displayed. It

t matter if tasks exist or not for these access point

t be used at the same time the parameter

hidden at the end of process. When all task for an access

or area is not change

at the same place next time it is

This parameters can’t be used at the same time the parameter 200137-

individually

With this option it’s possible to confirm all mandatory fields all at

with single barcode input (200137-240)

Define which view hosts the previous selected access point

different access point

give to the access point a new name to display on the tab

It’s the minimal setting for using the single barcode input.

Each mandatory field must be confirmed individually. The option

Scanner is linked to access point

Title:



200137-242

200137-243

200137-244

200137-245

200137-250

200137-251

200137-252

200137-253

200137-254

200137-255

200137-256

200137-257

Rev:

145

Rev. Date:

07.05.2012

Scanners are linked to an access point:

It can be a strong link (with parameter 200137-242 and 200137

243) or a weak link (with parameter 200137-241).

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 i

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

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 for abort all


Barcode for skip current transaction


Barcode for abort transaction in area


Barcode for restart task


Barcode for confirm location

To change a location , scan first the barcode “Confirm location”, then

scan the new location


Barcode for Print


Barcode for Confirm Quantity

Rev. Date:

07.05.2012

of 38

242 and 200137-

241).

In this case barcodes are available, quantity discrepancy is

t which is waiting for

error provider is

nd, the input will be linked to this

discrepancy is not allowed

select the access point which is linked with this scanner

Each time this scanner is used the background color of the single

Each time this scanner is used the background color2 of the single

nner linked with access point





with access point

To change a location , scan first the barcode “Confirm location”, then


only scanner linked with access point

Title:



200137-260

200137-261

9. Parameters mapping between version 2.3 and 3.1

9.1.1 200122 Task processor and 200137 Task processor

Parameters 200122 are no more used. Some of them have an equivalent in Task Processor parameters

Parameter Description

200122-

01

Command bar position

200122-

02

Command bar width

200122-

03

Command bar Auto Hide

200122-

04

Big button in Command bar

200122-

05

Show text in button from

Command bar

200122-

12

Show Material

200122-

13

Show Material Information 1

200122-

14


200122-

15


200122-

16


200122-

17


Rev:

145

Rev. Date:

07.05.2012

In this case no need to scan the exactly expected quantity. Scan

this barcode will confirm the current quantity


Select an access point


Assign a barcode for the selected access point

The application does not check if this barcode is unique

Parameters mapping between version 2.3 and 3.1

Task processor and 200137 Task processor

Parameters 200122 are no more used. Some of them have an equivalent in Task Processor parameters

Description Equivalent in Task Processor 2 parameters 200137

Command bar position See 200137-01

Command bar width See 200137-02

Command bar Auto Hide See 200137-03

Big button in Command bar See 200137-04

Show text in button from

Command bar

See 200137-05

Show Material Alias Obsolete

Show Material Information 1 Obsolete





Rev. Date:

07.05.2012

of 38

the exactly expected quantity. Scanning



Assign a barcode for the selected access point

t check if this barcode is unique

Parameters 200122 are no more used. Some of them have an equivalent in Task Processor parameters 200137

Equivalent in Task Processor 2 parameters

01

02

03

04

05

Title:



200122-

18

Show Orderline Info 1

200122-

19


200122-

20


200122-

21


200122-

22


200122-

23

Show Material Image

200122-

24

Grid layout for free locations grid

200122-

25

Shelf viewer mode

200122-

26

Views X

200122-

27

Views Y

200122-

28

Handling Units Grid Layout of

task processor

200122-

29

Hide display on drive

200122-30 Selected tab for pick

200122-

31

Selected tab for put

200122-

32

Define the storage unit and

access point sequence at the

screen

200122-

33

Show tabs always

Rev:

145

Rev. Date:

07.05.2012

Show Orderline Info 1 Obsolete





Show Material Image Obsolete

Grid layout for free locations grid Obsolete

Shelf viewer mode Obsolete

Views X See 200137-12

Views Y See 200137-12

Handling Units Grid Layout of

task processor

Obsolete

Hide display on drive See 200137-12

Selected tab for pick See

200137-12 – 213

200137-12 – 214

Selected tab for put Obsolete

Define the storage unit and

access point sequence at the

See

200137-12 – 230

200137-12 – 231

200137-12 – 232

200137-12 – 233

Show tabs always See

200137-12 – 211

200137-12 – 220

200137-12 – 221

Rev. Date:

07.05.2012

of 38

12 – 200

12 – 201

12 – 210

213

214

230

231

232

233

211

220

221

Title:



9.1.2 200104-17 Number of handling units per lane

Parameter Description

200104-

17

Number of handling units per

lane

Rev:

145

Rev. Date:

07.05.2012

Number of handling units per lane

Description Equivalent in HandlingUnit Rank

Parameters 300203

Number of handling units per See 300203-01

Rev. Date:

07.05.2012

of 38

HandlingUnit Rank

01

power pick global -...

Documents