AI BIM
Coordination
One federated model, clashes sorted by discipline pair and every issue sent to the designer who owns it — reviewed by a structural engineer before it reaches your team.
Coordination your designers can act on
Federated model
All discipline IFC models in one coordinated set, aligned to the project origin and checked for georeferencing and storey structure before any clash run.
Clashes by discipline pair
Results grouped by discipline pair — structure and MEP, architecture and structure, and so on — with tolerances agreed for the project, so each designer sees what concerns them.
BCF issues to each designer
Every confirmed issue goes out as a BCF topic with a viewpoint, the elements involved and the responsible designer. It opens in the designer's own BIM tool.
ÜBN and BEP check
Models checked against the Estonian ÜBN requirements and the project's BIM execution plan: naming, classification, required properties and model structure.
Weekly coordination report
One report per week: open and closed issues by discipline pair, what changed since the previous model set and the items that block the next design stage.
Engineer-led meetings
A structural engineer leads the coordination meeting, explains each issue and agrees the fix and the owner with the design team.
Four steps, repeated for every model set
- 01
Send the models
IFC files or a link to your common data environment, plus the BEP if the project has one.
- 02
We federate and check
We assemble the federated model, run the clash and compliance checks and review every result. False positives stay with us.
- 03
BCF and report
Confirmed issues go to each designer as BCF topics. You receive the coordination report.
- 04
Closure tracking
Each new model set is checked against the open issues until every issue is closed or formally accepted.
Our own engineering platform: StructBoard
We built StructBoard for our own engineering work: IFC geometry and the structural model, check streams per discipline, a decision base built on our projects — every decision with its sources, options and an independent check — a standards registry, drawing search and revision comparison, Tekla automation and status updates to your phone.
Software does the repetitive part. The engineering judgement — what is a real problem, who fixes it and how — stays with an engineer.
- IFC geometry
- Check streams per discipline
- Decision base
- Standards registry
- Revision comparison
- Tekla automation
- Status to your phone
For the party that carries the coordination risk
Developers
One view of design quality across all designers before tender or construction, with every open issue named and owned.
General contractors
Clashes resolved in the model, not on site. Issues tracked to closure with each designer while the programme still allows it.
Architects as lead designers
Coordination support for the design team, with structural expertise in the meeting and a report the client can read.
Experience15 years of structural practice in precast and steel structures, on projects in Estonia, Latvia and Sweden. We coordinate models the way we build our own: from the structure outwards.
Kindluse School extension, stage I
Harju County, Estonia. The precast structure as a Tekla model, shown as an interactive 3D erection sequence. An example of our model work; the scope of a coordination assignment is agreed separately.
View the project →Per model set, per month
The fee depends on the number of disciplines, model size, how often models are updated and the meeting rhythm. Send the project scope and we reply with an offer within 24 hours.
Pilot projects by request: one building or one design stage, so you can judge the reports before a longer engagement.
Request a coordination offerBefore you send the models
Which formats do you work with?
IFC 2x3 and IFC 4 models. Issues are issued in BCF 2.1 or BCF 3.0. Native authoring files are not required.
Which design tools can the designers use?
Any tool that exports IFC and reads BCF — for example Tekla Structures, Revit, Archicad or MagiCAD. Each designer answers issues in their own tool.
What does the software do, and what does the engineer do?
Software runs the clash and compliance checks, groups the results and drafts the issues. An engineer reviews every issue before it is sent; nothing reaches your designers unchecked.
Where does our data go?
Your models are used only for your project. Storage, access and deletion after the project are written into the offer.
Who signs the report?
Coordination reports are issued by Grey Gecko and signed by the responsible engineer. Each designer stays responsible for their own design.
Can we start before all disciplines have a model?
Yes. We start with the models that exist and add disciplines as they are delivered; the report shows which disciplines were checked.
COORDINATION OFFER.
Tell us the project, the disciplines and the design stage. Attach a BEP or sample models if you have them — large models can follow by link. We reply with an offer within 24 hours.