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 Start
and Complete
in
the POD:
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.
For more information, see Hook Points.
The following table describes additional hook points common to the resource and operation level:
Hook Point |
When a Hooked Activity Executes |
---|---|
|
After the operator chooses |
|
After the operator chooses |
|
After the operator chooses |
|
After the operator chooses |
Note
The system executes the hooked activity only once for all SFC numbers the operator selected.
The following table describes additional hook points available only at the operation level:
Hook Point |
When a Hooked Activity Executes |
---|---|
|
After the operator chooses |
|
After the operator chooses |
The following table describes additional hook points available only when an operator or machine logs an NC code against one or more SFC numbers:
Hook Point |
When a Hooked Activity Executes |
---|---|
|
After the operator logs an NC code and before the system sends the SFC number to its new destination or state, such as |
|
After the operator logs an NC code and after the system sends the SFC number to its new destination or state, such as |