The pevious post on this blog was called A Master Data Mind Map. In there I tried to map some different examples of master data entities within some known master data domains as party, product, location, financial and calendar.
In the comments and in a following twitter conversation, the placement of the asset entity was questioned.
Prash Chan (@MDMGeek) said: “There is another type of asset I came across once, mapped to location domain, largely because the assets were identified by the place where they were installed.”
Jamie Watters (@jamietwatters) said: “Don’t disagree, but think there are other areas of asset data that makes it unique instead of using product or location. Areas such as engineering, design, construction, maintenance, commissionin make managing asset data pretty unique.”
Indeed, I am actually also on the fence here.
There are certainly often strong relations to a location for an asset. But that is also true for parties as well and some products too as told in the post Product Placement.
Assets can be many things. Gartner (the analyst firm) has the concept of the things domain encompassing products and assets.
Asset may in fact just be its own domain. Property too perhaps as the Real Estate Domain. Services could claim independence from the other products someday. Customer is today often seen as its own domain not belonging to party as examined in the post MDM for Customer Data Quadrant…
Andrew White of Gartner did address these naming issues in a blog post back in 2009 here.