ANSYS Customization and Automation Services

Typically a client comes to us when their team is spending a significant portion of time on repetitive manual work in the calculation workflow — or when standard ANSYS cannot cover a specific material, analysis type, or required output format.

Standard ANSYS covers most simulation tasks — but not everything. Limitations show up as repetitive manual work, the inability to integrate internal or commercial software, or the need for custom material models.

What we do:

• Extend ANSYS with capabilities it doesn’t have out of the box — custom UI, automated steps, third-party integration
• Automate repetitive calculation processes — from model preparation through computation to output export
• Develop scripts, ACT extensions, and UPFs based on what the specific task requires — see more about ACT Apps, APDL Scripts or UPFs

Benefit for your project:

• Without automation you re-solve the same calculation problem each time. With automation you do it once — and the entire process runs without manual intervention. The return on automation investment makes sense as soon as the recurring calculation takes more than a few hours.
• Calculation processes become repeatable, scalable, and documented. Without addressing this, you remain dependent on specific individuals and manual effort. Internal development of automation also requires a combination of CAE expertise and programming skills — it depends on whether you have this combination available within a single team.

When to address this:

• When standard ANSYS doesn’t cover your specific material, analysis type, or output format

• When you’re losing time to repetitive manual work in the calculation workflow

These are three different levels of customisation — each addresses a different type of problem.

What this means in practice:

• ANSYS ACT Apps extend the ANSYS Mechanical user interface — adding new functions, automating steps, or integrating external software. The result is distributable as a single file (.wbex)
• ANSYS APDL scripts automate and parameterise calculation processes at solver level — an effective tool for repeated analyses, custom post-processing, or access to ANSYS binary data
• ANSYS UPFs go deepest — enabling custom material models, element types, or failure criteria to be defined directly in the ANSYS MAPDL solver in C, C++, or Fortran

Your result:

• Which approach makes sense for your case will be assessed after reviewing the brief — we often combine multiple levels

Yes — specific examples from practice:

• ACT extension FEMFAT inside ANSYS for Magna Powertrain Engineering Center Steyr — integration of FEMFAT fatigue analysis directly into ANSYS workflow
• Figures Manager — a free ACT extension for automated export of result images, offered to the entire ANSYS community free of charge, see Free ANSYS ACT Extensions
• Custom material model for steel fibre-reinforced concrete structures (SFRC) implemented via UPFs — validated on experimental data

Benefit for your project:

• More reference projects in the Reference Projects section

Yes — we connect available technologies into end-to-end automated pipelines.

What we do:

• Connect ANSYS Workbench, Mechanical, SpaceClaim, and DesignXplorer into automated sequences
• Parametric studies, optimisation loops, and repeated analyses run without manual intervention
• Outputs — reports, images, data — are generated automatically in a standardised form

What this means for you:

• Every hour spent on manual setup is an hour that could have been computation. The return on automation investment typically shows after the first few repetitions of the calculation.
• If automation requires a custom software solution beyond ANSYS, this connects to Software Development

When to address this:

• When you’re running the same type of calculation repeatedly and manual work accounts for a significant portion of total time

We primarily specialise in the ANSYS ecosystem. For broader software development — such as connecting simulation results to a custom application or monitoring system — see more info in the Software Development section.

A brief description of the problem is enough — we’ll give you a specific process proposal and indicative scope. If it doesn’t make sense, we’ll tell you that too.