Velocity charts are dashboard widgets that plot cumulative counts over time for a BOM subtree: parts created, parts released, and purchase orders matched to that BOM. Each chart is anchored to a root part.
You can now anchor a velocity chart by typing a part number, instead of picking one exact entity and application. Search for the part number in the chart's search field and select it from the results.
When the same part number exists in more than one connected PLM system, Violet resolves the anchor automatically:
It picks the application whose copy of the part actually has BOM children, since that is the one with real assembly data to chart.
If more than one application has BOM children (or none do), it breaks the tie using a fixed priority order of PLM systems: SolidWorks PDM, Duro, Ion, Arena, Teamcenter, Windchill, Aras, then Enovia.
The part number picker shows the application each result resolves to, so you can confirm which BOM the chart will use before saving.
If a chart still references an exact entity and application from before this change, it keeps working unchanged. You only need a part number going forward.
If no Part matches the number you entered, the chart run fails with an error telling you no Part was found for that number, with a suggestion to check the part number.
Velocity charts that track "POs created" now also count purchase orders that are matched through their PO Lines, not just POs matched directly. A PO Line's part number rolls up to its parent PO, so the chart reflects matches found on either the PO Line or the PO Line's part number.
