Service description of the TBDS Outbound Order Book service

1. display transport and service orders via the RIO platform;

2. transmit both transport and service orders via an API interface provided by TBDS; and

3. execute, manage and track/monitor transport and service orders by adding status messages to an order, such as the current position of a transport vehicle.
   

In addition, the User of the TBDS Outbound Order Book service must have established a contractual relationship or a similar legal relationship with a client (freight payer) named in Section 4.2 of this service description, which continues during the use of the TBDS service.

If the User wishes to make full use of the functional scope of the TBDS Outbound Order Book service and also to have the position of a vehicle transmitted to the client (freight payer) as part of the transport status message, the User must either

1. register its vehicles equipped with telematics hardware in the RIO administration area and book the TBDS service “Geo” for these vehicles via the RIO Marketplace;
   or

2. register their vehicles that are not equipped with telematics hardware in the RIO administration area, also activate the use of the RIO Pocket Driver app for these vehicles and book the TBDS service “Geo” via the RIO Marketplace.

Technical prerequisites for using the TBDS service
Technical prerequisite for using the TBDS Outbound Order Book service via the web front end is an internet-capable computer (this is not provided by RIO) on which an up-to-date operating system and a current web browser are installed. TBDS recommends using the following web browsers: Google Chrome, Mozilla Firefox or Microsoft Edge. Unfortunately, TBDS cannot guarantee unrestricted functionality of the TBDS service if other web browsers are used than those mentioned above.

For the transmission of transport and service orders, TBDS provides you with a so-called REST API (application programming interface) with which you can communicate with your client (freight payer) on a service2service basis. To use this REST API, you require a user/client ID and associated login information, which you will receive from TBDS via your RIO platform user account after booking the TBDS Outbound Order Book service. The message format used for data exchange between you and your client (freight payer) via REST API is the VDA/Odette/ECG standard: “Finished Vehicle Logistics” FV14a, FV14b, FV17, FV18 on xml basis. The exact message specification will also be provided to you by your client (freight payer) after booking the TBDS service.

Miscellaneous

1. Archiving and deletion of transport and service orders
   Transport orders and service orders are archived 30 days after completion of an order or 180 days in the event of order continuation (i.e. no order completion so far) and automatically deleted by TBDS 12 months after archiving, and are therefore no longer available to you in your RIO platform user account.

2. Current clients (freight payers)
   TBDS currently cooperates with the following customers (freight payers):
   
   Client (freight payer)
   Volkswagen AG
   Berliner Ring 2
   38440 Wolfsburg

3. Information on the exchange of data between TBDS and your client (freight payer)
   Detailed information on the exchange of data between TBDS and your client (freight payer) can be viewed and downloaded in the data protection notice for the TBDS Outbound Order Book service on the RIO platform’s Marketplace at the web address https://rio.cloud/de/documents/outbound-order-book/privacy-policy.