Describing the Forwarding Process of Maintenance Notifications

The image depicts a schematic diagram showing the relationship between a naval ship, Frigate 12345, and a naval base. The ship is identified by its unique number, D12345, and is further divided into sections for Armament and Propulsion Plant. The Frigate 12345 is linked to an Actual Responsible Work Center at the naval base, which then forwards information to a New Responsible Work Center at the naval base.

Example: Frigate 12345 is linked to Force Element A (Maintenance platoon) via the master equipment. The maintenance notifications and maintenance orders are processed by the work center of force element A. If various repairs cannot be performed by this work center, the open notifications and orders can be forwarded to a new work center that has the capability to perform the repair.

The image shows a maintenance notification form in an SAP application. The form includes fields for Reference Object, Subject, and Responsibilities. The Choose Recipient window on the right side displays a list of maintenance groups that can be selected as the responsible work center.

A maintenance notification can be forwarded using the forwarding button in the Responsibilities screen area. After pressing the button, you will see all previously defined maintenance relations to which this notification can be forwarded.

The image depicts a maintenance workflow process involving different work centers and tasks. It shows two mobile processing work centers - a Flight engineer (A11B) and a Maintenance crew member (A13B), as well as an ERP Processing Maintenance planning unit (A12B). The process involves notification, order, execution, and confirmation steps, with information flowing between the mobile processing centers and the planning unit.

This figure illustrates the procedure for forwarding maintenance notifications (when mobile devices are used).

Describing the Forwarding Process of Maintenance Notifications

Maintenance Relationships - Forwarding