Work Order Duplicate Detection

The same fault is often reported multiple times by different people, through different channels, or across operational shifts. Manually identifying and reconciling duplicate work orders through data exports and ad hoc reviews is time-consuming and error-prone, resulting in wasted effort, unnecessary resource allocation, inflated maintenance backlogs, and poor data quality.

AI-powered Work Order De-duplication enables organizations to detect, review, and resolve potential duplicate work orders both at the point-of-creation and post-creation, reducing manual effort and improving operational efficiency and data quality.

Post-Creation De-duplication: Enables automatic detection, review, and resolution of duplicate work orders - both on-demand for individual records and at scale via background and scheduled batch processes.

Point-of-creation De-Duplication: Before a new Work Order or Fault Report is saved or committed, the system evaluates the entered record in real time against existing active work orders, alerting the user to potential duplicates with similarity scoring and AI-generated explanations, enabling users to prevent duplicate work orders from entering the maintenance lifecycle.

How Duplicate Work Orders Are Detected

IFS Cloud uses AI to identify potential duplicate work orders by comparing their descriptions, business context, and time proximity.

How the matching works

The system combines three types of information to calculate a similarity score for each pair of work orders.

1. Description similarity

The system compares the meaning of the descriptive text in the following fields:

Because the system analyses meaning rather than just matching words, work orders with different wording can still be identified as potential duplicates.

For example, "Water leaking from pump seal" may match "Mechanical seal leak on cooling water pump."

The system also applies a minimum description similarity requirement before calculating the final score. Work orders that do not meet this requirement are excluded from further matching, regardless of their business context or time proximity.

2. Business context

The system compares the following fields to determine whether the work orders relate to the same business context:

Matching values increase the likelihood of a duplicate match, while differing values reduce it. This helps prevent unrelated work orders with similar descriptions from being identified as duplicates.

3. Time Proximity

The system considers the time between the creation of work orders. Work orders created close together in time are generally more likely to be duplicates.

The time-based score decreases as the time between work orders increases. The rate of decrease is controlled by the time sensitivity (DUP_TIME_SENSITIVITY) parameter, which determines how strongly the time between work order creation affects the matching score.

A higher time sensitivity gives greater preference to work orders created close together in time, while a lower time sensitivity reduces the influence of creation time on the matching score.

Similarity score and threshold

The system combines the matching factors using configured weights to calculate a final similarity score.

Final score = (W1 x Description Similarity) + (W2 x Business Context Match) + (W3 x Time Proximity)

Where:

The Similarity Threshold (DUP_SIMILARITY_THRES) parameter defines the minimum final score required for work orders to be identified as potential duplicates.

The threshold can be adjusted to suit your organization's requirements and the level of confidence needed when reviewing potential duplicates.

Enabling duplicate detection at work order creation

The Use Duplicate Check for WO/Fault Report (DUP_CHECK_ON_CREATE) parameter controls whether duplicate detection is performed when a work order or fault report is created.

When this parameter is enabled, the system uses the entered Site and Maintenance Organization fields to filter existing Work Orders. It then considers only Work Orders created within the search horizon specified by DUP_SEARCH_HORIZON for duplicate checking. Any potential duplicates are displayed for review before the user continues.

When disabled, this duplicate check is not performed at the point of creation. Duplicate detection can still be performed on existing work orders using the available post-creation functionality.

Understanding the results

The system groups related work orders into clusters. Each cluster contains work orders identified as potential duplicates.

The results include the following information:

When checking a single work order, the results include only the cluster containing that work order.

Where to configure the settings

You can find the duplicate detection parameters under System Definition/ Object Properties/ Maintenance Configuration.

Parameter Purpose
DUP_SIMILARITY_THRES Sets the minimum final similarity score required to identify potential duplicates.
DUP_TIME_SENSITIVITY Controls how strongly the time between work order creation affects the matching score.
DUP_CHECK_ON_CREATE Enables or disables duplicate detection when a work order or fault report is created.
DUP_SEARCH_HORIZON Defines the number of days the system looks back to identify potential duplicate Work Orders at Work Order creation. Only eligible existing Work Orders created within the specified period are considered when comparing them with the information entered for the new Work Order.

Reviewing and resolving duplicate work orders

AI identifies potential duplicate work orders, but the final decision remains with the user. Review the suggested matches to confirm whether they are genuine duplicates before taking action.

This human-in-the-loop approach combines AI-powered detection with user oversight, helping organizations reduce duplicate work while retaining control over maintenance records and cancellation decisions.

Work order duplicate detection is used in IFS/Maintenance and IFS Cloud for Service Management.