00196806-02_IM_EDM_1_10_en.pdf - 第43页

EDM V1.10 / Installation Manual 07/2011 Edition 5.2.4.3 User guidance on the ED M Client These parameters spe cify how the various push o perations are presente d to the user at the EDM Client. Setting Default Valid for …

EDM V1.10 / Installation Manual 07/2011 Edition

5.2.4 Configuring push mode

Push mode provides a large number of settings that allow EDM to be tailored to the needs of the

customer.

5.2.4.1 General settings

Setting Default Valid

for

Explanation

EnablePushMode false ALL Activates push mode. This setting

must be enabled on all EDM

computers (EDM Master, EDM

Client and EDM Clearing Pool) that

are to participate in push mode.

Table 5-4: General settings

5.2.4.2 Automatic push in the Clearing Pool

Auto Push can maintain the consistency of the data if a line engineer on an EDM Client makes

changes to an object that are rejected in the Clearing Pool. In this event, the version of the object in

the EDM Master can be automatically transferred to the line. This means that the object on the line

that is invalid from the perspective of the data preparation engineer is replaced by the copy in the

Clearing Pool.

Setting Default Valid

for

Explanation

ClearingPool.AutomaticPush.Enabled false Clearing

pool

Activates Auto Push at the

Clearing Pool.

ClearingPool.AutomaticPush.

RequireConfirmation

true Clearing

pool

Specifies whether the Clearing

Pool should show a confirmation

dialog box on every Auto Push.

Table 5-5: Settings for Auto Push

EDM V1.10 / Installation Manual 07/2011 Edition

5.2.4.3 User guidance on the EDM Client

These parameters specify how the various push operations are presented to the user at the EDM

Client.

Setting Default Valid for Explanation

ConfirmAtLineServer true Data

Transfer

Manager

If set to "true", a confirmation

dialog box is displayed on the EDM

line for the push operations to be

imported. Otherwise, the import is

executed immediately, depending

on the settings described in 0

If Operator

MayOverride.

dual push

ConfirmAtLineServer is

enabled, this setting acts as th

default value and can be

overwritten for each indivi

operation in the Data Transfer

Manager.

AllowReject false Data

fer

hether the line engineer

ride.AllowR

Trans

Manager

Specifies w

is permitted to reject the push

operation (or is forced to impor

pushed objects). If

OperatorMayOver

eject is enabled, this setting acts

as the default value and can be

overwritten for each individual pu

operation in the Data Transfer

Manager.

AllowDelay true Data

fer

hether the line engineer

the

Trans

Manager

Specifies w

is allowed to delay a push.

Delaying causes the GUI on

EDM line to be minimized for a

time to that work on the EDM lin

is not obstructed.

If OperatorMayOverride.

AllowDelay is enabled, this

setting acts as the default value

and can be overwritten for each

individual push operation in the

Data Transfer Manager.

OperatorMayOverride.AllowDelay false Data

fer

rridden in

Trans

Manager

AllowDelay can be ove

the Data Transfer Manager.

OperatorMayOverride.AllowReject false

fer

AllowReject can be overridden Data

Trans

Manager

in the Data Transfer Manager.

OperatorMayOverride.ConfirmAtLine false

fer

ConfirmAtLineServer can be

Server

Data

Trans

Manager

overridden in the Data Transfer

Manager.

Table 5-6: Settings for user guidance

EDM V1.10 / Installation Manual 07/2011 Edition

5.2.4.4 Protection against overwriting current production data

In some cases, it makes sense to suppress the pushing of recipes or boards that are currently

being assembled on the production line. In the initial setting for push mode, the user at the line is

requested to confirm the push and is thus responsible for the decision as to when to import the

data. If this dialog box is not required (e.g. ConfirmAtLineServer is set to "false"), the push

would be executed immediately. The following settings delay import of the data until such time as a

new recipe is specified. The fine settings (EnableLineDataConflictChecks.Board,

EnableLineDataConflictChecks.Job,…) relate to the type of the pushed objects. Dependent

data is not taken into consideration (if, for example, a recipe is being produced that requires setup

A, setup A is nevertheless overwritten if a different recipe with setup A is to be imported).

Setting Default Valid

for

Explanation

EnableLineDataConflictChecks false Line Enables overwrite protection.

EnableLineDataConflictChecks.Board true Line Protects the board currently being

produced.

EnableLineDataConflictChecks.Job false Line Protects the job currently being

produced.

EnableLineDataConflictChecks.

ProductionSchedule

false Line Protects the current production

schedule.

EnableLineDataConflictChecks.Recipe true Line Protects the recipe currently being

produced.

EnableLineDataConflictChecks.Setup true Line Protects the setup currently being

produced.

Table 5-7: Settings to protect against overwriting

5.2.4.5 Settings for the data transfer / push mode GUI

Behavior

Setting Default Valid for Explanation

ClearCommentAfterDataTransfer false Data

Transfer

Manager

Specifies whether the comment

window is to be cleared after the

push operation.

ClearDisplayNameAfterDataTransfer false Data

Transfer

Manager

Specifies whether the display

name is to be cleared after the

push operation.

ClearLineSelectionAfterDataTransfer false Data

Transfer

Manager

Specifies whether the line

selection is to be cleared after the

push operation.

ClearObjectSelectionAfter

DataTransfer

true Data

Transfer

Manager

Specifies whether the object

selection is to be cleared after the

push operation.

Table 5-8: Settings for data transfer - behavior