Where an AI model on its own is the better choice
ChatGPT, Claude and similar models are useful to an engineer today, and none of this needs Studio:
- Explaining a method. How inlet and outlet control differ, when the Rational method stops being appropriate, what a curve number stands for.
- Working on the words. Drafting a method statement, tightening a report section, turning notes into minutes.
- Reading what you give it. Summarising a brief, a tender or a chapter of a standard, and finding the clause you need.
- A second pair of eyes. Checking the logic and the units of a calculation you paste in.
Where it falls short as a calculator
- The arithmetic is not guaranteed. A language model predicts text. A calculation with several steps can go wrong in the middle and still read as right.
- Coefficients come from memory. Inlet-control constants, runoff coefficients, curve numbers and regional parameters live in published tables. A model recalls them approximately and cannot show which table it used.
- Writing code moves the problem. Many assistants can write and run a short program, which fixes the arithmetic. You are then reviewing a new, untested implementation of the method every time you ask.
- It has no data. A catchment needs a terrain model and a design storm needs a rainfall database. A model on its own has neither.
- It leaves no record. The answer is a paragraph in a chat: no saved inputs, no method statement, nothing a reviewer can run again.
The same agent, connected to Studio
Delta Hydro Studio publishes its calculation engines as 80 tools on an MCP server. Add it to the agent you already use and the division of work changes: the model reads your request, chooses the tools and supplies the inputs; the engine does the calculation; the result is saved to your project. You keep the agent's other connectors too, so it can read a crossing from QGIS or levels from a spreadsheet and pass them on.
ChatGPT or Claude on its own, asked to design a culvert
- The number comes out of a language model. It can be wrong and still read as right.
- No method is named and no inputs are kept, so there is nothing to check it against.
- Ask the same question twice and you can get two answers.
- The answer stays in a chat window. You retype it into your design.
The same agent, connected to Delta Hydro Studio
- The agent calls the engine: FHWA HDS-5 for the culvert, the Rational method for the peak. The model supplies inputs and reads results.
- Every input and result is saved as a record in your project.
- The same inputs give the same result, every time.
- The record opens in Studio with charts, intermediate tables and a Word and Excel report.
| An AI model on its own | The same agent on Studio | |
|---|---|---|
| Where the number comes from | The model writes it, or writes a short program for the occasion. | Studio’s calculation engine. The model supplies inputs and reads the result. |
| Method | Whatever the model recalls, named or not. | The published method the tool implements, named in the record: FHWA HDS-5, the Rational method, TR-55. |
| Coefficients and tables | From memory, without a source. | From the tables built into the engine, or looked up with a tool that cites them. |
| Catchment and rainfall data | None, unless you paste it in. | A terrain model for delineation, and design rainfall for South Africa, the United States and Australia. |
| The same question twice | Can give two answers. | The same inputs give the same result. |
| What is left behind | A paragraph in a chat. | A saved record with every input, charts, tables and a Word and Excel report. |
| Limits on what it may do | None that you set. | A quote before a paid study, a spending limit, no deletions, agent work marked in the audit trail. |
| Responsibility | Yours. | Yours. The record is there so the review can be shown. |
What stays with the engineer
The agent takes over the data entry, not the judgement. It asks for an engineering value it does not have, puts choices such as a runoff coefficient back to you, and recommends a design flood without adopting one. Every record it creates is marked as agent work in the audit trail. You review the inputs it chose and the results it produced before any of it reaches a drawing or a report.
How to try it
- Open a Studio account.
- Add the Studio MCP server to your agent. The set-up guide has Claude, Claude Code, Cursor and VS Code step by step; ChatGPT takes the same server address in its connector settings.
- Ask for a small job you can check by hand, such as a Rational peak or one culvert, and open the saved record.
The AI agents page shows a session from request to review.