Assetize

All learning series · Manage add-on · Part 1

Maximo Service Provider

Understand customer boundaries before agreements, pricing and billing.

Start here

Confirm this product is ready, then use the lesson. The readiness checks are the gate for configuration, for a first journey and for production.

  1. Are you ready to use Maximo Service Provider? Licensing and AppPoints, the records that must exist, and three checklists.
  2. Basics
  3. Configuration
  4. Practical example
  5. Practice and verify
  6. Advanced concepts

Are you ready to use Maximo Service Provider?

Service Provider is the add-on for a business that maintains other companies’ assets. Have the customer, the agreement and the user’s tier in place before you create a billable work order.

Before configuration

Maximo Manage is the prerequisite. Service Provider is an add-on priced at Premium, or at Limited when the user’s three modules include Service Provider. A Base user who is given this add-on is outside the Base tier.

Before the first successful journey

Two customers, one agreement or price schedule, a site, and a work order you can attribute to one customer.

Before production use

The IBM service-provider terms apply when you process a client’s data. Bill review can be a self-service application at 0 AppPoints. Everyone who maintains the client’s assets still needs their own tier.

Licensing, entitlement and AppPoints

Service Provider is a Maximo Manage add-on. The MAS 9.2 licensing guidance prices industry solutions and add-ons at the Premium tier, or at Limited when the user selects up to three modules and those modules include the add-on. There is no Base tier once the user is given an add-on application. The guidance does not publish a separate Service Provider install quantity. It does publish an additional rule: a customer that uses Maximo to manage assets for a third party deploys Service Provider, unless a waiver is approved by the named IBM sales, price and product roles in that topic. Bill Review is in the self-service list at 0 AppPoints. The people who plan and perform the work are not covered by that self-service row.

Keep four facts separate for Maximo Service Provider. Entitlement is the proof of entitlement and the License Information for IBM Maximo Application Suite. The MAS 9.2 licensing guidance supplements that agreement. Available AppPoints are the pool shown on the AppPoints Usage dashboard: Suite administration, then Suite, then Administration, then AppPoints Usage. Assigned access is the security group together with the user type on the person: Limited, Base or Premium, and Authorized or Concurrent. Consumption is what that assignment draws. Authorized users and administrators reserve AppPoints continuously. Concurrent users draw AppPoints while they are signed in. Install AppPoints stay reserved for the life of that environment. A non-production install of a component draws no install AppPoints when the same component is already installed in production. Administrators and User Management users open the dashboard. Other people need the LICENSEUSAGE security group. Compliance enforcement and idle timeout sit on the dashboard Configuration tab and are suite-administrator settings.

The same guidance publishes these user conversion ratios: Limited is 5 AppPoints for one concurrent user and 2 for one authorized user; Base is 10 concurrent and 3 authorized; Premium is 15 concurrent and 5 authorized; an administrative Base user is 10 AppPoints and an administrative Premium user is 15, both as authorized users. A Base administrator who already reserves 10 AppPoints can be given Premium application access with no further AppPoints. Those ratios were read from the MAS 9.2 licensing guidance on 18 October 2026. Your agreement sets how many AppPoints you purchased. An application that opens shows that the component is deployed. Read the proof of entitlement and the dashboard as well.

Installed and enabled applications

Confirm the Service Provider applications are deployed with Manage and that Customers (SP) opens. The modules page lists a Service Provider module. Installed means the applications are on the menu for an administrator. Usable means a customer-restricted user sees only their customer’s records.

Foundation configuration

You need an organization and a site, people for your own staff, and customer records that are not your own organization. Locations and assets belong to a customer when the journey is about their equipment. Crafts and labor rates matter when the agreement prices labor. They can wait until the first billable work order. GL accounts matter when the bill has to land in your books.

Product configuration

Create the customers, then the customer authorization and the price schedule or agreement the work will use. Grant internal staff a group that can see the customers they serve, and grant a customer user a group that cannot see the other customer. Review the default that shows every customer to a new administrator group before that group is used in production.

Infrastructure and integration

Service Provider runs in Manage. A customer portal or a separate billing system is an extra integration with its own credentials. No map, TURN server or optimization service is required for the first customer work order.

Data and operational readiness

The first journey needs two fictional customers, one asset or location for the first customer, and one work order charged to that customer. The second customer’s user must not see that work order. A missing customer is data. A user who sees both customers is security. A missing application is the add-on or the group.

Setup order for a customer work order

  1. 1. Add-on entitlement at Premium or Limited Base is not the tier once Service Provider applications are granted.
  2. 2. Two customers and an agreement The agreement is what makes the work billable.
  3. 3. Staff group and customer group Different customers stay in different result sets.
  4. 4. One asset and one work order Attributed to the first customer, invisible to the second.
