Scheme and wireframes for reporting Phys Risk evaluation results to users, at a Portfolio and Asset-level

[NickKellett]

When Phys Risk users evaluate their asset portfolios against certain vulnerability model(s), the result needs to be presented to them and incorporated in their business decision-making and workflows. When used in a web application, this phys risk output format may vary from a CSV file to a resource link, to a pointer on a map.

The sandbox currently displays a prototypical output but it would be beneficial to advance this work to determine:

1. Do different hazards and/or scenarios produce different output types?
2. Are there standard reporting fields we can follow
3. What information is displayed at the portfolio level vs individual asset level
4. What formats are displayed - ex. a traffic light, a number, a graph/vulnerability curve, a textual explanation of the underlying model and uncertainty, etc
5. Are technical vs non-technical users viewing the same output? If not, why not?
6. What elements can be standardized across different use cases? What elements are always application specific?

I anticipate this issue will lead to a set of wireframes and/or data set that can later be incorporated into a web application like the Phys Risk Sandbox.

@joemoorhouse @jmcano-arfima @jtoroafs