Skip to content

New projects

BIM Modeling & Coordination

Coordinated digital models that resolve conflicts before they reach the field and produce clearer structural deliverables.

Applies to
New construction
Coverage
Miami-Dade & Broward County, Florida

When you need it

Find the conflicts before the site does.

Most conflicts between the structure, the architecture and the mechanical, electrical and plumbing systems are discovered on site, where they cost the most to fix. A coordinated model moves that discovery back into design, where it costs a conversation instead of a change order.

  • 01The project team works in Revit and needs the structure modeled to the same standard.
  • 02The owner or contractor requires a federated model and clash reports as a deliverable.
  • 03Ducts, pipes and structure keep colliding on drawings and someone has to own the resolution.

Design teams running multi-discipline coordination · Contractors requiring model-based deliverables · Owners who want the as-designed model to survive into operations

Scope & deliverables

What's included

  1. Structural modeling — foundations, columns, slabs, walls, framing
  2. Federation of structural, architectural and MEP models
  3. Interference checking and clash resolution tracking
  4. Model-derived drawings, schedules and quantities
  5. Coordination meetings and issue reporting
  6. Model delivery aligned to project information requirements

What you receive

  1. Structural model at the agreed level of information
  2. Clash and issue reports with resolution status
  3. Model-derived drawings and schedules
  4. Coordination record for the project file

Next step

Tell us the software the team uses, the level of detail required and the coordination schedule. We propose the modeling scope and the exchange format.

How the work runs

01

Set the rules

Shared coordinates, level and grid naming, model breakdown and level of information agreed before modeling starts.

02

Model the structure

The structural model is built as the design source, not as a drafting by-product.

03

Federate

Discipline models combined and checked against each other on a fixed cycle.

04

Resolve

Conflicts logged, assigned and tracked to closure — with the structural fix engineered, not improvised.

05

Deliver

Drawings, schedules and the model itself issued as one consistent set.

Good to know

What changes the scope — and what no engineer can promise.

  • Coordination quality depends on what the other disciplines deliver and when; the process is collaborative by definition.
  • A model is not a substitute for a signed and sealed drawing set — it supports it.
  • Level of information should match the decision being made, not the largest number available.

Software & open standards

The model has to survive the hand-off.

We work in the tools the rest of the project team already uses, and exchange through open formats so the model does not become a dead end when it leaves our office.

  • RevitStructural modeling
  • NavisworksClash detection
  • AutodeskPlatform
  • CYPEStructural analysis
  • BCFIssue exchange
  • buildingSMARTIFC / openBIM

Product names and logos are the property of their respective owners and are shown to identify the software used in our workflow.

Next step

Tell us about the building. We reply with a scope.

A county notice in your hand, a building that worries you or a new project — describe it and attach what you have. A phone photo of the letter is enough. You hear back from the engineer, with questions or with a written proposal.

Miami-Dade & Broward County, Florida