Introducing Proactive Maintenance (4HI)

Proactive Maintenance - Time-Based Single Cycle Plans

Using task lists, you can centrally define and manage maintenance tasks for your technical objects. General task lists can also help you to prepare maintenance plans and orders.

A task list group combines one or more task lists according to their logical features. Within a task list group, each task list is identified by a group counter. This enables you, for example, to combine several task lists in one group. Within the group, the system allocates a sequential number (the group counter) to each individual task list.

Regular activities to be carried out for technical objects can be assigned to maintenance items.

A time-based maintenance cycle needs to be assigned.

When scheduling a maintenance plan, plan dates and call dates are created/updated. Additionally, call objects such as maintenance orders can be generated.

A maintenance strategy represents a rule for the sequence of planned maintenance and inspection tasks.

A time-based maintenance strategy contains the maintenance packages that define the cycle in which the tasks must be performed, for example, every 10 days, every 3 months, and so on. It contains additional scheduling parameters such as shift factors, preliminary and follow-up buffers, and hierarchy. Maintenance strategies are required in strategy plans.

For each plant, you may use the same maintenance strategy.

Using task lists, you can define and manage regularly performed maintenance tasks for your technical objects. General task lists can also help you to prepare maintenance plans and orders.

Only task lists with an assigned time-based maintenance strategy can be assigned to a maintenance plan.

A task list group combines one or more task lists according to their logical features. Within a task list group, each task list is identified by a group counter. This enables you, for example, to combine several task lists in one group. Within the group, the system allocates a sequential number (the group counter) to each individual task list.

Regular activities to be carried out for technical objects can be assigned to maintenance items .

A time-based maintenance strategy needs to be assigned.

When scheduling a maintenance plan, plan dates and call dates are created/updated. Additionally, call objects such as maintenance orders can be generated.

Using task lists, you can centrally define and manage maintenance tasks for your technical objects. General task lists can also help you to prepare maintenance plans and orders.

A task list group combines one or more task lists according to their logical features. Within a task list group, each task list is identified by a group counter. This enables you, for example, to combine several task lists in one group. Within the group, the system allocates a sequential number (the group counter) to each individual task list.

The Maintenance Planner needs to record the initial reading of a counter assigned to the technical object (equipment / functional location) to be monitored. At least one measurement document is required for scheduling the plan. Once the scheduling is done, regular readings must be recorded in the system by the Maintenance Technician. This process can also be automated my making use of systems which get the reading from technical objects and load to SAP system through interfaces.

Continuous recording of these readings are relevant for accurate determination of maintenance due dates.

Regular activities to be carried out for technical objects can be assigned to maintenance items .

A counter-based maintenance cycle needs to be assigned.

When scheduling a maintenance plan, plan dates and call dates are created/updated. Additionally, call objects such as maintenance orders can be generated.

Using task lists, you can centrally define and manage maintenance tasks for your technical objects. General task lists can also help you to prepare maintenance plans and orders.

Only task lists with an assigned counter-based maintenance strategy can be assigned to a maintenance plan.

A task list group combines one or more task lists according to their logical features. Within a task list group, each task list is identified by a group counter. This enables you, for example, to combine several task lists in one group. Within the group, the system allocates a sequential number (the group counter) to each individual task list.

Regular activities to be carried out for technical objects can be assigned to maintenance items.

A counter-based maintenance strategy needs to be assigned.

The Maintenance Planner needs to record the initial reading of a counter assigned to the technical object (equipment / functional location) to be monitored. At least one measurement document is required for scheduling the plan. Once the scheduling is done, regular readings must be recorded in the system by the Maintenance Technician. This process can also be automated my making use of systems which get the reading from technical objects and load to SAP system through interfaces.

Continuous recording of these readings are relevant for accurate determination of maintenance due dates.

When scheduling a maintenance plan, plan dates and call dates are created/updated. Additionally, call objects such as maintenance orders can be generated.

Using task lists, you can centrally define and manage maintenance tasks for your technical objects. General task lists can also help you to prepare maintenance plans and orders.

A task list group combines one or more task lists according to their logical features. Within a task list group, each task list is identified by a group counter. This enables you, for example, to combine several task lists in one group. Within the group, the system allocates a sequential number (the group counter) to each individual task list.

Regular activities to be carried out for technical objects can be assigned to maintenance items .

Counter-based maintenance cycles and/or a time-based maintenance cycles need to be assigned.

The Maintenance Planner needs to record the initial reading of a counter assigned to the technical object (equipment / functional location) to be monitored. At least one measurement document is required for scheduling the plan. Once the scheduling is done, regular readings must be recorded in the system by the Maintenance Technician. This process can also be automated my making use of systems which get the reading from technical objects and load to SAP system through interfaces.

Continuous recording of these readings are relevant for accurate determination of maintenance due dates.

When scheduling a maintenance plan, plan dates and call dates are created/updated. Additionally, call objects such as maintenance orders can be generated.

This is Screening phase of the process where the supervisor might need to review the maintenance request. Change responsibility of the requests (if required) and take appropriate decision to proceed with request or reject the request.

After a maintenance request is approved, we are in Planning phase of this process. The approved Maintenance Request will be called Maintenance Notification. This process step shows how to convert a maintenance notification into a maintenance order and, provides details about planning the resources for the order.

After you have planned resources for the maintenance order, it can be submitted for approval to the supervisor. This will set the status of the maintenance order to Ready to Prepare subphase.

This process step enables you to approve a maintenance order from My Inbox (F0862) app.

The maintenance order is in Preparation phase now. Maintenance Backlog Overview screen will allow you to view various cards. You can check Maintenance Backlog Card which shows backlog of maintenance orders based on phase or buckets.

With this app, you can view and manage all externally-procured materials and lean services that are required to execute your maintenance orders in a single place.

This process step shows you how to assign purchase requisitions to a source of supply and to convert assigned source purchase requisitions to purchase orders.

Here you post the goods receipt for the purchase order.

You are now in Execution phase of the process. Here you post the goods issue from storage location.

Once Preparation is done and backlog is reviewed, the order can be set for Ready to Schedule to start Scheduling phase.

In this step, you can schedule the order operations and set the operations ready for execution.

In Execution phase, technician will execute Pre and Main operations.

After execution of Pre and Main work by the Technician, the Maintenance Supervisor will review the work and change the status from Main Work Completed to Post Execution phase.

In this activity, you report the performed services in the service entry sheet.

In this process step the technician will execute post operations activities (if any) and also update the malfunction details and failure data.

Maintenance planner can review the cost of maintenance orders.

After the required maintenance work has been performed, the maintenance order is set to technically completed and the maintenance notification is set to completed.

The technical completion reduces all the purchase requisitions, open reservations, and capacities still outstanding for the maintenance order.

Nevertheless, the order can continue to receive costs, for example, through invoice receipts for delivered and used materials. However it is blocked for all changes in the processing.

The order settlement transfers the costs incurred that were temporarily collected for the maintenance order, to the recipient, for example, to the cost center for the maintained object. This process step shows you how to technically complete a maintenance order.

In this process step you create the invoice with reference to the purchase order.

In this process step you release a blocked supplier invoice.