Hi Vinod,
Excellent question!
You're right. Not all Assets on the DX have DIY hours associated with them. Let me explain.
First, you need to understand how we calculate DIY Hours. We do this using a code analyzing Digital Worker called Demming. Demming goes through the Assets in the DX and locates the downloadable .bprelease files for each Asset that has one. Demming examines the processes, objects, WebAPI, code stages, and other components in the .bprelease file and calculates a code complexity. We've taught Demming how to map code complexity to the Level of Effort reconstruct that complexity to develop DIY Hours.
Now that you understand how we do it let's look at why we can't do it for all Assets.
First, it might be that the Asset is new or updated, and Demming has not yet run against that Asset.
Second, Demming can only calculate DIY hours for downloads that come from the Digital Exchange. Thus, if the Asset is from a TAP partner and the software is available from the partner, then Demming can't do the calculations for DIY Hours.
Third, the download might be an executable or some other file format that Demming does not understand.
Does that answer your question?
By the way, if you see an Asset on the DX that you think should have DIY Hours associated with it, but it does not, let us know on this forum, and we'll look into it and get a specific answer to you.
Thanks for the questions.
------------------------------
Paul Nerger
VP Digital Exchange
Blue Prism
America/Los_Angeles
------------------------------
