SAP PM Go-Live Readiness Checklist (Free, PDF)

0%

0 of 37 items complete

13 critical items still open - these are the highest-risk gaps.

Download checklist:

Master data

Functional location structure indicator and numbering approved by maintenanceCRITICALEquipment categories defined and mapped to the asset registerCRITICALEvery equipment record has a functional location or an agreed reason it does notMaintenance plant, cost center and planning plant filled on technical objectsCRITICALEquipment classes and characteristics loaded for reportingWork centers created with capacity, cost center and activity typesMeasuring points and counters set up for condition-based plansSpare parts BOMs linked to equipment and functional locationsDuplicates and obsolete equipment removed before load

Configuration

Order types, notification types and number ranges configured and testedCRITICALOrder type to settlement profile and cost center assignment checkedCRITICALPlanner groups and partner roles defined per plantCatalog profiles and damage, cause and activity codes agreedMaintenance strategies and packages createdUser status profiles configured where waiting states are neededPriority and scheduling parameters tested end to endPrint forms for work orders and permits approved

Planning and execution

Task lists built for the first wave of preventive plansMaintenance plans created and scheduled with correct start datesCRITICALDeadline monitoring (IP30) set up as a background job with a plant variantCRITICALCorrective cycle tested: notification, order, release, issue, confirm, TECOCRITICALReservations and goods issue to orders tested with real spare partsTime confirmation tested including final confirmationOrder settlement tested to cost center or assetCRITICALBacklog and open work orders loaded or agreed to be closed in the old system

Access and interfaces

Roles by process step tested, including authorization on order type and plantCRITICALSegregation of duties reviewed for release, goods issue and settlementInterface to purchasing and stores tested for non-stock partsInterface to finance and cost reporting testedMobile or tablet app tested with real technicians if usedReports for backlog, compliance and cost agreed with maintenance

Training and cutover

Key users trained and have signed off user acceptance testsCRITICALEnd users trained with role-specific quick guidesCutover plan with load sequence, owners and times approvedCRITICALFallback and rollback plan documentedHypercare support plan and issue triage owner namedData load reconciliation counts signed off by maintenanceCRITICAL

Tick what is done and signed off. Any unchecked critical item should block go-live until it has an owner and a date. Below about 80 percent overall, hold a readiness review before cutover.

Readiness review

Optional: share your open critical items and we will give a short outside view.

Optional. The tool and every export work without this. No spam.

How to use the checklist

Work through each group with the owner named beside it: master data with maintenance engineering, configuration with the PM consultant, planning with the planner, access with security, and cutover with the project manager. Tick an item only when evidence exists, such as a test log or a reconciled count. Items marked critical should hold go-live if open. Export the list to PDF or Excel and use it in the readiness review.

Why these checks matter

Most PM go-live problems come from the same places. Master data without a functional location breaks area reports. Missing settlement rules block order closure and leave costs unreconciled. A maintenance plan without a start date or a deadline job never generates a single order, so preventive work silently stops. Authorization gaps appear when real users try to release or confirm. Each critical item targets one of these known failure modes.

Master data quality drives every downstream report
Settlement must be tested to the receiver, not just configured
Preventive plans need both scheduling and a recurring batch job

Reading the result

A high score with open critical items is still a no-go. Treat critical items as gates and the rest as risk. If many master data items are open, delay the load rather than going live with poor data, because cleaning data after go-live is slower and visible to every user. If training items are open, extend the pilot to a smaller plant or line first, and keep the old process available as a fallback for a defined period.

Frequently Asked Questions

What is the most important SAP PM go-live risk?

Poor master data is usually the biggest risk, followed by untested settlement and preventive plans that never generate orders. If technicians cannot find the equipment or the order cannot be closed, the system loses trust within days of go-live.

How long before go-live should preventive plans be loaded?

Load and schedule plans well before cutover, in a test client first, to check start dates, call horizons and the first generated orders. Plans loaded on cutover weekend without testing often produce duplicate or missing work orders.

Do we need to migrate old work orders?

Usually only open orders and key history are worth migrating. Closed history is often kept in the old system or an archive. Decide which equipment history is needed for reliability analysis, and load only that, with clear mapping of codes.

Does this checklist apply to S/4HANA?

Yes, the core PM controls are the same. On S/4HANA add checks for Fiori apps and roles, business partner setup for partners, and any simplification items that apply to your migration path.

If you want a second pair of eyes on your PM readiness or a way for planners to query the new system in plain language after go-live, get in touch.

Talk to an Expert Explore More Free Tools

Related Tools

SAP

More SAP tools

See all

SAP PM Go-Live Readiness Checklist