All learning series · Suite tool · Part 1
IoT connectivity
Establish a trustworthy device-to-asset data path before analytics.
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 IoT connectivity? 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 IoT connectivity?
IoT connectivity gives a device a name, a credential and a path into the suite. The 9.2 licensing guidance does not publish a separate IoT install quantity. The application that consumes the data, often Monitor, carries the user tier.
Before configuration
Know which application will consume the messages, and have a device identity that is not a person’s password.
Before the first successful journey
One device, one topic or queue, and one message with an identity, a time, a unit and a value.
Before production use
Credentials rotate, and someone owns the broker. A message that reaches the broker and never reaches Monitor is a mapping problem, not a device failure.
Licensing, entitlement and AppPoints
The MAS 9.2 licensing guidance does not list a separate IoT install AppPoint quantity. Do not invent one, and do not copy Monitor’s user tier onto the broker as if it were an install. The people who use the consuming application take that application’s tier. Monitor is Limited. A third-party broker, SIM or device-management subscription is licensed by its provider. Device credentials are not Maximo user entitlements.
Keep four facts separate for IoT connectivity. 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 IoT service or broker your suite uses is deployed, and confirm the consuming application is the one you entitled. Installed means the endpoint accepts a connection. Configured means the device is registered and mapped. Usable means the consumer shows the value.
Foundation configuration
The Manage asset is the thing the device measures. The device identity is a separate key. Units and time zones are agreed before the first message. People and work orders come later, when a message becomes work.
Product configuration
Register the device, issue its credential, and set the mapping to the asset and the metric. Restrict who can register devices. Review a default that accepts any payload before you open the endpoint to a plant network.
Infrastructure and integration
The device network needs DNS, TLS and a path to the broker, plus any proxy the plant uses. Ports and certificates are part of that path. Capacity is the connection and message rate your platform was sized for.
Data and operational readiness
The first journey is one valid message and one rejected message: the rejected one has a bad credential or a missing unit. The valid message appears in the consumer. Arrival at the broker is not arrival in Monitor. Check the mapping between those two.
Setup order for a device
- 1. Consuming application and its tier No separate IoT install quantity in the 9.2 guidance.
- 2. Broker or IoT service deployed The endpoint the device will call.
- 3. Device identity and credential Not a person’s password.
- 4. One message in the consumer Identity, time, unit and value.
| Requirement | Why needed | Mandatory/Conditional/Optional | Where to configure or verify | Minimum working example | Verification procedure | Consequence if missing | Remediation | Source |
|---|---|---|---|---|---|---|---|---|
| The consumer’s user tier, and no invented IoT install quantity | The guidance publishes no IoT install line. Users belong to the application that shows the data. | Mandatory | Suite administration → Suite → Administration → AppPoints Usage. The 9.2 install table. | Monitor users at Limited, if Monitor is the consumer, and no IoT install charge added by assumption. | Read the install table and the consumer’s user line. | An install quantity from another product is entered for IoT. | Remove it. License the consumer and any third-party broker. | Licensing in Maximo Application Suite 9.2 |
| The IoT endpoint deployed | The device needs a place to connect. | Mandatory | Suite administration → Catalog or the broker administration for your suite. | The endpoint accepts a connection with the device credential. | Connect once and record the version or service name. | Devices are configured against a URL that is not deployed. | Deploy the service before you issue credentials. | Modules and applications in Maximo Application Suite 9.2 |
| A device identity and a credential | The device is not a Maximo user. | Mandatory | Device registration. | Device PUMP-1-EDGE with its own credential. | Connect with that credential and fail with a wrong one. | A shared password is copied onto the device. | Issue a device credential and store it for that device only. | Modules and applications in Maximo Application Suite 9.2 |
| A payload contract | Identity, time, unit and value are the minimum. | Mandatory | The message definition. | One JSON or the format your service documents, with those four fields. | Send one message and read the four fields back in the consumer. | A number arrives with no unit or no time. | Reject or fix the payload before you trend it. | Modules and applications in Maximo Application Suite 9.2 |
| A mapping to an asset | The consumer has to know which asset the device is. | Mandatory | The mapping in the IoT service or in Monitor. | PUMP-1-EDGE mapped to asset PUMP-1. | The consumer shows the value on PUMP-1. | The broker has the message and the asset timeline does not. | Fix the mapping. The device is already fine. | Modules and applications in Maximo Application Suite 9.2 |
| A network path from the device | Registration on a laptop is not the plant path. | Mandatory | DNS, TLS, proxy and firewall from the device network. | The device network opens the broker port and trusts the certificate. | Send the message from that network. | The message works on the office LAN only. | Open the plant path. | Modules and applications in Maximo Application Suite 9.2 |
A. Ready to configure
- You have confirmed there is no IoT install line to buy, and the consumer’s tier is covered.
- The endpoint is deployed.
- A device name and a unit are chosen.
- The asset exists.
B. Ready for the first end-to-end journey
- The device connects with its credential.
- One valid message appears on the asset in the consumer.
- A bad credential is refused.
- A message that reaches the broker and not the asset is fixed as a mapping.
C. Ready for production operation
- Device credentials have an owner and a rotation.
- The broker’s capacity is the sized rate, with an owner.
- Third-party connectivity licences are in place.
- Support can tell a dead device from a mapping error and from a down broker.
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.
- The IoT capability and supported connection method for the selected suite build.
- A test device or simulator, nonproduction credentials and a training asset mapping.
IBM sources + Assetize exercise
01 · Basics — Understand the building blocks
The MAS catalogue includes an IoT tool. Treat connectivity and device identity as a separate layer from asset analytics and maintenance transactions.
A device identifier describes the source. An asset identifier describes the maintained equipment. Their relationship can change when a sensor is replaced.
Topics in this series
- Devices and assets
- Message contracts
- Connectivity
- Replay and quality
- Monitoring integration
02 · Configuration — Work through the setup
Use a training environment and match the actions to the IBM guide for your installed build.
- Write a measurement contract: device ID, event time, units, quality and asset mapping.
- Register/configure the simulator using the supported procedure for the deployed IoT service.
- Send a small sample and compare received identity, timestamps and values.
- Disconnect, buffer a few observations and reconnect using the client's documented behavior.
- Inspect duplicate and out-of-order handling before forwarding the data to Monitor or another consumer.
03 · Practical example
Fictional teaching example
A replacement temperature sensor has a new device ID but measures the same pump. The exercise preserves the pump's history while showing when the source device changed.
04 · Practice and verify
Prepare a 20-event sample including a duplicate, late event and changed device mapping. Trace what each consumer receives.
Expected result
The asset mapping is explicit, replay behavior is recorded and units remain consistent across the connection.
Common mistakes
- Using a sensor serial number as the permanent asset identity.
- Assuming that receipt guarantees timely processing.
05 · Advanced concepts
Plan credential rotation, device replacement, quality flags and retention. Document the boundary between the IoT service and monitoring calculations.
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