Unleash 2D-3D Collaboration Across Your Tools with Autodesk Data Exchange

PHILIPPE VIDEAU: Hi, everyone. My name is Philippe Videau and welcome to our class called Unleashing 2D and 3D Collaboration Across Your Tools with Autodesk Data Exchange. Today we're going to get into connected data flows between many of the 2D and 3D CAD and BIM applications you might use in your everyday, like AutoCAD, Revit, Civil 3D, and Tekla Structures. And we're going to be talking about Autodesk Data Exchange, a new interoperability and collaboration tool that you can use to share data across these applications.

Before jumping in just a quick note about myself, I've been at Autodesk for over seven years. I've been working on our cloud data team to help bridge the divide across our applications and teams in the way those to work with each other. I'm here with Gaurav Bhamre. He's my colleague and fellow product manager on our cloud data team working on our connector ecosystem and has a ton of experience in architecture and BIM applications.

Before we get started, just a quick note on the safe harbor statement here. We're-- a lot of text here, but basically we're going to be looking at and stating some planned or future development that you'll see, especially in our roadmap slides but throughout the presentation. Basically, don't make any purchasing decisions based solely upon the content in this presentation.

All right, quick overview of the session outline. I'll kick it off with an introduction of our cloud platform vision, where we're going with that cloud platform, and then start to expand on how Autodesk Data Exchange fits into that platform vision. I'll give you an overview of that. And then we'll walk through the meat of the presentation, which is the workflows on 2D and 3D collaboration. So you'll see a couple of the different, maybe, common apps that you use in your workflows-- 2D, 3D, BIM, and CAD applications-- and we'll get into some demo videos there.

Gaurav will take the bulk of that and then he'll get into how you can get started with Autodesk Data Exchange within these workflows. And then we'll have a couple of slides at the end on what's coming next with our roadmap.

All right, so before jumping into the topic of interoperability and how you might share data across the apps and teams you use, I want to step back a little bit and talk through why this is important and why all this requires a platform mindset, not just an application or tool-specific view. And really how a platform-- want to talk through how a platform mindset is a change across our industry, not just from Autodesk perspective as a software vendor, but also from your perspective as folks who work within architecture, engineering, construction, within design and manufacturing, or within media and entertainment. We'll obviously be focusing more on AEC in this presentation but certainly applies to those of you who use those other design and manufacturing and media and entertainment tools as well.

So one piece that has clearly become more and more critical to our industry, especially with the onset of more analytics, more-- the buzz around artificial intelligence and machine learning-- all of that requires data. It's the new fuel of our industry. Not only does a ton of data go unused across AEC projects-- you see some of the statistics there, almost 96%-- but there's also a rapidly growing desire from owners, from contractors, from architects to make better use of data across more connected design build and hand off process.

And when we look at some of the benefits of using data, powering insights, powering real time analytics, again, those AI and machine learning systems and then using all that to improve your current projects to improve future projects based on past or future performance. We all want to build better for the future and use those insights to really influence better future buildings and how those are designed and built.

For this to work, data needs to flow seamlessly across applications and services for it to be most useful. And when that data gets locked into a specific tool, that's really the first hindrance to its use. So to actually realized the full opportunities around unlocking insights across the entire project lifecycle, it's important that data flows across industries too.

Buildings don't just involve the use of architectural and engineering tools, they evolve. They're becoming more like products themselves through processes like industrialized construction. They require more visualization and interactive tools like digital twins. So the traditional silos that existed and that still exist largely between our industries are also collapsing too. And a platform that can surface and connect data easily across these can best unlock these opportunities.

And we're talking about tools that are Autodesk-built, we're talking about tools that aren't Autodesk-built, maybe your own custom tools as well. So connecting all those different applications, that's what we've built and continue to evolve with on Autodesk cloud platform.

And a part-- and an emerging part of that platform is helping tools connect better through Autodesk Data Exchange. And today I want to focus on interoperability and sharing connected data across the tools you use every day and we'll get into specifically those 2D and 3D tools as well. Looking at Autodesk Data Exchange, it's a relatively new platform product that we released last year and have been rapidly evolving since.

So we largely started this platform journey and especially our work on interoperability because we heard from you, we heard from our customers, and saw ourselves that really the fragmentation in how data flowed through our products and also the third party products. Collaboration, as you probably already and live and breathe, is-- in AEC is very fragmented through some of the data challenges shown here.

