mbg@portfolio:~/systems-management · case study 03 · read 9 min
Quiet search --:--:--
$ cd case_03/systems-management
// iDRAC + OpenManage Enterprise · four generations · one design intent

Systems management portfolio.

A decade leading UX architecture and team management for Dell's systems management software portfolio. Two products, iDRAC for the single server and OpenManage Enterprise for the fleet, held to one coherent UX across four generations of PowerEdge. The portfolio is now the systems management flavor of the ISG Design System, Dell's community-built design language.

Role
UX architecture & team mgmt
Team of 13 across US · Egypt · Taiwan
Products
iDRAC · OpenManage Enterprise
14G → 17G PowerEdge
Timeline
2015 → Present
Multiple generational ships
Flagship release
iDRAC10 · Sept 2025
First UI reinvention in ~8 years
iDRAC10 home dashboard
FIG. 00 iDRAC10, firmware 1.20.60.50 onward. The color-coded active health icons across the top, and the left-side expanding navigation, are two of the most consequential IA decisions from the redesign, and the first pieces of the ISG Design System to ship publicly.
⚠ Author note — remove before publishing
All figures populated. No outstanding placeholders.

Available alternate (unused): images/sysmgmt-xx-idrac8-network-alt.png — iDRAC8 Network page with 6 top tabs and Jump-to anchors. Stronger "fragmented IA" example than current FIG. 03 if a swap is wanted.
01 Position what the work was

Two products, one coherent UX, four generations of hardware underneath them.

The stack is two products. iDRAC is the per-server controller, agent-less and out-of-band, on every PowerEdge. OpenManage Enterprise is the fleet console, managing thousands of servers from one browser. My work is UX architecture and team management across both, across four generations of PowerEdge (14G through 17G), with iDRAC10 shipping in September 2025 with the first complete UI reinvention in eight years.

02 The Strategic Bet ISG Design System

Treat the portfolio as a design system.

Before this work, Dell's server management surfaces had drifted. iDRAC, OME, Lifecycle Controller, CloudIQ, each with its own grammar. The ISG Design System is Dell's answer, a community effort across the ISG org contributing tokens, IA principles, and interaction patterns. My team's contribution is the systems management flavor of it, and iDRAC10 is where that flavor first shipped in public.

Public reference

Dell KB: KB 000348267, iDRAC10. Info Hub walkthrough: Navigating the New iDRAC10 Interface.

03 The Generational Proof · iDRAC8 → iDRAC10 before / after

iDRAC10 is the first IA refresh in over a decade.

iDRAC's UI hadn't seen a meaningful redesign in over a decade. Admins were reaching around the UI, not through it. iDRAC10 is a complete redesign. Four IA shifts matter most.

IA.01Home page · text overview to health dashboard.

iDRAC8's home was a dense summary with recent logs and a deep sidebar. iDRAC10 leads with color-coded health icons for every critical subsystem. Glance-to-triage from one view.

Before · iDRAC8
iDRAC8 System Summary
FIG. 01iDRAC8. System Summary, with deep sidebar nav and field-by-field server detail. Read-to-understand.
After · iDRAC10
iDRAC10 home page
FIG. 02iDRAC10. Color-coded health icons + side nav. Glance-to-understand.

IA.02Navigation · nested sidebar to flat left-side expandable.

Nav moved from a deeply nested sidebar accordion to a flat left-hand vertical with in-place expansion. The old pattern made admins drill three levels down to reach a setting. The new one keeps sibling options visible and optimizes for the 99% case of an admin returning to a known task.

IA.03Detail expansion · dedicated sub-pages to side panel.

iDRAC8 used dedicated sub-pages for every detail view. To inspect fans, you'd drill into Hardware, then Fans, then a separate page; to compare two subsystems, lose your place. iDRAC10 uses row selection plus a persistent side panel. The list keeps its place, and it separates two actions that used to collide: selecting a row to see it versus checking a box to act on it in bulk.

Before · iDRAC8
iDRAC8 Fans sub-page with deep sidebar accordion
FIG. 03iDRAC8. Each subsystem (fans, batteries, CPU, memory, power) lived on its own page, reached through a nested sidebar accordion.
After · iDRAC10
iDRAC10 Storage Overview
FIG. 04Not apples-to-apples with FIG. 03, but the same principle applied to a different subsystem: component inventories stay in one place, with details revealed inline. Controllers, physical disks, virtual disks, and enclosures share one tabbed page.

IA.04Information architecture · fragmented menus to consolidated tabs.

The Storage Overview shown above is the clearest example. iDRAC8 split controllers, physical disks, virtual disks, and enclosures across a deep menu hierarchy. iDRAC10 consolidates them into one tabbed page. The same approach extends to a new Environments tab, which brings cooling, power, and temperature under one roof.

iDRAC10 Power Info under Environments tab
FIG. 05Power Info under the new Environments tab. PSUs, draw, BTU/hr, and historical trends in one view.
iDRAC10 Temperatures view inside Environments
FIG. 06Temperatures inside Environments. Inlet, exhaust, CPU, and DIMM thresholds with year-long history, in one place.

The iDRAC9 controller hasn't seen any significant changes to its web interface for a long time... With firmware version 1.20.60.55 applied, the new iDRAC10 web interface is a very welcome update as it isn't just a refresh, but a complete redesign.

Dave Mitchell · ITPro, 24 Sep 2025
04 The One-to-Many Counterpart · OpenManage Enterprise 4.3 → 4.6

OME applies the same design intent as iDRAC, at fleet scale.

OpenManage Enterprise is the fleet console, up to 8,000 devices under full management and 25,000 in monitoring-only mode, in one browser. The design problem is the inverse of iDRAC's. iDRAC has to give you everything about one machine without drowning you. OME has to give you the shape of thousands without reducing them to a number. 4.6 added a SmartFabric topology view, native Apache Kafka, a rebased SLES 15 SP6 appliance, and new deployment targets (Proxmox, Nutanix AHV, OpenShift).

OpenManage Enterprise home dashboard
FIG. 07OME 4.6 home. The fleet at a glance, with widgets for warranty, firmware, and configuration drift.
OpenManage Enterprise All Devices view
FIG. 08All Devices. Fleet inventory with system groups, custom groups, and per-device drilldown.
OpenManage Enterprise System Profile workload grouping
FIG. 09System Profile. Workload-tuned grouping (Database, HPC, NFVI, SDS) drives policy at scale.
OpenManage Enterprise Non-Dell Servers
FIG. 10Non-Dell Servers. iLO, ThinkSystem, and OEM hardware managed alongside PowerEdge.
OpenManage Enterprise Monitoring Metrics
FIG. 11Alert thresholds. Per-device power and temperature gauges with collected-at timestamps.
05 Outcomes shipped · cited · extending

The framework is extending. The portfolio is cohering.

4
PowerEdge generations shipped · 14G → 17G
25kdevices
OME 4.6 monitoring-mode ceiling · single console
ISG
Design System extending across the Dell ISG server portfolio

ITPro reviewed iDRAC10 as a complete redesign, not a refresh. What matters more internally is that agentic AI for systems management plugs into the same IA and the same design tokens. The flavor isn't just carrying visual cohesion, it's the substrate the next generation is being built on.

→ NEXT_CASE

Dell Research Library · shipped research platform.

Continue → 04/research-lib