Assetize

Learning Lab

Level 0 · 15 levels · Foundations · about 45 minutes

Level 0 — How this lab works, and the big picture

By the end: Explain what asset management is, what Maximo does and who uses it, how classic Maximo 7.6.1 and Maximo Application Suite relate, and where Assetize, mxH, mxR and the Data Workbench fit, using one picture for each.

The rhythm behind everything in this lab. Something breaks or falls due, a work order is raised, approved and planned, a technician does the work, parts and hours are recorded, and that history shapes the next plan. Maximo is the system that keeps this loop turning for thousands of assets at once.

A loop of six steps: an asset breaks or falls due, a work order is raised, it is approved and planned, a technician does the work, parts and hours are recorded, and the history feeds the next plan. A highlight travels round the loop.

Lesson 1

How this lab works

Welcome. This lab takes you from "what is an API?" to shipping a real Maximo change through a pipeline. There are fifteen levels in four stages. Foundations (Levels 0 to 3) covers the big picture, how software talks, Maximo for beginners and the habits of a good developer. Practitioner (4 to 8) goes inside Maximo: its data model, its REST API, its versions, and how Maximo software is built. Builder (9 to 13) covers testing, pipelines and the three Assetize products. The Final level (14) puts it all together on one upgrade story.

Every level has the same parts, in the same order. Learn the order once and you will always know where you are.

  • A hero picture at the top: the one image to remember from the level.
  • Lessons. Each one teaches one idea: what it is, why it matters, how it looks in a real team, a worked example and the common mistake.
  • Pictures inside the lessons. They start moving when you scroll to them. Press Replay to watch again. Some are clickable: try things and see what happens. If your device asks for reduced motion, they show their final state.
  • A quiz. Some questions show a picture; some ask you to pick the right picture. Pass mark: 70% (80% on the final level). Retake as often as you like; your best score is kept.
  • Picture flashcards. The picture is on the front, the term and one line on the back.
  • From Level 1, sim missions in the terminal and tasks on the Maximo SIM. Sources sit at the foot ("Where these facts come from"), and every level ends with a feedback box.

The Maximo SIM is the training Maximo. DEV is dev.assetize.com.au and UAT is uat.assetize.com.au/maximo. You log in and use the screens: Work Order Tracking, Assets, Inventory and the rest. From Level 1, a level can also include a terminal for API practice. That terminal stays in the page, on a made-up Melbourne plant: two boiler feed pumps (PUMP-101 and PUMP-102), a conveyor (CONV-301), a rooftop air-conditioning unit (HVAC-401), a standby generator (GEN-501) and a forklift (FORK-601).

No key, no data. Your first sim mission in one picture: a request walks up to Maximo without a key and bounces back with 401. In Level 1 you do this for real in the terminal.

A request walks up to a locked Maximo door. Without a key it bounces back with 401. A valid key for a user without permission gets past the door and stops at the security gate with 403. A good key with the right access gets 200 and the records.

  1. Look at the hero picture
  2. Read a lesson and replay its pictures
  3. Take the quiz
  4. Flip the flashcards
  5. Send feedback

This level, start to finish

Remember: Go slowly. One level a day is a good pace. Understanding beats speed, and the quiz will show you which pictures need a second look.

The mistake: Skip straight to the quiz and guess, then move on with a pass and no picture in your head. Do this instead: Watch each picture twice: once to see it, once to explain it in your own words. Then take the quiz. The flashcards will bring the pictures back in a week.

Your progress stays in this browser. When you are ready, the report page puts your scores, missions and feedback into one report you can send to the team. The lab is a two-way street: we test you, and you tell us where the lab is unclear, too fast or too slow. We read every word.

Lesson 2

What an asset is, and why anyone cares

An asset is a physical thing an organisation owns and must keep working. A pump in a water plant. A train carriage. A lift in a hospital. A transformer on a power line. A forklift in a warehouse. Each one is tracked one by one, with its own number, serial number, cost, location and history.

IBM's documentation puts it precisely: assets are unique instances of items. An item is a kind of thing in a catalogue, such as "electric motor, 15 kW, 4-pole". An asset is one particular motor of that kind, with serial number MTR-2018-9921, bolted onto conveyor 301. Two motors of the same item are still two different assets, because each has its own life.

