Here's a large Vault Pro customer reference site in action inc. approval process & automation

[@Neil3D]

Yea so just to repeat - if you didn't read the description, this really isn't going to be interesting to everyone! If you're not into Vault, don't care, don't want to care, fine by me and by all means just click away! This is very niche and high level intended for the benefit of engineering managers, sys admins, CAD managers or even C levels who like to get hands on and involved. Hope someone finds it of use!

[@Syrsylo]

I recently joined a small manufacturing company that has one guy using inventor for +20 years, all on a local drive, never knew what iproperties were. I was on the verge of tears how beautiful this system is.

[@ScottMoyse]

Kareem Tawil that's far too common

[@Juandv30]

Great Video. I implemented vault professional in my previous job and when I saw this video I realized that we did a good job. This is the first video showing a real life implementation. One thing I would like to learn is how “workspace Sync” works. It would be great if you can post a video showing this feature I started my own company a couple years ago and implemented Vault Basic right from the begining. Hopefully one day I will step forward into Vault professional again Thanks for taking your time to show your work!!

This is the best Vault video ever made. You are successfully painting the picture of an awesome product - something that all Autodesk resellers I have ever been in contact with are failing to do. A system configured like this is what all (?) small/medium engineering and manufacturing companies are expecting making the move to Vault for the first time, but unfortunately this is not what we get and instead the investment become very disappointing since Vault is rather stupid and dysfunctional in its vanilla state. I wonder if there is a way for someone to package this and sell a more advanced pre-configured Vault (similar to what you are showing) in order to bypass the 5 years of setup, configuration and lessons learned. I would buy it.

[@haleymanufacturinginc.9259]

Very nice! We're a small startup manufacturing company and we've been using Vault Pro for about two years now. Many of the things you've demonstrated are exactly the things that have been relentlessly filling up my "things I need to implement" list. Great to see what kind of results I can look forward to!

[@Discover-Hidden]

i liked the pace of your explaination. Other youtube teachers are too slow to keep up with my adhd focus. Thank you.

[@42designfab]

Super-useful , Neil! 18 years as a consultant, doing very much what you do . Since then, 8+ years as a small business owner trying to leverage everything I know into a small creative team. THANK YOU for sharing. It's always helpful to leverage other workflows into what we do. Keep it up and thank you much for everything you share.

[@BenjaminJamesYoung]

Interesting! I'm having to make advances in our Vault setup with how thing are moved between lifecycles, ECOs and categories and setting up rules for what's allowed and what's not. We've expanded a bit lately and now that there's more people joining our engineering team I'm finding that some people are ignoring written procedures and keep on doing so even if they've been made aware of said procedures, again ... and again. So, now it's time to get creative with Vault and put and end to the laziness! I particularly liked the BOM for a welded assemblies being a single line item. I hadn't thought of doing that before. Makes sense. Do you think using Vault for the following is a good idea: The equipment we design is rather special and is not sold onwards. We offer some very niche services and we always send our own operators with the gear out to the actual jobs. Each job we go out on is unique and always requires some sort of customisation. We almost always have to make some project specific parts, and some times have to have our tools assembled in a certain way. Or send out certain combinations of gear. We can mix and match as we please. For every job we go out on a packing list is made in a separate system with lots a data entered in manually. It's very prone to human errors. Yes, we do export lists from Vault which are accurate, but they get edited and imported somewhere else and "strange" things end up happing. (PEBKAC!) But everything we send out is in the Vault somewhere. So I figure why not use the Vault to make a packing list by using Items, and keeping using Vault as the reference? For every project we build up project specific assemblies with everything that is needed and setup as required for the project. By making items from the top level project assembly into an item we would then have the packing list for a job. Straight from the source - with very little chance of errors. I was also thinking that we could define items that are spare parts kits for the gear, which would be made by picking the appropriate parts/items from the Vault and adding them to said item along with quantity of spares. Spare parts lists also vary from job to job - either by which parts are included and/or quantity. We could for example have custom Item categories for Projects, Spart Parts Kits etc. A Project planner or manager could even build a BOM for a job using items. Doesn't need to be a CAD user. They go in, pick out the gear needed for the job, lump it all together in a Project Item and there's your packing list. (this would bypass project specific assemblies, but maybe for "simple" jobs, then that would be OK) What do you think of using the Vault like that? We should probably have Vault linked to an ERP system. I had that done at a previous workplace and it worked a treat. But haven't come so far where I'm working now - they're a bit sceptical of spending more money ... But at the same time I don't see why using Vault for this purpose wouldn't work. Or am I missing something?

