Please note:
- Civil3d Native object properties will export through to a Navisworks file but not during an IFC export.
- Aec Extended Properties will pass through to both Navisworks and IFC.
This is why the information you're expecting won't come through the IFC file.
Using NWC export is limited to only those contexts selected by the export tool programming and as with dwfx will not add user defined context entries added to the partparam xml file.
DWFx files is the only version to publish Native QTO data, Nwc ignores this.
SO;
- If you want details available in Revit, IFC is the way forwards but you need to add everything of relevance as an Aec Property Data table.
- If you just want Civil3d OTB contexts & parameter information then just export to Nwc to get the basics into Navisworks.
- If you have Custom Contexts then you need to use Aec Extended Properties which will pass between either Ifc and Nwc files.
Aec Extended object Properties
Although I have created this data using a program the principle should still work (see image).
Type PropoertySetDefine and create a new style table called Pipe Table and one for Structure Table, set each object types to pipe or structure respectively.
Add all details for pipes in the pipes one and structures in the other. Once the data tables have been attached to the structures and pipes.
NB: See elsewhere for detailed tutorial regarding adding automatic information Chris@Civil3dReminders has a good example on his blog site.
Now type IFCexport and export the file.
Open the IFC in Navisworks and you should get the data displayed on the Pipe Table or Structure Table Tabs.
Hopefully this will assist.
Mike
Below in Navisworks from IFC export of the StructurePropertyTable data attached to structure.

Mike Evans
Civil3D 2022 English
Windows 7 Professional 64-bit
Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz (8 CPUs), ~4.0GHz With 32768MB RAM, AMD FirePro V4900, Dedicated Memory: 984 MB, Shared Memory: 814 MB