Navisworks and Revit: coordinating civil models with a BCF workflow

A coordination issue is useful when another person can locate it, understand it, and verify the resolution. An emailed screenshot may explain a conflict, but it loses value without model revisions and responsibility. A BCF workflow helps structure issue communication between compatible tools and teams.

Coordination begins before opening Navisworks or Revit. Civil geometry needs known units, coordinates, and scope. This guide separates model preparation, where NM Civil Solutions plugins can contribute, from issue exchange and tracking through a compatible BCF implementation.

1. Agree on the exchange before starting

BCF is a buildingSMART standard for communicating issues and their context. It does not replace the geometry model. Agree both the model delivery method and the compatible tool or platform that will carry the issues. These are related but separate parts of the workflow.

Check versions and available integrations rather than assuming that every Navisworks or Revit installation supports the same process. Create one simple test issue and open it at the receiving end. Verify which references and contextual information survive the exchange before committing the whole project to the workflow.

2. Give the civil model an identifiable source

Record coordinates, units, discipline, owner, and revision. Distinguish preliminary context from geometry intended for detailed checks. Otherwise, a regional terrain surface may be interpreted as a final construction reference, leading the team to draw conclusions that the source cannot support.

NM Terrain supports TIN-surface preparation from elevation sources in Civil 3D. It can provide territorial context for reviewing infrastructure against the site. Keep source and resolution information with the model and use appropriate survey information for checks requiring detailed accuracy.

NM Hydraulic Builder supports parametric channels, pipes, and hydraulic structures as 3D solids in AutoCAD and Civil 3D. It helps prepare civil components for later coordination. Test the receiving geometry and properties with a small sample. The plugin is not presented as a BCF exporter or a native Revit-family generator.

3. Validate the combined model first

Use a small collection of recognizable objects from each discipline. Check a known location and control dimension, then confirm elevation and orientation. A long conflict list has limited value when the models do not share the intended reference or when a unit conversion has changed their scale.

If the agreed exchange requires extracted surface geometry, Advanced Surface Manager provides organization and extraction tools in Civil 3D. Select a suitable representation and test it through the actual receiving workflow. Do not assume that every property survives every conversion.

4. Write an issue someone can act on

Use a subject that identifies the conflict and area. Explain the observed situation, required outcome, and question to be resolved. “Fix the model” gives the recipient little guidance. A useful issue should let a reviewer determine the next action without reconstructing the entire project conversation.

• Identify model revisions and affected objects where the integration supports it.
• Save a clear view with enough surrounding context.
• Assign responsibility and a verifiable condition for resolution.
• Record the decision, including accepted conditions that need no geometry change.

For a channel intersecting a foundation, identify the civil and structural revisions and explain which alternative needs evaluation. A screenshot alone does not establish whether the channel, foundation, or coordination assumption should change. That decision belongs to the project team.

5. Verify closure against a new revision

A reply does not prove that the conflict is resolved. Load the corresponding revision, check its identity, and repeat the relevant review. Closing an issue against old geometry or a screenshot from a different delivery creates a misleading record of project progress.

Retain the relationship between issue, decision, and accepted revision. If object identifiers or exchange methods change, confirm that the references remain useful. State what was checked and why the result was accepted, especially when several disciplines edit the same area.

Putting the steps together

For a drainage project, prepare the Civil 3D context, model the required hydraulic components with Hydraulic Builder, and validate their exchange into the coordination environment. Check position and geometry before documenting conflicts, then use the agreed BCF-compatible tool to assign and review issues.

The NM plugins support organized civil preparation; BCF tracking remains the responsibility of the compatible tools selected for the project. Review our automation services or describe your workflow if you need additional checks or project-specific reporting.