Privacy settings

We use Microsoft Clarity to understand how CALC is used — only if you agree. Necessary cookies keep the app working (sign-in, security, free-quota enforcement) and are always active.

Dlubal CALCDocumentation

Search documentation…

Search titles, headings and page text

Open Dlubal CALC

How Mia works

Mia is the assistant inside Dlubal CALC. Between your message and the answer sit three things worth knowing about, because each one explains a behaviour that otherwise looks arbitrary.

The tier decides how hard it thinks

Two tiers, and you choose in the message bar:

TierFor
StandardMost questions. One pass, fast
DeepLong chains, several interacting checks, anything with an attachment

A Standard message costs 1 credit, a Deep one 2.

Note

Some turns are pinned to Deep whatever you picked. An attachment is the clearest case: the Standard model may not be able to read the file at all, so answering with it would produce a confident answer about a document nobody looked at.

Tools run when the answer needs them

Mia does not answer everything from memory. When a question needs a rule, a location or a model, it calls a tool and the result goes into the answer:

  • the Dlubal knowledge base and your company knowledge, for standards and internal documents
  • geo data for a location, covering snow, wind, seismic, climate and altitude
  • web search, when you allow it
  • RFEM, when it is connected

Dlubal-operated cloud tools remain available and do not need global switches. Availability is not execution. Mia calls a tool only when the question needs it. RFEM remains switchable because it is a local application where Mia can read or change a model.

Costs apply only to the actions listed in Plans and credits, and only when they actually run. That is why two similar questions can cost different amounts.

Example: "what is qL²/8" costs one message and nothing else. "Which snow load applies in Passau" costs the message plus one geo lookup, because it has to fetch data for the location.

It says what it assumed, and asks when it cannot

Engineering assumption

The rule Mia follows is to state assumptions rather than bury them, and to ask rather than invent when something essential is missing. That is why an incomplete prompt gets a question back instead of a plausible number.

There is a second rule worth knowing because it shapes answers about the software itself: Mia will not tell you that a setting is on or off by default, or where exactly a control sits, unless a retrieved source said so. If you need a default and no source states it, you get told to check it in the program. A wrong default sends you hunting for a checkbox that was already ticked.

What it can see

This conversation, the files attached to it, and the results of the tools it called during it. Not your other chats, not a colleague's, and nothing on your machine that you did not attach or expose through the Dlubal-Connector.

Where to go next