The tenant is capable of processing reservation requests for cycling channels and handling the tests including the creation of a protocol, start and stop of the test, logging of errors, exporting and saving the data as well as performing selected analyses. To fulfil its tasks, it is registered in FINALES with the quantities cycling channel and capacity with the corresponding methods service and cycling. The cycler saves the status, errors, parameters and the request of each individual channel in a JSON document and consequently is resistant to planned and unexpected stops. The tenant performs an intermediate export of the capacity trajectories after the duration estimated for at least 40 cycles elapsed. The exported data are subsequently processed by the analysis functionality and posted to FINALES. The experiments continue and are stopped once 200 cycles are finished. A final export is triggered after the estimated time required for 200 cycles elapsed. Since the optimisation of the EOL is based on the predicted EOL, the data obtained from the final export is not posted to FINALES, but stored locally. Details regarding the Cycler tenant can be found in section SI-2.4.