Set Up Operational Rules for Connected Assets

Use the Operational Rules task in the Maintenance Management work area to create rules that can automatically generate maintenance work orders based on condition events.

After you create an operational rule, you can make it applicable to all the connected assets, specific asset items, or asset item categories. You can restrict the rule applicability to certain locations or operating organizations.

Asset fault events need to be ingested using condition codes of Maintenance. To automatically create work orders, we strongly recommend that you create the corresponding condition codes in Oracle 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.

Operational Rules

Operational parameter events need to be ingested using operational parameters defined in Smart Operations. Operational parameters values such as pressure, temperature, and vibration are sent from connected equipment. Operational parameters need to be configured before they can be used in operational rules. Use the Operational Parameter task in Maintenance Management to create or modify operational parameters.

To set up operational rules:

1. Navigate to the Maintenance Management work area.
2. Click the Tasks icon and select Operational Rules under Maintenance Setup.
   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. Add one or more Evaluation Criteria for the operational rule.
   1. Click Add under Evaluation Criteria.
   2. Select an Event Type.
      You can use the Asset Fault or Operational Parameter event type for Maintenance.
   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.

      In case of Asset Fault events, 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.

      In case of Operational Parameter events, you can use any Operational Parameter defined in Smart Operations. Examples of operator are equals, not equals, greater than. For example: Temperature greater than 70.

   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 appears if you have used multiple evaluation criteria. Evaluation parameters define if any or all evaluation criteria need to be satisfied for the operational rule to trigger.
7. Select an Outcome for the operational rule.
   The Outcome defines the actions that are executed if the evaluation is successful. You can use one of the following for Maintenance:

   • Create maintenance work order.
   • Create maintenance work order and production exception.

   For both of these entries, you can configure work order to happen on the first occurrence, or if an issue persists for a longer time.

   Example 1: If Maintenance Work Orders should be created on any occurrence of the conditions being met, the delay evaluation field should be left unselected (this is the default).

   Example 2: For certain connected assets, faults or operational parameter violations can occur sporadically. This is typically related to noise or temporary situations (e.g. during startup sequence of an asset). If this situation does not persist it is considered harmless and there is no need to create a Maintenance work order. To cover such situation Evaluation Parameters can be specified. In the given example, only events that occur longer than 10 minutes will create a work order, which is specified as the delay interval. Total duration specifies the interval during which such events are considered to belong together. If new occurrences happen after the total duration it is a considered a new situation (such as a new startup sequence) and will not be considered related to the initial occurrence.
8. Optional: Customize work order descriptions. Description templates can contain references to operational parameters as well as context parameters. Context parameters can be:
   • • RULE_NAME: rule name of the evaluated rule
     • RULE_CODE: rule code of the evaluated rule
     • ASSET_NUMBER: asset number of the asset which sent the event
     • FAULT_CODE: fault code received from the asset

   Here's an example string you can write for a new work order description that has a context parameter: asset number, and two operational parameters: actual pressure and actual temperature:

   Temperature and Pressure are above threshold for ${ASSET_NUMBER}. Actual temperature was ${Temperature}, actual pressure was ${Pressure}.

9. Optional: Specify condition codes explicitly for a certain outcome. These explicit condition codes are used when the work order is created and are used to identify maintenance programs using these condition codes.

   For example, the condition code used for the Maintenance work order creation is a preconfigured condition code: FC1.

10. Optional: Configure work orders to be created with a failure event set which indicates if the asset is down.
11. Optional: Automatically request meter readings when work orders are created.