All learning series · Suite tool · Part 1
Maximo Optimizer
Understand objectives, constraints and why a solve can be infeasible.
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 Maximo Optimizer? 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 Maximo Optimizer?
Optimizer is an installation entitlement, separate from Planning and Scheduling. Have the calendar and the resource data in place, then choose the model that matches the decision you are making.
Before configuration
You need the install AppPoints, a deployed Optimizer, and a Manage site whose calendars, shifts and work the model can read. The manual Gantt does not require this product.
Before the first successful journey
Pick one model and assemble only the inputs that model reads: craft capacity and dates for maintenance scheduling, skills and availability for labor assignment, or coordinates and a map for spatial scheduling.
Before production use
Agree the objective, the capacity limits and who may publish a result onto live work. Optimizer Limited adds hard limits on VPCs, models and serial execution.
Licensing, entitlement and AppPoints
Optimizer is licensed per installation. The MAS 9.2 licensing guidance allocates 220 AppPoints for Maximo Optimizer, or 60 AppPoints for Maximo Optimizer Limited. Optimizer Limited is restricted to deployment on 2 virtual processor cores, use of a single optimizer model, and serial job execution. Those install points are reserved for the life of the environment. User access to the scheduling applications that launch a model still follows the Planning and Scheduling tier: Base, or Premium when the person also has an industry solution or add-on. Do not treat the 220 or the 60 as a per-user charge, and do not apply either figure to a schedule that never runs a model.
Keep four facts separate for Maximo Optimizer. 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
Deploy Optimizer from the suite catalog onto the Manage workspace. Confirm the optimization scenarios list a model. Long-term models run from Graphical Scheduling and Graphical Scheduling - Large Projects: resource leveling, capacity planning and maintenance scheduling optimization. Short-term models run from Graphical Assignment: labor and crew assignment, and spatial scheduling. A model that is not listed is not available to run.
Foundation configuration
Optimizer reads the same availability Planning and Scheduling uses, and then applies a model. Maintenance scheduling optimization considers resource availability, the maximum aggregated capacity of crafts, crews and tools, and aviation zones when Aviation is installed. Its default objectives are minimizing turnaround time, plan change, earliness and lateness against soft time windows, and doing high-priority work first. The work has to carry precedence, time windows and a craft or tool requirement or the model has nothing to optimize.
Labor and crew assignment uses availability and skill. The labor or crew calendar and shift still define the hours. The skill on the person has to satisfy the work. Spatial scheduling assigns by geographic location, so the work needs a location the model can read and the people need a start location. That is a different prerequisite from a manual Gantt, which does not need a map.
When work or a resource falls outside the calendar work periods, the model has no capacity in that gap. It will leave the work unassigned or move it into a window where capacity exists, depending on the time windows and the objective. Check the input calendar before you treat a sparse result as a product fault. Confirm available hours in Graphical Resource View for the same calendar and shifts the scenario uses.
Aviation zones are an extra constraint only when Aviation is installed and the work is tied to a zone. Do not add zone data for a plant shutdown that has no zones.
Product configuration
Create a scenario in the scheduling application that hosts the model. Set the objective and the constraints the model documents: respect appointments, keep the same person on a job, capacity ceilings, time windows. Run it against a copy or a scenario before anyone publishes onto the live work orders. Review the default objectives before production so a turnaround is not optimized for a goal you did not choose.
Infrastructure and integration
The Optimizer service has to be deployed and reachable from Manage. Optimizer Limited is limited to 2 VPCs and must run jobs serially, so a second job waits. Spatial scheduling needs the map provider and coordinates used by that model. No third-party solver licence is stated in the MAS 9.2 licensing guidance. Capacity of the cluster is part of the OpenShift entitlement for the suite, which is separate from the 220 or 60 install AppPoints.
Data and operational readiness
A first maintenance-scheduling run needs a handful of work orders in one site, with durations, precedence, a time window inside the calendar, and a craft that has capacity on those days. A first assignment run needs the same work plus labor or crews with skills and work periods. A first spatial run adds coordinates. History is useful for comparing a result with last week’s plan. It is not a substitute for the calendar.
Setup order for an optimization run
- 1. Install entitlement and deployment 220 AppPoints, or 60 for Optimizer Limited with its VPC, model and serial limits.
- 2. Scheduling calendar, shifts and work periods The model reads this availability. Build it as in the Planning and Scheduling course.
- 3. Choose the model and its application Long-term models in Graphical Scheduling. Assignment and spatial models in Graphical Assignment.
- 4. Model inputs Capacity and precedence, or skills, or coordinates. Only the inputs that model uses.
- 5. Scenario, then publish Compare the result in a scenario before it writes scheduled dates and assignments.
| Requirement | Why needed | Mandatory/Conditional/Optional | Where to configure or verify | Minimum working example | Verification procedure | Consequence if missing | Remediation | Source |
|---|---|---|---|---|---|---|---|---|
| Optimizer install entitlement | The model will not run without the installation. The charge is per install, not per user. | Mandatory | Suite administration → Suite → Administration → AppPoints Usage for install consumption. Suite administration → Catalog, on the Manage workspace for the deployment. Proof of entitlement for the 220 or the 60. | One Optimizer install on the production workspace. Non-production installs draw no install AppPoints when production already has the same component. | Read the install line on AppPoints Usage and match it to 220, or to 60 if the entitlement is Optimizer Limited. | Scenarios open and no optimization model runs. | Purchase and apply the install entitlement that matches full Optimizer or Optimizer Limited. Do not reuse Scheduler’s user tier as this quantity. | Licensing in Maximo Application Suite 9.2 |
| Optimizer Limited limits, when that is the entitlement | The 60-point install is usable only inside the published restrictions. | Conditional | Proof of entitlement, and the cluster size for the Optimizer workload. | A single model, jobs run one at a time, deployment within 2 VPCs. | Confirm the entitlement name is Optimizer Limited before you plan a second concurrent model. | A second model or overlapping jobs are outside that entitlement. | Move to the 220-point install, or keep to one model and serial jobs. | Licensing in Maximo Application Suite 9.2 |
| Planner access to the scheduling application that hosts the model | The person who runs the scenario still needs the Base or Premium application tier. | Mandatory | Manage → Security → Security Groups, and the user type on the suite user | The same planner as the scheduling course, with access to Graphical Scheduling or Graphical Assignment. | Sign in as that planner and open a scenario. | The install is present and the planner cannot open the application. | Grant the scheduling application at Base, or Premium if industry access is also granted. | Licensing in Maximo Application Suite 9.2 |
| Calendar, shifts and work periods covering the scenario horizon | The model treats gaps in the work periods as time with no capacity. | Mandatory | Calendars, and the calendar named on the schedule or scenario. | Calendar DAY with work periods for every day in a two-week scenario. | Compare the scenario dates with the last work period. | Work piles into the few days that have hours, or stays unassigned. | Extend work periods with Apply Shifts before you run the model. | Creating work lists in Graphical Work Week |
| Craft, crew and tool capacity the model is allowed to use | Maintenance scheduling optimization caps aggregated capacity for crafts, crews and tools. | Mandatory | Crafts, crews, tools, and the planned resources on the work. | Craft ELEC with known hours on DAY, and work that requires ELEC. | Run Graphical Resource View for the scenario calendar and read the craft hours. | The result leaves work unassigned because capacity was zero or was never entered. | Enter the craft hours, crew capacity or tool quantity the objective is allowed to consume. | Maximo Optimizer optimization models |
| Skills on labor and crews, for an assignment model | Labor and crew assignment matches work to people by availability and skill. | Conditional | Labor and crew qualifications. The skill on the work plan. | One electrician with the skill the work order requires, available on the scenario days. | Compare the work plan skill with the labor qualification record. | The model returns no assignment for that work. | Add the qualification or relax the requirement to a craft you have staffed. | Maximo Optimizer optimization models |
| Map and coordinates, for spatial scheduling only | Spatial scheduling assigns by geographic location. Other models do not need a map. | Conditional | Map provider, service address or coordinates on the work, start and end locations on labor or crews. | One site map, three work orders with coordinates, labor with a start location at the depot. | Open the spatial scenario and confirm each work order and person has a location. | The spatial model has no positions to compare. | Geocode the work and the depots, or use the labor-assignment model instead. | Maximo Optimizer optimization models |
| Aviation zones, only with Aviation installed | Maintenance scheduling can consider aviation zones. A plant shutdown without zones has no zone constraint. | Conditional | Aviation zone data on the work, and the Aviation component deployed. | Skip this row unless the work is aircraft work with zones. | Confirm Aviation is the installed industry solution before you enable zone constraints. | The model waits on zone data the site does not have. | Leave zone constraints off, or complete the Aviation readiness course first. | Maximo Optimizer optimization models |
| A scenario that is not the live schedule | Publishing writes dates and assignments onto work orders. | Mandatory | The scenario in Graphical Scheduling or Graphical Assignment. | One scenario named TRAIN-OPT over three training work orders. | Run the model, read the proposed dates, and compare them with the work orders before publish. | The first run moves live scheduled dates. | Run and review inside the scenario. Publish only after the dates match the objective you set. | Maximo Optimizer optimization models |
A. Ready to configure
- The proof of entitlement names Optimizer at 220 AppPoints or Optimizer Limited at 60, and AppPoints Usage shows that install reserved.
- Optimizer is deployed on the Manage workspace and at least one model is listed.
- The Planning and Scheduling calendar, shifts and work periods cover the horizon the model will see.
- The planner can open the scheduling application that hosts the chosen model.
- Optimizer Limited, if that is the entitlement, is the only model you intend to run, and jobs will be serial.
B. Ready for the first end-to-end journey
- The work orders have duration, precedence or a time window, and a craft or skill that exists on a resource.
- Graphical Resource View shows hours inside the scenario dates for that craft or person.
- Spatial and aviation inputs are present only when the chosen model uses them.
- The scenario runs and returns proposed dates or assignments.
- You can explain one placement from the objective and the calendar, and you have not published onto unrelated work.
C. Ready for production operation
- Objectives and capacity ceilings are agreed and written on the scenario the planners will reuse.
- Someone other than the person who ran the model compares a published result with the work orders.
- Cluster capacity for the Optimizer workload is covered by the suite’s OpenShift entitlement, separately from the install AppPoints.
- A second concurrent model is in the plan only on the 220-point install.
- Calendars and skills have an owner, because a model rerun inherits whatever those records say on the day.
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
- Maximo Optimizer optimization models — Maximo Manage continuous delivery, verified 2026-10-18
- Creating work lists in Graphical Work Week — Maximo Manage continuous delivery, verified 2026-10-18
- Creating resource lists — Maximo Manage continuous delivery, verified 2026-10-18
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
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 teaching material. Reviewed 2026-10-01.
Maximo ecosystem overview · Manage learning paths · Practice data in Workbench