If you're evaluating FLSmidth services for mining industry, or trying to decide whether Raptor cone crusher automation deserves a line item in next year's budget, this is for you. I'm a procurement manager who has tracked every equipment service invoice for the past eight years. That includes managing a maintenance services and spares budget north of $700,000 a year, negotiating against alternative suppliers, and documenting every order in our cost tracking system. These are the questions I wish someone had asked before I signed the first service contract.
FLSmidth services for mining industry cover the full flowsheet, from crushing and grinding to flotation, filtration, conveying, and the controls that connect them. For a mine operation, I think of it in four buckets: equipment supply, aftermarket parts, field services, and advanced automation solutions. Equipment supply includes crushers, mills, screens, feeders, and gearboxes. Aftermarket covers original wear parts and replacement parts. Field services handles inspections, repairs, and commissioning. The automation bucket is where Raptor cone crusher automation lives.
From my perspective, the portfolio is less important than the problem you bring to it. FLSmidth is strongest when you can point to a bottleneck and say, 'this is costing us money.' In our case, that was variable feed and a cone crusher that kept stalling. When we framed the service scope around that, the proposal became much easier to evaluate.
Raptor cone crusher automation is one of those things that sounds like a dashboard feature until you need it. According to FLSmidth's published product documentation, the system monitors pressure, power draw, feed level, oil temperature, and other operating signals, then adjusts parameters in real time to protect the crusher and keep output consistent. In practical terms, it catches early warning signs that lead to stalls, overloads, and liner damage before they turn into failures.
I'd argue the real value is consistency. After the commissioning period, we saw fewer unplanned stops and more predictable wear. There's a lingering belief that automation is only for brand-new crushers. That thinking comes from an era when retrofits required major mechanical changes. Today, the sensor set and control package can often be added to an existing machine, assuming the mechanical condition is sound.
The biggest cost risk is the gap between the quote and the full scope. The automation hardware is only one line item. You also need installation, electrical and network work, chute or guard updates, operator training, and integration with your existing control system. Any one of those can push a project over budget if it's not in the original proposal.
In 2024, I compared two proposals for a crusher automation upgrade. The second proposal looked significantly cheaper at first. But when I put both into the same evaluation spreadsheet, the second one charged separately for configuration, training, and commissioning. The first proposal included them. I'm not 100% sure of the exact percentage now—don't hold me to this—but the 'cheaper' option would have been about 17% higher in total cost. That's the difference between comparing bids and comparing outcomes.
Usually, yes, but 'usually' is doing a lot of work. We retrofitted one of our older Raptor cone crushers in 2024, and the key was a proper mechanical assessment first. Actually, 'first' understates it. The assessment needs to be the foundation, not a checkbox. You need to know the condition of the mainframe, shaft, bearings, and bowl assembly before adding automation. If the machine already has hidden damage, automation won't fix it.
Honestly, I'm not sure why some suppliers talk about retrofit as if it's a simple plug-and-play. It's not. You need a detailed engineering review, and you need the answer in writing: which sensors, which controller, which settings, and which training hours. That documentation is the prevention behind the upgrade. It's what stops a two-week project from becoming a two-month one.
I use three buckets: responsive support, planned maintenance, and performance-based agreements. Responsive support is basically 'call us when it stops.' Planned maintenance adds regular inspections, OEM parts, remote diagnostics, and a calendar of tasks. Performance-based agreements tie the supplier to an outcome, such as availability, throughput, or uptime.
Performance-based contracts can be great, but they are also the easiest to misread. The real question is not which tier sounds better; the real question is how performance gets measured. If the supplier measures from their own data stream and you measure from your plant historian, you're going to argue about numbers later. If you ask, 'who owns the data and how are exceptions handled?' you're already ahead of most buyers.
The one I'd add is: what happens when the network goes down? Automation control can be cloud-connected or local, and that choice matters for reliability. If your internet drops, does the crusher still operate safely? Can the system continue running on local logic? Can you export data to your own historian?
This might not seem like a purchase decision, but it turns into one. We've had suppliers that only offered data access through their cloud portal, which made it harder to correlate downtime with our own maintenance records. Another supplier could export raw data to local files. Both systems worked, but one fit our workflow better. That's the kind of detail that doesn't show up in a brochure.
Some in-house teams can handle day-to-day monitoring and adjustments. But for the initial setup, alarm philosophy, and control limits, I'd want the specialists. It's not that the controls are impossible; it's that a small error in pressure limits can cause unnecessary trips or, worse, mechanical damage.
We had a period where an incorrectly set threshold created false alarms until FLSmidth's team recalibrated the logic. That was a training issue, not a hardware issue. Budget for that training explicitly, and keep at least one operator and one maintenance tech involved in every commissioning session. They're the ones who will live with the system.
Start with your own numbers. I know that's not as interesting as comparing reliability charts and automation features, but it's the step that most determines whether a service contract pays off. Log your failure modes, mean time between repairs, overdue maintenance, and the actual cost of each unplanned stop. Include labor, lost production, emergency parts, and the overtime meals if you have to.
If you don't have clean data, begin collecting it now. Three months of honest history beats a six-figure contract based on assumptions. I built a simple checklist after being burned by a vague service agreement: downtime root cause, parts availability, response time, data access, and termination terms. Five minutes of verification beats five days of correction, and in heavy industry, that usually means the difference between a planned shutdown and an emergency one.
Ask for a commissioning plan in writing, too. Who does what, when, and what happens if a promised date slips. That sounds like project management, but it is actually budget management.
Discuss This Topic
If this article connects to an active wear issue at your plant, use the inquiry form to continue the conversation with our advisory team.
Tell Us What Is Wearing Fastest
Share plant stage, maintenance window, and the result you want to improve so our team can respond with a practical next step.