Share one current workflow problem. Include the authoring/checking tools, exchange format and version, project scale, expected result, observed result, and the smallest reproducibl
- Replies
- 1 replies
- Last activity
- Sep 16, 2026
A public, practitioner-led forum for BIM, open standards, automation, coordination, and the Exynix toolchain.
Share BIM knowledge, workflows, and experience with the community.
Learn from field-tested methods across openBIM, coordination, automation, and delivery.
Start a discussionNine working rooms
Interoperability, delivery standards, and practical BIM workflows.
Exchange, information requirements, validation, and issue handover.
Reliable automation patterns for Revit, Dynamo, Python, and C#.
Model coordination, information quality, and team delivery practice.
Questions, feedback, and workflows for the browser IFC viewer.
Revit productivity, model checking, and delivery workflows with ExyRev.
Model intelligence, reporting, and Power BI workflows with ExyBI.
Evidence-led product ideas and workflow improvements.
Share practical AEC workflows, automation, and lessons learned.
Current signal
Share one current workflow problem. Include the authoring/checking tools, exchange format and version, project scale, expected result, observed result, and the smallest reproducibl
Share a BIM/openBIM workflow, automation, model-checking method, dashboard, visualization, or coordination lesson that others can learn from. Explain the problem, constraints, appr
Use this topic for specific ExyViewer feedback. Include browser and device, model size/schema, the workflow you attempted, the exact point of friction, and what a successful result
The strongest automation candidates are repetitive, rule-based, frequent, and verifiable. Parameter population, naming checks, view/sheet setup, controlled export, and model-health
A useful BCF issue should be actionable without a meeting. Include a focused viewpoint, affected elements, a concise problem statement, the expected resolution, ownership, priority
An IDS requirement is most useful when it is narrow, testable, and tied to an agreed delivery purpose. Common pitfalls include ambiguous applicability, relying on display labels in
Large offsets, mixed coordinate reference assumptions, true-north/project-north confusion, unit mismatches, and inappropriate geometry representations can all make an IFC appear mi