Data Exchange Customer Spotlight: Interoperability in Action

TOBIAS HATHORN: Right. Thank you for joining us today for this session. We'll start off with the Safe Harbor Statement. We will be making forward-looking statements and be looking at roadmaps. So please do not make any purchasing decisions based on what you see today. And also, this content is proprietary, so please do not copy or redistribute without permission.

This session is called Data Exchange Customer Spotlight, Interoperability in Action. So I hope this is the class that you intended to attend. And I hope that this will be fun for you.

A little about myself, your host for the session, I'm a product manager and responsible for data interoperability at Autodesk. I've worked here for 18 years. And before that, I was an architect for five years, worked on a one-million square-foot architecture project in Revit and then joined the Revit team, working in different roles, from QA to user experience design, product owner, and eventually product management.

Now I work in the Autodesk Platform Services group, where we're working on the Data Exchange capability, which opens up Autodesk to a variety of external as well as internal apps for interop. Looking forward to sharing that with you today.

Our agenda follows our learning objectives. We'll go through Autodesk's Data Strategy and introduce you to Data Exchange and how that fits into the strategy. We'll also then spend most of the time in Customer Spotlights and Key Workflows. That's why we're here today and very excited to share those.

At the end we'll get into the roadmap and also make some announcements. So please stay tuned. Those are going to be interesting and exciting to share as well.

So let's kick off with the Autodesk data strategy, focused especially on the concepts of granularity and interoperability. So the average AEC firm quadrupled their data storage from 2017 to 2020.

And likely due to the complexity of the work that you all do, you need to store more than double the data of other industries. And it's not surprising that the amount of data is so large given all the different types of data that we have to deal with. So you can clearly see that in this chart-- environmental data, costing data, performance data, sustainability data, et cetera.

And unfortunately, all of that data might not actually be helping yet as much as you would like. There's still quite a bit of cost associated with rework due to bad data. And quite a bit of data is still going unused in construction. And owners still want more data than what's being provided today.

So there are some key themes we're hearing around the impact that today's data reality is having on your business. Basically, bad decisions are being made due to outdated or unavailable data. And the rework that occurs at each handoff in the building lifecycle, caused by a lack of interoperability, is a headache. And the underlying lack of trust in data-- we simply don't trust that we're seeing accurate, up-to-date, or transparent data.

So why are we struggling with all of these challenges for so long? Why haven't they been solved yet?

These challenges are symptoms of technical gaps in our industry, all of which we're working to address head on, so a lack of accessibility to granular data due to the data being trapped in files, proprietary file formats, especially. There's poor data connectivity between all the different tools in our ecosystem due to a variety of factors, including contractual models, as well as bulky file-based hand-offs caused by a lack of granular data.

And finally, there's just low quality data due to inability to set and enforce a data structure or standard as we're creating our work. Garbage in equals garbage out.

So by taking a closer look at these root causes, let's take a moment to define what we mean by granular data. We're referring to the underlying data that makes up a file or a model, which is today largely inaccessible, or at best difficult to access.

So for example, a project is comprised of thousands of models and files. And those models and files are made up of hundreds or thousands or tens of thousands of individual pieces of data. And so we've introduced the term "granular data" to refer to all of those individual elements, or bits of data, inside of files.

And historically, we focused on putting all of that data into files, essentially building the model, rather than focusing on the elements and the data that make it up. And in this existing paradigm, all the data we spend so much time putting into the model is largely inaccessible. So only technical users, data wranglers, are able to access the data within the design authoring software. And even then, it's largely a manual process of updating, analyzing, and aggregating all this data together.

These files are typically massive. And then to share that data, you have to rely on some pretty clunky workflows. Every time a change is made, you have to save or sync or publish the file. And that takes time. And it means that we're all working off of our own disconnected reality.

