Maximo Open Forum

Hello all, we do not have Service Provider, and probably won't be getting it, but I am looking for a better way to track our customers in Maximo.  One way is to create a custom Company Type of "Customer" for the Company Master application in the COMPTYPE domain.  

Is there any reason an expert might say this is a bad solution?  

My thought is that then I can use a custom field in the Asset's application to add records from the Companies application as the customer, either if they are the owner of the asset or if they are the only customer of the product produced by that asset.  

#Administration
#Assets
#Customizations
#EndUser
#EverythingMaximo
#ServiceProvider

------------------------------
Danny Richardson
Maximo Administrator Manager
Technimark LLC
------------------------------

I'd think it depends on what you want to do with it.  You've stated what you want to do; I'm kind of interested in why you want to. 

If it's more work order related, I'd add them as People (with customizations as needed).  This way, they could be referenced on Service Requests and Work Orders as the Reported By.  If it's more supply chain related, and/or you want to list out the Contact Info for one or more people who work at that company, then add these to the Company table.  If you need both/hybrid, I'd bet you could write a script to automatically add a Person record if you add a Company record having the condition Type=Customer.

------------------------------
Travis Herron
Pensacola Christian College
------------------------------

Expanding on Travis's question, Service Provider enables end users from that vendor to access the system and see only their assets, work orders, etc. It supports different SLA calculations for different customers. It supports customer billing. It supports the concept of customer hierarchies. It provides a lot of additional features that you may or may not need in your use case.

If this is for your own team to track who the equipment is for without impacting other flows like billing, end user access, etc. then I would agree Service Provider is overkill and companies should work fine. 

------------------------------
Steven Shull
Naviam
------------------------------

Mmmm, coffee finally kicked in...

"if they are the owner of the asset" -- definitely more of a Field Service Management idea than EAM; so Service Provider is probably the intended way to handle that.

Beyond that, could you make use of Asset's "Associate Users and Custodians" functionality? (If so, you'd need to add these as Person records.)

------------------------------
Travis Herron
Pensacola Christian College
------------------------------

Original Message:
Sent: 02-27-2026 09:24
From: Steven Shull
Subject: Discussion: Customer as Company Type in Company Master

Expanding on Travis's question, Service Provider enables end users from that vendor to access the system and see only their assets, work orders, etc. It supports different SLA calculations for different customers. It supports customer billing. It supports the concept of customer hierarchies. It provides a lot of additional features that you may or may not need in your use case.

If this is for your own team to track who the equipment is for without impacting other flows like billing, end user access, etc. then I would agree Service Provider is overkill and companies should work fine. 

------------------------------
Steven Shull
Naviam
------------------------------