Hi @b.stephenson,
I second this request. Typically when performing a Business Impact Analysis (BIA), I try to work my way from highest to lowest, understanding RPO/RTO/MTO of each as we go. Then we can analyze to ensure the RPO/RTO/MTO of the software meets the business process needs, and in turn needs of the overall business unit (and ensure we don’t have any gaps/risks).
So, my way of thinking is that we start with a business unit, which maps to a business process, which then maps to a specific tool/technology/vendor/supplier/etc. Then, we can use visualizations to look at these interdependencies in numerous different ways.
Hope that makes sense. Thanks!
-Noah