Equipment Usage-Based Maintenance Plans Guide

In MobilityWork, from now on, when a measure reading exceeds the defined threshold, a maintenance task is automatically generated. This allows:

• Not wasting time creating tasks manually.

• Ensuring maintenance exactly when it is needed, avoiding delays or oversights.

• Recording all readings and tasks in a traceable manner.
  
   

What is the threshold in MobilityWork?

A limit value defined in a maintenance plan indicating the point at which a maintenance task must be automatically created. When the numeric measure reading reaches or exceeds this value, the system considers that intervention is necessary and creates the corresponding task. 

The threshold is used to define the frequency or usage amount after which maintenance is activated, ensuring that tasks are performed at exactly the right time.

Thresholds are always incremental: they cannot be negative and never reset to 0 after a reading. Each new threshold is calculated by adding the initial threshold to the previous threshold, ensuring a continuous and logical progression.

Maintenance plans based on measures can only be created with numeric measures because the system must mathematically compare readings to thresholds to automatically generate tasks. 

• Numeric measures: allow ≥, ≤, etc. comparisons and trigger tasks correctly.
  Example readings:

  • 300

  • 400

  • 556

  • 434.665

• Text-type measures: cannot be compared to a threshold, so they are not compatible with maintenance plans.
  Example readings:

  • Production 345

  • (23-56)

  • Ok 43

  • Limit 679

  • 23 > 10

  • 10 degrees

  • All ok

How it works? 💡

Imagine you have a usage-based maintenance plan with this rule: Generate a task every 300 units on the Production measure 

❌ Measure reading at 250 units = DOES NOT GENERATE A TASK 

Explanation:
Measure reading: 250
Current threshold: 300 units
Maintenance plan check: Is 250 ≥ 300? NO, so no task is created
Threshold: 300 units

✅ Measure reading at 300 units = GENERATES A TASK

Explanation:
Measure reading: 300
Current threshold: 300 units
Maintenance plan check: Is 300 ≥ 300? YES, so a maintenance task is created
Next threshold: 300 + 300 = 600 units

❌ Measure reading at 450 units = DOES NOT GENERATE A TASK

Explanation:
Measure reading: 450
Current threshold: 600 units
Maintenance plan check: Is 450 ≥ 600? NO, so no task is created
Threshold: 600 units

✅ Measure reading at 620 units = GENERATES A TASK

Explanation:
Measure reading: 620
Current threshold: 600 units
Maintenance plan check: Is 620 ≥ 600? YES, so a maintenance task is created
Next threshold: 600 + 300 = 900 units

In this way, the system will check and, if necessary, create the corresponding tasks, which will also appear in the timeline.

To start with the magic, let’s go step by step.
 

Creating a measure-based maintenance plan
 

Role: Administrator

Steps to create a plan:

1. Go to Maintenance Plans → Create a Plan.

2. Fill in the basic plan information.

3. In the planning section, select the plan type: “Triggered by a measure.”

4. In the cycle section:

   • Measure: select a measure (Only numeric measures will be listed)

   • Initial threshold: value at which the first task will be created

5. Task duration: can be set in days, hours, or minutes depending on maintenance criticality

6. Validation and confirmation
   Before saving, the system will display an example of task generation according to the measure readings and configured threshold. This allows the administrator to verify that thresholds and task creation frequency are correct.

If you already have measures containing text-type readings, they will not appear in the list of measures available to create a maintenance plan. We recommend creating new numeric measures to fully use this feature.

If you want to create units and measures adapted to the new type of maintenance plan, here is a quick reminder:

Creating new units and measures 

Role: Administrator

Units
Units allow the system to interpret and quantify the values of your measures. There are two types:

• System units: already defined by MobilityWork, included by default in all installations. They cannot be deleted or archived. Their code starts with "$" for distinction.
   

  

   

• Custom units: can be numeric or text. Only numeric units/measures are compatible with measure-based maintenance plans. 

  These units can be archived and restored.

Example of a measure with a numeric unit:

Readings:
300
556
23
434.665

Example of a measure with a text unit:

Readings:
Production 345
(23-56)
Ok 43
Limit 679

