solution Use Case

Production Event Management (5) – manage resource conflicts (DataMiner SRM)

This is the fifth use case in an 8-part series on Production Event Management. The previous example showed how DataMiner can help you manage your production life cycle. In this part of the series, you’ll learn how DataMiner SRM (Service and Resource Management) can help you identify, manage and resolve resource conflicts using the out-of-the-box quarantine feature.

This is the scenario of our use case: a user schedules studio productions ahead of time. This means DataMiner will have to assign the resources that are required for the production. This could be done either fully automatically or manually; the latter is the case in our example.

DataMiner will only allow resources to be assigned if they are available at the scheduled time and if they have the right capabilities (e.g. for a UHD production only UHD resources will be considered by DataMiner). It is perfectly fine to schedule the same resources for subsequent productions. In our example, those are graphics machines (called GFX resources).

Now, let’s assume that two productions have been scheduled back to back using the same GFX resources, but suddenly it is decided that the second production should start earlier. Unfortunately, this leads to a resource conflict.

However, DataMiner has all you need to manage and fix such resource conflicts. DataMiner SRM will put the second production into “quarantine” to indicate that this production cannot be orchestrated as originally scheduled because the double-booked GFX machines are causing an issue.

To solve this problem, you could either select different resources that are available for your upcoming production, or you could finish the first production early. After choosing one of these options, you can release the second booking from “quarantine”.

Let’s have a closer look at how this works in DataMiner:

Leave a Reply