Use Case: Resources
In this step of the use case guide, the resource types and instances included in the use case are explored.
You should now see resource instances that were imported at start up, including a microdepot, three receivers, as well as two deliverers. If not, click here.
Resource instances pre-defined in the scenario
To explore the resource instances, click on a resource of the type Receiver. You will now see the different attributes of the resource, such as the street name, the wish-timeframe (wtf), and the city. Some attributes are not filled, as they are optional and not required in this use case.
We will now add another receiver, i.e., a parcel, to our scenario. For this, first copy the value of the wtf attribute of the current instance (make sure to include the curly brackets):
Now, click on Create another Instance on the right, and a form with all available attributes for the resource type Receiver will be displayed. Paste the value to the wtf field and fill in an address. The other attributes, grossWeight, length, and width do not need to be filled. It is advisable to choose an address close to the other instances here as well, for example:
streetName: August-Bebel-Straße
streetNumber: 46
zip: 14482
city: Potsdam
Please note that all adresses in this scenario exist but were drawn randomly and are in no way related to this project, its authors, institutions, etc.
Adding another receiver to the scenario
Now, click on Create Resource and you will be redirected again to the overview of resource instances.
You should now again see the overview of currently configured resource instances, now showing four different instances for the type Receiver. If not, click here.
Of course, you can also further explore the other resource instances, or even add your own resource types and instances by following the steps in the general user guide. If you are ready, you can proceed to the next step.
Last modified 3mo ago
Copy link