How You Report Maintenance Exceptions

Report and review maintenance exceptions on the Manage Maintenance Exceptions page. You can also create, update, and view exceptions using the Quality Issues REST API.

You can report the maintenance exceptions by providing the exception details and then add the work order operations that are impacted by the exception. The exceptions can be reported on the Report Maintenance Exception page. You can open the Report Maintenance Exception page through the following page flows:

• In the Tasks pane, in Work Execution, click the Report Maintenance Exception link.

• In the Tasks pane, in Work Execution, click the Review Maintenance Dispatch List link. On the Maintenance Dispatch List page, from the Action menu, select: Report Maintenance Exception.

• In the Tasks pane, in Work Management, click the Manage Maintenance Exceptions link. On the Maintenance Exceptions page, click the add icon.

Steps to Report a Maintenance Exception

To report a maintenance exception, perform the following steps:

1. Open the Report Maintenance Exception page.

2. Provide the exception details. Select from or enter the values for the following.

   Attribute	Description
   Exception Type	The type of the exception you're reporting. The exceptions can be of the following types: Work Area Work Center Component Resource Miscellaneous
   Exception Status	The status of the exception. This attribute is read-only and at the time of reporting an exception, the exception status is always Open.
   Description	The description of the exception.
   Severity	The severity of the exception. The valid values are: Critical, High, Medium, and Low.
   Expected Downtime in Minutes	Indicates the maintenance downtime that's expected due to the exception.
   Expected Resolution Date	Indicates the expected date for the exception resolution.
   Attachments	The attachments in the exception. It can be of file, text, or URL type.

3. Add the work order operations that are impacted by the exception. In the Impacted Work Order Operations region, click the Add icon.

4. In the Search for Work Order Operations dialog box, search for and select the work order operation that you want to add to the exception. Click the Add button. The Impacted work order Operations region displays the work order operation including details such as work order number, exception status, work order status, start date, completion date, and Item.

5. Click the Save and Close button. A notification is generated and sent to all the users with relevant roles.

How You Manage Maintenance Work Order Exceptions Using REST API

Use the Quality Issues REST API to report maintenance work orders exceptions and reference a work order operation. You can then view these exceptions on the Manage Maintenance Exceptions page. You can also enable work flow as part of the exception process.

Here is a sample payload to create a resource exception for a single work order operation:

{
"Name": "Maintenance Exception By ID",
"QualityTypeCode" : "ORA_ENQ_MNT_RESOURCE",
"Severity" : "ORA_MEDIUM",
"Downtime" : 0,
"Source": "ORA_MAINTENANCE",
"OrganizationCode" : "MNTALM",
"ReportedBy": "MNT_QA",
"ReportedDate": "2021-07-22T12:00:00+00:00",
"WorkflowStatusCode": "ORA_ISSUE_EXCEP_OPEN",
"AffectedObjects":[
{
"SupportedEntityCode" : "ORA_WORK_OPERATION",
"ContextId" : 300100549061424
},
{
"SupportedEntityCode" : "ORA_RESOURCE",
"ContextCode": "I-Inspector",
"SubContextCode" : "MNTALM"
}]
}

Payload Attribute	Level	Description	Allowed Values
QualityTypeCode	Parent resource	The type of the exception	Lookup: ORA_ENQ_SOURCE Values: ORA_ENQ_MNT_RESOURCE ORA_ENQ_WORK_CENTER ORA_ENQ_MNT_COMPONENT ORA_ENQ_MNT_WORK_AREA ORA_ENQ_MNT_MISCELLANEOUS ORA_ENQ_MNT_SUPPLIER_OPERATION
Severity	Parent resource	The severity of the exception	Lookup: ORA_ENQ_SEVERITY Values: ORA_HIGH ORA_MEDIUM ORA_LOW ORA_CRITICAL
Source	Parent resource	Maintenance is the exception source	ORA_MAINTENANCE
WorkflowStatusCode or WorkflowTemplateId	Parent resource	Optionally you can send a workflow template ID or a workflow status code	ORA_ISSUE_EXCEP_OPEN is an example of a workflow status code
SupportedEntityCode	Child resource: AffectedObjects Associates using a primary and secondary affected objects to the issue	For the primary affected object, you're referencing the work order operation	Therefore, the supported entity codes are first added as a child resource: Lookup: ORA_ENQ_SUPPORTED_ENTITIES Values and their associated IDs: ORA_WORK_ORDER - 1001 ORA_WORK_OPERATION - 1002 ORA_RESOURCE - 1003 ORA_COMPONENT - 1004 ORA_WORK_AREA - 1005 ORA_WORK_CENTER - 1006 ORA_INSPECTION_RESULT - 1007 ORA_RECEIPT - 1008
ContextId	Child resource: AffectedObjects	This will be the work order operation ID	Value will be the work order operation ID
SupportedEntityCode	Child resource: AffectedObjects	For the secondary affected object, you're referencing what the exception is for.	In this case, you could use the resource code: ORA_RESOURCE
ContextCode	Child resource: AffectedObjects	This will be the code of object you reference in the entity code	Pass the resource code in this example. This will be the code of the resource setup in the organization
SubContextCode	Child resource: AffectedObjects	This will be the organization code	Pass the organization code: the resource must be setup in this organization