From Idea

  • For System Inventory, the UX team analyzed the user requirements and combined system and device inventory in one view.

  • Motorola's design system Cobalt doesn't support master grid view. The need was to design a top-level grid for System Inventory, having rows that expand. When expanded, the device grid is displayed with other details related to the expanded devices' row.

  • UX team explored different concepts and searched for open-source design systems to save development cost & effort.


To Design Hand-off

  • The team decided the use AG Grid's Master Grid view solution. We explored ways to merge complex structure of system and device data base.

  • UX team internally evaluated concepts and decided to merge both Master Grid (System & Device Integration) and Simple Grid (Device information) in one view.

  • We documented details such as specification, user flows and interaction in Figma as ready for development.

86D 0H 10M 14S

86D 0H 10M 14S

Role: UX Lead

Collaborated with: Research Product Owners, Engineering, Program Manager

Duration: October 2023 - Ongoing

From idea

  • For System Inventory, UX team analyzed the user requirements and combined system and device inventory in one view

  • MSI's design system Cobalt does not support master grid view. The need was to design a top level grid for System inventory having rows that expand. When the System row is expanded, device grid is displayed with other details related to the expanded devices' row.

  • UX team explored different concepts and searched for open source design systems to save development cost & effort.


To Design Hand-off

  • The team decided the use AG Grid's Master Grid view solution. We explored ways to merge complex structure of system and device data base.

  • UX team internally evaluated concepts and decided to merge both Master Grid (System & Device Integration) and Simple Grid (Device information) in one view.

  • We documented details such as specification, user flows and interaction in Figma as ready for development

This project is still in design & development phase. Counting back for the launch date!

This project is still in design & development phase. Counting back for the launch date!

This project is still in design & development phase. Counting back for the launch date!

View More

Ongoing Research

The UX Team collaborates with the Research Team to prepare the agenda for every Voice of Partner research session on every 2 sprints. We have 4 partners joining our pilot research program. We evaluate the design and have updates based on user feedback. The aim is to complete 6 VOP sessions and Beta Sessions with the end users before the release.

So far, we received 19 feedback 9 implemented, 5 in progress and 5 pushed to future.

Ongoing Research

The UX Team collaborates with the Research Team to prepare the agenda for every Voice of Partner research session on every 2 sprints. We have 4 partners joining our pilot research program. We evaluate the design and have updates based on user feedback. The aim is to complete 6 VOP sessions before the release.

So far, we received 19 feedback 9 implemented, 5 in progress and 5 pushed to future.

Inventory View

1- As a user, I need to see all the systems and their devices.

2- As a user, I need to all the devices in one list.

Side Panel

Side Panel

As a user, I need to see status, upgrade, device and license details for each device.

As a user, I need to see status, upgrade, device and license details for each device.

Job View

As a user I need view to the job logs with all upgrades (in progress, completed or failed).

Abnormalities

As a user, I need to be notified with any abnormalities and guided to fix the issues.

Before Validation

  • The assumption was view of all devices was more priority than the system view.

  • Connection> License>Status was the priority order.

  • Color code was used to show the difference between active and redundant devices.


  • The assumption was view of all devices was more priority than the system view

  • Connection> License>Status was the priority order

  • Color code was used to show the difference between active and redundant devices

The assumption was view of all devices was more priority than the system view

  • Connection> License>Status was the priority order

  • Color code was used to show the difference between active and redundant devices

After Validation

  • Changed default view to Group by System and Devices.

  • Switched the order of the SMA License and Connection columns so users can see the relationship between connection and status.

  • Got rid of the color-coded dots under the Status column to avoid confusion.

  • Changed default view to Group by System and Devices.

  • Switched the order of the SMA License and Connection columns so users can see the relationship between connection and status.

  • Got rid of the color-coded dots under the Status column to avoid confusion.

From Idea

  • For System Inventory, UX team analyzed the user requirements and combined system and device inventory in one view

  • MSI's design system Cobalt does not support master grid view. The need was to design a top level grid for System inventory having rows that expand. When the System row is expanded, device grid is displayed with other details related to the expanded devices' row.

  • UX team explored different concepts and searched for open source design systems to save development cost & effort.


To Design Hand-off

  • The team decided the use AG Grid's Master Grid view solution. We explored ways to merge complex structure of system and device data base.

  • UX team internally evaluated concepts and decided to merge both Master Grid (System & Device Integration) and Simple Grid (Device information) in one view.

  • We documented details such as specification, user flows and interaction in Figma as ready for development

IT Technicians

