An enterprise asset is a technical resource that can be used across business units and/or across applications. This definition includes assets such as Web services, shared components, systems, interfaces, data definition and schemas. The idea is that an enterprise repository should contain any asset regardless of type. That being said, most organizations have a collection of repositories to fulfill the service of metadata delivery. One common theme is that if you don't share the asset, then why would you catalog it? What would you do if a business unit approached your metadata organization with a truckload of data assets but wanted to lock access down so that no one could access the information? Worse yet, these data assets are not enterprise level and can't be shared with other business units.

Personally, I have always tried to look at metadata as a business, and just like all businesses, there are costs associated with bringing data into the repository. You have to spend resources on data analysis, data transformations and data quality, not to mention the additional layers of complexity that more information brings to any knowledge store. Keep in mind, this is not a one-time expense. Each and every month, you will allocate a percentage of your efforts on the current portfolio. This may include general maintenance, reporting, data aging and quality inspections, all of which take time and effort. Based on this, you may only want the highest-valued assets in your collection, not just the greatest number.

Register or login for access to this item and much more

All Information Management content is archived after seven days.

Community members receive:
  • All recent and archived articles
  • Conference offers and updates
  • A full menu of enewsletter options
  • Web seminars, white papers, ebooks

Don't have an account? Register for Free Unlimited Access