And since the underlying data is inaccessible, when it comes to sharing, we've had to rely on some pretty clunky methods. Typically, the data exchange follows an export workflow, meaning as soon as the data is shared, it's disconnected and it's outdated. Rather than working off of one central source of truth, when it comes to granular data we're not able to accommodate a flow of data across tools, people, and processes. We actually have hundreds of versions the source of truth, and it's not good enough. Basically, a scheduled IFC export is simply not good enough.

Connectivity is a big challenge for many reasons. We've been protective of our data over time, largely due to risks, contractual concerns. Most of our technology solutions as an industry have been closed and proprietary. And as an industry we've been cloud resistant, either due to job site, spotty internet, or even IP concerns.

So since everything's been disconnected, we're making decisions based on bad information. The data we need is trapped in the model, making collaboration impossible and rendering all of the data's potential value and insights hard to achieve.

All of the deliverables on the right are just different views of data. But today, they're difficult to produce and nearly impossible to keep updated. This is costing billions of dollars of rework annually.

So Autodesk is embracing granular data, first in power formula and the next generation of design workflows. And to do that, we're building the AEC data model to provide granular data. And we're building data exchanges to connect the diverse ecosystem of apps that you use.

These are both built on Autodesk Platform Services, our common set of cloud-based services that support all of our industry clouds, including Fusion for manufacturing and Flow for media and entertainment. And what we need is a fundamental mindset shift for both Autodesk and the industry.

And it's not about the model anymore. It's about the underlying data that makes up the model. That underlying data, that granular data, as well as the schemas that structure it need to become more accessible in the cloud, outside of the design authoring environment and all of its mega file glory. By breaking up files into valuable bits of data, granular data that's stored and managed on the cloud, we can start to address the underlying issues that make it so difficult to work together today.

Once the data is granular, then bulky file import-export processes are eliminated, as users can now tap into only the bits of data, the subsets of data that they need, instead of moving entire files around. One seemingly small change, like the width parameter of a door, can have massive impacts on the cost and the budget of a project. So with accessible granular data, that change gets shared out much faster than it does today.

And with granular data, we can start to map schemas across disparate formats. We're finally able to translate data between different systems and reduce the complexity of trying to work together in different tools. The representation of a pipe in Revit can finally be recognized as a pipe in Plant 3D or MicroStation. This enables true interoperability so that data can flow seamlessly and accurately across different tools.

And once the data and its structure is accessible and connected at a granular level, we can easily isolate just the data we care about, whether it's the 3D views necessary for a Data Exchange, or a total carbon report for environmental audits. These are all just different representations of granular data. And so different views of the data become easy to generate by any project team member, allowing better decisions to be made quickly.

So as Autodesk starts to deliver on the promise of granular data, we are starting to build out the foundation of data models, first to unlock the data that's normally trapped within files so that customers can access and make use of their data in order to deliver on business outcomes. But that's only the first step. As more and more Autodesk flagship products start to embrace this cloud, this will bolster our industry clouds, like Fusion, Forma, and Flow, by expanding them with net new customer experiences that delight our customers.

And with these new experiences, we can start disrupting industries through value differentiating customer outcomes that fuel digital transformations. And all along this path will be releasing things iteratively so that customers recognize and realize value as we go. And you'll see granular data start to power Autodesk and third-party apps, too. Imagine the Autodesk data platform as a utility grid that connects data from design apps, like Revit, Civil 3D, AutoCAD, Inventor, into third party apps like Rhino, Tekla, and SolidWorks, and even into Microsoft's Office suite.

And this is where we're going to start talking about Data Exchange. It's intended to help move your design data across boundaries securely between apps and between organizations. First, let's talk about the application boundary, as we are demonstrating that Autodesk is an open ecosystem by acknowledging that Autodesk tools are not the only ones required to get your work done. You can already see that we've built connectors for Rhino, Tekla SolidWorks, and for Power BI, meaning that you can pull data in or send data out of the Autodesk ecosystem.

Second, let's talk about organizational boundaries. Data exchanges provide gated access to only a subset of your designs without requiring access to your source files. In the past, the smallest unit of collaboration was the file. But now you can collaborate on a single element if you want or a handful of elements, filtered by category or level or phase or by discipline. You don't have to send your entire Revit file to other project team members anymore.

