CSI Supported Elements - Work around for Node Elements can only send

Hi all, I note from the Speckle Docs that for the CSI software Supported Elements there is a limitation where only Node elements can send.

For example: SAP2000 Supported Elements

I can of course create more nodes and convert loads to fit this constraint but are there other common workarounds?

My purpose is to primarily to identify and resolve potential questions before a broader audience in my business tries to pick up more use of Speckle.

Thanks in advance.

1 Like

Hey @chrisbest200!

Welcome to the community and thanks for posting this! :cool_spockle:

This has been on my to do list for a bit, so thanks for the nudge on it! Could you tell me a bit more about your workflow? Are you wanting to create load assignments outside of CSI Products (e.g. Grasshopper) and receive them inside ETABS / SAP? Or are you wanting some sort of connectivity between ETABS and SAP?

1 Like

Hi Björn, I don’t have a specific workflow myself at present, but I am targeting more of an approach that ties together Parametric Design and Single Source of Truth. I am certainly using a lot of Grasshopper generally and I do see this as a likely part of many solutions going forward. I have also have a bit of knowledge with the BHoM too.

So the ability to automate and control information through Speckle and Grasshopper is a strong positive. However, I know that if there aren’t easy workarounds or solutions to the managing load assignments (particularly parametrically), many of our engineers will ‘fall back’ to traditional workflows and hence the benefits of Speckle (and Grasshopper) might not be realized by them and our business.

Knowing how this is addressed by others, or knowing a solution is coming, allows me to head off some of the questions I know will come and to try to make the transition to the platform more easier for more analysis driven Engineers.

Hopefully this gives you some more clarity but also happy to provide more context if you have questions.

1 Like

Thanks for the explanation @chrisbest200!

Integrity of loading data is indeed extended beyond just nodal loads. See below:

Loading information sent from ETABS to Speckle

This can be received and decomposed in Grasshopper

We have things setup for the workflow in reverse as shown, but things can get tricky depending on workflow nuances. Happy to discuss this in further detail - we can gladly setup a call for that :slight_smile:

Long story short, solutions are in place and more are coming to support workflow connectivity. Moreover, with Automate, engineering QA and QC processes can run on top of model data. Giving even more clarity.

An extended example / application can be experienced IRL here at our 2024 SpeckleCon in two weeks: Gergő Jedlicska on LinkedIn: #bim #specklecon2024 #speckle #automate

1 Like

Thanks again, you have provided a lot of information and I will dig deeper into what you have provided. I will particularly look into Automate, as QA/QC is a common reason I hear for not adopting these sorts of workflows (in my view very incorrectly). I will also try to work with my team to generate what sort of workflow they are looking to use and hopefully I can ask more specific questions.

1 Like