Collection triggers are events or conditions that a transaction must satisfy before quality data collection is invoked. They enable you to tie quality data collection to specific points in your routing, thus ensuring that quality data is recorded as soon as it is available. You can define a unique set of collection triggers for each collection transaction that you associate with a collection plan. You can define as many collection triggers as are required to make data collection as specific as possible.

Defining triggers for a transaction's collection plan is optional. If you define collection triggers for transaction collection plans, Quality data collection is automatically invoked only when all conditions for all or some collection triggers are met.

For example, if you define the following collection triggers for the Move transaction:

• Item = (equals) C45268

• From Operation Sequence Number = (equals) 40

Quality data collection is automatically invoked only when C45268 assembly items are moved out of operation sequence 40. In this example, the triggers work together to ensure that the right data is collected at the right point - operation sequence 40 - a critical inspection point in an assembly's routing.

For information on how to create AND and OR relationships between collection triggers, See: Associating Collection Plans with Transactions.