# SAP PM Go-Live Readiness Checklist > Source: https://netray.co/tools/sap-pm-go-live-readiness-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A checklist to test whether your SAP PM implementation or rollout is ready to go live, grouped by master data, configuration, planning, access and cutover. ## Category sap ## Erp SAP ECC / S/4HANA ## Audience - SAP PM consultant - Project manager - Maintenance manager ## Tool **Kind:** checklist **Scoring Note:** 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. **Groups:** #### Master data **Items:** **Text:** Functional location structure indicator and numbering approved by maintenance **Critical:** true **Text:** Equipment categories defined and mapped to the asset register **Critical:** true Every equipment record has a functional location or an agreed reason it does not **Text:** Maintenance plant, cost center and planning plant filled on technical objects **Critical:** true Equipment classes and characteristics loaded for reporting Work centers created with capacity, cost center and activity types Measuring points and counters set up for condition-based plans Spare parts BOMs linked to equipment and functional locations Duplicates and obsolete equipment removed before load #### Configuration **Items:** **Text:** Order types, notification types and number ranges configured and tested **Critical:** true **Text:** Order type to settlement profile and cost center assignment checked **Critical:** true Planner groups and partner roles defined per plant Catalog profiles and damage, cause and activity codes agreed Maintenance strategies and packages created User status profiles configured where waiting states are needed Priority and scheduling parameters tested end to end Print forms for work orders and permits approved #### Planning and execution **Items:** Task lists built for the first wave of preventive plans **Text:** Maintenance plans created and scheduled with correct start dates **Critical:** true **Text:** Deadline monitoring (IP30) set up as a background job with a plant variant **Critical:** true **Text:** Corrective cycle tested: notification, order, release, issue, confirm, TECO **Critical:** true Reservations and goods issue to orders tested with real spare parts Time confirmation tested including final confirmation **Text:** Order settlement tested to cost center or asset **Critical:** true Backlog and open work orders loaded or agreed to be closed in the old system #### Access and interfaces **Items:** **Text:** Roles by process step tested, including authorization on order type and plant **Critical:** true Segregation of duties reviewed for release, goods issue and settlement Interface to purchasing and stores tested for non-stock parts Interface to finance and cost reporting tested Mobile or tablet app tested with real technicians if used Reports for backlog, compliance and cost agreed with maintenance #### Training and cutover **Items:** **Text:** Key users trained and have signed off user acceptance tests **Critical:** true End users trained with role-specific quick guides **Text:** Cutover plan with load sequence, owners and times approved **Critical:** true Fallback and rollback plan documented Hypercare support plan and issue triage owner named **Text:** Data load reconciliation counts signed off by maintenance **Critical:** true ## Content **Intro:** A maintenance system fails on go-live day when technicians cannot find equipment, plans do not generate orders, or goods issue is blocked. This checklist covers what to verify in an SAP PM implementation before you switch over. **Sections:** #### How to use the checklist **Body:** 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 **Body:** 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. **Bullets:** - 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 **Body:** 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. **Cta:** 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. **Faq:** #### What is the most important SAP PM go-live risk? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms sap pm go live checklist, sap pm implementation checklist, sap plant maintenance cutover, sap pm rollout readiness, sap pm master data checklist, sap pm testing checklist, sap eam go live, sap pm project template --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json