Mobility scenario modelling (Scenarios)
Colin de Kwant, Amir Rashid, Ciarán O'Reilly and Carlos Casanueva
Vehicles are mostly viewed as a product, an asset, to support its owner in performing functional tasks (such as transporting, lifting etc), providing services (eg private‐/public services, rental, entertain) and or improving well‐being or comfort (eg status, safety, ergonomics) fitting an environment and duration (use or life cycle). Many needs and requirements to design vehicles follow from the product owner (customer) viewpoint. Other stakeholders like governments will have other requirements for suppliers and owners along the vehicle life cycle to serve goals from a society, macro‐economic and or environmental point of view. Collectively we can we refer to requirements related to these points of view as "situation properties". These properties vary per customer segment, environment and over time. Vehicles are ideally designed using any and all technology (eg connectivity), concepts (eg design reuse) and capabilies (eg lightweight‐, software design) available to the manufacturer to fit the understood customer needs and requirements from other stakeholders. The availability and economic feasibility of technology and capabilities also varies between manufacturer, industry and over time. We will refer to these as "asset properties". Finally, even if two manufacturers each have the technology and capability to serve a particular need and fit a situation, if and how these manufacturers will actually respond will most likely differ. Variance in response, i.e. creating and supplying a design solution and doing so in time before needs and situation have changed, can be due to strategy, used process or data flow management. We will refer to these variables as "response properties". The goal of this project is to decompose, select and interlink situation, asset and response properties to create a configurable model for future mobility scenarios. The model shall be easy to use or adapt for industrial partners.