Sarah is the IT Technician who is responsible for 5 customers' systems and their hundreds of infrastructure components. Regularly she:

1- Checks the health of the systems and components.
2- Makes onsite upgrades if the components are outdated.
3- Fixes and resolves issues.

Systems & Components

One IT Technician can be responsible for multiple systems. Each system have types, IDs, IP Addresses, Names, Network Status and RM Connection Status.

Each system includes components:
1- CMSS (CapMax System Server)
2- Repeater
3- Subscriber
These servers are responsible for managing the presence and mobility information of radios in the system over the air.

Today

The backbone of Mototrbo's 2-way communication system is made up of Repeaters, Capacity Max Servers, and Gateways. These components work together to make sure that the radio network is always available and that communication is secure, and clear across an enterprise. In summary, Mototrbo infrastructure components need to be set up, well-maintained, and upgraded regularly to keep the robust and reliable communication system supporting various industries and applications.

Today

The backbone of Mototrbo's 2-way communication system is made up of Repeaters, Capacity Max Servers, and Gateways. Mototrbo infrastructure components need to be set up, well-maintained, and upgraded regularly to keep the robust and reliable communication system supporting various industries and applications.

Today

The backbone of Mototrbo's 2-way communication system is made up of Repeaters, Capacity Max Servers, and Gateways. These components work together to make sure that the radio network is always available and that communication is secure, and clear across an enterprise. In summary, Mototrbo infrastructure components need to be set up, well-maintained, and upgraded regularly to keep the robust and reliable communication system supporting various industries and applications.

Target User

Motorola collaborates with a network of authorized dealers and system integrators. These experts work closely with customers to design, deploy, and maintain the infrastructure tailored into specific needs. They provide expertise in system planning, installation, configuration, and ongoing support. These experts are responsible for regular health checks and upgrades of the components such as servers. Everything is handled manually. It takes up to 2 days for them to make an upgrade to a specific device with a lack of guidance. Upgrade can take up to 1 month if any error occurs during any upgrade step.


Target User

Technicians/administrators are responsible for health check and upgrades of Mototrbo system and devices (servers & repeaters) today. Everything is handled manually. It takes up to 2 days for them to make an upgrade to a specific device with a lack of guidance. Upgrade can take up to 1 month if any error occurs during any upgrade step.

Design Process

Currently, we are 2 UX designers and 1 researcher working on this project. On a regular basis, we collaborate with RM, Cloud Gateway, Front End Development and Product Teams. 2 weeks sprints are used for design and development. We have Voice of Partner Sessions for usability feedback on every 2 sprints.

Design Process

Currently, we are 2 UX designers and 1 researcher working on this project. On a regular basis, we collaborate with RM, Cloud Gateway, Front End Development and Product Teams. 2 weeks sprints are used for design and development. We have Voice of Partner Sessions for usability feedback on every 2 sprints.

Job View

As a user I need to view the job logs with all upgrades (in progress, completed or failed)

Abnormalities

As a user, I need to be notified with any abnormalities and guided to fix the issues

IT Technicians

Sarah is the IT Technician who is responsible for 5 agencies' systems and their hundreds of devices. Regularly she:

1- Checks the health of the systems and devices
2- Makes onsite upgrades if the devices are outdated
3- Fixes and resolves issues

Systems & Devices

One IT Technician can be responsible for multiple systems. Systems have types, IDs, IP Addresses, Names, Network Status and RM Connection Status. Each system can include devices:
1- CMSS (CapMax System Server)
2- Repeater
3- Subcsriber

Overview

Mototrbo Connect is a new portal that has been designed to help manage inventory and upgrades for Mototrbo infrastructure. With this portal, technicians can access system and component details for multiple customers simultaneously. The portal also guides the users on how to maintain and upgrade the components such as servers and repeaters.

Role: UX Lead

Collaborated with: Research Product Owners, Engineering, Program Manager

Duration: October 2023 - Ongoing

Overview

Mototrbo Connect is a new portal that has been designed to help manage inventory and upgrades for Mototrbo infrastructure. With this portal, technicians can access system and component details for multiple customers simultaneously. The portal also guides the users on how to maintain and upgrade the components such as servers and repeaters.

Role: UX Lead

Collaborated with: Research Product Owners, Engineering, Program Manager

Duration: October 2023 - Ongoing

Overview

Mototrbo Connect is a new portal that has been designed to help manage inventory and upgrades for Mototrbo infrastructure. With this portal, technicians can access system and component details for multiple customers simultaneously. The portal also guides the users on how to maintain and upgrade the components such as servers and repeaters.