This page outlines the technical requirements to integrate with Lanterne’s operations management solution.

1. Data streams

<aside> 💡 We need to be able to read trips and live vehicles data. If you have MDS 1.0 or greater implemented, the easiest solution would be to use that as it contains all required information.

</aside>

1.1. Trips data

<aside> 📈 We need trips data to run our demand prediction models and make rebalancing recommendations accordingly.

</aside>

The following information should be included in the data:

• Start time
• End time
• Start location
• End location

The format can be according to the MDS trips endpoint or a similar format.

mobility-data-specification/provider at main · openmobilityfoundation/mobility-data-specification

1.2. Live Vehicles data

<aside> 🛴 We need live vehicles data to know about the current position and state of vehicles in order for our sytem to automatically create the appropriate tasks for those vehicles.

</aside>

The following information should be included in the data:

• Static vehicle id / qr code (Note that a rotational id, like provided through GBFS, is not sufficient)
• Battery level
• Vehicle location
• Time last connected to server