For one, this happens because there are a ton of tools used across an AEC project-- across AEC projects with lots of vendor offerings. Sharing data is inconsistent across the board, even between our own products at Autodesk.

Data sharing is time-consuming, taking your teams away from the creative and differentiating work that you need to push your business forward. It can be really costly with maintenance of different plugins that allow for the reading and writing of different data across those tools. And, also, it frequently involves a lot of manual effort, leading to manual errors when you share or reshare data from the same project.

Secondly, we work in a collaborative world where delivering a project requires multiple firms and stakeholders and that's just the reality. So on top of the fragmented tools that are out there. You have to manage cross-company data flows and managing who has access to what data can be complex. And that especially becomes top of mind when your company needs to protect your own IP, your own design intent IP, and really when you need to share only what's necessary with stakeholders.

Lastly, projects aren't getting any simpler. The amount of bespoke requirements and collaborators is only increasing. So given that tool fragmentation, this makes keeping stakeholders up-to-date even more difficult and costly with the current set of tools and ecosystem. And when you're looking to automate your processes, having data flow and having that data connected effectively across those tools is paramount.

So a lot of this happens today because of file-based collaboration is painful for a number of reasons. Today files are the smallest unit of collaboration. And as files move between different products in organization-- organizations, there's a patchwork of standards which really results in no collaboration standard, especially across companies. This results in challenges like translation-- costly translation. It results in versioning overhead, which means that you, perhaps are BIM manager, have to manage a bunch of different versions of different files across your teams. And then like we had mentioned, lastly, it makes the exchange of data across those boundaries, across those organizational boundaries difficult, especially if you have IP concerns.

So what we're doing at Autodesk is we are taking those files and we're cracking them open into those valuable bits of data, the different objects, the properties that represent a building, a product, you name it. We're taking those bits of data and we're storing them, we're standardizing, and we're managing that as more transparent data in the cloud.

This will help us to start to standardize and simplify collaboration across our applications and teams, so that you can take just the bit of data you need, share it with another application, another team, another person, and they can send that data-- their relevant data back to you all through the cloud.

Data stays in sync when updates occur upstream, downstream. And so that's what we're starting to build with Autodesk Data Exchange and on our platform, an experience to allow you to share the right data with the right person in the right context. And that's what we're calling Autodesk Data Exchange.

So, again, our primary mission is to hit on those pain points, is to start to connect this-- these apps together into a connected application ecosystem, where data sharing is simplified, standardized, and streamlined across the tools and teams you work with. We really want to make sure that you can also curate the data that you share so you can protect that IP, so that you don't overshare and overburden stakeholders with too much data noise.

And then, lastly, so that you can build more automated systems across the tools you use. We want to ensure that data is connected, that it's durable and reactive with changes that happen in different applications, and that you can control how those changes, how those notifications propagate across the ecosystem.

So I'll show-- go through a quick demo video of how data exchanges work at a high level. So, yeah, so data exchanges as you mentioned-- or as I mentioned-- taking a subset of data and propagating it across different applications so that you can share the relevant data with stakeholders and then having that data move back, perhaps, to your own application with updates. So let's take a look at some of these workflows.

So here you imagine you've got an architect using Revit. She wants to share a subset of data, let's say this floor, not the whole building model, but just a certain pieces of it with some stakeholders. She can use our plugin right there, that's the data exchange connector for Revit. She can create the exchange data and share that via Autodesk Construction Cloud like you see on the right hand side, where any stakeholder who has access to the project can come in and view that exchange.

Other stakeholders in the project may be using Rhino 3D in the top right, right there, can bring in that subset of data, the rich geometry. They can map the different properties and categories within Rhino itself. And another stakeholder who might be on the design and manufacturing side halfway across the globe can bring in that same subset of data into a tool like Inventor, again bringing in that rich 3D and property data too.

Now, what's unique here is that when we talked about that durable connection, let's say our architect updates her exchange, those stakeholders downstream can bring in those updates seamlessly. And only the deltas flow, so the latency across these workflows is reduced when you're sharing that data across these applications.

We can also bring in that data into business tools. So here we have Power Automate on the right hand side. Updating that data exchange actually triggers an update to Power Automate, which allows for the writing of just the property data to a table like you see here. We also have connectors for Power BI, which allow you to bring in that property and viewable data into that tool as well. We won't talk too much about that here, but we have another presentation at Autodesk University that covers more of those Power BI workflows.

