Differentiate parameters

• Differentiate rework count by item reason

• Differentiate rework count by job sequence number

• Differentiate rework count by operation ID

• Differentiate rework count by rework process

• Differentiate rework count by WO ID

Choices Are:

Yes/No

Default:

Yes

Enabled When:

Always

Meaning Depends on the Following Parameters:

None

Description:

These parameters define whether or not to aggregate counts of rework that have a different value for the field named in the parameter.

Counts of the number of times something is reworked are kept in a table called rework_count. This table has fields for the item ID, the lot number, and the sub-lot number, which are used to identify a specific amount of production. Of these, only the item ID is guaranteed to exist, since it is not necessary in MES to use lot numbers or sub-lot numbers (of course, without at least a lot number the system has no good way to track a specific amount of production).

In addition to these fields, there are also fields for the work order ID, the operation ID, and the sequence number of the job; the item reason; and the rework process.

These eight fields together are guaranteed to be unique; that is, each different combination of these field values will have its own row in the rework_count table, and for each row, a rework count is maintained. When rework is reported, only the fields that correspond to the differentiate parameters that are set to Yes will be written to in the rework_count table.

As an example, let’s assume that a given lot of material may not be reworked for the same defect more than three times. In this case, only the Differentiate rework count by item reason parameter would be set to Yes. This means that for a given lot of a given material, different item reason codes (corresponding to different defects) would be recorded separately, and rework for one defect would not count towards rework for another type of defect. However, neither the job generating the rework nor the process used to generate the rework jobs (i.e., the method used to remedy the defect) would be recorded. Therefore, rework for a given defect found in one job would count against the number of times it could be reworked for the same defect in other jobs, even if the different jobs used different dynamic routing processes.