I agree with Abid Ali.
I use it to find all of the Objects that are related to the Service of the Main Object that I am working with at any particular time. As also mentioned, this can help in better understanding the relationships when dealing with integration, MIF, Mobile Applications, or even populating/loading data into Maximo via various avenues. Much like the Relationship Tab of the Object maps out how Attributes are linked together, the "Service" property can map out how all the Objects are linked together as well. And once they are together in your List, you can navigate through each Object to review its design, such as whether or not each Object is Persistent or not.
Being able to find all the Objects tied to the Service can also help System Administrators to understand all the Objects that might be populated when dealing with the various "front-end" Transactions of the Users. Being able to get to "ALL" the data of say a particular Work Order can help to understand why something didn't work properly or what happened to this record and when it happened. Unfortunately, sometimes it's just bad data that's responsible, and not all of it is displayed in the Maximo Application.
To me it's just one more way to ensure that you don't miss any piece of the puzzle, especially as more and more functionality is added to Maximo. In the past, I believe there were maybe eight (8) Objects tied to the JOBPLAN Service (and it was easy to remember them all) and now there are over 25...and 1200+ Objects. At some point, it could be important to know what happened with all 25 of those Objects when I clicked "Save" or performed some other action on the Record; or how those 1200+ Objects interact with each other.
------------------------------
Steve Platt
Georgia Building Authority
404-915-3391
------------------------------