AI agents trained by your engineering firm
AIFlock Engineering is the version of AIFlock for engineering firms and technical offices. Its agents find the data in your project documentation and check it against the standards you apply. Then they leave you a draft of the annex or the report, and you review it before you sign it.
| Item | Value | Document |
|---|---|---|
| Roof area | … | … |
| Module | … | … |
| Inverters | … | … |
| Max. DC voltage drop | … | … |
| Allowable load | … | … |
| The 2009 report said 0.15 and the system weighs 0.13. | ||
Three jobs an engineering firm does every week
Projects and annexes
They gather the project’s input data, each item with its document, and prepare the annex.
See the warehouse caseTechnical reports
They prepare the report with the document each figure comes from, so you can check it.
See the bridge caseAudits and inspections
They classify the field observations and leave the report with a deadline for each defect.
See the plant case
The warehouse assignment, start to finish.
The video tells the same case as this page: the roof load, the cable schedule that gets recalculated and the annex your engineer reviews.
Example case · made-up names and data. AI-generated voice-over, in Spanish.
This is how a calculation annex gets done today.
The load figure is in some PDF from the 2009 project, and nobody remembers which one. Nor is it clear whether the 2015 refurbishment changed it, because its annex is in another folder. The annex gets written on the last day.
The same assignment, with your team of agents.
You ask the coordinator for the annex the way you’d ask a colleague at the office. It proposes a plan with four agents and, once you confirm it, each one does its part with your documents.
The cable schedule and the consumption spreadsheet are attached in the chat: the calculation agent reads them and gives you back a new Excel file.
- PDProject documentationGathers the input data from the project collection, including the 2015 refurbishment annex.Allowable load: 0.12 kN/m² according to the 2015 refurbishment annex; the 2009 report said 0.15. Flagged for your review.
- STStandardsChecks the criteria against the ITC-BT-40 and the DB-SE-AE you uploaded to the collection.Criteria checked against the standards in your collection.
- CACalculationIf you attach the cable schedule spreadsheet in the chat, it checks the cross-sections and the voltage drop with Python.Spreadsheet checked: 3 of the 86 strings exceed 1.5% and it suggests 6 mm².
- AWAnnex writerWrites the annex with the input data, their documents and the load warning.Anejo_calculo_borrador.docx, for your review.
Your engineer stops looking for data and starts reviewing results.
- PDFWarehouse drawings, 2009 revisionQueued
- PDFStructural reportQueued
- PDFRoof refurbishment annex, 2015Queued
- PDFModule and inverter data sheetsQueued
- PDFREBT, ITC-BT-40Queued
- PDFCTE, DB-SE-AEQueued
- DWGRoof plan.dwgQueued
- XLSXCable schedule, to check the calculationAttached in the chat
They work with the documentation you already have.
You upload each project’s documents to a collection: drawings in PDF, reports, data sheets and the standards you apply. The agents search them and tell you which document each figure comes from.
- Drawings go in PDF. Today we don’t read DWG or other CAD formats.
- You upload the standards. That way they work with the edition your firm applies.
- If a calculation needs checking, you attach the Excel file in the chat and the agent gives you back another one with the results.
A feasibility report with three geotechnical studies.
In the North Bridge case, the agents find the data in the 2023 and 2024 geotechnical studies. Then they cross-check it with the standards in your collection and write the report in Word, which your engineer checks before signing.
Example case · made-up names and data: North Bridge feasibility report. Narrated in Spanish.
An installation audit before the inspection arrives.
The technician comes back from the plant with the completed checklist and attaches it in the chat. The agents cross-check it with the project, the previous inspection report and the standard, and classify each observation.
| No. | Field observation | Standard in your collection | Severity | Proposed deadline |
|---|---|---|---|---|
| 1 | 300 mA RCD on a socket circuit; the project specifies 30 mA | … | Serious | Immediate |
| 2 | Signage for the warehouse fire extinguishers, pending since the 2021 inspection report | … | Serious, repeated | 1 month |
| 3 | Secondary panel CS-07 without circuit labels | … | Minor | 3 months |
| 4 | Fire hose reel no. 7 with its annual service overdue | … | Serious | 1 month |
Example case · made-up names and data. The engineering firm gets the plant ready for the inspection; the inspection and its report belong to the inspection body.
The plant reaches the inspection with every defect located and a deadline for each.
You correct it once and it applies it to the next project.
Your engineer tells the documentation agent what to do when two documents don’t match. It uses the most recent one, flags it in the annex and keeps the rule for the next assignment.
Training an agent means giving it your instructions and your corrections. Your documents don’t train any AI model, ours or anyone else’s.
When two project documents don’t match, use the most recent one and flag it in the annex.
Project documentationUnderstood: I’m using the load from the 2015 annex (0.12 kN/m²) and noting it in the input data. I’ll apply this in future projects.
Load in the annex: 0.15 kN/m², according to the 2009 report.
You confirm the plan and review what they hand over.
Before the agents start, you see the plan and confirm or change it. When they finish you have the Excel file and the Word draft to review at your own pace, and what each agent did is logged.
- Plan confirmed by the engineer, with four steps
- Project documentation: input data gathered; the 2009 and 2015 loads don’t match
- Standards: criteria checked against the ITC-BT-40
- Calculation: cable schedule checked, attached in the chat
- Annex writer: Word draft delivered
We get it running with one of your projects.
We load the documentation.
We upload the documents of a closed project and the standards you apply to a collection.
We adjust the agents.
We give them your criteria and the way you write annexes and reports.
We test it with an assignment.
The agents prepare one of your annexes or reports, and together we correct whatever doesn’t come out the way you’d do it.
Transparent pricing, real results.
Choose the plan that fits your processes. Start small, scale when you see results.
Starter
For teams starting with AI automation
Pro
For companies automating real processes
Business
For teams with complex processes
Custom
For organizations with specific needs
Developers / Platform
Build on the AI Flock Engine.
Each additional user costs €40 a month. All the details on the pricing page.
Where your data is. The app runs in Finland, the database and documents are stored in Germany and the AI model runs in the European Union. Web search uses a provider outside the EU, listed in our subprocessors list.
Learn to use it in the Academy (in Spanish).
Five short guides to get your team off to a good start: setting up the technical base, asking questions about the documentation, working with standards, checking calculations in Excel and preparing a report in Word.
- Monta la base técnica del proyecto para que tus agentes la consulten
- Pregunta a tu documentación y exige el documento y la página
- La normativa técnica la subes tú, y su vigencia la controlas tú
- Cálculos y tablas con Excel, adjuntando el archivo al chat
- Prepara un informe técnico con varios agentes y recíbelo en Word
What engineering firms ask us.
Do my drawings and documents train any AI model?
No. Your documents are stored in your collection and the agents look them up to answer, but they aren’t used to train any AI model, ours or anyone else’s. What the agents do learn are your instructions and your corrections, which stay in your account. The data is in the European Union: the app runs in Finland and the documents are stored in Germany.
Can you read DWG drawings or other CAD formats?
Not today. Drawings have to be exported to PDF, and the agents read the text they contain. Besides PDF, they work with Word, Excel, PowerPoint, CSV and text files, and scanned documents are read as images. If you have the original of a scanned document, upload it instead of the copy, because its text is read more reliably.
Can they run calculations with my Excel files?
Yes, with the Excel files you attach to the conversation. The calculation agent reads them, runs the operations you ask for, such as cross-sections, voltage drops or quantity takeoffs, and gives you back a new Excel file with the results. Today it doesn’t create charts or calculate on Excel files stored in a collection: to calculate, the file has to be attached in the chat.
Do you include the technical standards?
We don’t include a library of standards. You upload the ones you apply to your collection, such as the Spanish low-voltage regulation (REBT), the Building Code (CTE), the fire safety regulation (RIPCI) or the Eurocodes, and the agents look them up like any other document. That way they work with the edition your firm uses, and when a standard changes, you replace the document.
Who signs the annex or the report?
Your engineer. The agents prepare the draft in Word with the data, the calculations and the document each figure comes from, and your team reviews it, corrects it and signs it. An installation audit works the same way: the engineering firm gets the plant ready for the inspection, and the inspection and its report belong to the inspection body.
How do we get started?
We start with a thirty-minute meeting about one of your projects. Then we load its documentation, adjust the agents to your criteria and test it with an assignment from that week. The free trial is for getting to know the app with a few documents; to work with a complete project, we set it up with you during onboarding.
Tell us about a project and we’ll show you how your agents would prepare it.
AIFlock Engineering was designed by the team of Joaquín Peña Siles, PhD in multi-agent systems and professor at the University of Seville.