How IT admins manage devices via Connect's dashboard

Picture yourself as an IT Admin managing the devices located across multiple warehouse locations.

SOTI Connect is a Mobile Device Management (MDM) Solution for Internet of Things (IOT) devices such as mobile printers. It offers an advanced dashboard view allowing for quick, high level glances of all the devices and their properties. Users may get informed about key device information by text and charts.

Users require more versatility

Connect's device dashboard is too rigid in it's layout and incapable of allowing IT Admin to separate device data into views that are organized in the best ways for them

So how do we allow IT admin to analyze and manage their device fleet in a way that is easier to digest and control?

Dashboard Visual Studio aligns Connect with SOTI's goals

As SOTI products aim to have boost their visualization presence to convey device data in other, more telling ways past tables, this feature will allow users to view their data and perform operations through many different visual options.

Ensuring consistency across all product builders

SOTI XSight and SOTI Snap both have drag and drop builder features - one for creating location tracking maps and the other for building apps, respectively. With there being two other app builder UIs, I designed this feature with the intent to maintain the look and feel of any other SOTI builder.

Drawing from common builder paradigms

Following the analysis of internal builders, I furthered my study to understand common practices of drag and drop features.
Styling and theming options
Pre-designed templates
Drag and drop widgets
Testing and previewing
Set between draft and published
User authentication and permissions

Prioritizing features into phases

From the given acceptance criteria from Product Managers I further expanded on the list of feature capabilities that I found from my research analysis that may add value to this solution. Once the full list of potential offerings were collected, I grouped them by priority and feasibility. This allowed for us stakeholders to understand what will be going into phase one and those that will be considered for the second phase of this feature.

Testing and approval from stakeholders

After deciding on the full list of criteria for phase 1, I produced a user flow, and wireframes. I then walked Product Managers and Engineer through the assets, noting any feedback or adjustments needed before moving towards a high-fidelity prototype.

Introducing user defined dashboard views

By using the flexibility to make your own views, admins can see their printers and network using metrics which are uniquely valuable to them.