Assetize

All learning series · Manage add-on · Part 1

Maximo IT

Connect a reported service issue to the affected service, asset and resolution.

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

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.

  1. Define a training service and identify its dependent equipment or configuration items.
  2. Log an incident with symptoms, impact and the correct requester.
  3. Apply the configured classification, ownership and priority rules.
  4. Record investigation and restoration evidence; link a problem or change when the training process requires it.
  5. 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 guidance, not claims of executed lab procedures. Reviewed 2026-10-01.

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