FAQ
These answers keep the product boundary clear: Quatrion supports first-pass CAD-native review, not replacement of existing engineering systems or final validation.
Answers to common buyer, engineering, security, and pilot-scoping questions.
Questions
Does Quatrion replace CAD tools?
No. CAD tools remain the system of authoring and release. Quatrion is a review and reasoning layer that works with CAD-derived assemblies and returns evidence tied back to geometry.
Does Quatrion replace FEA or CFD?
No. Quatrion can help prioritize which parts, zones, or cases deserve solver attention. It does not replace specialist solvers, material-aware simulation, or engineering sign-off.
Does Quatrion certify compliance?
No. Reference agents may help screen against review criteria, but they do not certify regulatory compliance or replace formal validation.
Can raw CAD stay local?
Yes, Quatrion is designed so raw CAD can remain inside a configured local, on-prem, or private-cloud boundary. Exact topology is reviewed during pilot scoping.
What file formats are supported?
Early-access format support is scoped per workflow. Public site materials reference common CAD exchange paths such as JT, STEP, GLB, IGES, and STL; native CAD paths depend on licensed conversion, deployment constraints, and pilot requirements.
What is first-pass triage?
First-pass triage is an evidence-linked screening step that helps engineers decide where to look next. It is not final validation.
How are findings tied to geometry?
Findings can include part IDs, surface references, measurements, overlays, inputs, tool-chain metadata, outputs, and replay metadata.
Can teams author their own agents?
The SDK preview is intended for teams that want to define custom review agents using manifests, declared inputs, outputs, evidence expectations, and configured tools.
What is available under NDA?
Detailed benchmark methodology, architecture-review material, security boundary discussion, representative evidence, and pilot-specific SDK details can be shared with qualified teams.
How do early-access pilots work?
A typical pilot scopes one assembly, one starting agent, deployment boundaries, required inputs, and evidence expectations. The goal is to show whether the workflow produces review-worthy findings for the team.
Is Quatrion just ChatGPT for CAD files?
No. The agent is connected to model-aware spatial context, deterministic measurement tools, CAD kernel operations, and solver-backed workflows. The value is model-aware action tied to geometry and evidence, not generic text generation over a file name.
Can Quatrion certify final analysis or engineering sign-off?
Not by default. Quatrion exposes trust summaries, confidence grades, and validation boundaries. It is strongest for screening, triage, early design review, and repeatable workflows. A workflow is promoted to sign-off use only when a customer-specific validation program is met.
Where do our models, tools, and agents run?
The architecture is designed around local, on-prem, and cloud Kubernetes paths. Model and provider selection are operator-owned, and services use provider-neutral object and file references. Exact deployment details are scoped with your security team.
Can Quatrion work with our exact PLM or CAD stack?
Quatrion has conversion and GLB/JT-oriented ingestion paths plus service boundaries designed for integration. A pilot should start with one representative model and one workflow before committing to full enterprise PLM coverage.
How accurate are the results?
It depends on the workflow. Deterministic measurements and solver-backed analyses have different validation requirements. Quatrion's stance is to expose confidence, readiness, and failure modes rather than hide uncertainty.