WordWhat it isExample from the sim plant
ItemA kind of part in the catalogueMOTOR-15KW: electric motor 15 kW 4-pole
AssetOne physical thing, tracked one by oneCONV-301-M: the drive motor on conveyor 301
LocationA place where assets sit and work is doneCONV-LINE1: conveyor line 1
SiteA plant, depot or campus that groups locationsMELB: the Melbourne plant
Assets live in locations. A site holds a building, which holds a plant room, which holds locations. A pump asset sits in one location. Watch it move to another location: its history moves with it.

A site contains a building, which contains a plant room, which contains locations. A pump asset sits in one location, then moves to another, and its history moves with it.

Why do organisations care so much? Four reasons, and you will hear all four from customers. Money: a large organisation can spend millions a year keeping assets running, and replacing one too early or too late wastes money. Safety: a lift, a pressure vessel or a rail bogie that fails can hurt people. The law: many assets need inspections on a fixed schedule, with proof that they happened. Uptime: when a pump stops, the plant behind it may stop too.

The location and the asset are separate on purpose. The location is the place: "boiler room". The asset is the thing in it: "boiler feed pump B". When a pump is taken out for repair and a spare goes in, the location stays where it is and the assets swap. The location keeps a history of everything done at that spot. Each asset keeps its own history wherever it goes.

Assets live in locations. The same tree after the move. The pump now sits in its new location, and every work order it ever had is still on its record.

A site contains a building, which contains a plant room, which contains locations. A pump asset sits in one location, then moves to another, and its history moves with it.

The mistake: Treat "asset" and "location" as two names for the same thing, and record every job against whichever one is easier to pick. Do this instead: Ask: is the problem with the thing, or with the place? A worn seal belongs to the asset. A blocked drain in the plant room belongs to the location.

Lesson 3

The asset management cycle

Looking after assets well is called enterprise asset management, EAM for short. IBM describes Maximo's job in five words: it manages assets, schedules, resources, processes and inventories. In everyday terms, EAM software records every asset, plans the work to look after it, sends people to do the work, orders the spare parts, and keeps the history so the next plan is better than the last.

The asset management cycle. Follow the highlight round the loop. Notice that the last step, history, feeds straight back into the first: what you learn from each job changes what you plan next.

A loop of six steps: an asset breaks or falls due, a work order is raised, it is approved and planned, a technician does the work, parts and hours are recorded, and the history feeds the next plan. A highlight travels round the loop.

  1. Something breaks, or falls due. A pump leaks, or the calendar says the forklift needs its yearly check.
  2. A work order is raised. A work order is Maximo's record of one job: what, where, who, when, and with what parts.
  3. It is approved and planned. A supervisor approves it; a planner adds the steps, the trades, the parts and a date.
  4. A technician does the work, often with a phone or tablet in hand.
  5. Parts and hours are recorded. These are called actuals: the hours, materials, services and tools really used.
  6. History builds up. Engineers read it to find assets that fail too often, and change the plan.

There are two broad ways to look after an asset. You can wait until it breaks and then fix it. That is corrective maintenance. Or you can service it on a schedule before it breaks. That is preventive maintenance, PM for short. Most organisations do both: preventive work for assets that matter, run-to-failure for cheap things where a breakdown costs little.

Corrective: fix it when it breaksPreventive: service it on a schedule
  • Work starts with a failure
  • Often urgent, often at night
  • Cheap for low-value assets
  • Expensive when the asset stops a plant
  • Work starts from a plan in Maximo
  • Booked ahead, parts ready
  • Costs a little every time
  • Prevents the big, expensive failures
A PM makes work on a schedule. A preventive maintenance record with a 12-week frequency drops a new work order onto the calendar each time it falls due. The next due date moves forward after each one.

A preventive maintenance record with a frequency drops a new work order onto a calendar each time it falls due. The next due date moves forward after each one.

How big does this get? IBM's published case study for the King Abdullah Financial District in Riyadh says its Maximo manages more than 100,000 assets across 34,000 locations, with over 16,200 preventive maintenance plans. Nobody can run that from a spreadsheet. That scale is why customers buy Maximo, and why the products you will build must be careful with their data.

