Level 2 · 15 levels · Foundations · about 85 minutes
Level 2 — Maximo for beginners: assets, work, parts and people
By the end: Name Maximo's main records and how they connect, walk a work order through IBM's statuses and say which moves Maximo allows, explain how PMs and job plans make work, read current and available balance, follow a purchase from request to invoice, and describe a day in the life of each person who uses Maximo.
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.
Lesson 1
Organisations, sites, assets and locations
Maximo is organised in layers, and nearly every record you touch belongs to one of them. At the top is the organisation: a company or business unit that shares money settings such as currency, general ledger accounts and vendors. Inside it are sites: a plant, a depot, a hospital campus. IBM puts it simply: "The basic units of a multisite implementation are organizations and sites." Using several of each lets an enterprise share some parts of its operations and keep other parts separate.
Assets, locations, work orders, PMs and storeroom balances all belong to one site. IBM's rule for site-level records is that the identifier must be unique within the site. So PUMP-101 at the Melbourne site and PUMP-101 at a Sydney site are two different assets. That is why almost every API call about assets or work carries a siteid.
An organisation holds two sites. Work orders, assets and locations belong to one site. A user with access to only one site sees that site's records; the other site's records are greyed out.
| Layer | What it is | In the sim (sample data) |
|---|---|---|
| Organisation | Shares currency, accounts, vendors | ASTZ, Assetize Demo Organisation, currency AUD |
| Site | A plant, depot or campus | MELB, Melbourne Plant |
| Location | A place where assets work, or where stock is kept | BOILER-RM (boiler room), CENTRAL (central storeroom) |
| Asset | One physical thing, tracked one by one | PUMP-101, boiler feed pump A |
Locations come in types, and the type changes what Maximo lets you do with them. In Maximo 9.1 the LOCTYPE domain lists, among others: OPERATING (where assets do their work), STOREROOM (where stock is kept and issued from), REPAIR (workshops), HOLDING (where received items wait for inspection; IBM allows one holding location per site), SALVAGE, VENDOR, COURIER and LABOR. Operating locations are joined into systems: a hierarchy of parent and child locations, such as site, building, plant room. IBM notes that only locations whose type is based on OPERATING can be put into systems.
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.
Assets have their own hierarchy too. A conveyor (CONV-301) can be the parent of its drive motor (CONV-301-M), so a job on the motor rolls up to the conveyor. An asset has a status: NOT READY, OPERATING or DECOMMISSIONED in the sim. Some assets are rotating: serial-numbered parts, such as that motor, that travel between operating locations, repair shops and storerooms. IBM: "A rotating item that has a storeroom and balance represents the balance of a group of serialized, rotating assets."
When an asset moves, Maximo records it. IBM: moving an asset between non-storeroom locations, for example from an operating location to a repair location, "has no financial implications. However, an asset-move transaction is recorded." The asset keeps its number and its whole work history.
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.
An asset's neighbourhood: locations, systems, meters and rotating items, drawn
The mistake: When a pump is swapped out, create a brand-new asset record for the spare and retire the old one. Do this instead: Move the asset. Moving records the transaction and keeps the history. A new record starts the history at zero and hides every repeat failure.
Lesson 2
What is on a work order
A work order, WO for short, is Maximo's record of one job. It answers seven questions: what is the job, on what, how urgent, who, when, with what, and what really happened. Once you can find the answer to each question on a work order, you can read any work order in any Maximo.
The WORKORDER object drawn as a card of attributes: WONUM, DESCRIPTION, STATUS, ASSETNUM, LOCATION, SITEID, WORKTYPE. STATUS opens a list of allowed values from its domain, WOSTATUS.
| Question | Attribute | Work order 1002 in the sim |
|---|---|---|
| Which job? | WONUM, DESCRIPTION | 1002, PUMP-102 seal leak, standby pump |
| On what? | ASSETNUM, LOCATION, SITEID | PUMP-102, BOILER-RM, MELB |
| What kind of work? | WORKTYPE | CM (corrective maintenance) |
| How urgent? | WOPRIORITY | 2 |
| Where is it up to? | STATUS | APPR (approved) |
| Who? | SUPERVISOR, LEAD | AWILSON, TNGUYEN |
| When? | SCHEDSTART, SCHEDFINISH | 11 August, 8 am to 4 pm |
Work arrives from several directions. Anyone in the organisation can raise a service request (SR), such as "strange noise from conveyor line 1"; a planner turns it into a work order. PM records make work orders on a schedule (Lesson 4). Planners also create work orders directly, and a job often leaves behind follow-up work. Each organisation sets its own list of work types. Common ones are PM (preventive), CM (corrective) and EM (emergency): in the sim, work order 1001 is a PM, 1002 a CM and 1005, a generator that will not start, an EM.
A work order has two halves: the plan and the actuals. The plan is the estimate: tasks, labour hours by craft (trade), materials, services and tools. The actuals are what really happened. IBM: "As work progresses on an approved work order, you can report the actual labor hours, materials, services, and tools used." Planners compare the two to plan better. In the sim, work order 1001 was planned at 2.5 labour hours and took 1.9.
The last thing a good technician records is the failure. Maximo keeps failure codes in a hierarchy. IBM: "Typical failure codes are Problem, Cause, and Remedy." Under a failure class such as PUMPS, the problem might be LEAK, the cause a worn seal, and the remedy a replaced seal. Codes, not free text, are what let a reliability engineer count every pump leak this year in one query.
The WORKORDER object drawn as a card of attributes: WONUM, DESCRIPTION, STATUS, ASSETNUM, LOCATION, SITEID, WORKTYPE. STATUS opens a list of allowed values from its domain, WOSTATUS.
The mistake: Type everything into the description, and skip the work type, asset and failure codes because they slow you down. Do this instead: Fill in the coded fields. The description is for people; the codes are for reports, rules, integrations and every engineer who reads the history later.
Remember: In the "Read the backlog" mission below you ask the sim for the number, status and description of three work orders: the first thing a supervisor looks at every morning.
Lesson 3
A work order's life: the statuses
Every work order has a status. IBM: "The status of a work order indicates its position in the processing cycle. The status determines which actions can be performed on the work order." Status is the spine of work management. Reports, rules, integrations, mobile apps and the products you will build all read it.
| Status | IBM's meaning | Worth knowing |
|---|---|---|
| WAPPR | The work order is waiting for approval. | The default for work orders created in Work Order Tracking |
| APPR | The work order is approved and the work can begin. | |
| WSCH | The work order is waiting to be scheduled. | The default for work orders created in the Preventive Maintenance application |
| WMATL | Materials must arrive before the work can be performed. | |
| WPCOND | The work can be performed only when the condition of the plant is suitable. | For example, a plant shutdown |
| INPRG | The work is in progress. | The default for work orders created in Quick Reporting |
| COMP | The physical work is completed. | |
| CLOSE | The work order is closed. | Unused inventory reservations are removed and it becomes a history record |
| CAN | The work order is canceled. | You cannot cancel once work is in progress or actuals are reported |
| HISTEDIT | The work order was edited in history. | Only after CLOSE |
A work order status machine: WAPPR to APPR to INPRG to COMP to CLOSE, with WSCH and WMATL as side statuses and dashed arrows to CAN from WAPPR and APPR. A token moves along allowed arrows. Once the work order is in progress, an attempt to cancel it is refused and shakes red, and the allowed moves are listed: WAPPR, WMATL, COMP, CLOSE.
Which moves does Maximo allow? IBM publishes a table of the possible changes for a standard work order. Read it carefully, because it is not the strict one-way line most people imagine.
| From | IBM lists these moves |
|---|---|
| WAPPR | APPR, INPRG, WMATL, WPCOND, COMP, CLOSE, CAN |
| APPR | INPRG, WMATL, WPCOND, COMP, CLOSE, or back to WAPPR |
| WSCH, WMATL, WPCOND | Much the same as APPR: INPRG, COMP, CLOSE, the other waiting statuses, or back to WAPPR |
| INPRG | WMATL, COMP, CLOSE, or back to WAPPR |
| COMP | CLOSE only |
| CLOSE | HISTEDIT only |
| CAN | None |
Two lessons hide in that table. First, the start of a work order's life is flexible: IBM lists moves from WAPPR straight to INPRG, COMP or CLOSE. Second, the end is strict. COMP can only go to CLOSE. CLOSE is history. CAN is final. And IBM's rule on cancelling is firm: "You cannot cancel a work order if the work is already in progress or if actuals are already reported." IBM's support desk adds that a completed work order cannot be sent back to waiting on approval, and that the same rules apply to any status synonyms a customer adds.
A work order status machine: WAPPR to APPR to INPRG to COMP to CLOSE, with WSCH and WMATL as side statuses and dashed arrows to CAN from WAPPR and APPR. A token moves along allowed arrows. Once the work order is in progress, an attempt to cancel it is refused and shakes red, and the allowed moves are listed: WAPPR, WMATL, COMP, CLOSE.
A work order status machine: WAPPR to APPR to INPRG to COMP to CLOSE, with WSCH and WMATL as side statuses and dashed arrows to CAN from WAPPR and APPR. A token moves along allowed arrows. Once the work order is in progress, an attempt to cancel it is refused and shakes red, and the allowed moves are listed: WAPPR, WMATL, COMP, CLOSE.
Customers often want their own words for statuses, such as AWAITPARTS for "waiting on parts". Maximo does this with a synonym domain: the customer's word maps to one of IBM's internal values, and the business rules keep working on the internal value. That is why your code should test the internal value, not the word on the screen.
A customer value such as AWAITPARTS maps to Maximo's internal value WMATL. The screen shows the customer's word; the business rules use the internal value.
The mistake: Assume Maximo always forces a work order through approval, so your integration never checks. Do this instead: IBM's table lets a WAPPR work order move straight to INPRG, COMP or CLOSE. Customers who need approval enforced add workflow, conditions or process flow control (IBM: "process flow control can restrict which status changes are possible"). Ask what their system does, and handle refusals in your code.
Remember: The approved-work mission below filters on status="APPR". Status is the first filter of every dispatch board you will ever build.
Lesson 4
PMs and job plans: work on a schedule
A preventive maintenance record, or PM, is a plan that makes work. IBM: "Preventive maintenance (PM) records are templates for scheduled preventive maintenance work. They are used to generate preventive maintenance work orders." A PM says: for this asset or location, at this frequency, raise this work, using this job plan. IBM also lets a PM set the status its work orders start in; otherwise they start at WSCH, waiting to be scheduled.
| On a PM | What it does | PM-1001 in the sim |
|---|---|---|
| Asset or location | What the work is for | PUMP-101 in BOILER-RM |
| Frequency and units | How often: days, weeks, months or years | 3 MONTHS |
| Job plan | The steps, labour and parts copied onto each work order | JP-PUMP-3M |
| Work type | The type set on each generated work order | PM |
| Next due date | When the next work order falls due | 1 October 2026 |
| Status | ACTIVE, DRAFT or INACTIVE | ACTIVE |
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.
Most PMs are time-based. IBM: "For time-based PM records, the generation criteria is based on elapsed time since the target start date or completion date of previous work." A check box decides which: leave it clear and the schedule is fixed to the calendar; tick "Use Last Work Order's Start Date to Calculate Next Due Date" and the schedule floats with when the work really started. Other PMs are meter-based, such as every 500 running hours of a generator, and some combine both.
Three more settings decide when work actually appears. Lead time: IBM says it is "an amount of time that you specify on a preventive maintenance (PM) record so that work orders are generated in advance of their next due dates", so parts and people can be ready. Status: PM statuses "determine whether work orders can be generated", and the PMSTATUS domain holds ACTIVE, DRAFT and INACTIVE; an ACTIVE PM is the one that makes work. And the generator: a planner can press Generate Work Orders, and the PMWoGenCronTask cron task runs on a schedule and, in IBM's words, "generates scheduled work orders for planned maintenance".
- PM falls due (date or meter)
- Lead time reached
- PMWoGenCronTask runs
- Work order created (WSCH by default, or the status the PM sets)
- Job plan copied on
- Next due date moves forward
How a PM turns into a work order
A job plan is the recipe. IBM: "Job plans are detailed descriptions of work tasks (operations), labor, materials, and tools for a type of work." You can use a job plan "as a template for a work plan on a work order for repetitive maintenance work." In the sim, JP-PUMP-3M is "Pump quarterly inspection and lubrication", 2.5 hours. A typical plan like it reads: 10, isolate and lock out the pump; 20, inspect seals and coupling; 30, lubricate bearings; 40, test run and return to service. Change the job plan, and every future work order it stamps out changes with it.
A job plan template with tasks, labour and materials is applied to a new work order, and the tasks, labour and materials copy onto it.
How a PM turns into a work order, drawn
The mistake: Add the same tasks and parts by hand to every generated work order because the job plan is "a bit out of date". Do this instead: Fix the job plan once. Every future work order gets the change, and the history shows when the method changed.
Remember: The "Find the planned maintenance" mission below lists the ACTIVE PMs and the asset each one looks after. Notice which PM is missing.
Lesson 5
Items, storerooms and balances
Spare parts live in three kinds of record, and beginners mix them up all the time. The item is the catalogue entry: a kind of part, such as BEARING-6205, "deep groove ball bearing". The storeroom is a location of type STOREROOM; IBM: storeroom locations are "the places inventory items are stored in and issued from." The inventory record joins them: one item in one storeroom, with its bin, its balances, its costs and its reorder settings.
| Record | What it is | In the sim (sample data) |
|---|---|---|
| Item | A kind of part in the catalogue | BEARING-6205, deep groove ball bearing 6205-2RS |
| Storeroom | A location where stock is kept and issued from | CENTRAL, the central storeroom |
| Inventory | That item in that storeroom, with balances | BEARING-6205 in CENTRAL, bin A-01-03 |
Two numbers matter more than any others. The current balance is how many are physically on the shelf. The available balance is how many you can actually promise to a new job. IBM's support note on the reorder calculation gives the rule: Available Balance = Current Balance − Reserved Quantity − Expired Quantity. In the sim, BEARING-6205 has a current balance of 14 and an available balance of 12: two bearings are already held for other work.
A storeroom shelf with items. Some are tagged as reserved for other work orders. Current balance counts every item on the shelf; available balance counts only the untagged ones.
Reservations are how planned work claims stock. When a work order that plans materials from a storeroom is approved, Maximo reserves them. IBM separates two kinds: a hard reservation holds the stock, and "Soft reservations do not affect available balances." Maximo decides which kind from the date: "Automatic reservations are specified as hard or soft based on the required date."
- Issue: parts leave the storeroom for a work order, an asset or an account. IBM: you can issue rotating and non-rotating items, from different storerooms, and return them.
- Transfer: parts move from one storeroom to another.
- Receipt: parts arrive from a vendor and the balance goes up (Lesson 6).
- Count: someone counts the shelf and corrects the balance to match.
When stock runs low, Maximo can order more. Each inventory record has a reorder point. IBM's support note gives the starting formula: Order Quantity = (ROP + 1) − Quantity on Order − Available Balance, where ROP is the reorder point. In the sim, the HEPA filters for the rooftop unit have a reorder point of 4, nothing on order and 3 available, so the formula asks for (4 + 1) − 0 − 3 = 2. The reorder process can raise a purchase requisition or purchase order for you, which is where Purchasing takes over.
Where a part goes: received, stored, reserved, issued and replenished, drawn
| Current balance | Available balance |
|---|---|
|
|
The mistake: Use current balance to decide whether a job can start. Do this instead: Use available balance. The difference is parts already promised to other work.
Lesson 6
Purchasing: from request to shelf to invoice
When a part or a service is not in stock, someone has to buy it. IBM sums up the process in one sentence: "The steps in the purchasing process include creating purchase requisitions, creating purchase orders, receiving services and items, and recording vendor invoices." Four documents, four steps, and usually four different people.
A purchase requisition becomes a purchase order to a vendor, the goods are received into the storeroom, the invoice is matched and the stock balance goes up.
| Document | Who | What it says | Example |
|---|---|---|---|
| Purchase requisition (PR) | A planner, a storeroom, or the reorder process | "We need this." Internal: transfer from another company storeroom. External: buy from a vendor (IBM). | Two HEPA filters for the rooftop unit |
| Purchase order (PO) | The buyer | A commitment to one vendor, at a price, by a date | PO3001 to BEARCO: bearings and belts, AUD 486.60 |
| Receipt | The storeroom or receiving clerk | What actually arrived, recorded in the Receiving application | 12 bearings received into CENTRAL |
| Invoice | Accounts payable | What the vendor wants paid, matched against the PO and the receipts (IBM) | BEARCO's invoice for PO3001 |
Like work orders, requisitions and purchase orders start waiting for approval (WAPPR) and must be approved (APPR) before they move on. Approval rules are often set up as workflow; IBM notes that requisitions and purchase orders generated by the inventory reorder process can be routed into a workflow process too. In the sim, PO3001 is approved and PO3002, the HEPA filters, still waits.
A purchase requisition becomes a purchase order to a vendor, the goods are received into the storeroom, the invoice is matched and the stock balance goes up.
Receiving is where purchasing meets the storeroom. Some items must be inspected before anyone may use them. IBM: items that need inspection, serialisation or both "go into a holding location before they can be transferred to the appropriate storeroom", and each site can have only one holding location. Services are received too: a contractor's hours are confirmed before they are paid.
A purchase requisition becomes a purchase order to a vendor, the goods are received into the storeroom, the invoice is matched and the stock balance goes up.
The invoice closes the loop. IBM: you "match invoice details against purchase orders and receipts." Finance people call this a three-way match: the PO says what was agreed, the receipt says what arrived, the invoice says what the vendor wants paid. When all three agree, the invoice is approved for payment.
From "we need this" to "it is paid for", drawn
- PR: we need it
- PO: we committed
- Receipt: it arrived
- Invoice: matched and paid
The four purchasing documents
The mistake: Pay an invoice because the amount looks right, without checking anything arrived. Do this instead: Match it: PO, receipt and invoice must agree. A receipt is the proof that the organisation got what it is paying for.
Lesson 7
The people who use Maximo, and their day
Maximo is used by people with very different jobs, and each sees it differently. In MAS, IBM provides Work Centers, which it describes as "role-based user interfaces where users can access and complete daily tasks". Classic screens open on a Start Center, a home page of lists and key numbers chosen for a group of users. Technicians and supervisors in the field use Maximo Mobile, which IBM describes as "a role-based mobile solution" with apps for work execution, inspections, inventory and service requests, on iOS, Android and Windows.
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.
| Time | Who | What they do in Maximo (sample day at the sim plant) |
|---|---|---|
| Overnight | Maximo itself | PMWoGenCronTask raises work order 1004, HVAC-401 filter change, from PM-1002 |
| 7:00 | Amara, supervisor | Reviews the backlog, approves 1004, checks what is waiting on material |
| 7:30 | Chidi, planner | Builds next week's work: job plans, crafts, parts and dates on each work order |
| 8:00 | Thanh, fitter | Opens work order 1002 on his phone, starts work, later records hours, parts and the failure |
| 9:30 | Storeroom clerk | Issues seals against 1002 and receives the BEARCO delivery against PO3001 |
| 11:00 | Buyer | Turns the HEPA filter requisition into a purchase order and chases a late delivery |
| 14:00 | Reliability engineer | Counts this year's pump failures by problem and cause code |
| 16:00 | Administrator | Creates an API key for a new integration user, and checks last night's cron tasks ran |
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.
Every one of these people relies on the same records being right. The supervisor's backlog depends on statuses. The planner depends on job plans and available balances. The technician depends on the right asset and a clear task list. The buyer depends on requisitions that say exactly what is needed. The engineer depends on failure codes. The administrator depends on all of it changing safely.
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.
- For the technician: fewer taps, clear tasks, works on a phone in poor light.
- For the planner and supervisor: lists that load fast and filter on status.
- For the storeroom and buyer: balances and documents that match the real world.
- For the engineer: coded data, never free text only.
- For the administrator: changes that can be tested, shipped and rolled back. That is what mxR is for.
The mistake: Build for "the user" and test with an administrator account that can do everything. Do this instead: Name the person the change is for, and test it as that person: their permissions, their device, their busy morning.
Remember: When you read a requirement, ask three questions: whose job does it help, whose job does it touch, and how will each of them know it worked?
Level 2 missions in the Maximo sim
- Read the backlog. Get three work orders, with only their number, status and description.
- Only the approved work. Filter the work orders so only the APPR (approved) ones come back.
- Find the planned maintenance. List the ACTIVE preventive maintenance (PM) records and the asset each one looks after.
Real practice on the Maximo SIM
Tasks you do by hand on the training Maximo, with the evidence your trainer checks.
- Log in and read the work backlog (DEV). Every Maximo day starts on the list of work. Learn to find it on the screens before you ever query it in code.
- Find an operating asset and where it lives (DEV). Assets and locations are separate records. Seeing them side by side on the screen makes the difference stick.
- Raise a corrective work order and approve it (DEV). This is the most common thing anyone does in Maximo. Do it once by hand and the API version later will make sense.
- Read a storeroom balance (DEV). Planners check stock before they promise a job. Current balance and available balance are not the same number.
Check yourself: the Level 2 quiz
18 questions. Pass mark 70%.
- What is the difference between an asset and a location?
- There is none
- An asset is a tracked physical thing; a location is a place where assets sit or stock is kept
- A location is a kind of asset
- Assets are only for IT equipment
- PUMP-102 has moved to the workshop. Which record keeps the pump's own repair history? (picture: Assets live in locations)
- The old location
- The new location
- The asset itself
- Nobody: it starts again
- Look at the picture. This user has access to site A only. What do they see of site B's work orders? (picture: Organisations and sites)
- Everything
- Nothing: site B's records are out of reach for them
- Only the descriptions
- Only closed work orders
- A planner creates a new work order in Work Order Tracking. Which status does it start in?
- APPR
- INPRG
- WAPPR
- CLOSE
- Which status do work orders created in the Preventive Maintenance application start in by default?
- WSCH, waiting to be scheduled
- COMP
- CAN
- HISTEDIT
- Look at the picture. The work order is COMP and someone tries to move it back to INPRG. Will Maximo allow it? (picture: The work order lifecycle)
- Yes, any move is allowed
- No: from COMP the only move is CLOSE
- Only on Fridays
- Only through the database
- Work has started on this job. The supervisor tries to cancel it. What happens? (picture: The work order lifecycle)
- It is cancelled
- It is refused: you cannot cancel once work is in progress or actuals are reported
- It goes back to WAPPR
- It is closed instead
- What happens when a work order is closed?
- Nothing changes
- Unused inventory reservations are removed and it becomes a history record
- It is deleted
- It goes back to the planner
- Your integration assumes every work order passes through APPR before INPRG. Is that safe?
- Yes, Maximo always forces it
- No: IBM's table lets WAPPR move straight to INPRG, COMP or CLOSE unless the customer adds rules
- Yes, but only on MAS
- No, because APPR does not exist
- This PM has a 4-week frequency on a fixed schedule. The last work order was due on 2 March. When is the next one due? (picture: A PM makes work on a schedule)
- 30 March
- 2 April
- Every day from now on
- Whenever someone remembers
- Which PM status makes new work orders?
- DRAFT
- INACTIVE
- ACTIVE
- CLOSE
- What runs on a schedule to generate preventive maintenance work orders?
- The Receiving application
- The PMWoGenCronTask cron task
- A purchase order
- The Start Center
- Look at the picture. What is being copied onto the new work order? (picture: A job plan stamps out the work)
- The asset's purchase price
- Tasks, labour and materials from a job plan template
- A purchase order
- Another work order's actuals
- The shelf holds 20 of a part. Five are held by hard reservations for other jobs and none have expired. What is the available balance? (picture: Current balance and available balance)
- 20
- 25
- 15
- 5
- What does a soft reservation do to the available balance?
- Lowers it
- Raises it
- Nothing: IBM says soft reservations do not affect available balances
- Sets it to zero
- The goods have arrived at the storeroom. Which purchasing step is lit, and what does it change? (picture: From request to shelf)
- The requisition: it asks for approval
- The receipt: it records what arrived and the storeroom balance goes up
- The invoice: it pays the vendor
- The PO: it commits money
- In what order do the purchasing documents usually come?
- Invoice, PO, PR, receipt
- PR, PO, receipt, invoice
- PO, PR, invoice, receipt
- Receipt, invoice, PR, PO
- The highlighted person turns requests into ready-to-go work with job plans, parts, trades and dates. Who is it? (picture: Who uses Maximo)
- The buyer
- The planner
- The administrator
- The storeroom clerk
Remember it as a picture
- Organisation and site: An organisation shares money settings and vendors; sites are plants or depots. Assets, locations and work orders belong to one site.
- Location: A place: where assets work (OPERATING), where stock is kept (STOREROOM), workshops (REPAIR) and more.
- Moving an asset: Moving records an asset-move transaction. The asset keeps its number and its whole history.
- Work order: Maximo's record of one job: what, on what, how urgent, who, when, with what, and what really happened.
- WAPPR: Waiting for approval. The default status for work orders created in Work Order Tracking.
- No cancelling once work starts: IBM: you cannot cancel a work order once work is in progress or actuals are reported.
- COMP to CLOSE: From COMP the only move is CLOSE. A closed work order is a history record.
- Synonym status: A customer's own status word maps to IBM's internal value. The rules work on the internal value.
- PM: A template for scheduled work. An ACTIVE PM raises a work order each time it falls due.
- Job plan: The recipe: tasks, labour, materials and tools for a kind of job, copied onto each work order.
- Current and available balance: Current: everything on the shelf. Available: current minus reserved minus expired.
- Purchase requisition (PR): "We need this." Internal: transfer from another storeroom. External: buy from a vendor.
- Purchase order (PO): A commitment to one vendor, at a price, by a date. It waits for approval before it goes out.
- Invoice matching: The invoice is matched against the purchase order and the receipts before it is approved for payment.
Where these facts come from
- IBM Knowledge Center: Work order statuses (meanings, defaults and allowed changes)
- IBM Support: From the Maximo Support Desk, allowable status changes for work orders
- IBM Docs: Preventive maintenance overview
- IBM Docs: Job plans overview
- IBM Docs: Material reservations (hard and soft)
- IBM Support: Maximo reorder calculation (available balance, order quantity)
- IBM Docs: Purchasing process
- Assetize record: Work order statuses
Try it on the real tools
How did Level 2 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.