Luminaire and panel families that work inside a real coordination model, and why every major Saudi project now writes "Revit family" into the BOQ next to the spec sheet.
The geometry is incidental. What consultants need: wattage, lumen output, IES file path, distribution code, IFC GUID. A pretty 3D family without parameters is useless.
Level of Development 300 = geometry accurate, parameters complete, IES attached. LOD 200 is conceptual. LOD 400 is fabrication. Tender drawings demand LOD 300.
Revit federates the disciplines, Navisworks finds clashes. A 50 mm-deep luminaire clashing with a 100 mm slab beam shows up before site, not during commissioning.
Use shared parameter files (SPF) so types flow into schedules and IFC export cleanly. Custom family parameters that don't schedule are dead data the moment the file is shared.
Level of Development per AIA G202, what each LOD means in the field.
| LOD | Geometry | Information |
|---|---|---|
| LOD 100 | Conceptual mass | Approximate area, cost |
| LOD 200 | Generic systems shown | Approximate size, location |
| LOD 300 | Specific systems modelled | Quantities, sizes accurate |
| LOD 350 | Coordinated with other trades | Clash-detected, installable |
| LOD 400 | Fabrication-ready | Vendor part numbers, mounting |
| LOD 500 | As-built verified | Field-verified, FM-ready |
| Typical KSA tender | LOD 300 | LOD 350 in mega-projects |
Revit is a database with geometry on top. Treat it like one.
One central model, each engineer borrows worksets. Sync every 30 minutes. This avoids the I sent you the file by email disaster that plagues AutoCAD MEP workflows.
Build a luminaire family with type catalogs for every variant (CCT, beam, watts, IES file). One family powers 50 schedules across the project. Don't draft individual fixtures.
Revit schedules auto-populate from family parameters: count, watts, CCT, room. Hand-typed quantity tables are a sign the model isn't trusted, fix the model parameters instead.
Run a hard-clash report between MEP and structure every Friday. Issue clash ID to the responsible engineer. By GA freeze, hard clashes should be zero, not deferred to RFI.
Owner-FM workflows live in IFC (ISO 16739). Export from Revit at major milestones with type, level, room and asset ID populated. Importing IFC back into Revit corrupts geometry, IFC is one-way.
Lighting and power packages delivered as Revit families and IFC exports for owner FM. LOD 400 fabrication models on request, with our actual fixtures parametrised.
Practical lighting know-how from NLC Academy. No spam, unsubscribe anytime.
By subscribing you agree to receive NLC emails.