When users first login, they will be greeted with Operations module where the main KPI dashboards live.
On the far left, there is a menu that allows users to navigate through different modules and their sub items.
Please note: you may not see all of the options as shown, as it is dependent upon your individual access. If you see something you need, please contact your organization administrator.
Clicking on one of the items will take you to the respective module. This will be the key tool for navigating through the different modules at a click of a button. To access the other the submenus, click on the small arrow to see the items relevant to it.
To collapse this menu and to take up less screen real estate, click the collapse button at the top right of this menu to show an icon only version of this.
To expand this side menu, you can click on the button once again.
The operations module shows the user a live look at their fleet, from either a device or location view via KPIs. These KPIs are usually defined for particular use cases per customer, but there are some that come out of the box with each implementation.
Each KPI has its own metrics that define it, but there are some similarities and jargon we use to define it. KPIs are all driven by device data to give a live feed and look at your organization’s health.
The first topic to discuss in the threshold for a KPI. These thresholds define the health of a KPI and give users a quick understanding of the status of each metric. At a glance, each KPI has a color depending on what threshold is met. When a KPI is green, we assume that the threshold is healthy status as displayed below.
If the KPI is yellow, it is in a warning status. This usually means the KPI is in danger of falling into a red/Danger status, but is not usually something that needs to alerted on.
If the KPI is in a red state, it is in a danger status. This means that the KPI is an unideal state and is not working as inteded.
If the KPI is in a blue state, it means that the KPI is currently not accurate state because there is no information coming in from the device. This usually means that the device is offline and any metrics shown are out of date and do not represent the current state of the KPI.
If the current state of a KPI is showing as grey or has two hyphens, this means that the KPI is inactive. A KPI is usually in an inactive state because there has not been data for the KPI to populate.
The overall status is shown on the left of the dashboard that shows the health of a location or device. This is calculated from each KPI that makes up the entity.
Hovering over a KPI or status can give you a summary as to what is causing that status.
Some KPIs will show you what those thresholds are when they are hovered as well.
There are cases in which a KPI has a number underneath it with multiple colors, we call these KPI Components.
For this KPI, it’s made of three components being CPU, Memory, and Hard Drive. Clicking on a KPI can give you a better view as to what data is behind the KPI.
Clicking on the accordion icon in the top right will expand a data graph to show you historical trends of the KPI.
On the left, you’ll also get a summary for that device/location of the status of the other KPIs.
Clicking on any of these icons will traverse you to the KPI to see that data. Some KPIs have a component that is populated by the device and can be deleted if no longer relevant. See the software KPI below:
Clicking on the trash can icon on the right will remove the component from the KPI. Please note, not all components can/should be deleted.
On the main dashboard, there is a tasks column that has a icon that allows users to execute actions from the device/location.
This is also accessible in the pop up modal as well when you click on the KPI.
Some organizations even have multiple dashboards for their KPIs. You can access this by clicking on the accordion icon next the dashboard title.
