Practitioner-written articles covering IBM Maximo KPIs, implementation patterns, and troubleshooting. Built from real projects, not theory.
The orientation guide nobody gives you on day one. What Maximo actually is, the terminology that trips everyone up, where to start based on your role, and the community resources worth your time.
Read article →Two clocks are running on 7.6.1.x, a support clock and a licensing clock, and the licensing one has a hard April 2027 close. Why the deadline is real now, and why in MAS your security model is your AppPoint bill. Includes the live MAS migration timeline.
Read article →Porting a decade of accumulated access into MAS meters the waste as a recurring AppPoint bill. The two-phase rebuild: inventory effective access per user, then design a small set of roles on least access, with segregation of duties checked across the combinations people actually hold.
Read article →Size from what each role actually does, not headcount. Assign the lowest tier that covers the apps, move pure requesters to zero-cost Self-Service, model concurrency on real peak, and tighten the access padding the bill. A number you can defend line by line.
Read article →Mobile is not a license tier and not a discount. A mobile user consumes at their Manage tier, set by what the role does, not the device. Split the population and size the work.
Read article →Concurrent is not a discount, it is a bet on peak usage. A Concurrent seat costs more, so it only wins when peak logins stay well below headcount. Three shifts is break-even, not savings.
Read article →Tightening access frees AppPoints, but banking the saving is usually the least valuable move. The freed headroom is a paid-for capability budget you can reinvest before renewal.
Read article →A high quote is usually a faithful price of what you handed over. Arguing it wins a one-time discount; fixing the model wins a reduction that repeats every year. Rebuild, then re-quote.
Read article →Sizing AppPoints is a decision exercise, not data entry. A spreadsheet totals a number; it cannot tell you whether it is the right one. Assess and decide, with the right people, before you quote.
Read article →Application, site, and data level. Most security frustration is solving a record-level problem with a site-level tool, or forgetting that access combines across every group a user holds. Includes the layer funnel and the two combination tables.
Read article →Do not build a group per truck. Model the assignment as data with one tech group and a condition that scopes off each user's own record. Covers the ownership-field decision, the condition family, and the combination rule that makes or breaks it.
Read article →Your storeroom restriction looks right but the tech still sees too much. The restriction is not broken, access is combining, and a broad group is OR-ing past your scope. How to find the offender and fix it by membership.
Read article →What actually separates preventive, predictive, and condition-based maintenance, the two myths that cause the most confusion, where each one lives in Maximo, and why PM is the number a regulator wants to see. Includes the maintenance strategy continuum.
Read article →How to set and validate Reorder Points, Maximum Levels, and Safety Stock in IBM Maximo using 12-month consumption and real vendor lead times. Includes a quarterly review decision tree, a criticality-based safety stock framework, ROI scenarios, and the stockout bookend.
Read article →How to identify dead stock in IBM Maximo using the Last Issue Date field, calculate the carrying cost, run a quarterly disposition review, and track improvement without creating stockouts. Includes decision tree, ROI scenarios, and the stockout bookend.
Read article →How to calculate Inventory Turns in IBM Maximo, the mistakes most organizations make with rotating assets and averages, and where to set targets by industry. Includes Version A vs. Version B segmentation, dead stock analysis, and the stockout bookend.
Read article →Either the number is hollow, counting work orders that closed without the work being done, or the PMs are wrong work on the wrong assets. Here is how to tell the difference, and what to do Monday.
Read article →The right target depends on your compliance window, your industry, and your asset criticality. Includes benchmark ranges by maturity level and by industry, plus suggested targets by asset class.
Read article →PdM compliance trails for two structural reasons: unpredictable arrival and specialized resources. The combined number hides a gap on your most critical assets.
Read article →Three metrics, three questions, three blind spots. PM compliance measures timing, schedule compliance measures the plan, PM yield measures effectiveness. Any single one can hide the other two.
Read article →Four causes to work through in order: definition change, backlog wave, availability or parts, and a segment that fell behind. Find the answer and the evidence.
Read article →Check frequency units, lead time, fixed vs. floating, and time zones in this order. Includes the admin-side cron task and time zone mismatch signature.
Read article →Two causes: status synonym mapping that rolls up to completed internally, and cleanup automation that sweeps too broadly. How to find and fix both.
Read article →Looking for the Advanced KPI Series or the MAS Migration article? Those are still at their original URLs under /blog/.