Redwood: Capture and Evaluate Events from Connected Assets for Condition Monitoring

When an asset produces an error or a failure state, maintenance teams must manually create maintenance work orders to restore the asset. With this update, condition events from a connected equipment can be leveraged to automatically generate a condition-based maintenance work order corresponding to the event.

This update lets you:

• Configure operational rules for equipment fault codes to capture and evaluate events from connected assets.
• Use maintenance programs that include fault event codes for which condition codes are set up in Maintenance. The maintenance programs can have work requirements defined for an asset or group of assets, use one or more condition codes, and contain one or more work definitions.

Condition alerting with machine events include the following:

• Event Ingestion: Connected assets can send fault events. These events contain the asset number, the time it occurred, the fault type, and the fault code. You can configure fault codes in maintenance as condition codes. Condition codes can be created for failure and diagnosis.
• Evaluation Criteria: Use operational rules to evaluate incoming fault events. When you configure an operational rule, it applies to all connected assets so that any incoming event from a connected asset is evaluated against all configured operational rules. 
• Outcome: The outcome for an operational rule describes the actions to be executed when the evaluation criteria is met.  If the fault code has been configured as a failure condition code, then the created work order contains a failure event. If the fault code has been configured as a diagnostic condition code, then the created work order uses the maintenance program corresponding to the diagnostic condition code.

Guided Journey

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

Operational Rules Task in Maintenance Management

The Operational Rules page shows a list of existing rules. You can create, edit, and delete rules from this page.

Operational Rules Page

The rule definition screen lets you edit the rule:

• Details of the rule contain the general definition of the rule, such as the name, code and description.
• Evaluation criteria defines the conditions that are evaluated for incoming events.
• Evaluation parameters define if any or all evaluation criteria need to be satisfied for the rule to trigger.
• Outcome defines the actions that are executed if the evaluation is successful.

Rules Definition Screen

When adding an Evaluation criteria, use the Asset Fault event type for Maintenance.

Asset Fault Event Type

Every evaluation condition contains multiple sections:

• Condition details include the condition name, description, and whether the condition is active.
• The Rules section has operators at the rules and conditions levels, which determine if Any or All of the condition lines must be met.
• Condition lines define the rule conditions using Attributes, Operators, and Values. Any combination of Fault Code and Fault Type attributes can be used for asset faults. Fault Code and Fault Type are those sent by the connected equipment. Examples of operators include Equals and Not Equals.
  For example: Fault Code equals 700.
  

Evaluation Condition Screen Showing Condition Details and Rules

The Outcome section defines the actions that are executed upon successful evaluation of the evaluation criteria. For Maintenance use one of the first two options:

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

Outcome Details Drawer

Creating maintenance work orders automatically enables maintenance teams to quickly respond to asset breakdowns and failures, reducing downtimes.

Here's the demo of these capabilities:

Steps to Enable

To enable this feature you need to log a Service Request (SR).

This feature requires additional services (“SCM Core Service-Smart Operations”) to be provisioned on your instance. To enable this service, you need to log a Service Request (SR).

• Select Product Module: Oracle Maintenance Cloud Service.
• Select Category: Maintenance Work Orders.
• Select Subcategory: Maintenance Work Orders.
• Select Component: Installation Issue (INSTALL).
• Select Severity: 3-Minimal Loss of Service.
• Copy and paste this text into description area of the SR: Enable the SCM Core Service-Smart Operations.

Please note that this service can be enabled on instances that are available on Oracle Public Cloud regions.
In addition, you can access the user guide and implementation guide to learn more about this feature and how to set it up.

Tips And Considerations

1. Operational rules configured by users apply to all connected assets.
2. Connected Asset events received via industrial communication protocols need to be converted to a REST payload that Fusion Maintenance Cloud can ingest and take actions on. The accepted payload specifications are documented here: REST API for Oracle Fusion Cloud SCM.
3. Asset Fault events need to be ingested using condition codes known in Maintenance. To automatically create work orders, we strongly recommend that you create the corresponding condition codes in Maintenance for all fault codes sent by the equipment. The following types of condition codes are supported:
   1. 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.
   2. 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.

Access Requirements

Users need this privilege to create/edit/delete/view rules: 

• Manage Operational Rules: For Create/Read/Update/Delete operations.
• View Operational Rules: For Read Only operation.
• Access HCM Common Components 
• Manage HCM Rules

Users need this duty role to manage operational rules:

• Access to SMO rules management (ORA_DR_SMO_MANAGE_OPERATIONAL_RULES_MNT_DUTY).