So we've got a bunch of different connectors, Gaurav we'll talk about that, but, for now, let's keep going here so we can get to some of those demos. So to sum up, Data Exchange is all about sharing those curated sets of really object-based or granular data across those application and country boundaries so that you can have a high level of trust and control over those sharing workflows.

So why might you use Data Exchange compared to some of the other maybe file-based or custom methods that you use today for sharing data? Well, for one, like I mentioned, we're sharing data, not just files, which allows you to control what data gets shared with different individuals or teams.

You don't have to deal with the kind of versioning overhead that you might have to deal with files. You might even use powerful integrations like Rhino inside Revit. That's a great tool for interoperability between [AUDIO OUT]

--tools like Rhino and Revit, but it does require some grasp to simplify that interoperability by using just those application plugins that you saw in the video that you'll see in our subsequent demo videos.

Moreover, Data Exchange includes rich data, so it includes 3D geometry, 2D geometry that you'll see, different parameters and properties, as well as web viewables. So we're really getting at, not just derivations of data, but the rich data itself that you might have challenges sharing today.

Also, like you saw, we're focused on curated collaboration here. So exchanging relevant subsets of data, not your entire model. Oftentimes, we hear from customers, I don't want to share my entire model, I just need to share these bits of data, like you saw in the video there. And that's the sort of level of control that you have using data exchanges. You can create gated workflows that allow you to push and pull data when ready in your tool of choice.

So as an author or as a consumer, you can send data just when you need and you can consume data just when you need. You're not just have an open pipe where data is streaming whenever you make changes.

And, lastly, Data Exchange is supported by a common data environment. This is Autodesk Docs, which is hosted on the Autodesk Construction Cloud. This allows you to manage data and permissions using those out of the box Autodesk Docs permissioning features, so no new tools to use, you're going to be able to use the common Autodesk Docs platform here. You can even use exchanges with common workflows that use different modules on ACC, like issues, transmittals, and bridge.

So, specifically, when we talk about using exchanges within your 2D and 3D workflows, they can provide a significant leg up when transferring data across tools like AutoCAD, Revit, Tekla, and Civil 3D-- tools used for-- you might be using them for site layout, for detailing, for coordination, or for building deliverables. With Data Exchange, you can start to address many of the challenges you've heard and that you experience in these use cases.

First and foremost, across many of these tools, no live link or no associativity exists between the different applications and between that data that is authored in those different applications. So, for example, between Tekla Structures and AutoCAD. Because there's no associativity between shared files, stakeholders oftentimes have no idea what's changed, leading to time spent figuring out what's up-to-date and leading time spent communicating with authors on, hey, what's changed in the most recent file you've sent over.

Data exchanges, in contrast, are tied to the data source. So when authors-- when designers authors make a change they can simply push those changes to stakeholders who can then bring in the modifications and understand what actually changed.

Second, many of you today who may work across Revit and AutoCAD, especially, likely spend a lot of time cleaning up models or DWGs created by Revit, for example. You can see some of the statistics on the right hand side on that interaction between AutoCAD and Revit, some of the struggles that you might experience today. A lot of those are about cleaning up information between those two tools when you share data across those tools.

With Data Exchange, you control the data that gets sent and what you bring in, so you don't need to purge all those unnecessary elements, spend a bunch of time doing that, for instance. Working with the data objects, the data elements will be more straightforward, especially from the stakeholder or receiver of data perspective.

All right, let's get into some workflow demos. I'll kick off this first one. This is a 2D, 3D workflow between AutoCAD and Revit, super common workflow. Here we're using the Data Exchange connectors for those two applications, but we also introduce our connector for Dynamo in order to bring in that AutoCAD data into Revit as Revit native elements so you can do more with the data you've brought in. You can definitely just use the AutoCAD and Revit connectors but for now you'll see that this workflow is much more powerful, again, because it's bringing in those elements as Revit native versus generic models, which will be supported between just AutoCAD and Revit today.

All right, so here we're in AutoCAD and we've got a relatively simple building model-- building layout here. We're going to pop open the Data Exchange connector for AutoCAD. That's what you just saw pop up in there on the left hand side. We can go and select the specific wall elements to create an exchange. We have different filtering options based on the application to select the data that you want to put into that data exchange. Once you go ahead and do that-- and we'll see more on the Revit side on how to do that as well-- that data exchange-- you simply create the data exchange, you select the folder in ACC and you-- and it gets created there.