Remember: Every feature in Maximo, and every Assetize product, serves some step of this loop. When you meet something new, ask: which step of the cycle does this help?

The mistake: Think of Maximo as "a database of assets". Do this instead: Maximo is a system for running work. The assets are the nouns; the work orders moving round this cycle are the verbs.

Lesson 4

Maximo, then and now

Maximo began at a company called MRO Software. IBM bought MRO Software in 2006, and Maximo has been an IBM product ever since. For many years it shipped as one Java application called Maximo Asset Management. People call that "classic Maximo" or "7.6", after its last release line, 7.6.1. IBM shipped fix packs on that line (7.6.1.1, 7.6.1.2, 7.6.1.3), and you will meet customers on each of them.

Classic Maximo and MAS. Left: classic 7.6.1, one application on WebSphere servers. Right: Maximo Application Suite, a core plus applications running as containers on Red Hat OpenShift. Same Maximo work, two very different ways of running it.

On the left, Maximo 7.6.1 runs as one application on WebSphere servers. On the right, Maximo Application Suite runs in containers on Red Hat OpenShift: a core for users and licences, and applications such as Manage, Monitor, Health, Predict and Visual Inspection, each as pods.

Today IBM ships Maximo as Maximo Application Suite, MAS for short. MAS is a set of applications that run as containers on Red Hat OpenShift, a platform for running containers. A container is a small sealed package that holds one program and everything it needs. A core part of MAS looks after users, login and licences. The applications sit on top of it.

MAS applicationWhat it does, in one line
ManageThe classic Maximo work: assets, locations, work orders, PMs, inventory and purchasing
MobileRole-based apps for technicians and supervisors on iOS, Android and Windows
MonitorCollects sensor (IoT) data and shows it on dashboards against assets
HealthScores the condition of groups of assets
PredictBuilds predictive models of which assets are likely to fail
Visual InspectionTrains image models to spot defects in photos

For most of this lab, "Maximo" means Manage, the application that does the classic work. The business rules inside Manage are the same family as in 7.6.1. What changed is the platform underneath, how people log in, and how changes are installed. Level 6 goes deep on that.

The support clock. The support clock drives almost every upgrade conversation. Read the dates left to right, and find today's marker.

A timeline: 30 September 2025 end of regular support for Maximo 7.6.1.x, 1 May 2026 MAS 8.x on Extended Support only, 30 April 2027 Dual Support ends, 1 July 2027 MAS 9.0 moves to Extended Support. A marker shows today.

Why do customers move? Because IBM's support clock says so. Regular support for Maximo Asset Management 7.6.1.x ended on 30 September 2025. Customers can buy extended support, and IBM's path forward is to move to MAS and migrate to Manage. Dual Support, which lets a customer run 7.6.1 alongside a MAS licence, ends on 30 April 2027. All MAS 8.x releases moved to Extended Support only on 1 May 2026, and MAS 9.0 follows on 1 July 2027. Those dates are why so much of Assetize is about upgrades.

The mistake: Answer a question about "Maximo" without asking which one, and quote a 7.6.1 forum post to a customer on MAS 9.2. Do this instead: Ask "which version?" first, every time. A fact that is true on 7.6.1 can be false on 9.2. Assetize ties every record to the versions it covers for exactly this reason.

Remember: Remember the three names: Maximo Asset Management 7.6.1 (classic), Maximo Application Suite (the suite), Manage (the application inside it that does the classic work).

Lesson 5

Who uses Maximo

Maximo runs in organisations whose work depends on physical things that must not fail. IBM's own case studies give a feel for the range: Downer in Australia, which uses Maximo as the single source of truth for more than 1,500 train carriages; Riyadh Airports; VPI, with four power plants; the New York Power Authority; the King Abdullah Financial District. Add water utilities, mines, oil and gas, manufacturers, data centres, hospitals and universities, and you have most of the customers you will meet.

Who uses Maximo. Maximo in the middle, seven people around it. Each one does a different job in the same system, and each one sees a different slice of it.