So let's see a typical Data Exchange workflow in action. This one acts on a published Revit model that includes a published 3D view. It's easier than ever to load just what you need into Inventor.

So in this video, we can see a Revit file. And we've isolated down just a part of that model using the section box. Now that view is included in a published set and published to Autodesk Docs. Once you get to Docs in the viewer, you're able to navigate to the different 3D views that have been published in that set.

And from those published 3D views, you can create a Data Exchange that will include only the things that are included in that view. So when you load this Data Exchange into Inventor, that's all you get, not anything more than what you intend or need.

So with this workflow, an Inventor component like a railing can be added and manipulated. And then as the Revit model changes and gets updated on a publish, then the Data Exchange can be automatically updated. And when it's reloaded in Inventor, it can snap and maintain the relationships that exist between those Inventor components.

We call this a typical reference workflow because you're not tweaking any of the geometry coming from Revit. You're using it as a reference to work with your Inventor model.

So let's see another typical workflow. This one is slightly different in that it's using a different mode of working using the connectors that have been built. And this is a work packaging workflow. So persona A working at Acme, Luna, she's reached a milestone in her design workflow. And so she's going to set up her view to contain only the elements she needs. And again, she's done this with Section Box, with turning categories on and off, View Properties, and View Templates.

Now, using this Revit connector, which is a plug-in into the Revit app, she's able to choose which folder in Autodesk Docs she wants to put the Data Exchange. And that's valuable because she can keep the Revit file separated from the Data Exchange and only share the Data Exchange with the people who have permission to see that folder in Autodesk Docs.

So in Docs, now there's a Data Exchange, and she can see a preview of it before she shares it with her collaborator, who works at Globex, a different company. And they use Rhino instead of Revit. And he's going to do a canopy design over this courtyard that she shared with him.

So he's able to access the shared folder, get a preview of the Data Exchange before he loads it, and then even choose just the parameter groups that he wants to load into the model. And as soon as he's done, voila. He has a pretty rich set of geometry to use as context for the canopy that he needs to add.

This is added using Grasshopper or Rhino tools. And he's able to create a Data Exchange to send back over to Luna. And here is the Rhino geometry now showing up in Autodesk Docs. And here's Luna loading the Data Exchange into her design. So now she has a reference model coming from the authoring tool Rhino. Now they can coordinate their two models to make sure that the structure, which supports the pylons, which supports the courtyard, is in place.

These same data sets can be loaded into other systems like Inventor, and they can also be loaded into Power BI. This is the rich Revit data coming from Revit. So it has all of the parameters, The I in BIM. And you also have this nice viewer, so you can put together a wonderful dashboard in order to show stakeholders, as well as your team, what you're working with. But you can also load the Data Exchange coming from Rhino so that all of the attributes on those panels can be utilized outside of the Rhino context tool.

All right, so that's a couple of typical workflows with the Data Exchange. And I want to highlight how these are different from what you might typically be doing with Import, Export, and linking workflows.

Primarily, data exchanges are granular data, so you can work with subsets of your model instead of the entire file. Data Exchanges can be separated from their source file to protect IP but can also be updated easily, so they provide durable value throughout the project life cycle. And lastly, Data Exchanges are built on the Autodesk platform as an API first service, so any customizations required can be done by the community, not just Autodesk.

You may have noticed that the Data Exchanges are all hosted in Autodesk Construction Cloud. And that's key, because all of this data starts in the cloud and ends in the cloud, meaning that you never have to manage files like you would have to today.

All right, so let's get into some customer stories. These are early adopters that are starting to embrace Exchanges as a new way of working. And the first workflows that we'll look at are these having to do with Data Dashboards.

This means that customers are interested in visualizing their design data in Power BI. They're trying to minimize the friction in extracting data from files, so anybody can work with the data. And customers are trying to add a 3D viewer component for maximum impact when reviewing this data.