We can move over to the Dynamo interface. This is, again, a tool that works with Revit. It's a visual programming tool that allows you to level up and automate your workflows with Revit. Here we open the Data Exchange connector and we search for the exchange that was just created by the author. We can load that in using the get exchange node and then we can actually bring that into the Dynamo space and select the different units of measurement, how we want to perhaps translate those units using the receive node, and then we use the data exchange to geometry node to actually convert those into geometry that Dynamo and Revit can ultimately can ultimately read in. So here you see that just the wall objects from AutoCAD or just those that primitive geometry was brought in here, not all the other data that was brought in, just the filtered data.

So what we can do here is we can level up these workflows. So we brought in that geometry, but how do we make it more intelligent? Well, we can use the power of Dynamo and the integration it has with Revit to start to add different categories, or families, or other information that might be useful for our workflow to continue in Revit. Here we're adding the wall category to our model here. And we can see that once we run that script in Dynamo that those wall elements appear. They're built from that 2D-- from those 2D geometries that were brought in from AutoCAD and we can see right there that was brought in as a Revit native wall. Awesome.

So we can continue our workflow in here. Perhaps you want to add different elements, different objects here. We're just going to add a simple floor to show that this data can also be brought back into AutoCAD. So, oftentimes, 3D data might not be brought into AutoCAD from Revit, you can bring in 2D geometry as well from Revit into AutoCAD, again, using this same method.

So here we're going to open up the Data Exchange connector for Revit, we are going to select the Autodesk Docs folder in which we want to share this set of elements or the whole model here in this case. And you'll see there in that connector you'll see that you need to select a 3D view and Revit to share that data. You can also filter by different categories here. So you'll see that filter by, which you'll see in more videos, as well. You simply select create exchange and that will write that data exchange to that Autodesk Docs folder that you had selected.

We can take a look at that, and this works with AutoCAD and all our connectors as well. We can view what has just been created in that Data Exchange on the web. So if we had opened that AutoCAD exchange, it would have looked like a 2D, almost like a DWG in the cloud. This allows stakeholders to view that, even if they don't have access to AutoCAD or Revit.

So here, we're back in AutoCAD. We can open up the Load Data Exchange module, and then go ahead, like we did with Dynamo, select the exchange that we want to bring in that's relevant. And then we just load in those elements that were shared with us. We can do some lightweight mapping of [INAUDIBLE] layers here, and you can see that data comes in nice and smoothly into AutoCAD as well.

All right, so hopefully, you can start to think of some more-- probably more complex applications to use this in, but this is one of the applications you can start to work with, hopefully, in your everyday. And with that, I will pass it on to Gaurav, who will get into some of our other workflows.

GAURAV BHAMRE: Thanks, Philippe. So now, we will dive into other workflows starting with how Data Exchange can support your structural design and detailing workflow. In this case, specifically, we'll be looking at a use case where you have a designer working in AutoCAD and wants to share the site layout or the structural layout with the designer who's working on Tekla.

Of course, this is supplemented by the Autodesk Docs as a platform provider, and this is a workflow where you see 2D information is being used to create 3D structural models and add more details on top of it. So let's dive into the video, Philippe.

So here, we have a small sample set where you can see the structural plans for a building. And as a user, I just want to share a small set of that structural plan. Traditionally, I would end up sharing the entire DWG to Tekla, which will include a lot of cleanup. But here, we are doing the cleanup and selecting the subset just at the time of sharing the data.

So as you can see, I've created a block, and now, as we saw earlier, we can filter by either blocks, layers, or selection. So we have selected the block that we want to share out, and now, we are creating an exchange from AutoCAD. Once the exchange is created, you can view that exchange on Autodesk Docs. That does not require any application, so other stakeholders who want to refer your details can always go on Autodesk Docs and view the exchanges.

Now, we are in Tekla, and we will be loading the exchange in Tekla. As you can see, the experience of creating and loading exchanges is pretty consistent across our different Data Exchange connectors. So once you use some of our connectors, you can get the hang of the entire ecosystem, and the experience remains pretty consistent.

So the user has verified the exchange, and now, yeah, as we just mentioned, we have some lightweight mapping there from elements to Tekla categories. Now, our exchanges have been loaded. We'll just quickly adjust the view, and we can see the-- all right, so now, we can see the layout plan coming up in Tekla.

