What does a driver need when the road leaves little room for error?
The project considers the physical and informational demands of trucking on the Qinghai–Tibet route: long journeys, high-altitude conditions, sparse support and changing attention demands.
Its research basis is secondary material, including documentaries, manuals and accounts from online discussions. The journey is a constructed design scenario, not a record of my own field driving.
The interface is one part of a larger support system.
The journey mapping brings together preparation, driving, emergencies and rest. It points to a need for information that changes with the situation, and support that continues beyond the dashboard.
This led to a layered concept: what the vehicle perceives, how a system might interpret it, and how the driver or a service could respond. The architecture remains a proposal.
Different driving situations create different information demands.
Propose interface states that prioritise the information relevant to the current scenario.
Essential actions should be easy to locate under pressure.
Explore physical controls alongside the screen-based cabin interface.
Support needs begin before driving and continue into rest.
Extend the design into a service blueprint covering the whole journey.
Design the system before adding another dashboard screen.
The proposed architecture brings together vehicle, environmental and physiological information. Interface states and service actions are then organised around the scenario.
Elements such as oxygen support, automated interpretation and connectivity are speculative components requiring engineering and specialist safety assessment. The diagrams are not implementation evidence or operating guidance.
A cabin interface, connected to the journey around it.
The visual design explores the relationship between the cabin, physical controls and digital information. The service blueprint extends the proposal across preparation, driving, emergency support and rest.
Together, these artefacts make the intended experience discussable before committing to detailed engineering.
The next test belongs in a physical cabin mock-up.
The supplied work contains cabin visualisations, interface states and system diagrams. It does not document a functional cabin or road test.
A next-stage evaluation would use a full-scale mock-up to examine reach, control visibility and screen legibility, including glare and vibration. The proposed safety-related functions would need a separate specialist assessment.
A system concept needs explicit boundaries.
This project expands the design scope from a screen to a journey and service network. Its strongest contribution is the mapping between situations, information and support.
Its central limitation is that secondary research cannot replace direct validation with drivers and relevant specialists. The next iteration should prioritise those perspectives before expanding the feature set.