Obviously, they'll want to share and update this data frequently. And they'll want to determine progress on their projects in order to mitigate risk.

So this first example came after Autodesk University last year. Brent Mauti from Turner Fletcher was very keen on picking up the Data Exchange Power BI connector and starting to experiment with it as soon as AU ended. So we worked together on this first dashboard that was created, just a simple space allocation diagram where he sliced his Revit model by just one floor and included just furniture categories and walls so that he can start to do a department assessment, how many desks are on this floor were associated with which department. Pretty straightforward, but incredibly easy to do and visualize in Power BI.

So he had a pretty good experience and was happy to share his feedback that the whole thing, the setup from Revit to Power BI, was just amazing. And I liked that he got it right away, the ability to control how much data is in the packet. It was really exciting for him and very easy to use.

I want to share another example. This one is from CRB. They're using Power BI to compare the model quantities and estimate quantities on their construction projects. Note that these gray bars are estimated, i.e., budgeted quantities. And the blue bars are modeled, or remaining quantities. And this gives CRB an overall percent complete. And it also gives visibility into the progress they're making by system.

They are also merging two different data sources together, basically Exchange data, which comes from the model, and data coming from the Assets module. And you can see that in the table below. CRB can see asset properties like ID and schedule.

And they can also see the data coming from the Assets module. So they can see the schedule and the field status and whether the asset is even installed yet. This allows a user to drill down to individual assets.

So there's quite a bit of power in being able to select from the viewer itself and then get a sense of what is going on with that particular element. You can see the status and how much it contributes to the overall percent complete on the project.

And this has been great to work with CRB. They shared this quote with us, "With the Data Exchange for Power BI, they've unlocked the ability to analyze 3D element data like never before. By automating the publishes, model-based progress tracking and 4D visualization workflows are saving their project teams multiple hours every single week." So that really adds up quickly and makes their company more efficient.

So this is another example, more recent. We were contacted by Rodgers Builders about when our Power BI connector would be certified by Microsoft. It was just released to general availability, so it's no longer in beta, but it's not yet certified by Microsoft. At the end of the presentation, I'll let you know how you can help with that.

Basically, we followed up with Rodgers and asked what was their use case and what are they really trying to get done. And we were really impressed, so I wanted to share their story.

They're monitoring steel installation. First they break the steel into sequences and then plot those sequences out over a schedule. And that's what you can see in the upper left. Then, given the reported progress on installation, they can estimate and even try to predict when the steel installation will finish so that the other trades can start their work. And this all boils down to communicating insights with their subcontractors.

So we worked with them in getting this quote, which sums up the value of using Data Exchange. "Our teams want to see updates every day. Since we know that steel is installed and what's remaining, our dashboard is a communication tool to push subcontractors. Because if steel is late, it's going to be impossible for the rest of the project to stay on schedule."

All right, those are some cool Power BI examples, and we even have some more that you'll see in a moment. But I want to talk about a different key workflow that Data Exchanges are unlocking for people, basically being able to do better design coordination and delivery than they have in the past.

So we see people linking their model elements from Revit, Tekla, Civil 3D and Navis all together and then sharing the key model geometry as a reference with each other. This helps to maintain key properties for documentation and coordinate models during design and pre-con phases. Basically, companies are able to share data and not files for security and IP protection.

So this first example is a wonderful one from the Ramboll company. And they're working between Tekla, Revit, Tekla and Revit especially. So let's kick off the video.

Here you can see them starting in Tekla. And traditionally they've used IFC for this type of workflow. They're able to choose where in Autodesk Docs they want to put this particular section of the building and the properties associated with it. So they extract from Tekla and then bring it into Revit for doing the documentation work that they've always done in Revit because it's the best tool on the market for it.

So they load in the steelwork coming from Tekla, and they're able to adjust where it is in space so that it can be aligned and coordinated. And the best thing is that the properties come along with the geometry. So they're able to set up filters using Revit's filtering capabilities, but filtering on the properties that are coming from Tekla.