So the good thing about these layouts is they still work as primitive geometry, so you can snap to the edges and corners and center points of this primitive geometry. So what we are doing here is just checking the height of the columns, so in this case, we will be placing the columns at the central point of [INAUDIBLE] layout plans. We just check the height of the columns, selected the required families or elements in Tekla, and started placing the columns as mentioned in the plan.

When we get these plans over to Tekla, they also maintain the scale and the origin to origin coordinates. So when you create exports out of these 3D models, they are always aligned with your 2D layout plans, so that keeps your coordination effort to a minimum. Right now, we're just creating a simple frame, but you can extend this workflow to complex structural elements, also placing gusset plates, angles, trusses, and et cetera.

So as you see, we created a frame from our 2D layout, so as we saw, these layouts are also in sync with the original source layout. So whenever you have a change in your structural drawings, you can always send the deltas over to Tekla, and the reference layout will be updated. And accordingly, you can make changes into your structural details as well.

On the right side, you can see these elements are showing up under reference models as generic elements, the ones that are coming in from the AutoCAD, but the ones that you've created will always show up as Native Tekla elements. Let's move to the next workflow.

So the next one is site infrastructure coordination, and this is very interesting, because most of the construction project requires heavy coordination between site infrastructure and architectural model and structural models as well. So in this case, we'll be taking up that example with a very small sample set, just a few site elements, and a load data, and see how a structural designer or an architect can work together with a civil engineer or a landscape designer.

And they might be part of a same organization, different organization, different teams, or may be based in two different fields altogether, and you can still coordinate that small amount of data, and you don't have to go through the rigorous process of entire model coordination. So you can tap on to your specific class from Navisworks and grab that particular element and share it over to Civil 3D just for your reference. So let's have a look at the workflow.

So here, we are starting from a basic building structure. The data we are planning to share is a fire hydrant, the road that you see over here along with the storm drain, and the catch basin. As I mentioned, a very simple data set, and we will just use the Revit connector to share it over to our Civil 3D designer, or our civil engineer.

As you can see, we are filtering that those categories that we just want, and there are other options. All of these categories are populated by default Revit categories, so you can always choose the ones that you would need to. [INAUDIBLE]

We quickly verify if we have all the details on ACC. It looks like we've got our fire hydrant load and the catch basin over in the exchange. Now, we go to Civil 3D, and we'll be loading that exchange into the 3D. Again, very standard process. While loading, though, we also have data mapping in place, so all of your Revit categories get mapped to the Civil 3D layers. That's what it's asking right now.

And yeah, so as you see, as it is a subset, the exchange got loaded pretty quickly. Now, I will refer the roads and the fire hydrant to create the pressure network and the storm network, so I'm just creating a lightweight layout of the pressure network connecting from the fire hydrant, going through the roads.

So this can be-- this workflow can be extended to coordination workflows, as I said. And if you have just the schematic drawings, you can always use those schematic drawings to share these kind of layouts. Right now, we will be creating a storm line, similarly with the different gradient.

Now, we have our sample set ready in Civil 3D, and if the civil engineer wants to share the same data back with the architect who shared the roads and the site information, he can do so creating a new exchange altogether. And in this case, we are using Revit and Civil 3D, but this exchanges can be used by different applications as well.

So you do not have to create different export types or different file formats every time you share exchanges with different stakeholders. Same exchange will work with Tekla. Same exchange will work with AutoCAD, and vice versa.

So we're loading the latest exchange from our civil engineer or designer into Revit now. This is the exchange. We'll load it back into Revit, and the exchange is placed in Revit. As you can see the exchange aligns perfectly with your model, and that being a problem in a lot of site coordination process. [INAUDIBLE] Data Exchange is taps onto that issue for a lot of coordinators or BIM designers.

So what we're doing here is we are changing the position of fire hydrant slightly to check how the deltas come around and how the coordination process would look like. You can relate this to your issues resolution or clash detection or crash resolution process, where you have a small conflict between your different elements, and the architect needs to share that detail or the updated elements with the designer.

So we updated the position of the fire hydrant, and we'll be changing the layout of the pipes accordingly. And when you change the layout of the pipes along with the geometry, the properties are also updated on the Revit's end. So say, for example, you are doing any quantity takeoffs or any annotation workflows on Revit. Those will also get updated.

