What this is
SpecTrace is an early research-stage project. Right now it is research, not a product: I am trying to understand a specific quality and metrology workflow before deciding whether anything should be built.
This is not a sales call and not a sales page. There is nothing to buy, and I am not claiming to have a finished tool, customers, or proof. I am simply looking to learn from people who do this work.
Who is behind it
Michael Pakyurek is a machine learning and computer vision engineer with experience building data-quality and applied vision systems. He is researching how quality and metrology teams handle inspection documentation through SpecTrace, an early research-stage project focused on understanding the workflow before building a product.
You can confirm who I am here: linkedin.com/in/michaelpakyurek.
The question I am researching
From your experience, which creates more avoidable work: drawing/FAI preparation, matching measurement results back to the compliance package, or something else?
A one-line answer is genuinely useful. There is no wrong answer, and pointing me somewhere I have not considered ("or something else") helps just as much.
Related workflows I am trying to understand
These are areas I am asking about to find the real bottleneck. Listing them is not a claim that SpecTrace addresses any of them.
- Drawing ballooning and GD&T interpretation
- FAI / AS9102 package preparation
- CMM programming and measurement result import
- Matching measurement results back to drawings and the compliance package
- NCR / CAPA / SCAR documentation
- Customer-portal uploads and revision changes
What I will not ask you for
Learning about a workflow does not require sensitive material. A conversation or email exchange about SpecTrace does not require any confidential, ITAR, CUI, export-controlled, or customer-restricted documents, and I will not ask for them. I am interested in how the work flows and where it slows down, described in general terms.
How to reply or refer someone
The easiest way to help is a short email reply to the question above: research@getspectrace.com.
If someone else would have a better view of this work, a referral is welcome. If an email exchange reaches a point where a brief call would be easier, we can arrange one by email — a call is optional and never required.