SAP PM explained: asset management in SAP

Asset Management — classically PM, Plant Maintenance, and widely called EAM — is the SAP area that models a company's physical assets and manages the work done on them: functional locations and equipment, maintenance notifications and orders, preventive plans, and the cost every repair carries. This guide covers the objects the area holds, the work from site walk to hypercare, the neighbouring areas and the routes in.

Functional locations, orders, plans and cost

Spoken, the area is PM or EAM, and WCM in utilities; the codes below are its application components, with cost across all of them.

Technical objects (PM-EQM): Functional locations say where maintenance happens, equipment says what is maintained; under them hang maintenance BOMs, measuring points, counters and warranties. The structure indicator fixes the edit mask and hierarchy levels of every functional location, so changing it after go-live renumbers everything hung on it.
Maintenance processing (PM-WOC): A fault is reported, an order is planned with operations, spares and external services, technicians confirm time, the order closes and its cost settles.
Preventive maintenance (PM-PRM): Task lists, strategies and their packages, time- and counter-based plans, and the scheduling run that calls the next order before failure.
Work Clearance Management (PM-WCM): Permits, isolation and safety approval before anyone touches a live asset — standard in utilities and process industries.
The cost side: Every order settles — to a cost centre, an internal order, or a WBS element when a shutdown runs as a project — which keeps Controlling close.

Does the work happen in the plant or in the project room?

Both, and in that order: the hierarchy is agreed by walking the plant with maintenance planners, then configured against the names they already use.

Design weeks — workshops on the technical-object structure, notification and order types, and the damage, cause and activity catalogue that makes history analysable.
Build and data weeks — configuration, task lists and strategies, then equipment records built from drawings, nameplates and a legacy extract: the stretch that overruns whatever greenfield, brownfield or rollout shape the programme runs.
Test, cutover and hypercare — a notification becomes an order beside the planners, its confirmation posts hours to the right cost object, then the first scheduling runs and the backlog arrive with AMS.

Why a maintenance order never stays inside PM

Spares and external services are ordered against the order's account assignment, so Procurement sits beside Asset Management on most teams. Project Systems appears when a turnaround is budgeted as a project; Quality Management meets it at calibration, where inspecting test equipment rides on a maintenance plan. Utilities, oil and gas, mining and rail each maintain differently, so industry depth counts here (which combinations work).

Who ends up owning Asset Management

From maintenance itself — planners, supervisors and reliability engineers who became key users (the key-user route).
From the shop floor — Manufacturing consultants share the plant, the work centres and the vocabulary.
From Service — close objects, minus the entitlement check and the price that make a job billable.
From the technical side — developers on order forms, mobile apps and hierarchy migration, who often know the data model best.

What gets read is a plant you structured: a hierarchy the planners accepted, a preventive programme taken live, an equipment load reconciled against nameplates. Questions follow that line — equipment or functional location, how a plan's call horizon behaves, where a confirmation's cost lands (what interviews test).

What is changing in maintenance work

The process core stayed; the name did not — on S/4HANA the area is Asset Management. Fiori apps ship for planner and technician tasks and mobile confirmation is a standard scope item, so how the day is tooled is a project decision, not a given. The drift toward condition-based calling rewards a clean object structure (the career effect).