Last year we founded our German speaking community meetings for FIWARE users and interested peers. Join our impactful group from Germany, Austria, and Switzerland, share your expertise, learn from each other and get impulses and news from keynote speakers.
Being part of the networking group for DACH allows you, together with your peers, networkers and co-creators: develop your business, impact the next developments and use cases, and find new ways of connecting. It is invaluable for finding out what is happening within your industry and geography, and providing new ideas for the future expansion of your core business. Our aim is to create a self-sustainable, growing and impactful group using such meetings for business, as a think tank, best-practise exchanges, and direct involvement.
The very first German-speaking Networking Group (Netzwerktreffen) kicked off on Oct 19 under the SCCON roof with over 50+ participants joining in person followed by food and drinks. You can check the video on our Youtube.
This meeting took place in Berlin TXL: on the site of the former Berlin-Tegel Airport, the Urban Tech Republic, an innovation park with universities, research and start-up centers, and the Schumacher Quartier, a social-ecological model residential quarter, are being built. We are planning a site visit of the Berlin TXL post-use project with FIWARE as a smart city platform.
We covered such hot topics as Open source, Digital twins, Smart cities index, Sustainable development, etc.
2. Ihre Stadt zu einem smarten Lebensraum entwickeln,
der sauber, nachhaltig, sicher, energieeffizient,
lebenswert und leise ist.
Alexander Süssemilch, März 2023
7. c
c
SYSTEM OVERVIEW MOBILITY
7
Functions
(activation,
payment, ...)
Data
(occupancy,
number of X,
...)
1. Frontends/
Use Cases
3. Single services/
infrastructure
2. Cloud
Open Mobility App Smart Mobility Dashboard
Sensors
Charging Stations Parking
Car Sharing
Scooter Sharing
Public transport data
Further traffic data
Urban Data Platforms, Data Spaces
App-Backend Dashboard-Backend
…
1
13. c
c
SYSTEM OVERVIEW MOBILITY
13
Functions
(activation,
payment, ...)
Data
(occupancy,
number of X,
...)
1. Frontends/
Use Cases
3. Single services/
infrastructure
2. Cloud
Open Mobility App Smart Mobility Dashboard
Sensors
Charging Stations Parking
Car Sharing
Scooter Sharing
Public transport data
+ SCHILDER
Further traffic data
Urban Data Platforms, Data Spaces
App-Backend Dashboard-Backend
…
2
17. • Kombination von Services
• Echtzeitdaten
• Mängelmelder
• Personalisierung
• Echte Intermodalität
• USPs ggü. Google Maps
• …
LASST UNS DOCH LIEBER…
18. c
OPEN MOBILITY APP
Aggregation of mobility
services of a smart city
Universal solution for the digitization of the urban mobility ecosystem
A product of the EDAG GROUP
19. c
c
B2C
There are a lot of different
mobility services in one city
B2G
A city has few data, control
options, and end-user
touchpoints
INTERMODALITY
Attractiveness of public
transport through
intermodality difficult to scale
PAINS
19
20. c
c
WHAT WE ARE DOING
20
„We are implementing a mobility app for
non-urban areas.
Every city, every municipality has its own
requirements and wants to implement mobility
ideas independently.
For this purpose, we are developing a modular system
to enable customers to easily put together a
modular app."
21. c
c
WHITE LABEL MOBILITY APP
FUNCTIONS
• Personalized Home-Screen (Dashboard)
• Live Mobility Map (Filtering)
• Route planer
• Integration of 3rd Party Apps (data and functions)
• Booking and payment options
• Account management
SOLUTION
21
22. c
c
WHITE LABEL MOBILITY APP
APPROACH
WHITE LABELING FRAMEWORK
OPEN SOURCE POSSIBILITIES
JOINED DEVELOPMENT BETWEEN SMART CITIES
COMMUNITY MANAGEMEND
MOBILITY AND CITY STANDARDS (MDS, FIWARE, OICP, …)
SUPER APP APPROACH
SOLUTION
22
26. c
c
26
OPEN SOURCE STRATEGY
Public Money, Public Code
FRAMEWORK DEVELOPMENT BY EDAG
(at the moment not public money)
Single services can then be financed by
cities (connection of XYZ). These will be
published as independent libraries and
can be used by other apps and services.
Open Standards
(FIWARE, Mobility Data Specification
from google, Charging, …)
30. c
c
Gemeinsam mit Städten, deren Bewohner:innen und den richtigen
technischen Lösungen die Zukunft der Städte gestalten
31. c
Questions for us? Suggestions for us?
Start the most important dialog of the day!
Contact
c
T +49 661 6000 25854
M +49 170 9214924
E alexander.suessemilch@edag.com
L https://www.linkedin.com/in/asuessemilch/
Alexander Süssemilch
Head of Connected
Mobility Services
@EDAG Group
Reesbergstraße 1 - 36039 Fulda - www.smartcity.edag.com
31
Editor's Notes
Call bus:
Rufbus: Feste Linie nach Fahrplan, fährt aber erst los wenn jemand anruft
Es gibt zwar ein Time tabel, aber erst wenn jemand bucht.
Story: Vorher analog per Telefon am Landratsamt, jetzt digital per App buchen und perspektivisch auch bezahlen
Technologien: NodeJS im Backend, React im Frontend (Redux, MUI); Standards: Trias (S-Schnittstelle für den öffentlichen Nahverkehr (900 Seiten)); Nano-Services (Run micro)
Mediation: Daten von allem möglichen (Bahn, Verkehrsverbünde, Usern, 3rd Party Services,
Datenbasis für: Routing-Vorschläge, Auswahl von Mobilitätsformen
Verkaufsargument: Zentraler Datenzugriffspunkt für Smart City Services mit Berechtigungsprüfung und Datenschutz. Schnittstelle zur
Quelle: https://www.merkur.de/bayern/nuernberg/nuernberg-vgn-star-wars-tarifzone-karte-ubahn-sbahn-sternenkarte-coruscant-91592402.html