![]() Planning Phase: Accepted Maintenance Requests (Notifications) In the Planning phase, a ‘Maintenance Planner’ creates a maintenance order for one or more accepted maintenance requests (now called ‘Notification’) using the new app ‘Manage Maintenance Notifications and Orders’. ![]() It may be noted that only screened maintenance requests are visible in ‘Find Notification’ app. On re-submission, the maintenance request again moves to phase ‘Screening’ but sub-phase ‘Resubmitted (Request)’. The requests in sub-phase ‘Action Required’ can be further worked on by the originator and re-submitted for screening. While the accepted maintenance requests move to the next phase ‘Planning’, the rejected maintenance request gets closed (status ‘Completed’). He can also edit information related to malfunction, responsibility and other details.Īfter the review, either he can accept them, reject them or send them back to the imitator for insufficient information.īased on the Supervisor action, the maintenance request moves to following phases and sub-phases: While reviewing a request, the Supervisor can also assess priority by selecting a combination of consequence categories, consequences, and likelihood. (Fiori App – Screen Maintenance Requests) Screening Phase: List of open maintenance requests In screening phase, a Supervisor (Gatekeeper) reviews all the open maintenance requests in the new FIOR app ‘Screen Maintenance Requests’. On submission, the new request moves to the next phase ‘Screening’ where it is reviewed. When the maintenance request is submitted, it is available in another new FIORI app ‘My Maintenance Requests’ where the technician can view all his requests that were submitted, rejected, completed or returned due to insufficient information. Initiation Phase: Creating a maintenance request The app provides the simple screen to enter malfunction / maintenance request details and provision for attachments / links. During the Initiation phase, a technician creates a maintenance requests for an equipment or a functional location using the new FIORI app ‘Create Maintenance Request’. The initiation phase is only applicable to maintenance request. The progression of the 9 phases of the reactive maintenance process across maintenance request and maintenance order are described in detail below: 1. Process Phases Details – Reactive Maintenance The process phase model not only provide the simplified and granular status management to guide users along the process but also improve tracking and schedule compliance of the maintenance backlogs. The new end to end best practice processes (scope item 4HH, 4HI, 4VT, and 4WM) using notification / maintenance orders are structured according the 9 phases as described in the diagram below:Įnd to End Phase Model for the New Scope Items The phase model for the maintenance order is structured using the following phases and sub-phases: The phase model for the maintenance request (notification) is structured using following phases and sub-phases: ![]() The blog post explains in detail how the process phases and sub-phases are progressed in a typical reactive maintenance process. It may be noted that the system statuses continue to exist, but they take backstage. This is very similar to the concept of the user status. In S/4HANA Cloud Release 2102, SAP has further improved the phase model by allowing the reversal of many phases.įor maintenance order and operation, SAP has also introduced configurable ‘Phase Control Code’ to allow you to control the transition of phases e.g. Similar to statuses, phases and sub-phases are used for selection criteria and to permit or prohibit business transactions. The ‘process phases’ are available for the maintenance objects ‘Notification (Maintenance Request) and Maintenance Order but only for the new scope items as below: ‘Phase’ and ‘Sub-phase’ and are set up by SAP. The ‘process phases’ have 2 levels of hierarchy viz. ![]() In S/4HANA Cloud Release 2011, SAP introduced the new concepts of ‘Process Phases’ to track the life cycle of the maintenance processes as an alternative to System and User statuses used previously.
0 Comments
Leave a Reply. |