Is there any way for generative scheduling to take into account cross-entity dependencies? For example, requiring shot layout to start only after all assets in that shot have been approved in a particular asset task?
Not sure about the web UI but I can see this being possible if you author an OSF json yourself, as that allows dependencies linking Shot Tasks to Asset tasks, but this would require some massaging of your SG data via api to generate this as an input to gen scheduling.
Although, I can’t yet make sense of the documentation when it comes to describing dependencies and what the syntax actually means or how it affects the dependency link…
Syntax
^[a-zA-Z0-9][a-zA-Z0-9_\-.]*(:(FS|SS|FF|SF)([+\-]?[0-9]+%*)?)?$Examples
"Activity1""Activity2:SS""Activity3:FS-2""Activity4:SS+50%"
https://help.autodesk.com/view/GENSCHD/ENU/?guid=gs-osf#dependency
2 Likes
Hi! Yes this is possible. In Flow Production Tracking, the API can be used to create task dependencies between tasks in different entities and these cross entity dependencies will be carried into Generative Scheduling if they are present.
Alternatively, as @Halil suggested, you can also create these kinds of dependencies when authoring an OSF file. In case it helps, the OSF documentation includes a link to an example OSF that might help with understanding the syntax, you can find it here: https://areadownloads.autodesk.com/wdm/FGS/simple.osf.json
But basically, the syntax for dependencies is activity:dependency_type+offset where the only part that is required is activity. activity is always the upstream dependency in the relationship and can be any type of activity. Tasks, milestones, and summaries (which are what you would usually use to represent shots or sequences) are all activities, so this means that when authoring your own OSF, you are not limited to task → task dependencies, but can instead do things like milestone → sequence dependencies or have a shot where the entire shot has a dependency on some upstream task.
The specific dependency types supported in OSF are described in more detail on this page Help (under the Dependency) section, but the accepted values here are FF, FS, SF, and SS. Offset can be negative or positive and described in days or percentages, so for example Activity4:SS+50% describes an upstream dependency to Activity4, and it’s a start-to-start dependency with a 50% positive offset, so that means the task that contains this dependency in its dependencies can start when Activity4 is 50% done.
Hope that helps a bit!
5 Likes