Socio-Economic Assessment and Sustainability
Evaluating socio‐economic impacts and sustainability of automated driving provides valuable knowledge for different stakeholders to make informed decisions about CAD investments. Developing a highly automated transport system calls for substantial investments both by industry and by public road authorities. Furthermore, the life cycles of investments in the road transport system are long, and the decisions made today have far-reaching consequences in the future. The social impacts of automation are, however, largely unknown. Assessment should have strong emphasis on social effects, user requirements, acceptance and user outreach.
Widespread use of common impact assessment methodologies, such as the FESTA Handbook, can harmonise evaluation efforts. Using a sound methodology also helps to build validity of evaluation results as the work then follows the phases of a scientific study. Methodologies can provide best practices and lessons learned, and they are not generally seen too binding, either. For small studies that have a strict timeline, methodologies provide helpful documents and checklists. Evaluation communities can even share tools and data models.
The road map below shows the enablers and challenges for socio-economic assessment on our way towards the set objectives for sustainable and inclusive mobility for all everywhere and for livability of all areas.
ARCADE is currently working on detailing actions identified in Deliverable 3.7 (under documentation, link below) for the Socio-Economic Assessment and Sustainability area, related to:– Large-scale pilots and FOTs
– Automated mobility and urban planning
– Inclusive automated mobility concepts
– Common testing and validation methodology
– Societal needs and risk analysis
– Accident and traffic database with ODD aspects for scaling up
– Lifetime cost studies of CAV.
Have feedback on this section? Let us know!
Please add your feedback in the field below.
Your feedback has been sent!
Thank you for your input.
An error occured...
Please try again later.