Maintenance software for sugar and ethanol mills
A mill runs two maintenance operations at once, the plant and the cane harvest fleet, and both have to reach SAP PM with the same data. PM Run takes orders, notifications and confirmations to the field, online or offline, and schedules the off-season against the real capacity of each work center.

What maintenance software for sugar and ethanol mills is
It is the system that organizes maintenance across a mill's two fronts, the plant (cane preparation, milling tandem, boiler, cogeneration, elevation and conveying) and the harvest fleet (harvesters, haul-out wagons, tractors and trucks), from planning the off-season shutdown to executing work in the field during the crushing season. PM Run does this as a layer on top of SAP PM: Gantt scheduling with capacity per work center, order creation and execution on the phone, online or offline, and confirmations posting back to SAP, which remains the central record of assets, orders and costs.
A mill keeps two maintenance operations running at the same time
Inside the plant, wear concentrates where the cane travels: preparation with knives and shredder, the milling tandem with its bearings, gearboxes and headstock alignment, the boiler and pressure vessels under the mandatory inspection of Brazil's NR-13 standard, the cogeneration turbogenerator and the elevation and conveying network that moves cane and bagasse between stages. The plant runs 24 hours a day through the whole crushing season and sends the bill during the off-season.
Out in the field, the harvest fleet follows the opposite calendar. Harvesters, haul-out wagons, tractors and trucks are pushed hardest exactly while the plant is crushing, and maintenance happens in the field workshop and the tire shop, far from any terminal. The cost weight is not marginal: according to a survey published by Cana Online, fleet maintenance accounts for 24.1% of the cost of a bag of sugar, with trucks taking 30% of that spend, harvesters 23% and tractors 17.9%.
These are two routines with different crews, rhythms and locations, judged by the same availability figure and feeding the same SAP PM. When each one records in its own way, the planning team spends the week consolidating spreadsheets instead of scheduling the next one.
The off-season shutdown is a project with scope, schedule and a definition of done
Between December and March a Center-South mill bills only 4% to 5% of its annual revenue, because the plant is not crushing. It is the only window in which the milling tandem and the boiler can be stripped down with the plant stopped, and it is roughly four months that have to deliver a full year of availability: knife and hammer replacement in preparation, laser alignment of headstocks and drives, inspection of piping, valves and heat exchangers, hydrostatic testing, plus the contractor packages moving in and out of the plant in a tight window.
And the window keeps shrinking. Sector press at Canal Jornal da Bioenergia reports that mills have been cutting the off-season period to expand sugar and ethanol output and meet cogeneration commitments, and that the shorter window demands more effective planning and scheduling so the start of the next season is not compromised.
Planning without scheduling does not survive that squeeze. Scope becomes a list of orders, the list has to fit the capacity of each work center week by week, and every crew has to confirm what it executed on the day it executed. Without that, real shutdown progress only shows up in the next morning meeting, when the decision to replan is already a day late.
During the season, stopping is expensive and breakdown work goes unrecorded
With the mill crushing, the math changes. A report by CompreRural estimated the loss from a milling stoppage at up to R$ 1.22 million every 12 hours, and that number is what pushes the sector to defer everything that is not an emergency to the off-season. The side effect is well known: equipment reaches the shutdown more degraded than the plan assumed.
Meanwhile, maintenance keeps happening. Night-shift breakdown work on a mill roll, harvester base cutter blades that lose their edge in about eight hours of operation, field workshop rescues out in the cane. Much of that execution never becomes a record in SAP PM, or becomes one days later, typed by someone else from a handwritten note. Without that data, mechanical availability, MTBF and MTTR become estimates, and maintenance cost per ton does not match what the operation actually spent.
What is at stake in these decisions has grown. In an interview with Cana Online, consultant Dário Sodré, of D2G, sums up the shift: in 1990 a maintenance manager was responsible for around US$ 1 per ton of cane, today that responsibility reaches US$ 5 per ton, and mills already commit 26 kg of recoverable sugar per ton just to pay for maintenance, against 19 kg per ton in the recent past.
Between the field, planning and SAP, the data goes through paper and spreadsheets
The average cost to process one ton of cane was R$ 26.24 in the 2024/25 season, and plant maintenance accounted for 30.3% of that figure, according to the Expedição Custos Cana 2025 study by Pecege, published by RPAnews. It is one of the two largest lines in the industrial cost. A line that size should not depend on re-keying spreadsheets.
The typical path is still this one: the mechanic writes the job on a paper form, the team leader consolidates it in a spreadsheet at the end of the shift, someone types it into SAP the next day and the planning team builds the indicator in a third spreadsheet. Every handoff loses detail, delays closing and creates a different version of the same fact. The shortage of qualified technicians, flagged by JornalCana as one of the sector's bottlenecks, makes it even more expensive to spend skilled hours on data entry.
What PM Run delivers in a mill
PM Run features applied to both maintenance fronts of a mill, always connected to SAP PM.
Field execution, online and offline
The technician receives the order, executes it and confirms it by operation on the phone, even with no signal inside the plant or out in the cane, and PM Run syncs once the network is back.
Order created in the app, mirroring IW31
The crew opens the order right where the job is, with the same fields as SAP PM's IW31, without waiting for someone in the office to type it.
Notification with a photo at the equipment
Maintenance notification with cause, symptom and object part catalogs, with photos and PDFs attached, recorded against the asset instead of the shift's memory.
Off-season scheduling on a Gantt
The official schedule groups the period's orders in a Gantt view, distributes them by capacity and skill of each work center and integrates with SAP PM.
Labor and measurement confirmations
Automatic or manual labor confirmation and measuring point readings by equipment or functional location, with QR Code to identify the asset in the field.
Data ready for your own dashboard
The analytics platform delivers maintenance data automated from execution recorded in SAP, so the mill builds its own dashboard: availability, backlog by criticality, MTTR and MTBF by equipment class, cost and crew utilization.
The mill routine without and with PM Run
| Mill routine | Paper form, spreadsheet and SAP GUI | With PM Run |
|---|---|---|
| Night breakdown during the season | Written on a form, typed in later | Confirmed in the app, on the spot, with a photo |
| Job in the cane with no signal | Waits for the return to base to be recorded | Executed offline and synced on return |
| Opening an order in the field | Radio request, someone types IW31 | Order created in the app, mirroring IW31 |
| Off-season scheduling | One spreadsheet per crew, no capacity view | Gantt with capacity per work center |
| Shutdown progress | Shows up in the next morning meeting | Same-day confirmation and a status kanban |
| Maintenance indicators | Manual consolidation, closes late | Data ready, dashboard built by the planning team |
SAP is already in the mill, what is missing is the execution layer
The sector has been consolidating management on SAP and migrating to S/4HANA, and that is public record. Usina Coruripe completed its S/4HANA migration in 2025 with a total downtime window of only three days, according to Agro Summit, and São Martinho moved to the RISE with SAP cloud model, as reported by technology press. These are market cases, brought here as sector context, not as PM Run customers.
What an ERP migration does not solve on its own is the last meter. The order has to be executed inside the milling tandem, the confirmation happens out in the cane, and the schedule is rebuilt every week by the planning team. SAP PM remains the central record of assets, orders, costs and the preventive strategy, which is where the plan and its frequencies live. PM Run is the execution and planning layer running on top of it, so the data is born where the work happens.
What is proven, and in which context
The platform runs on top of SAP PM in large industrial operations, with more than 12,000 maintenance users working in the app and the portal every day.
More than 12,000 users
PM Run, ITSS Group
With notification, photo and order on the phone and fast adoption in the field, maintenance began centralizing information in SAP PM. The context is citrus juice agribusiness, not a sugarcane mill, and the figure measures the plant assessed.
95% work order confirmation at the plant assessed
Citrosuco, citrus juice agribusiness
Frequently asked questions
Does PM Run replace SAP PM in a mill?
No. SAP PM remains the central record of assets, orders, costs and the preventive strategy. PM Run is the execution and planning layer on top of it: it takes orders, notifications and confirmations to the field and posts the data back to SAP.
Does PM Run cover maintenance of the cane harvest fleet?
It covers maintenance of equipment registered as assets in SAP PM, including harvesters, haul-out wagons, tractors and trucks. The field workshop mechanic opens a notification, executes the order and confirms it on the phone, offline when there is no signal. PM Run does not do telemetry, on-board computers or sensor-based fleet monitoring.
How does PM Run help with the off-season shutdown?
Through the official schedule in the Planning module: the period's orders enter a Gantt view, distributed by capacity and skill of each work center, and execution goes to the field through the app, with same-day confirmation. There is no separate shutdown module, the shutdown is run with the general SAP PM order capability.
Does the app work with no signal inside the plant and in the cane fields?
Yes. The technician downloads the offline base, executes and confirms without a network, and PM Run syncs the information once the connection is back.
Does PM Run deliver a ready-made availability and MTBF dashboard?
It delivers maintenance data ready and automated from execution recorded in SAP, so the planning team builds its own dashboard. Availability, backlog by criticality, MTTR and MTBF by equipment class, cost and crew utilization are examples of what a mill builds with that data, in the format it already uses.
Is there a public sugarcane mill case study with PM Run?
There is no published sugarcane mill case so far. The available evidence is institutional, with more than 12,000 users on SAP PM, and the Citrosuco case, which is citrus juice agribusiness rather than a mill, with 95% work order confirmation at the plant assessed. In the diagnostic session the conversation is about your operation, with what exists in your plant today.
Related content
SAP PM Maintenance Routine Diagnostic
A 45 minute conversation about your off-season and crushing season routine in SAP PM, with practical feedback on what can be adjusted in scheduling and field execution.