So everything can be colored, even though it's imported geometry. And even beyond that, you can start to create schedules from the information coming from Tekla as well. So all of these properties that are being added into the schedule can be a mix of Revit properties, as well as Tekla properties, giving you the best of both worlds for the workflow that's at hand, in this case using documentation of the model.

And they had a great quote to share with us as well. They believe in being flexible, and they need reliable access to updated design data. It's the key to efficient project delivery. I love the call-out for efficiency.

"Structural designers enjoy spending as much time as possible in their preferred design software"-- in this case, Tekla-- "and they want to spend as little time as possible importing and exporting data. The Data Exchanges help us to combine the cross-discipline BIM collaboration features of Revit and the detailing fabrication features of Tekla, all the while organizing and tracking the design process on Autodesk Construction Cloud."

So that's an awesome testament to how Data Exchange is being used to improve Ramboll's business. I want to diverge a little bit beyond Revit workflows and also show this Civil 3D workflow. Eventually this will go into Power BI and show you some cool things in Power BI as well.

So here we see a bridge that's been modeled in Revit, and just a subset of that bridge model is actually being sent over to Autodesk Simple 3D tool. Basically, the view is being set up, curated to only include the things that are necessary. And then the Data Exchange is put in Autodesk Docs.

This time there's a Power Automate connection being used so that when that exchange shows up or when it's updated, the team can be notified with a Microsoft Teams notification. This is revolutionary to the way people are collaborating instead of having to send an email.

So now in Civil 3D, you can see the model comes in and even the rich properties of the Revit model have come along with it. Additional work is done in Civil 3D, like the different systems being added. Basically, corridor solids and pipe network solids, even terrain solids are added and then exported via Data Exchange. And these can now be brought into Power BI with their attributes. So you can create rich workflows and dashboards around Civil 3D data, not just Revit data.

One thing I really like about this demo is how quickly navigation is possible using the data widgets, not necessarily the 3D modeling widgets. So the customer is now able to perform property set health checks, as well as quantification in Power BI, and even construction sequencing can start to happen in Power BI.

So a lot of different materials workflows, as well as just counting workflows, are set up and much easier to do in Power BI than they might be to do in Civil 3D. This allows more stakeholders to have input and project team members to see status as things move along in the project.

OK, now I want to touch on something that's a little bit exciting. And these are the custom workflows that are enabled by using Data Exchange. You can go beyond the classic or basic "create, load, and update" workflows. These are basically the out-of-the-box things that our connectors allow.

You can start to create your own mappings. You can start to create your own connectors even. And you can exchange special geometry, not just the solid geometry that's set up automatically. This allows you to define and automate your firm's bespoke workflows.

So let's take a look at a few examples. This first one is manufacturing to BIM, so helping a customer set up a workflow between Inventor and Revit using Dynamo as a custom mapping layer in that workflow.

So let's take a look at this video. Here you'll see a fairly complex Inventor model that's all the elements on a factory floor. And these are helpful to see in Revit. And when you load those into Revit, you'll end up getting everything onto the same layer by default, the generic category. And you can see a View filter here is set up to color everything on the generic category as red.

And that's not exactly what's intended. So in this case, the customer was able to use Dynamo and load a Data Exchange into Dynamo in order to condition that model before it goes into Revit. They used an Excel spreadsheet to help map from an Inventor part into the specific Revit family category and then also use Dynamo to map parameters and their values onto those specific families.

So now, when loaded into Revit, you can see much more color because the View filters are set up for each category to be displayed correctly. And you can see parameters have been added correctly on to the correct families and into the correct categories.

So this is much more along the lines of what the customer intends to have happen. Not everybody is a great Dynamo user, but with Data Exchange, you can start to do more custom things in Dynamo.

Even beyond Dynamo, if you have an IT department or work with a developer, you can even start to build out your own custom connectors. So this is an example of what's possible with the Data Exchange SDK in order to build a connector, in this case for Bentley, Open Roads, and start to import and export geometry with Open Roads.

