Hello @PBRimbault ,
you can get involved with the Tekla connector by helping suggest workflows that you need in particular in this thread or sending me models to test out the alpha on or be a tester when the alpha gets released. If you want to speed the development along faster, we can talk more to see how we can get you started.
Two cases - either as an import tool pulling scenes into the editor for further manipulation, or live, as part of some live showcase/optioneering app to put in front of clients.
Faster visualisation, continuity of attribuition (which an fbx/obj conversion would demolish), all in favour of visualisation.
(Side thought re. navis… a “comment/task” schema would allow you to do things like commit to-do tasks through a vis app and have them populate the navis model?)
Would be cool to see Synchro Pro/Bexel manager or similar tool that’s used for 4D BIM planning.
Keen to see a connector for Autodesk Plant 3D.
Plant 3D has 2 big sections, a schematic design tool to produce P&IDs (piping and instrumentation diagrams), as well as a 3D modelling environment which creates 3d piping models, for the most part. It’s a bit like fabrication MEP, but sits on AutoCAD and also produces ‘parametric’ models of equipment items (configurators for pumps, vessels, heat exchangers). As Autodesk have it, everything sits on a collection of SQLite databases, with an option to key into SQL server and BIM360 collaboration. Key powers of Plant versus others:
-
‘Specification driven’ piping. Basically, a series/collection of components which may be applied to different conditions such as service (chilled water, avgas, effluent, steam). This includes an acceptable selection of valves, filters, guages, flanges and couplings, branch connectors and so forth, which can also change at different diameters.
-
Validation between piping and P&ID databases.
-
Generaton of ‘piping isometric drawings’.
-
Creation and control of systems and their connections between collections of equipment items and facility areas.
Workflow
We would like to be able to move 3D plant data without losing connection information, attributes or geometric fidelity in particular to Revit for the management of these families and creation of better deliverables. We’ve found that the AutoCAD drawing engine as they have it, is no longer appropriate for the risk and effort levels required, for example:
-
time it takes to generate a single view. Instead of (more or less) instantaneous performance we can attain from Revit, plant 3d goes through a process of ‘flat shotting’ and layer reassignments, so this process can take minutes or more
-
disassociated annotations such as sections and view titles.
Also - there is no visual scripting environment for Plant 3D available. If we are able to create connector(s) which understand each schema then we open up to the opportunity to create a more user friendly automation library.
I’ve done an AU preso on some of these issues, which might explain these more.
Thanks for the detailed workflow @Matthew_Randell !
I’m still shocked at how poorly interoperable Autodesk software is - we’ll definitely check out what we can do 
It’d be great to see an OpenLCA connector. @timmcginley is launching a new LCA in Building course at DTU and we are working on easing LCA evaluation, integration with modelling in a BIM environment. More integration with software oriented on circular building and sustainability could be awesome! Thank you. 
I see a lot of people have voted for Navisworks, how do you see that integration working? What information would you like to exchange with Speckle and how do you see it working overall?
PS
Thanks @bruadam !
As someone who works for General Contractor, sometimes we only get Navis files from the Appointing Party in the tendering process. Having all the info and geometry available in Grasshopper would save me a lot of time I think.
Exporting clashes from Navisworks and managing issues in a Speckle powered app. Importing clash views from Navis into Revit and solving them one by one.
As someone who works for General Contractor, sometimes we only get Navis files from the Appointing Party in the tendering process. Having all the info and geometry available in Grasshopper would save me a lot of time I think.
Navis → Speckle is possible. Geom + Data. Navis only knows about Meshes.
Speckle → Navis is a bit of a non-starter. You can augment data to objects already in the Model, but any geometry you generate by API (and that isn’t straightforward) can’t be used for scheduling or clashing.
Exporting clashes from Navisworks and managing issues in a Speckle powered app. Importing clash views from Navis into Revit and solving them one by one.
So that’s a “two-plugin” request. 
Now, while @teocomi is a quiet expert in exporting Navis issues, I also have something bubbling along in the background. I’m working on an NW plugin that syncs Issue data and Viewpoints in real-time to a browser view. It uses Firebase and GCS for images right now, but I have a strong inclination to port the app as a Speckle implementation for 3D interaction. What you describe is a workflow that could be a BCF server end-point for speckle - which is food for thought.
We’ve definitely been mumbling internally on supporting BCF-style issues within Speckle, and you’ll probably see a beginning with some commenting features soon 
So yeah, we definitely want to add Navis to the mix, but it might take a while before we can properly integrate it 
Thanks to both for the feedback!
People voting for ArcGIS, great news, some planning is being made in this direction! Please help us understand better your AcrGIS usage and interoperability needs by responding to the survey: ArcGIS connector survey
Yeah Navis will be awsome! since it works as an integration platform for a lot of formats, instead of developing a ton of connectors you could use Navis as a federation tool for models and them Speckles to send data where is needed. it will solve a lot of workflows where you need to extract data from models and process it.
BIM Track!!!
I had forgotten but am now amused to see the request I recalled was from @gokermu about Navisworks.
There is a two-part solution to my orignal pessimistic response. 
This is a different way of thinking about integration than other connectors which inject data into scenes within Connectors, but in theory, works. A Navisworks 
Connector would save a ‘Read’ as a model.speckle file (essentially rehydrated JSON) and a separate loader plugin would then convert to NWC and either aggregate or refresh that NWC file into the Scene. There will be a bunch of UX nicety to managing the streams/files in a model that is a less interesting challenge 
but, I have the download and conversion at least a little bit underway.
So, hopefully, that’s some embryonic good news, even though you are now more capable than I am to fulfil your dreams.
And, yes, I have considered that this raises the mouthwatering prospect of another ADSK workaround like Revit down-versioning where you can theoretically build your own NWDs from frozen published NWDs sent from others. 
Just some suggestions:
PTC-Creo (or step as common format)
Navisworks to anything (step, dgn, …)
Autodesk Plant 3D to AVEVA PDMS and vice versa
Thanks @Jens !
I moved your topic here as we already have a growing list of connectors to develop 
In regards to navis, the good news is that there is already a community contribution in the works!