Asset Templates (Tr)

An Asset Template as the name suggests is a template for an asset. You can generate new assets from the asset template and apply an asset template to existing assets and update those assets from the asset template.

Main tab

The Asset Templates (Tr) application has two additional tabs when compared with the standard Asset Templates application, Warranties and Measurement Points.
Asset Templates (Tr) – Main tab (top)

On first glance of the Asset Templates (Tr) application and when comparing with the standard application you’ll see two additional tabs for Warranties and Measurement Points but there are also several new fields on the main tab.

We’ll start by looking to add a new asset template and populating as many of the fields on the main tab as we can before generating an asset and exploring that asset in the Assets (Tr) application. We’ll then look at some of the other tabs.

The Asset Templates (Tr) application also has a number of additional fields on the main tab. I'm creating a new asset template record, 1001.
Asset Templates (Tr) – Main tab (top) – New record

I’ve created a new asset template 1001 – Transport Asset Test. Asset Templates are defined at the Organization level and the default status is Draft.

I’ve added a value in many of the fields as you can see. Asset Description, Asset Type, Manufacturer, Vendor, Usage, Purchase Price, Replacement Cost, Budgeted, and Priority are all standard fields.

On the Asset Templates (Tr) main tab I've entered values for many of the fields on template 1001. We'll see whether they are copied to an asset.
Asset Templates (Tr) – Main tab (middle) – New record

Scrolling a little vertically, you’ll find that Year, Model, Component, Component Position, Asset Condition, Repair Limit (%), Operator Qualifications, GL Revenue Account, Long Term Assignment Resource and Motor Pool Assignment Resource are Transportation fields and won’t be found in the standard application.

Model and Asset Condition both have a Select Value with no default values, so we’ll later find the domains for this and set up some values and then try updating the assets that we generate.

The Asset Templates (Tr) application is based on the object PLUSCTEMPLATE and there are 24 attributes beginning PLUST, more than the 10 just referenced. We’ll explore that later as well.

Generate New Assets

You use the Generate New Assets action and select the quantity of assets to generate, I will create just one asset in the FLEET site.
Asset Templates (Tr) – Generate Assets (top)

Before you can use the action Generate New Assets you will need to use the action Change Status and change the status to ACTIVE, otherwise you will receive the error BMXAR0176E – You can only apply an asset template while it is in Active status.

When you use the Generate New Assets action the first dialog that opens asks you to select the Site, I chose FLEET.

The Generate New Assets dialog is the same as it is in the standard application except Warranty Start Date and Meter Start Date are additional fields that can be defaulted onto the asset, and there is no Depreciation Start Date.

You will need to specify the Quantity of assets to generate, and you can add a Prefix or Suffix.

After using the Generate Assets button in the dialog the asset data is generated but it has not yet been saved to the database. You can modify the asset records, for example to enter the Serial Number.
Asset Templates (Tr) – Generate Assets (bottom)

After using the Generate Assets action the Assets table shows you the assets that will be created if you use the OK button. This is based on the object PLUSTPREGENASSET which is non-persistent, and which does include the Depreciation Start Date (DEPRSTARTDATE), therefore configuring the field to the Default Asset Table Data section should work. I have raised an IBM Support case for this, it is missing and should be enabled.

I used the OK button and asset 2146 was created in the FLEET site.

After using the OK button the dialog closes. You can check the assets created by using the action View Asset Template Usage.
Asset Templates (Tr) – View Asset Template Usage

You can check that the Asset Template has been applied to the asset through the action View Asset Template Usage.

Let’s take a look at the asset from the Assets (Tr) application.

Assets (Tr) – Main tab

In the Assets (Tr) application and main tab we can check to see whether the data we entered on the Asset Template has been copied to the new asset, 2146.

We will need to scroll vertically down to see all the fields.
Assets (Tr) – Main tab (top) – New asset generated from asset template

In the Assets (Tr) application at the top of the main tab, we can see that the Asset Description, Year, Manufacturer, Asset Type, Purchase Price, Replacement Cost, and Installation Date have all been copied to the new asset.

After scrolling down for asset 2146, there are several other fields which have been populated, all the fields where I had entered values.
Assets (Tr) – Main tab (middle) – New asset generated from asset template

