Skip to content
News

How EAM and FSM reduce your maintenance costs

•

9 min leestijd

Enterprise asset management (EAM) and field service management (FSM) reduce maintenance costs when more work is planned and fewer repeat visits are needed. EAM shows what each asset costs to maintain and when work is due; FSM sends technicians out with the right information and parts. Unplanned maintenance can cost more than planned work, because it adds disruption, urgent purchases and lost production. The business case depends on your assets, your data and your ability to act on the findings.

What does reactive maintenance cost you?

Think of a call in the middle of the night about a stopped machine, an urgent technician visit and an express delivery of parts. Calculate the cost of that downtime from your own lost output, recovery work and delivery obligations.

Start with your maintenance accounts and asset history. Separate planned work, reactive work, parts and production losses. Do not infer a maintenance budget from turnover alone. Reactive work can add costs through:

  • Urgent deliveries and expedited freight
  • Out-of-hours technician rates
  • Production losses and catch-up work at higher costs
  • Customer penalties for missed deliveries

Excess stock can tie up working capital while critical parts are unavailable. Measure stock value, shortages and budget variance together to see where planning and inventory decisions need to improve.

How do you see what an asset really costs?

By booking hours, materials, purchases and expenses on the work order. An urgent purchase made outside it appears in purchasing, not in the asset’s history. So do hours on a general cost centre.

According to IFS, these work task bookings create the financial postings in IFS Cloud. At status Finished, a work order moves to history for later analysis. That needs a completion date and authorised postings, and an unconverted purchase requisition blocks that status.

Forgotten hours, materials or external costs can be added later by reopening the work order. Agree with your controller which costs always go on the work order, and who closes it. You decide which cost types to see per asset.

Which maintenance strategy pays off for which asset?

You decide that per failure mode, because one machine can fail in several ways. Run-to-failure only fits where the consequences of failure are demonstrably acceptable. Maintenance by calendar or operating hours suits wear that builds up with time or use. Condition-based maintenance suits failures that give a measurable warning, such as rising temperature or pressure.

IFS Cloud can record this in an FMECA (failure mode, effects and criticality analysis). Per failure mode, your team records a decision such as preventive, corrective, run-to-failure, predictive, spare part management, training or redesign. From a preventive decision, you create a PM action (a preventive maintenance task for an object) with a calendar, condition or event trigger.

Spare part management and training count as maintenance decisions too. An expensive part kept in stock can be the cheapest protection against long downtime. Check that FMECA is in your licence; not every function sits in the same module. Our roadmap to smarter maintenance sets out the phases.

How does predictive maintenance help you anticipate failures?

We start with your processes and introduce technology afterwards. First we analyse your current maintenance processes and identify where the biggest gains lie. Only then do we implement EAM software with predictive maintenance.

Condition data, such as vibration and temperature readings, can help identify abnormal behaviour before a failure. Detection depends on the asset, sensors and model quality. Your maintenance teams validate alerts and decide when to intervene.

Possible improvements to measure include:

  • Fewer emergency purchases at premium prices
  • Less capital tied up in unnecessary stock
  • A higher share of jobs resolved on the first visit
  • Replenishment aligned with actual consumption and lead times

Read what AI adds to predictive maintenance.

How do you build a business case to reduce maintenance costs?

Establish a baseline before implementation and compare equivalent periods afterwards. Track maintenance cost, unplanned downtime and asset availability alongside the cost of software, implementation and ongoing operation.

Measures to track:

  • Total maintenance cost per asset or production unit
  • Unplanned downtime hours
  • Asset availability and useful life

Calculate the investment and payback for your own scope:

  • Annual benefit: avoided costs and released capacity supported by measured evidence
  • Investment: software, integration, data preparation, training and change management
  • Payback: upfront investment divided by net annual benefit, where that benefit is positive
  • Total cost of ownership: implementation plus recurring costs over the chosen evaluation period
  • Check reporting requirements separately; software alone does not establish compliance

