Tooling should automate much of the reporting of asset activities and metrics. The repositories typically track
activity-level metrics, meaning the number of retrievals and searches, updates, and so forth. This is useful, but
doesn't address the cost side of assets.
For the business to understand the benefits of assets the activity metrics and the cost metrics need to be brought
together to understand the potential value of the assets. This is typically done in the context of a project, or may be
rolled up to the enterprise.
For example, if the enterprise wants to know the value of using asset X on project Y, the enterprise needs to enforce
the collection of asset consumer experiences in using the assets. This includes capturing information such as "hours to
use the asset", "hours saved using the asset", and then combining that with cost metrics for the resources involved.
Even with this level of capturing metrics and reporting, there is still much that is subjective or
simple estimations, which negatively impacts the quality of the numbers being reported.
|