Creating a new unit

Role: Administrator

• Go to Measurements → Manage Units button

• Click “Create a Unit”

• Fill in required attributes:

  • Name: “Pieces Produced”

  • Symbol: “pcs”

  • Code: auto-generated from the name

    • The system checks code uniqueness and shows an error if it already exists

• Type: numeric or text (choose numeric for maintenance plans)

• Save. The unit will be available for creating new measures
  
  

Creating measures

Role: Administrator

Measures are quantifiable values that the system can read and use to trigger maintenance plans. They can represent pieces produced, hours of use, pressure, temperature, etc.
 

Reminder: Only measures with numeric units can be used for automatic maintenance plans based on equipment usage.

Steps to create a measure:

• Go to Measurements → Click “Create a Measurement”

• Fill in the required fields:

  • Name: e.g., “Production Measure”

  • Code: auto-generated from the name, unique on the network

    • The system checks that the code is not duplicated

  • Description: optional, e.g., “Number of pieces produced by the equipment”

  • Unit: select the corresponding unit, created previously (only active units can be selected)

Once measures are created, the user can:

• Create maintenance plans based on these measures

• Create or modify checklists including steps with measurements

• Start recording measure readings from:

  • The equipment  page BETA (only in the web version)

  • An activity within a task

  • A checklist associated with a task

If your measures and plans are ready, you can now record readings.

Recording measure readings

Recording from the equipment BETA page

Roles: Administrators, Technicians, Production

Only in the web version

Steps:

1. Go to the equipment page and view details

2. Click “Record measure reading” at the top right

3. Select the measure

4. Enter the value

5. Select the date and time of the reading

6. Save the reading
   
   

Notes:

• Future dates are blocked and cannot be recorded

• Past dates trigger a warning but can be saved

• Readings made from the equipment cannot be modified or canceled

• Readings can be viewed from the dashboard, filtered by equipment

• If a maintenance plan exists, the equipment of the reading must exactly match the one associated with the plan to generate a task
  
   

Recording from an activity within a task
 

Roles: Administrators, Technicians, and (Service Providers only if assigned to the task)

The process is the same to add an activity: you need to have a created, unfinished task and add an activity. Select the measure and fill in the information

Notes:

• If a maintenance plan exists, the equipment of the task must exactly match the plan and the measure configured to generate a task
  
  

Recording from a checklist

Roles: Administrators, Technicians, and (Service Providers / Production only if assigned to the task)

The process is the same to fill out a checklist: you need to have a checklist already created with the measures you want to use, add this checklist to the created, unfinished task, and fill it out

Notes:

• Equipment must exactly match the plan and measure configured to generate a task
  
  

What happens after recording a measure reading?

Automatic task generation

In MobilityWork, once a numeric measure reading is recorded, the system checks whether this reading exceeds the current threshold defined in the associated maintenance plan. Depending on the result, one of the following actions is executed:

1. Reading below threshold
    

   
   Action: No task is created
   Threshold: Remains the same until the next readings
   
   Example:
   Current threshold: 600 units
   Measure reading: 450 units
   Result: No task created, next threshold remains 600 units

   ---

2. Reading equal to or above threshold
    

   
   Action: The associated maintenance task is automatically created
   New threshold: Calculated by adding the initial threshold to the current threshold
   
   Example:
   Initial threshold: 300 units
   Task generated for measure reading: 457 units
   Next threshold: 600 units
   Measure reading: 620 units
   Result: Maintenance task created
   Next threshold: 600 + 300 = 900 units

   ---

3. Reading exceeding multiple thresholds at once
    

   Action: If the reading exceeds multiple maintenance cycles, the system calculates the next threshold. This prevents duplicate task creation if production progresses quickly. The system ensures maintenance is always performed just after the last exceeded threshold.

   1. Example:
      Initial threshold: 500 units
      Task generated for measure reading: 700 units
      Next threshold: 1000 units
      Measure reading: 2200 units

   
   System interpretation:

   Intermediate thresholds were 1000, 1500, 2000
   The reading of 2200 exceeds all thresholds
   The system creates a task for the last reached threshold, 2000
   Next threshold: multiples of 500 above 2200, i.e., 2500

   Result:

   Task created for threshold 2000
   Next threshold adjusted: 2500
   
    

   ---

