# Solar Dashboard Design: Keep Device IDs Beside Models

Source: https://www.jvds.cn/en/share/ui-design/solar-monitoring-object-and-metrics-u133
Language: en
Published: 2026-10-21
Author: JVDS Design Studio

This solar dashboard design uses black, orange and dimensional panels for a strong equipment character, with white-gray cards for readings. Name and identifier remain below the model and on mobile. Among similar devices, these small words identify objects more reliably than rendering angles.

## Key takeaways

- Models sit beside names and identifiers, making device recognition independent of appearance.
- Sources and alerts enter the overview; units, time and status need separate explanations.

## Models show type; identifiers show the instance

The panel model takes most of the mobile upper area, with Meevis Solar Panel and ID below, then a gray battery card. Dark backgrounds clarify model lines, while name and identifier connect its appearance to a record.

Device monitoring can identify type first, then instance. Similar panels need persistent identifiers in alerts and cross-device viewing. The place-like heading above should distinguish device and site levels rather than explain every scope at once.

JVDS prioritizes stable identity. Models may rotate, shrink or change views, while identifiers and current location remain findable. Visible location and image entries are discussed only as controls without assumed destinations.

![Mobile solar panel model above Meevis Solar Panel and ID 449836](https://www.jvds.cn/upload/2026/1008/d187-tp/u133-i1.webp)

Mobile device page | Model, name and identifier sit together; place and device identities need clear separation.

## White metric cards give large numbers sources

Current Power, Production, Consumption and Alerts sit below the desktop model, with restrained orange lines on gray-white. Current Power adds Solar, Grid and Battery components so overview readers see more than an isolated total.

Cards repeat heading, large value and graphic, but each needs its own unit and time scope. Similar titles use kW and kWh; visual consistency does not justify making units identical. Establish field meaning before names and summaries.

Alerts beside ordinary trends help reveal problems, but orange also marks sources and gauges and cannot alone [indicate severity](https://www.jvds.cn/en/share/ui-design/semantic-color-tokens-design). JVDS would specify alert name, state, time and device relationship, connecting details to equipment and moment for further checks.

![Current Power, Production, Consumption, Alerts and Site Power beneath a black device model](https://www.jvds.cn/upload/2026/1008/d187-tp/u133-i2.webp)

Desktop dashboard | Models identify objects; pale cards supply sources, trends and checking entries.

## Mobile stacks cards below the retained object

Mobile retains device name and identifier above battery and current power, with two enlarged similar cards beside it to show titles, components and trends. Display numbers 1, 2 and 3 divide the presentation; they are not three app steps.

Dense small-screen cards need adjacent fields and units. Current readings and multi-day graphics need time relationships so historical trends are not mistaken for current values.

Follow a desktop alert to the same mobile device and check identifier, metric period and result correspondence. JVDS would stabilize [equipment identity and data time](https://www.jvds.cn/en/share/ui-design/dashboard-data-visualization-mistakes) first, providing a dependable reading context for rendering and orange atmosphere.

![Mobile device name above Battery level 80 and Current Power 5.48](https://www.jvds.cn/upload/2026/1008/d187-tp/u133-i3.webp)

Mobile arrangement | Device identity remains with cards; presentation numbers are not product steps.

## Frequently asked questions

### Does a monitoring dashboard need a model?

Models help identify type; identifiers and places identify specific equipment. Readings still need units, periods and update status.

## Design review checklist

- Check metric headings, units and time scope.
- Retain device identifiers when returning from alerts.

## Connect equipment appearance to findable records

If your energy or equipment management product needs models, metrics and alerts organized, begin with device hierarchy and data fields.

JVDS provides UI/UX design and website design and development. We can work through page content, interface structure and implementation needs together.

[Contact JVDS to discuss your project](https://www.jvds.cn/contact)