Maintenance+ helps teams do more than complete maintenance work.
When maintenance is captured consistently, every work order becomes part of a bigger picture. It helps your team understand asset condition, maintenance effort, recurring issues, operational status and compliance history.
This is what we mean by maintenance intelligence.
What is maintenance intelligence?
Maintenance intelligence is the insight created when maintenance activity is recorded in a structured way.
A completed work order tells you what happened.
A completed work order with priority, estimated hours, actual hours, fault codes and lifecycle status tells you much more.
It can help answer questions such as:
What work was completed?
What work is still open?
Which maintenance tasks are urgent?
Which tasks take longer than expected?
Which assets have recurring faults?
Which assets are operating, non-operating or decommissioned?
Which assets are still in the yard but no longer in service?
Can we prove an asset has been decommissioned?
Are our maintenance plans still fit for purpose?
Maintenance intelligence helps teams move from simply recording maintenance to learning from maintenance.
Why configuration matters
The value of Maintenance+ grows when the right information is captured from the beginning.
If tasks are completed without priority, hours, fault codes or lifecycle context, your team may still know that maintenance was completed.
But it becomes harder to understand patterns, compare effort, report on asset status or provide evidence later.
Good configuration helps your team capture useful information consistently.
This includes:
Priorities
Estimated hours
Actual hours
Fault codes
Lifecycle status
Maintenance history
When this information is recorded consistently, it becomes easier to report on maintenance activity and make better decisions.
Priorities: understanding urgency
Priority helps your team classify how urgent or important maintenance work is.
Aquipa includes default priority items:
Critical
High
Medium
Low
Unknown
Priorities help teams focus on the work that matters most.
For example, a Critical task may need immediate attention, while a Low priority task may be routine or less urgent.
Priorities can help Maintenance Managers understand:
Which work needs immediate attention
Which work is routine
How much maintenance activity is critical, high, medium or low priority
Whether urgent work is being resolved in time
Where resources should be focused first
Priorities can also be configured in the Configuration Panel under the Maintenance module. Custom priorities can include a rank, label, description and action required.
Priority can also be made mandatory when creating tasks and task templates. This helps ensure maintenance work is classified consistently from the start.
Estimated hours vs actual hours: understanding effort
Estimated hours show how long a task or work order is expected to take.
Actual hours show how long the work really took.
Comparing estimated hours with actual hours helps Maintenance Managers understand whether maintenance planning is accurate.
This can help answer questions such as:
Are our maintenance estimates realistic?
Which tasks regularly take longer than expected?
Which assets require more maintenance effort?
Are we allowing enough time for planned maintenance?
Do we need to adjust future scheduling?
Do we need different skills or resources for certain task types?
This helps teams improve planning over time.
Instead of only knowing that work was completed, you can also understand how much effort it required.
Fault codes: understanding recurring issues
Fault codes help standardise how maintenance issues are recorded.
Fault codes are configured in:
Configuration Panel > Maintenance > Fault Library
When creating a fault, you give it:
Code
Label
Description
These fault codes can then be assigned to maintenance tasks so issues can be tracked consistently.
This is useful because free-text descriptions can vary between users. One person may write “hydraulic leak”, another may write “oil leak”, and another may write “hose leaking”.
A fault code gives the team a consistent way to classify the issue.
Over time, fault codes can help Maintenance Managers identify:
Which fault types occur most often
Which assets have recurring issues
Which issues create the most maintenance work
Which faults should trigger preventative action
Which maintenance plans may need to be reviewed
Which issues are isolated events versus recurring trends
Fault codes help turn individual maintenance tasks into useful reporting data.
Lifecycle status: understanding asset state
Lifecycle status helps your team understand and report on the operational state of an asset.
In Aquipa, lifecycle status can be used to categorise assets based on where they sit in their operational lifecycle.
The main lifecycle statuses are:
Operating
Non-Operating
Decommissioned
Lifecycle status is useful because maintenance teams need to know whether assets are active, inactive or permanently removed from operation.
It also gives teams a way to report on assets by operational state.
Reporting on Operating assets
An Operating asset is active and eligible for use.
Reporting on Operating assets can help teams understand:
Which assets are active
Which active assets have maintenance plans
Which active assets have open work orders
Which active assets have overdue maintenance
Which assets are available for work
For Operating assets, teams may need to ensure the correct maintenance plans are configured and current maintenance work is being managed.
Reporting on Non-Operating assets
A Non-Operating asset is inactive or not currently functioning.
This status is useful when an asset is temporarily out of service but still needs to be managed.
Reporting on Non-Operating assets can help teams understand:
Which assets are inactive
Why assets may not be available for work
Whether maintenance is required before they return to service
Which assets may need attention before becoming operational again
Which assets should not trigger unnecessary maintenance activity
This helps teams manage inactive assets without losing visibility of them.
Decommissioned assets as audit evidence
A Decommissioned asset has been permanently removed from operation.
The Decommissioned lifecycle status is especially valuable from an audit and compliance perspective.
An asset may still be physically present in a yard, depot or storage location, even though it is no longer active or available for use.
During an audit or review, someone may ask:
“Why is this asset in the yard, and is it still in service?”
If the asset has been marked as Decommissioned in Aquipa, the business has a clear record showing that the asset is no longer operational.
This helps provide evidence that:
The asset has been removed from operational use
The asset is not part of the active fleet
The asset should not be treated as available for work
The asset has a lifecycle record showing its current status
Historical maintenance and compliance records are still retained
The asset’s status can be explained during an audit or review
Decommissioned status is not just a label. It is useful evidence that an asset has been formally removed from operation while still retaining its historical record.
Maintenance history: understanding what happened over time
When work orders are completed and closed, they become part of the asset’s maintenance history.
This history helps teams understand:
What maintenance was completed
When it was completed
Who completed the work
What checklist results were recorded
What comments or evidence were added
Whether any issues were found
Which fault codes were assigned
What priority was recorded
How long the work was expected to take
How long the work actually took
Over time, this creates a clearer picture of how an asset has been maintained.
How maintenance intelligence helps Managers
Maintenance intelligence helps Maintenance Managers make better decisions.
It can support:
Maintenance planning
Resource allocation
Risk management
Audit preparation
Asset reporting
Compliance reviews
Preventative maintenance improvement
Identification of recurring issues
Better scheduling and forecasting
Instead of relying on memory, disconnected spreadsheets or inconsistent notes, Managers can use structured maintenance records to understand what is happening across their assets.
How Technicians contribute to maintenance intelligence
Technicians play an important role in creating useful maintenance intelligence.
The information recorded during task completion helps build the maintenance record.
Technicians support better reporting by:
Completing checklist items accurately
Adding useful comments
Uploading supporting evidence where required
Recording actual hours where required
Applying fault codes where required
Submitting tasks for review
Good task completion helps Managers understand what happened and make better decisions later.
Simple example
A Technician completes a hydraulic inspection task.
They record that the task took 2.5 actual hours, select a hydraulic fault code, add a comment explaining the issue and submit the task for review.
The Maintenance Manager can now see:
The task was completed
How long it took
What type of fault was found
Which asset the fault relates to
Whether similar faults have occurred before
Whether the maintenance plan may need to be reviewed
This is maintenance intelligence in action.
Summary
Maintenance+ helps teams manage work orders, but the real value grows when each work order captures useful information that can be reported on, reviewed and used to improve maintenance decisions over time.