We would like to have a clear view of transit times in Rapido, in order to ensure an efficient user experience, optimize internal workflows and enable accurate calculations of the various relevant dates.

To assess these service times, it is important to define the topology for which the solution is being proposed: We will assume two universities (UniversityA and UniversityB) participating in a Rapido pod. Each university has a central point (branchI and branchJ), which is the only branch responsible for handling shipments. In addition, each university has many other branches.

The total time from when a user at UniversityA (associated with any given branch) submits a request for an item held at UniversityB (in any given branch), until the document is delivered, can be divided into five sub-times (T1 + T2 + T3 + T4 + T5), as follows:

• T1: Time from when the user places the request until the staff at University_A retrieves the item and prepares it for shipment.

• T2: Time it takes for the item to travel internally from the owning branch at UniversityA to the central dispatch branch (branchI). This is relevant for the internal logistics of the lending institution.

• T3: Time from the central dispatch point at UniversityA (branchI) to the central receiving point at UniversityB (branchJ). This is the inter-institutional transit time, and it is defined in the Rapido pod settings as "Delivery Time". This time is essential for calculating both the Lending Due Date and the Borrowing Due Date.

• T4: Time from the central receiving point at UniversityB (branchJ) to the branch where the user is located. This reflects internal distribution within the borrowing institution. The default pickup location is the final point where the user will collect the document, and this includes any processing time from when the item arrives at the central point until it becomes available to the user.

• T5: Time from when the item arrives at the user’s branch at University_B until the loan is actually performed and the item is checked out to the user.

Obtaining these five time components in a single report would require accessing data from three different Analytics Subject Areas:
- Borrowing Requests (Resource Sharing)
- Lending Requests (Resource Sharing)
- Physical Items Historical Events

We believe it would be highly beneficial if Ex Libris could create an out-of-the-box report that combines this information. We really believe this would be very useful for many consortia, and we encourage Ex Libris to consider developing such a report.