Maximo in the middle, with seven people around it: planner, supervisor, technician with a phone, storeroom clerk, buyer, reliability engineer and administrator, each with one line on what they do.

PersonWhat they do in MaximoWhat they care about most
PlannerTurns requests into ready-to-go work orders with job plans, parts, trades and datesWork that can start on time with nothing missing
SupervisorApproves work, assigns crews, watches the backlogThe day's jobs done, safely
TechnicianDoes the work, often on Maximo Mobile; records hours, parts and the failureA clear job, the right parts, a quick way to finish it
Storeroom clerkIssues parts, receives deliveries, counts stockShelf numbers that match the system
BuyerTurns requests for parts and services into purchase orders to vendorsThe right price, delivered on time
Reliability engineerReads the history to stop the same failure coming backClean failure data and long histories
AdministratorLooks after users, security, settings, integrations and upgradesA system that stays up and changes safely
Who uses Maximo. Zoom in on the technician. IBM describes Maximo Mobile as a role-based mobile product for technicians and supervisors, with apps for work execution, inspections, inventory and service requests.

Maximo in the middle, with seven people around it: planner, supervisor, technician with a phone, storeroom clerk, buyer, reliability engineer and administrator, each with one line on what they do.

Remember: As a developer, you build for all seven. Before you change anything, ask: whose job does this touch, and how will it feel to them on a busy Monday?

The mistake: Design a screen or an API for "the user", as if there were only one. Do this instead: Name the person. A field that helps the planner may slow the technician down on a phone in the rain.

Lesson 6

Assetize in one picture

Assetize (assetize.com.au) helps the people who run, build and upgrade Maximo. At its heart is an evidence base: more than 80,000 published records about Maximo, drawn from more than 130,000 source documents. Each record states one fact, the Maximo versions it covers, and the sources behind it, with IBM documentation ranked first. Every record has its own page, at an address like assetize.com.au/record/work-order-statuses.

Assetize in one picture. Read it left to right: IBM documentation and other sources flow into the evidence base; the free tools and ASK draw on it; and three products, mxH, mxR and the Data Workbench, do real work on a customer's Maximo.

IBM documentation and other sources flow into the Assetize evidence base of source-backed records. From it come the free tools and ASK, and three products: mxH for upgrades, mxR for shipping changes and the Data Workbench for loading data, each pointing at a customer Maximo.

On top of the evidence base sit free tools that anyone can use. You will meet many of them in this lab.

ToolThe question it answers
Upgrade Desk and CompareWhat changes between my version and the one I am moving to?
Resolve a production issueWhich screens and script lines can fail this action, and what fixes each one?
Ask Maximo (ASK)A practical question, answered with the sources to check it
Change WatchWhich MAS 9.x changes matter most right now?
Relationship ExplorerHow are Maximo's objects connected, version by version?
UI Playground, Workflow Designer, Script Test HarnessWill my screen, workflow or script work before it reaches a real Maximo?
Connect your AI (MCP)Can my own AI tools answer from the same cited records?
Assetize in one picture. The evidence base lit up. Everything else in the picture reads from it, so its quality decides the quality of every answer.

IBM documentation and other sources flow into the Assetize evidence base of source-backed records. From it come the free tools and ASK, and three products: mxH for upgrades, mxR for shipping changes and the Data Workbench for loading data, each pointing at a customer Maximo.

One design rule shapes how Assetize is built, and you will follow it in your own code. AI helps at build time: it reads sources and helps shape records, and every record is checked and stored with its sources. At run time, when someone asks a question, the answer is built from stored facts and ranked records that already exist, and no AI model decides it. That way the same question gets the same answer, and every answer can be traced back to its source.

AI at build time, facts at run time. Two halves. Build time: AI helps read sources, records are checked and stored with their sources. Run time: the answer is built from typed facts and ranked records, and no AI model decides it.

At build time, AI helps read sources and shape records, and every record is checked and stored with its sources. At run time, the answer is built from typed facts and ranked records that already exist; no AI model decides it.

The mistake: Repeat a Maximo "fact" you half remember from a forum, with no version and no source. Do this instead: Find the record, check its versions, and read its sources. If IBM says it, quote IBM. That habit is what makes Assetize worth trusting.

