All learning series · Suite tool · Part 1
Maximo Optimizer
Understand objectives, constraints and why a solve can be infeasible.
Before you start
MAS learning path. Match the component documentation to your installed release and maintenance build before configuring it.
- Optimizer deployed and access to a supported example model.
- A small training dataset and the appropriate entitlement for the selected model and job flow.
IBM sources + Assetize exercise · Not lab-verified
01 · Basics — Understand the building blocks
Optimizer runs optimization models and manages related jobs. IBM describes its framework for optimization data/application management and its embedded CPLEX solver.
An objective expresses what to improve. A hard constraint expresses what must hold. A completed job does not automatically mean the proposed plan meets the business expectation.
Topics in this series
- Models and jobs
- Objectives and constraints
- Input quality
- Feasible and infeasible cases
- Scenario comparison
02 · Configuration — Work through the setup
Use a training environment and match the actions to the IBM guide for your installed build.
- Select a documented model available in your environment and record its expected inputs.
- Define the business objective, such as minimizing late work, separately from hard constraints.
- Prepare a small feasible dataset with known labor availability and task durations.
- Submit a training job through the supported model workflow. Inspect status, result and constraint satisfaction.
- Remove required resource availability and run a second case. Explain any infeasible result instead of weakening constraints silently.
03 · Practical example
Fictional teaching example
Two four-hour tasks can fit one qualified technician's eight-hour day only if travel, breaks, availability and precedence also permit it. The example deliberately adds a qualification mismatch to explain why hours alone are insufficient.
04 · Practice and verify
Run or manually work through a feasible and infeasible case. Record the inputs, job identifier, status and violated or limiting constraints.
Expected result
The proposed solution respects every declared hard constraint. The impossible case is identified and has a clear business explanation.
Common mistakes
- Equating job completion with a usable schedule.
- Changing constraints until the solver returns a result without documenting the compromise.
05 · Advanced concepts
Compare objectives, runtime limits and sensitivity to changed availability. Keep model version and input snapshot with every accepted result.
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