Skip to main content
Question

Can we have more details about the Deprecation and Removal Plan (DARP) for Work Order Based Service

  • October 2, 2026
  • 1 reply
  • 58 views
NIKKID
Do Gooder (Customer)

I would like some help understanding the scope of Deprecation and Removal Plan (DARP) for Work Order Based Service. I want to start moving processes from “work order” based services to “request based” services, but we’d appreciate knowing exactly what’s coming before we start making big changes:

To anyone who has more information on this, please help us with the following questions:

1. Will Maintenance still rely on work orders and tasks for things like PM Actions / Programs and Plans after 27R1 with full support?


2. Will Serial Objects, Functional Objects (EquipmentObjects) functionality ultimately remain the same after 27R1 with full support?


3. Will we still have access to our historical work orders. In other words, will we still be able to pull up the historical work orders page and see what services we completed with all the basic data we currently have after 27R1?


4. Will the MWO Service App remain the primary way can receive information from our techs at customer sites so long as they are using “request-based service functions” instead of “work order-based service functions” after 27R1? Or, do will we need to deploy a new app altogether after 27R1. Which version of the MWO Service App do we need to use to be compliant with request-management?


5. Most importantly, what do you suggest for migration of our work order and work task data and basic data if needed? If work order records will be preserved, do you recommend we transition to request management without a formal data migration?

My very condensed understanding of key phrases in questions above:

Service = work performed for a customer on their equipment objects

Maintenance = work performed for us internally on our own equipment objects

Equipment Objects = physical or conceptual (serial or functional) assets we can optionally track in our system or against work orders.

Work Orders = currently the foundation of all work in Service & Maintenance, contains work tasks. All transactions driven against work tasks.

PM Actions / PM Programs/Work Task Templates = work order/task generators for service or maintenance

MWO Service App = externally focused on customer PM or Service needs

MWO Maintenance App = internally focused on our own PM or Service needs
 

    1 reply

    Hero (Employee)
    Forum|alt.badge.img+9
    • ajnsse
    • Hero (Employee)
    • October 5, 2026

    Hi ​@NIKKID 

    Thank you for the questions. I'll try to clarify and answer your questions. I hope you have also read the full DARP document for 26R1 published here on the community. There the affected areas are listed. And as you can see in that document none of the areas PM/ PM programs, Equipment, historical work orders etc. are listed.

     

    We are also going to update the DARP information for the upcoming 26R2 release - so make sure to have a read of that when available.

     

    1. Will Maintenance still rely on Work Orders and Tasks for PM Actions / Programs and Plans after 27R1?

    Yes. The DARP only applies to the Work Order-based Service Management solution and customer service processes built on that model. Maintenance Management remains a strategic and fully supported part of IFS Cloud and continues to use Work Orders, Work Tasks, PM Actions, PM Programs, PM Plans, and related maintenance functionality. The announced deprecation does not target Enterprise Asset Management / Maintenance processes.

     

    2. Will Serial Objects and Functional Objects remain supported?

    Yes.

     

    3. Will historical Work Orders still be accessible?

    Yes. Historical Work Orders are ofcourse remaining available for inquiry, traceability, auditing, reporting, and commercial history purposes. The DARP focuses on some specific Work Order-based service execution processes, and absolutely not on deleting any historical records.

     

    4. What happens with the MWO Service App?

    The DARP specifically mentions mWO Service that currently includes both work order based and request management based processes.

    However, this does not mean mobile support disappears. Mobile capabilities are already supporting Request Management-based processes and Request Tasks. 

    Today, customers can continue using the supported MWO versions that support Request Management capabilities, mWO Service. There is also still going to be, as already exists, a maintenance version of mWO that will still support work order based work.

     

    5. What migration approach is recommended?

    The final migration tooling and supported transition path are still being developed and no deprecation will happen before these are all in place.

     

    In relation to the key phrases I also really want to highlight that “Maintenance = work performed for us internally on our own equipment objects” is not fully correct. Customer information and invoicing will still be part of the work order solution. As you can also read from the DARP document those areas are not listed for deprecation.

    Terms & ConditionsAccessibility statement