M2M Platform

2026

A connectivity management platform for 70,000+ SIMs, rebuilt module by module from a legacy system. Eight SIM detail tabs became four, and a 44-control search became one query bar. Phase 1, awaiting final integrations.

M2M Platform

2026

A connectivity management platform for 70,000+ SIMs, rebuilt module by module from a legacy system. Eight SIM detail tabs became four, and a 44-control search became one query bar. Phase 1, awaiting final integrations.

Client

Enterprise IoT & Telecom

Client

Enterprise IoT & Telecom

Role

Senior Product Designer

Role

Senior Product Designer

Service

Enterprise Platform, Information Architecture, Prototyping

Service

Enterprise Platform, Information Architecture, Prototyping

M2M Platform case study cover

The challenge

The challenge

An enterprise connectivity platform for 70,000+ SIMs inside delivery trucks, payment terminals, meters and trackers. When one stops transmitting, something physical stops working. The brief was to replace the legacy platform outright, not reskin it. I was the sole designer.

What the audit found
  • No fleet-level state. The platform showed 25 rows, not the fleet, so every aggregate question meant an export to Excel.

  • Two gears, no middle. One exact identifier, or a 44-control boolean builder.

  • Raw data, not information. Bytes instead of megabytes, timestamps instead of “6 days ago”.

  • Broken edges. No way to tell “no data” from “failed to load”.

  • English-only and left-to-right, with Arabic customer names already in the data.

Why SIM Management went first

The risk in a brief that size is designing twelve modules shallowly instead of one properly. SIM lifecycle is the highest-traffic module and contains every hard pattern: dense tables, bulk destructive actions, deep drill-down, audit logs and sensitive fields. Solved there, the patterns carry into dashboards, billing and the AI layer.

Legacy SIM table above the redesigned overview with status cards and an AI insight
Legacy SIM table above the redesigned overview with status cards and an AI insight
From 25 rows to the whole fleet

① Before: raw identifiers, 25 rows at a time ② Fleet state as clickable status cards ③ AI insight ranked by impact

Decisions & outcome

Decisions & outcome

Seven decisions carried the module, each tied to a specific failure in the legacy audit. Four of them:

Fleet state as the landing view

Clickable status cards above the table, each with a today-delta, so reading the fleet and narrowing to it are one gesture.

A middle gear for search

One composable bar across seven identifiers, with inline filters and Advanced Search one click away.

Eight tabs to four, a header that never moves

Tabs organised by task instead of database table (Overview, Configuration, Diagnostics and Activity) under a persistent identity header.

AI that triages, not decides

Insights are grounded in live data and ranked by consequence. The assistant can draft a bulk suspend but never run one; every action goes through the normal confirmation, with a human as the last step.

Where it stands
  • SIM detail view: eight tabs became four.

  • Bundle-status lookup: nine steps became four.

  • Advanced search: 44 controls became one query bar plus clickable status filters.

  • Fleet state that took five separate searches now loads as the default view.

Three sprints designed and handed over in Q2 2026: SIM Management, dashboards and the AI layer. Phase 1 is awaiting final integrations, so these are audit counts against the delivered design, not production metrics.

Legacy advanced search form above the redesigned search bar with filter chips
Legacy advanced search form above the redesigned search bar with filter chips
44 controls → one query bar

① Before: the boolean search builder ② One bar across seven identifiers ③ Active filters shown as chips ④ Advanced Search one click away

Legacy SIM details tabs above the redesigned header and four task tabs
Legacy SIM details tabs above the redesigned header and four task tabs
Eight tabs → four, organised by task

① Before: eight tabs by database table ② An identity header that never moves ③ Overview, Configuration, Diagnostics, Activity

SIM table with ten rows selected and the contextual bulk action bar
SIM table with ten rows selected and the contextual bulk action bar
Bulk actions in context

① Selection count ② Actions appear only when rows are selected

No-results state above a failed-to-load state that keeps the SIM identity header
No-results state above a failed-to-load state that keeps the SIM identity header
“No data” is not “failed to load”

① An empty result echoes the query ② A load failure says so ③ The identity header stays on error

Want the full story?

The full case study goes deeper, with every decision up close, more screens and the reasoning behind them.

Create a free website with Framer, the website builder loved by startups, designers and agencies.