gxceed
← 論文一覧に戻る

D2.5 Technical requirements and targets integrated for pilots

D2.5 パイロット向け技術要件と目標の統合 (AI 翻訳)

Shift2Zero Partners

Zenodo (CERN European Organization for Nuclear Research)📚 査読済 / ジャーナル2026-04-10#EV・輸送Origin: Global
DOI: 10.5281/zenodo.19496078
原典: https://doi.org/10.5281/zenodo.19496078

🤖 gxceed AI 要約

日本語

Shift2Zeroプロジェクトの成果物で、ユーザー中心の要件抽出プロセスを文書化。87件のインタビュー、8回のワークショップ、512名の調査などを通じて181の要件を特定し、パイロット実証に向けた電動小型商用車のイノベーションをユーザーニーズに適合させる。

English

This deliverable documents user-centered requirements elicitation for Shift2Zero innovations, collecting data from 87 interviews, 8 workshops, a survey of 512 participants, and simulations. It defines 181 technical requirements for electric light commercial vehicle innovations, validated through co-creation workshops and developer feedback, ensuring user-friendliness and market orientation for pilots.

Unofficial AI-generated summary based on the public title and abstract. Not an official translation.

📝 gxceed 編集解説 — Why this matters

日本のGX文脈において

本件はEU主導プロジェクトの一部であり、日本のGX文脈への直接的な関連は薄い。ただし、電動小型商用車のユーザー要件分析手法は、日本でのEV物流導入における参考事例となり得る。

In the global GX context

This EU-funded project deliverable focuses on user requirements for electric light commercial vehicles, contributing to transport decarbonization. It offers methodological insights for user-centered design in EV logistics, relevant to global efforts in fleet electrification.

👥 読者別の含意

🔬研究者:Requirements engineering methodology for EV logistics innovations, with validation approaches combining user and developer perspectives.

🏢実務担当者:Practical insights on how to collect and validate user needs for electric commercial vehicle development, useful for fleet operators and EV manufacturers.

🏛政策担当者:May inform policies supporting user-centric design in electric vehicle deployment, though the deliverable is project-specific.

📄 Abstract(原文)

Deliverable 2.5 documents the process of user-centred requirements elicitation for the Shift2Zero innovations within Task 2.5 (User requirements analysis for pilot preparation and definition of technical requirements), starting with the project and ending with the completion of Work Package (WP) 2 in project month 12. The aim of this deliverable is initially to summarise the information gained from Tasks 2.1 (End-user & stakeholder mapping, user-specific contexts & needs), Task 2.2 (User-specific needs for conceptual design guidelines), Task 2.3 (User-specific preferences and trade-offs) and Task 2.4 (Synergies with new logistics concepts & innovations). Based on these insights, the findings are transferred into a harmonised list of requirements. These requirements are then validated through co-creation workshops from the user perspective and through discussions from the developer perspective. This final list of requirements covers the perspective of the various users and stakeholders and the necessary characteristics and capabilities that the innovations need to fulfil. These requirements in turn form the basis for further innovation development of WP 3 conceptual designs and ensure that the innovations meet the actual needs of users and stakeholders by offering tangible added value.To collect the requirements for the Shift2Zero innovations, a systematic and methodical approach is applied. User needs and initial requirements are collected through expert interviews, workshops with end users, surveys, simulations and discussions in Task 2.1 to Task 2.4. In total, 87 interviews, eight workshops, seven mapped ecosystems, a survey with 512 participants and seven simulations provide a solid data basis with well-founded insights. These user needs and preliminary requirements are then thoroughly analysed, converted into formal requirements and sorted thematically. Based on this foundation, the systematic documentation of requirements is carried out in a central requirements list. After this step, the requirements are available in a complete and unambiguous form, making it possible to validate them from both the user and developer perspectives. The user side validation aims to validate the earlier interpretative step in which user statements were transformed into formal requirements. For this purpose, co creation workshops in Bologna, Padua and Aachen are conducted at three locations in collaboration with Gruber Logistics, Alke Electric Vehicles, RWTH Aachen University and additional external companies. Using augmented reality glasses, an immersive scenario is created that allows participants to digitally experience the Shift2Zero innovations at this early project stage. The realistic and interactive representation allows participants to open doors, test mechanisms and evaluate ergonomic usability. All relevant insights from these activities are then integrated into the requirement list.In addition to the validation from the user perspective, validation from the developer perspective is equally important to ensure technical feasibility and to maintain the intended project focus. For this purpose, the requirements are aligned with the responsible developers in several iteration cycles, beginning at the General Assembly in Bergen in September 2025. After completing the final iteration loop of the requirements list in Task 2.5 and incorporating feedback from both users and developers, the requirements for each innovation are documented in an updated version. This requirement list is the outcome of this deliverable and contains 181 formulated requirements, providing a detailed description of the objectives for the Shift2Zero innovations while considering the social, political, economic and technical layers.These requirements now serve as the baseline for the design and development of innovative vehicle solutions within Work Package 3. This ensures that the eLCV innovations developed within Shift2Zero are not only technologically advanced but also practical, user friendly and market oriented.Furthermore, the requirements contribute to the planning of pilot activities in Work Package 6. Within these pilot activities, the developed innovations will be tested and verified in real life demonstrations. Finally, based on the current requirements, an adapted and validated list of user needs and technical requirements will be generated that reflects the practical experience gained.

🔗 Provenance — このレコードを発見したソース

gxceed は公開メタデータに基づく研究支援データセットです。要約・翻訳・解説は AI 支援で生成されています。 最終的な解釈・検証は利用者が原典資料に基づいて行うことを前提とします。