BIM coordination
Bringing models together, finding where systems compete, and keeping issues moving toward a clear decision.
Joey S. Martinez · CAD, BIM, and practical automation
CAD, BIM, coordination—and the practical work of making project information useful.
Practical lessons from CAD and BIM production: the problems, the checks, and the workflows that make the next handoff clearer. Written from experience, by Joey S. Martinez.
A little about me
Joey S. Martinez
CAD precise communication · BIM connected information · Joe judgment and accountability
Capabilities at a glance
Revit production
Building and maintaining models, documents, families, parameters, templates, and standards that other people can actually use.
Automation
Using pyRevit, Dynamo, Python, and the Revit API to take repetition out of production work without hiding the judgment calls.
Digital delivery
Setting up clean exchanges, checks, naming, versioning, and handoffs so the right information reaches the next person.
Problems I've worked through
Real production problems, explained without the confidential details.
These examples are generalized on purpose. They describe the thinking and technical work involved without naming an employer, client, or project.
01Revit standards
Text-style consolidation
Problem + approachProduction models collect nearly identical text types. I built a controlled mapping workflow that updates placed notes safely instead of relying on a blind purge.
ResultPlaced notes update through a reviewable mapping, so redundant styles can be removed without relying on a blind purge.02Linked models
Coordinate export
Problem + approachCoordinates get unreliable when elements sit in linked files with different transforms. This exporter resolves the links and produces consistent location data for checking and handoff.
ResultLinked-element locations are exported in one consistent coordinate frame, ready for checking and handoff.03Model validation
Linked-family matching
Problem + approachA matching routine compares host and linked elements while accounting for incomplete parameters, naming differences, duplicate candidates, and ambiguous data.
ResultLikely matches and ambiguous exceptions are separated, reducing manual comparison without hiding uncertainty.04Production automation
Bulk schedule workflows
Problem + approachPython and Revit API utilities handle repeatable schedule operations, validate the inputs, and keep changes grouped in dependable transactions.
ResultRepeatable schedule changes run consistently in validated transaction groups instead of one schedule at a time.05Cloud delivery
ACC cloud-model access
Problem + approachAn ACC-aware batch workflow accounts for model paths, Revit versions, links, exporters, add-ins, and the realities of deploying tools to production teams.
ResultCloud paths, Revit versions, exporters, and add-ins are handled as explicit deployment conditions rather than late surprises.From the workbench
Field notes worth keeping.
Practical workflows and personal reflections on drawings, models, and the judgment behind them.
AEC practice · Founding field note
The Evolution of a Drafter
Software changed the medium. It did not change the responsibility to understand, communicate, coordinate, verify, and deliver work that can be built.
Read notePlain English
CAD, BIM, and the tools—without the jargon.
Click any term for a short explanation of what it is, what it does, and why anyone outside the industry should care.
My path through CAD + BIM
I learned the work through drawings, then learned to see the system behind them.
I entered the AEC industry through drafting and CAD production, where I learned that a drawing has to communicate clearly to the next person—not just look correct on a screen. Working in design roles across different disciplines taught me to follow the connections between systems and treat coordination and constructability as part of the design itself.
Revit and BIM expanded that responsibility. The work became less about producing a single drawing and more about keeping geometry, data, documents, disciplines, and handoffs dependable as the project changed.
That path led into model standards, multidisciplinary coordination, Autodesk Construction Cloud, digital delivery, and practical automation with pyRevit, Dynamo, Python, and the Revit API. The technology keeps changing; the useful habits do not: understand the problem, communicate clearly, and check the work.
This is the short version. I will add specific turning points and lessons as I continue building the archive.
The founding field note
The software changes. The responsibility doesn't.
The Evolution of a Drafter is my longer reflection on judgment, coordination, curiosity, accountability, and what technical practice should become as the tools change.
Read The Evolution of a Drafter