Assetize

All learning series · Suite tool · Part 1

IoT connectivity

Establish a trustworthy device-to-asset data path before analytics.

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 · Not lab-verified

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.

  1. Write a measurement contract: device ID, event time, units, quality and asset mapping.
  2. Register/configure the simulator using the supported procedure for the deployed IoT service.
  3. Send a small sample and compare received identity, timestamps and values.
  4. Disconnect, buffer a few observations and reconnect using the client's documented behavior.
  5. 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 guidance, not claims of executed lab procedures. Reviewed 2026-10-01.

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