OEM methodology · Gulf mobility

أنظمة instrumentation للتنقل في الخليج — NEOM · البحر الأحمر

Falcon Gulf Instrumentation

State logic Radial hierarchy Safety first

A state-driven radial cockpit architecture for marine and desert mobility — production-derived HMI logic shaped on the gauge floor, not in a mood board.

NEOM mobility Red Sea marine Garmin / Raymarine logic Qt · QML alignment

Outline-mode radial gauge hierarchy study

1 · Origin & domain

Expertise from the production floor — not a job title.

Origin: a manufacturing environment that produced gauges for marine, off-road, on-road, and military industries — shaped by software engineers, industrial designers, product managers, motherboard fabricators, sales, floor staff, and quality inspectors.

Systems worked on

Marine · off-road · industrial · defense-grade instrumentation · UI systems. All domains except automotive.

What separates this from UI design

Production-calibrated problem solving — resolving real design issues under fabrication, safety, and field-readability constraints.

Executive summary

State-driven instrumentation for desert and marine platforms.

A dual-layer cognitive model translated into a software-defined radial cockpit interface.

Gyrfalcon layer · legacy

High-density telemetry, RPM, dynamic load — inherited mechanical gauge logic and performance complexity.

Saker layer · foresight

Speed, navigation, safety-first hierarchy — directional intelligence for future mobility logic.

Performance wraps clarity through hierarchy — but never overrides it.

2 · Role & contribution

Instrumentation UI / HMI systems designer

Radial gauge system architecture
State-based UI logic design
Cockpit information hierarchy
Visual cognition mapping
Cross-brand identity isolation system

Design stack

Figma · Adobe Illustrator · After Effects

HMI structure

Qt / QML · Unreal Engine HMI concept alignment

3 · Problem statement

Modern instrumentation fails under operational stress.

Core failures

No cultural adaptation
Hierarchy inconsistency
Information overload
Poor cross-domain translation
Conflicting performance vs. navigation systems

Cost of failure

Safety risk under motion
Performance misread at speed
Internal mapping confusion for operators

4–5 · Design objective & core concept

Dual-Inheritance Falcon System

Layer	Symbolic model	Functional role
Gyrfalcon	Legacy · high-performance complexity	RPM · telemetry · dynamic data
Saker	Foresight · operational clarity	Speed · navigation · safety

Two layers keep field-of-vision load focused at high speeds. One area reads. One area decides.

Design objective: separate performance and navigation cognition · maintain 2-second glance readability · adapt across marine and desert · support Arabic/English bilingual logic · scale across OEM multi-vehicle platforms.

6 · Information architecture

Three radial data zones

Outer · RPM Propulsion load · second priority at sea to avert engine stress

Middle · Speed ISO-readable motion reference · compliance layer

Core · Navigation Primary at sea · heading · waypoints · celestial cues

Navigation dominates the screen — waypoint bar logic familiar from game HUDs. Stars, sun, and moon remain telling references on open water.

Radial gauge cluster — RPM, speed, and navigation zones

7 · Information hierarchy

Priority rule system

01

Safety alerts — always override

02

Navigation integrity

03–05

Speed awareness · performance telemetry · ambient / luxury UI

Cognitive load reduction under motion stress — not decoration under duress.

6.1 · State-based UI logic

Four operational states — structure changes, not decoration.

Cruise

No-wake zone · low load · speed + navigation priority · reduced visual noise.

Sport

Moderate performance engagement · stabilized radial motion.

Performance

RPM outer ring dominance · telemetry exposure · enhanced motion response.

Emergency

Alert override · navigation collapse · critical data only.

State triggers: speed · engine load · user input · system alerts · environmental zones. What changes: structure · hierarchy · motion · density.

8 · Human factors

Safety-first instrumentation constraints

Glance rule: 2-second maximum readability under motion
Always override: emergency alerts · port · starboard hazards
Forbidden at high speed: animation · visual density
High-contrast desert visibility · anti-glare logic

9 · Multi-environment adaptation

Desert, marine, and night operating modes

Desert mode High contrast · sand-tone palette · reduced bloom · heat readability

Marine mode Deep blue spectrum · horizon overlays · primary entry domain

Night mode Bioluminescent cyan · low-luminance hierarchy for night helm

Marine first — because production familiarity lives there. Desert second — because contrast logic transfers.

10–11 · Cultural & visual rules

Gulf-native instrumentation logic

Arabic-first spatial hierarchy with English secondary alignment. RTL structure must never distort radial geometry spacing.

Gulf-native by lived context — not imported UX patterns applied from outside the region.

Non-decorative rule set

Geometry follows function
No ornamental overlays on data layers
Tick marks = measurable logic
Radial spacing encodes performance density

12 · OEM system alignment

Cross-domain mobility translation

Automotive HMI

Tesla-style state UI · BMW iDrive hierarchy · Mercedes hyperscreen layering.

Marine systems

Garmin / Raymarine helm architecture · navigation-first prioritization.

Aviation influence

Honeywell-style cockpit layering · forward situational awareness mapping.

13 · Application & industry use

Where the system lives

Yacht helm

Primary entry — highest domain expertise and production familiarity.

Desert SUV

Second expansion — high-contrast performance clusters.

Autonomous mobility

State-driven UI for NEOM / Red Sea corridor platforms.

Aviation-inspired cockpit

Layered situational awareness for next-gen mobility ecosystems.

Ultimate vision: Islamic dome design integration — biomimetic radial geometry aligned with Gulf architectural intelligence, not surface ornament.

14 · Outcomes

What this case study demonstrates

Systems-level HMI thinking — not screen design
State-based UI architecture understanding
Cross-domain mobility translation (marine → desert → aviation)
Cognitive load engineering awareness
Real-world instrumentation production logic

OEM reviewers evaluate constraint awareness and honest experience boundaries — not marketing language.

15 · OEM evaluation & positioning

What a hiring manager evaluates

Can this designer think in systems?
Can they structure states, not screens?
Do they understand safety hierarchy?
Can they scale across platforms?
Do they understand real instrumentation constraints?
Can they separate brand identity from system architecture?

“A state-driven radial instrumentation architecture designed for Gulf mobility ecosystems, balancing high-performance telemetry with operational clarity under safety-first OEM constraints.”

Zarah Sharda Studio · Falcon Instrumentation · 16 slides Executive cut (6) Infographic Live prototype Portfolio