MRO Notification

An MRO Notification represents a reported maintenance issue related to an Asset. It records the responsible user, due date, priority, and current processing status. A Notification can also serve as the origin of a Work Package. The created Work Package references the Notification so that its origin remains traceable.

Technical object name: NOTIFICATION

Runtime class: UBIK.MRO.Notification

A Notification is created for an Asset using LK_ASSET. Functional Locations and Equipment can be referenced because they are specialized Asset types.

In addition to the standard properties of a UBIK^® content object, a Notification provides MRO-specific properties for its Asset, assigned user, due date, priority, status, and optional Work Package template. These properties can be edited after creation. Changes to NOTIF_STATUS are restricted by the defined status transitions.

Properties

Notification Priority

The priority is stored in NOTIF_PRIORITY. The following values are available:

Notification Status

The current processing state is stored in NOTIF_STATUS. The following values are available:

Status changes are validated by the Notification. Only the following transitions are permitted:

Setting the same status again is permitted. Other status changes are rejected. Completed and Rejected Notifications can only be moved to Closed and cannot be reopened through the standard status logic.

A Work Package can be created from a Notification either using a Maintenance Plan or through manual creation. In both cases, the created Work Package is linked to the originating Notification using LK_NOTIFICATION. This makes the origin of the Work Package traceable.

Maintenance Plan-based Creation

For Maintenance Plan-based creation, the Maintenance Plans assigned to the Notification's Asset are evaluated.

• If multiple Maintenance Plans are available, one of them is selected for the creation.
• The Work Package is created based on the selected Maintenance Plan and its Work Package template.
• The created Work Package references the originating Notification through LK_NOTIFICATION.

Manual Creation

For manual creation, a new Work Package is created for the same Asset as the Notification.

• The Work Package is linked to the Asset referenced by LK_ASSET.
• The Work Package references the originating Notification through LK_NOTIFICATION.
• Subordinate Work Packages and Tasks can be added to structure the required maintenance work.

Relevant Work Package property

The FileDocumentNotification class provides document attachments for Notifications. Each document is linked to its Notification using LK_NOTIFICATION.

Runtime class: UBIK.MRO.FileDocumentNotification

The MRO Notification implementation does not define additional restrictions for file types, file sizes, or the number of attached documents.

• MRO (Plugin)
• Work Package
• MRO Objects (Client)
• MRO Implemented Objects
• MROMaintenancePlans
• MRO Material Management