Central coordination of UrbANT via clac transport management system

With the web-based software solution CLAC Citylogistik (based in Aachen), neomesh introduces a communication center or management interface through which the UrbANT are controlled.

The data exchange between this interface and the UrbANT is realized via a software interface (Vehicle API) as a live communication channel. Likewise, it serves as the technical (data) basis for the smartphone app via smartphone API.

The UrbANT receive transport orders and can be directed to different geo-positions. In return, each UrbANT regularly sends its current status - also called heartbeat - to the API. This heartbeat contains, among other things, position data, status and current utilization of the vehicles. In addition to the general commissioning of transports, there are also extensive possibilities for fleet management of the UrbANT or other vehicle types. Here, a distinction is made between application scenarios of the follow-on mode and the mobile parcel station. In order to restrict the respective access according to need and right, different user groups are created, which are differentiated between user groups with different rights and functions. For example, corporate customers such as retailers can use fleet management to realize large orders or multiple bookings. It is also possible to determine which UrbANT is used with which loading instrument, which hat attachment is required in the field and whether there is a need for a vehicle association. End users have the option of registering and viewing usage and billing data. Ordered services are then billed through automatically generated invoices and sent digitally from the server.

The user group service technicians, have the possibility for teleoperation, a direct, hardware access to individual vehicles through a remote connection (eg VNC, RDP, WebRTC) for maintenance and emergency access. In this case, a change of position can also take place without a transport order for the purpose of a technical checkup or to assume an ideal waiting position until the next order. The waiting position depends on statistics of evaluated transports as well as on the needs of the users.

In addition to the work and conception of the vehicle API, we have started the development of a Smartphone API. The user authentication via RFID token and PIN has already been completed here. The previous concept of a mobile hub was extended and implemented to realize the mobile parcel locker by a compartment subdivision.