In a typical iteration of an optimisation task, an optimiser tenant posts a request for a certain quantity. Requests must specify only one quantity but may include a list of acceptable methods. According to the multitenancy approach, several tenants may therefore be allowed to serve the request. This enables an improved use of instruments and resources as the earliest available tenant will process a request accepting its method. However, this requires the tenants to mark the request as reserved prior to start processing it, to hinder other tenants from picking up the same request. Once a tenant picked up the request and marked it as reserved, the relevant method of the tenant is executed and the results are posted to FINALES after formatting them according to the applicable output schema. An optimiser tenant may subsequently check for new results and generate a follow-up request starting the next iteration.