Assetize

All learning series · Suite application · Part 1

Maximo Monitor

Turn measured operating conditions into an actionable monitoring view.

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 Monitor? 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 Monitor?

Monitor watches measurements that arrive with a device identity, a time and a unit. The 9.2 guidance prices it at the Limited tier.

Before configuration

Monitor is deployed, the user is on a tier that includes it, and you have one device or simulator and one asset to attach it to.

Before the first successful journey

A short series of timestamped values, in one unit, mapped to one asset.

Before production use

The device identity, the unit and the alert threshold have an owner. A flat line can be a dead feed or a healthy asset. You need the timestamps to tell them apart.

Licensing, entitlement and AppPoints

The MAS 9.2 licensing guidance prices Maximo Monitor at the Limited tier for authorized and concurrent users. The application table includes Monitor at Limited, Base and Premium, because the higher tiers include Limited. There is no Monitor install quantity on the install table. A device, a gateway or a historian vendor is licensed by that vendor. IoT connectivity, when it is the path into Monitor, is covered in the IoT course and is not a second copy of this tier.

Keep four facts separate for Maximo Monitor. 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 Monitor is deployed and a device or entity can be registered. Installed means the application opens. Configured means one entity is mapped to one asset and one measurement. Usable means a new value appears on that asset’s timeline.

Foundation configuration

You need the Manage asset and site, the unit of the measurement, and the clock. People who respond to an alert need a work process in Manage if the alert becomes work. That work order is a later step. The first proof is the value on the timeline.

Product configuration

Register the entity, map it to the asset, and set one threshold. Grant operators Monitor and keep device administration separate. Review a default threshold before it pages anyone.

Infrastructure and integration

The device or simulator needs a route to the ingestion endpoint, with the authentication that endpoint expects. DNS, TLS and the broker or gateway are part of that path. Capacity is the rate your deployment is sized for. State the figure from your sizing, not a generic rate.

Data and operational readiness

The first journey needs a handful of points with timestamps and a unit, on one asset. One point outside the threshold should raise the alert you configured. A missing asset mapping is configuration. A silent feed is the path or the device. A value in the wrong unit is data.

Setup order for a monitored asset

  1. 1. Limited, Base or Premium user Monitor is included from Limited upward. No install line.
  2. 2. Monitor deployed Its own application.
  3. 3. Asset, entity, unit The mapping.
  4. 4. A short series and one threshold The value appears, and one alert fires.
Readiness for Maximo Monitor
RequirementWhy neededMandatory/Conditional/OptionalWhere to configure or verifyMinimum working exampleVerification procedureConsequence if missingRemediationSource
A user tier that includes MonitorThe guidance prices Monitor at Limited. Base and Premium include that access.MandatorySuite administration → Suite → Administration → AppPoints Usage. Manage → Security → Security Groups, and the suite user type.An operator on Limited.Grant Monitor and read the tier.The operator is given Predict or Health in the same group and moves to a higher tier by accident.Keep this group to Monitor until you intend the higher product.Licensing in Maximo Application Suite 9.2
Monitor deployedIt is a suite application with its own version.MandatorySuite administration → CatalogMonitor opens and can register an entity.Record the version.Only Manage is deployed.Deploy Monitor before you send data.Modules and applications in Maximo Application Suite 9.2
An asset and a device identityThe measurement has to land on one asset.MandatoryMonitor entity mapping and the Manage asset.Entity PUMP-1-VIB mapped to asset PUMP-1.The entity page names the asset.Values arrive under an unbound device.Create the mapping before the feed.Modules and applications in Maximo Application Suite 9.2
Timestamps and a unitA number without a time or a unit cannot be trended.MandatoryThe ingestion payload and the metric definition.Temperature in °C, one timestamp per minute, for a short run.Read three points back with time and unit.The chart has values and no axis you trust.Send time and unit with the value.Modules and applications in Maximo Application Suite 9.2
One thresholdThe alert is the action. The chart is the evidence.MandatoryThe alert rule on that metric.Alert above a limit you choose for the training series.Cross the limit once and see the alert. Stay under it and see no alert.Every point alerts, or no point can alert.Set the limit against the series you sent.Modules and applications in Maximo Application Suite 9.2
A route from the device to ingestionThe laptop is not the device network.MandatoryDNS, TLS and the credential the endpoint requires.The simulator uses the workspace endpoint and its own credential.Send one point from that network and see it on the asset.A local test works and the plant network never arrives.Open the path the device will use.Modules and applications in Maximo Application Suite 9.2

A. Ready to configure

  • The user tier includes Monitor and the dashboard agrees.
  • Monitor is deployed.
  • The asset and the unit are chosen.
  • You have a device or a simulator and a credential.

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

  • The entity is mapped to the asset.
  • A short series appears with timestamps and the unit.
  • One value crosses the threshold and one alert is raised.
  • Values under the threshold do not alert.

C. Ready for production operation

  • Device identities, units and thresholds have an owner.
  • The vendor licence for the gateway or historian is in place.
  • Alert-to-work, if you use it, is a Manage work process with its own group.
  • A silent asset is checked as feed, mapping, then equipment.

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.

  • Monitor available with a test data source.
  • A synthetic sensor feed and a documented mapping from device/entity identity to a training asset.

IBM sources + Assetize exercise

01 · Basics — Understand the building blocks

Monitor organizes operational measurements so teams can examine asset behavior. Its APIs expose raw and aggregated metric data by entity type.

A measurement needs identity, timestamp, units and context. A dashboard showing a number is only useful when the number refers to the intended equipment and time period.

Topics in this series

  • Entities and measurements
  • Data ingestion and units
  • Calculations and dashboards
  • Alerts and operational context
  • Maintenance handoff and replay

02 · Configuration — Work through the setup

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

  1. Define one pump entity and the meanings of temperature, vibration and operating state in your training data.
  2. Use the installed Monitor data-ingestion procedure to supply a small timestamped sample.
  3. Inspect the entity's raw measurements and compare them with the input file.
  4. Configure a view or calculation for an agreed time window; distinguish individual readings from aggregate values.
  5. Apply a documented alert function available in your build and test normal, sustained-high and missing-data samples separately.

03 · Practical example

Fictional teaching example

A pump is warm during startup. In the practice design, the operator investigates only if a high-temperature condition persists while the pump is running. The threshold and duration are teaching assumptions, not equipment limits.

04 · Practice and verify

Create ten normal readings, ten persistent high readings and a deliberate time gap. Record which observations reach the dashboard and alert process.

Expected result

Identity, units and times match the input. Persistent high data is distinguishable from a gap and from a transient startup event.

Common mistakes

  • Sending every raw reading directly into a new work order.
  • Interpreting absence of telemetry as healthy operation.

05 · Advanced concepts

Design deduplication, alert ownership and a deliberate handoff to maintenance. Test stale data, replayed readings and a restored connection before scaling the feed.

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