Asset Relationships

Maximo Bite Size
Maximo Bite Size
Asset Relationships

Good afternoon and welcome to Maximo Bite Size, a podcast on the functionality of Maximo Manage. Today is the fourteenth and last episode in the series on Asset Management and we will be discussing Asset Relationships.

Of all the aspects of Locations and Assets, then Asset Relationships may be the least likely to be used unless you are also using Maximo Linear where it is important.


The Relationships application defines a set of nouns that describe a relationship between two assets or an asset and a location. The type is BIDIRECTIONAL or UNIDIRECTIONAL. For example, A connects B is bidirectional because it can be read in the opposite direction as B connects A. In this example the relationship is ‘CONNECTS’.

There is a hidden attribute COMPRELATION – Complementary Relationship, which can be used to pair two UNIDIRECTIONAL relationships, if you add the complementary relationship on one of the relationships records it will be added to the other record.

The Classification field serves no purpose other than to define a type of relationship. There is no corresponding specification. The Use With field would be set to ASSET. The other option is CI – a Configuration Item, and this is the default for new records, you may want to change this. Configuration Items are used in IT environments for something which is under configuration control. In the Maximo world it could be a document.

The Allow Override is used if you enter Asset Relationship Rules. This defines the types of assets that can be related to other types of assets, the type of asset is defined by a classification. For example, you could say that a relationship can be used with a particular source classification and a particular target classification. For example, a relationship of INTERSECTS is only used between two assets each with a classification of ROAD.

The validation rules can be extended down to include conditions on attribute values of the source or target in the relationship. This will validate that the attribute in the source or target specification has a value which you specify and a condition like is equal to, greater than, greater than or equal to, etc. There are buttons to create a group of conditions, or a new line item in the condition, and a qualifier for how lines are combined, an AND or OR. The relationship between groups of rules is always an OR. When the validation rules are defined and used on an asset you may receive an error message like “BMXAA8016E – The rule validation for the relationship failed. Rule conditions must be met for the relationship to be established.”

If you use the Allow Override attribute on a relationship then instead of an error you will receive a warning with Yes/No buttons, for example, “BMXAA8021W – The relationship rule validations failed. Do you want to override the validation rules for this relationship and allow the relationship to be created?”

Relationships are defined at the System level.

Asset Relationships

Asset Relationships are added in the Assets application and Relationships tab. Asset Relationships are also defined at the System level, but there is only one SiteID and OrgID, therefore it is expecting both the source and target to be in the same site. That site should be the site where the current asset record resides.

You are adding a relationship between a source and a target. There are two pairs of fields. Source Asset or Source Location, only one of these can be used. Target Asset or Target Location, again only one of these can be used. The current asset must be either the source asset or the target asset otherwise you will receive an error message. Therefore, while you may think you can add a relationship between a source location and a target location, you can’t, the error message will be displayed.

When creating an asset relationship record, think whether the current asset is the source or the target in the relationship you wish to use and add the asset into the appropriate field. Now go to the other end of the relationship and enter an asset or location. Of course, it is always easiest to enter this as you would write it starting with the source asset or location, but if this is not the current asset then the current asset must be entered as the target asset.

The sequence number allows you to enter multiple relationships and display them in a logical order. The Use As Reference field would only be used with Linear Assets, and if you are not using Linear Assets then this field can be hidden.

Above the Relationships table window is a field that allows you to filter the relationships according to whether the current asset is the Source, Target, or the View All option allows you to see both.

I hope you enjoyed this podcast episode and I look forward to seeing you in the next series when we will review Maintenance Planning, starting with People and Person Groups.

The music is called Busy City from the group called TrackTribe, please check them out on TrackTribe.Com, all one word.

Until another time, goodbye.

Leave a Reply

%d bloggers like this: