All learning series · Foundation · Part 1
The Maximo Ecosystem: What Each Component Does
Find your way around MAS: the platform, maintenance, asset performance, field execution, industry extensions and enterprise connections.
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 The Maximo Ecosystem: What Each Component Does? 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 the Maximo ecosystem?
Before you configure any product, name the job and the component that owns it. Entitlement, deployment and a security group are three different checks.
Before configuration
You need the suite agreement, the list of deployed applications, and one maintenance outcome you are trying to change.
Before the first successful journey
The component that owns the outcome is deployed, a user of the right tier can open it, and the record they will change already exists.
Before production use
Each deployed component has an owner, a tier and a support path. A catalog tile is not a working process.
Licensing, entitlement and AppPoints
Maximo Application Suite is licensed in AppPoints. The MAS 9.2 licensing guidance is the map of which application sits at Limited, Base or Premium, and which components add an install quantity. Manage, including Scheduler, Linear and Calibration, is the maintenance system. Spatial adds a 20-point install. Industry solutions and add-ons are Premium or Limited, and several of them add their own install points. Monitor is Limited. Health is Base. Predict and Visual Inspection are Premium, and Visual Inspection adds install points. Your proof of entitlement is the quantity you purchased. The dashboard is what this suite is consuming. This orientation does not replace the readiness section on the product you are about to configure.
Keep four facts separate for the suite. 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
Open the suite catalog and write down what is deployed and each component’s version. Manage’s version is not the version of every add-on. An application that opens is deployed. The user’s tier is the entitlement check. The record they save is the usable check.
Foundation configuration
Organizations, sites, people and assets live in Manage and are reused by the products that sit on top. Configure that foundation in the product course that needs it. This page only asks you to know which site the outcome belongs to.
Product configuration
Pick the one product whose course you will follow next. Use that course’s readiness table rather than a generic setup. Security groups are what move a person from one tier to another, so grant the group and then read the dashboard.
Infrastructure and integration
A client-managed suite needs OpenShift entitlement for the cores it uses, as the licensing guidance describes. SaaS draws from the subscription pool and bills from hourly usage. Product-specific routes, GIS, TURN and external systems are in the product course.
Data and operational readiness
Bring one real outcome, such as repeat failures on one asset class. The first useful record is the asset, the work or the reading that outcome needs. A missing application is a catalog decision. A missing record is data. A refused menu is the group or the tier.
How to choose the next course
- 1. Name the outcome The decision or the record that has to exist.
- 2. Name the component Manage, an industry solution, an add-on, a suite application or a connector.
- 3. Read that product’s readiness section Its tier, its install line and its first records.
- 4. Then configure In that product’s course, not in a second collection.
| Requirement | Why needed | Mandatory/Conditional/Optional | Where to configure or verify | Minimum working example | Verification procedure | Consequence if missing | Remediation | Source |
|---|---|---|---|---|---|---|---|---|
| A proof of entitlement for the suite | AppPoints are the pool. Products draw from it in different ways. | Mandatory | Your agreement and License Information. The 9.2 licensing guidance as the supplement. | The purchased AppPoint quantity, written down beside the dashboard’s available pool. | Compare the agreement with AppPoints Usage. | A deployed application is treated as a purchased one. | Read the agreement. Deployment is the next row. | Licensing in Maximo Application Suite 9.2 |
| The catalog of what is actually deployed | Versions differ by component. | Mandatory | Suite administration → Catalog | A list of deployed applications and versions for this workspace. | Open the catalog and record Manage and each add-on separately. | A procedure from one version is followed on another. | Match the product course to the version you recorded. | Modules and applications in Maximo Application Suite 9.2 |
| A user whose tier matches the product | Limited, Base and Premium include different applications. | Mandatory | Suite administration → Suite → Administration → AppPoints Usage. Manage → Security → Security Groups, and the suite user type. | One person granted only the product you are evaluating. | Read the tier after the group is applied. | The administrator’s tier is used as if everyone had it. | Test with the user who will do the job. | User access and entitlements in MAS 9.1 and later |
| One site for the outcome | Foundation data is site-specific. | Mandatory | Organizations and Sites in Manage. | The site that owns the asset you care about. | Open the site and confirm the user can see it. | Records are created in the wrong site. | Select the site before the product setup. | Modules and applications in Maximo Application Suite 9.2 |
| The product course, not this orientation | Each product has its own install line and first journey. | Mandatory | The readiness section of the product course. | You leave this page for that product’s Start here. | The product section’s checklists A, B and C are the ones you tick. | The suite overview is used as the configuration guide. | Open the product course. | Licensing in Maximo Application Suite 9.2 |
| OpenShift or SaaS, matching how you bought the suite | Client-managed suites need core entitlement. SaaS bills the shared pool hourly. | Conditional | The 9.2 licensing guidance for OpenShift. The SaaS AppPoints topic for subscriptions. | The offer named on your agreement. | Confirm client-managed or SaaS before you read an install line. | A customer-managed install quantity is applied unchanged to a SaaS bill, or the reverse. | Use the topic that matches the offer. Maintenance Cost Insights is the course that calls out a SaaS-specific part. | AppPoints for Maximo Application Suite as a Service |
A. Ready to configure
- The agreement and the dashboard have both been opened.
- The deployed applications and versions are listed.
- The site for the outcome is known.
- The next product course is chosen.
B. Ready for the first end-to-end journey
- A user of the intended tier can open that product.
- The first record the product course names can be created or is already there.
- You can say which check failed when something is missing: entitlement, deployment, group or data.
- The product course’s own checklist B is the one you complete next.
C. Ready for production operation
- Each deployed component has an owner.
- User tiers are reviewed when groups change.
- Install AppPoints are read per product, not copied from a neighbour.
- SaaS usage or client-managed capacity is reviewed on the report that matches the offer.
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
- AppPoints for Maximo Application Suite as a Service — MAS as a Service, verified 2026-10-18
- Modules and applications in Maximo Application Suite 9.2 — MAS 9.2, verified 2026-10-18
Before you start
An orientation to the Maximo ecosystem, with Maximo 7.6.1.3 as the classic EAM baseline and MAS as the suite context. Availability, product names and deployment choices vary by release and entitlement. This lesson does not require a running lab.
- Bring one maintenance problem you want to solve, such as repeat pump failures or delayed field updates.
- If you have suite access, keep the installed-application list and component versions beside the IBM catalogue. Otherwise, complete the exercise on paper.
IBM sources + Assetize exercise
01 · Basics — Understand the building blocks
The name Maximo can describe a maintenance application, a family of asset products or the whole Application Suite. Start by asking which business responsibility you mean. Recording work, watching equipment, assessing condition and choosing a replacement investment are different jobs, even when they concern the same asset.
Maximo Manage handles the operational asset and maintenance records: assets, locations, work orders, preventive maintenance, inventory, purchasing and related processes. MAS provides the suite environment in which applications are administered and accessed. OpenShift supplies the container platform for client-managed suite deployments. A platform service, a Manage extension and a suite application belong at different levels of an architecture.
Asset performance applications help teams interpret observations and decide where to focus. Monitor deals with operating signals; Health organizes condition and health assessment; Predict adds predictive analytics. Visual Inspection analyzes images. These capabilities need suitable data and deliberate connections to the maintenance process. An analytical result becomes useful when someone can review it and take an accountable action.
The ecosystem also includes industry solutions, add-ons, field applications and connectors. An industry solution adapts processes to a sector. An add-on extends a specific responsibility, such as maps or customer billing. A connector carries defined business information between systems. Their presence in the catalogue does not mean every component is installed in your environment.
| Component | What it does | Typical output |
|---|---|---|
| MAS platform and suite administration | Administer the suite, users, access and deployed applications. | An application catalogue and access to the components enabled for your environment. |
| Maximo Manage | Run asset, maintenance, inventory and purchasing processes. | Operational records, work plans, actuals and maintenance history. |
| Maximo Mobile | Let field teams perform supported Manage tasks, including configured offline work. | Field observations and work updates synchronized with Manage. |
| IoT connectivity | Connect device identities and operational measurements to downstream consumers. | A defined data path with asset identity, timestamps and units. |
| Maximo Monitor | Monitor operating data and conditions. | Monitoring views and alerts for investigation. |
| Maximo Health | Assess asset condition and prioritize attention using configured health information. | Health assessments that a reliability team can interpret. |
| Maximo Predict | Apply predictive models to asset degradation, failure and anomalies. | Model-dependent predictions with a defined time window and data context. |
| Maximo Visual Inspection | Train and use visual models to evaluate images for defined defects or conditions. | Image-based inference results for review and follow-up. |
| Maximo Collaborate | Connect technicians with remote expertise. Formerly named Assist. | A collaboration session supporting diagnosis and knowledge sharing. |
| Planning and Scheduling | Plan work against dates, people and resource availability. | A work schedule whose assumptions can be checked. |
| Maximo Optimizer | Support optimization problems through objectives and constraints. | A solution or an explanation that the constraints cannot be satisfied. |
| Reliability Strategies | Relate equipment functions and failure modes to appropriate maintenance tasks. | A justified maintenance strategy for implementation and review. |
| Asset Investment Planning | Compare asset interventions over a planning horizon and budget. | Investment scenarios and an approved plan linked to execution. |
| Spatial | Connect maintenance records with geographical features and maps. | A site-qualified operational record linked to its GIS feature. |
| Service Provider | Manage customer-specific service agreements, pricing and billing. | Customer-separated service records and traceable charges. |
| Health, Safety and Environment | Support risk, incidents, permits and controlled change within maintenance processes. | Risk and action records tied to responsible owners. This is distinct from Maximo Health. |
| Asset Configuration Manager | Track approved equipment configuration and installed component structure. | A configuration record against which installed equipment can be checked. |
| Industry solutions | Add sector processes for Utilities, Aviation, Transportation, Nuclear, Oil & Gas, Civil Infrastructure and Renewables. | Sector-specific records and workflows, selected for the business need. |
| Maximo IT | Support IT asset and service-management processes. | Service issues and changes related to IT assets and services. |
| Enterprise connectors | Exchange defined information with systems such as SAP, Oracle, Workday, Envizi and TRIRIGA. | Mapped transactions with clear ownership, acknowledgements and exception handling. |
| Maximo Real Estate and Facilities | Address real estate and facilities responsibilities; part of the suite catalogue from MAS 9.1. | Facilities and property processes alongside asset maintenance. |
Topics in this series
- Suite platform versus business applications
- Manage and field execution
- Monitoring, health and prediction
- Reliability and investment decisions
- Add-ons, industry solutions and connectors
02 · Map a business need to its components
Check each proposed handoff against the installed applications.
- Write the outcome first: for example, reduce repeat failures of a duty pump while retaining a clear maintenance history.
- Assign the operational record to Manage: identify the asset, location, responsible site and work process.
- Identify how the observation arrives. A technician uses Mobile; a sensor needs an IoT data path and monitoring; a camera-based defect may use Visual Inspection.
- Choose the decision capability only when needed. Use Health for condition assessment, Predict for a suitable predictive question, Reliability Strategies for maintenance policy, or Asset Investment Planning for long-term intervention choices.
- Add contextual extensions deliberately: Spatial for geographical identity, Service Provider for customer obligations, HSE for the relevant risk process, or an industry solution for its sector-specific work.
- Mark each required connection and its owner. Confirm what is actually deployed, who can access it, and which handoffs need integration or review. Avoid assuming a product tile creates an end-to-end process.
03 · Practical example
Fictional teaching example
A fictional pumping station repeatedly loses capacity. Manage holds the pump and repair history. A technician records findings through Mobile. Operating measurements feed the monitoring path, where an alert identifies a change worth investigating. Health helps the reliability engineer compare this pump with similar assets. Predict is relevant only if a suitable model and data can answer the failure question. The engineer reviews the evidence and raises approved work in Manage. Spatial supplies location context where needed; HSE supports the applicable risk controls. If recurring repairs make replacement worth considering, Asset Investment Planning compares interventions over the chosen horizon. This is a responsibility map: the connections and approvals still need to be designed and tested.
04 · Practice and verify
Draw a component map for the pump problem. Label every arrow with what moves across it: a measurement, alert, asset identifier, work request, approved work order or completion update. For each component, write its responsibility, input, output, owner and whether it is installed, required later or unnecessary for this use case.
Expected result
You can explain where the maintenance record lives, where observations originate, who interprets them, who authorizes work and where execution feedback returns. Your map distinguishes Health from HSE, a health assessment from a prediction, a work schedule from an investment plan, and an application from its hosting platform.
Common mistakes
- Selecting every available product before defining the outcome.
- Treating an alert, prediction or health score as an automatically approved work order.
- Assuming matching asset descriptions establish identity between systems.
- Confusing deployment availability, user access and a tested business handoff.
05 · Architecture decisions
Review the architecture at its boundaries: who owns the asset identifier, how timestamps and units are normalized, which system owns financial records, and how failed handoffs are retried and reconciled. Add the required integration, security and operational support responsibilities to the map. Begin with the components needed for the first business outcome; introduce further capabilities when their inputs, owners and acceptance criteria are clear.
IBM references
- IBM — Suite applications, industry solutions, add-ons and tools
- IBM — Maximo Application Suite architecture
- IBM — Maximo Health overview
- IBM — Maximo Predict
- IBM — Maximo Mobile overview
- IBM — Reliability Strategies
- IBM — Asset Investment Planning
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