[@DJScopeSOFM]

This is really awesome! I wish I could set up something similar to this but much more simplified for AutoCAD blocks and shop drawing libraries.

[@ScottMoyse]

Igor Rebenko Vault Pro + Sheet Sets is awesome

[@DJScopeSOFM]

Scott Moyse I've always used sheet sets, make my job easier, but it only goes so far. Cataloguing and automating drawings and procedures would be amazing though.

[@ScottMoyse]

Igor Rebenko oooh you've done most of the hardwork. You have to try vault Pro wth them.

[@ScottMoyse]

Igor Rebenko but I hate AutoCAD ;-) I just love the concept of sheet sets + Vault Pro. Data management goodness

[@DJScopeSOFM]

Scott Moyse, so you can get Vault for AutoCAD? Interesting, I need to check it out.

[@FTMJarra]

Local Hero, learned sh*t loads from your channel....another mega video mate, it's interesting to me, did you help set up the former sister co. vault as well.?

[@dend9566]

I wonder how do the rules for the category content center work? and are they in a life cycle?

[@dend9566]

Very help full video. Can u do a video about single compare to multi project files in Vault?

[@craigc2466]

Any guestimation at to when you may possibly do something more indepth on the topic of BOM Structure control (Normal / Inseparable / Purchased etc) & the effects on Itemisation & Item Release?

[@davidolsson]

Do you see any advantage in having the Design Data folder in Vault and from there controrl the Style Library? I've met customers using both this and the locally stored way.

[@crashfactory]

Very useful video, thanks!

[@Darren-kw4ih]

awesome video

[@kennykcheng]

Can vault basic or pro be install and use on a windows 10 home edition or does the windows has to be pro edition?

[@anonym0usplatypus]

Can you please do an in depth tutorial on weldments, pipes, and cables?

[@craigc2466]

Coincidentally just what I needed at this point in time (trying to explain Vault Basic limitations to a client company), however I have query relating to the example w'mnt you used. If the w'mnt BOM structure was set to "purchased", surely it would not allow the creation of a BOM List for the .idw, how was the BOM List created on this .idw?

[@Neil3D]

It isn't, in this case this is a good example of how a BOM and drawing parts list are two different things. For us, we buy a purchased single line item - that being the main assembly. But the IDW shows the fabricator what the design is made up of, the thickness of the plates etc but we don't put them into our BOM as we don't buy them, we buy the finished product which is a single line item. Not sure if that makes sense but this is an example of when a BOM and a parts list are very different.

[@eecr5110]

Thank you.. It was very useful

[@ScottMoyse]

Thanks heaps for this... It's nice to see the ECO process being used well.... the drawing review mechanism in those ECOs make me feel ill though. This is the first time I've seen file and item lifecycles working together happily. Are the state based security models independent? Or have you configured them to be the same and your automation is keeping it all in sync? What happens if a user tries to change an item's lifecycle state instead of the file?

[@Neil3D]

So yea all the lifecycle definitions are independent, items use their own lifecycle and then files have a different lifecycle. The automation maps the states together i.e. File WIP = Item WIP, and then if it detects a state change it syncs the other to the same state. We only have it going from file to item though, so if a file is assigned to an item, the state change must be initiated from the file... that's just a procedural thing we manage. If an item has no CAD data, state change just happens from the item. If an item changes state and it has a file, then they indeed fall out of sync and we have to step in as admins and fix the sync issue... that doesn't happen often though as staff are trained to not do that, but it can happen and it's a daily admin duty.

[@ScottMoyse]

TFI - CAD & Technology For Industry thanks for the clarity. It's handy to know what compromises are made.