See the process unfold
Inspect shape and progression beyond a final measurement.
Process curves & comparisons
What does the shape of a process tell us that a single result cannot?
Keep the measured curve with the product record, so engineers can compare how a process unfolded instead of relying only on its final value.
A practical path from evidence to action
- Record the curveProduct and process context
- Choose a comparisonCompatible curves or a reference
- Inspect shape and alignmentCoordinates, metrics and limits
- Review the differenceEngineer-led interpretation
Compare like with like
Choose the coordinate and alignment basis deliberately.
Preserve the reference context
Review the reference associated with the relevant process definition.
Two results can finish at the same value and take different paths.
A force, pressure or motion profile may reveal behavior that a single summary measurement cannot explain. IntelliTrack™'s curve workflows keep that evidence available for comparison, with the product and recipe context needed to interpret it.
How it works in IntelliTrack™
Capture the profile, then choose a defensible comparison.
Store the curve with context
Capture the supported curve data with the relevant product and process record.
Compare compatible profiles
Compare up to four curves of the same kind. Select the supported coordinate basis and alignment that fit the question.
Review the evidence and reference
Inspect the differences and applicable metrics or limits. Where configured, use deterministic similarity to find related two-dimensional curve patterns.
Illustrative manufacturing scenario
A press-fit passes its endpoint but looks different in the middle.
Engineering compares the recorded curve with other units and an applicable reference. The team examines where the shape differs before deciding whether to check tooling, materials or the setup.
Curve comparison
What you can inspectCompatible profiles displayed on a selected coordinate and alignment basis.
Your team's decisionDecide whether the apparent difference survives a fair comparison.
Reference and limits
What you can inspectThe relevant recipe reference and configured evaluation context.
Your team's decisionAssess the result against the intended process definition.
Optional similarity investigation
What you can inspectRelated compatible two-dimensional curve signatures and their production context.
Your team's decisionChoose examples for investigation without treating similarity as proof of a cause.
Keep the comparison meaningful.
- Capture the right coordinate values, sampling and units. Comparing profiles with different meanings or sampling assumptions can mislead the review.
- Reference changes belong to controlled recipe revisions. The applicable instance preserves its reference context; changing a reference is not a retroactive regrading of production.
- Deterministic similarity requires the relevant Insights functionality and compatible two-dimensional signatures. Optional AI narration is separate and requires its configured provider.
Practical questions
What to know before you start.
How many curves can we compare?
The comparison workflow supports up to four curves of the same kind. Select comparable products and conditions, then use the coordinate and alignment options that answer your engineering question.
Can we change how the curves align?
Supported options include native or sample-based coordinates, normalized X where applicable, and alignment such as start, peak or threshold. Explain the selected basis when interpreting differences.
Does similarity search need an external AI provider?
The supported deterministic similarity workflow uses compatible two-dimensional curve signatures through Insights. An external provider is needed only for optional assisted narration, not the underlying similarity calculation.
Does two-dimensional similarity apply to every 3D path or surface?
No. Curve visualization capabilities and the two-dimensional similarity workflow have different scope. Evaluate the exact data type you want to capture and compare.
Will changing a reference change historical pass/fail results?
A new reference belongs to a controlled recipe revision and its applicable instance context. It does not automatically rewrite historical verdicts. Review any re-evaluation requirement as a separate controlled activity.
Bring a curve your engineers know how to interpret.
A representative passing curve and a questionable result make a useful starting point for reviewing capture, comparison and reference requirements.