Date: Fri, 29 Mar 2024 07:42:26 +0000 (UTC)
Message-ID: <1309845246.4045.1711698146518@skald.opmantek.com>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_4044_1344920425.1711698146517"
------=_Part_4044_1344920425.1711698146517
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
Dashboard Design Considerations
Dashboard Design Considerations
Dashboard Design Considerations
While you can add as many components as you desire to an individual Dash=
board we highly recommend you adhere to the following design recommendation=
s:
- Limit the number and overall size of each component so that the user ca=
n see the entire Dashboard without needing to scroll either horizontally or=
vertically
- Top-level dashboards should make use of high-level KPI metrics, grouped=
data and device statistics and allow the user to "drill down" from this 50=
,000 ft view into more detailed levels of information
- The components used on a dashboard should be directly related to the ac=
tivities and questions the user will have. Avoid including superfluous, or =
"good to have" information, as this will become distracting and reduce the =
overall usability of the dashboard
- While you can stack multiple data points in an individual opCharts Char=
t, it is often best to limit the overall number of data points, type of dat=
a, and data ranges. This will improve the overall readability of the chart,=
as well as make the intention of the data more readily apparent to the ope=
rator.
------=_Part_4044_1344920425.1711698146517--