Let's watch this video and see. So this is an example of a developer environment where a customer has been able to build up a specific Autodesk Data Exchange connector and even start to build up their own custom types of data that they want to exchange.

You'll see some information here about the different types of the system that are interesting to this person and the ways that they've got those data types set up to work. All of these need to be defined ahead of time, but they're all also custom to this firm and the workflows that they need to execute.

So in this case, they're exchanging an alignment curve from Open Roads and interested in sending this to Dynamo and into Revit and into Civil 3D. And all that is awesome to see, because the way Data Exchange is set up today, you may be able to send this geometry, but this way they're able to send it exactly the way they want to so that it maps into their downstream workflows the way that they intend. They're using the Data Exchange connector system and Autodesk Docs as the storage for this data.

There's very exciting things in the future for where this is going. But I wanted to just share at least a little bit of a preview of what they're capable of doing today.

All right, so now we've seen some examples of what customers are able to do with the Data Exchange system today. And now we'll talk a little bit about what kind of announcements and where our roadmap is heading so that we can do even more with data exchanges in the future.

So here's a snapshot of the goals that the Data Exchange team is aiming towards in the next year. We're really interested in bringing production utility to customers, helping to see adoption on production use cases. So we're very keen to highlight even more customer success stories next year. And we're providing learning content like videos in order to help promote even more production use.

We'll be bringing more and more connectors to general availability, graduating these connectors from beta to GA. We've already brought the Power BI connector from beta to GA and seeing pretty fast adoption of that connector. In the near future, you'll see additional connectors going to GA, while others of our connectors will remain in beta for longer.

We're also super keen on workflow versatility, being able to have seamless experiences with deeper integrations, automations, and customizations. So these will come through our SDK and GraphQL capabilities.

This is a snapshot of our public roadmap. I put a QR code in the corner, so you can scan this and visit our public roadmap for yourself. This is on the Released tab, so you can see all of the key features and connectors that we've released in the last few years. This is a great way for you to have transparency into what we're working on next and comments about what's interesting to you. You can also use that blue plus arrow in the lower left-hand corner in order to submit your own ideas for things that we should be pursuing.

I want to touch on the Power BI GA one more time. If you go to the Autodesk App Store now, you can download and start using this on your production projects. When you tie this in with the Publish method of creating a Revit 3D view and then publishing to Autodesk Docs and automatically updating a Data Exchange every time that Revit file is published, you'll have a very powerful workflow going from Revit to Data Exchange to Power BI.

And in order for our connector to get certified by Microsoft, we need your support. Microsoft is keen to do this, but they don't update and provide certification for every connector. So we have an idea board on Microsoft system, which is connected to this QR code. So if you can scan and use this, you'll have a chance to comment and vote for this connector to become certified.

And you can see these couple of quotes that came off of that board. And they really warmed my heart. Makes me very happy that we're providing tools that are making our customers more efficient.

So I want to touch on a couple of the other items that you may have seen on that roadmap that we've just completed and/or we are working on right now. This is an amazing integration with ACC Bridge. And not everybody is familiar with Bridge, so I'll describe it. But we'll also watch a video of how this system works.

Basically Bridge is another way for you to separate your hub, your company's data, from other companies. data. In Autodesk Docs, you don't have to invite other companies into your hub anymore. Instead, you can bridge a folder full of data between two different hubs. And Data Exchanges can now be inside those folders and bridge between two different hubs.

So you don't have To include your source Revit files in a folder that gets bridged over to another hub. Instead, you can provide just a Data Exchange in a folder that gets bridged to another hub. This gives you even more IP protection than you've ever had before.

So let's watch a short video of this tool in action. When you go through the shared dialogue in Autodesk Docs, you have the ability to automatically sync updates to a target project by using Bridge. This is all set up as part of the Bridge workflow. And it just so happens that Data Exchanges are included in that bridged workflow.

So now these two folders, belonging to two different hubs, are in sync with each other. So when a new Data Exchange is added to that same folder, you'll see it also show up in the second hub. This automation, which adds content automatically, is part of the Bridge system.

