Description
Key Learnings
- Discover Shared Views, Shared Data, and Project Sync
- Learn how to create use cases for each: Shared Views, Shared Data, and Project Sync
- Learn how to generate the technical requirements to set up Shared Views, Shared Data, and Project Sync
- Get an overview of what is possible (connecting to ERP, connecting to Fusion Lifecycle)
Speakers
- Kimberley HendrixBased in Tulsa, Oklahoma, Kimberley Hendrix provides custom solutions for lean engineering using Autodesk, Inc., products and industry knowledge to streamline design and engineering departments. Hendrix has worked in the manufacturing industry for over 30 years and she specialized in automated solutions for the heat exchanger industry. She has worked with Autodesk products since 1984. Hendrix is associated with D3 Technologies as the Manager of Data Management, focusing on data management, plant, automation, and mechanical issues
- Senthil KumarDevelopment Manager for the Data Management Engineering Team at Autodesk in Singapore. Senthil is with Autodesk for the last 20 yrs. In Autodesk, Senthil worked as a Product Support Engineer, QA, QA Manager, and Product Owner Product Manager before becoming Development Manager. Prior to joining Autodesk, Senthil worked for Autodesk Distributor, PTC and Delcam.
KIM HENDRIX: So, thanks for skipping the opening ceremonies. I kind of feel honored that you guys all missed all the glitz and glam to come talk about data management with us.
So we're going to talk about extending your data management-- your Vault outside of your firewall using the tools that are in the box. There's some other classes later that'll get you out of the box to connect those things together.
So I'm Kim Hendricks, and I work for D3 Technologies out of the Tulsa office. And somebody reminded me last year that I said this. I do have twins, and I got to keep my job, so give me good reviews because the one's in law school and one's in medical school. So I got to keep my job, and I'll let Senthil introduce himself.
SENTHIL KUMAR: Good morning. This is Senthil-- I'm on of the Vault product managers with Autodesk for the last 14 years. All along in Vault, I started as a QA, then QA manager, product owner, now product manager-- based out of the Singapore office. It's a long way. Happy to see you all.
KIM HENDRIX: Yeah, collaborating with Senthil was awesome because there was 13 hours between us or something. It was good times. We made use of Fusion Team and all those tools that are afforded to us to do this, so it was good. So go for it. OK.
So we're going to go over several different ways to share your data outside of your Vault. Oh, we got some automatic timing going on there.
We're going to define our Shared View, Shared Data, and Project Sync. It's going to go through. We'll go onto the next one.
We'll talk about how to set each one of them up-- what the use-cases are for each one of them, and then Senthil will go on to Project Sync, and what we're going to use that for-- and the use-cases.
And then I'm going to attempt to do a live demo on both Shared Views and Shared Data, but my port times a blink, so if it's irritating-- we'll stop that.
If you have a phone or an iPad or something that has a QR reader-- get it out because I'm going to show a QR code in a little bit. And you guys can pull something up that we've done.
So, basically, the basis is external collaboration. So getting feedback is Shared Views. So that's a quick visual representation of a model or a drawing that you can share out for real-time collaboration during the design phase.
Delivering design phase is your Shared Data. So we're going to deliver those files in native format using Fusion Team or Fusion Drive. It's a one-way connection using shared data.
And then Project Sync is to exchange that for a more elaborate collaboration between outside forces to go back and forth. So, any questions about that?
So Shared Views first. We'll define it a little bit. So it came out in Vault in 2018.2. And it's also available in Inventor and in AutoCAD right inside, so you don't actually have to have Vault to use that.
And there's that QR code if you guys want to prep for that-- it'll be on a couple slides. If you don't have a QR reader, there's actually a link at the bottom, but it's a shortened link, so it's case sensitive. So if you're going to do that, then be sure and do the case sensitive.
So with Shared Views and Shared Data and all that-- Autodesk Desktop Connector is available-- that's how it links to stuff out there.
But remember that Shared Views are temporary visualizations. It's not your raw CAD data. And they stay out there for 30 days unless you extend it-- if you're the owner, and you extend it. And then there's some pictures there. I'll show you some more about what it looks like an AutoCAD in Inventor.
So the basis of Shared Views is it's very quick, and it's fast. And, correct me if I'm wrong, Senthil, but since Shared Views came out-- it just exploded. It's being used quite a bit.
SENTHIL KUMAR: Right.
KIM HENDRIX: And Share Data's been out for quite a while. And it's not getting as much use even though it's a little bit more powerful.
But the Shared Views is so quick and easy to use that to collaborate on that early stuff-- it's being used pretty well. So the beauty of it is, there's nothing to set up. There's one checkbox in your Vault that lets you enable it. And then for your collaborator, they need nothing but that link that you can send them.
And then if they have an Autodesk account, they can comment and send it back, and it comes back in your Vault. And I'll show you all that in a minute.
And so it is protected because it is just a representation-- a pretty picture, a 3D model that they can turn, twist, look at-- or a drawing. So it's not any of your native CAD files or anything like that, so.
So we don't need to read the slides, Jim. So this is what it looks like in AutoCAD. It's a panel that pulls up for Shared Views and if you're an owner, you're Shared Views will show up right there.
And if there's comments on them-- I think there's a pointer on this, but I'm not very good at it-- like this one right here says I've got one comment. I've got two comments. I can go up there and look at it. And if you look real close, it'll show you that they expire in a certain amount of time because it's 30 days.
So Inventor has the same panel. Off to the right, you can turn it off and turn it on-- your Shared View, so you can get it right inside your Inventor.
And then you also have the same panel inside of Vault. And on the one on Vault-- I clicked on it, actually, so you can see one of the comments below on there.
So does everybody have their little QR code read? OK, we're going to do a-- we're going to try this on 5. Let's turn that one off, and that one on.
SENTHIL KUMAR: Yep.
KIM HENDRIX: Nope, we went back.
SENTHIL KUMAR: Yep.
KIM HENDRIX: We're good?
SENTHIL KUMAR: Mm-hmm.
KIM HENDRIX: OK, it's probably going to blink, but I'm going to try to do it real quick. So to do a Shared View, you could pick on an assembly, and you can right-click on it, and go to Shared Views.
AUDIENCE: There it is-- here.
KIM HENDRIX: There it is. It's going to blink, but bear with me. I can name it whatever I want. I can choose to hide the components or hide the part properties, and I create Share, and it takes it just a second to do it depending on the Wi-Fi in here.
Now that I have you guys all using your Wi-Fi-- probably have the bandwidth down. There it goes. And I have my Shared Use turned off.
AUDIENCE: Does it use Job Processor?
KIM HENDRIX: No-- good question. The question was-- in case you didn't hear, was-- does it use Job Processor, and this does not. It's handled right on the client-side using the Desktop Connector.
So it pops up there, and I can view it in the browser, or I can copy the link. I'll view it in the browser real quick. So the browser is the Autodesk Viewer, which is a free viewer on the web.
So I'm not logged in right now to Autodesk, so I can pull it up. So this is actually a little engineering project that my son did. It's a cup with a condiment holder on the top of it. But I can view it, look at it, print it, I can make comments, and I can do markups as well.
So if I do markups, I can circle stuff. I can put text on there. I can say, isn't this cool? And I could say that, and it goes right back to my Vault.
It's saying I'm going to have to sign in to save my comments. I'll sign in. There we go. And so it's applying those to my-- and if I go back to my Vault and close this, and show my Shared Views.
I'll close my properties so we have a bit more room. There we go. And here's the one I did, and it expires in 31 days. And there's some here that have the-- and this is how the comments look. So I get real-time feedback from that.
So that QR code I sent you was the one I did the other day. Did anybody pull it up on their phone? Anybody see it? OK. So on your phone-- it's very mobile-- laptops, iPads, the Apple version, the Samsung version-- the whatever version you have because it's in a browser. I'm going to switch back to you, Senthil. Quit blinking.
SENTHIL KUMAR: Sure.
KIM HENDRIX: There.
SENTHIL KUMAR: There you go.
KIM HENDRIX: So questions about Shared Views-- they're use? What'd I do with the little clicker? Gosh, you guys are quiet. I did this in a practice set for three people, and they asked a million questions.
AUDIENCE: So is that draw A360, or is it just another file [? period? ?]
KIM HENDRIX: Senthil, what's the background on that?
SENTHIL KUMAR: So this is Lite Model Viewer, LMV. So it's not using anything on A360 or anything. So the data is getting processed locally, and only the Viewable is going to the Viewer. So no K-Data-- nothing goes to the cloud-- just the Viewable.
KIM HENDRIX: It's not using Fusion Team or RS Drive, or anything like that--
SENTHIL KUMAR: No, nothing. And you cannot even download this one.
KIM HENDRIX: Right. And if you try to print your file, it doesn't actually even print in a usable format. It puts it at the top, and I think, in the handout, I actually show that, but it puts it like a little viewable in some description below it. So it's not like somebody can go and build from that viewable typically.
AUDIENCE: Can you make it only viewable to certain people, or is it open to anybody that's got a link?
SENTHIL KUMAR: Whoever has a link-- they can open it up.
KIM HENDRIX: Yeah, if they have the link, they can see.
AUDIENCE: Only in the Vault Pro or Workgroup?
KIM HENDRIX: It's in Workgroup [INAUDIBLE]. Yeah, but not in basic, yeah.
AUDIENCE: Can you block it just so it's Plain View, so you can rotate it around, so if you might have a 3D plan, you can just zoom in and out in the right columns?
KIM HENDRIX: Well, if you do it of a drawing, which I didn't do-- it's just a drawing. So depending on the file that you use. If you do it of a model, then you have it in 3D. But if you do it of just a drawing file-- an AutoCAD drawing file or an Inventor drawing file, then it's flat.
AUDIENCE: In Civil 3D service, you won't be able to rotate it?
KIM HENDRIX: I don't think it works in Civil 3D, does it?
AUDIENCE: In paper view.
SENTHIL KUMAR: So can you do that using your DWF? So if you're able to do that using DWF-- you can do that same thing in Viewer.
KIM HENDRIX: And that's why we have the big guns with this.
SENTHIL KUMAR: [INAUDIBLE] is this like no.
AUDIENCE: I think especially if you turn part-time off [INAUDIBLE]?
SENTHIL KUMAR: Yes.
KIM HENDRIX: Yes, you can-- assuming I don't check those boxes that hide things.
SENTHIL KUMAR: Right.
KIM HENDRIX: If I'm hiding the panels on that, then you can't turn things off and on when I create it. So that's a choice that you get.
AUDIENCE: Can you set it up so that you can't section it?
SENTHIL KUMAR: Yes.
KIM HENDRIX: Yes. You don't want people seeing your guts?
AUDIENCE: Nope.
KIM HENDRIX: OK. Just checking-- just checking.
AUDIENCE: With respect on the issues to where it can or cannot [INAUDIBLE] share with the media, you have to have certain
KIM HENDRIX: You're talking about to be able to create a Shared View? It's an On or Off in the Vault. So for everybody, it's either On, or it's Off.
There's not any permissions around. When I get to the setup, you'll see, it's literally just a checkbox in your collaboration that turns it Off and On. You have to have admin rights to be able to turn that On.
But once it's On-- It's On for everybody that has rights to the file. But it only goes to their Autodesk account as an owner. So it's not like you're going to have that Shared Views panel is going to be populated with everybody in the company's Shared Views because you're only going to see the ones that you put out there, because it's controlled by your log in. Yeah.
AUDIENCE: So can admin see their members' Shared Views?
KIM HENDRIX: No.
AUDIENCE: [INAUDIBLE]?
KIM HENDRIX: No. It's controlled by your Autodesk login. Remember that part where I said it was quick and easy? So there's some give and take with quick and easy, right?
Anyway, so any other questions about-- oh, and the other thing I didn't talk about was this little picture right here-- is the email that you get when you create a Shared View that tells you it's ready. That's a screengrab of what the email looked like when I created that. Yeah.
AUDIENCE: Can the users see other users comments?
KIM HENDRIX: Can users see other users comments?
AUDIENCE: So if I roll this out, with like five people-- can everybody see what everybody's--
KIM HENDRIX: Everybody's comments-- if they have the link, yes.
SENTHIL KUMAR: If they have the link, yeah.
KIM HENDRIX: Yeah. Yeah. That was a good question. But, yeah, so if they're all-- if you pull it up in the viewer, all the comments are there. And you can mark them resolved. And I think once you mark it resolved-- the comment goes away.
SENTHIL KUMAR: Yes.
KIM HENDRIX: I think it goes away if the owner of it marks it resolved-- that comment goes away from the list. And then you, as an owner, it expires in 30 days, and you have the option to extend it. So if you're still collaborating, you can extend that view.
AUDIENCE: So are there an unlimited number of Shared Views you can have [? on an Autodesk ?] server?
KIM HENDRIX: Not that I'm aware of.
SENTHIL KUMAR: No.
AUDIENCE: [INAUDIBLE]?
SENTHIL KUMAR: That's why we get that 30 days. So then after that-- it goes away.
KIM HENDRIX: Yeah.
AUDIENCE: Can you use that net 30-day time frame to arrest [INAUDIBLE]? Or is it just--
SENTHIL KUMAR: By default, it's 30 days.
KIM HENDRIX: Yeah, by default. I think you can delete them though.
SENTHIL KUMAR: You can delete them.
KIM HENDRIX: Yeah, so if you're done with it in 30 days, so then you can remove it.
SENTHIL KUMAR: Go ahead and delete it. Yeah.
KIM HENDRIX: Yeah, you can remove it. Yes.
AUDIENCE: How does it get shared out to other users?
KIM HENDRIX: So remember when I did my-- when my blinking display went on? It popped up, and it said, copy the link.
And you send that link out to-- like that link up there-- that ACTBS, you send that in an email to whomever you want to get it. So you can control who gets it. I mean, I guess if they can go randomly generate those, they could look at links.
AUDIENCE: I can open it in any web browser?
KIM HENDRIX: Yeah, any web browser. I don't think there's any web browser-- I've tried it on Edge, and IE, and Chrome, and Mozilla, and I haven't had any-- and the Apple stuff, and I haven't had any problems. And did you--
AUDIENCE: Can you delete the Shared View history somewhere?
KIM HENDRIX: No. That's a great question. So that's the other thing about this. This is work in progress collaboration. So all your comments-- they're not stored, which is one of the things that I requested, but it was like no, we're not going to do that.
But the only way you can store them is to screengrab it from your admin set, and save it as an attachment or something.
AUDIENCE: Is the Shared View link stored in the Vault somewhere?
KIM HENDRIX: No.
SENTHIL KUMAR: No.
KIM HENDRIX: No, but it's in your Shared View panel for as long as it's there, so you can get to it.
AUDIENCE: Right, but I can't get it from the [INAUDIBLE]. You can't go past the Vault when you are in the Shared View, can you?
SENTHIL KUMAR: No.
KIM HENDRIX: Oh, not that I know of.
SENTHIL KUMAR: No.
KIM HENDRIX: That's a programmer asking stuff.
[LAUGHTER]
I don't think so.
SENTHIL KUMAR: But you can get a copy of that and then put that into the UDP, and then attach the file.
AUDIENCE: Sure.
KIM HENDRIX: Yeah, I guess you could do that. You could put it in a property, and then you can get--
AUDIENCE: Do it manually?
SENTHIL KUMAR: Manually.
KIM HENDRIX: Yeah. Manually-- you'd have to copy it until you think of a way to do it otherwise.
SENTHIL KUMAR: That's a wishlist.
KIM HENDRIX: Yeah. [LAUGHS]
SENTHIL KUMAR: [LAUGHS]
KIM HENDRIX: Any other questions on Shared Views? OK. So I'm going to move on to-- so this was a video that I-- so I'll put this PowerPoint on-- I don't have it on the AU website yet, but I will.
And for each one of these demos that I'm attempting to do live, there is a video that goes along with it that you get to listen to my raspy voice.
So that was the feedback. So we're going to move into Shared Data, which has actually been around for how long? Do you know how long Shared Data's been around?
SENTHIL KUMAR: It's at 18.3.
KIM HENDRIX: OK. And it takes advantage of the Pack & Go. And Pack & Go's been around as long as I can remember. Pack & Go's been around. But they added some options to it to make Shared Data work with you.
And the examples I'm using are Fusion Team, but it also works with Autodesk Drive. And then you could look on-- is it the red one that's the pointer?
SENTHIL KUMAR: Yeah. It's very small.
KIM HENDRIX: Oh, there it is. OK. So when I go into Pack & Go, I pick my top-level assembly or drawing like you would if you were going to send them to somebody. I can choose-- if I have my mapping setup, and we'll get to that in a little bit. I can choose my Fusion 360, or Autodesk Drive, or SharePoint or whatever I've got there.
And then when I hit Next, it's going to say, OK, but where do you want it-- in my Fusion 360? So I select a folder, and it will pack it all up, and it doesn't-- you have a choice between zip files. But I don't put zip files on Fusion Team.
So I have it unzipped-- and then when it goes out into my Fusion Team, it looks like you manually loaded it, but it does it for you. And if you update it, and load that same data again, it'll load on top of it-- inversion it on Fusion Team. Tell me when I say something wrong. Because [INAUDIBLE]--
SENTHIL KUMAR: Sure.
KIM HENDRIX: So it's that next level of collaboration. So now you've got your work in progress stuff done, and you've designed your widget or gidget or whatever it is that you're designing, and you've worked with all those people and got that real-time solutions back.
And, now, you really need to share the native data for maybe tooling, or for more extensive collaboration, or for them to use in their files or to open and work on for you, or maybe they create drawings for you, or whatever this-- that's what the Shared Data is. It's that next level of sharing it outside.
So they don't have to have access to your Vault. And it's a one-way push, so you're not getting their stuff back-- although, if they added it-- if you give them rights in Fusion Team-- it's there in your Fusion Team. But it's not going to push back automatically to your Vault. That's the next step, which is the Project. Sync.
So this is a one-way push to share it outside the native files. So, remember, when you do this, you are giving them the native files of your CAD stuff. So if you don't want him to have the guts, then don't give them this one.
So that's how we're using that one. OK, we're going to try this again. We'll try a Shared Data. We'll switch it. Sorry for the blinking-- let's go to the [? rotor ?] this time.
And I grabbed my stuff off GrabCAD, so you can see this is in some other deal. So I'm going to do this assembly right here.
And I go to File and Pack & Go. And I'm going to do it as Unzipped. And I have a choice right here like I said, so I can do Fusion 360.
And I don't want to put my project file out there again, so I'm going to uncheck that. And I have choices there. So and I say, OK.
It's going to bring up my Fusion 360. And close your eyes, so you don't see everything in my Fusion 360. I'll put it on my D3 Tech, and I'll go to AU. And we'll put it in File Sets. That's it. OK.
So it feels like it did that super quick, but if I go look at my Desktop Connector down there, it's actually doing a little bit of work in the background. It's got to upload that, but it's pretty quick.
And let's see if I can go to my Fusion Team. Let's see if it's there. And they're still loading the file, so only a couple of them are there. But you can see that they go up there rather quickly. And I'm on the Wi-Fi that everybody is using here, so it goes up there rather quickly. I'm going to switch back to you because it's--
SENTHIL KUMAR: Sure.
KIM HENDRIX: The blinking irritates me. So any questions about Shared Data? Yeah.
AUDIENCE: What about the drawings associated with the parts within the [INAUDIBLE] based on the IM?
KIM HENDRIX: So the question is, what about the drawings? If I had started my Pack & Go at the drawing level, it would have grabbed the drawing as well and then all of its children.
My example-- I started the assembly level. So whichever level I start-- if I start at the upper-level parent of the drawing, then it'll zip it up with it as well-- not zip it, but send it as well.
AUDIENCE: So we have to start on the drawing late on the assembly?
KIM HENDRIX: Yeah, if you want the drawings to go with it, or you can-- on that-- can I select Parents on the Pack & Go? Yeah. There's a setting in the Pack & Go where you can select the parents like you can if you're doing other things, and then it'll give you the option of the drawings as well.
So you do the assembly and then, say, select Parents, and it would go find your parents and let you pick between all the drawings that are associated with it, or you can start at the drawing, and it'll pick all the children by default.
Does somebody else have a question over here-- Shared Data? No? How are we doing on time? OK. We're good. So like I said, Shared Data is that next level. And, again, there's a little video, and I'll play that since you don't need it.
So now we're to the point where we've done it in the Work in Progress, and we've shared it quickly with our views. And then we've delivered some design files.
And then, next is, let's collaborate back and forth with outside engineers or contractors or customers if you need the rest of this stuff and that. I'm [INAUDIBLE]
SENTHIL KUMAR: Thank you, Kim. Thank you. So we have seen Shared View, Shared Data-- now, you want to get back and forth.
So the two-way communication-- that's where the Product Sync is going to help. So what's Product Sync? It's a feature that can help you to synchronize your Vault folder to your Cloud Mapping drive.
So this can be one direction, or it can be bi-directional. So you want to send the data, or you want to pull and push. The pull and push can be both manual as well as automatic. If you want to synchronize the data at a specific time, you can send those times.
So what are the use cases where this Product Sync is going to help? Let's select another user-- a design engineer. Now, he wants to send an up-to-date Release data to his customer, right? So that's one use case.
And the second use case is, let's say a user would like to outsource some of the CAD files to another vendor so that they can clean up, and they can create drawings. And then once they create the drawings, they would like to get that back into Vault without any loss of data, right? That's a second use case.
The third one is-- I want to send everything to my outsourcing company, and I want to get everything done. And then once it is done, I want to get that back into Vault.
And the very important thing with the Product Sync is you do not need to expose the entire Vault to the drive-- the Cloud. You can specify which folder that you want to map. And you can also specify which state. Like now, I want to send only the Release data I don't want to send all those Work in Progress data. So you can specify all those things.
Let's do a small demo. I'm going to run a video because the sync takes a bit of time. So here you are going and conjugating to the Vault folder. I'm going to specify the one folder. And then I'll go into the Fusion 360, and I'm going to specify the product out there. And then, here you can specify the schedule every few minutes, or a few hours that I want to synchronize.
And, also, I'm going to specify only the Released files. I don't understand any other files. Once it is done, it sends into the-- I'm going to Inventor. I'm going to change the state from Work in Progress to Released.
So as soon as the Change Date is done, the file is released, the Job Processor kicks in, and the file is synchronized and then sent to the Cloud.
You don't need to do anything. So it's done automatically in the background using the Job Processor-- plus the Desktop Connector. So I can open directly from the Desktop Connector inside Inventor.
So there's the supplier who is opening the file that I sent. He is opening it, and he will edit all this information, and then save it back to the Fusion Team, and that comes back to the Vault.
He is creating a CNC code, and then this code gets saved back to the Fusion Team and comes back to the Vault. Any questions?
AUDIENCE: [INAUDIBLE] you said coming back to Fusion Team and the Vault.
SENTHIL KUMAR: So that's like-- you can have bi-directional associativity like synchronization. So once you set that on-- once the changes are done in the Fusion Team-- it comes back to Vault.
AUDIENCE: How does that work with [INAUDIBLE]?
SENTHIL KUMAR: No, it's only on the file level. Yeah.
AUDIENCE: Can you control-- what information you get synced? So, for example, you have a whole list of problems that are not the kind that you want to share--
SENTHIL KUMAR: Mm-hmm.
AUDIENCE: --with an outside collaborator-- does everything go?
SENTHIL KUMAR: Just the files.
AUDIENCE: Just the files?
SENTHIL KUMAR: Yeah.
AUDIENCE: So you'd have to make sure that they're not linking to get synced back to [INAUDIBLE]?
SENTHIL KUMAR: No. Just the files. And, in the Fusion Team, you cannot edit any properties, or you can see the properties.
AUDIENCE: Ah, OK.
SENTHIL KUMAR: Yeah.
AUDIENCE: So the person outside of your company either has to have the drive-- Autodesk drive--
SENTHIL KUMAR: Fusion Team.
AUDIENCE: --or Fusion Team?
SENTHIL KUMAR: Right
AUDIENCE: Either one.
SENTHIL KUMAR: Right.
KIM HENDRIX: Wait-- the person outside your company doesn't. You can give them access to yours to share your data. They don't have to have a subscription.
AUDIENCE: So they have to have access to my Autodesk drive?
SENTHIL KUMAR: The Fusion Team-- you can invite your collaboration.
AUDIENCE: OK.
SENTHIL KUMAR: Yes, sir.
AUDIENCE: So if you've got files you said, let's say, version 21-- and you just port it to the Fusion, and someone gave to you as a change-- Fusion doesn't recognize it like a version 21-- it treats it like version 1.
SENTHIL KUMAR: Right. And when it comes back to Vault, then it's version [? 12. ?]
AUDIENCE: [INAUDIBLE].
SENTHIL KUMAR: Yep.
AUDIENCE: So does it actually do check out, or is there any issue with the user using it all at the same time?
SENTHIL KUMAR: No. OK. It's not going to check out. So the file goes in, and when it comes back, it checks out, and then versions [? of. ?]
AUDIENCE: OK. [INAUDIBLE] can use your user when [? he's placing ?] it back in Vault?
SENTHIL KUMAR: Yes. So when you pull the data from the Cloud-- so it uses the same user who is logged in.
AUDIENCE: Could you do an assembly that pulls all the parts up [? in order? ?]
SENTHIL KUMAR: Right. That's the one--
AUDIENCE: Once you do the assembly.
SENTHIL KUMAR: Right. So that's the one thing now-- I'll be going through that call. So you can choose what data that you want to synchronize. And you can enable the Manual Sync to trigger the sync process. And this is the one-- the third one.
So the files that you are uploading is going through the Desktop Connector. It knows that it is a CAD file. So when you select the assembly, it pulls up all the related data.
And it also supports links. So let's say you have a folder that has a link-- filings inside the Vault plan and the files are available in multiple folders, so the link will go and pull all the related files and then gets uploaded. So you don't need to go on and do all those manually.
AUDIENCE: So is there a way just to get the assembly, and operate the children [INAUDIBLE]?
SENTHIL KUMAR: Just assembly?
AUDIENCE: Yeah.
SENTHIL KUMAR: Then, no.
KIM HENDRIX: Well, in that case, you'd want to do a Shared View because you want him to see a picture.
SENTHIL KUMAR: Yeah.
KIM HENDRIX: Because--
AUDIENCE: [INAUDIBLE].
KIM HENDRIX: That's true-- you'd have to send him a DWF file maybe.
I guess you could upload a DWF file and accomplish that. It wouldn't do it through Project Sync, but you could to a DWF file, and then it wouldn't go away.
AUDIENCE: So will it follow the formation of the Vault, so if we did seek it-- after you've transitioned it from a work product-- or a state to a different state that is read only? Is [? Arduino ?] syncing then, or--
SENTHIL KUMAR: Yeah. Then you'd need to have the permissions to sync.
AUDIENCE: So, with permission, it's possible?
SENTHIL KUMAR: Right?
AUDIENCE: OK. OK. [INAUDIBLE]
KIM HENDRIX: And this is-- correct me if I'm wrong-- this is handled through the Job Processor?
SENTHIL KUMAR: Right.
KIM HENDRIX: Right. So it queues a job when it does it and uses the Job Processor. Everybody knows the Job Processor-- what it is, right?
AUDIENCE: So this works with only Fusion, or will it also work with the AutoCAD Electrical project?
KIM HENDRIX: AutoCAD Electrical Project on a Pack & Go. I don't know why. Project Sync would work with an electrical project.
SENTHIL KUMAR: Yes.
KIM HENDRIX: Yeah.
SENTHIL KUMAR: Yeah.
KIM HENDRIX: Yeah. I mean, it works with whole folders.
SENTHIL KUMAR: Should be.
KIM HENDRIX: Yeah.
SENTHIL KUMAR: As long as you have those files inside the Vault. Yeah, you can push it in.
KIM HENDRIX: Good question, though.
SENTHIL KUMAR: Yep.
AUDIENCE: What about those files checked out from the Vault because you share them, and it checks out, it is closed under-- in the Fusion-- [INAUDIBLE]. Where can checks out and checks in
SENTHIL KUMAR: Right. So when it comes to Vault, it [? motions ?] up.
AUDIENCE: [INAUDIBLE], it checks out, and it checks in.
SENTHIL KUMAR: Right.
AUDIENCE: And it means that I can share the files on Fusion. And it means that the files-- or they have a newer version.
SENTHIL KUMAR: Yeah, it'll do all right.
AUDIENCE: Whatever it is.
SENTHIL KUMAR: Right.
AUDIENCE: [INAUDIBLE].
SENTHIL KUMAR: So that's why when you specify a folder, you are going to collaborate that folder, so you don't do anything till that gets done and gets back.
AUDIENCE: And you can share our folder to those with two levels. And they can invent their file that has some parts [INAUDIBLE] all sites like you shared-- will it go throughout this file?
SENTHIL KUMAR: Yes. When you upload it, it takes up all the related files. Yeah.
AUDIENCE: When you do the six-step, published step on your website-- [INAUDIBLE] and add yourself-- add the specific step on your website when you do it?
SENTHIL KUMAR: Right.
AUDIENCE: OK.
SENTHIL KUMAR: So in the demo, I was showing it's only the Released state.
AUDIENCE: Right. But you could do it different--
SENTHIL KUMAR: Different state. Yeah.
AUDIENCE: [INAUDIBLE]
SENTHIL KUMAR: Yes.
AUDIENCE: That's when you do the job--
SENTHIL KUMAR: Right.
AUDIENCE: The job [INAUDIBLE]?
SENTHIL KUMAR: Pardon?
AUDIENCE: Is the job itself-- Our Jobs job part of the Job Processor job through APA?
SENTHIL KUMAR: Good question. Through APA?
AUDIENCE: Through the [INAUDIBLE] or if you replace it through the script.
SENTHIL KUMAR: I need to check that out.
AUDIENCE: Does that mean we can change something inside of Permissions of when we share?
KIM HENDRIX: Yeah.
AUDIENCE: Inside there?
SENTHIL KUMAR: So the sync can happen in either direction. You can, also, if you want to support the subfolders-- you can now apply to subfolders-- and you can schedule the timing for the sync. And, also, admin can control which ones they can sync.
Out of the box, we have 5 job types-- manual upload and download, the scheduled upload and download, and scheduled sync, which is the bi-directional.
So all scheduled jobs are cued up. And then you can view Job Queue using an ADMS console. And in order to use Product Sync, you need to have the Desktop Connector. So Desktop Connector is going to pull your data and push it to the Fusion Team.
So, in summary, bi-directional CAD exchange between your Vault and the Cloud drive and awareness of where you are pushing that CAD file.
So all the related files are getting pushed. And you can also select the data to push to the Cloud through the Job Queue. And then if you have a Fusion Team, you can invite your collaborator to your Fusion Team to collaborate. Right.
AUDIENCE: Are you saying just the drawings without their children?
SENTHIL KUMAR: You cannot. I see no--
KIM HENDRIX: It'd be the same as assembly because it wants the children to make it a viable file up there. It'd be the same as if the assembly-- as you'd want to-- if the drawing is the only thing you want to send, then send a PDF. [LAUGHS] Or a DWF because that doesn't then require the children behind it.
SENTHIL KUMAR: Yeah.
AUDIENCE: In Fusion-- where they go in Fusion-- does it create a new project, or-- because I put locations in mine.
SENTHIL KUMAR: You use specifically the location of where you want to go.
AUDIENCE: That's Fusion's 5. That's not 3, correct?
SENTHIL KUMAR: That's not--
KIM HENDRIX: 3.
AUDIENCE: 3. It's not part of [INAUDIBLE], or--
SENTHIL KUMAR: You need to have a Fusion Team icon.
KIM HENDRIX: Yeah. Fusion Team's a separate subscription.
SENTHIL KUMAR: Yeah.
KIM HENDRIX: Autodesk Drive is a subscription benefit.
SENTHIL KUMAR: For Vault Pro.
KIM HENDRIX: Yeah. For Vault Pro. But to do Project Sync, you have to have Fusion Team.
SENTHIL KUMAR: Fusion Team.
KIM HENDRIX: Yeah. You have to have the Fusion Team.
AUDIENCE: Isn't that in the order by when the most recent release came out right over BIM?
SENTHIL KUMAR: BIM?
AUDIENCE: Yeah.
SENTHIL KUMAR: So right now, with BIM-- it's in the previous state.
AUDIENCE: Does that mean-- it ultimately means that it's not just Fusion, it will be BIM?
SENTHIL KUMAR: It will be BIM 360.
KIM HENDRIX: We should have put a Safe Harbor statement up, huh?
SENTHIL KUMAR: [LAUGHS]
KIM HENDRIX: [LAUGHS]
SENTHIL KUMAR: Yeah.
KIM HENDRIX: But that's the goal, isn't it?
SENTHIL KUMAR: Yes, rather.
AUDIENCE: But that's two outside clients. Let's say one is, you got [INAUDIBLE]. Ones-- That's license fees?
SENTHIL KUMAR: No.
AUDIENCE: It's only one--
SENTHIL KUMAR: One license.
AUDIENCE: [INAUDIBLE] license fees?
SENTHIL KUMAR: Yeah.
AUDIENCE: [INAUDIBLE]
SENTHIL KUMAR: As long as they have the access to the Fusion Team. Yeah.
KIM HENDRIX: Yeah. As long as you invite them to your team, it doesn't hit other licenses.
SENTHIL KUMAR: Right. Yeah. That license is different. Fusion Team's license is different. And the Vault is different. Yeah.
KIM HENDRIX: Yeah-- good question. The Job Processor will take another Vault license, though.
SENTHIL KUMAR: Yeah.
KIM HENDRIX: So you have to be aware of that when you're setting that up. Any other questions about Project Sync?
AUDIENCE: [INAUDIBLE]
KIM HENDRIX: Does it make-- does everybody understand the difference between the three that we've gone through so far? Cool.
SENTHIL KUMAR: Thank you.
KIM HENDRIX: Thank you, Senthil.
SENTHIL KUMAR: You're welcome.
KIM HENDRIX: So the technical stuff-- how to set it up for us admin-type people-- there is Desktop Connector. You've heard us say it multiple times. It needs to be running on your system, and probably your Job Processor's system if you're doing all things.
So if you're doing Shared Views-- Shared Data from your client, you'll need Desktop Connector on your client. If you're doing Project Sync-- then Autodesk Connector has to be on your Job Processor, which, ideally, is a separate machine.
It can be downloaded multiple different ways. There's a link there. You can get it from your Fusion Team to install a Desktop Connector. I think you can google Autodesk Desktop Connector, and it'll come up.
There's many ways to install it, but it has to be there. And if it's not, when you try to map your Cloud drive, it'll say, you have to have Desktop Connector. So it won't let you do it without it. So that's step one when you're starting to set things up is to make sure that we all have Desktop Connector.
And then we've got to go to our Collaboration settings inside the Vault. And this is an admin-- you can do it from the Client, but you have to have admin privileges to make changes here.
So for Shared Views, this is the only setting. That's kind of the beauty of Shared Views is-- that's it. Just check that, and make sure they have an Autodesk account, and Shared Views works. It's pretty sweet.
If you want to do the other stuff-- the Project Sync Management-- you have to configure the Drive Mapping, and I'll show you that in a minute.
Shared Data just requires the Desktop Connector because it uses the Pack & Go, and then it lets you map your drive. So there's no other settings inside a Vault for Shared Data. Any questions about the settings?
AUDIENCE: [INAUDIBLE].
KIM HENDRIX: So if you're going to start mapping your Cloud drives-- if you don't have Desktop Connector, this is the warning you get-- I had to go to another machine to make that happen.
So then if you go to Configure, you create a new Cloud Mapping, and you can create-- I don't think there's a limit-- as many Cloud Mappings as you want.
SENTHIL KUMAR: Yeah.
KIM HENDRIX: Be careful with that. But you can probably create as many you want. So we'll create a new one. And then this is really busy, but it's spelled out better in the handout.
I was afraid we were going to run out of time, but Senthil and I talk too quick, so. You name it, and then you say what Vault folder do you want it to read from. You can go down as deep or as high-level as you want on that. And then you specify your Cloud drive. And when you hit that, you're going to get this dialogue right here.
When you hit this button right here-- you'll get this, and it'll go to your Fusion drive, and you can pick your folder that you want.
And then here's the stuff that Senthil was talking about-- about enabling Manual Syncing or not. And Upload Related Files Based on Release Bias-- so we can control that or not.
And then we come down here, and we do the scheduling. So this is my first one, and it's not scheduled, but it is bi-directional, which means I'm going to have to manually push it-- manually queue that. But I can schedule it on a timed basis or on a release function and do it bi-directional.
If I want to schedule it-- I did some more over here. There's these three tabs right here. So the General's going to give me what I said here. And then if I go to the Schedule tab, I get this right here. And I could say, every day at 10 o'clock, or every night at 5 o'clock-- sync this.
So if you're working between the States and Singapore, you could schedule it at different times so that each of them has the latest stuff back and forth. So you can schedule that and apply that action to subfolders daily, or every hour, or none at all.
Also, one of the things that I don't think Senthil touched on much is-- you can also filter out. So if you have this whole folder that you want, you can filter out and make sure that you only do Release Dates, or you can have a special UDP that says-- sorry-- a user-defined property that says, sync this-- is it true or false? And that you get whatever search condition you want to apply here or multiple ones.
Just remember that these are "ands" and not "ors" on your filters, right? "Ands" not "ors" on your filters so that way you have a little bit more control.
If you're doing a top-level project folder, but you really don't want him to have your FEA calculations, or your emails that you put in there along that project, or whatever your criteria is, you can control that a little better that way and still do the top-level folder project.
So I know that's a busy slide. Any questions about setting up that Drive Mapping? The handout that's on that AU website actually describes each one of those in pretty good detail. You have a question?
AUDIENCE: Is that admin on a user by user basis, or by set up one user [INAUDIBLE]
KIM HENDRIX: You have to have certain rights to set up a Cloud Mapping. But I don't think you have to have admin to actually set up a mapping. I have to look at the roles.
So, I mean, it's meant for your project lead to set them up so that they're mapped correctly to your Fusion Team. You have to have-- I don't even know what roles you have to have to set that up. You don't have to have admin.
SENTHIL KUMAR: You don't have them. No, not in admin.
AUDIENCE: This is per folder.
KIM HENDRIX: Per folder, yes.
AUDIENCE: In our own setting. Because these settings are for--
KIM HENDRIX: Per folder, right. So for each folder that you want to map to the Cloud-- because I mean, you wouldn't want to put your whole Vault up there. I mean, I guess you can, but you wouldn't want to put your whole Vault up there to share on your Fusion Team. You want just the projects that need to be collaborated on, so you do it by folder.
AUDIENCE: All subfolders go with it then.
KIM HENDRIX: The subfolders-- if you tell it to do that-- it does. Sorry, I admit to not do that. I hit the wrong button.
Yeah, you can apply the selected action to the subfolders. But it will take the children as necessary because it's CAD-aware so if it's got a child to it-- it will take them the same. Any questions about configuring? Yeah.
AUDIENCE: Can you control permissions [INAUDIBLE]?
KIM HENDRIX: Well, it's in your Fusion Team, so you can control who you invite to that folder. And who you give access to it there. It would fall to your security out on your Fusion Team's site.
So I looked on my Vault, and I was really surprised that none of you put a comment on that Shared View that I had you-- nobody commented on it. I was surprised. Did you have a question?
AUDIENCE: Yes, on the-- when somebody makes a change on Autodesk-- it's synced, so this isn't coming back, it's not happening.
KIM HENDRIX: No, this syncs.
AUDIENCE: Oh, this syncs--
KIM HENDRIX: This is bi-directional, or it can be bi-directional.
AUDIENCE: When you invite someone to your Shared Drive, and they're doing something with it-- do we know when it comes-- when it brings back-- do you know who it was?
KIM HENDRIX: I don't know.
AUDIENCE: Does it retain the user's name?
KIM HENDRIX: That's a good question. I don't know.
SENTHIL KUMAR: So from Fusion Team?
KIM HENDRIX: Yeah.
SENTHIL KUMAR: The user information.
AUDIENCE: You can get whoever's logged into the Job Processor?
SENTHIL KUMAR: Yes.
KIM HENDRIX: Yeah. Probably the Job Processor.
SENTHIL KUMAR: Job Processor.
AUDIENCE: So when the change gets checked back in-- that's not this one-- that's the--
KIM HENDRIX: No, that's this one. This is the only one that gets it back to Vault.
SENTHIL KUMAR: Yeah.
KIM HENDRIX: Right? The Job Processor would be the one that the user--
AUDIENCE: And that gets to just to whoever the Job Processor--
SENTHIL KUMAR: Right.
KIM HENDRIX: Well, whoever you have logged in as a Job Processor would get it.
AUDIENCE: So you'd have to do something clever to figure out--
SENTHIL KUMAR: Who is--
KIM HENDRIX: Yeah, you'd have to go look on a Fusion Team to see who--
AUDIENCE: --and then bring that back into--
KIM HENDRIX: Fusion Team will tell you who added it last.
AUDIENCE: Right.
KIM HENDRIX: But I don't think that information carries back to the Vault because the Job Processor is the account inside of Vault because your Fusion Team people don't have accounts inside of Vault, so.
AUDIENCE: Right.
KIM HENDRIX: Yeah.
AUDIENCE: If you'd want to know, you'd have to put it out for three different--
KIM HENDRIX: Yeah, you'd have to do something clever in the UDP of the actual file or something.
AUDIENCE: So you'd have to do something where all the Fusion Team. You'd have to grab that information and stick it in the property or something.
KIM HENDRIX: Stick it in property or something. Yeah.
SENTHIL KUMAR: Right.
KIM HENDRIX: Comment or something, yeah. Something-- you'd have to do something that way. Yeah, good point, though. Yeah. You need to know who's got access to your Fusion Team for sure.
AUDIENCE: Obviously, a more important once you decide to you [INAUDIBLE].
SENTHIL KUMAR: Yeah, now with this one, you need to log in to the Autodesk ID-- even through the job Processor.
KIM HENDRIX: Oh, good point. So the Job Processor also has to have an Autodesk ID.
SENTHIL KUMAR: Apart from your Vault log in-- so you need to log in through the Autodesk ID.
KIM HENDRIX: Yeah. And that was new in 18.2 or 18.3 or something where the Job Processor actually has a login to Autodesk ID as well.
SENTHIL KUMAR: Yeah.
KIM HENDRIX: It's not just to grab a license, but it's for this as well.
SENTHIL KUMAR: Yeah.
KIM HENDRIX: Yeah. Any other questions? So, in our handout, we were going to talk about the other things outside of ERP connections and Fusion 360 Connections, and we opted not to do that because there's a couple of really great classes coming up that are on that. And we didn't figure we'd have time.
So these are the classes that would cover those two items. So if you have time to see-- oop. That thing is autorun. But the PDM and PLM Together is at 1 o'clock today, and Connecting the Vault with ERP-- it's just going to go back and forth-- Bills of Materials, Files, and More is this afternoon at 4:30. So those are the classes that will take care of that.
There are-- we're just going to go back and forth. There's lots of ways to connect your Vault outside of-- quit. Stop that from automatically going.
So this is connecting your vault-- I'm just going to let it go-- --to connect your Vault outside to other systems. Yes-- question.
AUDIENCE: Yeah, I was following along in your handout as you all were talking, and I think-- and I might be wrong about this-- but when we started going through Project Sync, the presentations didn't match up. There were a few things missing and that you left out that were presented here.
KIM HENDRIX: I don't know. That's all Senthil. The handout and the Project Sync that-- they don't jive?
SENTHIL KUMAR: I think it was synced.
KIM HENDRIX: Synced. [LAUGHS] Well--
AUDIENCE: [INAUDIBLE]
SENTHIL KUMAR: We will look into that.
KIM HENDRIX: We'll check-- I don't know.
SENTHIL KUMAR: We'll look into that. Yeah. [LAUGHS]
KIM HENDRIX: Do you know what is different?
AUDIENCE: There were about, I think, four or five slides when you were going through-- it was after the second slide-- the same portion when you were speaking. I have no-- I couldn't tell you off the top of my head. I just know that the two didn't jive anymore.
SENTHIL KUMAR: We'll look into that.
AUDIENCE: It picked back up.
KIM HENDRIX: Oh, it picked back up?
AUDIENCE: [INAUDIBLE] near the end of the file.
KIM HENDRIX: They were synchronizing somewhere along there.
SENTHIL KUMAR: [LAUGHS]
KIM HENDRIX: I don't know. So anyway, that's out Vault outside of your team. So any questions about anything we've covered? I will put the presentation up after this class. Yeah.
AUDIENCE: Do you find you're [INAUDIBLE] when files are out at the Fusion Team site, they are not checked out of the Vault. So they're created by the--
SENTHIL KUMAR: Fusion Team.
AUDIENCE: --Fusion Team.
SENTHIL KUMAR: Right.
AUDIENCE: At the same time, they could be checked out in any permanence on the Vault side. So you have a possible conflict there. Do you have a best practices suggestion for how to avoid that?
SENTHIL KUMAR: So you can lock down that folder, which is getting synced. Nobody can check out files from that folder. So you can log onto that folder till those collaborations are done.
AUDIENCE: Who should do that?
SENTHIL KUMAR: So the person who is syncing. So the person who is starting the sync from Vault to the Fusion Team. So you can lock it down.
AUDIENCE: [INAUDIBLE].
KIM HENDRIX: I would probably set a lifecycle state that locks it down while the collaboration is happening.
SENTHIL KUMAR: Right.
KIM HENDRIX: And that would be my transition to do it. I would set a lifecycle state that says, in collaboration or something, and I would lock it down while it's in there, and then let it go back and forth to Fusion, and then when I'm done, I would move it on to the next one. I mean, that's how I would handle it.
AUDIENCE: Like if I can keep files as I multimode because lifecycle state stays--
SENTHIL KUMAR: Released.
AUDIENCE: --turned off and released, and released to production of the lot.
SENTHIL KUMAR: Mm-hmm.
AUDIENCE: [INAUDIBLE] Fusion, I mean--
SENTHIL KUMAR: Right. So when the Job Processor user-- we should give that user permission to update that at least-- file.
AUDIENCE: So the Job Processor user--
SENTHIL KUMAR: Should have the--
AUDIENCE: [INAUDIBLE]
SENTHIL KUMAR: Yeah. And update the Release file.
KIM HENDRIX: Yeah. Your Job Processor user has to have superpowers.
AUDIENCE: [INAUDIBLE].
KIM HENDRIX: Yeah, at the release dates, and all those kinds of stuff-- anyway, to create DWFs and PDFs and Export and Import, and do all the things. And so you'd have to give it rights to the lifecycle state that you have locked out so that it has the rights to move that over. Good question.
AUDIENCE: [INAUDIBLE]
KIM HENDRIX: Well, the initial setup for sure needs to be done by an admin. Yeah, the initial setup does. Once you get those lifecycles in play, though, then the user can do the mapping, and all things would work from there, so.
Any other questions? I thought we were going to be out of time. We finished 10 minutes early. All right. Thank you.
SENTHIL KUMAR: Thank you.
[APPLAUSE]
Downloads
Tags
Product | |
Industries | |
Topics |