All learning series · Manage add-on · Part 1
Maximo IT
Connect a reported service issue to the affected service, asset and resolution.
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.
- Are you ready to use Maximo IT? Licensing and AppPoints, the records that must exist, and three checklists.
- Basics
- Configuration
- Practical example
- Practice and verify
- Advanced concepts
Are you ready to use Maximo IT?
Maximo IT is a separate part you buy with Maximo Application Suite as the prerequisite. The tier changes if Service Provider is installed.
Before configuration
Confirm the part is on the entitlement. Without Service Provider the tier is Limited or Base. With Service Provider installed the tier is Limited or Premium, not Base.
Before the first successful journey
One service, the equipment or configuration item it depends on, and an incident with an impact and a requester.
Before production use
The catalog, the priority rules and the self-service portal have owners. Self-service IT use is 0 AppPoints only for the actions the guidance lists.
Licensing, entitlement and AppPoints
Maximo IT is a separate part. Maximo Application Suite is a prerequisite. The MAS 9.2 licensing guidance prices it at Limited or Base. If Service Provider is installed, the tier is Limited or Premium, and Base is not the tier. Self-service IT applications are 0 AppPoints for receiving help from an agent, searching for solutions, entering and viewing service requests, approving them from the self-serve application, and viewing owned assets. Agents and administrators use the Limited, Base or Premium tier that matches whether Service Provider is installed. There is no Maximo IT install quantity on the install table.
Keep four facts separate for Maximo IT. 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 Maximo IT is deployed and the service desk applications open. Service Provider’s presence changes the user tier, so record whether it is installed before you assign users. Installed means the IT applications open. Configured means a service and a priority exist. Usable means a requester can log an incident and an agent can see it.
Foundation configuration
You need people for the requester and the agent, a service, and the asset or configuration item that service depends on. Classifications and impact codes are the priority rules. Locations matter when the service is a place. A change record is a later IT process and can follow the first incident.
Product configuration
Define the service and its dependency. Set classification, impact and priority. Grant requesters only the self-service actions. Grant agents the incident application. If Service Provider is installed, set the agent’s tier to Limited or Premium before they take incidents. Review the default priority so every ticket does not open as critical.
Infrastructure and integration
Maximo IT runs with the suite. A directory for requesters, a mail gateway or a monitoring tool that opens tickets is an external system with its own credentials and licence. The first incident can be entered in the product.
Data and operational readiness
The first journey needs one service, one related item, one requester and one incident. The agent sees the impact and the item. The requester sees their request and not the agent’s queue. A missing service is configuration. A missing person is data. A Base user rejected because Service Provider is installed is entitlement, not a broken catalog.
Setup order for an incident
- 1. Separate Maximo IT part Suite is the prerequisite. Note whether Service Provider is installed.
- 2. Tier: Limited or Base, or Limited or Premium Base only when Service Provider is not installed.
- 3. Service, dependency, priority The catalog entry and the impact rules.
- 4. Requester incident and agent queue Two people, two groups.
| Requirement | Why needed | Mandatory/Conditional/Optional | Where to configure or verify | Minimum working example | Verification procedure | Consequence if missing | Remediation | Source |
|---|---|---|---|---|---|---|---|---|
| Maximo IT part on the entitlement | The guidance calls it a separate part purchase. The suite alone does not include it. | Mandatory | Proof of entitlement. Catalog. | The part is named on the entitlement and the IT applications are deployed. | Compare the entitlement to the catalog tile. | The team enables IT menus with no part on the agreement. | Add the part before production use. | Licensing in Maximo Application Suite 9.2 |
| The tier that matches Service Provider’s presence | Limited or Base when Service Provider is absent. Limited or Premium when it is installed. | Mandatory | Suite administration → Suite → Administration → AppPoints Usage. Manage → Security → Security Groups, and the suite user type. Whether Service Provider is deployed. | An agent on Base in a suite that has no Service Provider, or on Premium if Service Provider is installed. | Check the Service Provider deployment, then read the agent’s tier. | A Base agent is given IT access on a suite that has Service Provider. | Move the agent to Limited or Premium. | Licensing in Maximo Application Suite 9.2 |
| Self-service only for the listed requester actions | Search, request, approve and view owned assets are the 0-AppPoint IT actions. | Conditional | The self-service IT list in the 9.2 guidance, and the requester group. | Requester REQ-IT can submit and view their request and cannot work the queue. | Sign in as REQ-IT and confirm the agent queue is absent. | The requester works incidents and is still counted at 0. | Give queue access the agent tier. | Licensing in Maximo Application Suite 9.2 |
| A service and a dependent item | The incident is about a service, not a free-text symptom alone. | Mandatory | The IT service catalog and the related asset or configuration item. | Service EMAIL, dependent item MAIL-1. | The service record lists MAIL-1. | Incidents have a priority and no service. | Create the service and the dependency first. | Modules and applications in Maximo Application Suite 9.2 |
| Classification, impact and priority | The agent needs a rule, not only a description. | Mandatory | Classifications and the priority matrix for the installed IT build. | Impact site-wide, priority high, for a named classification. | Log an incident and see the priority the rule sets. | Every incident opens at the same priority. | Enter the rule before the first production queue. | Modules and applications in Maximo Application Suite 9.2 |
| Requester and agent as different people | The journey is the handoff. | Mandatory | Manage → Security → Security Groups, and the suite user type | REQ-IT logs the incident. AGENT-IT owns it. | Each user sees only their side. | The requester closes the incident from the agent queue. | Split the groups. | User access and entitlements in MAS 9.1 and later |
A. Ready to configure
- The Maximo IT part is on the proof of entitlement and the suite is the prerequisite.
- You know whether Service Provider is installed, and the agent tier matches that fact.
- The IT applications open.
- A service name and a requester exist.
B. Ready for the first end-to-end journey
- The service and its dependent item save.
- REQ-IT logs an incident with impact.
- AGENT-IT sees it with the priority the rule set.
- REQ-IT does not see the agent queue.
C. Ready for production operation
- The catalog, priorities and self-service portal have owners.
- Directory and monitoring integrations have their own licences and a tested path.
- Agent tiers are reviewed again if Service Provider is added later.
- Self-service accounts match the actions the guidance lists.
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.
- Licensing in Maximo Application Suite 9.2 — MAS 9.2 licensing guidance, verified 2026-10-18
- User access and entitlements in MAS 9.1 and later — MAS 9.1 and later, verified 2026-10-18
- Accessing the AppPoints Usage Dashboard — MAS 9.2, verified 2026-10-18
- Modules and applications in Maximo Application Suite 9.2 — MAS 9.2, verified 2026-10-18
Before you start
MAS learning path. Match the component documentation to your installed release and maintenance build before configuring it.
- Maximo IT access and test service-desk roles.
- A fictional service, related equipment and training classification/priority rules.
IBM sources + Assetize exercise
01 · Basics — Understand the building blocks
Maximo IT brings IT asset and service management together. A ticket records the reported issue; a configuration item or asset supplies technical context; the service describes business impact.
Incident restoration, root-cause investigation and a controlled change have different purposes. Linking them preserves the full story.
Topics in this series
- Services and assets
- Incident classification
- Assignment and response
- Resolution evidence
- Problems, changes and knowledge
02 · Configuration — Work through the setup
Use a training environment and match the actions to the IBM guide for your installed build.
- Define a training service and identify its dependent equipment or configuration items.
- Log an incident with symptoms, impact and the correct requester.
- Apply the configured classification, ownership and priority rules.
- Record investigation and restoration evidence; link a problem or change when the training process requires it.
- Verify service restoration and capture a reusable resolution before closing the ticket.
03 · Practical example
Fictional teaching example
A fictional telemetry gateway interruption affects maintenance visibility. Restarting a gateway restores service, but repeated interruptions may require a problem investigation and a separately reviewed configuration change.
04 · Practice and verify
Trace the service, incident, technical item, owner and restoration evidence in one record map.
Expected result
The incident is routed and resolved with evidence. Any underlying investigation or change remains separately tracked.
Common mistakes
- Using the same record type for every service-management activity.
- Closing based only on an engineer's action rather than restored service.
05 · Advanced concepts
Explore service dependencies, change impact and knowledge reuse. Validate any AI-generated ticket summary against its underlying records.
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