Handling Seated eScooters

Seated escooters can look like scooters, or look like bikes, which can affect model performance. Additionally, different locations can apply parking regulations based on scooter, ebike, or seated scooters.

Recommended approach:

Consider a seated eScooter as the eScooter or eBike asset type where possible, to minimise configuration management tasks. Specifically when:

• The seated escooter looks like an existing vehicle:
  • escooter (small-medium wheels + an added seat) → escooter assetType, or
  • ebike (medium-large wheels, no pedals) → ebike assetType
• AND The parking rules align to that of escooters & ebikes, respectively

Additional reporting and benchmarking can be enabled through record metadata.

❗️

Using the wrong assetType can lead to model issues that directly affect the end-user ability to end the ride

Additional seated eScooter assetType

If that is not possible, locations can be configured with escooter, ebike AND seated escooter parking rules.

Records can then be submitted using the seatedEScooter assetType.