General Assembly meeting in Bari
19 October 2026 |The AcceptRemote consortium held its General Assembly on 15–16 September 2026 in Bari, Italy, hosted by Politecnico di Bari. The two-day meeting brought project partners together to review progress since the project started in May 2026, coordinate ongoing activities and discuss the next steps in developing and validating remote operation solutions. University of Deusto-DeustoTech was represented by Leire Serrano and Erick Rodríguez.
1 MINS READ ←Back to NewsReviewing progress and aligning project activities
The first day focused on reviewing the work carried out across the project’s work packages and examining how the different research activities were beginning to connect. Discussions covered the societal and human factors relevant to remote operations, alongside technical developments in system architecture, connectivity, AI-supported functions and human–machine interaction. Particular attention was given to how these activities would contribute to the three AcceptRemote pilots: RideCare in Istanbul, LogiCare in Toulouse and FlexiCare in Munich. The discussions highlighted the importance of coordinating technological development, societal readiness activities and pilot preparations from the early stages of the project.
Exploring stakeholder needs and pilot requirements
The second day was dedicated to two interactive workshops, both organised around the three pilot scenarios. The first workshop focused on stakeholder needs and expectations regarding remote operations. Working in pilot-specific groups, partners considered the needs, concerns and expected benefits of different actor groups and prioritised the issues requiring particular attention during the project’s co-design and co-development activities. Discussions covered aspects such as trust, predictability, inclusiveness, training, technical capabilities and potential benefits for operators, users and wider society. The second workshop addressed pilot requirements, constraints and architecture. Building on the initial pilot inputs and component descriptions prepared by the partners, the three groups reviewed their pilot workflows and explored how different system components would need to interact. This included identifying relevant interfaces and dependencies, considering data and information flows and remote-operation modes, and distinguishing between aspects that could already be defined and those requiring further work. Together, the two workshops addressed the pilots from complementary perspectives: the needs and expectations of different stakeholders and the technical requirements of the solutions being developed. Their outcomes will contribute to the refinement of pilot requirements and the further mapping of components, dependencies and workflows.