BIM in the Gulf — every format you receive, and how to read it without a CAD seat

On a single Gulf project, you can easily receive: architectural PDFs from the consultant, structural DWGs from the structural engineer, MEP RVT files from a separate consultant, an IFC export from the BIM coordinator, and DXF marked-ups from a site engineer.

The traditional answer is "buy AutoCAD licences for everyone who might touch them." That's expensive. It's also wrong — most of the people who need to view and measure drawings shouldn't be in CAD at all.

What each format actually is

PDF is what you almost always receive at issue-for-construction stage. It's a flat raster (sometimes vector) snapshot. You can mark up, measure (with calibration), and reference. You can't easily change.

DWG is AutoCAD's native vector format. Layers, lines, blocks, annotations — but version-locked to AutoCAD releases (R12, R2010, R2018, R2024 all exist and aren't fully interchangeable). To read it, you either own an AutoCAD-family seat, or you use a library like LibreDWG, or you pass it through an ODA File Converter to normalise to a known version.

DXF is AutoCAD's interchange format — same content as DWG but text-based. Easier to read programmatically, less common at issue.

RVT is Revit's native format. Where it gets hard: RVT is binary, versioned, and requires the Autodesk runtime to extract reliably. The practical way for non-Revit users to consume RVT is through Autodesk Platform Services (APS) cloud translation — upload an RVT, get a viewer derivative and an IFC export back.

IFC is the openBIM interchange. Vendor-neutral, well-documented, contains geometry + properties + relationships. The right format to ask for if you want to extract quantities programmatically.

How ORKSTRA reads each

ORKSTRA pairs a reader to each format so you don't need a CAD seat:

• PDF — Apryse Premium (high-fidelity) with PDF.js as a free fallback. Measurement, calibration, markup, vector annotations all in the browser.
• DWG / DXF — LibreDWG for routine reads; ODA File Converter for legacy R12..R2024 normalisation; APS for the few clients who only send Revit.
• RVT — APS Model Derivative API for cloud-side translation. You upload once, get viewer + IFC + quantities back.
• IFC — Web-IFC (web-ifc + web-ifc-three) for browser-native reading. Pulls IfcQuantityArea, IfcQuantityVolume, and custom property sets directly to the BOQ.

Why this matters at takeoff time

If the BIM is good, you shouldn't be doing a manual takeoff at all. A properly modelled IFC contains the wall areas, slab volumes, door counts, finish schedules — directly accessible via the property sets.

ORKSTRA's QTO engine reads IFC quantities, runs Triple-AI on PDFs (when the BIM is incomplete or absent), and uses APS-translated RVT derivatives when the consultant only ships native Revit. You don't choose your format; the model picks the best path for what landed in your inbox.

That's the difference between "we support BIM" and "we ship in any format your project actually receives."