Engine Prep
Import from native and neutral formats, heal broken geometry, normalise units and structure, and build the clean model everything downstream depends on.
- Import & translation
- Geometry healing
- Simplification & defeaturing
Engine Suite is a modular platform for pre- and post-validation of manufacturing. It prepares a design model, runs your engineering rules against it, carries the results through simulation and inspection, and produces the evidence an engineer can sign their name to.
In most engineering teams the checks exist — in a checklist, a spreadsheet, a macro someone wrote years ago, and in the heads of two senior engineers. The knowledge is real. It just is not repeatable, and it does not travel with the model.
Engine Suite makes the same checks executable. The rules become configuration, the run becomes a record, and the outcome becomes a document — with the 3D evidence attached to it.
Geometry health, manufacturability and standards compliance, checked automatically on every revision instead of at the end.
Measured and scanned data compared against nominal, with deviation reported in the same language as the design intent.
Each module is useful on its own and stronger in sequence. Everything they produce writes back to a single project record, so nothing is stranded in a file on someone's desktop.
Import from native and neutral formats, heal broken geometry, normalise units and structure, and build the clean model everything downstream depends on.
Your engineering standards expressed as executable rules, run over a part or a whole assembly with findings pinned to the geometry that caused them.
Hand-off to your simulation stack — model preparation, batch runs and parametric studies driven from the same project, without re-keying inputs.
A fast 3D review environment for large assemblies, with measurement, sectioning, comparison and markup that non-CAD stakeholders can use.
Documents generated from the run itself — findings, 3D snapshots, measured values and approvals — in the template your customer or auditor expects.
The connective tissue: CAD and PLM hooks, shop-floor and inspection data in, and APIs so the suite fits the toolchain you already run.
A typical Engine Suite cycle, whether triggered by an engineer or by a release event in your PLM.
Every step is recorded. Model revision, rule set version, who ran it and what was waived — so a result from six months ago can still be explained.
The model arrives from CAD, PLM or a watched folder and is prepared automatically.
The applicable rule set runs; findings are classified by severity and attached to geometry.
Engineers examine findings in 3D, accept, waive with reason, or send back for change.
Simulation results and, later, measured data are compared against the same intent.
Evidence is compiled, approved and released to whoever needs it — internal or customer.
Engine Suite is not a replacement for your CAD, PLM or solver. It sits between them and does the part none of them do well: making engineering judgement repeatable.
Deployment, integrations and rule sets are configured per customer during onboarding — the suite ships with a working baseline and is tuned to your standards from there.
Problems found at the model stage instead of on the shop floor, where they cost tooling time and rework.
Senior engineers' judgement captured as rules the whole team runs — and that survives people changing roles.
Reports generated from actual runs, with traceability back to the exact revision and rule set used.
The same checks applied across sites, suppliers and product lines, regardless of who prepared the model.
Reviewers see findings in 3D with context, instead of reconstructing the issue from a screenshot in an email.
Once checks are executable, they can run on every release — unattended, on your infrastructure.
The fastest way to judge it is to run it against a part you already argue about. Send us a representative model and the checks you care about, and we will walk you through the result.