Condition-based maintenance
When repairs follow a calendar or an outage, the company pays twice: for unnecessary planned work and for unplanned downtime. We put your equipment into IFS EAM, bring in sensor data through ICONICS and set up work orders that are raised by actual condition.
- Equipment is serviced on schedule even when nothing is wrong
- Faults are discovered after an outage or a complaint
- SCADA and sensor data never reach the business system
- Nobody can quickly say what each asset cost over the year
- Maintenance is planned by equipment condition, not by habit
- Fewer unplanned stoppages and emergency call-outs
- Costs are visible per asset and per site
- Replacement decisions rest on history, not gut feeling
Four steps
Asset register
We build the hierarchy of sites and equipment with technical data, and agree which assets are critical to operations.
Connect the data
Through ICONICS we feed sensor and SCADA readings into IFS EAM and set the thresholds that call for an inspection or a repair.
Work orders and planning
Work orders are raised automatically by condition, with parts and crews attached. Calendar-based work stays where it makes sense.
Cost and investment
Costs are collected per asset, which gives a basis for planning replacements and investment in IFS AIP.
Modules and platforms
Industries
Common questions
How long does an IFS Cloud rollout take?
The first phase usually takes 3 to 9 months, depending on the number of modules, sites and users and on how ready the data is. We give an exact plan after the diagnostic stage.
What does it cost?
The cost is the IFS Cloud subscription plus implementation work. The subscription depends on users and modules; the work depends on configuration, integrations and data migration. After the diagnostic stage we give an estimate and a five-year cost of ownership.
Can we keep 1C?
Yes. Often 1C stays for statutory accounting and tax reporting while IFS runs procurement, inventory, production, maintenance and management accounting. The two systems are integrated so nothing is entered twice.
Cloud or our own servers?
IFS Cloud can run in the cloud or on the company’s own servers. The choice depends on data-residency requirements, IT policy and budget. We compare the options at the design stage.
Do we have to roll out every module at once?
No. Most companies start with finance, procurement and inventory, or with asset management, and add other modules in later phases. It is one platform, so new modules work with the data already in it.
What happens after go-live?
In the first weeks after go-live we stay close to users and fix whatever gets in their way. After that comes support under a contract with clear response times, IFS updates and changes for new needs.