Skip to content
Shared platform · Application

Shared Components

Mission control, a plant HMI, a farm advisory app and an ERP screen have more in common than they look: tables of live data, alarms that must be noticed, forms that must not be got wrong. Shared Components is the design system and component library behind all of them, so a new product inherits accessibility, theming and interaction behaviour rather than reinventing it.

What it does

Inside the platform

01

Design system & tokens

One typographic scale, palette and spacing system, themed per product without forking the components.

02

Data-dense components

Tables, time-series views, alarm lists and status surfaces built for operators watching them all day.

03

Accessibility built in

Keyboard operation, contrast and screen-reader behaviour handled in the component, not left to each application.

04

Operator patterns

Confirmation, authority and two-person approval flows implemented once and reused wherever an action carries consequence.

How it fits together

The shape of the work

Four very different consoles, one component underneath

An alarm list on a plant floor and an alarm list in mission control are the same problem wearing different colours. Building them once means the keyboard behaviour, the contrast and the two-person approval flow are inherited — a product cannot ship without them by forgetting.

Mission controlVyovrindaPlant HMIIndustrial AutomationFarm advisorySasyavedaERP screensSamavāyaComponent library — themed per product, never forkedData tableTime-seriesAlarm listForm & validationConfirm & authorityStatus surfaceDesign tokensType scalePaletteSpacingContrastMotionThe dark component is the one that carries consequence: confirmation, authority level and two-person approval, implemented once.Accessibility lives inside the component — keyboard operation, contrast and screen-reader behaviour are not each product’s problem to remember.
Who builds on it

Used across the group

  • Every operator-facing product in the group

Ownership

A shared platform. It has no natural home in any single unit, so the group funds it centrally and the shared engineering bench maintains it. Every company and division draws on the same version.

How we decide what is shared

Building something that needs Shared Components?

Tell us the constraints and we will come back with how this platform would carry them — or say plainly if it would not.