# Use Case: Allocation

After exploring the resources, optimization algorithms, and recipes, it is now time to actually perform a resource allocation, in this scenario, the generation of a *Tour* resource which includes a link to a deliverer.

To request an allocation using the user interface and not the API, go to **Recipes** using either the navigation bar at the top or the main menu at the top right. Click on one of the recipes.

{% hint style="info" %}
If you have created your own recipe following the [guide in the previous step](https://rembrandt.gitbook.io/docs/use-case-optimization#bonus-create-your-own-recipe), you can of course also use this new recipe!
{% endhint %}

On the right-hand side, you will find an **Actions** section, click on **Execute this Recipe**. A popup on the top right will notify you that the recipe has been started and that you have been redirected to the page of this execution.

![An unfinished execution of a recipe](https://2302517564-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LeJ6kGUyZS2zT96wHZ3%2F-MctebOLcagKkdNzqv02%2F-MctfqqrkZYw4cFjCt9f%2Fgrafik.png?alt=media\&token=77f677e2-d7b3-4ff1-813f-7a7ab7b17e82)

Most probably, the page will indicate that the execution was not yet completed. in the section **Ingredient States** you can see which parts of the recipe were already executed. If an error occurred, the erroneous ingredient will be marked here as well. Refresh the page to check if the execution succeeded by now, indicated by `Finished successful` and `100%`.

{% hint style="danger" %}
In case you see `Execution failed`, it will most probably be at the *algorithm* ingredient. In this case, make sure that you have performed step three of the [use case set-up](https://rembrandt.gitbook.io/docs/set-up#getting-started).
{% endhint %}

As soon as the execution of the recipe as successfully terminated, the **Actions** section at the right will yield a new button **View Result**. Click on this button, and you will be redirected again to the overview of resource instances, now filtered by the execution, i.e., only resources that resulted from the recipe execution are shown. In this case, a single *Tour* instance should be listed.

![Overview of resource instances that resulted from the recipe execution](https://2302517564-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LeJ6kGUyZS2zT96wHZ3%2F-MctebOLcagKkdNzqv02%2F-Mcti3GJdNQkFWEiC8cL%2Fgrafik.png?alt=media\&token=722feac8-ecad-4ab8-bf8c-1d88bf505a3e)

You can now click on this instance to explore the attributes of the tour. For example, you can see that the tour consists of four parcels, that a certain deliverer has been assigned (*tmsCarrierId*), and that even a link to map with the tour has been added (*visualization*) that you can open and view.

### Goodbye!

Hopefully, this small guide has shown you the different functionalities of Rembrandt. If you are now interested in creating your own scenario, you can use the guides on the left to discover the [general workflow](https://rembrandt.gitbook.io/docs/user-guide-1/user-guide) with Rembrandt and all presented concepts of Rembrandt in more detail. If you want to create your own optimization docker algorithm, you can use [this guide](https://rembrandt.gitbook.io/docs/contributing-1/optimization-container).