Configure and Manage Performance Metrics for Your Workstations
Welcome to the demo of the 25A feature, Configure and Manage Performance Metrics for Your Workstations in Oracle Fusion Cloud Manufacturing. You can configure parameters, performance metrics, and workstation reason codes using the Redwood user experience. Also supports to monitor the shift's progress using metrics or key performance indicators KPIs based on the organization's processes and standards. Tracking metrics and KPIs helps proactively address issues and deviations, ensuring production continuity. It provides the ability to meet production goals on the shop floor related to quality, delivery, and overall equipment effectiveness OEE.
To start with, let us see the navigation to the new Redwood user interface for Smart Operations Configurations. You can go to Work Execution from Supply Chain Execution. Here, go to View all actions. Smart Operations Configurations is the new task added in manufacturing setup. You can click on Smart Operations Configurations. You can see that the new Redwood user interface, Smart Operations Configurations, is launched. You can see the three smart operations configurations tab, Configuration Parameters, Metrics, and Workstation Reason Codes.
First, let us review the Configuration Parameters. The parameters Performance Loss Threshold in Minutes, and UOM for Quantity Metrics, are available in production supervision. You can change the parameter values.
Performance Loss Threshold in Minutes specifies the threshold duration in minutes, below which all workstation stops without a reason code are counted as minor stops, and therefore a performance loss. A stop duration greater than this threshold value automatically counts as an availability loss if a reason code is not specified. The parameter UOM for Quantity Metrics specifies the common unit of measure to use when work order products have different UOMs. You can update and save the parameter values using the Update action. The parameters Operator Assignment and Work Order Operation Assignment are available in Workstation execution.
Let's see how you can change the parameter values. You can select one of the values from the list for the respective parameters. The parameter Operator Assignment controls operator check ins at workstations. The value Not enforced means any operator can check into any workstation. Enforced means only operators assigned to a workstation by the Production Supervisor can check in to the workstation.
The parameter Work Order Operation Assignment controls work order operation assignments at workstations. The value Not enforced means the operators can scan any eligible work order operation. Enforced means the operators can execute only those work order operations that are assigned to the workstation by the Production Supervisor. Enforced with sequence means the operators can execute only work order operations assigned to the workstation in the sequence specified by the Production Supervisor. You can update and save the parameter values using the Update action.
The next one is the Metrics. The metric setup establishes benchmark targets for metrics such as Plan Adherence, OEE Overall Equipment Effectiveness availability, performance, and quality in the manufacturing plant. You can also update the metric values. The target value for the metric Plan Adherence can be updated. Similarly, you can update the value for all other metrics.
The next one is the Workstation Reason Codes. Workstation Reason Codes help record activities that result in workstation status changes. When an Operator selects a workstation reason code, the workstation status is accordingly set. You can see that some of the reason codes are predefined and available to the user by default. You can also create reason codes manually. You can perform copy, or update, or delete actions for the reason codes. The reason code with Creation Method as Predefined, can be copied or updated, but can't be deleted. The reason code with creation method as Manual can be copied or updated or deleted. You can create a Reason Code using the Create action.
You can provide the following details and create a new reason code. Enter a Reason Code. Enter the name for the reason code. Select the Workstation Status. Each reason code is associated with a workstation status like Idle, In Use, or Down. For example, a workstation may be down for scheduled maintenance activity.
Select a value for the loss. Each reason code is associated with a workstation status and potential loss, such as Availability loss, Performance loss, Break, or Not a loss. For example, a workstation may be down for scheduled maintenance, leading to an availability loss. The stop duration is accounted correctly in OEE calculations as Availability loss, Performance loss, Break, or Not a loss.
You can create the reason code using the Save action. You can see the toast message that the Reason Code is created, and the newly created Reason Code is shown. You can also update the reason code using the Update action. As a part of Update action, you can set the Inactive Date for the Reason Code. Select the checkbox to Set the Inactive date. Provide the Inactive Date.
You can update the changes to the Reason Code using the Update action. You can see the message that the Reason Code is updated, and the updated details of the Reason Code displayed. You can also delete the Reason Code using the Delete action. You can see the message that the Reason Code is deleted. You can select an existing Reason Code and copy or duplicate it. A new reason code is created, and the message is shown.
You can see that the Reason Code setup is copied as Setup underscore 1. Thereafter, you can update the copied Reason Code as required. Also, note the constraint when you try to delete a Reason Code. If the Reason Code is used in a workstation, then it can't be deleted. You can see the message displayed, and the user is allowed to inactivate the Reason Code instead of deleting it.
This concludes the featured demo. Thank you for watching.