Remember: The Assetize promise in one line: every answer can be followed back to where it came from.

Lesson 7

mxH, mxR and the Data Workbench

The free tools explain Maximo. The three products do real work on a customer's own Maximo. You will work on all three, so learn their one-line jobs now. Levels 10, 12 and 13 go deep on each.

mxH is for upgrades. Its hook: "Your Maximo upgrade is a diff. mxH runs your customisations against every release and tells you which lines of that diff are yours." IBM changes thousands of things between releases. Most of them never touch a given customer. mxH compares the customer's own export (their objects, attributes, Java, scripts and screens) with the dictionaries it ships for 7.5.0, 7.6.1.1, 9.0, 9.1 and 9.2, and grades each difference that reaches their own work.

Your upgrade is a diff. Two sets: what IBM changed, and what the customer customised. mxH lights up only the overlap, because that is where an upgrade breaks things.

Two overlapping sets: what IBM changed between the two releases, and the customer's own customisations. Only the overlap is highlighted: the changes that touch the customer's own lines.

mxR is for shipping changes. Its idea: ship Maximo changes the way Maximo ships work. Every change is a work order. mxR raises it from the Git diff, decides whether it is a hot deploy, a restart or a rebuild, deploys it to one site at a time, runs a job plan of Maximo tests, and closes it. If something fails, the work order is cancelled with a failure code and a recovery runbook. One command-line tool, one API key, and Git as the only source of truth.

An mxR work order moves site to site. An mxR change work order goes WAPPR, APPR, INPRG and COMP on DEV, then the same work order and commit move to TEST and then PROD.

An mxR change work order goes WAPPR, APPR, INPRG and COMP on DEV, then the same work order and commit move to TEST and then PROD. Failure sends it to CAN with a failure code.