Scrolling vertically a little further down, beneath the reference for the Asset Template (1001) is the Vendor, Component, Component Position, Usage, Priority, Repair Limit (%), and Budgeted Cost, with all values the same as they were on the Asset Template.

The Repair Limit Amount has been calculated from the Repair Limit (%) applied to the Purchase Price. I’ll explore how that amount is used in another article. There are other asset fields on the main tab, for example Position Number is associated with Axle Configurations. There are also 6 other tabs of information at the bottom of the main tab, which we’ll need to introduce one article at a time.

Model and Asset Condition

The Model and Asset Condition fields require setting up the associated ALN Domain with some values.

The Asset Template has now been updated with a value in each of those two fields.
Asset Templates (Tr) – Main tab (middle) – Model and Asset Condition updated

I have now updated the same asset template with a Model, A612-4 and an Asset Condition, NEW, which can both be seen in the left column of the Details section.

The Model is based on an ALN Domain PLUSTASSETMODEL, assigned to the attribute PLUSTMODEL defined as UPPER (10). The number of manufacturer models for all assets using an asset template, may soon become larger than is practical to find in a Select Value which cannot be filtered by manufacturer. This may require some configuration, for example to make it a table domain based on the INVVENDOR records found in Item Master – Vendors tab, or the domain removed so that the field does not have validation. 

For the Condition field I entered the values NEW, GOOD, FAIR, and POOR in the ALN Domain PLUSTCONDITION. This is assigned to a field PLUSTCONDITION which is defined as UPPER (8).

Apply to Existing Assets

When the Asset Template has been updated you can use the Apply to Existing Assets action to apply the changes. You will need to use the Select Assets button to select the assets that you wish to update, often this is by first selecting assets that belong to the asset template.
Asset Templates (Tr) – Apply to Existing Assets – Select Assets

The action Apply to Existing Assets also opens with a dialog to select the Site. The Select Assets dialog allows you to select existing assets whether they already belong to the Asset Template, or not. I have filtered by Asset Template 1001, there is only the one asset 2146 which will be updated, and I have selected this.

After Asset 2146 has been selected, we are ready to execute the update by using the blue OK button.
Asset Templates (Tr) – Apply to Existing Assets

The table details for the selected assets allows you to update the same fields that are seen above in the Default Asset Table Data section. If you are selecting multiple assets and each asset will have the same value, then use the Default Asset Table Data section, otherwise, for Serial # which is different for each asset, use the table details field.

In the Assets (Tr) application, for asset 2146 we can check that the value for Model and Asset Condition has been copied.
Assets (Tr) – Main tab – Model and Asset Condition updated

After using the OK button and navigating to the Assets (Tr) application, for asset 2146 the Model field in the left-hand column and the Asset Condition field in the right-hand column have been updated. The Asset Condition is read-only because there are actions to Change Asset Condition and View Asset Condition History, we’ll discuss those in another article.

There are 24 fields added to the asset template by Maximo Transportation, the attributes all start PLUST. However, half of those fields are to do with Asset Depreciation, which was replaced with Maximo core functionality, the fields can be ignored. Some of the fields in the first list below we will reference in future Maximo Transportation articles.

Old Asset Depreciation fields can be ignored.

There is an object PLUSTTEMPLATE which like the depreciation fields can be ignored, it is an old object.

Warranties Tab

On the Warranties tab in the Asset Templates (Tr) application, I've selected two approved asset warranty contracts at random and associated them with our new asset template 1001.
Asset Templates (Tr) – Warranties tab

The Warranties tab allows you to associate one or more Asset Warranty Contracts. Notice, I’ve used the phrase Asset Warranty Contracts and not Warranty Contracts, i.e. you can only associate records created in the Asset Warranty Contracts (Tr) application and not records created in the Warranty Contracts application.

The Asset Warranty Contracts must be set to APPR state to be associated.

One difference between Asset Warranty Contracts and Warranty Contracts is that Warranty Contracts have revisions, Asset Warranty Contracts do not.

Again I am using the Apply to Existing Assets action and selecting asset 2146 to apply the contract changes.
Asset Templates (Tr) – Apply to Existing Assets

I’ve used the Apply to Existing Assets and selected the asset we used previously, asset 2146 in the Fleet site. The Warranty Start Date will default to today 5th March 2025.

