1 / 29

Using Autodesk® Vault for Collaboration Between Purchaser and Suppliers

Using Autodesk® Vault for Collaboration Between Purchaser and Suppliers . Driss Yammouri Senior Consultant / MFG / Autodesk Consulting. Who is Driss?. Industrial Engineer Autodesk Employee + 10 years of consulting experience Data Management, ERP Integration, … ) Visualization

alma
Download Presentation

Using Autodesk® Vault for Collaboration Between Purchaser and Suppliers

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Using Autodesk® Vault for Collaboration Between Purchaser and Suppliers Driss Yammouri Senior Consultant / MFG / Autodesk Consulting

  2. Who is Driss? • Industrial Engineer • Autodesk Employee • + 10 years of consulting experience • Data Management, ERP Integration, … ) • Visualization • Implementation • Coaching, Training • Project Management • Acting on a global basis • Based in Munich, Germany • Married, 1 Daughter

  3. Agenda • Scenarios for internal and external collaboration • External Collaboration - Overview • External Collaboration – The Workflow • Summary

  4. Scenarios for External and Internal Collaboration

  5. Example Berlin Konstruktion München Externer Dienstleister New York Vertrieb San Francisco Fertigung Los Angeles Home Office Madrid Hauptsitz

  6. Collaboration Scenarios

  7. Collaboration Scenarios München Fertigung Madrid Hauptsitz

  8. Collaboration Scenarios

  9. Webclient live

  10. Collaboration Scenarios

  11. Collaboration Scenarios

  12. External Collaboration - Overview

  13. Challenges • Easy to use • Provide data easily • Get fast access to the provided Data • Simple data import • Data and process security München Externer Dienstleister Berlin Konstruktion

  14. ...more challenges • Customer don‘t want to share his know how with the Supplier • Simplified design • Design-Envelop-Approach • Bounding geometry • Only the needed data will be provided • In best case: one part • Protection of the provided data • No unmeant modification for the source Data • Easy update scenario • Update easily changes in the design for purchaser and supplier

  15. Solutions • Direct connection via VPN • Fast internet access needed • Existing VPN access to the company network • ... • Provide data manually • Autodesk Streamline • FTP • Email • DVD • ...

  16. Solutions – Overview Direct connection via VPN Provide data manually • Access via VPN • Stable and fast VPN-connection needed • Download faster than the Upload • „External“ works like an „Internal“ • No Data-Export/Import needed • Data are always up to date • Access to all standard parts • User will have special rights and a special view (e.g. One special Folder) • Additional administrative costs • Available license for the ext. supplier? • No access to the Vault Database • Manual, deferred database update • Not so much Admin costs • Additional effort for the data export/import • Standard parts database has to be provided • Use Case: enclosed/completed design task • Rename of data is not allowed • Remove of data is not allowed • No additional license needed

  17. Completed design task Supplier Purchaser

  18. Completed design task • Demo

  19. Design changesmade by thepurchaser Purchaser Change Settings Change Copy

  20. Design changesmadebythepurchaser • Demo

  21. Supplier updates the design environment Supplier Purchaser Send back to the Purchaser

  22. Supplier updates the design environment • Demo

  23. Good To Know - Purchaser • Provide a Vault environment as database backup • Include Number-scheme, Lifecycle, Templates, etc • Provide your standard parts database • „MDF“ file can be imported via ADMS Console • Provide „local content“ (if used – see Inventor settings) • Duplicate standard parts will be recognized during data import • Define a Folder structure for the supplier • Supplier saves his data in this special folder(s). This folder could be renamed later. • A project file • Use identical workspaces • Lifecycle (release for transfer at the purchaser) • Process security and project documentation • Create a „supplier“ user • Follow which file was created, modified etc by whom

  24. Good To Know - Purchaser • Provide a Vault environment as database backup • Include Number-scheme, Lifecycle, Templates, etc • Provide your standard parts database • „MDF“ file can be imported via ADMS Console • Provide „local content“ (if used – see Inventor settings) • Duplicate standard parts will be recognized during data import • Define a Folder structure for the supplier • Supplier saves his data in this special folder(s). This folder could be renamed later. • A project file • Use identical workspaces • Lifecycle (release for transfer at the purchaser) • Process security and project documentation • Create a „supplier“ user • Follow which file was created, modified etc by whom •  Supplier keeps your CAD Standards •  Reduce time and costs by providing an „initial-package“ •  High data quality, fast and easy data export and import •  Reduce costs and improve quality by using one workflow for all suppliers

  25. Good To Know - Supplier • Document of your delivered effort using lifecycle status • Follow: what was delivered and when, which version was delivered • Which changes from the Purchaser had affected your design • Restore the purchaser backup • Detach all existing DBs in your ADMS Console (otherwise all DBs will be deleted) • Use one single „Vault“ per each purchaser • Not used Vaults can be backed up/detached • Use only the specific Vaults from that Clients you are working for • Detach all not used Vaults to keep performance • Purge your local workspace before you do an import! • Choose the „right“ project file before starting your work! • Use identical workspace structure • Important for standard parts, iParts...

  26. Good To Know - Supplier • Document of your delivered effort using lifecycle status • Follow: what was delivered and when, which version was delivered • Which changes from the Purchaser had affected your design • Restore the purchaser backup • Detach all existing DBs in your ADMS Console (otherwise all DBs will be deleted) • Use one single „Vault“ per each purchaser • Not used Vaults can be backed up/detached • Use only the specific Vaults from that Clients you are working for • Detach all not used Vaults to keep performance • Purge your local workspace before you do an import! • Choose the „right“ project file before starting your work! • Use identical workspace structure • Important for standard parts, iParts...  Use the templates and Styles from the purchaser and keep automatically his CAD-Standards  Reduce time and cost for Initial environment setup by using a Vault Backup  Security, documentation, Organisation  Use all advantages of Autodesk Vault Products like Copy Design, automatic File naming, etc

  27. Summary • Easy to use • Provide Data easily • Get fast access to the provided data • Data and Process Security • Client don‘t want to share his know how with the Supplier • Provide only needed data • Protection of the provided data • Easy update scenario

  28. Q & A

More Related