SPINE Digital Discussion Hub

@MARIA-VASILAKI said in Talinn - Presentation of measures:

We would like to ask Tallinn about the value of Smart City Platform, what will be the benefits and how will you use it ?

Thank you for very good question!

We expect the Smart City Platform to provide significant value through real-time insights and performance tracking. Once we establish connections with relevant data sources and complete necessary integrations, we aim to use the platform's dashboard to dynamically monitor and improve Key Performance Indicators (KPIs) outlined in both the SPINE project and our Sustainable Urban Mobility Plan (SUMP). This should enable more responsive decision-making and support continuous improvement in mobility initiatives across the city.

@antonia-buric

Another question - what kind of EV charging stations are you implementing?

To improve the services near mobility centres for all categories of users, SPINE envisages the installation of accessible charging stations for electric vehicles. Some of the planned features respond to special mobility needs: ramps, canopies, spaces and signage for people with reduced mobility, special sockets for recharging electric wheelchairs, lighting, interoperability with platforms, multilingual, usable with universal payment methods without any subscription.

Currently, it is not the Municipality of Bologna (COBO) that directly installs the electric vehicle (EV) charging stations. Instead, there is a direct collaboration with Charging Point Operators (CPO), formalized through a memorandum of understanding. COBO provides space free of charge, while the CPOs (such as Enel X Way and beCharge) handle the installation and management of the charging stations without additional costs for the public administration. This model has worked well so far, but there are some limitations:

flexibility in the choice of locations: strict constraints cannot be imposed on EV charging station positioning, as CPOs may consider certain areas too expensive or inconvenient. In practice, the selection of locations is a compromise between demand factors (represented by the needs of users and the Municipality) and supply factors (i.e., the economic interests of the operators). For example, CPOs tend to prefer areas near power distribution cabinets to reduce installation costs, such as excavation and cabling expenses;

charging station power: CPOs are often incentivized to install high-power infrastructure because it generates higher revenue and takes advantage of economies of scale, allowing more charges to be completed in the same time-frame compared to lower-power stations. However, COBO is not focused on this model, as it aims to promote intermodality, which means enabling the combination of vehicle charging with the use of other forms of transport, such as public transit. High-power charging stations, which recharge vehicles quickly and encourage rapid vehicle turnover, do not support this approach. For example, users might decide to recharge their vehicle in 20 minutes, wait on-site, and then continue their journey by car instead of using a bus.
Therefore, COBO's intention is to focus on lower-power charging stations, which allow for slower recharging (typically taking a few hours) and give users greater flexibility as regards their desired parking time. Indeed, the low-power charging station better aligns with long-term parking, which is typical of intermodal areas where users might leave their cars for several hours and use public transportation for further trips, thus promoting intermodality.

@antonia-buric: we used to have a clearly defined set of features per type of hub but while rolling out and designing the first hubs it became clear that every locations requires a custom approach. It all depends on the environment, other services already available in the neighbourhood, what can be moved and what cannot be moved. I'll see if I can find the list of features and typologies that we used to have.
We're not tracking users. However, we do have our shared mobility trip data and we do yearly surveys on usage. Some questions are linked to multimodality.

@Miroslava: we're not really counting on smart parking management to switch behaviour. I personally think the smartest parking management measure we took is not allowing on-street parking for visitors in the old town. (and paid on-streek parking in large areas of the city). Other measures like showing available on-street parking spaces and guiding car users to those spots only makes it easier for car users, not harder. The smartest parking management strategy is to make it difficult for car users as early as possible in their trip. So car to closest trainstation and then into the city by train is better then car to P&R close to the city and then tram.

@Christophe: There's a list of +70 data layers we use for the various modes. Beside that we use the network data from OpenStreetMap and our routeplanner is also based on this. For map visualisation and theming we use Mapbox Studio. Users are able to turn on and off some layers. As a city we can also ensure that some layers we think are essential are always on. This can be P&R or mobility hubs. By showing them we make people aware about the options. Past the possibility of turning on and off layers, we don't give the user more options to theme a map. It is a very complex thing and most users won't use it. We do have an accessibility map style that makes everything more readable (still needs finetuning). In our app we do have guidance and navigation. It is possible to turn off or on the sound of the navigation. Everything is available in 4 languages and the website should be screenreadable. For the map component we're still looking into ways to make it screen readable. To my knowledge there's not a single application that has managed to do this. You can now check it out on the live site: www.sna.be

We get our data directly from the mobility providers and often it's the same source as they use themselves. We don't further try to improve the data.