For asset 2146 in the Assets (Tr) application there is a Warranties tab, but the asset warranty contracts have not been copied.
Assets (Tr) – Warranties tab

The Assets (Tr) application has a Warranties tab, and I half expected the warranties from the asset template to be copied here, but they weren’t. When I tried to add the Asset Warranty Contract manually by using the New Row button on the Contracts table, no contracts were displayed. 

The Asset Warranty Contracts I was trying to apply were either beyond the End Date of the contract or were for the BEDFORD site and asset 2146 is a FLEET asset. Hence why neither of the asset warranty contracts were copied. As there are no revisions on Asset Warranty Contracts and I cannot add FLEET as an authorized site, then I’ll create a new contract. 

I've created a new Asset Warranty Contract and approved it. There are no Associated Assets. This time I have made sure that the contract is not expired and that it is authorised for the FLEET site.
Asset Warranty Contracts (Tr) – Associated Assets tab

I’ve created a new Asset Warranty Contract starting at the beginning of the month to the end of June, contract 1072. I’ve used the Authorized Sites action to add both BEDFORD and FLEET sites, and then I changed status to APPR. The Associated Assets tab shows no assets linked to the asset warranty contract.

Back in the Asset Templates (Tr) application I've deleted the previous asset warranty contracts and added the new one, 1072.
Asset Templates (Tr) – Warranties tab – New asset warranty contract selected

I’ve now returned to the Asset Templates (Tr) application, deleted the previous two Asset Warranty Contracts and associated the new contract 1072. I’ve then used the action Apply to Existing Assets and selected asset 2146.

After applying the asset template to asset 2146 the Assets (Tr) application now shows that asset warranty contract 1072 has been applied.
Assets (Tr) – Warranties tab – New asset warranty contract applied

This time the asset was added to the asset warranty contract using the default of today for the Warranty Start Date.

The Contracts table is based on the object WARRANTYASSET, the same data as will be seen on the Asset Warranty Contracts – Associated Assets tab.

In the Asset Warranty Contracts (Tr) application for contract 1072 the Associated Assets tab now shows asset 2146 from the FLEET site.
Asset Warranty Contracts (Tr) – Associated Assets tab is now populated

We can now see the same asset in the Associated Assets tab in the Asset Warranty Contracts (Tr) application. The Assets table is based on the same object WARRANTYASSET.

Meters Tab

In the Meters tab of the Asset Templates (Tr) application there are a few fields which have been added by Maximo Transportation. The Primary Meter checkbox is one of those.
Asset Templates (Tr) – Meters tab (top)

The Asset Templates (Tr) application and Meters tab has a few differences to that which you will see in the core Asset Templates application.

I’ve entered a meter to record the fuel used, the meter is FUEL-G, a CONTINUOUS type meter.

The Primary Meter is a field added by Maximo Transportation. I haven’t explored meter functionality in transportation yet, but I have noticed there is a Primary Meter section on the main tab of Work Order Tracking (Tr), and it looks as if a meter reading for the primary meter can be enforceable on a work order.

Scrolling vertically down to the Continuous Meter Details there are four other Transportation fields, Commodity Code, Item, Capacity and Daily Limit.
Asset Templates (Tr) – Meters tab – Continuous Meter Details

If I scroll vertically down, there are four additional fields:

As you can see, I didn’t enter either a Commodity Code or Item, but I’ll come back to this.

When using the Apply to Existing Assets action the Meter Start Date defaults to today.
Asset Templates (Tr) – Apply to Existing Assets

When using the action Apply to Existing Assets, now that there is a meter, the Meter Start Date is defaulted to today. I will update the same asset 2146 in the FLEET site.

After applying the meter changes, reviewing the meter details for asset 2146 on the Assets (Tr) application and Meters tab, the meter has been created with the same Meter Start Date.
Assets (Tr) – Meters tab (top)

On the Assets (Tr) application, asset 2146 now shows the same meter copied from the asset template.

Scrolling vertically down to the Continuous Meter Details we can see that the Daily Limit and Capacity values have been copied from Asset Template 1001.
Assets (Tr) – Meters tab – Continuous Meter Details