The Data Workbench is for loading data. Workbench 3 says it plainly: map a spreadsheet to Maximo, check it, see exactly what will change, load it, and prove what landed. You add your Maximo (its address and an API key, which stays in the workspace's credential store), pick what to load, then check, run and reconcile. The preview lists every create, change and delete before anything is written.

A data load you can prove. A spreadsheet becomes a load you can prove, one step at a time: connect, pick, map, check, preview, load, read each row's result, reconcile.

A spreadsheet becomes a load in steps: add your Maximo, pick the object structure, map columns, run the checks and one-click fixes, preview every create, change and delete, load, read each row's result, and reconcile against Maximo.

ProductThe customer's questionWhere you learn it
mxHWhat will our upgrade break, in our own customisations?Level 12
mxRHow do we ship Maximo changes safely, one site at a time, with tests?Level 10
Data Workbench and Workbench 3How do we load this spreadsheet and prove it landed?Level 13

Remember: By the end of this lab you will be able to explain each product to a customer in two sentences, and know how to work on its code.

Check yourself: the Level 0 quiz

17 questions. Pass mark 70%.

  1. What is an asset in Maximo?
    • A file stored on a server
    • One physical thing an organisation owns and looks after, tracked one by one
    • A user account
    • A row in a spreadsheet
  2. Look at the picture. The pump has moved to a new location. Where is its repair history now? (picture: Assets live in locations)
    • Deleted when it moved
    • Left behind on the old location only
    • Still on the asset record, wherever the pump goes
    • In a separate spreadsheet
  3. What is the difference between an item and an asset?
    • There is none
    • An item is a kind of part in the catalogue; an asset is one particular physical thing of that kind
    • An asset is a kind of part; an item is one physical thing
    • Items are only used for IT equipment
  4. Look at the loop. Why does the last step feed back into the first? (picture: The asset management cycle)
    • It is a drawing mistake
    • The history of past work shapes the next plan
    • Work orders are deleted after the last step
    • Maximo restarts every night
  5. A pump is serviced every 12 weeks, whether it shows a problem or not. What kind of maintenance is that?
    • Corrective
    • Emergency
    • Preventive (PM)
    • Run to failure
  6. Which picture shows classic Maximo 7.6.1?
    • Picture A
    • Picture B
  7. Which MAS application does the classic Maximo work: assets, work orders, PMs, inventory and purchasing?
    • Monitor
    • Predict
    • Manage
    • Visual Inspection
  8. Look at the support clock. It is 1 November 2026. Which of these has already happened? (picture: The support clock)
    • Regular support for Maximo 7.6.1.x ended (30 September 2025)
    • Dual Support ended (30 April 2027)
    • MAS 9.0 moved to Extended Support (1 July 2027)
    • None of them
  9. Look at the highlighted person. What is their main job in Maximo? (picture: Who uses Maximo)
    • Approving purchase orders
    • Issuing parts, receiving deliveries and counting stock
    • Writing automation scripts
    • Scoring asset health
  10. Who usually records the hours, parts and failure on a job, often from a phone or tablet?
    • The buyer
    • The technician
    • The administrator
    • The vendor
  11. A customer says "we are on Maximo". What should you ask first?
    • Which colour theme they use
    • Which version they run
    • How many users they have
    • Whether they like it
  12. Look at the picture. Where does AI help Assetize? (picture: AI at build time, facts at run time)
    • At build time: reading sources and shaping records, which are checked and stored with their sources
    • At run time: an AI model decides each answer fresh
    • Nowhere at all
    • Only inside the sim
  13. Look at the picture: two sets, and only their overlap is lit. Which Assetize product works this way? (picture: Your upgrade is a diff)
    • mxR
    • The Data Workbench
    • mxH
    • Change Watch
  14. In this picture a change moves from site to site as a work order. Which product is it? (picture: An mxR work order moves site to site)
    • mxR
    • mxH
    • ASK
    • The UI Playground
  15. Which picture shows the step where the Data Workbench lists every create, change and delete before anything is written?
    • Picture A
    • Picture B
    • Picture C
  16. Where does an Assetize record get its authority?
    • From how many people liked it
    • From its cited sources, with IBM documentation ranked first
    • From the AI that wrote it
    • From its page title
  17. In the sim you send a bad command and get an error. What has happened to real customer data?
    • It may be damaged
    • Nothing: the sim runs in your browser on sample data
    • It was emailed to the team
    • Your account is locked

Remember it as a picture

  • Enterprise asset management (EAM): Looking after physical assets: raise work, approve and plan it, do it, record it, learn from the history. Maximo is IBM's EAM system.
  • Asset and location: An asset is the thing (boiler feed pump B). A location is the place (the boiler room). They are separate records.
  • History moves with the asset: When a pump moves, its own repair history goes with it. The location keeps the history of work done at that spot.
  • Preventive maintenance (PM): Work on a schedule, before something breaks. A PM record makes a new work order each time it falls due.
  • Classic Maximo 7.6.1: One Java application on WebSphere. Regular support ended 30 September 2025; Dual Support ends 30 April 2027.
  • Maximo Application Suite and Manage: MAS runs as containers on Red Hat OpenShift. Manage is the application inside it that does the classic Maximo work.
  • The support clock: IBM's support dates drive upgrades: 7.6.1 regular support ended 30 September 2025, MAS 8.x is Extended Support only since 1 May 2026.
  • Technician and Maximo Mobile: The technician does the work and records hours, parts and the failure, often in Maximo Mobile on a phone or tablet.
  • The people around Maximo: Planner, supervisor, technician, storeroom clerk, buyer, reliability engineer and administrator: one system, seven views.
  • Assetize: An evidence base of source-backed Maximo records, free tools and ASK on top, and three products that work on a customer's Maximo.
  • AI at build time, facts at run time: AI helps build and check records. Answers are built from stored facts and ranked records; no AI model decides them.
  • mxH: Your Maximo upgrade is a diff. mxH shows which IBM changes touch your own customisations.
  • mxR: Ship Maximo changes the way Maximo ships work: each change is a work order, deployed and tested one site at a time.
  • Data Workbench and Workbench 3: Map a spreadsheet to Maximo, check it, see exactly what will change, load it, and prove what landed.

Where these facts come from

Try it on the real tools

How did Level 0 go?

Rate the level and say what worked, what did not, what you liked and what you did not. Send it now, or with your full report.