Data transfer from one GH model to another GH model

Hi everyone :slight_smile:
I am in a great need of help as my GH model (14MB in size) is currently composed of a section that is generating the parametric models, a section that compiles the data and sends it to Midas Civil NX for analysis aaand another section that enhances the data with more metadata (UDAs) and sends it to Tekla Structures. As my code is so huge, from time to time, it triggers ultra-paranoid mode both for me and for Grasshopper.
I have started to split the big model into 3 smaller (smaller = still 9MB for the largest remaining one) parts but I am struggling with data transfer from one to another as I have loots of data to transfer.
My current approach is to output the data (Data Output object) from the first section by entwining (graft enabled) all data pipes (remote sender/receiver couple) that I need for the second section and, on the first branch ({0;0}) of the entwine component I added a list of all remote senders/receivers NickNames.


Then, in the other GH model, I import the data (Data Import component) and I use a python script + a cluster to retrieve the correct data for the correct remote sender/receiver. The python script is connected to the output of the remote sender and it ONLY takes over itโ€™s NickName. Then, the cluster takes over the NickName from the python component and searches for itโ€™s index in the list supplied in {0;0}. If found, the cluster knows exactly where the corresponding data is in the data structure and only has to extract and deliver it.


My problem is that section two has even more data pipe lines (~100) and it is veeery hard to make sure that the NickName of the remote sender/receiver connected to position X in the entwine component is exactly on position X in the list in {0;0} because if it is not, then the data will not end up where it is supposed to be on the other side.
As such, I am asking you if you see any other viable approach for this whole story and if not, is there any possibility of creating a component that works exactly like an entwine but also attaches the NickName of the connected remote receiver automatically somewhere in the data so that the previously mentioned, manually created, list of NickNames is not neccessary anymore?
Thank you in advance and looking forward for your proposals :heart:

@Radu_Felecan

maybe speckle is useful here.

speckle-releases