- Have minimum of number of connection. Only necessary connection that requires to build the dashboard should be there remove rest of the connection which you would have for testing purpose.
- Try to have aggregation and complex calculation on the database side only. Means try to bring minimal dataset possible since the dashboard is for showing the KPIs, key figure, metrics.so bringing only calculated values to dashboard design can save lots of processing time.
- Remove extra component from the dashboard. Try to keep them as of need basis.
- Creating multiple layer of visual component and showing that on conditions will complex the design and could slow the dashboard. Approach for Tab based dashboard. Which would be simplified one. Again the use consent is on the priority.
- Reduce the number of excel formula used. Keep the excel sheets as per need basis. Delete the dummy data.
- Always keep a tab on when to refresh the data connection. Unnecessarily refreshing data could really hamper the performance of the dashboard.
- Support platform guidelines is mentioned in the installation guide but it does not clearly states about the hardware requirements in case of complex dahsboards.so taking this point depending on your complexity of the system and dashboard once should consider the hardware requirement.
- To provide detail drill down you can link it to a Webi or Crystal report. That can also help different drill and prompt option. Try to have only summarized information on the dashboard.
Thursday, 19 September 2013
Xcelsius Dashboard Best Practice
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment