Equipment maintenance for complex assets
Learn how to effectively plan, schedule and carry out maintenance schedules for complex multi-level assets using asset trees and work order packages.

Learn how to effectively plan, schedule and carry out maintenance schedules for complex multi-level assets using asset trees and work order packages.
Expert Insight
Mike Clements is a senior consultant at FMIS with over 20 years experience in deploying complex asset management and equipment tracking systems around the world.
To contact Mike or any of our consultants, please contact us here.
Tracking and carrying out maintenance programmes for complex assets and equipment requires specialist tools and processes. Mike Clements has implemented complex equipment maintenance systems to track hundreds of thousands of assets around the world. Here he shares his experience to help you manage your equipment more efficiently.
Preventative maintenance schedules are the cornerstone of planned maintenance. Schedules may be meter-based, time-based or driven by some other metric. Automated routines running off these schedules will typically trigger reminders leading to some form of work order to ensure the required maintenance is carried out.
For simple assets, a one-to-one relationship between the work order and the asset is sufficient. For more complex or composite equipment, this single work order per single piece of equipment relationship becomes problematic. When you have composite assets, kits, assemblies, or a tree of assets with many connections, which require constant daily, weekly and other regular checks then that composite asset or asset tree creates a lot of additional complexity.
If we take a vessel-based ROV as an example, then the ROV is not so much a single asset as a collection of linked assets or child assets that make up the parent asset. This type of asset is more accurately described as an asset tree comprised of multiple assets linked together in a series of virtual or actual sub-assets.
In this example, each of these elements is then mapped onto a piece of equipment that can be further broken down into sub-assets, sub-assemblies and individual pieces of equipment. Each piece will have its own maintenance schedules, certificates and spares.
In as little as a week, a complex asset tree can generate tens or even hundreds of separate work orders, each with its own set of checklists, safety checks, meter readings and measurements to be taken at the point of actually completing the work.
In order to handle this level of complexity, it is essential that supporting systems can go beyond stand-alone schedules and work orders to:
Looking at this example, the complexity involved in scheduling planned maintenance is clear. In the real world, even well-planned schedules cannot always anticipate additional variables such as reactive maintenance or shifting project plans. Scheduling maintenance for complex assets is as much about flexibility as it is about being able to aggregate multiple schedules efficiently.
With so many separate inter-dependent elements comprising a complex asset, it is important that you can see the interplay between the various elements comprising the asset tree. An issue with any single component will impact the asset tree as a whole.
In our ROV example, when viewing an asset tree within the FMIS Equipment & Maintenance System, we can see that there are many different levels within a templated asset tree model. Any item that is red would indicate that there is a defunct or missing piece of equipment. We can also see whether the item is tested or not.
In order to complete scheduled work orders efficiently, it is necessary to package the orders into some form of sequence. This may be determined by the asset level within the asset tree and/or by the sequence of the various checklists implied in those work orders generated by the whole asset tree.
Packaging work orders offers many benefits including:
It is common for work orders to have to be carried out in a specific order on complex equipment items. This sequence of tasks, known as a work order package, forms a critical path that jobs need to follow through the complex package of work orders for a composite asset tree.
A work order package for a collection of assets in an asset tree can be for a distinct time period – week, month etc. Within the package, it may be necessary to group work orders (along with any checklists or task lists) into sub-packages that have a distinct route and critical path.
It is important to be able to easily identify these routes within a whole asset tree work order package. It may be necessary to look forward in time to include future six-monthly/annual checks or other maintenance activities into the package while the whole asset tree is already subject to maintenance.
Equipment maintenance systems for organisations that have composite asset trees will need to provide an optimised approach to batching all related work orders into packages that can be sequenced and worked on in a consolidated manner. Coherent packages will reduce complexity and support the navigation of a critical path through your planned maintenance schedule.
For more information on how FMIS Equipment and Maintenance could transform your equipment maintenance programme, please contact us here or call us on +44 (0) 1227 773003.
FMIS Ltd
167b John Wilson Business Park
Whitstable
Kent
CT5 3RA
United Kingdom
Phone:+44 (0) 1227 773003
Fax:+44 (0) 1227 773005
Sales:sales@fmis.co.uk
Support:support@fmis.co.uk
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
CookieLawInfoConsent | 1 year | Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie. |
PHPSESSID | session | This cookie is native to PHP applications. The cookie is used to store and identify a users' unique session ID for the purpose of managing user session on the website. The cookie is a session cookies and is deleted when all the browser windows are closed. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
CONSENT | 2 years | YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data. |
_ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
_gat_UA-48954022-1 | 1 minute | A variation of the _gat cookie set by Google Analytics and Google Tag Manager to allow website owners to track visitor behaviour and measure site performance. The pattern element in the name contains the unique identity number of the account or website it relates to. |
_gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
Cookie | Duration | Description |
---|---|---|
VISITOR_INFO1_LIVE | 5 months 27 days | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. |
YSC | session | YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. |
yt-remote-connected-devices | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt-remote-device-id | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |