Integration Capability

Integration Capability layer

It shows how easy/hard each app is to integrate.

GEMINI Munich PoC App

🔧 Ease of Integration: 3 / 5

⚠️ Challenges: Parking data provider APIs may be missing; data mismatches

🔗 System Compatibility: Depends on alignment with MLL backend

👨‍💻 Tech Expertise Required: High

🛠️ Maintenance Difficulty: Medium

📝 Notes: Requires knowledge of traffic management systems and DevOps.

BlueFlow

🔧 Ease of Integration: 3 / 5

⚠️ Challenges: Ticket system compatibility; data privacy constraints

🔗 System Compatibility: Requires custom connectors for legacy systems

👨‍💻 Tech Expertise Required: High

🛠️ Maintenance Difficulty: Medium

📝 Notes: Needs GDPR compliance and OAuth management.

HSL Route Planner

🔧 Ease of Integration: 5 / 5

⚠️ Challenges: Minimal (public APIs are stable)

🔗 System Compatibility: Fully compatible with MLL ecosystem

👨‍💻 Tech Expertise Required: Low

🛠️ Maintenance Difficulty: Low

📝 Notes: Preferred integration platform for new services.

Bosse Route Planner

🔧 Ease of Integration: 4 / 5

⚠️ Challenges: Limited to Finnish municipal ecosystems

🔗 System Compatibility: High in local context

👨‍💻 Tech Expertise Required: Low

🛠️ Maintenance Difficulty: Low

📝 Notes: Well-suited for deployment within local and regional public transport environments.

Clem.mobi

🔧 Ease of Integration: 3 / 5

⚠️ Challenges: Proprietary API and platform dependency

🔗 System Compatibility: Medium

👨‍💻 Tech Expertise Required: High

🛠️ Maintenance Difficulty: Medium

📝 Notes: Custom code exchange required for offline access.

Goodmoves APP

🔧 Ease of Integration: 3 / 5

⚠️ Challenges: Integration of invoicing systems and IoT parameters

🔗 System Compatibility: Medium

👨‍💻 Tech Expertise Required: High

🛠️ Maintenance Difficulty: Medium

📝 Notes: Uses ERP (Odoo) with custom modules.

Parkin Saclay

🔧 Ease of Integration: 4 / 5

⚠️ Challenges: GBFS vs custom protocol alignment

🔗 System Compatibility: High

👨‍💻 Tech Expertise Required: Medium

🛠️ Maintenance Difficulty: Low

📝 Notes: Benefits from standardized GBFS data, but may require adaptation when integrating with custom operator protocols.

IDFM

🔧 Ease of Integration: 4 / 5

⚠️ Challenges: Integration of public and private mobility data

🔗 System Compatibility: High

👨‍💻 Tech Expertise Required: Medium

🛠️ Maintenance Difficulty: Medium

📝 Notes: Requires coordination between multiple mobility operators and data providers.

Dott

🔧 Ease of Integration: 3 / 5

⚠️ Challenges: Varied file formats, mapping differences, scalability

🔗 System Compatibility: Depends on city platform

👨‍💻 Tech Expertise Required: High

🛠️ Maintenance Difficulty: Medium

📝 Notes: Standardization needed for smoother integration.

Keppler

🔧 Ease of Integration: 4 / 5

⚠️ Challenges: Not designed as a transport integration tool

🔗 System Compatibility: High (for analytics use)

👨‍💻 Tech Expertise Required: Medium

🛠️ Maintenance Difficulty: Low

📝 Notes: Well suited for mobility data analytics and visualization, but not intended for direct integration with operational transport systems.

OnzeAuto by GoodMoovs

🔧 Ease of Integration: 4 / 5

⚠️ Challenges: Backoffice and hardware integration complexity

🔗 System Compatibility: High with supported OEMs

👨‍💻 Tech Expertise Required: High

🛠️ Maintenance Difficulty: Medium

📝 Notes: Requires onboarding and technical setup support.

MooneyGo

🔧 Ease of Integration: 4 / 5

⚠️ Challenges: Payment systems and legacy integration

🔗 System Compatibility: High with modern platforms

👨‍💻 Tech Expertise Required: Medium

🛠️ Maintenance Difficulty: Medium

📝 Notes: Requires integration with existing payment infrastructures and transport operator systems.

Gemini (Turin)

🔧 Ease of Integration: 3 / 5

⚠️ Challenges: Inherited from MooneyGo; regional customization needed

🔗 System Compatibility: Medium

👨‍💻 Tech Expertise Required: Medium

🛠️ Maintenance Difficulty: Medium

📝 Notes: Requires adaptation to regional transport systems and local operational requirements.