Now, as the Data Exchange is updated, like when a Revit file is republished to version 2, the Data Exchanges associated with that Revit file are also updated to version 2. And the downstream Data Exchanges in the bridged folder are also updated to version 2. So this allows you to keep multiple stakeholders from multiple companies all in sync with each other as your project goes on without needing to provide source access to your Revit files.

The second new feature that I want to talk about is importing IFC files into a Data Exchange. IFC is a very powerful interoperability standard in the AEC industry. And we don't see IFC going anywhere anytime soon. So what we've tried to set up is a way to bring your IFC files into Data Exchanges so that they can go into Revit or into Power BI, similar to some of the workflows we've seen today.

So let's watch this short demo video of how powerful it is to bring IFCs into the Data Exchange ecosystem. Since IFC doesn't have its own native file application type, IFC files are converted to Data Exchanges in Autodesk Docs. So when you open an IFC file in Docs, you're able to click the Create Exchange button and put that Data Exchange in a separate file or in a separate folder. Then you can even separate your IFC file from the downstream Data Exchanges.

Here's a preview of just the data that you've put into the IFC, and you can see the preview and the data structure is intact. Now that same data can go into Revit. And you can also bring that data over into Power BI. So now your existing IFC workflows are still able to participate in these new, rich, granular data workflows-- pretty cool.

The last announcement that I want to make is very exciting and is more of a platform demonstration of Autodesk Platform Services. In order to demonstrate that we're an open ecosystem, Data Exchanges have partnered with BIMDeX to enrich the connector ecosystem that's available. So far, we only have a preliminary proof of concept to show, but you'll see more and more exciting and very innovative ways of working between BIMDeX and Data Exchanges.

Let me show you a quick video of our initial proof of concept. This is going to show the BIMDeX connector for Plant 3D, extracting geometry and properties. You can see the Plant 3D element and all of the attributes that it stores on all of the varied types of pipes and components.

Now, this is using the BIMDeX technology to extract this rich data and using the Data Exchange technology to store this rich data in Autodesk Docs. So now when visiting Autodesk Docs, you can see this assembly that came from Plant 3D is visible in the Autodesk Docs folder.

And now in Revit, you can use the Data Exchange connector and load this geometry into Revit. Now this is the BIMDeX connector, which loads it in. So it's a different technology and incredibly rich about bringing all of the metadata you see in the Properties panel. This is just the first example, and we hope to show many more, maybe even by the time we get to AU.

I'll show a quick highlight of what we intend to achieve with this partnership. Autodesk is excited to announce a groundbreaking partnership with gold partner SrinSoft, Inc. By integrating BIMDeX's advanced interoperability capabilities and Autodesk Data Exchange and Autodesk Construction Cloud using the Autodesk Platform Services, this partnership aims to offer a comprehensive solution that meets the industry's growing demand for cloud-based, data-driven workflows that improve import and export capabilities while organizing and tracking the design process on ACC. So thank you, SrinSoft and the BIMDeX Group for this awesome partnership.

This is the last slide of my presentation, so I just want to show you a few resources on where to go about learning more about Autodesk Data Exchange. First of all, there's a landing page on the Autodesk Platform Services page. So if you just search for Data Exchange, you'll probably end up here. We're showing up in the top five results on Google these days.

Now in the upper right, you can see several learning modules that show up in the Autodesk Learn page. These will cover a lot of the same material that I covered today but in more depth so that you can follow along with Getting Started tutorials. This will walk you through the new Navisworks connector, as well as the Autodesk Docs workflow, the Revit connector workflow, and the Power BI workflow.

In the lower right is our Data Exchange support page, also known as the Community Forum, where you're able to go post questions and get answers, usually see from the product team directly, but sometimes from other of the early adopters of the Data Exchange system.

So thank you very much for coming. I'm sorry I can't answer any questions for those of you that are watching this recording, but I hope you enjoyed the presentation. Thank you.