Review budget variances periodically and trace them to work orders, parts usage and changes in production demand.

How do you measure MTBF, MTTR and first-time fix?

With definitions agreed before the baseline. Three indicators show whether maintenance and service improve:

  • MTBF (mean time between failures): the average time between two consecutive failures
  • MTTR (mean time to repair): total downtime from failures divided by the number of failures
  • First-time fix: the share of jobs resolved on the first visit, without a return visit

MTTR covers more than the repair. It usually includes notifying the team, letting equipment cool down, reassembly and testing. Waiting for a part or approval counts too.

For first-time fix, agree which jobs count. A planned two-visit job is not a repeat visit; a return because a part was missing is. Ask technicians to record the cause of each follow-up visit: parts, information, skills or scheduling.

How does asset history help the technician in the field?

The technician sees earlier work on the same asset, and their own records extend that history. Missing information about earlier visits or the installation can lead to a wrong diagnosis and a second visit.

IFS Cloud has two mobile apps for this: IFS Maintenance MWO and IFS Service MWO. Technicians see the objects linked to their work, enter measurements and view spare parts. Online, they can also see an object’s location and history. They book materials and manage their own stock in the app.

Those measurements feed the maintenance plan. A reading outside a PM action’s limits creates a work order at the next condition generation, a job IFS says must run regularly. IFS Planning & Scheduling Optimization takes travel time into account when it plans, alongside skills, location and priority.

How did EWT move material bookings from monthly to instant?

Emergya Wind Technologies (EWT) implemented the Service & Maintenance module in IFS Applications. Eqeep did the functional verification and testing for the earlier upgrade to version 9. Since that upgrade, EWT’s service technicians book the materials they use on their tablets via the Mobile Work Order app. Each booking reaches IFS instantly; previously, material bookings were done once a month.

With these direct bookings, EWT can refill vehicles and vans more accurately and on time, and has more control over the flow of materials.

Where should you start?

Start with a bounded scope and agree the baseline, owner and evaluation period for each improvement:

  1. Centralise planning and measure technician utilisation
  2. Digitalise work orders and measure completion-to-invoice time
  3. Optimise inventory and measure stock value alongside parts availability

Prioritise assets where failure has a material operational impact. Use maintenance history and condition data to choose a pilot, then compare its results with the baseline before expanding.

The return is specific to your operation, so agree in advance which benefits you can measure. Include the full implementation and operating costs in that evaluation.

As implementation partner, Eqeep works with organisations to translate EAM and predictive maintenance into lower maintenance costs and higher uptime. We are involved throughout, from process analysis to implementation and adoption.

If your maintenance process is small and simple, a lighter set-up may fit better than a full platform. Read how IFS Cloud EAM and IFS Ultimo differ.

Questions about reducing maintenance costs

How much can EAM save on maintenance costs?

That differs per organisation, so we do not quote a standard percentage. The saving depends on your share of unplanned work, your downtime costs and what your team does with the findings.

What is the difference between EAM and FSM?

EAM follows your own assets from installation to replacement. FSM connects service requests, planning, field work and invoicing for service to customers. In IFS Cloud both share one platform, with separate mobile apps for maintenance and service.

Do you need sensors to plan condition-based maintenance?

Not always. IFS Cloud can create work orders from readings technicians enter themselves, such as operating hours or an oil level. From two meter readings, it forecasts the next maintenance date, assuming even use. Our article on IoT and digital twins covers when sensors do add value.

What could EAM mean for your maintenance costs?

Tell us where you stand with IFS. After one conversation you will have a clear next step. That step can be an EAM assessment of your maintenance costs. Discuss your IFS question

Stay one step ahead with IFS. Get release news and practical examples from IFS Specialized Partner Eqeep in your inbox. Free, and you can unsubscribe at any time.

Yes, keep me posted