What follows here is a general discussion of collection plans.
Actions can be specific to Work in Process, such as the Put the job on hold action. You can also add message, alert and user-defined actions. See: Application Specific Actions, Message Actions, Alert Actions, and User-Defined Actions.
You can make the entry of quality data mandatory for the move transaction by setting its Mandatory option. If data entry is required, you cannot save the parent transaction, in this case the move transaction, without entering quality data. See Mandatory Data Collection.
You can also specify that data should be collected in the background. As you save the move transaction, the system searches for valid background collection plans. Valid collection plans are those that are associated with the Move Transaction collection transaction and are set to background data collection. See: Background Data Collection.
You can define one or more collection triggers for each collection transaction. Collection triggers allow you to specify the conditions under which quality data collection is invoked as move transactions are entered.
Overview of Shop Floor Control
Defining Collection Elements
Creating Collection Plans
Quality Collection Transactions
Entering Quality Results for Move Transactions