I don't completely agree with the importance of RT-data for the user. In a good mobility system, the user does not need realtime data. Beside that, the whole IT-system of the city of Antwerp has been rebuild from scratch after a cyberattack last year. Even the design of a simple button on a website has been checked to ensure that it's not possible to gain access through such things.

@MARIA-VASILAKI : the screens we're installing are eInk screens like ereaders. The reason for this is that they can operate for a reasonably long time on batteries without the need to connect the infrastructure to the net. This makes it easier for us to install the screens anywhere we want on the public domain without having to open the ground to make an electric connection. As part of the service contract, the company installing the screen, replaces the batteries when needed. The cost of all this is covered in the SPINE budget.

The journey planner app, as well as the rest of the website is WCAG approved. It is useable with screenreaders and alike. However, making maps suitable and 100% WCAG proof is something nobody has found a solution for yet. I've seen a thesis on the use of AI to provide a spoken output of what is shown on the map but it stays tricky. We did include an accessibility layer in which we created a seperate more readable baselayer. We're still planning to fine-tune it with the community more but currently the focus is on improving the accessibility data we have and show to the user.

On the topic of discussing wider topics then spine or involving local stakeholders I think that's the whole goal of this platform. Sharing knowledge, not only during meetings but also through this platform.

@Francisco SPINE is the framework where the coordination between the bus operator and other involved services is being piloted, focusing on how information will be jointly and consistently provided to the user.

Regarding the surveys, we have different approaches. There are existing campaigns that SPINE will take advantage of, but they are not specific to the project. On the other hand, it is expected that specific SPINE campaigns will gather insights on the impact of the specific SPINE measures.

@Miroslava Due to the context in which the LEZs are being developed in Spain, the City Council is implementing the LEZs outside of the SPINE framework. Nonetheless, it is expected that some of the LL measures will assist in their management once implemented.

@Christophe Datasets are being used mainly by the technical partners, and their activities are being adapted to the data the city is able to provide.

@Francisco

Software development seems to be necessary, because even in the case of Antwerp where Flanders region installed interactive screens in the mobility hubs, it was very difficult to align the functionalities in the information they wanted to show. Antwerp nevertheless chose to develop their own platform to avoid vendor lockin. In Bologna case, the screens have to be installed in areas owned by the municipality as there was difficulty to find common ground with the rail operator owing the land. Resulting to points which might not be the optimal ones. No audio in any of the Lead cities for now.

Very interesting the internal work made in Tallin, with the different departments to define the solutions. Are you made up some like a "SPINE team" internally in the municipality to make different follow up about the advance of the project?

One question for Las Palmas, is there going to be some digital channel to deliver the information to the citizens about the different services in the hub apart from the information in place in the hubs that you mentioned in your presentation.
congrats for the work In the beautiful place of Las Palmas!

prova di risposta

For example, is it possible to convey surveys?

And trying to reply

IMG_1925.jpeg

@SPINEadmin
1. Convincing private mobility operators to open their platforms for Mobility as a Service (MaaS) involves addressing their concerns, highlighting the benefits, and presenting a clear, mutually beneficial vision.
Potential benefits to be emphasized (non-exhaustive list):

Increased Market reach by expanding customer base: by integrating into MaaS platforms, mobility operators can access a broader range of customers who prefer using multi-modal transport solutions. Increased market reach thanks to higher utilisation rates: more exposure can lead to higher vehicle usage rates and increased revenue. Brand visibility. Data Security: assure operators that sensitive data will be handled securely, with clear data-sharing agreements that protect their proprietary information. Operational control: clarify that operators will retain control over their operations, including pricing and availability. Technical support: offer assistance with the technical integration process, including APIs. Use pilot data to show positive outcomes and build trust. Regulatory compliance: highlight any regulatory requirements or incentives that support MaaS adoption, showing that integration can help operators stay compliant. Public funding: mention potential access to public funding or grants available for integrated mobility solutions. Environmental Impact: emphasise the role of MaaS in reducing emissions and promoting sustainable transportation, aligning with global and local sustainability goals. Case studies: present successful case studies from other regions or cities where MaaS integration has led to increased revenues and customer satisfaction.
It is important also to engage the operators in continuous dialogue through: Stakeholder Meetings: hold regular meetings with potential and current partners to discuss progress, address concerns, and brainstorm improvements. Feedback Loops: establish continuous feedback mechanisms to refine the MaaS platform based on operator input.

