Straight answers about the HyperMesh copilot.
SMARTY.cc is an AI copilot for HyperMesh engineering. It lets engineers describe workflow tasks in plain language and helps translate that intent into repeatable HyperMesh actions and automation. Engineers remain responsible for reviewing and validating every output.
- AI copilot designed for HyperMesh engineering workflows
- Natural-language direction instead of manual menu navigation
- Intended to reduce repetitive model-preparation work
- Works with, rather than replaces, your HyperMesh environment
- Engineers review and validate every output
- Not the same product as SMARTIES.ai
Frequently asked questions.
- Q.01
What is SMARTY.cc?
SMARTY.cc is an AI copilot for HyperMesh engineering. It adds a conversational layer to HyperMesh so engineers can describe a task in plain language and have that intent translated into inspectable workflow actions and automation. It is not a simulation solver, not a replacement for HyperMesh, and not an autonomous engineering authority. The qualified engineer stays in control and validates the result.
- Q.02
Is SMARTY.cc the same product as SMARTIES.ai?
No. SMARTY.cc and SMARTIES.ai are separate products. SMARTY.cc is the AI copilot for HyperMesh engineering, available at smartie.cc. SMARTIES.ai is a different product aimed at small-business automation. They share no feature overlap and should not be confused.
- Q.03
Does SMARTY.cc replace HyperMesh?
No. SMARTY.cc works with HyperMesh, not instead of it. HyperMesh remains the core engineering environment. SMARTY.cc is positioned as the conversational automation layer that sits on top of the HyperMesh environment your team already runs, using HyperMesh's own programmable interfaces to execute actions. See how it works for the end-to-end model.
- Q.04
What kinds of tasks can SMARTY.cc help with?
Internal product materials describe assistance across geometry cleanup, part classification and organization, surface and solid meshing, material and property assignment, solver deck preparation, mesh quality checking, workflow scripting, and engineering report generation. The intended pattern is the same in every case: describe the task in natural language, let SMARTY.cc map it to the appropriate HyperMesh actions, then review the result before accepting it. Full worked examples live on the use cases page. Exact command coverage and supported workflow scope should be confirmed with the SMARTY.cc team for your specific HyperMesh version and solver profile.
- Q.05
Can SMARTY.cc help with geometry cleanup before meshing?
Geometry cleanup assistance is part of the internally documented product concept. Potential tasks include identifying geometry defects, suppressing or repairing problem features, and applying predefined cleanup criteria repeatedly across a part family. The exact commands available and any workflow limitations should be confirmed with the SMARTY.cc team before production use.
- Q.06
Does SMARTY.cc generate Python scripts?
SMARTY.cc is intended to translate engineering intent into automation, and HyperMesh provides extensive Python APIs that support that approach. Exact script-generation behavior, how generated scripts are presented for review, and how they are executed must be confirmed for the current release. Treat any generated script as a draft and validate it against your known workflow before applying it to a production model.
- Q.07
Which solvers does SMARTY.cc support?
Supported solver profiles are not confirmed in currently available materials. Do not assume support for any specific solver. Provide your solver profile to the SMARTY.cc team and ask them to verify compatibility. SMARTY.cc should not be described as a simulation solver or physics engine in its own right.
- Q.08
Which HyperMesh versions are compatible?
Supported HyperMesh versions, including whether both Altair-branded and Siemens Simcenter Hypermesh releases are covered, are pending confirmation. Compatibility can also depend on the operating system, Python version, and deployment environment. Share your environment details with the SMARTY.cc team to get a direct answer.
- Q.09
Does SMARTY.cc work on premises or in an air-gapped environment?
Internal planning materials recommend exploring air-gapped and on-premises deployment options, but those deployment modes are not confirmed as currently available. If your organization has air-gap, private-cloud, or data-residency requirements, escalate the question directly to the SMARTY.cc product and security team rather than relying on a general answer.
- Q.10
Is SMARTY.cc SOC 2 certified?
No certification has been confirmed. Internal strategy materials recommend beginning SOC 2 readiness work, but a recommendation to pursue certification is not the same as holding it. Do not treat SMARTY.cc as SOC 2 certified based on available information. Direct security and compliance questions to the SMARTY.cc team for current documentation.
- Q.11
Will my model data be used to train AI models?
This is not confirmed in currently available materials. No commitment about data retention, zero-telemetry, or training-data policy should be taken from this page. The SMARTY.cc team can provide current data-handling terms for your specific implementation once deployment architecture is established.
- Q.12
Does SMARTY.cc guarantee correct engineering results?
No. SMARTY.cc assists with engineering workflows. The engineer and the engineer's organization remain responsible for validating all model changes, mesh criteria, material and property assignments, contacts, loads, boundary conditions, solver settings, and final outputs. SMARTY.cc should be used as an engineer-controlled assistant, not as a certification authority or autonomous decision-maker. See the security model for how review and audit are enforced.
- Q.13
Will SMARTY.cc replace engineers or scripting specialists?
No. SMARTY.cc is intended to reduce repetitive setup work and make engineering automation more accessible to domain experts who do not want to write every script manually. Automation specialists continue to handle architecture, complex integrations, testing, and governance. The goal is to expand who can participate in automation, not to eliminate the people who run it.
- Q.14
Can SMARTY.cc help junior engineers follow approved processes?
That is a described use case. SMARTY.cc can make established procedures easier to follow and explain, helping newer engineers apply team standards consistently. It should not replace training, supervision, or foundational engineering judgment. A junior engineer using SMARTY.cc still needs a qualified reviewer to validate outputs.
- Q.15
How do I run a first pilot?
The recommended starting point is a single, narrow, repeatable workflow with clear acceptance criteria and a known manual baseline to compare against. Good first pilots often map to one of the mapped use cases: mesh-quality checking and exception reporting, standard part naming and classification, controlled geometry cleanup on a familiar part family, or a pre-export readiness checklist. Walk through how the workflow runs before you start. Use sanitized or non-production model data until security and deployment details are confirmed. Run the workflow with an experienced engineer present, compare SMARTY.cc output against the manual result, and only approve the workflow for broader use after validation. To scope one, contact the team.
- Q.16
What does SMARTY.cc cost?
Pricing, packaging, licensing structure, and trial terms are not publicly established in currently available materials. Commercial terms depend on deployment, number of users, workflow scope, and integration requirements. Contact the SMARTY.cc team directly for current pricing.
- Q.17
How do I request access?
Use the contact page to reach the team. They can confirm current availability, access process, and whether a pilot or demo is the right first step for your environment.
- Q.18
Is SMARTY.cc an official Siemens or Altair product?
No. SMARTY.cc is a separate product designed for HyperMesh engineering workflows. HyperMesh, originally an Altair product, is now presented by Siemens as part of the Simcenter portfolio. SMARTY.cc is not owned, endorsed, certified, or distributed by Siemens or Altair, and no formal partnership with either company has been confirmed.
Ask the SMARTY team.
Include your HyperMesh version, solver profile, and the workflow you want to start with. The team will route your question to the right person and get you a direct answer.