Exception Management Rules#
Exception Management rules are used to detect Exception Management violations. An Exception Management rule tests a particular indicator for a specific pattern. These rules are expected to be triggered as Manual or Automatic Actions on Checklist Items added in Checklists of scope Exception Management. This is, Exception Management rules are triggered by Protocol Instances used in Checklists.
| Rule Name | Description |
|---|---|
| ExceptionManagementHoldMaterial | For each Top-Most Material in the Protocol Instance, the rule will: a) Look for the first hold reason in the Material step that is still not assigned to the Material. If no reason is found, the system will not process information. b) Put the Material on hold (applicable for each Top-Most Material in the Protocol Instance). |
| ExceptionManagementPutEquipmentDown | For each Resource added in the Protocol Instance Context, the rule will: a) Look for a Resource with State Model set to SEMI E10, and State set to Unscheduled Down. If no State Model exists or if no State Model State matches the Unscheduled Down SEMI E10 attribute, the system will not process information. b) Look for a transition from the current Resource state to the state found in a). If it is found, it will perform a Resource State Change to the state found in a), otherwise it will perform an Adjust State to the state found in a). |
| ExceptionManagementSendMail | 1. Rule will send an email to the distribution list defined in /Cmf/System/Configuration/Mail/LocalSupport/ with the following information: a) Subject b) Body 2. If a distribution list is not defined, the system will not process information. |
The video below illustrates an example where the ExceptionManagementHoldMaterial rule was configured to be used in a given Protocol:
Info
To continue learning, proceed to the use cases: