Workflows / LOD 400 deliverables: every file a project hands over
LOD 400 deliverables: every file a project hands over
Every file an LOD 400 model hands over from Calq, what it carries and the tool that writes it: IFC4, IFC 4.3 and IFC2X3, BCF, IDS, COBie, bar schedules and BVBS, DSTV NC, SAF, schedules, drawing sets as PDF, DWG and DXF, terrain and set-out.
- Available
Open standards first
A deliverable is only as good as the program that reads it. Calq writes the open standards the industry agrees on, so a contractor, a consultant or an owner reads what Calq writes in the tool of their choice. Check each file in the program that receives it.
Model files
- IFC4 Reference View by default, IFC 4.3 on request, IFC2X3 Coordination View 2.0 for older tools; with the structural analysis model, the work schedule, cost items and assets on request (export_ifc; the Export menu)
- IDS: the information requirements, written and checked against the model (export_exchange ids, check_ids)
- COBie for the owner's systems (export_exchange cobie)
- gbXML for energy analysis (export_exchange gbxml)
Coordination files
- BCF 2.1 and 3.0 with viewpoints, in and out (export_exchange bcf, import_bcf)
- IFC provisions for voids and BCF requests for a linked party (export_link_requests)
Workshop files
- BVBS for bending machines (export_exchange bvbs)
- DSTV NC for steel workshops, one file per member and plate, with the structural IFC, the analysis IFC and SAF in one package (export_structure_package)
- SAF for analysis programs (export_saf)
- The bar bending schedule as an Excel workbook (export_bar_schedule); the pipework spools as a PCF file and a spool list (export_exchange pcf and spools)
Drawings, schedules and site
- Drawing sets as PDF, DWG (AutoCAD 2018) or DXF (export_drawing)
- Schedules as spreadsheets (export_schedule), quantities and bills (export_boq)
- The terrain as LandXML and points, the set-out as a coordinate list (export_exchange landxml, topocsv, setout)
- The drawing register and the specification (export_exchange register, spec)
Name and issue them
Every file's name, status and revision comes from the one delivery table under ISO 19650: the project, the originator, the volume, the level, the type, the role and the number. Set it once (set_delivery), issue revisions (issue_revision) and send transmittals (issue_transmittal), and every export follows.
Questions
Which IFC versions does Calq write?
IFC4 Reference View by default, IFC 4.3 on request and IFC2X3 Coordination View 2.0, all from one writer.
Does Calq write files for fabrication machines?
Yes: BVBS for rebar bending machines and DSTV NC for steel workshops.
How are the files named?
By the ISO 19650 delivery table set on the model, so every export carries its container name, status and revision.