Show TOC

Background documentationObject Level Hook Points Locate this document in the navigation structure

 

You set up activity hooks at the object level in Operation Maintenance, Resource Maintenance, Routing Maintenance, and NC Code Maintenance (see Setting Up Activity Hooks).

The figure below shows the object-level hook points that are common to Operation Maintenance, Resource Maintenance, and Routing Maintenance and their relationships to Starts and Completes in the POD:

This graphic is explained in the accompanying text.

Note Note

When the operator selects multiple SFC numbers, either individually or in a shop order or process lot, the system executes the hooked activity for each SFC number selected.

End of the note.

For more information, see Hook Points.

Additional Resource and Operation Level Hook Points

If you want the activity to execute only once for the entire set of SFC numbers, see the table below. The following table describes additional hook points common to the resource and operation level:

Hook Point

When a Hooked Activity Executes

PRE_BATCH_START

After the operator chooses Start, before the system executes the start

POST_BATCH_START

After the operator chooses Start, after the system executes the start

PRE_BATCH_COMPLETE

After the operator chooses Complete, before the system executes the complete

POST_BATCH_COMPLETE

After the operator chooses Complete, after the system executes the complete

Note Note

The system executes the hooked activity only once for all SFC numbers the operator selected.

End of the note.
Additional Operation Level Hook Points

The following table describes additional hook points available only at the operation level:

Hook Point

When a Hooked Activity Executes

PRE_SIGNOFF

After the operator chooses Signoff, before the system executes the signoff

POST_SIGNOFF

After the operator chooses Signoff, after the system executes the signoff

Additional NC Code Level Hook Points

The following table describes additional hook points available only when an operator or machine logs an NC against one or more SFC numbers:

Hook Point

When a Hooked Activity Executes

PRE_DISP

After the operator logs an NC and before the system sends the SFC number to its new destination or state, such as USEABLE_AS_IS

POST_DISP

After the operator logs an NC and after the system sends the SFC number to its new destination or state, such as USEABLE_AS_IS