2. By carefully designing MaaS business models and implementing strategic measures that address the needs and interests of both cities and stakeholders, it is possible to create a sustainable, efficient, and user-friendly mobility ecosystem. This collaborative approach ensures that the benefits of MaaS are maximised for all parties involved.
As clarified in SPINE D.2.5 “BOLOGNA LL and Implementation Version 1”, released in June 2024: “The city or public transport authority pays for the development of the MaaS application, which can be both web-based and mobile application-based. The cost is related to the extent and complexity of the mobility services that must be integrated within the platform and the extensiveness of the transport area that must be covered. The local authority decides which mobility services should be integrated. If, next to a journey planner, payment services also need to be included for direct booking and payment through the application, the complexity increases and thus also the cost of the development. Therefore, the core feature of the white-label MaaS-solution is the journey planner and real-time information provision.”
Strategies for Creating a Win/Win for Cities and Stakeholders:

Public-Private partnerships: collaboration between government entities and private companies to deliver MaaS.
Win/Win: Cities benefit from innovative solutions and funding, while private companies gain access to public infrastructure and data. Integrated and inclusive planning: develop a MaaS platform that integrates all modes of transportation, ensuring accessibility for all demographics.
Win/Win: Cities achieve better transportation efficiency and inclusivity, stakeholders see increased user base and customer satisfaction. Data sharing policies: establish clear policies for data sharing between stakeholders, ensuring privacy and security.
Win/Win: Cities gain valuable data for urban planning, ztakeholders can enhance their services with shared insights. Sustainable mobility options: prioritise sustainable transportation modes such as electric vehicles, biking, and walking.
Win/Win: Cities benefit from reduced pollution and improved public health, stakeholders meet growing consumer demand for green options. Customer-centric approach: design the MaaS platform with a focus on user experience, including easy access, real-time information, and reliable services.
Win/Win: Increased user adoption and satisfaction for stakeholders, cities experience smoother traffic flow and happier residents. Policy and regulatory support: governments can provide supportive policies and regulations that facilitate MaaS implementation.
Win/Win: Ensures that MaaS can operate smoothly and comply with local regulations, providing a stable environment for businesses to invest and innovate. Pilot: start with pilot programs to test and refine the MaaS offerings before scaling up.
Win/Win: Allows cities and stakeholders to identify and address potential issues early on, ensuring a smoother rollout and scalability.

3. Potential issues for the future inclusion of clearing in the current version of the Bologna MaaS can be identified as:

The cost for upgrading the MaaS app for involving a huge number of operators. The establishment of the contract framework and the ticketing management system for the various operators in the MaaS (structure of contracts among various service provider and integration of ticketing systems); The time needed to sort out all the contractual and bureaucratic issues in order to be able to incorporate the integrated ticketing system.

4. Routing logic and nudging strategies are fundamental in MaaS to direct user behaviour and optimise the efficiency of the transport systemMaaS to direct user behaviour and optimise the efficiency of the transport system.
Routing logic:

Multimodal integration: combining different transport modes (public transport, private vehicles, bicycles, walking, sharing, etc.) into a single route and using algorithms to determine the fastest or most convenient combination of transport modes. Use of real-time data: incorporating real-time information on PT traffic conditions, public transport timetables, delays and cancellations and adapting routes in real time according to changing conditions to ensure efficiency and reliability. User preferences and profiles: taking into account user preferences (faster route, less walking, ecological routes, etc.).

Nudging strategies:

Promoting sustainable transport: highlighting routes that use public transport, biking, or walking over private car use and displaying the environmental impact of different route choices to encourage eco-friendly decisions. Park&Ride (P&R) incentives: encouraging users to park outside the city centre and use public transport for the remainder of the journey, showing time, cost savings, and reduced congestion benefits of using P&R facilities. Behavioural nudges: setting the default route to the most sustainable or cost-effective option while allowing users to choose alternatives. Feedback and reminders: offering feedback on travel habits and suggesting improvements, such as reminders to use public transport during peak hours.

What is MaaS?

Hello fellow SPINE OBB members,

I'm Giannis, working with MOBY with a keen interest in the integration of technology in urban mobility solutions. I'm particularly excited about the upcoming workshop on MaaS and looking forward to learning from the case studies and discussions.

One aspect I'm eager to explore is how data analytics can enhance MaaS platforms for better user experiences. I believe this workshop will provide valuable insights into tackling the challenges of implementing MaaS in urban areas.

Looking forward to engaging with you all!

Best,
Giannis