IBM Support

From the Maximo Support Desk - ACM Technical Record Creates Asset But No Work Order

Technical Blog Post


Abstract

From the Maximo Support Desk - ACM Technical Record Creates Asset But No Work Order

Body

Maximo clients have reported that in some scenarios, that the ACM Technical Record does not create the expected PM Work Order.  It is observed that the corresponding

Asset gets created only.

The most likely reason for this condition is that the values of the Effective Date and Comply By Date fields are the same on the Maintenance Plan of the Technical Record.

If the Effective Date value is the same as the Comply By Date value, then this causes the Frequency Date on the resulting PM to be set to 0.  These values must be different.

image

 

The application uses the difference in time between these two dates to determine the frequency of the PM that is created for the applicable assets.  If the two dates are the same, the PM Frequency will be set to zero. This creates the scenario whereby the PM will have no defined Frequency, and the result is that a "no event" record gets created (PLUSALFEVENT).  These are the records visible on the Maintenance Plan tab of the Assets(CM) application.

The summary is that you need to ensure that the Effective Date is at least one day earlier than the Comply By Date so that this process will work as expected.
 

Additional Notes on Asset Configuration Manager 7.6.4.x Feature Pack:

It's significant to note that a number of enhancements were added to the Technical Records application in ACM 7.6.4 in order to accommodate an increased range of scenarios when defining when the work needs to be carried out by (via the information on the Maintenance Plan defined on the Tech Record).  These enhancements include a new field, "Reference Date".  This can be set to the "Effective Date" value of the Technical Record or to the "Date of Manufacture", or to the "Date of Receipt"(of the Asset).

Additionally, the new "Calendar Unit" and "Calendar Interval" fields allow greater flexibility in defining when the work should be carried out by.  For example, you can set the Reference Date to the "Date of Manufacture"(of the Asset), and set the Calendar Interval / Calendar Unit to 3 YEARS; this would mean that the "Comply By Date" for each individual asset is determined by their own respective Dates of Manufacture - this was not possible in previous versions.

This also applies to requirements where the deadline for the work is based on a meter value (and now up to 3 meter values can be defined on the maintenance plan).  The advantage of this is that the creation of the Frequency on the PM and the associated Active Date on the Maintenance Plan event record is driven by this new way of defining the frequency information on the maintenance plan.

Unfortunately the scenario described at the top of this article was not anticipated - where the Effective Date and Comply By Date were set to the same values (such as on a client's existing data).  For the situation where your existing data may have created this condition, the recommendation would be to update the existing TR Maintenance Plan (PLUSATREVENT) records to set the Effective Date to 1 day less than the Comply By Date value.

 


Tom Richardson is an IBM Maximo Support Engineer and frequent contributor to the Asset Management Blog community.  For a complete index of links to his articles, visit
Index of articles by Tom Richardson, Support Engineer
 

[{"Business Unit":{"code":"BU005","label":"IoT"}, "Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":""}]

UID

ibm11112061