Yep. All right, so we have updated the pipe layouts, and now when I'm sharing the exchange back with the architect, I just need to update my exchanges. So that keeps the entire exchange process in sync, and you can work with multiple collaborators or stakeholders just with two exchanges.

All right, so this is how-- these are very simple workflows that we demonstrated right now, but you can try out more complex workflows as Philippe just mentioned, and you can use, again, multiple connectors in a chain to support your workflows. We are using two connectors at this point. As we demoed, you can use Dynamo, Grasshopper, Rhino to enhance your workflows and support your complex use cases.

How you can get started with our connectors, we have a list of learning resources that you can follow. First off, we have all of our connectors on Autodesk App Store, so you can got to Autodesk App Store right now and get the hands on our connectors. Feel free to join our beta program that will enable or give you the access to our latest and greatest connectors, as well as the latest features that we are enabling for our data exchanges.

You can learn more about our data exchanges on our Data Exchange home page. That also includes our latest webinars, our public roadmap, and all the blog posts that we share for the latest news on our connectors and data exchanges in general. For any additional inquiries, feel free to drop a comment on our community forum, and also, feel free to reach out to us on our Data Exchange email address.

Now, let's have a look at what is coming up next for data exchanges and what do we have today. So here's a quick roadmap for our data exchanges. Today, we have a couple of connectors in ACC industry as well as manufacturing industry. As you can see, we have connectors for Revit, Civil 3D, Rhino, Grasshopper, and Inventor Tekla Dynamo.

We also have business applications like Power Automate, as Philippe has just demonstrated, and we are working towards more workflows and enabling more connectors. For business applications, we are planning for Power BI, which will give you more insights on the data that you're sharing, and you can load data from multiple applications into one platform and visualize the data that is coming in.

You can create business reports, dashboards for your organization and your projects. We will be enabling data exchanges for IFC as well, which will allow the users to create Data Exchange from the IFC file that is shared on ACC, so that way, you don't need an application to access IFC and create exchanges out of it. You can do it right away, leveraging our ACC. Then we have a plan to enable data exchanges on Navisworks, SketchUp, SolidWorks, and open [INAUDIBLE] as well.

One of the major announcements is also BIM 360. As we know, a lot of your projects are still on BIM 360, and you would like to try out data exchanges there as well. So we will be enabling data exchanges on Bim 360 very soon. On a related note, we are having a target to tackle media and entertainment applications, like the Maya 3ds Max and Unreal Engine. So on top of that, we'll also be expanding on a few manufacturing applications, and that will be updated on our public roadmap very soon.

So this is the applications that we're tackling. On top of that, there are some capabilities that we are adding to our data exchanges, so you can do more with your data, and you can have better control over the exchanges that you're sharing. Right now, we support primitive and solid geometry that mostly enables reference workflows-- that mostly enables primitive workflows. But later, we will be enabling more type of geometries, which will enable native translation for you.

Currently, we have color support, which is basic, so which will enable you to identify your elements. But later, we also plan on supporting materials and finishes, which will help you with your MNE workflows, where you want accurate finishes and accurate render styles.

One of the important things for our 2D and 3D workflows is annotations, so today, we have limited support. So we do not have the support for annotations, but later we will be having support for annotations. So when you create an exchange with annotations or dimensions, you can directly pull that into your drawing review or drawing creation process.

We are also working, in the future, for features that are designed compare, which will enable you to compare designs between different designs and different versions of design, so you can share the comments or you can share the feedback on different versions and submittals of your design. One more exciting thing is the Data Exchange template, so we are working towards a template, which will help you create a standard process of creating data exchanges. So if you are working on a complex group or a larger group, you can create a template for Data Exchange that can be shared between your organization, and that keeps the Data Exchange as a standard process or a comprehensive process.

So this is our roadmap. We also have a public roadmap, which we'll see now. So here, we have a public roadmap, which is also available on our cover page for data exchanges. So the public roadmap contains what we have today, what is in progress, and what is under consideration for the future releases. So most of this public roadmap is influenced by your comments. So as you can see, we have some great comments and feedback so far from our customers and our users, and these comments influence our next moves. And we would like to hear from you regarding what kind of workflows you want to support and how we can enhance your collaboration between teams using the interoperability tools that we build. And we can expand on top of what we have today.

All right, that brings us to the end of our session. Thank you for your feedback so far, and thanks for your time. Hope you have a great AU.