Asset Dependency Graph
What it does
When caches, rigs, or published assets feed other shots, the pipeline tracks ElementLineage edges (parent PEID consumed by child PEID). Three surfaces use reverse and forward lineage:
- Where used - from any element, see which shots/elements consume it (grouped by show).
- Incoming dependencies - on a shot, see upstream published elements this shot pulls in.
- Ripple alerts - when a lead publishes a new version, downstream assignees get an inbox note.
How to read Incoming dependencies
- Current - your work links to the same version that is published now.
- Outdated - you still reference an older PEID; a newer version is published upstream. Re-pull.
- Not published - upstream exists but no lead has published a canonical version yet.
What to do
On outdated rows, open the upstream graph, pull the published version in your DCC, and re-save. Producers can open Where used before approving a publish to see blast radius.
Overview
Where-used, incoming dependencies, and publish ripple alerts via PEID lineage.
Steps
- Read the sections above.
- Use Try it now buttons to open the live page.
- Ask your lead or HR if something does not match your studio setup.
Gotchas
- Your role may not see every link - module config and license entitlements apply.
- See How Metrics Are Derived if a dashboard number looks wrong.
Cross-links
- Published Versions & Dependencies - see Help Center
- Provenance & Lineage Graph - see Help Center
- PEID-3 Cost per Element - see Help Center
Try it now - opens live in your studio