BARVEA Sp z o.o.

Your IFC file passed validation. Does that mean the numbers inside are right? No. And that is the single most important thing to understand about BIM data quality control. The official buildingSMART IFC validator left beta in March and shipped two rule packs this year: - v1.0.2 (30 June): rules IFC430 and IFC431, checking entities excluded from the IFC 4.3 MVDs - v1.0.3 (6 August): the normative TAS000 rule for tessellated geometry, plus fixes More than 100 rules, a free account, a public release cycle. It belongs in the standard workflow of anyone exchanging data through IFC. But the validator checks whether a file is built correctly. It cannot check whether the data matches reality. Fresh example: the Revit 2027 IFC exporter bug spent months producing wrong base quantities for footings and slabs. Those files passed validation cleanly, because a wrongly computed width is a perfectly legal number as far as the schema is concerned. Full control takes two stages: structural validation plus content checking. For the second stage we built a free tool: IFC Schedules generates quantity schedules straight from the IFC file and shows property fill rates before you start counting. Full story on the blog: https://lnkd.in/dhiwrnSF #BIM #IFC #openBIM #buildingSMART #validation #QTO

Who is a BIM Manager? And why isn't it the same as a BIM Coordinator? A BIM Coordinator works at the single-project level - coordinating models, catching clashes, keeping geometry consistent. A BIM Manager operates more broadly - responsible for BIM standards and strategy across the whole company. They set the rules a Coordinator enforces daily. On our team these roles are genuinely split and staffed: Mikołaj Rożek - BIM Manager, Piotr Komorowski - BIM Coordinator. Not business-card titles - the actual division of work on every project. We wrote about what a BIM Manager actually does, and why demand for the role keeps growing. Full article: https://lnkd.in/dRpnaqdw #BIM #BIMManager #BIMManagement #BIMProjectManagement #BARVEA

Pulling a quantity schedule out of an IFC model usually ends one of two ways: you click through elements in a viewer and retype them into Excel, or you buy a tool that does ten times more than you need. We are releasing a third option. For free. IFC Schedules is a Windows application that generates quantity and property schedules directly from IFC files. How the work goes: - load one or more IFC files at once, IFC2X3 and IFC4, into a single workspace - pick the categories to schedule: walls, doors, slabs, MEP - before committing to columns, see what percentage of elements actually carry a given property, with sample values - filter with nested AND/OR condition groups rather than a flat list, for example "(Fire Rating = EI60 OR EI90) AND Storey = Level 2" - group across multiple levels with per-column aggregation: count, sum, average, min, max - export to Excel, one sheet per category, or to CSV - save the whole setup as a template and load it again in the next project with one click Two things we cared about. First: it runs entirely on your own machine. The app opens a local browser tab pointed at localhost. Models and generated schedules never leave your computer. No telemetry, no analytics, no accounts, no login. With client models that matters. Second: it is genuinely free. No seat limits, no gated features, no paid plugin to unlock. Using it in paid client work is expressly permitted. That was a deliberate decision, not an introductory offer. Interface available in English, Polish, Spanish and German. Written by Mikołaj Rożek. IFC parsing is handled by the IfcOpenShell library, licensed LGPL-3.0. Download: https://barvea.com/en/apps If you do IFC takeoffs regularly, tell us what is missing. We would rather build the next version around real needs than around a feature list. #BIM #IFC #OpenBIM #QuantityTakeoff #AEC #ConstructionTech #Architecture #BARVEA

In 2015, Andrew Tallon laser-scanned Notre-Dame Cathedral. Out of scholarly curiosity, not in anticipation of a disaster. 50 scanner positions. Over a billion points. 5mm accuracy. Four years later, when fire consumed the roof structure and the spire collapsed, that data became the reconstruction blueprint - the most precise record of the cathedral's geometry ever to exist. It's the best proof that laser scanning heritage buildings isn't a tech curiosity. It's an insurance policy for architectural heritage. We wrote about why it's worth scanning a heritage building before it's too late - accuracy standards, HBIM, and what happens when that documentation doesn't exist. In two weeks we're heading out ourselves to scan another historic site - case study coming soon. Full article: https://lnkd.in/dH4wr6X8 #LaserScanning #HeritageBuildings #HBIM #BIM #HeritagePreservation #CulturalHeritage #BARVEA

BIM project management looks different in 2026 than it did a year ago. Three things that happened in the last few months: - AI generates BIM model elements from text alone - 86-95% accuracy (TU Munich, presented at the Hanmi Global summit, June 2026) - Site-photo analysis + BIM model = up to 50% more accurate structural-element identification - Trimble Tekla and Allplan both shipped built-in AI assistants (natural-language modeling, 24/7 support) The common thread: every one of these tools runs on a human-in-the-loop model. AI speeds up the routine - but verification, decisions, and accountability stay with the BIM Manager. We wrote a full breakdown - with real numbers and sources, no marketing fog. Is AI already supporting BIM project management in your office, or still a one-project experiment? Curious to hear in the comments. Full article: https://lnkd.in/dkSCWAEd #BIM #BIMProjectManagement #BIMManagement #AI #AEC #ISO19650 #Revit #Trimble #Allplan

