Overview of Production Exceptions

One of the key execution capabilities that Oracle Manufacturing offers is that you can report and manage production exceptions. As a production operator or the production manager, you can report the problems that occur on the shop floor. These might be problems that can affect the smooth progress of a work order and are thus reported as production exceptions.

You can also associate other work orders to a particular exception. These might be work order operations that are impacted by the problems. For example, if 3 work orders use a particular component which is in short supply, an exception can be reported and all 3 work orders can be associated to it.

All users having the production supervisor role (WIP_MANAGE_PRODUCTION_EXCEPTIONS_PRIV) privilege and required access to the manufacturing plant will be notified about the production exception.

After an exception has been reported, you can manage (query, create, update, and review of production exceptions) if you've been assigned (WIP_MANAGE_PRODUCTION_EXCEPTIONS_PRIV) privilege. You can also take specific actions to resolve the problems and then close the exception.

An exception can be reported when progress can't be made on a particular work order due to problems like shortage of a particular component. The following are the types of production exceptions reported in a plant:

• Work Area

• Work Center

• Resources

• Components

• Miscellaneous

• Supplier Operations

Note: Exceptions for supplier operations are automatically reported by the application. You can't manually report an exception for a supplier operation.

The manufacturing issue types are predefined and you can't extend these predefined issue type values.

The process of reporting exceptions will fail in these scenarios:

• If Issue Types corresponding to Production Exception is set to the User-defined or Inherited from Parent options, the process of creating them will fail. So, ensure that you use these settings only for legacy data import, if at all. It is recommended to always set them to Sequence-generated.

• If additional mandatory fields have been added to quality issue through the application composer.

IoT Integration for Production Execution

Oracle Fusion Cloud IoT Production Monitoring can automatically log production exceptions on resource instances in Manufacturing Cloud. You can configure rules to detect changes in machine conditions that indicate failure or predicted failure and use this information to log machine incidents in IoT Production Monitoring. Along with these machine incidents, you can configure automatic creation of a corresponding production exception in Manufacturing Cloud and a maintenance work order in Maintenance Cloud, so that appropriate action can be taken.

Production exceptions are created with a resource exception type referencing the resource instance. Maintenance work orders are created on the asset number mapped to the resource instance. When the production exception is closed in Manufacturing, the corresponding incident is closed in IoT and vice versa.

For more information, refer to the Production Exceptions for Machine Incidents topic in the Using Oracle Internet of Things Production Monitoring Cloud Service guide.

Exceptions of the Resource type are automatically generated by IoT Production Monitoring for resources defined as automation equipment upon manually stopping the execution, or receiving a execution failure signal from automation equipment. For more information, refer to the Using Oracle Internet of Things Production Monitoring Cloud Service guide.