1. Executive Dashboard Systems Secure CITI Adam Zagorecki April 30, 2004

2. Overview Executive dashboard – overview Executive dashboard – overview Executive dashboards in practice Executive dashboards in practice Designing ED: objectives, limitations and compromises Designing ED: objectives, limitations and compromises Technical considerations Technical considerations ED for emergency management ED for emergency management Conclusions Conclusions

3. Problem Statement Investigation of the application of the concept of executive dashboards in context of emergency management. Critical literature review Critical literature review Provide a set of guidelines for application of the ED for emergency management Provide a set of guidelines for application of the ED for emergency management Use of automated methods for performance monitoring Use of automated methods for performance monitoring

4. Dashboard Systems Started around 1985, they are currently considered as a hot topic in business intelligence (new name for decision-support systems). Started around 1985, they are currently considered as a hot topic in business intelligence (new name for decision-support systems). Started as a business application – a display on the executive desk that shows how the business is performing. It was not an optimal solution. Started as a business application – a display on the executive desk that shows how the business is performing. It was not an optimal solution. They become managerial dashboards, similar concept, which serves multiple decision makers. Example: Southwest Airlines. They become managerial dashboards, similar concept, which serves multiple decision makers. Example: Southwest Airlines.

5. Goals of Executive Dashboard There are 3 goals that the ED should address: There are 3 goals that the ED should address: “Answer fundamental questions about the system or organizational unit” – e.g. status of resources, etc. Key Performance Indicators (KPIs). “Answer fundamental questions about the system or organizational unit” – e.g. status of resources, etc. Key Performance Indicators (KPIs). Alert managers to problems. Alert managers to problems. Help to make decisions that impact the complex systems. Help to make decisions that impact the complex systems.

6. Key Performance Indicators Idea: usually one screen summary that shows Key Performance Indicators. Idea: usually one screen summary that shows Key Performance Indicators. KPIs are benchmarks strictly tied to the nature of the system, always user specific. KPIs are benchmarks strictly tied to the nature of the system, always user specific. KPIs are usually simple measures that are delivered directly from a database. KPIs are usually simple measures that are delivered directly from a database. Selection of KPIs is the basis of success or failure of the ED. Selection of KPIs is the basis of success or failure of the ED. GOAL: to reduce information load and focus attention on the emerging problems.

8. Design: Visualization Experience shows that low end visualizations (charts, maps, histograms) are more adequate than more advanced displays. Experience shows that low end visualizations (charts, maps, histograms) are more adequate than more advanced displays. The main purpose is to deliver information in a quick and easy to comprehend manner. The main purpose is to deliver information in a quick and easy to comprehend manner. The use of web browsers is highly recommended, because users are familiar with them and they lower implementation costs. The use of web browsers is highly recommended, because users are familiar with them and they lower implementation costs.

9. Technology used The design assumes existence of a central data warehouse, therefore a problem with multiple sources is assumed to be non-existent. The design assumes existence of a central data warehouse, therefore a problem with multiple sources is assumed to be non-existent. All necessary number crunching is assumed to be done by data warehouse software. All necessary number crunching is assumed to be done by data warehouse software. Alert levels are simple thresholds that are defined by user (customizable) Alert levels are simple thresholds that are defined by user (customizable)

10. Typical Design (business) Organization (business) Data Warehouse Executive Dashboar d KPIs

11. Executive Dashboards and Public Management

12. Multi-organizational effort Executive dashboards were developed for profit oriented organizations with clearly defined objectives. Executive dashboards were developed for profit oriented organizations with clearly defined objectives. The executive dashboard is an example of a STS, therefore most problems identified for STS are true for ED, in particular: The executive dashboard is an example of a STS, therefore most problems identified for STS are true for ED, in particular: getting all major actors involved in the enterprise, resolution of conflicts among actors’ expectations getting all major actors involved in the enterprise, resolution of conflicts among actors’ expectations lack of interest or resistance from some of the actors lack of interest or resistance from some of the actors who will pay? who will pay?

13. Data Sources From technical perspective important difficulties arise from the lack of a central data warehouse: From technical perspective important difficulties arise from the lack of a central data warehouse: need for defining data exchange protocols between different organizations need for defining data exchange protocols between different organizations implementation of secure communication between multiple intranets implementation of secure communication between multiple intranets

14. Design suggestions Identify Key Performance Indicators should be the first step in the design process Identify Key Performance Indicators should be the first step in the design process KPIs should be identified by practicing emergency managers who will be users of the system KPIs should be identified by practicing emergency managers who will be users of the system What information can be available to the system? What information can be available to the system? System should be used on daily basis by emergency managers and all actors involved in crisis management. System should be used on daily basis by emergency managers and all actors involved in crisis management.

15. Design suggestions Data quality in the system should be positively correlated with the automatization (level of intelligence) of the system. Data quality in the system should be positively correlated with the automatization (level of intelligence) of the system. Data quality should determine the degree of technical complexity of the system. Data quality should determine the degree of technical complexity of the system.

16. Conclusions Executive dashboards were originally developed for business organizations, and implementation is still not mature. Executive dashboards were originally developed for business organizations, and implementation is still not mature. Executive dashboards vs. managerial dashboards. Executive dashboards vs. managerial dashboards. Executive dashboard is never a “product” – requires customization for every customer. Executive dashboard is never a “product” – requires customization for every customer. KPIs are based on experts’ knowledge. KPIs are based on experts’ knowledge.

17. Emergency management Key difference between business settings and public management is the number of different organizations involved in using ED: Key difference between business settings and public management is the number of different organizations involved in using ED: no single data warehouse (technical problems, costs) no single data warehouse (technical problems, costs) often contradictory objectives (social difficulties) often contradictory objectives (social difficulties) limitations on free communication (technical, legal issues) limitations on free communication (technical, legal issues)

18. Thank you