Maintenance software integrated with SAP PM has no single price, because the cost of the project is the sum of eight blocks: the software vendor's quote, covering implementation and subscription; SAP licensing for the people who will use the system; the integration with SAP; network and infrastructure at the plant; field devices; asset identification tags; your internal team's time; and contingency. Each block has an owner, which can be the vendor, IT or maintenance, and its own way of getting to a number. The budget is complete when all eight are sized for the full contract term, and only on that basis do two quotes become comparable.
The architecture you choose changes how much each block weighs. A CMMS that runs separately from SAP, an app that runs on top of SAP PM and SAP Service and Asset Manager, SAP's own mobile app, split licensing, integration and IT work in different ways. That is why the per-user price on a quote, read on its own, accounts for a small part of the total.
Why maintenance software integrated with SAP has no list price
The price depends on variables only the buyer's operation knows: how many people will use the system, at how many plants, with which modules, through which integration method and under which SAP contract. Two companies with the same number of technicians can get different quotes if one integrates through SAP CPI and the other through a web service, or if one is on RISE with SAP and the other holds an on-premise ERP license.
When a per-user price shows up on a CMMS pricing page, it covers the software subscription, which is one of the eight blocks; the other seven stay out of the math until someone sizes them. How to compare products by architecture is covered in maintenance software options by architecture.
What maintenance software costs per user and for a large plant
The per-user price is the billing rule for one block, and it means little until you know who counts as a user. In preventive maintenance software, a user can be the technician who executes the work order on a phone, the maintenance planner who builds the weekly schedule, the supervisor who approves, or the contractor who only confirms the job, and each vendor decides who is counted. Two other costs also grow per person: the SAP license for whoever uses the app, under your SAP contract, and each technician's device.
At a large plant, what grows beyond the user count are the physical blocks: more dead zones to cover with Wi-Fi, more phones and spares, more equipment and functional locations to tag when QR code scanning is used in the field, more work centers to configure and more key users to train. In a multi-site operation, the first plant usually serves as the template for the others, and the cost of each additional site depends on how much of the first design carries over in the rollout.
Which cost blocks go into a maintenance software budget for SAP PM
The table lists the eight blocks of a complete budget, what each one covers, who usually pays, where the number comes from and how to size it before you request quotes.
| Block | What it covers | Who pays | Where the number comes from | How to size it |
|---|---|---|---|---|
| Software quote | Implementation (design, configuration, testing, training and go-live) and the software subscription, including hosting when the product runs in the vendor's cloud | Maintenance or IT, depending on company policy | The vendor's quote | Ask for a quote by module, number of users per role and number of plants, with one-time and monthly charges shown separately |
| SAP licensing | The metric for whoever uses the app: named user, FUE under RISE with SAP, or SAP Digital Access by document | IT, under the SAP contract | Your current SAP contract and your SAP account team | Count users by role, estimate the work orders, notifications and confirmations created per year, and confirm the classification with your SAP account team |
| Integration | Connection method (web service exposed through SOAMANAGER, SAP PI, SAP CPI, RFC or your own integration platform), interface users and failure monitoring | IT | The vendor's quote and your integration platform contract | Choose the method with your SAP architects; if the integration runs through SAP Integration Suite, add its subscription and consumption |
| Network and infrastructure | Wi-Fi in dead zones, an integration server or gateway when one is needed, single sign-on, firewall rules, and vendor access to SAP systems through VPN or SAP Router | IT | A coverage and infrastructure survey of the plant | Map where work orders are executed, measure signal in those areas and list the access the vendor requires |
| Field devices | Standard, rugged or hazardous-area certified phones, spares, accessories, mobile device management (MDM), data plans and replacement after breakage | Maintenance or IT | A hardware quote and your device policy | Count technicians per shift, separate those who work in hazardous areas, and set the spare ratio and the refresh cycle |
| Asset tags | QR code tags on equipment and functional locations, printing and mounting, when field scanning is used | Maintenance | The equipment and functional location master data in SAP PM | Count the objects that will get a tag and pick a material that holds up in each area |
| Internal team time | Key users, IT and Basis, user acceptance testing and training for the crews | Maintenance and IT, in hours | The vendor's project plan | Turn each project phase into hours per person and per phase |
| Contingency | A reserve for scope changes, customization and project surprises | Whoever approves the budget | Company finance policy | Size it by the uncertainty left in the other seven blocks, higher where the survey was incomplete |
Integration has a cost under every method
Exposing a web service through SOAMANAGER takes Basis and authorization setup in SAP. When you already run SAP PI or SAP CPI, the integration reuses that platform, with its own contract and consumption. A direct RFC call or your own integration platform also needs configuration, an interface user and someone to watch for failures. The interface user follows your security and licensing policy, and monitoring needs an owner from day one: what to log and how to handle integration errors is covered in the SAP PM integration log.
Internal team time counts in hours, even when it is not on the quote
The hours your company spends on the project do not show up in the vendor's price, and they exist under every architecture. IT grants access to the development, quality and production systems, creates users and opens the firewall. Maintenance key users take part in the design, run user acceptance testing and pass the training on to the crews. Turning those phases into hours per person puts on the books the time the project takes away from plant routine.
How architecture changes the cost: a separate CMMS, an app on top of SAP PM or SAP Service and Asset Manager
Three paths come up when a company that runs SAP PM budgets for maintenance software, and each one shifts cost among the vendor, IT and maintenance.
A CMMS separate from SAP
A CMMS that runs separately from SAP, in the cloud or on premises, has its own asset register, maintenance plans and history. For a site that already runs SAP PM, that means keeping data in two places or building and maintaining an integration that moves work orders, notifications, confirmations, costs and materials between the two systems, because cost, inventory and purchasing stay in the ERP. The budget then has to cover the initial master data migration, ongoing reconciliation between the two databases and getting your data out when the contract ends. If the CMMS creates documents in SAP through the integration, the SAP licensing question applies to it too. What a CMMS is and when it makes sense is covered in what is a CMMS.
An app or layer that runs on top of SAP PM
An app on top of SAP PM uses SAP itself as the system of record: equipment, functional locations, plans, work orders and history stay in the ERP, and the app takes execution, scheduling and data capture out to the field. Master data is not duplicated, the integration with SAP PM is part of the product, and the project sets the connection method. PM RUN follows this model. The blocks that weigh most here are the vendor's quote, SAP licensing for field users under your SAP contract, and devices.
SAP Service and Asset Manager
SAP Service and Asset Manager, the successor to SAP Asset Manager, is SAP's mobile app for maintenance, service and safety technicians. According to the version 2511 Quick Start Guide, dated April 2026, it requires a subscription to the app, sold in the SAP Mobile Execution and Dynamic Forms bundle in Basic, Standard and Professional usage types; an SAP BTP account with Mobile Services active, plus Application Runtime and SAP Business Application Studio in the Cloud Foundry environment; Cloud Connector; SAP Gateway; and, on ECC or on S/4HANA releases 1610 to 1809, the mobile add-on installed in SAP. For S/4HANA Cloud Public Edition, SAP points to a different app, SAP Maintenance Assistant.
The same guide addresses technician licensing: the subscription gives access to equivalent transactions in SAP, without full transaction access, and the user has to be classified with a special user type in SAP's system measurement, through transaction USMM, so that it is not also counted as a named user. Custom app development is not included; extensions stay inside the app.
The table compares where each block weighs on the three paths. It describes the architecture; the details of each offer come from the vendor's quote.
| Block | CMMS separate from SAP | App on top of SAP PM | SAP Service and Asset Manager |
|---|---|---|---|
| Software | CMMS subscription or license, plus implementation | Vendor quote, with implementation and subscription | Subscription to the SAP Mobile Execution and Dynamic Forms bundle, with implementation quoted separately |
| Master data and history | In two systems, with initial migration and reconciliation | In SAP PM | In SAP PM |
| Integration | Built and maintained between the CMMS and the ERP | Part of the product, with the connection method set in the project | SAP BTP Mobile Services, Cloud Connector and SAP Gateway |
| SAP license for users | Depends on whether the CMMS creates documents in SAP; confirm with your SAP account team | Named user, FUE or Digital Access, under your contract | Comes with the app subscription, with users classified under a special user type in SAP; anyone who also uses other SAP software outside that scope follows the user type in your contract |
| Platform | The CMMS vendor's, or your own server | The vendor's cloud, when the product runs in the cloud | Your company's SAP BTP account |
| Devices, network and tags | Same survey on all three paths | Same survey on all three paths | Same survey on all three paths |
| Internal team | Administering two master data sets | SAP IT team and key users | SAP and SAP BTP administrators, a security expert and key users |
| Exit at contract end | Export history from the CMMS | History already stored in SAP | History already stored in SAP |
What to plan for in a field project on any of the three paths is covered in the SAP PM mobile project.
How SAP licensing for field users fits into the budget
SAP licensing for whoever uses the app depends on your company's contract with SAP, and no software vendor decides that classification. Under an on-premise ERP contract, access can be measured by named user or by SAP Digital Access. Under the SAP Software Use Rights in version v.10-2026, Digital Access licenses use of the ERP through directly integrated non-SAP applications without requiring a named user for the people using them, and it is licensed exclusively on the number of documents created annually; maintenance notifications and work orders are Service & Maintenance Documents, and, under this metric, a lookup does not create a document. Under RISE with SAP, users are measured in FUE (Full Use Equivalent), and access through third-party applications has its own metric, also based on documents created per year.
The same terms treat user interfaces to the ERP as part of the ERP, requiring a named user for whoever uses them. That is why the classification of an app comes out of a contract review with your SAP account team. As of November 2026, SAP does not publish list prices for any of these metrics. How to count users, estimate documents and run that conversation is covered in SAP licensing for maintenance technicians, and the FUE metric in RISE with SAP.
What you pay once and what you pay every month over the contract term
Comparing quotes on first-year cost favors whoever charges little for implementation and more for the subscription, or the reverse. A total cost that holds up in a finance review adds the blocks over the full contract term and separates one-time charges from recurring ones. The table shows that split block by block.
| Block | One-time | Recurring |
|---|---|---|
| Software | Implementation | Subscription |
| SAP licensing | Additional licenses or Digital Access documents, when the contract calls for them | SAP maintenance or subscription, under your contract |
| Integration | Configuration and testing | Integration platform subscription and consumption, plus failure monitoring |
| Network and infrastructure | New Wi-Fi, gateway and firewall rules | Network operations and support |
| Field devices | Initial purchase, accessories and spares | Data plans, MDM, replacement after breakage and refresh at the end of the cycle |
| Asset tags | Printing and mounting for the existing register | Damaged tags and newly registered assets |
| Internal team | Project hours, user acceptance testing and training | Training new team members and user administration |
| Contingency | Project reserve | Scope changes requested after go-live |
Device refresh drops out of a spreadsheet that only looks at year one. When the phone refresh cycle set by IT is shorter than the software contract term, the purchase repeats within the period, and the budget needs to show it. Ask each vendor for the minimum Android and iOS versions the app supports, because that decides when a phone that still works stops being usable.
What to ask every vendor to compare quotes
The questions below put different quotes on the same basis. The third column says why the answer changes the total.
| Topic | Question | Why it changes the total |
|---|---|---|
| Billing rule | What metric is the subscription billed on (named user, active user, site or asset), and who counts as a user? | It sets the cost of each role: technician, planner, supervisor and contractor |
| Growth | What happens to the price when the number of users or sites grows, and is there a rule for scaling down? | The rollout to other plants changes the math for the following years |
| Subscription | What does the subscription include: hosting, version upgrades, support and a test environment? | Anything outside the subscription comes back as a separate cost |
| Integration | Who configures the SAP integration, through which method, and who monitors failures? | It sets IT hours and whether an integration platform is needed |
| Customization | What is standard product and what is customization billed separately? | Anything outside the standard becomes a new budget after the contract is signed |
| What your company provides | Which SAP system access, users, devices, firewall rules and SAP settings are on your side? | Each item becomes an internal or third-party cost |
| Documents in SAP | How many documents does the app create in SAP per executed work order, and which users does it connect with? | It is the basis for the licensing conversation with your SAP account team |
| Project phases | What are the phases, what is remote, what is on site, and who pays for travel? | Travel and internal team hours depend on it |
| Exit | In what format does the data come out at the end of the contract? | A future migration has a cost too |
How to defend the maintenance software budget to leadership
A business case that survives a finance review shows, over the same horizon, the cost of every block and a return that can be verified. Two mistakes sink it: multiplying every freed-up hour by the crew's average cost and calling the result savings, and leaving out the incremental costs that make the gain possible. A freed-up hour from a fixed crew becomes capacity for other work; it becomes cash when it cuts an identifiable expense, such as overtime or contractor hours.
For a first estimate, the maintenance ROI diagnostic for planners asks for plant sector, number of maintenance technicians and planners and operating regime, compares your indicators with your industry median and top performers, and returns the estimated return as a range, with the assumptions on display. That result sits next to the sum of the eight blocks, over the same period, so leadership sees cost and return on one page.
Where PM RUN fits in this budget
PM RUN is the maintenance execution, mobility and planning platform that runs on top of SAP PM, on ECC 6.0 or S/4HANA, on premises or in the cloud, without replacing SAP. It is contracted through a fixed-scope proposal, with the modules you choose and implementation priced separately from the subscription. PM RUN's cloud servers are part of the proposal, and PM RUN configures the integration while your company grants the users and access. What goes into the proposal and what your company provides is on PM RUN pricing and quotes, and the modules on maintenance software for SAP PM.
Frequently asked questions
How much does maintenance software cost?
There is no single price. The cost of maintenance software integrated with SAP PM is the sum of eight blocks: the software quote, SAP licensing, integration, network and infrastructure, field devices, asset tags, internal team time and contingency. The per-user price on a quote covers only the software subscription.
How much does CMMS software cost per user?
It depends on the vendor's billing metric and on who it counts as a user: technician, planner, supervisor or contractor. On top of the per-user subscription come the SAP license for whoever uses the app, under your SAP contract, and each technician's device.
What does maintenance software cost for a large manufacturing plant?
At a large plant, the user count grows and so do the physical blocks: Wi-Fi coverage, phones and spares, QR code tags on assets, work centers to configure and key users to train. Across several plants, the first one serves as the template, and the cost of each additional site depends on how much carries over in the rollout.
Is CMMS pricing comparable to the cost of an app on top of SAP PM?
Only the total answers that. A CMMS subscription can be lower, but the budget then has to carry integration with the ERP, master data kept in two places, the initial migration and data exit at the end of the contract, and the SAP licensing question remains if the CMMS creates documents in SAP.
Does an app integrated with SAP remove the need for SAP licenses for technicians?
No. Using SAP through the app is still licensed, and your contract sets the metric: a named user per technician; SAP Digital Access, which counts documents created per year and does not require a named user for people working through a directly integrated non-SAP application; or, under RISE with SAP, FUE and S/4HANA Cloud, Digital Access. If SAP treats the app as a user interface for the ERP, each technician needs a named user. The call comes out of a review with your SAP account team.
Does the SAP integration have a cost?
Yes, under every method: a web service exposed through SOAMANAGER, SAP PI, SAP CPI, RFC or your own integration platform. All of them need configuration, an interface user and monitoring. When the integration runs through SAP Integration Suite, its subscription and consumption go into the IT budget.
Who pays for technicians' phones and tablets?
Your company, through maintenance or IT depending on internal policy. The budget covers the device type (standard, rugged or hazardous-area certified), spares, accessories, MDM, data plans, replacement after breakage and the refresh cycle.
What should a maintenance software quote include?
Implementation and subscription shown separately, the billing rule and what happens when users or sites grow, what the subscription includes, who configures the SAP integration, what counts as customization billed separately, what your company provides and the project phases.
References
- SAP. SAP Software Use Rights, enGLOBAL v.10-2026. Accessed November 8, 2026.
- SAP. SAP Cloud ERP Private, Service Description Guide, v.12-2025. Accessed November 8, 2026.
- SAP Learning. Explaining SAP Service and Asset Manager Features. Accessed November 8, 2026.
- SAP Help Portal. SAP Service and Asset Manager 2511, Quick Start Guide. Accessed November 8, 2026.