Visual summary of the rules

Maintenance plan level actions

Updating maintenance plan history

Whenever a task is generated by a usage-based plan:

• It is automatically recorded in the maintenance plan history with the following information:
  
  

• User who recorded the reading

• Task ID created

  • Measure with recorded value and reading date

• Threshold reached (strikethrough) and next threshold
   

  
   

Quick access in maintenance plan detail:

• Click on the last reading → leads to the dashboard with reading details

  • In the dashboard, the task ID containing this reading will be added; if the reading was made from equipment, this part remains empty

• Click on the next occurrence → leads to the next scheduled task

• Click on the task list → displays tasks associated with the plan
  
   

Managing readings that generated tasks

Modifying or canceling measure readings
Once a reading exceeds a threshold and a task is generated, it may be necessary to modify or cancel the reading. The system automatically handles these changes to maintain threshold and task consistency.

Case 1. Modifying a reading that still generates the task
 

Example:
Initial threshold: 500 units
Last threshold reached: 1000
Next threshold: 1500
Recorded reading: 1100 (task generated)
Action: User corrects reading from 1100 to 1250
System interpretation:

• 1250 remains between last threshold (1000) and next (1500)

• Original task remains active

• Last threshold reached updated: 1250

• Next threshold remains 1500

Result: Task is not deleted, only the reading is updated

Case 2. Modifying a reading that no longer exceeds the threshold
 

Example:
Initial threshold: 500 units
Last threshold reached: 1000
Recorded reading: 1100 (task generated)
Next threshold: 1500
Action: User corrects reading from 1100 to 950
System interpretation:

• 950 no longer exceeds the threshold that generated the task (1000)

• Associated task is automatically canceled

• Last threshold reached returns to previous (500), since 950 > 500

• Next threshold recalculated: 1000
   

Result: Task is canceled, plan returns to pre-trigger state, and canceled task history includes explanation

Example history message:

"Task was canceled by Ana Alvarez. The measure reading that generated this task was replaced, causing task cancellation."

Case 3. Modifying a reading that now exceeds a new threshold
 

Example:
Initial threshold: 500 units
Last threshold reached: 1000
Recorded reading: 1100 (Task A generated)
Next threshold: 1500
Action: User corrects reading from 1100 to 1650
System interpretation:

• 1650 exceeds the next threshold (1500)

• Task A is canceled because the reading of 1100 no longer corresponds to the new threshold

• A new Task B is created for threshold 1500

• Last threshold reached updated: 1500

• Next threshold: 2000

Result: Task A is canceled and new Task B is created for threshold 1500 corresponding to reading 1650

Case 4. Modifying a reading that activates a previously skipped intermediate threshold
 

Example:
 

Task A

• Initial threshold: 500 units

• Recorded reading: 800 (Task A generated for threshold 500)

• Next threshold: 1000
   

Task B
 

• Recorded reading: 12000 (Task B generated for threshold 12000, skipping intermediate thresholds 1000, 1500, …, 11500)

• Last threshold reached: 12000

• Next threshold: 12500

Action: User corrects reading from 12000 to 1200
 

System interpretation:

• 1200 exceeds previously skipped 1000 threshold

• Corrected reading now takes into account threshold 1000

• Task B for 12000 is canceled

• Next threshold: 1500
  
   

Result: Task B for threshold 12000 is canceled with history event explaining cancellation, and new Task C is created for threshold 1000

Case 5. Modifying a reading revealing that another previous reading should have generated a task
 

Example:
Task A
 

• Initial threshold: 500 units

• Recorded reading: 600 (Task A generated for threshold 500)

• Next threshold: 1000

Task B

• Recorded reading: 8000 (Task B generated for threshold 8000, skipping intermediate thresholds 1000, 1500, …, 11500)

• Last threshold reached: 8000

• Next threshold: 8500

• Recorded reading: 1200 (no task generated because < 8500)

Action: User corrects reading from 8000 (Task B) to 800
 

System interpretation:

