Civil 3D + 1: Supercharging Your Workflows with the Autodesk AEC Collection (Navisworks Part 4 of 5)
Civil 3D is your engine, but pairing it with 2–3 other AEC Collection tools turns it into a full production line that’s faster, more accurate, and easier to manage.
In this series, Shawn will walk through practical, low‑friction ways to pair Civil 3D with other tools you already have: Autodesk Docs (Forma Data Management), ReCap Pro, InfraWorks, Vehicle Tracking, Navisworks, etc. He’ll tailor this towards CAD managers, but any firm, big or small, can take advantage of the “Plus One” mentality. As a CAD manager, you don’t need to turn your team into power users of ten different programs. You do need to define a few core “paired” workflows where Civil 3D stays the primary environment, but other tools quietly handle reality capture, data management, visualization, and analysis in the background.
The goal is simple: make the work your team is already doing more efficient, more predictable, and easier to manage at scale.
Civil 3D Is the Hub, Not the Whole Machine
Civil 3D is still the design and production workhorse for corridors, grading, and plan sets. Your standards, styles, and templates all live there, and that’s not going to change anytime soon. What has changed is the ecosystem around it.
The AEC Collection is designed so models and data move between applications rather than living in isolated DWGs and PDFs.
For most land development shops, the lowest‑effort, highest‑impact combinations could look like this:
- Civil 3D + Autodesk Docs (Forma Data Management) for controlled project data and reviews.
- Civil 3D + ReCap Pro for accurate existing conditions from scans.
- Civil 3D + InfraWorks for faster concept design and visualization.
- Civil 3D + Vehicle Tracking for integrated swept path checks.
- Civil 3D + Navisworks for easy clash detection.
- Civil 3D + Dynamo for endless process automation.
Today, let’s look at Navisworks. Check back tomorrow for Dynamo for endless process automation.
Civil 3D + Navisworks: Clash detection for Civil 3D object exports
You can absolutely use Navisworks to clash‑check Civil 3D object (corridor, pipes, etc) exports; the key is exporting in a way Navisworks can reliably read, then setting up smart clash tests and tolerances. In just a few simple steps, coupled with very simple CAD standards and settings, you’re minutes away from clash checking just about anything in Civil 3D.
1. Prepare your Civil 3D model
Focus on getting a “clean” Civil 3D file before export:
· Use a dedicated Navisworks export drawing with only the relevant corridors, surfaces, and pipe networks data‑referenced in, not your working file.
· Make sure the corridor model is fully rebuilt, with appropriate code set styles so all key elements (pavement, subgrade, daylight, etc.) display as 3D solids or surfaces.
· Turn off or freeze nonessential layers so they don’t clutter the Navisworks model; only visible objects export via NWC.
For checking corridor vs. utilities (or gravity vs. pressure networks), ensure utility networks are modeled in 3D with correct elevations (gravity pipes, pressure pipes, or 3D solids).
2. Export from Civil 3D to Navisworks (NWC)
Use the built‑in exporter so Navisworks reads Civil 3D geometry correctly:
· In Civil 3D, run NWOPT to review exporter options and verify units and coordinate handling are correct.
· With only the needed objects visible, run NWCOUT and save the corridor model to an .NWC file in your project location.
· The exporter will include Civil 3D objects, surfaces, and xrefs that are visible in the current view, so use layer control to manage what goes across.
Repeat this as needed for other discipline models (e.g., structures, MEP, utilities, Revit models) if they are not already in Navisworks.
3. Build a coordinated model in Navisworks
In Navisworks Manage:
· Append your Civil 3D corridor NWC along with utility, structural, and any Revit or IFC models into a single coordinated model.
· Verify coordinate alignment (shared coordinates / project base) so the corridor aligns properly with utilities and structures.
· Use Selection Sets to group objects: e.g., “Corridor ‑ Pavement & Subgrade”, “Existing Utilities”, “Proposed Utilities”, “Structures”.
This makes it much easier to create targeted clash tests (corridor vs. utilities, subgrade vs. structures, etc.).
4. Set up clash detection for corridor checks
Use Clash Detective in Navisworks Manage to compare corridor elements against other systems:
· Create a new clash test (e.g., “Corridor vs Proposed Utilities”) and set Set A = corridor solids/surfaces, Set B = pipe/utility networks or 3D solids.
· Apply appropriate tolerances (clearance values) using clash rules and tolerances so you can check either “hard” clashes or maintain a buffer (e.g., 1 ft vertical clearance).
· Optionally, enable rules such as “Ignore items in the same layer” or discipline‑based rules to reduce false positives.
Run the clash test to generate clashes and use viewpoints/comments to document issues; you can then export clash reports or integrate with ACC/Navisworks issues for tracking.
A few practical tips when using Navisworks for corridor clashes:
· If corridor components come through as surfaces instead of solids, consider extracting corridor solids in Civil 3D (e.g., for pavement, subgrade) so clashes behave more predictably.
· Use a simplified style for the “Navisworks export” drawing: no contours, labels, or unnecessary linework, just 3D design geometry and key references.
· For pipe networks, you can still use Civil 3D’s Interference Check for quick checks, but Navisworks gives you a more holistic, multi‑discipline clash environment and better reporting.
Simple Tutorial: Export a road corridor from Civil 3D to Navisworks
In part 5, we will finish our series looking at Dynamo.
BIO: Shawn has been a part of the design engineering community for roughly 20 years in all aspects of design, construction and software implementations. He has implemented and trained companies across the Country on Civil 3D and other infrastructure tools and their best practice workflows. Shawn can be reached for comments or questions at sherring@prosoftnet.com.
