Use Equipment Sensor Data to Capture Inspection Results During Production Execution at Workstations

Welcome to the demo of the 25B feature Use equipment sensor data to capture inspection results during production execution at workstations. Increasingly, manufacturing plants are equipped with connected equipment that can send machine events, including quality inspection characteristic results produced during execution.

With this update, you can automatically record quality inspection results by leveraging machine signals through IoT communications. This would lead to increase in operator productivity by allowing operators to focus on the actual production tasks in front of them.

Now, let's look at a demo scenario for this feature. I would launch the execute production at a workstation task in work execution work area. I would select my workstation and check into it. I will first receive an execution start signal from the connected equipment. I will then be able to see the execution status for the in-progress work order operation.

The equipment would then directly send the quality results to Fusion Manufacturing Cloud. The quality disposition would be reported based on the inspection plan. I will then view the automated reporting of operation completion and rejection transactions at the workstation.

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 25B 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. Entity code, event time, and event type code are mandatory fields.

The entity code 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. The event type quantity report has been enhanced in 25B to support quality inspection. The sample payload is displayed on the screen.

Let's get into the demo. From the work execution work area, I launch the execute production at a workstation task. I check into my workstation molding station zero one. I'm looking at the workstation details page. Notice the equipment section here.

Molding machine zero one is the connected equipment, which would be giving us the equipment signals for the automated execution and automated quality reporting. I receive a start signal from a connected equipment. And now the workstation is in a new status. And the work order operation 10 molding for the work order M1-1331 is in execution at this workstation.

I now receive a quality inspection results from the connected equipment. The disposition is automatically reported as operation completion transaction and the production summary section is automatically updated for the production operator looking at the operator Workbench.

After some time, I receive quality inspection results which pertain to a rejection transaction. Again, the production summary is automatically updated for the production operator at the operator Workbench.

The quality inspection results can be viewed in the supervisor Workbench work order tab, searching for the work order and looking at the transaction history of that work order. Under the column inspection results, you can click on the Eye icon to view the inspection characteristic results reported by the connected equipment or reported manually by an operator.

For more information, please refer to manufacturing 25 a 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. This concludes the demo for this feature.