You would need to vertically scroll in the table details of the asset meter to see the Primary Meter, Capacity and Daily Limit all copied from the Asset Template. 

Item and Commodity fields in the second column are both read-only. Meter Serial Number in the first column is also read-only. Hopefully I’ll find out how to update those when I do an article on Asset Meter functionality in Maximo Transportation. 

On the Asset Templates (Tr) application, I've updated the  Meter adding in a Commodity Code. In the test I found that it did not update the existing asset meter when the Apply to Existing Assets action was used.
Asset Templates (Tr) – Meters tab with Commodity Code

I’ve returned to the Asset Templates (Tr) application and entered a Commodity Code for the FUEL-G meter. After using the Apply to Existing Assets action again on asset 2146, it did not update the Commodity field on the asset meter, perhaps because it is now read-only.

The conclusion I came to is that you need to set up the meter on the Asset Template with all the values you need before using either Generate New Assets or Apply to Existing Assets.

Measurement Points Tab

The Measurement Points tab is another addition to the Asset Templates (Tr) application. This looks as if it is a template for creating Condition Monitoring points. I've added values to the warning and action limits, priority and job plan fields.

Again I will use the Apply to Existing Assets action.
Asset Templates (Tr) – Measurement Points tab

There is a Measurement Points tab in the Asset Templates (Tr) application, hopefully this will create Condition Monitoring records as there is no template for creating these records, it is manual entry, or you need to set up Application Import to load the details.

I’ve selected a Meter, PRESSURE, that does not exist on the Asset Template or Asset that I am going to select to update. I’m wondering whether this will work, as Maximo should be attempting to write the Condition Monitoring Point back onto the Asset Meter record.

I’ve entered the Upper/Lower Warning/Action Limits, entered the two priorities and used the same Job Plan reference TIREPRES to be used if a measurement exceeds both the Upper and Lower Limits. 

Support for Characteristic Meters is also available; it is lower down in the Measurement Points tab.

I’ve used the action Apply to Existing Assets and selected asset 2146 to see whether the Measurement Point record has been applied.

In the Assets (Tr) application a Meter record has been created and it references the Condition Monitoring Point 1005.
Assets (Tr) – Meters tab with Gauge meter created

The first thing I’ve done is check the Assets (Tr) application and Meters tab for asset 2146, the PRESSURE meter has been added, which is great. You can see that Measurement Point 1005 has been created.

In the Condition Monitoring application the same limits, priorities and job plan values have been copied from the asset template.
Condition Monitoring – Created from Asset Template

In the Condition Monitoring application, you can find the Measurement Point record created for asset 2146 in the FLEET site. All the limits, priorities and the Job Plan details have been copied.

I noticed that we didn’t give a description for the Measurement Point record, I’ll correct that when I add a Characteristic Meter in the next scenario.

The Asset Templates (Tr) application also supports the creation of Characteristic Measurement Points.
Asset Templates (Tr) – Measurement Points tab – Characteristic meter

You can see that I have now added a description to the PRESSURE Measurement Point and created a second record called Engine Oil Colour which is of CHARACTERISITIC type.

You’ll soon see that there is a Characteristic table window, but you need to enter a record in the Measurement Points table for a Meter Type of Characteristic before being able to enter a record, otherwise you will receive the error – BMXAL0441E – To add a characteristic action value, the measurement point must be associated with a characteristic meter.

Below the Measurement Points table window is a second linked table window for you to enter the Characteristic Action Values.
Asset Templates (Tr) – Measurement Points tab – Characteristic Action Values

Below the Measurement Points table is another linked table called Characteristic Action Values for Measurement Point which is only accessible if you have created a Characteristic Measurement Point and this is your active record.

You can create multiple records for each Characteristic Meter. I’ve entered one so that when the oil colour is DBROWN – Dark Brown a work order can be generated with the PMBFTL Job Plan applied, the work order priority will be 3.

When the Asset Template is applied once again to asset 2146, the new Characteristic meter has been created and can be seen on the Assets (Tr) Meters tab.
Assets (Tr) – Meters tab – Characteristic meter created from Asset Template

When checking asset 2146 in the Assets (Tr) application the Meters tab shows the new meter OILCOLOR has been added with the reference to the Condition Monitoring record, 1006.

