1. What the MRO app is for
MRO means Maintenance, Repair and Overhaul. It works differently from manufacturing. You are not producing to a plan. You are reacting to equipment that arrives when it breaks.
The app exists to make that reactive work manageable.
The three goals
Goal | What it means day to day |
More on-time delivery | You meet the dates you promised your customer |
Less turnaround time | The cycle from arrival to shipment gets shorter |
Better team productivity | Less time looking for information, more time fixing problems |
The problems it solves
Problem | Why it is hard |
Repair demand is unpredictable | You cannot plan for breakdowns the way you plan production volume |
Repair lead times are hard to see | Without visibility, a stalled order looks the same as a moving one |
Priorities compete | Several orders need the same scarce part, and the shop floor does not always work on what matters most |
Volumes keep rising | Older equipment creates more MRO orders every year |
Logistics visibility is poor | Parts, subcontractors and internal repair loops all move at different speeds |
The app answers these by keeping everything in one place: what each service order needs, what is missing, when capacity runs out, and what to do first.
💡 The key MRO insight is that you often do not need more stock. You need the right orders served first. If several service orders need the same scarce part, and some are missing one component while others are missing many, serving the nearly finished ones closes more orders with the same stock. See Simulations for how to test this before you commit.
2. Which view should I use ?
The app has four views. Each one answers a different question.
If you are asking | Open |
"What is the state of my service orders?" | Service Order Book, table view |
"Which orders are blocked, and by which part?" | Service Order Book, heatmap view |
"What is missing, and since when?" | Missing Part view |
"Will I have the capacity to do this work?" | Capacity view |
"What happens if I change my priorities?" | Simulations. See the separate article. |
3. Service Order Book
This view lists all your maintenance work, ongoing and scheduled. You use it to check status, follow progress, and confirm that orders will finish on time. Each order carries its context with it: who is assigned, which parts it needs, and its planned timeline.
3.1 Table view
Every service order appears as a row. Each row is a piece of equipment, with its service order number and serial number. Orders are sorted by date, oldest first.
Column | What it shows |
Status | Combines service order coverage, delivery status and commercial status. Hover over it for the detail behind the figure. |
Service Order | The service order number. |
Equipment | The ID or reference number of the equipment. |
SN | The serial number of the equipment. |
Required Cov | When the component is needed, and when the stock projection algorithm allocates parts to it. |
Revised Due | The completion date negotiated and agreed between you and your customer. Always populated, and the date Pelico uses to calculate on-time delivery. |
Reception | The date the module was physically received. |
Customer Req. Date | The date the customer originally asked for, before any negotiation. Can be contractual. Hidden by default. |
💡 Revised Due and Customer Req. Date are not the same date. Customer Req. Date is what the customer asked for on their own. Revised Due is what you and the customer agreed after discussing it. When the original request could be met as-is, the two match. When it could not, Revised Due is the commitment that replaced it.
This matters because on-time delivery is measured against Revised Due, not against what the customer first asked for.
3.2 Heatmap view
The heatmap sits next to the table view. Here the columns are the parts your MRO operations need, and the rows are your service orders. It is the fastest way to see which part is blocking which order.
Reading a column header. Each header is the name of a part, and it is clickable: selecting it opens further actions on that part.
Reading a cell. Stock appears as XX / YY:
XX is the stock required to execute all MRO orders.
YY is the stock currently available.
Colour code for stock levels
The colour answers one question: does current stock cover what the service orders need?
Colour | Meaning |
🟢 Green | Stock covers the need. |
🟡 Yellow | The need is conditionally covered: supply is expected in time. |
🔴 Red | Stock does not cover the need, or the supply arrives too late. |
💡 Some views express this as a shortfall figure rather than a stock figure. Where you see a number described in terms of used parts, read it as demand minus available stock: a positive value is the quantity still missing, so it turns the cell red. Zero or below means stock covers the demand. The number measures the gap, not what is on the shelf. This is why a positive value is bad news.
💡 The heatmap is the starting point for most MRO work: allocating a scarce part, unblocking an order after kitting, escalating a shortage. See MRO Usage Scenarios.
4. Missing Part view
This view shows the parts holding up your service orders, on a timeline. Each line gives you enough context to act on the part instead of just noting it.
Element | What it tells you |
Blocking Date | The date when the part will block production. |
Required Part | The specific part needed. |
Plant | The location where the part is needed. |
Parent Equipment | The equipment the part belongs to. |
Part Type | Whether the part is M, B, or M&B (Make, Buy, or both). |
Related Events | Supply events, and any Stock Transfer Opportunities. |
Days Until Missing | How many days until the part runs out, with the break date. |
Colour coding
Colour | Meaning |
🔴 Red | The part is blocking production. |
🟡 Yellow | The part is conditionally covered. |
💡 Days Until Missing is the column to sort on. Blocking Date tells you when a part becomes a problem; Days Until Missing tells you how long you have left to do something about it.
5. Capacity view
This is the only place in Pelico where work centre capacity is modelled. Capacity is set as hours per week, per work centre.
What it gives you
Early warning of blockages. You see where repair work will stall before it does.
Load against capacity. You see the work you have next to the hours you have. Bottlenecks become visible instead of something you guess at.
💡 This view has no equivalent in Production Control. The Suggested Start Date in the Work Order Book ignores capacity on purpose. It tells you when material and upstream work allow a start, not whether you can take it. If capacity is your constraint, this is the view that tells you.
6. Planned workload vs capacity
This extends the Capacity view by adding forecast demand, so your capacity analysis reaches beyond firm orders.
Feature | What it gives you |
Sales forecasts included | Forecasts enter your planning early, so you can see blockages coming |
Effect on workload | Forecasts feed the workload, which lets you compare load and capacity over the long term |
Material needs shown | You see how forecast demand turns into material needs, and where that creates bottlenecks |
Filtered analysis | You can limit the analysis to the work centres you care about |
Work centre heatmap | Week by week view of blockages across all work centres, over the coming months |
Blockage indicator | A status flags any service order that needs a work centre with too little capacity that week |
💡 The blockage indicator is worth understanding. It is a capacity problem, not a material one. A service order can have every part it needs and still be flagged, because the work centre it needs is overloaded that week. That is a different problem with a different fix: move capacity, or move the work.
⚠️ Pelico uses the word "heatmap" for two different views. The heatmap view in the Service Order Book shows service orders against blocking parts. The work centre heatmap here shows work centres against weeks. They are not the same.
7. How MRO connects to the rest of Pelico
Coverage works the same way in MRO as everywhere else in Pelico. A service order gets the worst coverage status among the parts it needs, and the statuses mean the same thing: covered from stock, conditionally covered while supply is expected, delayed when supply arrives after the need date, or blocked with no solution.
Topic | Where to read about it |
Coverage, stock projection, pegging | Pelico's Algorithms |
Testing a change before you commit to it | Simulations |
Simulating gate commitments to reduce work in progress | Simulations, MRO section |
Escalation tickets and tiers | Introduction to Production Control |
8. FAQ
How is MRO different from Production Control?
Production Control manages work orders against a production plan. MRO manages service orders against repair demand that arrives without warning. The coverage logic is the same. The views, the priority questions and the capacity model are different.
Why is my service order blocked when all its parts are available?
Check whether it is a capacity blockage rather than a material one. A service order that needs a work centre with too little capacity in a given week gets its own status, separate from material coverage.
Where do I see work centre capacity?
In the MRO Capacity view. It is set in hours per week per work centre, and it is the only capacity model in Pelico.
Do sales forecasts change my MRO plan?
Yes, where they are switched on. They feed the workload used for long-term load and capacity analysis, and Pelico shows what they mean for material.
Do coverage statuses mean the same thing in MRO as in Production Control?
Yes. Covered, conditionally covered, delayed and blocked are calculated the same way. See Pelico's Algorithms.
9. Glossary
Term | Definition |
Blocking date | The date from which a missing part starts holding work up. |
Capacity view | The MRO view comparing workload against work centre capacity. |
Load vs capacity | The work you have to do compared with the hours available at a work centre. |
MRO | Maintenance, Repair and Overhaul. |
OTD | On-time delivery. |
Rotable | A repairable part kept in a pool and exchanged rather than replaced. |
Service Order (SO) | An order to maintain, repair or overhaul a piece of equipment. |
Service Order Book | The view listing all service orders with their status and context. |
Turnaround time (TAT) | The time from equipment arrival to shipment. |
Work centre | A resource with a limited number of hours available each week. |
WIP | Work in progress. Repair work started but not finished. |
