Entities

Basic entities

The Movens platform handles the requests from the users and the trip execution via three main entities:

• A Transportation Request (shortened TR) represents the need of the user to go from a location to another.

  It contains at least the date/time and place of departure, and depending on the mobility services that are activated on Movens, the date/time and place of arrival.

  Filters may be added to the TR to ensure the platform only provides for specific service matches.

• A Movement Authority (shortened MA or MovAuth) represents the response of the platform to a TR.

  The platform usually proposes many candidate MovAuths to the TR of an user; when the user confirms one (or many) MovAuths, these become confirmed MovAuths, also called reservations.

  MAs contain the date/time and place of actual departure and arrival, as well as many other per-service details that may indicate further data (e.g. access codes, vehicle numbers/plates, bluetooth communication keys, etc.).

• A Trip represents the actual trip itself.

  This entity is created and shared among all involved parties (platform, smartphone apps, on-board devices) at all times during the trip itself.

  The Trip entity gets augmented with events and data provided by the devices, and the platform makes sure all events are processed and all data is coherent before sanctioning the entity as confirmed.

  A confirmed Trip is ready for billing and is not expected to change anymore.

The Community System

Inside Movens, users can be linked to a number of communities, that represent the hierarchical structure for user management.

A Community may have a distinct logo and colors, that can be shared with the smartphone apps to further enhance the UX.

The Community tree is managed inside of the Administrator WebGUI, and can help in partitioning tariffs, promotions and other functions.

The Group System

Users and transportation resources can be made part of homogeneous groups, that are the main rule making-and-matching system inside Movens.

Groups are not related to the hierarchical structures (e.g. communities, categories, etc), and an entity can belong to many groups. For example, a single User may belong to a “generic” group and to a “under 26” group, and also to a “student” group.

The Administrator is responsible for setting sharing rules based on groups to limit and allow access to the resources by the various user groups.

Sharing Rules

The Sharing Rules link a specific user group to one or more resource groups from a transportation service module. With these, the Administrator can allow the usage of different resource groups to different users.

Availability and Movement Rules

The Availability and Movement Rules can be used to allow/deny the usage of a resource group in a transportation service module.

With the Availability Rule the Administrator can limit the usage of the resources of a group to the specified time range. Multiple Availability Rules set on the same resource group allows the usage of the group’s resources to multiple time range.

With the Movement Rule the Administrator can allow or deny the resources of a group the usage on a specified zone. The single rule can specify also a time range in which the rule has effect, but it is not mandatory. An allow rule is required for the resources of a group to use a movement zone.

License Documents

The License Documents are any kind of document that allows a user to use a specific mean of transportation (i.e. driving licenses, season passes, public transportation tickets).

To be able to place a reservation on a vehicle and start the related trip, the user must have a valid license document for this kind of transportation.