Use Operational Rules for Connected Equipment

Use the Operational Rules task in the Work Definition work area to create rules that can automatically generate production exceptions and maintenance work orders based on condition events. Operational rules can also automatically update the workstation status.

Asset fault events need to be ingested using condition codes known in Maintenance. To automatically create maintenance work orders, we strongly recommend that you create the corresponding condition codes in Maintenance for all fault codes sent by the connected asset. The following types of condition codes are supported:

• Diagnostic Code: Used for less severe conditions, which are handled by the maintenance engineer. The diagnostic code should be defined in the related Maintenance work definition that covers the necessary work. The diagnostic code is referenced in the work order that is created.
• Failure Code: Used for more severe conditions that require immediate maintenance action and may result in the asset being down or not available for manufacturing operations. The work order contains the received fault codes in a Failure Capture Set. If configured, a production quality exception can also be created.

To set up operational rules:

1. Navigate to the Work Definition work area.
2. Click Operational Rules from the Actions or Tasks list.
   The Operational Rules page shows a list of existing rules. You can create, edit, and delete rules from this page.
3. Click Create Operational Rule to create a new rule.
   The New Operational Rule page appears.
4. Under Details, enter a Name, Code, and Description for the operational rule.
5. Optionally enter an Inactive Date.
   The operational rule becomes inactive after this date is reached.
6. Under Applicability, choose the organizations and the resource instances to which the rule applies.
   By default, the operational rule applies to all organizations and their resource instances, assets, and asset items.
   For example, you can select one or more manufacturing plant organizations under Organization. You can optionally select one or more equipment resources for the Association Type.
7. Add one or more Evaluation Criteria for the operational rule.
   1. Click Add under Evaluation Criteria.
   2. Select an Event Type and click Continue.
      For example, you can use the Asset Fault event type for Maintenance work orders.
      You can also use Operational Parameters to trigger the rule based on operational process data.
   3. In the New Conditions dialog, enter a Rule Name and Description.
      The Rule Name is the name for the set of rules or conditions that you add to the evaluation criteria. You can also choose if the evaluation criteria is Active.
      The Rules section can contain one or more rule groups. Each rule group in turn can contain multiple rule conditions. The Rules section has operators at the rules and conditions levels, which determine if Any or All of the condition lines must be met.
   4. Add one or more condition lines for a rule group.
      A condition line defines the rule conditions using an Attribute, Operator, and Value.
      You can use any combination of Fault Code and Fault Type attributes for asset faults. Fault codes and Fault types are sent by connected equipment. Examples of operators include Equals and Not Equals. For example: Fault Code equals 700.
      For operational parameter attributes, you can specify conditional operators and values that satisfy the rule. For example: Temperature Greater than 50.
   5. If you have multiple condition lines, select Any or All under Operator for the rule group.
      The Operator setting determines if Any or All of the condition lines must be met.
   6. Optionally add more rule groups and conditions.
      If you have multiple rule groups, select Any or All under Operator for the Rules page. The Operator setting determines if Any or All of the rules must be met.
   7. Click Save to save your evaluation criteria.
   8. Optionally add more evaluation criteria.
      The Evaluation Parameters section lets you optionally delay evaluation to minimize noise and reduce redundancy by suppressing the first instance of fulfilled criteria.
      If you have used multiple evaluation criteria, then the Evaluation Parameters section lets you define if any or all evaluation criteria need to be satisfied for the operational rule to trigger.
8. Select an Outcome for the operational rule.
   The Outcome defines the actions that are executed if the evaluation is successful. Depending on the evaluation criteria, you can use from the following:

   • Create maintenance work order.
   • Create maintenance work order and production exception.
   • Create production exception.
   • Create production exception only when workstation is in use.
   • Update workstation status.
   • Mark workstation as down.
   For example, when setting the outcome to update workstation status, you can select a reason code from your predefined reason codes.
9. Click Create to create the operational rule.