Documentation.

Getting started means connecting SMARTY.cc to a HyperMesh environment you already run, describing a repeatable workflow in plain language, and reviewing the automation SMARTY.cc drafts before applying it.

1. Point SMARTY.cc at the HyperMesh installation and project directory an engineer on your team already uses day to day.
2. Describe the workflow in plain language: what the inputs are, what the outputs should be, and the acceptance criteria that mean the run is correct.
3. Read the drafted automation. SMARTY.cc writes it out as a reviewable sequence of steps, not a black box.
4. Apply the workflow against a small representative model first, confirm the result, then run it at scale.
5. Iterate on the prompt. Small edits to the description usually beat large edits to the generated automation.

For the end-to-end model, see How it works.

You need a running HyperMesh installation your team already uses, engineer accounts for the people who will direct workflows, and at least one documented repeatable workflow that SMARTY.cc can be pointed at. A short prompt describing the workflow and a small representative model to test against are enough to complete a first run.

SMARTY.cc runs against the HyperMesh installation your team already uses. You point it at that installation, describe workflows in engineering language, and SMARTY.cc drafts the corresponding HyperMesh actions for review.

Conversational direction. Workflows are described in engineering language: the meshing operation, the connection type, the load case, the acceptance criteria. SMARTY.cc translates that description into the sequence of HyperMesh actions required to carry it out.

Drafted, not hidden. Automation is presented for review before it runs. Nothing modifies the model until an engineer confirms the drafted steps match the intent. That contract is deliberate and does not change under time pressure.

Engineer review as a gate. Every applied change is attributable to a human engineer who approved it. SMARTY.cc is a copilot; final responsibility for the model, the results, and the downstream decision sits with the engineer running it.

Nothing modifies a model until an engineer approves the drafted sequence. Every applied change is attributable to the human engineer who approved it, and SMARTY.cc-directed actions taken inside HyperMesh are recorded so a reviewer can trace what changed and who signed off. Exact audit-log scope and retention for a specific deployment are set in the written customer agreement; see Security for the shared-responsibility model.

Most first-time issues come from a handful of recurring causes:

• HyperMesh version mismatch. Confirm the version SMARTY.cc is targeting matches the one your team actually runs. Feature availability changes between releases.
• Ambiguous workflow description. If the prompt could be read two ways, the drafted automation will pick one. Rewrite with the specific element type, connection, or load case named.
• Missing acceptance criteria. Without a clear definition of "correct", there is nothing to check the drafted steps against. Add the criteria to the prompt.
• Unsupported element or material type. Some specialty elements are not yet covered. SMARTY.cc will say so rather than guess.
• Units not stated. When units are implicit, drafted automation tends to inherit whatever is set on the current model. State them explicitly for anything that will be reused.

If you hit something not covered here, email hi@smarty.cc or see Support.

Prompts that produce good automation follow a consistent shape: state the goal, list the inputs, name the acceptance criteria, and say what should happen at the review step. Keeping that structure across a team makes drafted workflows easier to review, easier to reuse, and easier to hand off to the next engineer.

The Use cases page maps the workflow patterns SMARTY.cc supports today, including geometry cleanup, standard surface meshing, large-assembly organization, material and property assignment, and solver-deck readiness checks.

Email hi@smarty.cc with your HyperMesh version, the workflow you were running, and what you expected to happen. See Support for the full checklist and informal pilot response targets.

Related: FAQ, Security, Privacy Policy.