Create Automatic Production Exceptions for Equipment

Welcome to the demo of the 25A feature, Create Automatic Production Exceptions for Equipment Related Events at a Workstation. Manufacturing plants are increasingly equipped with machines that are able to communicate via IoT communications. With this update, customers will be able to make use of these machine signals to create production exceptions, mark the workstation as down, and create maintenance work orders to bring the issue to the maintenance supervisor's attention. Users can create rules which will be applied on the signals received from the machines, along with evaluation criteria and the outcomes to be taken when the evaluation criteria are met. Accurate and automated reporting of production issues from equipment enables timely response to those issues and reduces production delays.

Let's look at a short demo for this feature. We will first see how a manufacturing engineer can configure operational rules for events received from an equipment. We will then look at how the rules configured lead to creation of production exceptions during execution of a work order operation.

Before we get into the demo, let's take a look at how data generated by connected equipment flows from the factory floor to Oracle Fusion Manufacturing Cloud. Industrial IoT gateways or middleware would be configured to communicate with the connected equipment through industrial communication protocols. The gateway or middleware would first transform this information into a format that Oracle Fusion Cloud Manufacturing understands and then post to it. Upon receiving this transformed payload, Oracle Fusion Cloud processes the event and then takes appropriate business actions.

The event types supported in 25A are as follows, asset fault, asset status, operation execution start, operation execution stop, and quantity report. As shown here on the screen, the payload consists of two main sections. entityCode, eventTime, and eventTypeCode are mandatory fields.

The entityCode here is the asset number of the connected equipment. Sample payload for all the events can be found in the references shared at the end of the demo. Now let's get into the demo.

I launch the operational rules task from work definition work area. Here I am presented with the list of operational rules created for my organization. An operational rule consists of four main parts, the Details section where the rule name, the rule description, and rule code are defined, the Evaluation criteria where attributes that are the inputs to the rule are defined, the Evaluation parameters defines the triggering logic for the rule, and the Outcome where users can select what action should be taken when the rule criteria are satisfied.

In evaluation criteria, you can add an event's attributes as input to the condition logic. Currently, event types of asset status and asset fault are supported. For asset fault event, fault code and fault type can be added as operands. For asset status event, the asset status can be added as the operand.

Once you have added the evaluation criteria, you can select an evaluation parameter. You can choose between any evaluation criteria being satisfied or all evaluation criteria being satisfied within a user-specified time window. In the outcome section, you can select the action that should be taken when the rule conditions are met. You can select from a predefined list of supported actions.

Now let's look at rule evaluation and outcomes in action. I am currently executing a work order operation, and the workstation is in in-use status. This workstation contains connected equipment which are capable of sending failure signals. Upon receiving a equipment failure signal, a production exception is automatically getting created. This production exception is also going to be available to the production supervisor in the production supervisor workbench. This automated creation of production exceptions enables real-time and faster response and thereby reduces production downtimes.

This concludes the demo for this feature. For more information on setup required and the steps to enable this feature, please refer to Manufacturing 25A What's New for the following features, complete work order operations automatically using equipment signals at workstations and create automatic production exceptions for equipment-related events at a workstation. Thank you.