# Ghulam Murtaza

Ghulam Murtaza works on software and automation for façade engineering and BIM, including tools for exploring façade projects, comparing panel layouts, and handling inconsistent model data.

- Profile: https://b2binfluencer.marketing/creators/ghulam-murtaza/
- LinkedIn: https://www.linkedin.com/in/ghulam-murtaza-9024071a5
- LinkedIn followers: 8,148
- Based on 11 dated posts, latest 2026-09-21

## Summary

They are most useful for practical facade BIM automation content tied to real workflow problems.

- Best for: A facade engineering software company doing practical BIM-to-facade automation co-marketing.
- Not for: A vendor claiming AI can calculate facade quantities without human review.
- Check first: Confirm sponsorship policy, deliverables, audience data, and dated product proof.

### Takeaways

- AI can identify and flag inconsistently classified Revit elements while engineering logic calculates and people verify.
- Changing panelization constraints reduced dimensional-check flags from 864 to 480, but remaining panels need review.
- Model naming changes like GLASS, GLZ, and CW_GLAZING can break BIM automation without confirmation.

## Main ideas

- **Make automation flexible enough for inconsistent project data**: BIM automation can break when projects use different names for the same element. Murtaza’s example is glazing labelled “GLASS,” “GLZ” or “CW_GLAZING.” They propose a context layer that uses geometry, metadata and surrounding model information to suggest what an element represents, then lets a user confirm the mapping and reuse the resulting rule. The aim is not fully autonomous BIM, but automation that adapts to how projects are delivered.
- **Use AI to interpret model data; let engineering logic calculate**: Rather than asking AI to calculate façade quantities directly, Murtaza suggests using it to identify elements, flag questionable classifications and indicate what needs human review. Geometry, rules and calculations remain with the engineering engine; people verify the results. They apply a similar principle to CAD: use AI to help understand why a geometry case failed, rather than blindly trusting AI-generated geometry.
- **Generate design alternatives without outsourcing design judgment**: Murtaza presents panelization as a way to explore constraints and problem areas, not to select a design automatically. Designers can set target panel sizes, joint widths and manufacturing limits, then compare alternatives. The remaining checks and the effect on architectural intent still matter.
- **Target operational friction, not engineering expertise**: Murtaza describes automation as a way to reduce repetitive work in façade firms, not replace engineers or remove technical expertise. The workflows they highlight range from connected tendering and drawing comparisons to mobile defect tagging, panel-pattern conversion and factory dashboards. They also share an interactive façade environment for exploring options and inspecting components, describing it as work still being developed.

## Work to read

- [Six facade workflows that can be automated in four weeks](https://www.linkedin.com/posts/ghulam-murtaza-9024071a5_facadeengineering-facade-curtainwall-activity-7463173535117504512-8pbY)
- [AI should interpret messy Revit data, not calculate geometry](https://www.linkedin.com/posts/ghulam-murtaza-9024071a5_facadeengineering-bim-revit-activity-7502977825424158721-_XC5)
- [Why BIM automation breaks when model naming changes](https://www.linkedin.com/posts/ghulam-murtaza-9024071a5_bim-facadeengineering-constructionautomation-activity-7501610978409693184-Uvo_)
- [A different way to explore and interact with facade projects](https://www.linkedin.com/posts/ghulam-murtaza-9024071a5_we-have-been-working-on-a-different-way-to-activity-7506302901498220544-bbM7)
- [Panelization alternatives reduce flagged panels from 864 to 480](https://www.linkedin.com/posts/ghulam-murtaza-9024071a5_facadeengineering-facadedesign-computationaldesign-activity-7507700643097128960-MHwb)

## Brand relationships

- **Façade Studio** (mention)
- **ConXOrbit** (mention)
- **GPT-6 Astra** (mention)

## Partnerships

Ghulam Murtaza's posts cover facade BIM automation, panelization, model-data cleanup, and an interactive facade project viewer, but do not specify sponsorship policies, rates, deliverables, disclosure practices, or a formal collaboration route. One post invites direct messages about trying a live facade system—a product-demo invitation, not a stated partnership process. Before planning spend on a BIM and facade automation collaboration, ask whether sponsored work is accepted and confirm deliverables, disclosure, and usage rights.

## Alternatives

- Steve Evans: Choose Steve Evans when buyers need to address design-data quality rather than facade delivery: finding duplicate and near-duplicate CAD files, searching for parts by 3D shape instead of filename or part number, rationalising a parts library after a merger or a move between PLM/PDM systems, and putting a cost on the waste. For vendors selling shape-based search or CAD data cleansing, the posts make the case at buyer scale: a reported 40,000-part cleanse with roughly 7,500 exact duplicates and 4,000 near duplicates, and a worked example putting avoidable engineering effort at about £900,000. The aerospace post also makes the case for 3D over 2D drafting — simulation, model-based definition, clash detection and faster prototyping — making it a fit for collaborations aimed at engineering managers weighing a modelling or data-hygiene purchase.
- Scott Gardner: Choose Scott Gardner when the collaboration is about AI governance: agent memory and state integrity, observability and disclosure when a system changes its own context, or open-weight AI policy and the limits of enforcing it. The two posts give vendors a risk-and-controls story grounded in concrete incidents — a live session where history was truncated, a synthetic summary replaced the system's memory, and an instruction told the model not to acknowledge the checkpoint — alongside the argument that governance should attach to consequential deployments, critical infrastructure, federal procurement, provenance and incident reporting, rather than model release alone. That framing suits vendors in monitoring, evaluation or compliance who need a credible voice on where obligations can actually be enforced.
- Nipuna N Jayasinghe: Choose Nipuna N Jayasinghe when the buyer is in apparel and softgoods: quality assurance, supplier onboarding, factory audits or sourcing. The posts distinguish GMP, technical evaluation and quality management as three separate audit dimensions, with named brand benchmarks. They also set out quality requirements for lace scallop balancing and motif matching, including how failed matching leads to buyer rejections. For vendors selling inspection, audit or quality-management software to garment manufacturers, this content maps directly to buyer decisions. The lace post shows how to make a specialist aesthetic requirement clear to a sourcing audience.

---
AI-assisted summary of public posts. Audience demographics are not available. Engagement appears only where we checked recent posts. Method: https://b2binfluencer.marketing/methodology/