Maximo KPI Guide: Planned Backlog
Know how much ready work you are carrying. Schedule against it. Keep it honest.
Most Maximo sites have a backlog number, and almost none of them can act on it. It lumps together work that is fully planned and ready to schedule with work that is waiting on parts, waiting on a plan, or waiting on a decision. So the number goes up, the number goes down, and the weekly scheduling meeting still runs on gut feel. A backlog you cannot schedule against is not a metric. It is a pile.
What You Get
This guide walks through implementing Planned Backlog as a live operational control in IBM Maximo. It starts by locking the definition so total backlog, planned backlog, and scheduled backlog stop getting confused with each other, then expresses the number in crew-weeks so it means something in a scheduling meeting instead of being a raw count nobody can size. It covers the verified Maximo field mappings (WORKORDER, WOSTATUS, WPLABOR, WPMATERIAL, and LABOR for crew capacity), a step-by-step KPI Manager configuration walkthrough, a Cognos Analytics dashboard, annotated SQL queries you can copy and run, a Green/Yellow/Red threshold framework with a trigger-action matrix that names who does what by when, root cause playbooks for when the backlog runs hot or dries up, and a quick setup checklist you can hand to your Maximo admin.
Who This Is For
This is for planners and schedulers who own the backlog and have to defend the schedule every week. For maintenance managers who need to know whether they are carrying enough ready work to keep crews productive without burying them. For Maximo administrators who need to configure KPI Manager, build the escalation rules, and set up the Start Center portlets. And for consultants implementing Maximo who want a field-level reference specific to the platform, not a generic backlog definition.
Not a 5-Page PDF
This is not a five-page PDF with a formula and a bar chart. It is a complete operational control guide covering definition, rules, thresholds, ownership, Maximo configuration, Cognos reporting, SQL queries, drilldowns, root cause playbooks, related KPIs, and the process discipline that keeps the backlog data honest over time. Every section includes specific Maximo field names, navigation paths, and configuration steps verified against MAS 9.
This guide is part of the Maximo KPI Guide Series. Each guide follows the same 8-chapter, 27-section structure so you can build a complete work management scorecard one KPI at a time.
Get the guide and set it up this week.
Amazon — Coming Soon