⏱️ A 3D model shows HOW a building looks. But not WHEN it'll be built or HOW MUCH it really costs. That's where the further BIM dimensions come in: - 4D = 3D + time (schedule, installation sequence) - 5D = 4D + cost (estimate from quantities pulled off the model) What do they actually deliver? 4D (time): - sequence simulation - catch conflicts before they hit the site - site planning: access, laydown, crane swings - a digital "dry run" = better safety 5D (cost): - estimating 50–80% faster - no more manual take-off from drawings - fewer quantity errors and disputes - change the design - the cost recalculates automatically Combined, 4D+5D answer questions that used to take analysts weeks: "If we accelerate steel by two weeks (4D), how does that hit cash flow next month (5D)?" One condition: it only works on a good model. Messy data = a wrong estimate and an unrealistic schedule. So 4D/5D is a step AFTER tidying the model (and the right LOD), not instead of it. Already doing 4D/5D - or do your schedule and estimate still live in separate spreadsheets? 👇 📖 https://lnkd.in/dmytxRVZ #BIM #4DBIM #5DBIM #Revit #Navisworks #CostEstimating #Scheduling #BIMmanagement #AEC #DigitalConstruction

Naming a company turned out to be harder than modelling one. After months of shortlists, dead ends and one name we genuinely liked but had to abandon, we landed on BARVEA. Today it becomes official: archBIM is now BARVEA Sp. z o.o. For our clients nothing changes. Same team, same contacts, same commitments on every ongoing project. The name is new, the standards are not. We still do what we have always done — BIM design, multidiscipline models, 3D scanning, Revit implementation and ISO 19650 workflows for architectural practices, developers and contractors across Europe. The website is refreshed too, along with our latest articles → https://barvea.com So — what do you think of the name? We are curious whether it sounds as good to you as it does to us.

📐 "Give me the model at the highest LOD, so it's complete." Sounds sensible - it's one of the most expensive misunderstandings in BIM. A higher LOD doesn't mean "better". It means "more expensive and heavier". The skill is specifying exactly the level that meets the purpose of the stage: - LOD 100 - concept, massing, indicative area - LOD 200 - approximate geometry (early coordination) - LOD 300 - accurate construction design (documentation standard) - LOD 350 - connections and interfaces between disciplines (where clash detection works) - LOD 400 - shop level, prefabrication - LOD 500 - as-built model, digital twin The most common mistake? A uniform, high LOD for the whole model. On a real project the structure might be LOD 350 while furniture is LOD 200 - at the same time. Forcing LOD 400 everywhere is weeks of needless work and a model that hurts performance instead of adding value. And one distinction that costs money: LOD (geometry) ≠ LOI (information). An element can have beautiful geometry and zero data. ISO 19650 combines both into LOIN - "how much information is genuinely needed to make a decision". The right LOD is the lowest level that meets the purpose. No higher. Which LOD do you usually specify - and do you ever overpay for detail nobody uses? 👇 📖 https://lnkd.in/dCWsy7wJ #BIM #LOD #Revit #AEC #ISO19650 #BIMmanagement #Architecture #BIMstandards #DigitalConstruction #InformationManagement

📐 „Poproszę model w najwyższym LOD, żeby był kompletny." To zdanie brzmi rozsądnie - a jest jednym z najdroższych nieporozumień w BIM. Wyższy LOD nie znaczy „lepszy". Znaczy „droższy i cięższy". Cała sztuka to zamówić dokładnie ten poziom, który spełnia cel etapu: - LOD 100 - koncepcja, bryła, orientacyjna powierzchnia - LOD 200 - geometria przybliżona (wczesna koordynacja) - LOD 300 - dokładny projekt budowlany (standard dokumentacji) - LOD 350 - połączenia i interfejsy między branżami (tu działa clash detection) - LOD 400 - warsztat, prefabrykacja - LOD 500 - model as-built, cyfrowy bliźniak Najczęstszy błąd? Jednolity, wysoki LOD dla całego modelu. W realnym projekcie konstrukcja może być w LOD 350, a wyposażenie w LOD 200 - jednocześnie. Wymuszanie LOD 400 wszędzie to tygodnie zbędnej pracy i model, który tnie wydajność zamiast dodawać wartość. I jeszcze jedno rozróżnienie, które kosztuje: LOD (geometria) ≠ LOI (informacja). Element może mieć piękną bryłę i zero danych. ISO 19650 łączy oba w LOIN - „ile informacji naprawdę potrzeba, żeby podjąć decyzję". Właściwy LOD to najniższy poziom, który spełnia cel. Nie wyższy. Jaki LOD najczęściej zamawiacie - i czy zdarza się przepłacać za szczegółowość, której nikt nie używa? 👇 📖 https://lnkd.in/d4vcJf42 #BIM #LOD #Revit #biuroprojektowe #ISO19650 #modelowanieBIM #BIMmanagement #architektura #standardyBIM #AEC

🚧 A duct runs into a concrete beam. On site: a halted crew, a meeting, a redesign, reordered components. Several thousand down the drain — at minimum. In the BIM model: five minutes of a coordinator's time. Material cost: zero. The entire economics of clash detection lives in that one difference. Industry numbers, 2026: → A single clash found on site = a few to tens of thousands → Rework = 5–12% of contract value. On a £30M scheme that's £1.5–3.6M → Case ROI: a $200k coordination investment → $2.5M+ in savings (10× return) → Clash detection cuts field change orders by up to 15% But beware the most common mistake: confusing the report with coordination. 3,000 clashes in a raw report isn't a result — it's raw material. Without filtering, coordination rounds and BCF, nobody resolves it. BIM coordination isn't a cost. It's insurance with a positive rate of return. How does it look on your projects — do you coordinate in the model or on site? 👇 📖 https://lnkd.in/d3X2upiy #BIM #clashdetection #BIMcoordination #Navisworks #Revit #AEC #BIMmanagement #construction #ISO19650 #digitalconstruction