Maximo

Maximo

Come for answers, stay for best practices. All we're missing is you.

 View Only

ISO 14224 maintenance time classification, aligned with IBM Maximo.

By David Iñiguez posted Wed April 16, 2025 06:34 PM

  

Maintenance times are often overlooked when managing work orders; keeping track of them is a key part of gathering information for future decision-making.

The various times handled in maintenance usually give us a clear idea of what stage a work order has reached. This allows easy identification of the stage in the work order cycle. This takes us from the creation, planning, scheduling, execution, and closing of the work order. Without times, this would be impossible.

In the ISO 14224 standard in the reliability data feedback scheme we find two important parts of times that are directly inferred: one is Planning and programming from preventive actions and the other is corrective actions through the reporting of maintenance events.

In the figure above we find two important blocks for timing, Operation and Maintenance block; and Failure and Maintenance Events block, we can obtain the following dates:

  1. Creation dates.
  2. Suggested dates.
  3. Scheduled dates.
  4. Actual dates.
  5. Status change dates.

Each of these dates allows us to easily identify what is happening with the work orders and how to gain an advanced understanding to generate subsequent dashboards that provide information for decision-making.

For example, during an audit, you may be asked:

  1. Work orders generated in January 2025.
  2. Work orders scheduled in January 2025.
  3. Work orders executed in January 2025.
  4. Work orders reviewed and closed in January 2025.
  5. Work orders in progress in January 2025.
  6. Work orders and their lead time from execution to closure.

Each of these questions and more are easily identifiable if you have the correct date management and identification. IBM Maximo aligns correctly with each of these requests and you can obtain important information from your maintenance process. In Maximo you will find:

  1. Notification date.
  2. Status change date.
  3. Start date no earlier than.
  4. End date no earlier than.
  5. Suggested start date.
  6. Suggested end date.
  7. Scheduled start date.
  8. Scheduled end date.
  9. Actual start date.
  10. Actual end date.

With all these dates, it is possible to create indicators that really provide you with information for decision-making. If you add to this the ability to create indicators and you are guided by a standard, for example UNE-EN-15341, you will be able to configure many indicators for decision-making.

"Remember, don't forget to pay attention to the dates; what's important must be controlled."

David.

#ibm #ibmmaximo #maximo #iso14224 #visualai #maintenancemanagement #facilitymanagmenet #facilitymaintenance #fleetmaintenance #wrenchtime #wrench #maintenancetimes

4 comments
23 views

Permalink

https://community.ibm.com/community/user/blogs/david-iiguez/2025/04/16/iso-14224-maintenance-time-classification-aligned

Comments

David Iñiguez
Tue April 22, 2025 01:05 AM

You're welcome. There's no fee in this community. If you're an IBM business partner or have access to Siesmic, I invite you to dive into the explicit information. Otherwise, I can look for information there for you.

Craig Kokay
Mon April 21, 2025 09:12 PM

Hi David,

Thanks for the clarity. It sounds like a worthwhile standard, though it seems that the details exist behind a paywall.

David Iñiguez
Mon April 21, 2025 09:00 PM

Hello, for those unfamiliar with indicator standards, you can search the standard I mention in the article. You can start with the ISO standard I mention in the article title, or the more advanced European standard for people who use or are "Maximo experts" but aren't familiar with the UNE-EN-15341 standards, where you'll find more than 100 indicators.

Now, if you're unfamiliar with indicator structures, you can use the indicator matrix by level, through economic, technical, and organizational indicators. Many of the evidential dates don't have to be used, even if they're hidden. You just need to define the necessary ones to ensure they're functionally correct and provide reliable information.

Regarding audit dates, other systems typically only provide simple dates. By using Maximo, you can identify the common error of rescheduling work or changing execution dates, or searching for dates with misconceptions. For example, within the classic rescheduling of orders, which ends up being the typical day-to-day work of every Maximo engineer, you can control scheduling accuracy using the dates I mentioned, which you'll find as an indicator of scheduling accuracy.

Another example is taking the scheduling dates, status changes from material hold to in progress, to identify how long a work order has been on hold for material, thus determining your procurement times. This requires more knowledge of Asset and Maintenance Management, not just Maximo.

Every organization must begin by aligning its organizational objectives and then defining its Asset Management goals. You will then need to define your SAMP (Strategic Asset Management Plan). Finally, you will define how Maximo can support you to establish a baseline. I recommend reading ISO 14224 "Annex E: Key Performance Indicators (KPIs) and Benchmarking." With your existing Maximo date management skills, you will be able to easily identify how to begin a business alignment.

I don't define the steps here; I show users who lack the expertise how to start a simple step. If you're already advanced, that's fantastic! Congratulations! If you'd like, I can share more details or advanced IBM MAS application libraries that you can deploy in your IBM environment and explore how to align standards with the technology solution.

Craig Kokay
Mon April 21, 2025 07:49 PM

Hi David,

Firstly, let's align the date/time fields names to how they are labelled in Maximo, so everyone knows which fields you have mentioned.

  • Notification date = Reported Date
  • Start date no earlier than = Start No Earlier Than
  • End date no earlier than = Finish No Later Than
  • Suggested start date = Target Start Date
  • Suggested end date = Target Finish Date
  • Scheduled start date = Scheduled Start
  • Scheduled end date = Scheduled End
  • Actual start date = Actual Start
  • Actual end date = Actual Finish

There are also more date/time fields that are not displayed, such as Respond By.  I would also include the Duration field and possibly the PM Due Date and PM Extension Date.

Now back to your article.  You mention the ability to create indicators, but have not giving us any idea of where or how or even what these indicators are.

What I can agree with is that measurements do need to be taken, however, in your example audit they generally tell me only the number, but not the quality.  For example, "of the PM work orders raised in January, how many were started within their target dates?"  How about "of the work orders scheduled in January, how many were completed within their scheduled dates?".  "How many work orders that were completed in January had their actual duration exceed their estimated duration".

These questions bring another depth to know you are doing what you said you would do, when you said it would happen, and that we didn't need to move any from their original dates.

Let's take a wild ride using the audit. 

  • 100 work orders were generated in January.  Okay, so what?  What was the source? SR, CM, PM, Investigations, Incidents...
  • 100 work orders were scheduled in January.  Okay, so what?  Of them 10 were from two years ago, 30 from the Christmas backlog, 40 from PMs and the rest CMs.  I can change the schedule in January, but actually schedule them for February, so they comply.
  • 100 work orders were executed in January. So, what? And what does executed mean?  Let's go with reaching the status COMP.  Were they scheduled to the finished in January?

You have to start somewhere.  Please define and set some measures, (normally referred as KPIs), and where possible have these aligned to the business goals.  Should they be expressed as KPIs? Are reports needed and do the reports need to be scheduled?  Do they need to be on the Start Center or a Dashboard or a BI reporting tool?