• Reading 800 does not trigger any threshold

• Next threshold to reach becomes 1000

• Task B generated for reading 8000 is canceled

• Last recorded reading at 1200 now reaches previously skipped threshold 1000

• Task C is generated for threshold 1000

• Next threshold: 1500
   

Result: Task for threshold 8000 is canceled, and Task C is created for previously skipped threshold 1000

Modifying the initial threshold in the maintenance plan
 

Role: Administrator

It is possible to modify the initial threshold of a maintenance plan based on a measure. This action directly influences the frequency of future generated tasks and the calculation of the next thresholds. The applied logic depends on the state of the plan at the time of modification.

When the initial threshold of a maintenance plan is modified: the next threshold is calculated from the last reading that triggered a task, to ensure the maintenance sequence remains consistent. If no reading has yet triggered a task, the next threshold is simply defined as the first multiple of the new initial threshold greater than zero, and no historical readings trigger retroactive tasks.

No retroactive task is created:

Existing readings, whether above or below the new threshold, do not generate automatic tasks.

Future tasks will only be triggered with new readings reaching or exceeding the next calculated threshold.

Formula:
New next threshold = first multiple of the new initial threshold > last reading that triggered a task

This logic allows for easy adjustment of the maintenance frequency without interference from historical readings, ensuring that future tasks are triggered at exactly the right time.

Here are some cases:

Case 1. No reading has been entered yet for this plan and measure
Initial state:

• Initial threshold: 500

• Existing readings: none

• Last reading that triggered a task: none

• Current next threshold: 500

Action: Modify initial threshold from 500 to 200
Calculation: First multiple of 200 = 200
Expected result: Next threshold = 200
No automatic task created
The first task will only be generated when a new reading ≥ 200 is recorded

Explanation: Since no task has been generated yet, the system simply sets the new threshold for future interventions

Case 2. Existing readings but no task triggered (readings < initial threshold)
 

Initial state:

• Initial threshold: 1000

• Existing readings: 450, 520, 900

• Last reading that triggered a task: none

• Current next threshold: 1000

Action: Modify initial threshold to 200
Calculation: First multiple of 200 = 200
Expected result: Next threshold = 200
No retroactive task created from existing readings

Explanation: Existing readings, whether above or below the new threshold, do not generate automatic tasks. Future tasks are only triggered by new readings ≥ next calculated threshold

Case 3. Task already triggered and existing readings below new threshold

Initial state:

• Initial threshold: 500

• Existing readings: 700, 900, 1200

• Last reading that generated a task: 1200

• Last threshold generating a task: 1000

• Current next threshold: 1500
   

Action:

Modify initial threshold 500 → 300
 

Calculation: 

First multiple of 300 strictly greater than last reading that triggered a task (1200) = 300 × 5 = 1500

Expected result: Next threshold = 1500, then next will be 1800
Future task triggered only when new reading ≥ 1500

Explanation: System recalculates next threshold using last reading that triggered a task as reference, ignoring readings below the new threshold

Case 4. Task already triggered and existing readings above new threshold
 

Initial state:

• Initial threshold: 500

• Existing readings: 1000, 2500, 3100, 3400

• Last reading that generated a task: 3100

• Last threshold generating a task: 3000

• Current next threshold: 3500
   

Action: Modify initial threshold 500 → 50
Calculation: 

First multiple of 50 strictly greater than last reading that triggered a task (3100):
3100 ÷ 50 = 62 → 50 × 62 = 3100 (not strictly greater)
50 × 63 = 3150 (strictly greater than last reading 3100)

Expected result: Next threshold = 3150
No automatic task created from existing readings (even though 3400 > 3150)
Next task triggered only when new reading ≥ 3150

Explanation: System never generates retroactive tasks. It only uses last reading that triggered a task as reference to recalculate next threshold.

This logic ensures all future tasks trigger exactly at the expected moment, without interference from past readings, and simplifies adaptation of maintenance to operational reality.

This feature is currently in BETA, and your feedback will greatly help us improve it and make it even more effective for all users.

If you have any questions, comments, or suggestions, do not hesitate to contact us via the "Help" button available in the application.