New Connector Request - Autodesk Plant 3D

Autodesk Plant 3d :smiley: In the energy and industrial market, Plant 3D is used for detailed piping systems that operate at different pressures, temparatures and risk levels to those in the Built environment. Creating a connector here would open us up to options to work in collaboration with energy distribution and storage, and food and beverage disciplines.

1 Like

Thanks @Matthew_Randell , great suggestion!
Do you have any specific flow in mind? How does it natively integrate with Revit & such?

I don’t have any experience with it so this would help us see how to fit it in our roadmap :slight_smile:

Hi teocomi, the Plant 3D - Revit workflow is something we are very very interested in. We currently go from P3D, to navis, to .ifc then into revit using a couple of add on salong the way. Happy to offer any support in making this workflow happen as the speckle platform looks a great one to work with. Cheers, Dave
@J_Loay

4 Likes

Any chance someone is working on a connector for Autodesk Plant 3D?

This is something we have heard, albeit so far infrequently.

As it turns out from the search, twice from @Matthew_Randell .

Matthew describes his ideal workflow in good detail. Is there anything you think to add?

Some users have begun having success via Navisworks, which is supported and, in-turn supports Plant3D.

Thanks for the response! That was my thinking originally was to use the SQLite reports/databases from P3D and leverage the Navisworks connector to make connections later on down the road…just wasn’t sure if a more direct connector was in the works or on anyone else’s radar.

We also already have a solid AutoCAD connector, and if I’m not wrong Plant3D is just another AutoCAD verical, meaning it shares most of the API.

If anyone wanted to pick up the challenge, we’d be glad to help support the development!

2 Likes

Hi @teocomi,
I’ve tested opening P3D files using Autocad as an alternative to Navisworks (as I can’t seem to import from Navisworks to Revit) as, as you said, it’s basically Autocad. However it doesn’t send all the geometries. It would say ā€œImpEntity - not supportedā€, however only it only affects some pipes & pipe connectors. As a random test I tried ā€˜exploding’ the whole model and surprisingly it would send just fine. Navisworks sends all the geometry just fine, just can’t import to Revit.

2 Likes

Wow, I saw a lot of people care about Plant 3D, me also same :sweat_smile:

3 Likes

Thanks for looking into this! Could you share a sample P3D for us to have a quick look?

I’d love to help look into why the Navisworks route didn’t work for you, would be good to have that at least as a fallback.

Can you share the project stream?

1 Like

We are interested also for a Plant3D connector, can be very helpfull

1 Like

Feel free to vote on this feature:

1 Like

Useful! there is a huge demand for this connector in the Energy Sector, one of the largest and growing sectors Globally. WSP would be very interested.

1 Like

@Aydimir_95 The bad news is we haven’t progressed support for more of the AutoCAD vertical. The good news is that we can publish Plant3D data via Navisworks.

Which workflows were you looking to support from Plant 3D and potentially Speckle?

We were looking Plant 3D to Revit workflow.

The development of the Plant 3D to Revit Connector has become a top priority at WSP. If you are looking to secure WSP as a client, this presents an excellent opportunity. We are currently considering hiring a team of Autodesk experts to create this tool, though I believe Speckle might be the most suitable solution.

Hello, there is currently a tool that Autodesk is developping, I’m working for WSP in Quebec Canada aand we are testing it now.

1 Like

@Aydimir_95 I’m happy that WSP already uses Speckle from various connectors, but we do hear your request. Regardless of what @McLean (your non-adjacent colleague) is testing, have you already tried the route through Navisworks into Speckle?

We see a lot of traffic from many of the AutoCAD verticals via that Navisworks route, including from Civil3D, for which we have a connector already. :spockle_smirk: