I get better model reviews when I treat every scene as an artifact with a purpose and a status. In this workflow, InfraWorks helps me inspect a broad setting, Shapezo gives me a quick generated context model from a map selection, CityEngine tests repeatable district rules, Archshaper explores a bounded building option, and OpenRoads carries the civil corridor decisions that need engineering structure.
Start with a project manifest
Before I open a model, I create a small manifest. It records the area of interest, coordinate reference, units, source date, expected level of detail, and intended use. I also add a status: source, generated, conceptual, designed, or verified.
This protects the handoffs. A context scene can be useful without being survey-grade. A generated building block can be useful without being ready for quantities. The manifest keeps that distinction from disappearing once files move around.
Build the regional context in InfraWorks
InfraWorks is my first visual review space when roads, terrain, water, existing buildings, and a proposal need to be compared at once. I use it to look for large-scale conflicts: poor access, a steep approach, a visible utility corridor, a bridge landing, or a river edge.
For each saved view, I retain the boundary and input date. A screenshot without that context is hard to reproduce. A stable view setup makes it easier to compare alternatives and identify when the difference comes from a design decision rather than a camera angle.
Generate a provisional branch in Shapezo
Shapezo begins with a selected map boundary. I frame a region on the map, and its AI generates a model for that area. This is helpful for early options where I need a quick representation of a place before detailed manual work exists.
I save the selected extent, generation date, and a note that the geometry can be inferred or simplified. I do not use it as controlled design geometry. I use it to spot missing context and create a short list of questions for authoritative mapping or survey data.
Test district behavior in CityEngine
CityEngine lets me encode repeated urban relationships. I can define block dimensions, parcels, setbacks, height ranges, and street patterns, then generate alternatives from a consistent rule set.
I version the rules with the output. If a scenario changes, I want to know whether the cause was a new boundary, a revised input layer, or a changed rule. That is a better debugging story than trying to infer intent from a final render.
Move the building question into Archshaper
Archshaper is useful for early building massing and site-fit work. I use it to explore access, frontage, mass distribution, open space, and the relationship between a building volume and the surrounding block. The output belongs in the conceptual branch until assumptions such as setbacks, grades, and nearby geometry are checked.
I keep architectural massing separate from the civil corridor model. They need to talk to each other, but they do not need to make the same claims at the same time.
Carry civil decisions in OpenRoads
OpenRoads is where I rebuild or establish the corridor with explicit engineering inputs. Alignments, profiles, templates, drainage, quantities, references, and sheets can remain connected as the design changes.
At this handoff, I verify stationing, units, vertical datum, surface references, and corridor limits. If an early line came from a generated scene, I use it as a visual reference and rebuild the design geometry from constraints. That extra step avoids silently promoting a concept into an engineering deliverable.
Reusable checks
- Record coordinate systems and units at every import.
- Preserve the selected extents and source dates.
- Mark generated and verified geometry separately.
- Version CityEngine rules with each scenario.
- Keep screenshots as review aids, not as the sole source of truth. The pipeline is not about forcing five tools into one file. It is about making each handoff legible. InfraWorks provides context, Shapezo gives an early generated branch, CityEngine tests rules, Archshaper tests building form, and OpenRoads carries connected civil design. A clear status for every artifact is what makes the whole sequence dependable.
Top comments (0)