Readiness for Maximo Service Provider
RequirementWhy neededMandatory/Conditional/OptionalWhere to configure or verifyMinimum working exampleVerification procedureConsequence if missingRemediationSource
Premium or Limited entitlement for Service ProviderAdd-on applications are Premium, or Limited inside the three-module rule. Base excludes them.MandatorySuite administration → Suite → Administration → AppPoints Usage. Manage → Security → Security Groups, and the suite user type.A dispatcher as Premium, or as Limited with Service Provider inside the three modules.Grant the group and read the tier the dashboard assigns. Confirm it is not Base.The user is priced as Base and then given the add-on, which the guidance does not allow.Move the user to Premium, or keep them Limited and inside three modules that include Service Provider.Licensing in Maximo Application Suite 9.2
The service-provider terms, when the assets belong to a clientThe guidance requires Service Provider for managing a third party’s assets, unless the named waiver is in place.ConditionalYour proof of entitlement and the additional terms in the 9.2 licensing guidance.Service Provider deployed because the site maintains Client A’s pumps.Match the business model to the add-on on the entitlement. Record a waiver if you have one.Maximo holds a client’s assets and Service Provider is not part of the entitlement.Add the add-on or complete the waiver path the guidance names.Licensing in Maximo Application Suite 9.2
Two customer recordsThe product’s job is to keep customers apart.MandatoryCustomers (SP).AZ-CUST-A and AZ-CUST-B, each with a name and a site.Search each customer and confirm they are different records.Work has nobody to bill.Create the customers before agreements or work orders.Modules and applications in Maximo Application Suite 9.2
An agreement or price scheduleA work order becomes service-provider work when a customer and a price are attached.MandatoryThe agreement or customer billing setup for the installed build.One labor rate for CUST-A on craft ELECT.Create a training work order for CUST-A and see the rate offered.The work order exists and the bill has no price.Attach the agreement before the first billed actual.Modules and applications in Maximo Application Suite 9.2
Separate security for staff and for a customer userCustomer users should see their own work. Staff see the customers they are assigned.MandatoryManage → Security → Security Groups, and the suite user typeGroup SP-STAFF for both customers. Group SP-CUSTA for CUST-A only.Sign in as each user and compare the work-order list.The customer user sees the other customer’s work order.Restrict the group by customer. Do not share one administrator group as the customer login.User access and entitlements in MAS 9.1 and later
Bill Review as self-service, for reviewers onlyThe guidance lists Bill Review at 0 AppPoints. That row is not a licence for planners.OptionalThe self-service list in the 9.2 licensing guidance, and the Bill Review application.A customer reviewer who only opens Bill Review.Confirm that user’s dashboard consumption stays on the self-service row and that they cannot plan work.A reviewer account is also used to create work orders and is still treated as free.Give work-planning access its Premium or Limited tier.Licensing in Maximo Application Suite 9.2

A. Ready to configure

  • The proof of entitlement includes Service Provider and the user’s dashboard tier is Premium or a qualifying Limited.
  • Customers (SP) opens.
  • The organization and site exist.
  • You have names for two fictional customers and one price.

B. Ready for the first end-to-end journey

  • Both customers exist.
  • One work order is stored against the first customer and picks up the training rate.
  • The second customer’s user does not see that work order.
  • A staff user does see it.

C. Ready for production operation

  • Client data is covered by the service-provider terms in your agreement.
  • Customer security is tested with a real customer user, not only with an administrator.
  • Rates, agreements and GL accounts have an owner.
  • Bill Review users are only the people who match the 0-AppPoint self-service description.

Sources for this readiness check

Licence statements come from the IBM topic named on the row. Installation of a component is a separate check from entitlement.

Before you start

MAS learning path. Match the component documentation to your installed release and maintenance build before configuring it.

  • Service Provider installed and accessible.
  • Two fictional customers, customer-specific test users and a training work order.

IBM sources + Assetize exercise

01 · Basics — Understand the building blocks

Service Provider introduces customer-aware service delivery. Customers, customer objects and security-group authorization determine which customer information a user can access.

Customer agreements define service terms; price and billing schedules express commercial rules. A work order cost and a customer charge answer different questions.

Topics in this series

  • Customers and data access
  • Agreements and scope
  • Price schedules
  • Service delivery and SLAs
  • Billing and reconciliation

02 · Configuration — Work through the setup

Use a training environment and match the actions to the IBM guide for your installed build.

  1. Create training customers AZ-CUST-A and AZ-CUST-B in Customers (SP).
  2. Review Customer Objects (SP) and group customer-authorization settings before adding operational data.
  3. Associate a training asset and work order with customer A. Confirm that customer B's user cannot access them.
  4. Define a small customer agreement and a price schedule using the installed-version procedure. Use a single, explainable charge.
  5. Record the work actuals, follow the agreement application and billing preparation process, and inspect the resulting bill details. Do not send a real invoice.

03 · Practical example

Fictional teaching example

A fictional service firm records two hours of labor at an internal cost of $80 per hour and a training charge of $120 per hour. The expected cost is $160 and the illustrative labor charge is $240 before any other terms; the configured agreement must explain the difference.

04 · Practice and verify

Prepare a customer-boundary matrix and trace a single test transaction from customer to work order to billing detail.

Expected result

Customer A and B remain separated. Each charge can be reconciled to its agreement rule and underlying transaction.

Common mistakes

  • Treating internal work cost as the bill price.
  • Testing only with an administrator who can see every customer.

05 · Advanced concepts

Add agreement revisions, fixed fees, response plans and SLA behavior one at a time. Re-test historical transactions against their applicable dates and terms.

IBM references

Product explanations link to IBM sources. Scenarios and exercises are original Assetize teaching material. Reviewed 2026-10-01.

Maximo ecosystem overview · Manage learning paths · Practice data in Workbench