Smart Report

Capturing effort for Smart Report

The custom attribute of an asset is defined with quantifiable value, that is termed as estimated value in units, expended during first time asset creation. For example: Assume a custom attribute to capture number of Hours spent on creating an asset. When you reuse such assets, you can volunteer to capture a value, termed as actual value, against estimated value defined in each of its custom attribute. The smart report engine utilizes these two values, estimated and actual, as key inputs to calculate and derive metrics to generate a Smart report.

In the smart report, these metrics are plotted in a graphical presentation to differentiate overall profit secured by an organization after effective reuse of assets by users.

The smart report can provide insights into the computed effort metrics of all the assets at three levels from a higher level of community to the lowest Asset level as follows:

• Community-level report - A community-level graph that depicts overall metrics captured by different users reusing assets across communities.
• Asset Type-level report - An Asset type-level graph is categorized into estimated and actual metrics captured on reusing assets available under specific asset types. In addition to efforts analysis, this report will also help you to analyze the asset type that is extensively reused.
• Asset-level report - An asset-level graph illustrating expected and actual metrics captured by a user reusing specific assets.

It is important to understand efforts statistics by analyzing cumulative efforts spent on asset utilization at all levels from first time asset submission to reuse by different users in an asset life cycle. This analysis helps you to evaluate the estimated and actual values saved on reusing an asset. Depending on the custom attributes type, the asset efforts are respective units.

The following example helps you understand an end-to-end process of capturing efforts in hours spent on asset creation and thereafter its reuse.

For example: User-1 creating Asset-A claims to save an Estimated Effort of 5 hours, while User-2 user reusing Asset-A may have observed to save 3 hours and update the Actual Effort as 3 hours. Similarly, User-3 and User-4 reusing Asset-A may have saved 2 hours and 4 hours of Actual Effort, respectively.

In the smart report for Asset-A, the analytics engine computes the cumulative Estimated Effort as 15 hours and Actual Effort saved as 9 hours.