AU Class
AU Class
class - AU

Get More Out of Your Connected Vault Professional

Diesen Kurs teilen

Beschreibung

This class will showcase the interoperability and advantages of having Vault software at the center of all your designs and documentation.

Wichtige Erkenntnisse

  • Learn about using Vault Mobile while on the go.
  • Learn about implementing Vault Gateway for the hybrid workforce.
  • Learn how to use Project Sync to connect Vault to Autodesk cloud services.
  • Learn about Shared Views for collaboration.

Referent

Video Player is loading.
Current Time 0:00
Duration 0:00
Loaded: 0%
Stream Type LIVE
Remaining Time 0:00
 
1x
  • Chapters
  • descriptions off, selected
  • subtitles off, selected
      Transcript

      MIKE THOMAS: Hello, and thank you for taking a look at this class. This is getting more out of your connected Vault Professional. My name is Mike Thomas. I'm the Technical Services Manager for Prairie Machine and Rokion, which is a mining machine, equipment manufacturer, and electric vehicle manufacturer.

      So why are we here today is we're here to connect our data. So cooperation is people working together in support of a common goal. But collaboration is when these same people work together to accomplish the same goal at the same time.

      So things haven't really changed. It's just things have been extremely ramped up in the past couple of years. Our customers want information yesterday because they thrive to be part of the process, and they want to make informed decisions. Our vendors need details ASAP. Because of the long turnarounds on these, they got to make sure they have the details so they can deliver the right products in a timely fashion.

      We no longer work in silos because we have multiple offices with multiple disciplines, and subcontractors, and vendors, and customers, and everyone trying to get a piece of that same data. And on top of this, many continue to work from home, and that brings its own obstacles. So ultimately, is we want that single source of truth. This ensures that we operate on consistent and relevant data.

      We want all stakeholders to actually be using the same data to make decisions, not a copy, of a copy, of a backup of something that was emailed three weeks ago. We want them to be working off live and relative data. So the single source of truth is the aggregation of data into a single location.

      So why would we not want to apply this to our engineering and CAD infrastructure? And what is that? That's Vault. Vault is that single source of truth where all our information can go.

      So let's talk about some of the tools at our disposal when we're using Vault, and specifically, we're using Vault Professional. So the first one to look at is Shared Views. And as you can see here, this is powered by the Autodesk Viewer, which is based on Forge. And you might have heard of Forge, but this is Autodesk Cloud Development Platform API.

      So Shared Views lets you collaborate online on design visualizations. Now this isn't just a Vault thing. Inventor can publish Shared Views. Revit can publish Shared Views. In fact, you can even just go to the Autodesk Viewer and just upload models on your own. There's just some nice-to-have things when it comes from Vault, and we'll get to that.

      Now it is just a 2D or 3D visualization. There's no models to download or even possible to download. So you can push your models up there and not have to worry about the person on the other end getting a hold of your drawings or your 3D models because you're just working off that visualization.

      We can use Shared Views to put something in front of the customer, maybe in front of other key stakeholders to get their approval, or a way to provide details to someone who's on site. Maybe they're commissioning the product and we need them to have this access. And what we want as our quality process is we want some feedback on how it's going.

      So anyone can view and comment on these Shared Views just using a link. So you create these Shared Views and you send the link. So anyone with that link and an Autodesk ID can access these Shared Views.

      And you can comment through comments. And it's not just text comments, you can actually do some other things with them. And I've already mentioned this is a Vault Pro thing. So Vault Pro has the Shared View functionality.

      So for the administrators out there, this is fairly easy. One is they have to have the item assigned to them in their Autodesk account. And it's by default, but you can manage who can share views globally through their license, essentially, through their Autodesk ID. But then globally for the entire Vault is you can enable or disable Shared Views.

      So if the decision is, you know what? We're not sharing views. Then you can just disable that. And that's right across the Vault. It's just not an option that's available. From an administration standpoint, that's it. There's nothing else to do with this. It's on or off, and that's it.

      Now sharing these, or creating these Shared Views is pretty easy. It's just a right click, and you pick Share. And notice that from an options wise, there's not that much. But I can enable that I want to hide component names or hide part properties. So I want them to see the model, but I don't necessarily want them to have all the metadata that goes with it.

      What happens then is it generates the link, so it takes care of pushing that up. And it generates the link which I can copy right from that Publish option. Now if you miss it from there, that's OK. There's another place to get that.

      But that's the process. It's a right-click, Publish. You give it a name. There's two options to choose from, and you Share. And then, Vault takes care of pushing that up into Forge, essentially, into that Autodesk Viewer.

      Now this is Vault 2024. This was also available in Vault 2023, and 2022, and maybe even older. But just if you're not on 2024, this is still an option for you. OK, so now once it's in the cloud, once it's in this viewer, the person who's viewing it can do the Pan, Zoom, Orbit, like we expect. You can turn parts off and on.

      Notice that you can explode, so you can essentially blow up the models really super quick and easy. You can also create sections. And what's kind of funny about this is these sections are probably easier to create here than it is in the CAD application, like Revit or Inventor. So you can create these, and then you can actually do measurements. Now I'm doing a measurement in a Section View here, but you can do measurements at any time. And notice that it's the measurement plus the components.

      Now something else I can do is I can capture snippets. So I can essentially generate an image, in this case, it'll capture the section and that measurement. And then I can mark it up. So notice that there's some real basic markup tools. I can do clouds. I can do text. I can do arrows. I can even do a pencil if I want to freehand draw this thing. But the idea is that I can mark up on this still image. So I position the model where I can see it the best, and then I create that markup, that snippet, and notice that it captures it for me.

      Now I can have multiple markups, whether I actually mark up in them or not. Sometimes you might just take an image of it, and then maybe what we want to do is we want to add some comments. So what I can do is write into this comment box here is I can add the comments.

      Now what's cool about these snippets is it remembers component visibility. It remembers the Section Views were enabled. So to return to it, it's exactly as it was when you created that snippet.

      So here I'm just going back to the model. I'm just restoring it to back to where it was. Now notice here that I turned on the Model Browser. Now remember that I turned off the Hide Component Names, so that's why I'm seeing all the component names here.

      So I can actually see that there's a bearing housing and there's some spring spacers. And when I click on it, I can actually get properties from that. So whatever metadata-- now this is an Inventor file-- see, these are iProperties, but I can get descriptions, and areas, and volumes, and stock numbers, part numbers. Again, remember that I turned off that Hide option when I published this. So if you don't want to include that metadata, because maybe there's too much information there, like you don't want to give your customer part numbers or manufacturer details, you can hide those so it's just the model they see.

      So that's the Viewer in action. And remember that the person who's viewing that visualization that, in the Viewer, only needs an Autodesk ID, which is free. They don't need any CAD application. There's no uploading, downloading. They just need a browser and an Autodesk ID is all they need.

      Now those Shared Views from within Vault, and this is the advantage, or the nice to haves within Vault, is that there's history. So you can see when it was created. You can manage it. And then you can actually review the comments and reply to the comments directly from within the Vault client. So you don't have to go through the browser.

      So here's a situation, that same model, I've refreshed it. I can see there's two comments. And notice right within Vault I can see those comments that were added. So it just acts like it's a thumbnail. And if I click on it, then within Vault I get this mini kind of browser which I can click on and I can review. And then I can actually reply to it right from within the Vault client.

      I can also acknowledge them, mark it as Resolved, so essentially say, yeah, we took care of this. Great comment. Glad you caught that. I'm going to mark this as Resolved.

      And like I was mentioning is, right within the Vault client the default is 30 days. I can extend these longer if we need them. If we're done with it, I can delete it. So I can just delete that link and say, hey, we're done with this. Let's delete this.

      It automatically expires after the 30 days so you don't have to worry about it. It'll just expire. And then you can actually launch the browser right from there and copy the link. So although you can do this outside of Vault just with a browser, the nice to haves here is you get some history. So I get a bit of history on, it was shared, and the comments are listed there. I can review them from within Vault. I can reply and comment, again, from Vault without having to leave the Vault environment.

      OK, so Shared Views seem great, but what's there to be aware of? What's the gotchas? What's the catch? Well, there's a couple catches, and one is Shared Views are static. So you publish them, it goes into the cloud, and it's static. So if the model changes, your drawing changes, you'll need to republish those so that the person on the other end can see those changes.

      They are public-ish. You're generating a link, so anyone with that link and an Autodesk ID can view the model. So it's just something to be aware of is that they're not public links. No one can just search for it and stumble upon it. But there's nothing stopping the person on the other end from sharing that link, and it just keeps going. So something to be aware of.

      There's also limited control. It is an on or off. There's really no way to limit it to specific folders, or projects, or files. You can't limit it to a lifecycle state. If it's on, then you can share any file, or any folder, or any location within your vault.

      It's also limited change history. There's really no way of integrating it with change orders. The markups and comments live in the cloud even though you can view them. So just be aware that there's limited change history. Well, that's the gotchas, but where would where would I use these, or where do we use these?

      Well, these are great when you have collaborators who are outside the corporate boundaries and they don't need access to the files, or you know what? You don't want them to have access to the files. They also don't have the software.

      So we're an Inventor shop. We've got a customer who wants to look at it. They don't have Inventor or if you don't want to have access to it, we can use Shared Views. So they're really good for those one-time, infrequent, short-term collaboration, where, hey, Mr. Customer, here's what you're going to be getting. Take a look at it and let me know some feedback before we proceed on it, but not really that ongoing type feedback throughout the whole process. So that's Shared Views, and that's just one tool out of the box on Vault Professional.

      Well, what if we need a little bit more than that? Well, there's Vault Mobile. So this is where you take your Vault with you. So what is it? It's the companion to your Vault. This is not a Vault client replacement. This isn't the thick client replacement.

      What can you do with it? Well, we can search. We can view. We can download. We can share. And I've marked here that it's available for Android and iOS because their very first iteration of this was just on iOS. But the app is now available on Android as well. Key note, the trend throughout this is that Vault Professional is required. A Vault Professional server is required for users to get access to the Vault Mobile.

      So what can I do with this? What's out of the box? What's in the app? Well, you can actually create folders and you can upload files. So if I was a sales guy and I was on site, and a customer had given me some specs or something they needed, I could actually take some pictures of them. I could upload them into Vault, or I could actually take the files, and maybe they were emailed to me, and I could upload those PDFs. So you can see, non-CAD files can actually be uploaded right from the mobile app.

      I can also download files and share links. So shared links you would use internally where it would be like, hey, I need you to look at this. You could share those links. And you can view, as you can see here, Microsoft Office files and PDFs natively. Nothing's really required. You can also view CAD files. That does require the Autodesk Viewer, the same one that Shared Views uses. But in those cases, an internet connection is required to view those.

      I can also add markups because it's using that Autodesk Viewer. So no different than we saw how I marked up with that Revcloud, we can do that. You can contribute to change orders in the act of markups or comments. And you can actually change lifecycles. So someone could actually use the mobile app to review something and then, let's say, approve it, or put it into review. So this Vault Mobile is-- it's a fairly functioning product for those kind of situations, those cases.

      So you want to use it when you need real-time access to your data outside your network. It's where you need searching, viewing, and basic markup is what you want, but you want it on the actual Vault. You don't want someone to have to share it to you. It's just going to be ad hoc as you need to it.

      The catch to Vault Mobile is that it does require some IT overhead on this because it requires a public-facing connection to your Vault server. So essentially, the app needs to be able to hit your Vault server to get access to the data. So that would be the catch to it is if you're not comfortable opening it up to the outside world, then Vault Mobile is not going to be the one for you.

      Well, we've got that Vault Mobile that's really good for when you're leaving the office. What about the same application but within the office, or within the corporate firewalls? Well, this is where the Vault Thin Client, and this, again, is a Vault Professional feature, where using a browser, we can QVP. So we can query, as in search, with the same power and options as the Vault client, so the same SQL-based searches to find our parts, and our drawings, and our designs.

      Query also means that you can see the history. You can see the uses and the where used. You can view change orders. Now unlike the mobile client, you can't participate in the change orders through the Thin Client, but you can view the change orders. You can also download files from it. You can share links, and you can update the visualizations.

      Now Thin Client, if you're not familiar with Thin Client, just means that it uses a browser. There's nothing heavy. There's nothing thick, so the Vault client is a thick client because it requires an installation and an application for your run, whereas the Vault Thin Client all runs through a browser.

      Now the Vault security still applies. You still need a user, but the user doesn't require a license. So this is QVP, requires a Vault account, but doesn't require a license for them to access it. Now from an administration aspect, there is something separate. You have to install the Thin Client onto the server, but then it's just provide the browser link.

      And as an administration you do have some control over what the users can see, namely, do we want them to see released information only? And do we want them to only see the latest version of the file? So what we've done in our facility is, for guys on the shop floor, we only want them to see the released files.

      So if the engineer has taken it to work in progress and is making changes to it, we don't want the people on the floor to see that. We want them to be working off the released information. When the engineers approve and re-release that information, then it immediately becomes accessible for the people in the shop to see that information. So that's how we do it, but it gives you that control from an administrative standpoint.

      So you can see, like I said, is it does require Vault client. I used Windows account because my Vault account's tied to my Windows account. They will log in. And notice that I am looking at files really no different than if I was in Thick Client. So I can see Properties, and History, and Where Used, and all those great kind of things.

      Here, I'm going to search for a file. So you can see, I just put the number in. I can go and get that Inventor part. I can see where that Inventor part is used. I can see what item it's assigned to, is there any change orders on it? So there's really not much difference at this level between the Vault client and the Thin Client.

      Here I'm doing a basic search for a bearing and I found way too much information for bearing. Even if I search for bearing cap, I'm getting way too much. So I'm going to do an Advanced Search, and I'm going to say, well, I really only want bearing caps that are within a date range. So after August of 2021, I want to see the bearing caps that were checked in, and I was able to limit that.

      So let's take a look at that assembly. I can see the components that make up that assembly. And like I said before is I can actually go to the item. We use items at Prairie Machine, so you can see how I was able to go from the file and go right into the item. And I can see, it's bill of materials. And I have control over which columns are visible to me.

      Now here's a case where the visualization wasn't updated. So what I'm going to do is I'm going to add that to the job queue so I can say, hey, I need to view this. I'm going to push this to the job processor. I'll come back to it in a minute because I'm going to wait for it to update. But while I'm waiting for it to update, let's go and take a look at the drawing.

      And this is just showing that change orders are available as well. Like I said, though, I can't participate in the change order, but what I'm able to do is I'm able to view it. So I'm able to see, what's its current state? What items are involved in it? We use items. Files will be the same, and then if there's any attachments, markups, or things like that.

      So although the mobile app and the Thin Client are similar in application, they have slightly different roles. So the Thin Client you want to use when your data is inside your network so it gives read-only QVP access to those that are inside. What's great about it is that since it's read only, no license is required, and all you need is a browser. So searching and viewing is what you need.

      Now technically, you could Jimmy rig the Thin Client to be available outside the network-- really no different than what you need to do with the mobile app. But that's really not its intention. Its intention is for inside your corporate firewall is what it's intended for. OK, so that's from a viewing aspect, how can I take the Vault on the go with me?

      But what do we do when we've got remote offices where we want people to have access to Vault? Maybe they're working from home, or they're contractors, or they're just going to be short term. We can utilize Vault Gateway.

      So, again, this is a Vault Professional thing. What this does is allows you to open up Vault for external access without a VPN or without HTTPS. So unlike the Vault Mobile Client where you had to essentially open up your Vault to the external world, this is doing something different. What this is doing is this is pushing all the zeros and ones through Forge, and letting Forge take care of the security and the access.

      So users essentially connect to this gateway during the Vault login through a system-generated URL. So what's the requirements for this? Well, the requirements are, like I said, you have to be using Vault Professional on subscription. The minimum is Vault 2022.1, which was the first version. So 2022.1, 2023, 2024, you can implement or utilize Vault Gateway.

      The Autodesk account, that's also the administrator, also needs to be an Autodesk account team administrator. So that same user, when you set this up, has to have a Vault license, and be someone who can administer the teams from the Autodesk account perspective. And your Vault server needs to have a default website binding configured to allow HTTP requests on port 80. Now there are some ways to work around it, but out of the box, locally, it needs to be communicating over port 80.

      So from a security aspect, it is just as secure as opening HTTPS. In fact, it is using HTTPS for the communications, so it's secure. And Autodesk is doing regular standard security testing that complies with some international standards. And if you want to see what those are, you can go to the Autodesk website and they're listed.

      A couple key things here is that there's no Vault data actually stored in Forge. It's just a pass through. So the information is just passing. Essentially, it's just authenticating that you're supposed to be there, and it allows you to pass through.

      It also limits the number of requests made during certain periods. So you shouldn't have any firewall rules broken by it. But this is only for the Thick Client. This does not work with the Thin Client. So you have to be using the Thick Client when you're doing this.

      So what's actually required here? Well, you have to have a service account. So you have to have an Autodesk ID that's associated with the Gateway, which must also have a Vault Professional. So as administrator, I have a Vault Professional license, but I'm also the manager of our Autodesk accounts. So my user is the one that was used to configure this gateway.

      Like I mentioned before, the Vault server does need outbound internet HTTPS access. So nothing special, it just needs to be able to browse the web over HTTPS. There's no inbound ports that need to be opened in the firewall. It's just not required. Your firewall, though, will have to have Autodesk.com essentially whitelisted, because the added information is through the browser. That's where the information is going to come from.

      When I first set this up, I went through and I enabled it. And it created this URL, and I got an error message that it could not be resolved. In that case, it's just I wasn't patient enough. So just a tip, if you're going through this like me, kind of panic right away because it didn't work, you might need to wait 15 to 30 minutes after enabling this for Forge to catch up, and everything to synchronize before you're able to take that URL and distribute it.

      Also, what's important, and this was actually a real bad gotcha for us, is it doesn't support logging and Windows authentication, which kind of makes sense because if I'm remote and I'm going to be logging into this remote Vault server, I'm not going to be using Windows authentication anyways. So I'm not going to have an account on that network. So it's just an important note.

      So the keys to this really is that, for the end user, there's really no difference. The only difference is the server is going to be an HTTPS URL, so that's it. They log in with the same username. They log in to the same Vault, and once they're logged in, it looks exactly the same and behaves exactly the same.

      There is a password requirement on this, which there isn't on the regular account. It has to be eight characters with at least one number and some letters in it. So there's some requirements, but that's it. This thing is magical. No VPN, no opening ports. It is super easy. It is a matter of just clicking Enabled, waiting for it, taking the URL, and sending that URL out. That is it. It's unbelievably simple to give these remote access this way, this fashion.

      So the last tool in the tool chest is Project Sync. So what Project Sync is, is this is a way to synchronize files and folders with the supported Autodesk Cloud drives. So what this is is that I can synchronize files from my Vault with Fusion Teams and BIM 360 Docs. Now Autodesk Docs also works, even though it's not listed here, but that works as well.

      Now I know what you're thinking. You're probably thinking, well, Pack and Go already works with Fusion Teams. That's correct. From Vault, you can do a Pack and Go and it will collect all the information for you and upload that to Fusion Teams. But that's Pack and Go. That's taking that information as a snapshot and uploading it to Fusion Teams, and that's it. If something changes, you need to re-Pack and Go to get that information up.

      Well, what about SharePoint? I know it's on Autodesk Cloud but it's a widely used cloud platform. And Autodesk actually dropped the SharePoint support in Vault 2022. So now all that's left is that you can Pack and Go it via OneDrive to a SharePoint directory. So Project Sync is 100% focused on the Autodesk Cloud services.

      One important note if you are going to be synchronizing with BIM 360 Docs, it does not support Inventor, Revit, or MicroStation references or relationships. It just doesn't understand that. However, if you're using Autodesk Docs or Fusion Teams, you won't have that problem or that gotcha on that.

      OK, so Project Sync is bidirectional synchronization from your Vault to the cloud. Now Vault is the master, so Vault will always send its updates first, and then it will pull down any kind of remaining changes, so Vault is the master. If there wasn't a master, your zeros and ones would be crossing over, and it would get into a last-save win, so Vault is the master in this case, and then it goes and looks for changes in the Cloud drive.

      Those who are using Fusion Teams and BIM 360 don't actually need access to Vault because Vault will just push that information up there and they can go get it. If they're using the Desktop Connector, the Autodesk Desktop Connector, it will actually pull those changes down automatically for them so they do have that option. Now the synchronization can be manual, so I will synchronize the information when I want. And that means uploading it to Teams or BIM 360, or downloading, pulling it down to be manual, and it can be synchronized. So every four hours, we want to run a synchronization to pull that information.

      So the Job Processor is required because that's what's actually doing the synchronization. So you do need an Autodesk ID tied to a Fusion Team, tied with a Vault login for that Job Processor to be able to do that. Now the synchronization jobs get the highest priority. So even more than those creating DWFs, or PDFs, or anything like that, it gets the highest relationship or highest priority so that synchronization happens before anything else.

      Project Sync does understand, it's Vault. It does understand file relationships, so understands that assembly has parts, so that part's used in assembly to make sure that it's syncing everything together. One thing to be aware of is Fusion Team doesn't really have any file reservation capability similar to Vault, so there are some scenarios where files might be edited out of turn. It's just something to be aware of if you're going to be using this with Fusion Team.

      OK, so from an administrative perspective, there's a little bit to do here but it's kind of a set-it-and-forget-it type thing. What do we need to do? Well, one, you need to enable the job server. So you have to have the job server, and you can have as many job servers as you want. But that job server also needs the Desktop Connector. Desktop connector is a free application. You just download it, install it on that same machine that's going to be doing the synchronization.

      You set up the synchronization by setting the root Vault folder, and it will do that folder and down, but you need that root, and then mimic, where is that going in the Fusion Teams, or the BIM 360, or the Docs? So you need that Vault root folder and then the Cloud drive root folder. Notice that the option to manually synchronization is an option. It's not enabled by default but we can enable that manual sync.

      Now once you've got that, you set the schedule. Now it can actually be one way. It could be every day at 12 o'clock we're going to upload to the Cloud drive, and every day at 11:00 PM we're going to download from the Cloud drive, or maybe we're only going to upload to the cloud. We're never going to download, or we're going to do bi-directional. You can get as granular as you want.

      So maybe it's just, you know what? We're going to synchronize every four hours and that's it, or maybe folder A is going to be once daily, but folder B is-- there's more happening in it so we're going to do that every four hours. So you have that control over that.

      What's very slick about the Project Sync is that you can actually tie in filters to it. So maybe we only want to do Inventor drawings, or more importantly, probably, is we only want to do released files. So only when the file is released do I want to synchronize that information. So we can tie it to really any property that's in Vault to only get the information that we want to synchronize.

      So a little bit of setup from the beginning because you have to job server and have all the right accounts set up, and then you need to set up the mapping. And then it's just set it, and forget it, and just let it go. All right, so let's pull this all together. We've looked at all these different tools. Let's look at this. What does this actually do for us?

      Now before I get too far in that, we should talk about Vault Replication. Again, it's a Vault Professional thing. What this allows you to do is actually replicate between sites. And there's no limit on the number of sites.

      So what we can do is we can do full replication, where your SQL database and your Filestore are replicated, or you can have one SQL instance, but then your files are replicated. Just like Project Sync, or similar to Project Sync is the replication can occur on demand, or you can also have it scheduled as well.

      So why would I want to do this? Well, if I've got multiple offices, I definitely want them to have access to one Vault. But there could be a huge performance hit where they go to open, let's say, an Inventor file that's got 10,000 files, and they got to wait for all that information to essentially come across the wide-area network so they can work on it.

      Well, what Vault Replication would do is that each site would have their own kind of Filestore, meaning that they're just opening those files locally over the local-area network, and they don't have to go across the wide-area network. Now by scheduling I can say, OK, you know what? At 1 o'clock in the morning, I want this to make sure that all the deltas are replicated. So if there's been changes throughout the day, let's have that replicated.

      Now what happens if, let's say, first thing in the morning I go in there and make some changes to a file, but now someone else is at the other office goes to open it? Well, Vault's still checking. So Vault goes and says, oh, over in that other location there, something's changed. So then, on demand, in real time, it's then going to pull that file across the area network so that my local Filestore has the most updated version.

      So you never have to worry about working on stale information. It's still one Vault. It's just replicating the data for a performance standpoint. So that's Vault Replication, which could come into play here. And this is what I just talked about, how we can have it as one SQL server, or we're doing full replication across it.

      So bringing it all together, obviously our single source of truth is Vault. Because that's where we're going to put our engineering and design data. That's where we're going to manage change. That's where we want everything to be.

      We can replicate this between-- I put two there, but really, multiple physically separated servers. So they could be separated by blocks, by cities, by countries. We can separate them that way.

      We can establish Vault Gateway so that we have-- home offices or contractors have access to our Vault as well. Obviously Replication won't work because we're not going to set up a Vault server at their location. If we have people outside that are working, especially if they're using Fusion 360, is we can set up Project Sync to push this information out to them so they don't need access to Vault, but they still have access to the information we want them. And then, of course, we've got the Thin Client for internal QVP, and we've got that Vault Mobile for Vault on the go.

      So what does this look like? Well, I've got two offices. I've got office A, office B. I've got a consultant who's working from their office. I've got someone working from a home office. I've got people out in the field, and then I've got a vendor who's using Fusion 360.

      Well, we just talked about how the Vault Replication will make sure that my two physically separated offices are working on that same data. Now I put an AutoCAD drawing in here for an icon. It's really any type of file. That could be a PDF. That could be an Inventor file. It's any type of file throughout there. So the Vault Replication makes sure that both offices are working off the same set of data.

      Well, like we saw is the Vault Mobile allows that person to take that drawing on the go with them. So I'm on site. Oh, I forgot to grab a copy of that drawing. It doesn't matter. They can bring up their phone or tablet and they can get that drawing in real time.

      With Vault Gateway, our consultant and our people working from home or remote offices can log directly into Vault and be working on that data as if they're in the office. And they can be checking in, and checking out, and approving, and working on change orders. And then for that person using Fusion 360, we have Project Sync, which will push and pull the information back and forth for us, all kind of synchronized. Not necessarily in real time, but still, yeah, pretty smartly to make sure that we're all working on the same page.

      Well, what happens if a change occurs? So everyone's taken a copy of this file. They've all looked at this drawing. Well, what happens if someone makes a change to it? So we can see here, user in the home office has made a change to it and they check it in. So version two has now been pushed to the Vault all because of Vault Replication. Well, version two is on both locations. It's still a single source of truth.

      Well, the person in office A goes through and they review it, and they approve it. And by approving it, they've released it, and by releasing it, it's now locked. So that's across the board. So whether I'm using Vault Mobile, whether I'm the home office using Vault Gateway, that file is locked. And unless I do a change order or go through the change process, then no one's changing it. So you can see a single source of truth.

      So to wrap this all up, collaboration occurs when multiple people are working together to accomplish a common goal. A single source of truth ensures that these people are working on consistent and relevant data because we want our stakeholders to actually be using the same data to make decisions. We don't want a copy of a copy of something that got emailed to them four weeks ago, or something that's in multiple places on the server. We want this one single source.

      Now if you're looking at collaboration, looking involving all these tools, you're still going to want to plan for this. You're going to want to clearly lay out responsibilities and agree on some type of cadence on check-in. Because if I'm working from my home office and I never check-in a file, well, it doesn't really help anyone. There's got to be some type of flow to it that I'm checking it in.

      And we want to make sure that we're utilizing the best individual skill sets but also the right tool for the responsibility. If I'm going on site to assist with a commissioning of equipment, the Vault Mobile App is probably sufficient because I just need to access the drawings and the models, and be able to mark them up. I'm not going to be checking them out, making changes. So in that case, for example, the Vault Mobile is exactly what I needed.

      Make sure you've got CAD standards and that everyone involved is using those same set of standards, including establishing a consistent file naming and folder structure. And even though all the tools provide comments, and markups, and change orders, you still want to strive for good communication, even if you're over communicating. So that, in a nutshell, is what Vault Professional can bring to you. It's not just the silo on a server that only people right around that server can access. You can make this that true single source of truth for whoever needs access to the information or how they need the information.

      So that's it. Thank you for attending. Thank you for watching this. I hope you got something out of it. And like I said in the slide before, you might be surprised what comes out of the box with Vault Professional.