The Assets (Tr) application also has a Measurement Points tab, a window onto the Condition Monitoring records created.
Assets (Tr) – Measurement Points tab

The Assets (Tr) application has a Measurement Points tab which is a mostly read-only view onto the Condition Monitoring record for the asset. The Measurement Point Description is the only field which can be updated.

The top record for Point 1006 is for the Characteristic meter just created. Below this, in the linked table window, the Characteristic Action Value entered is DBROWN – Dark Brown.

I am going to create an additional Characteristic Action Value on the same Measurement Point in the Asset Templates (Tr) application and see whether the new record is added. Unfortunately, no new characteristic action value was created. 

When you set up the Measurement Point records in the Asset Templates (Tr) application you need to define them fully, because once the record is created it doesn’t look as if there is functionality to update it.

On the Asset Templates (Tr) application when setting up the Measurement Points you can reference a Master PM instead of a Job Plan. The Master PMs must be referenced first on the PMs tab.
Asset Templates (Tr) – Measurement Points tab referencing Master PMs

You might have noticed that above Upper Limit Job Plan there is Upper Limit Master PM, there is also a Lower Limit Master PM. The Select Value for these fields only uses the Master PMs that you have already referenced on the PMs tab.

At this point no PMs have been created for asset 2146 in FLEET site.

When you use the Apply to Existing Assets action and select an asset where Condition Monitoring Points have already been generated, then you will find these records are not being updated.
Asset Templates (Tr) – Apply to Existing Assets

I am about to use the Apply to Existing Assets action. The dialog allows you to set the PM Start Date, it will be defaulted to today.

After using the OK button, the two PMs for asset 2146 were created at DRAFT state. All the fields from the Master PM including Frequency, Seasonal Dates and Job Plan Sequences seem to have been copied, this is standard functionality from the Asset Template application.

The existing Condition Monitoring record for asset 2146 has not been updated by applying the Asset Template. I’ve concluded that in many cases the Asset Template can be used to generate assets or to initially apply the asset template, but after applying the asset template then not all changes you make on the various tabs will be applied when those records already exist. 

I’ve raised the following IBM Idea – https://ideas.ibm.com/ideas/MASM-I-1363

Asset Templates (Tr) – Measurement Points should have the ability to update existing Condition Monitoring Points when Asset Template is applied a subsequent time after being updated.

I did try creating a new asset by using the Generate New Assets action. In this case it went as far as creating the two PMs, but it failed in creating the associated Condition Monitoring Points with the error – BMXAA2832E – PM 1051 must be an existing non-master PM that references asset 2147.

I received the same error when using the action Apply to Existing Assets and selecting an asset that had no reference to an Asset Template, again two PMs were created, but not the Condition Monitoring points. The issue has been reported to IBM Support. 

If the Master PM is meter-based then you will need to reference the meter on the Meters tab before you can reference a Master PM that references the same meter, otherwise you will receive error – BMXAA2751E – Cannot create PM for asset/location 2149. One or more meters specified in the master PM are not attached to this asset/location. However, it still fails on trying to create the Condition Monitoring Point.

Specifications tab

The Specifications tab on the Asset Templates (Tr) application looks similar to the same tab on the standard Asset Templates application except you will find an Invalid Binding when a Classification is applied with a Specification. This has been reported to IBM Support.

Classifications has a new attribute Date Value that can be found in many of the applications that have a Specifications tab. However, Asset Templates Specifications (PLUSCTPSPEC) is one place where there is no DATEVALUE attribute. It doesn’t make sense to have one, because why would you need a default date value for an asset specification? You would want to be able to enter a date, for example a commissioning date, but it is unlikely you would want a default for it, and less likely you would want the same default on the Asset Template.

If you want, the field with the Invalid Binding can be easily removed from the application. It is likely that the result of the IBM Support case will be to do just this.

A good feature of Classifications which should be considered for Asset Templates is to generate the asset description by using the Classifications Description Generation feature.

Assets (Tr) – View Asset Template History

The Assets (Tr) application has an action View Asset Template History that shows you how often an asset template has been applied to the asset.
Assets (Tr) – View Asset Template History

The Assets (Tr) application has an action View Asset Template History. As you can see Asset Template 1001 was applied to asset 2146 several times over the course of writing this article.