Autodesk vault 软件使用说明
Autodesk Vault 备份与恢复指南说明书
Backup and Restorewith 3rd Party ApplicationsContentsIntroduction (1)Backup Software Capabilities (1)Backing up a Single Autodesk® Vault Site (1)Backup Process (1)Restore Process (1)Backing up a Full Replication Publisher (2)Back Up the Service Master Key: (2)Backup Process for the Publisher (3)Backup Process for the Subscriber (3)Restore Process for the Publisher (4)Restore Process for the Subscriber (4)IntroductionThis guide demonstrates how to use a 3rd party solution to backup and restore Autodesk® Vault.Backup Software CapabilitiesThe software used for backup should have the following capabilities:• A SQL server backup agent for backing up and restoring the databases.• Ability to restore the SQL Master and MSDB databases.• Ability to verify the backed up database or file.• Ability to work within a replicated SQL server environment.• Ability to send e-mail alerts to administrators in the event of a backup failure. (This is a suggestion, not a requirement).• Ability to back up and restore the databases and file store with security settings.Backing up a Single Autodesk Vault SiteBackup ProcessFor a successful backup, the following must be backed up:1. All vault databases: KnowledgeVaultMaster, vaults and libraries.2. All vault file stores. The file store folder is found at:C:\ProgramData\Autodesk\VaultServer\Filestore on Windows 7, Windows 8,Windows 2008 Server and Windows 2012 Server.Note: Each vault could have a unique file store location. You can find the location by selecting each vault in the Vault server Con-sole.Configure your backup software to back up the databases first then backup the file store immediately afterwards. This sequence will help keep the database information consistent with the files being backed up.Optional: You may want to backup the Connectivity.ADMSConsole.exe.config and web.config files. These files store unique settings that may not be stored in the vault databases. The files can be found in the following locations:Connectivity.ADMSConsole.exe.config - <install path>\ADMS [Edition] 20XXWeb.config - <install path>\ ADMS [Edition] 20XX\Server\Web\ServicesRestore ProcessA restore should be perform on a computer with the same name as the original computer.For a successful restore, perform the following:1. Install the Autodesk Vault server software.2. Install of the hot fixes and/or services packs that were installed on the original server.3. Restore the databases.4. Restore the file stores in there original file store location.Note: The KnowledgeVaultMaster database must be restored whenever you perform a restore of a vault. It is not recommended to restore a vault database without restoring the KnowledgeVaultMaster that was backed up with it on the same date.Post Recover Steps:1. Once all databases and the file stores have been restored, start the ADMS Console to verify all databases can be seen. If anydatabases need to be migrated, a migration dialog will appear and you should migrate the database.2. With the ADMS Console closed, open a command prompt window.3. Navigate to <installdir>\Autodesk\ADMS [Edition] 20XX\ADMS Console directory.4. At the prompt type: Connectivity.ADMSConsole.exe -VUusername -VPpassword -OvalidatefilestoreThis command runs a validation on the file store and databases This will validate all of the files in the database against the files in the file store. If any files are missing, a dialog will appear with a list of missing files. This list will also be written to the ADMS server log. To see if the command is still running, open the Windows Task Manager and look for Connectivity.ADMSConsole.exe in the Processes tab.5. If any files are missing, you can look at previous recovery points and restore the necessary files.Note: If the single site is a remote file replication site only, you can use the same back up instructions above skipping the steps that involve backing up and restoring the databases. When you install the server software, install using the remote SQL option and point to the existing SQL server.Backing up a Full Replication PublisherIn a full replication configuration it is important to back up the publisher’s vault databases as well as two of the Microsoft® SQL system databases. This section explains everything needed to perform a proper backup on the Publisher server.Replication Configuration:It is recommended that you use the following configuration to make it easier to restore a replicated environment.1. An Active Directory user account should be used for all replication credentials.2. All servers participating in the replication configuration should be in the same domain or in trusted domains.3. Run the Microsoft SQL Service under a domain user account.4. Create a script to back up the SQL Service Master Key.Back Up the Service Master Key:The service master key is the root of the encryption hierarchy in SQL Server. It should be backed up and stored in a secure, off-site location. Creating this backup should be one of the first administrative actions performed on the server.BACKUP SERVICE MASTER KEY (Transact-SQL)• Exports the service master key.Transact-SQL Syntax Conventions• BACKUP SERVICE MASTER KEY TO FILE = path_to_file ENCRYPTION BY PASSWORD = passwordArguments• FILE = path_to_fileSpecifies the complete path, including file name, to the file to which the service master key will be exported. This may be a local path or a UNC path to a network location• PASSWORD = passwordIs the password used to encrypt the service master key in the backup file. This password is subject to complexity checks. For more information, see Password Policy.Remarks• The service master key should be backed up and stored in a secure, off-site location. Creating this backup should be one of the first administrative actions performed on the server.Permissions• Requires CONTROL SERVER permission on the server.ExamplesIn the following example, the service master key is backed up to a file.• BACKUP SERVICE MASTER KEY TO FILE = ‘c:\temp_backups\keys\service_master_key’ ENCRYPTION BY PASSWORD = ‘3dH85Hhk003GHk2597gheij4’;The service master key should be backed up on a regular basis. You will need to create a Windows Task scheduled on a regular basis to accomplish this.Backup Process for the PublisherFor a successful back up, the following will need to be backed up:1. All vault databases. Knowledgevaultmaster, vaults and libraries.2. The distribution database named AutodeskReplication.3. The SQL Master and MSDB databases.4. All vault file stores. The file store folder is found at:C:\ProgramData\Autodesk\VaultServer\FilestoreNote: Each vault could have a unique file store location. You can find the location by selecting each vault in the Vault server Con-sole.5. The SQL Master Key.6. The folder where the SQL replication snap shots are located.Optional: You may want to backup the Connectivity.ADMSConsole.exe.config and web.config files. These files store unique settings that may not be stored in the vault databases. The files can be found in the following locations:Connectivity.ADMSConsole.exe.config - <install path>\ADMS [Edition] 20XX\ADMS ConsoleWeb.config - <install path>\ ADMS [Edition] 20XX\Server\Web\ServicesBackup Process for the SubscriberFor a successful back up, the following will need to be backed up:1. All vault databases. Knowledgevaultmaster, vaults and libraries.2. The SQL Master and MSDB databases.3. All vault file stores. The file store folder is found at C:\ProgramData\Autodesk\VaultServer\Filestore by default.4. The SQL Master Key.Optional: You may want to backup the Connectivity.ADMSConsole.exe.config and web.config files. These files store unique settings that may not be stored in the vault databases. The files can be found in the following locations:Connectivity.ADMSConsole.exe.config - <install path>\ADMS [Edition] 20XX\ADMS ConsoleWeb.config - <install path>\ ADMS [Edition] 20XX\Server\Web\ServicesNote: Each site should backup there file store folders regularly. This is very important if you are not replicating the entire file store to a single backup location.applied to the original computer.1. Restore the SQL MSDB and Master databases.2. Restore the AutodeskReplication, KnowledgeVaultMaster and each vault and library database.3. Restore the file stores in there original file store location.Note: The KnowledgeVaultMaster database must be restored whenever you perform a restore of a vault. It is not recommended to restore a vault database without restoring the KnowledgeVaultMaster that was backed up with it on the same date.4. Create the shared folder for the SQL replication snapshots. Apply all user security on the folder and share it.5. Restore the files and sub-folders for the SQL replication snapshots folder.Post Recover Steps:1. Once all databases and the file stores have been restored, start the ADMS Console to verify all databases can be seen. If anydatabases need to be migrated, a migration dialog will appear and you should migrate the database.2. With the ADMS Console closed, open a command prompt window.3. Navigate to <installdir>\Autodesk\ADMS 20XX\ADMS Console directory.4. At the prompt type: Connectivity.ADMSConsole.exe -VUusername -VPpassword -OvalidatefilestoreThis command runs a validation on the file store and databases. This will validate all of the files recorded in the database against the files in the file store. If any files are missing, a dialog will appear with a list of missing files. This list will also be written to in the server’s console log. To see if the command is still running, open the Windows Task Manager and look for Connectivity.ADMS-Console.exe in the Processes tab.5. If any files are missing, you can look at previous backup and restore the necessary files.applied to the original computer.1. Restore the SQL MSDB and Master databases.2. Restore the KnowledgeVaultMaster and each vault and library database.3. Restore the file stores in there original file store location.Note: The KnowledgeVaultMaster database must be restored whenever you perform a restore of a vault. It is not recommended to restore a vault database without restoring the KnowledgeVaultMaster that was backed up with it on the same date.Post Recover Steps:1. Once all databases and the file stores have been restored, start the ADMS Console to verify all databases can be seen. If anydatabases need to be migrated, a migration dialog will appear and you should migrate the database.2. With the ADMS Console closed, open a command prompt window.3. Navigate to <installdir>\Autodesk\ADMS 20XX\ADMS Console directory.4. At the prompt type: Connectivity.ADMSConsole.exe -VUusername -VPpassword -OvalidatefilestoreThis command runs a validation on the file store and databases. This will validate all of the files recorded in the database against the files in the file store. If any files are missing, a dialog will appear with a list of missing files. This list will also be written to in the server’s console log. To see if the command is still running, open the Windows Task Manager and look for Connectivity.ADMS-Console.exe in the Processes tab.5. If any files are missing, you can look at previous backup and restore the necessary files.Important Things to Know:It is very important to restore within the default 14 day retention period. If you are restoring a subscriber, the backup used for the restore process must not be older than 14 days. If you do not have a backup within the 14 day retention period, you must delete the subscriber’s workgroup in the ADMS Console on the publisher and recreate it. If you are restoring the publisher, the backup used for the restore process must not be older than 14 days from the last synchronization date of all subscribers.Autodesk and Autodesk Vault are registered trademarks or trademarks of Autodesk, Inc., and/or its subsidiaries and/or affiliates in the USA and/or other countries. Microsoft is either trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. All other trademarks are the property of their respective owners. All other brand names, product names, or trademarks belong to their respective holders. Autodesk reserves the right to alter product and services offerings, and specifications and pricing at any time without notice, and is not responsible for typographical or graphical errors that may appear in this document. © 2014 Autodesk, Inc. All rights reserved.。
Autodesk Vault API学习与应用指南说明书
HOW TO INSTALL? VDF binaries are provided as part of the SDK installation!
Creating and Manipulating Vault Objects With PowerShell
WHERE TO FIND THE INSTALLED SDK BINARIES
Note: for older SDK installations, you may find the files installed to your Program Files (x86) directory.
Installing Visual Studio
o Note, for older year versions, the licensing binary is named as clmloader.dll
For PowerShell, we can copy this binary to C:\Windows\System32\WindowsPowerShell\v1.0, which is where the PowerShell executable lives.
Getting Started
1. Creating a new PowerShell project in Visual Studio 2. Loading the Vault Web Services Assembly 3. Connecting to a Vault with PowerShell 4. Calling Vault Web Services
FRAMEWORK (HANDY HELPERS)
Autodesk Vault SQL Cluster 配置指南说明书
Autodesk®VaultSQL Cluster Configuration for Autodesk Vault ServerContents Introduction (3)Purpose (3)Example (3)Configuring SQL Failover Cluster Instances (4)Add a SQL Server Node (12)Installing Autodesk Vault (16)Verify Failover Failover (17)IntroductionThis document is a guideline on how to configure Microsoft SQL Server as a cluster to work with Autodesk Vault server. This document does not cover best practices for SQL Server or the cluster configuration. Autodesk recommends consulting with Microsoft’s documentation for configuration and best practice details.PurposeAutodesk Vault functions in a SQL failover cluster configuration in which it is unaware of the cluster and does not requirereconfiguration of Vault if and when a failover occurs. This is known as the AlwaysOn Failover Cluster Instances (FCI). Moreinformation about this configuration can be found at AlwaysOn Failover Cluster Instances . Before configuring this feature, Windows Server must be configured for Windows Server Failover Clustering (WSFC). This document does not cover this configuration; please refer to Microsoft’s documentation.ExampleThis document illustrates the following configuration.Domain Controller SQL Server(SQL1)SQLVault Server dk SQL Server(SQL2)SQLCluster StorageConfiguring SQL Failover Cluster InstancesOnce the Windows is configured as a Windows failover cluster for SQL, it is time to install the Microsoft SQL Server software.1. Insert the SQL Server installation media in the first SQL Server (SQL1), and from the root folder, double-click Setup.exe.2. The Installation Wizard starts the SQL Server Installation Center. To create a new cluster installation of SQL Server, click NewSQL Server failover cluster installation on the installation page.3. The System Configuration Checker runs a discovery operation on your computer. To continue, Click OK.4. To continue, click Next.5. On the Setup Support Files page, click Install to install the Setup support files.6. The System Configuration Checker verifies the system state of your computer before Setup continues. After the check iscomplete, click Next to continue.7. On the Product key page, indicate whether you are installing a free edition of SQL Server, or whether you have a PID key for aproduction version of the product.8. On the License Terms page, read the license agreement, and then select the checkbox to accept the license terms andconditions. Click Next to continue.9. On the Feature Selection page, select the following components for the installation. Click Next to continue.10. On the Instance Configuration page, type a name in the SQL Server Network Name field. This name is used to identify theSQL Server failover cluster. Select the Named Instance and type AutodeskVault in the Named Instance field. Click Next.11. Use the Cluster Resource Group page to specify the cluster resource group name where SQL Server virtual server resourceswill be located. Click Next to continue.12. On the Cluster Disk Selection page, select the shared cluster disk resource for your SQL Server failover cluster. The clusterdisk is where the SQL Server data will be located. More than one disk can be specified.Click Next to continue.13. On the Cluster Network Configuration page, specify the network resources for your failover cluster instance:Network Settings — Specify the IP type and IP address for your failover cluster instance.Click Next to continue.14. On the Server Configuration — Service Accounts page, specify login accounts for SQL Server services. If more informationon configuring service accounts - see Server Configuration - Service Accounts. Click Next to continue.15. On the Database Engine Configuration page on the Server Configuration tab, select Mixed Mode and type the password thatwill be used for the system administrator (SA) account.16. On the Data Directories tab, specify the location of the database files. Click Next to continue.17. Continue through the remaining pages to complete the installation.Add a SQL Server Node1. Insert the SQL Server installation media in the first SQL Server (SQL1), and from the root folder, double-click Setup.exe.2. On the Cluster Node Configuration page, select the Cluster Network to join. Click Next to continue.3. On the Cluster Network Configuration page, specify the network resources for your failover cluster instance:Network Settings — Specify the IP type and IP address for your failover cluster instance.Click Next to continue.4. On the Server Configuration — Service Accounts page, specify login accounts for SQL Server services. If more informationon configuring service accounts - see Server Configuration - Service Accounts. Click Next to continue.5. Continue to click Next to complete the installation.Installing Autodesk Vault1. On a separate server on the network, insert the Vault Server and run the Setup.exe.2. On the Server Configuration page, configure the installation for a remote SQL server and enter the SQL Server Network Nameof the Cluster.3. When using a remote SQL instance, a shared network folder is required as a transition area between the SQL instance andthe Autodesk Data Management Server. The shared network folder can be located on the same computer as the SQLinstance or a different computer and must be accessible by both the data management server and SQL. The spacerequirement for the shared folder is equal to the total of all database files. Choose a location with sufficient space andperformance. Enter the UNC path to the shared network folder or click Browse to locate the shared folder on the network.Note: Both the user account under which the Autodesk Vault Server is running as well as the user account under which the SQL instance is operating need read/write access to the shared network folder.4. Complete the installation and start the Vault Server console to create a vault.Verify Failover1. Launch the Failover Cluster Manager and select the Roles node.2. Right-click on the Roles node and click Move -> Select Node…3. Select the SQL2 server or second node and wait for the failover to complete.4. Launch the Vault Server console and verify that Vault is still functioning correctly.Autodesk [and other products] are registered trademarks or trademarks of Autodesk, Inc., and/or its subsidiaries and/or affiliates in the USA and/or other countries. All other brand names, product names, or trademarks belong to their respective holders. Autodesk reserves the right to alter product and services offerings, and specifications and pricing at any time without notice, and is not responsible for typographical or graphical errors that may appear in this document. © 2016 Autodesk, Inc. All rights reserved.。
Autodesk Vault Data Standard教程简介与Read Me说明书
Vault Data Standard – TutorialIntroduction and Read MeAbout Autodesk Vault Data StandardVault Data Standard is a data control feature helping users capturing design relevant information in a standardized format during the data entry process in Vault Client, Inventor, and AutoCAD.For Vault Explorer Data Standard extension adds new commands to create files or folders, and additional tabs to the detail view. All user interface elements are customiz able to match your company’s requirements for standardization.The AutoCAD and Inventor extensions of Vault Data Standard subscribe to the save event and display a customizable Save New File dialog. Both CAD extensions add additional commands to edit file metadata and to create file copies based on customizable rules.We use the acronym VDS to shorten the full name V ault D ata S tandard in all episodes of this tutorial collection. About this TutorialThis course targets Vault key users and Vault Administrators getting started with Data Standard customization. VDS offers several options to customize the behavior by enabling options in Vault Behavior Configuration, e.g., Vault Numbering for Projects. Other customizations require editing of VDS configuration files, like Dialog definitions or PowerShell scripts reflecting the business rules and user guidance handling file’s metadata.Advanced customizations, like dialog extensions by additional user controls or tabs, require more skills in creating Dialogs (Windows Presentation Foundation) and in writing PowerShell scripts using direct Vault API (Application Programming Interface) calls. This Tutorial does not cover any advanced topics. However, the transition from Chapters 10 onwards to more in-depth scripting relates to each student’s ambitions and interest in learning programming concepts.VDS Tutorial - System Requirements•Autodesk Vault Workgroup or Professional 2020.2 or newer, Client and Server in the English language. For non-English Server environments note the additional step preparing the tutorial environment in chapter 1 •VDS Installation 2020.2 or newer, Default Configuration, en-US. Follow these steps to install the extension: Install Vault Data Standard•XML Editor. We recommend using an XML Editor rather than a text editor to edit the VDS configuration files following the Tutorial’s exercises. Select any XML Editor of your preference. This tutorialdocumentation used the Microsoft Visual Studio Code Editor.•PowerShell Editor. Windows 10 operating system includes a PowerShell ISE to edit and format PowerShell script files. Other editors like Visual Studio Code with PowerShell Extension are suitable as well.Setup your Environment1.SoftwareInstructor and Students – Client Machine:-AutoCAD or AutoCAD Mechanical, release 2020 or newer-Inventor Professional, release 2020 or newer-Vault Workgroup or Vault Professional, release and update 2020.2 or newerAll client’s installa tions are in English; Chapter 08 requires an additional Language Packs installed for each client; the documentation uses German language packs for all clients in this chapter.Instructor and Students need to have access to a Vault Server:-Autodesk Vault Server Workgroup or Professional, release 2020 or newer, English2.New Vault –VDS TutorialOn ADMS create a new Vault of the name VDS Tutorial while using the Manufacturing Configuration as shown below:This Tutorial requires an English Vault configuration. In case your ADMS server is localized (the pulldown list displays localized configuration names), navigate to the subfolder en-US to select the English configurationtemplate:3.Training FilesDownload, extract, and import all training files required to follow the practical exercises of this Tutorial.The download is available in the attachment section of the AKN Articlehttps:///community/article/3021211.Create the folder C:\VDS Tutorial\2.Open the Zip-Archive and extract each subfolder as follows:a.Extract all subfolders and files of ..\Vault Files\ to C:\VDS Tutorial\:b.Extract all subfolders, files, and Zip-Archives of ..\VDS Configuration Files\ to a location of yourchoice – but use a different location than C:\VDS Tutorial\.3.Allow adding CAD files to Vault Explorer for the Vault VDS Tutorial (The training files include templatefiles for Inventor and AutoCAD):4.Drag & Drop the extracted Training files to the root folder:5.Re-enable the option Disable Check-in of Design Files:6.Set Working Folder Options as shown below:7.To better compare screenshots of the documentation with your environment, we recommend enablingthe client option (Tools -> Options) Show working folder location:4.Configure AutoCAD/AutoCAD MechanicalStudents will create new drawings during exercises consuming the templates added before; configure AutoCAD Template Options to use these:For AutoCAD:For AutoCAD Mechanical:You may also use the AutoCAD templates in AutoCAD Mechanical; the title block definition is different. AutoCAD templates use MText fields mapped to file properties, whereas Mechanical drawings apply title blocks with block attributes. Chapter 04 – Save New and Edit Files in AutoCAD talks you through the decision criteria more in detail.5.Configure InventorInventor by opening the project file Designs.ipj from Vault while refusing the check-out option:With the project file enabled, Inventor is all set to follow the exercises for Inventor starting in Chapter 05.6.Configuration Files – Setup EditorWe recommend using the same Editor as shown in Videos and Exercise images for editing xml, ps1, xaml, and text files.Download and install Visual Code from https:///. After installation, add the PowerShell extension within the Editor:First Insights on Data Standard Configuration FilesGet a sneak peek on the VDS client configuration files. The configuration for all VDS client applications Vault Explorer, Inventor Vault, and AutoCAD Vault install into all users’ Program Data files. The path relates to the Vault version installed; the tutorial documentation uses Vault 2020, for later versions update the version number in the path, respectively.C:\ProgramData\Autodesk\Vault 2020\Extensions\DataStandardAccess all folders and files using VS Code Editor:Instead of editing the default configuration files in the Autodesk VDS default folders, you should copy the file before to the *.Custom folder structure and edit there. Data Standard extensions read all available configuration files during the start-up of the application and will prefer custom files as they exist.Note – Multi-language support definitions are stored in the subfolders named according to the locale/language code. Autodesk default and customized configuration use these in common. Your company configuration backup needs to include all language definitions and client language packs applied plus the *.Custom\*.* configuration files as a minimum.See also Help: Data Standard Configuration。
vault的基本使用方法
vault的基本使用方法Vault是一个用于安全地存储和访问敏感数据的开源工具，旨在为应用程序和基础设施提供一种统一的方式来管理访问凭据和机密信息。
以下是关于Vault基本使用方法的详细说明。
一、安装Vault二、初始化Vault初始化Vault是开始使用它的第一步。
运行以下命令以初始化Vault：```$ vault operator init```该命令将生成一个包含五个初始解密密钥的初始化密钥集。
保存好这些密钥是非常重要的，因为它们将在以后的步骤中用于解密Vault的主密钥。
同时，Vault还生成并显示一个根令牌。
根令牌是最高权限的令牌，因此需要妥善保管以防止未经授权的访问。
三、解封VaultVault在初始化后处于封锁状态，需要进行解封才能正常使用。
运行以下命令以解封Vault：```$ vault operator unseal```根据初始化密钥集中的其中三个解密密钥来解封Vault。
Vault保持解封状态的时间是有限的，当过了一定时间后，Vault将会自动重新封锁。
因此，您还需要定期运行解封命令来保持Vault的可用状态。
四、登录并创建访问令牌使用根令牌登录Vault，然后创建一个用于访问Vault资源的令牌。
运行以下命令以登录Vault：```$ vault login <root_token>```其中，<root_token>是Vault初始化时生成的根令牌。
登录成功后，您将获得一个临时令牌，该令牌在一定的时间后会自动过期。
运行以下命令以创建一个访问令牌：```$ vault token create```创建成功后，您将获得一个新的令牌，该令牌将用于访问Vault的资源。
五、创建和读取机密Vault的一个主要功能是存储和管理敏感数据，例如API密钥、数据库凭据等。
您可以使用Vault的KV（键值）存储引擎来创建和读取机密。
首先，需要启用一个KV存储引擎：```$ vault secrets enable -path=kv kv```然后，可以使用以下命令将机密存储到Vault中：```$ vault kv put kv/my-secret username="admin"password="secretpassword"```在上述命令中，kv/my-secret是存储机密的路径，username和password是要存储的键值对。
Autodesk Vault配置（第一部分）说明书
MFG219615 –Autodesk Vault Configuration Part 1 Chris BennerCAD Supervisor –Powell Fabrication & Manufacturing, LLC Mark LancasterProduct Support Specialist–Synergis Engineering Design SolutionsClass DescriptionNow that you have purchased one of the Vault products, you need to get the environment set up for you and your users. This class will look at what to do once the Vault Server has been installed. We will discuss topics such as creating users and groups, setting up permissions and security, establishing projects and working folders, and getting your CAD content into the Vault itself.Key Learning Objectives•Learn how to create users and groups within Vault•Learn how to establish user and folder permissions to protect your data •Learn how to set up projects and establish working folders•Learn how to move locally stored CAD data to the VaultAbout Me: Chris Benner▪CAD Supervisor @ Powell Fabrication & Manufacturing, LLC. St. Louis, MI USA▪20 Plus years CAD experience, 10 years with Inventor▪Autodesk Expert Elite▪Dad, husband. Fan of American football, music, craft beer, good scotch and an occasional cigar, semi professional photographer.Home:About Powell Fabrication & Manufacturing, LLC▪Board drafting –Yes I’m old▪20+ yr MFG/CAD world▪15+ yr 3D CAD▪CAD/Doc Mgmt Admin About Me: Mark Lancaster▪Autodesk Partner/Synergis EDS ▪Quakertown PA ▪MFG/Vault Products▪Installation▪Licensing/Subscription Support▪Autodesk▪Expert Elite▪Certified Inventor Professional▪I&L and Inventor Forum▪Lean MFGCongratulations!Now That I Have Vault,… WhatDo I Do With It?•We Are Assuming It Has Been Installed•Our Presentation Centers on Vault Professional•We Will Start with Roles & Permissions, Users & Groups •Time is Short for this material so, if time permits we will then: o Run Through the Config Options –Sooo Many Optionso Talk About Adding Data to the VaultVault Settings & ConfigurationLaying the foundation for your Vault AKA: Roles, Users, Groups, and PermissionsA poor (Vault) foundation may perhaps lead to this over time.RolesWhat are Roles?•Assigned –Vault user or group of users •Pre-defined•Function ability•Lowest form of security•Useful →Vault Basic•Mandatory/Entry pointPre-defined RolesVault AdministratorPre-defined RoleDocument Editor (level 2)Pre-defined RolePermitted Functionswithin VaultOverlapping AbilitiesDocument Editor (Level 1)Defined functionsDocument Editor (Level 2)Level 1 + highlighted functionsUser assigned both roles?Lowest role is winnerHighlighted functions no longer permittedAdditional Info•Global vault setting•Vault level•Vault Pro 2018 –New vault admin roles •Vault Pro 2019 –Custom role •SpreadsheetRoles & PermissionsVault Workgroup/Pro only•Role Based Permissionso1st level permissions•ACL and State Permissionso2nd/3rd level permissions•Balancing point•Why it’s importantRoles & PermissionsVault Workgroup/Pro only•User/Administrator roleo Access to all vault functions•ACL Permissions appliedo Per vaulted fileo Deny modify/delete access I’m the VaultAdmin I can do anything I like within VaultWell I’m the Engineering Manager and I don’t want you to modify or delete our Area 51 CAD filesVault User Accounts/User ManagementVault Users Accounts•Entry point•Static Vault Accounto Vault Admin & Guest provided •Active Directory Domain Accounto Vault Pro Only•Global Setting•Special Accounts As a group we’re so happy & excited about our Vault andhow it’sconfiguredVault Administrator -Static•Administrator →Account name•Blank password →Change it •Disable?•Designate 2 Vault Admins•Separate user/admin account•IT Group/Train•DON’T LOCK OUT ADMINGuest -Static•Guest →Account name •Blank password•Disabled•Not a fanWARNINGBefore jumping in and creating any Vault Accounts and Groups make sure you have a plan in how this will be accomplished. Once a Vault Account or Group is created it is unableto be removed.Modifying, disabling or promoting/demoting isonly permittedStatic Account -Creation•ADMS Console/Vault Client•Vault Administrator•Mandatory Field•Need Role/Vault Access•Enable/Disable•Vault Admin/User managedStatic Account -Creation•Active Directory Account•Credentials/Windows Log in•Account Update•Managed →Active DirectoryActive Directory Domain Account Vault Professional Only•Vault Admin/Importso ADMS/Vault Cliento Involve IT support•Exist? Link?•Define →Vault AdministratorActive Directory Domain Account Vault Professional OnlyStatic vs Active Directory Domain Account Vault Professional Only Active Directory Domain Account (imported)Domain Server Name Domain Account Name Static Vault AccountVault Groups/Group ManagementVault Groups•An Extension for Users •Optional•Useful/Same Configuration •Static Group•Active Directory Domaino Vault Pro Only•Global Setting (YES/NO)Vault Group -Creation •ADMS Console/Vault Client•Vault Administrator•Group to Group assignment•Vault Admin managedVault Group -CreationActive DirectoryDomain Group•Active Directory Group –IT/Network/Permissions •Import →Vault Admin•Defined (in Vault) →Vault Admin•Managed →IT/Network•Exist? Link?•Auto-Create Account•Manual update•Not a fanMixing Roles, User’s, Groups & AccessVDB1VDB2Vault ServerRolesGroup AVault User Group B Group CVault Permissions (Vault Workgroup/Pro)Permissions –Why its ImportantVault User Doc EditorLVL 2Access to delete files across Vault ConditionalVAULT BASIC ONLY Conditional delete means there’s no relationship exist atthis timePermissions –Why its ImportantVault User Doc EditorLVL 2Access to delete files across Vault ConditionalVAULT WORKGROUP/PROPermissions –3 LevelsLifecycle State PermissionHighest Level of PermissionAccess Control List (ACL) PermissionObject Based SecuritySecondary Level of PermissionRole or Role Based PermissionLowest Form of PermissionPermissions –Role BasedProvide access (light switch) to perform certainfunctions within VaultPermissions –ACLVAULT WORKGROUP/PROControl access that’s granted by the assigned vault rolePermissions –Lifecycle StatePer Lifecycle State, Restrict access that’s granted by the Role/ACLPermissionWIP In ReviewVAULT WORKGROUP/PROPermissions –Access Control List (Vault Workgroup/Pro)ACL PermissionsVAULT WORKGROUP/PRO •Per Vault•Vault Administratoro Security Administrator (2018)•RMC Folder/File/Details/Security •READ/MODIFY/DELETE •Allow: Grant access•Deny: Deny access•Blank/None: Nether Grant/DenyACL PermissionsVAULT WORKGROUP/PRO •Start @ Vault Root •Propagate permissions•Don’t forget Admino Cloaking to resolve •Override if neededo Lower structureo@ file level•Don’t swing for the fences •Remove later onLowest Permission WinsUser is assigned Doc Editor LVL 1Role doesn’tallow files tobe deletedACL Permissiongranted todelete filesRolelimitationstill winsACL PermissionVault PermissionsPermissions –Effective AccessVAULT WORKGROUP/PRO•Vault 2016/2017 Release •Folder or File Level•What’s really happening •Obj Based, State, Effective •One time checkACL Permission –Effective Access。
Vault 基本设置和应用
如果企业里，已经有域账号，则可直接导入使用，而且导入的账号和域账号之间保持关联。这样可 以避免维护额外的账户，登陆的时候也非常方便。
小技巧
在导入账号的时候，可以选择“Location”, 选择群组导入，也可以 输入显示名（名+姓， 如Kelvin Hao), 通过 Check Name，找到预账号。 导入的预账号如果不需要了可以删除（ demote) 对于非预账号，目前可以编辑，但不能删除
Web Client
Vault web client是通过IE浏览器登陆Vault进行文件搜索，查 看，打印等操作的一个模块。这个功能只有在Vault Collaboration 和Vault Professional中有。默认情况下， Web Client只能在局域网中使用，只要应用对象需要查看图纸 的是车间人员，施工人员等。
如何访问Vault
基本知识
数ቤተ መጻሕፍቲ ባይዱ管理模式介绍
在客户端，可以利用已有账号登陆Vault. 但在登陆前要确保Vault 服务器和客户断都已经正确安 装，而且License已经配置好。 对于Vault Professional 2011, License和AutoCAD的网络版license管理方式相同。既购 买多少个license, 则并发数就有多少个。 独立的Vault客户端，和应用程序中的add-in都会消耗license, 但Web client则不消耗 license.
Autodesk Vault服务器
命令菜单
数据管理模式介绍
数据库概要
快速入门 数据仓库
库文件
日志
站点信息
资源信息
Autodesk Vault服务器
利用Vault服务器可以进行的常用操作 ：
Vault基本设置和应用
Autodesk Vault客户端
命令菜单 工具面板 浏览树 我的工作
列表
快捷键 工作面板
选项卡 预览面板
状态信息
数据管理模式介绍
主面板
属性面板
客户端的种类
数据管理模式介绍
客户端 Autodesk Vault Vault 插件
Web Client
描述
主要优势
Autodesk Vault 是一个用于查看、搜索Vault中文件和数据， 独立应用程序，功能丰
小技巧
1，如果已经导入域账号，则选中 “ windows authentication, 则系统会自动填 写账号和密码
11，选
如何访问Vault
数据管理模式介绍
基本知识
如果企业里，已经有域账号，则可直接导入使用，而且导入的账号和域账号之间保持关联。这样可 以避免维护额外的账户，登陆的时候也非常方便。
小技巧
在导入账号的时候，可以选择“Location”, 选择群组导入，也可以 输入显示名（名+姓， 如Kelvin Hao), 通过 Check Name，找到预账号。
以及对Vault进行管理和设置的独立的应用程序。需要安装后才 富，性能稳健，和
能使用。
Outlook界面非常像，
因而交互性好，易学易
用。
Vault 插件是将Vault的功能和其他的应用软件紧密集成的组件。 和设计软件和办公软件
利用它们可以登陆或者登出Vault, 将文件检入或者检出Vault, 紧密集成，使设计人员
独立的Vault客户端，和应用程序中的add-in都会消耗license, 但Web client则不消耗 license.
1
2
Autodesk Vault 软件使用指南说明书
Increase your BIM workflow productivity and quality using Vault custom applicationsDarius ŠimkūnasBIM & Application strategist –collaboration platformsMagnus SvenssonBIM & Application strategist –Autodesk CivilAbout the speakerDarius SimkunasDarius Šimkūnas is the BIM & Application strategist at Tyréns AB. He focuses on collaboration platforms and Autodesk Civil products. Darius has over 15 years of experience with Autodesk, Inc. products, consulting and training employees. He was an Autodesk University speaker in 2013, 2014, 2015 and 2016. He has been working with AutoCAD Civil 3D software since 2005 and has a portfolio of functionalities for specific regional and company needs. He is an AutoCAD Civil 3D Certified Professional, has been a member of the Autodesk Developer Network (ADN) since 2008, and he has been working on infrastructure projects using new technology and methodology. Since 2012 Darius has been responsible for implementation of Vault software. As a project manager, he directly participates in the stages of implementation, resolution of strategic and technical issues, and product functionality enhancement according to the company's needs.About the speakerMagnus SvenssonMagnus Svensson is BIM and application strategist with focus on Autodesk civil products. He has been working on the development of functionalities and working methods in AutoCAD Civil 3D and Infraworks, holding educations and acting as BIM and application strategist and advisor in large infrastructure projects. Magnus is engaged in Swedish and international network for developing Civil 3D and Infraworks. He has special skills in parametric sections for corridor design in Civil 3D and 25 years of experience from different areas of civil design and IT management in large organizations.Agenda•About Tyréns•Introduction to a future standard of a Vault project•VDC/ICE/BIM workflow optimization –real project example •Sharing Vault outside the company network•Expanding Vault possibilities with API•Integrating Vault with other systems, ensuring project quality •Automating processes using Job servers•Automate automated processes using schedulers •QuestionsGeneral information on Tyréns Founded in 1940.One of Sweden's leading multi-disciplinary consultanciesSpecialists in urban planning and infrastructure2,700employees across Sweden, Denmark, the UK, Lithuania and Estonia Offering custom solutions for sustainable developmentPart of the international network SEEN with 6,000 expertsMost frequently used design software:•Autodesk AutoCAD, Civil 3D, MEP•Autodesk Revit•Autodesk Navisworks•Tekla•Bentley Microstation,Power Civil / Rail Track, PW•Bentley Navigator•Esri ArcGIS•Autodesk Vault Pro•…How Tyréns AB optimizes VDC/ICE/BIM processes with Vault API and integrations with other applications –a real project example!Bypass Södertörn•Vault use since early-2016•Stage–preliminary design•New road length –20 km (12.5 miles)•3+3 lanes highway• 3 main tunnels, length –over 5 km (3 miles)•Up to 100 new bridges and overpasses•About 25different disciplines involved in the project•About 400engineers from different disciplines working on the project •About 15different subcontractors using Vault live from Sweden and abroad •Customers use Vault for documents and model review.•…Bypass Södertörn statistic in Vault•~17,000 files.•~120 GB, latest versions only.•~4,000 DWG files including 2,500models.•~4,000Civil Data references includingover 2,000shared surfaces•VDC/ICE working process •ICE meetings and coordination models update once a week•Model base delivery with drawings •Classification system demands•Full team/project transparency for the client:o access to the live modelo time reportso progress stageo meeting notes, etc.•The client is part of the team with a special role.Project demandsOnce a week!Once a week!Improving BIM workflow. How to make a BIM model live?What we need to get a live BIM model? Data/Modelmanagement•Single source of data24/7Cross-discipline collaboration •Effective collaboration between disciplinesClassification system •Clear and easy to use automated controlProcess automation •Automate processes, avoid errors, ensure data relevancyCODESData management –the entire project in a single place*BIM model location –VaultBIM model*ProjectOffice 1Office 2Office 3CustomerDMZPartnersDMZSharing data with external partners and the client•ADMS server on DMZ allows sharing Vault using the https protocol for external users in a secure way•External partners work with Vault the same way as internal users•We are using Vault to share templates, configurations files, etc.•The Client can access the live model 24/7.Coordination model –Navis worksSource of informationCoordinationmodelLink to live modelAutoCovertManualCovertCoordination model is not the final result, but a live source of information to make decisions and progress•Main source of information for liveCivil 3D surfaces, alignments,corridors, pipe networks.•CAD 3D objects•CAD 2D objectsWhat we need to have a live BIM model?Datamanagement •Single source of data24/7Cross-discipline collaboration •Effective collaboration between disciplinesClassification system •Clear and easy to use automated controlProcess automation •Automate processes, avoid errors, ensure data relevancyCODESCross-discipline collaboration –Level 1 RoadsBridges Pipes Landscapes TunnelsCivil 3Dmodel filesEmpty file withSurface DrefsEmpty file withCorridor Drefs Surface DREFAlignment DREFPipe network DREFCorridor DREFBIM workflowExisting GroundsurfaceRock surfacePipe networkRoad AlignmentProfileRoad Corridor,Top, BottomsurfacesBridge Corridor,Top, Bottom surfacesRoad Corridors DREF’s fileBridge Corridors DREF’s file Road Surfaces DREF’s fileBridge SurfacesDREF’s fileCoordination modelDrawings, PDFDREFDREF DREFDREFDREFDREFDREFDREFDREF DREFDREFExport DataLive linkMain alignment file is used in 4,747files/objectsExisting Ground or Rock surface input dataLaser scanMeasuredinformationDrill, scaninformationAutomatic Civil 3Dsurface creationCivil 3D Surface Live Model collaborationCivil 3D modelsOthersoftwareprovidermodels2D CAD objects(lines, polylines)3D CAD objects(3D polylines,Mesh, solids,surfaces)XML, IFCAutomatic Civil3D models exportWhat we need to have a live BIM model?Datamanagement •Single source of data24/7Cross-discipline collaboration •Effective collaboration between disciplinesClassification system •Clear and easy to use automated controlProcess automation •Automate processes, avoid errors, ensure data relevancyCODESClassification system –CodesSQL database API engines allow integrations from different softwareAPIInput information fromdifferent sources (.csv)Classification system and ICE meetingsK-32CD--EZN1--14G-01How to explain what it is to everybody in the meeting room?Classification system and TyrEngineTyrEngine is a unique platform forvisualizing sustainable spatialplanning. By combining advancedgraphics techniques from theworld of gaming, a 3Denvironment is produced thatdemonstrates the results andimpacts of projects in spatialplanning, property and industrialdevelopments.What we need to have a live BIM model?Datamanagement •Single source of data24/7Cross-discipline collaboration •Effective collaboration between disciplinesClassification system •Clear and easy to use, automated controlProcess automation •Automate processes, avoid errors, ensure data relevancyCODESExpand Vault possibilities with APIVault API possibilities1. Vault client functionality •Additional functionalities of Vault client (properties tab, copy attribute values, etc.)2. Event handler •Automatically run functionalities on specific events(Check in, Move, delete, etc.)3.Vault + Civil3D,Excel, etc.•Vault initiates third applications and runs commands4. Job server•Run user initiated functions on a Job server(publish to PDF, Export C3D file to AutoCAD, etc.)5. Scheduledjobs •Scheduler runs jobs automatically without user inputVault client functionality•Smart properties tabo File name was encoded inCodes and values checkedo Using a special option valueswill be updated by CodesstandardVault client functionality•Update multiple file propertieso You can select one file as a baseand copy values to other fileso If the file name conforms to theClassification system standards,encoded attribute values will beupdated by CodesVault client functionality•Deleting multiple folderso You can delete more than onefolder at onceo Important! Do not give regularusers access to this function.Administrators only!o Ask for approval to deletedisplayed folders.Vault client functionality•Visual life cycle•Special thanks to DOUG REDMOND•Code example can befound athttp://justonesandzeros•New file from a templateo Select a template stored in theVaulto Create a file name by selectingvalues from the list (values from Codes database)o Attributes will by filled inautomatically•Safe deletion of files/folderso Regular users do not have the right todelete fileso Using a dedicated command files arerenamed to _delete by an admin usero If the file is used, an error messageinformation will be displayed.o_delete files are downloaded and backed up before automatically deleted fromVault.•Copying files with attribute values (taking values from a source file or a destination folder)•Getting user information about who is using your file even if you do not have access to that file •Write an e-mail directly•Creating users in Vault even you are not an administratoro Select an internal user or create an external oneo Select groups to addo Select projects to addo No possibilities to add to Admin groups and other restrictionsVault API possibilities1. Vault client functionality •Additional functions to Vault client (properties tab, copy attribute values, etc.)2. Event handler •Automatically run functions on specific event (Check in, Move, delete, etc.)3.Vault + Civil3D,Excel, etc.•Vault initiates third applications and runs commands.4. Job server•Run user initiated functions on a Job server(publish to PDF, Export C3D file to AutoCAD, etc.)5. Scheduledjobs •Scheduler runs jobs automatically without user input.•Folder creation controlo Fixed/controlled folderstructureo Regular users can createfolders only in _Tempo Illegal actions will beforbidden•Adding new fileso Set a parent folder category toa file automaticallyo Copy parent folder propertyvalues to a file automatically Folder category Properties values•Checking-in fileso Inform users that CAD filesmust be checked-in with CAD application integration.o Store illegal check-ins indatabase for administratoranalysis•There is a list of events to catch•What you need to Automate?Process automatization -Vault API1. Vault client functionality •Additional functions to Vault client (properties tab, copy attribute values, etc.)2. Event handler •Automatically run functions on specific event (Check in, Move, delete, etc.)3.Vault + Civil3D,Excel, etc.•Vault initiates third applications and runs commands.4. Job server•Run user initiated functions on a Job server(publish to PDF, Export C3D file to AutoCAD, etc.)5. Scheduledjobs •Scheduler runs jobs automatically without user input.Download thefile with all dependencies to local cache Open the filewithapplicationRuncommandAdd/update thefile in the Vault1.Make sure you can run your commands without any user input2.If the function does not exist or needs user input, write it using the software’s API3.Run function manually first4.Run function in the Vault workflow•Publish dwg to nwc.1.Download files withdependencies to C drive2.Check out nwc files3.Open files with AutoCADAccoreconsole4.Run NWCOUT5.Check in nwc files•Create Civil 3D surfaces from 3D faces •Surveyors create surface in other applications and export 3D faces.•One region can have about 500,000 3D faces. If you try to select all those 3D faces in Civil 3D it can take a very long time of crash software.•This custom application adds 3D faces in portions (100,000) using Accoreconsole and a Job server.•It takes a couple of minutes.Vault integrations with other applicationsCreate Civil 3D surface from 3D faces (514828)Create surface On Job server -7 minutes Create surface On Job server -50 minutes•Publishing Civil 3D to AutoCAD•Publishing DWG to PDF •Cleaning DWG files (Audit, Purge, Purge reg. apps., detach not found Xrefs)•Other functions depending of project needs Run Accoreconsole from Vault APIRun script -Load .dll and run command Write command with Civil 3D APIAutomated process Manual processVault integrations with other applications•Publishing nwf to nwd1.Download nwf with all dependencies to alocal drive2.Open the nwf file with Navis works3.Save the file as nwd4.Add/Check in the file to Vault nwfnwd。
Autodesk-vault-软件使用说明
Autodesk vault 软件为提高BIM深化设计室设计文件管理效率，故引入autodesk vault管理软件。
该软件能够通过集中地存储所有工程设计数据和相关文档，节省整理文件所需的时间，避免成本高昂的错误，更加高效地发布和修改设计。
Autodesk Vault 包含丰富的功能，其主要功能可以用以下简图表示：二、软件使用1、vault 版本Autodesk Vault 有四种版本，每个版本均已扩展以符合您的特定业务需求。
1.1 Autodesk Vault Basic ：Vault Basic 在一个中心位置安全地存储和管理数据，可帮助团队快速创建、共享和重用数字原型设计信息。
用户可以对Vault 中的文件执行基本的版本控制操作，并可以快速打包文件以便共享。
1.2 Autodesk Vault Workgroup :Vault Workgroup 通过在一个中心位置安全地组织、管理和跟踪数据，从而帮助团队创建和共享设计及工程信息。
这种易管理性可以启用工作组对数据访问和安全性的控制，并能简化各种准则下基于团队的设计。
用户通过Vault Workgroup 可以快速管理其设计以及实时跟踪所做的更改，因此他们无需付出额外的劳动就提高了生产率。
此外，Vault Workgroup 可直接在设计应用程序中实现生命周期和版本控制过程，这样不仅可以缩短周期时间，还能提高工程数据的质量。
1.3 Autodesk Vault Collaboration :Vault Collaboration 不仅具备了Autodesk Vault Workgroup 的所有功能，还新增了高级工具集，为管理员提供了管理大型工作组时所需的可扩展性。
用户可以使用包含的Web Client 与下游数据客户共享工程设计数据，并通过发布到Microsoft® SharePoint® 可扩展多个站点功能（使公司能够在分布式工作组之间同步设计数据）向扩大后的企业显示设计相关的信息，使数字模型的可抵达范围扩展到整个项目团队。
Autodesk Vault 2014 VDF编程指南说明书
Programming the Vault with the VDFDennis Mulonas – AutodeskDoug Redmond – AutodeskDV1670The Autodesk Vault 2014 release adds a powerful set of programming tools: the Vault Development Framework (VDF). Learn how to unlock the power of the VDF. Get more features in your apps with less code. This class goes over the basics of the VDF, such as how to use the Login dialog.Learning ObjectivesAt the end of this class, you will be able to:∙Explain the basics of the VDF∙Use UI components from the VDF∙Upload and download files through the VDFAbout the SpeakersDennis Mulonas is a software architect for the Vault. He has been working at Autodesk for 21 years.Doug Redmond is a developer on Vault and PLM 360. He runs the blog It’s All Just Ones and Zeros.IntroductionThis document is not just a repeat of the slide deck. Instead, this document will contain reference information and additional materials. The demo app shown in the class will be covered here, step-by-step.GlossaryADMS– Autodesk Data Management Server. The Vault server component that contains the database. In a multi-workgroup environment, there would be many ADMS installs, one for each workgroup.AVFS– Autodesk Vault File Server. The Vault server component that contains the file store. In a multi-site environment, there would be many AVFS installs, one for each site.Entity–A “base class” for the major currency types in Vault. Usually entity means file, folder, item, change order, or custom object.Vault API– The full set of programming interfaces supported by Autodesk. It includes the VDF and the web service API.VDF– Vault Development Framework. Value-add content for API developers, built on top of the web service API.Web Service API– The low level API that talks directly to a Vault server through HTTP.Working Folder– The location on a local computer that maps to a location in the Vault.VDF ComponentsThere are 4 DLLs that make up the VDF. These DLLs can be found in the “bin” directory of the SDK. VDF DLL’s are identified by the “Autodesk.DataManagement” prefix. Vault-specific functionality will have “Vault” in the name, and UI-specific functionality will have “Forms” in the name.Autodesk.DataManagement.Client.Framework.dll– The base workflow functionality. Autodesk.DataManagement.Client.Framework.Forms.dll– The base UI functionality. Autodesk.DataManagement.Client.Framework.Vault.dll– The Vault workflow functionality. Autodesk.DataManagement.Client.Framework.Vault.Forms.dll– The Vault UI functionality. When using the VDF you will usually reference to all 4 DLLs if any VDF UI components are involved. If you not using UI components, then just reference the 2 non-Forms DLLs. When deploying an EXE, you should deploy all referenced VDF DLLs. If you have a plug-in, you usually don’t need to deploy any SDK DLLs because the hosting app should already have the VDF DLLs available.DevExpress DLLsThe SDK bin directory also contains a bunch of DLLs with the “DevExpress” prefix. These contain third-party UI components used by the VDF. If your application does not use VDF UI, then you can safely ignore these DLLs. But if UI is used, then you may need to deal with DevExpress DLLs.If you have the Vault client installed, these DLLs will be available in the GAC. If you do not have the Vault client installed, you will need to reference these DLLs explicitly in your project. The same rules apply when deploying. If the user has the Vault client, then you don’t need to redistribute these DLLs. If the user does not have the Vault client, you need to redistribute the DLLs.It’s easiest to reference and redistribute all DevExpress DLLs in the SDK bin directory. There is no easy way to determine which exact DLLs you need.Demo ApplicationThis is a step-by-step guide to creating an EXE that leverages key components on the VDF. The app will let the user log in to vault, browse the Vault, select a file and download/open a file by double clicking on it.I’ll be using Visual Studio 2010 for this example, but the steps should be the same for later editions. The code samples are in C#, but it should be easy to follow for VB developers. There are also several tools available online for converting C# and code.This application can be found in the Additional Class Materials .zip file.Configuring the ProjectStartup Visual Studio and create a new project. Choose a Windows Forms Application type. VDF UI is built on Windows Forms, not WPF. The VDF is also not compatible with Windows App Store development. Use .NET Framework 4 since that is the version the VDF 2014 DLLs were built with.Once the project is created, the next step is to set the references. Go to the Solution Explorer, right-click the References folder and select Add Reference.In the Add Reference dialog, click on the Browse tab. Navigate to the bin directory of the SDK folder and select the following 6 DLLs:∙Autodesk.Connectivity.Extensibility.Framework.dll∙Autodesk.Connectivity.WebServices.dll∙Autodesk.DataManagement.Client.Framework.dll∙Autodesk.DataManagement.Client.Framework.Forms.dll∙Autodesk.DataManagement.Client.Framework.Vault.dll∙Autodesk.DataManagement.Client.Framework.Vault.Forms.dllBy default, the SDK folder is C:\Program Files (x86)\Autodesk\Autodesk Vault 2014 SDK. If you don’t have that folder, you may need to install the SDK. Go to your Vault client install folder (ex. C:\Program Files\Autodesk\Vault Professional 2014), go to the SDK folder and run the install.Once you have your references in place, it should look something like this:If you are having problem compiling, go to your project settings an make sure that the target framework is .NET Framework 4. Do not use a framework that says “Client Profile”.Logging in to VaultVisual Studio will create a default dialog, Form1, but you can delete it. All UI will be coming from the VDF.Inside your Program.cs file. Set up your using statements (Imports in VB). Here are the statements I will be adding for this example.using System.Diagnostics;using Autodesk.DataManagement.Client.Framework.Vault.Currency.Connections;using Autodesk.DataManagement.Client.Framework.Vault.Currency.Entities;using Autodesk.DataManagement.Client.Framework.Vault.Currency.Properties;using VDF=Autodesk.DataManagement.Client.Framework;Inside my main function, comment out all the Form1 stuff. So that it looks like: [STAThread]static void Main(){Application.EnableVisualStyles();Application.SetCompatibleTextRenderingDefault(false);//Application.Run(new Form1());// -- put program logic here --}The first part of the program logic is to log in. Popping up the VDF login dialog is easy. The below code will log the user in. If the return value is non-null the user is properly logged in. // log inConnection connection = VDF.Vault.Forms.Library.Login(null);if (connection != null){// -- put Vault operations here --}When run, the user will see the standard Vault login dialog.Selecting a File in VaultNow that you are logged in, the next step is to browse the Vault for a file. The SelectEntity dialog does most of the work for you. You just have to worry about the settings.The dialog uses a grid, and you need to set the initial state of the grid. The user can change the grid settings, but you need a starting configuration. At a minimum, the grid configuration needs a persistence key (to remember the user settings), a view column and a sort column. You can use any property for the view/sort settings, but this example will use EntityIcon and EntityName, which are out-of-the-box properties.var config = new VDF.Vault.Forms.Controls.VaultBrowserControl.Configuration(connection, "Autodesk.OpenFromVaultSample.grid", null);config.AddInitialColumn(PropertyDefinitionIds.Client.EntityIcon);config.AddInitialColumn(PropertyDefinitionIds.Server.EntityName);config.AddInitialSortCriteria(PropertyDefinitionIds.Server.EntityName, true);The EntityName is the display name for the object. The EntityIcon is the object icon, which helps the user can distinguish between files and folders.There is another settings object for the dialog itself. It has its own persistence key and contains a reference to the grid. For this example, the user should only be selecting Files, so ActionableEntityClassID is set to Files.var settings = new VDF.Vault.Forms.Settings.SelectEntitySettings();settings.PersistenceKey = "Autodesk.OpenFromVaultSample";settings.ActionableEntityClassID = EntityClassIds.Files;settings.GridConfig = config;Now you are ready to invoke the dialog. If the user selects a file, you will get a non-null result back.var results = VDF.Vault.Forms.Library.SelectEntity(connection, settings);if (results != null && results.SelectedEntities.Any()){// -- do operations on the selection --}When run, the user will see a dialog that lets them navigate the Vault folders and select a file.Downloading and Opening the FileThe user has selected the file, now it is time to download it. AcquireFiles is the function you want to use. As usual, some settings are required and results are returned. AcquireFiles can be used to download and/or checkout, so you need to set DefaultAcquisitionOption to just Download. You specify which file(s) to download by calling the AddEntityToAcquire function. // download the filevar settings = new VDF.Vault.Settings.AcquireFilesSettings(connection);settings.DefaultAcquisitionOption =VDF.Vault.Settings.AcquireFilesSettings.AcquisitionOption.Download;settings.AddEntityToAcquire(entity);var results = connection.FileManager.AcquireFiles(settings);if (results.FileResults.Any()){// -- perform operations on downloaded file --}This AcquireFiles call doesn’t specify a download location, so it defaults to the working folder. The VDF provides an easy way to look up that location by using the WorkingFoldersManager on the Connection object.// figure out where the file was downloaded on diskFileIteration file = results.FileResults.First().File;string localPath =connection.WorkingFoldersManager.GetPathOfFileInWorkingFolder(file).FullPath;Lastly you open the file using the default application associated with that file extension. This code doesn’t use the VDF. It uses the System.Diagnostics library in .NET.// Open the fileProcessStartInfo pInfo = new ProcessStartInfo();pInfo.FileName = localPath;Process p = Process.Start(pInfo);That’s it for the demo app. It’s a good starting point for using the VDF. This example used the default settings for most things, but there is a lot of additional functionally available to you by simply adjusting the settings.11Useful LinksIt’s Al l just Ones and Zeros/A blog just for the Vault and PLM 360 APIs. Updates weekly. Sample apps every month, usually with source code.ADN Manufacturing DevBlog/manufacturing/A blog for the Autodesk Developer Network to post tips, tricks and sample code. Covers all Autodesk Manufacturing products, including Vault.Vault Online Help/view/VAULT/2014/ENU/The official help documentation for Vault. Contains a section on using the VDF.Vault Customization Discussion Group/t5/Vault-Customization/bd-p/301A discussion group for Vault API developers. If you get stuck, this is where you go.12。
Autodesk Vault 2021 新特性详解说明书
MFG463491 –Autodesk Vault 2021 What’s NewSenthil KumarProduct Manager| @NG_SenthilKumarIrvin Hayes JrProduct Manager| @ihayesjrAbout the speakerProduct Manager for the Data Management Group at Autodesk in Singapore. With Autodesk for the last 15 yrs. In Autodesk, worked as a Product Support Engineer, QA, QA Manager, and Product Owner before becoming Product Manager. Prior to joining Autodesk, worked for Autodesk Distributor, PTC and Delcam..About the speakerIrvin is a Product Manager on the Autodesk Vault team based in Novi, Michigan. He has worked at Autodesk for fifteen years starting in product support and as a user experience designer. Irvin is a Microsoft® Certified Professional and has been working in the information technology field for more than 27 years. He helps partners, consulting, and sales develop Vault deployment plans in enterprise environments and system requirements. You can find multiple classes Irvin has presented at Autodesk University, on a wide range of Vault topics.Vault 2021: More Value for Subscribers Productivity-boosting functionality you can expectProductivity for CAD UsersSupports Inventorand Revit interoperability and adds significant workflow and usability improvements Smart Duplicate ReductionCompares 3D shapesand delivers insights onduplicate contentReduceFind ReuseMore Efficiency forAdministratorsAllows more granularity withinthe security model and minimizesdeployment and maintenancedowntimeProductivity for CAD UsersVault 2021 Supports Inventor and Revit interoperabilityFor custom fabricators that work in the buildingand infrastructure industry, Vault 2021 supportsthe new Inventor and Revit interoperability▪Revit data is stored and archived in Networkdrive or BIM 360▪The data is referenced (incl. links) in Inventorand gets synced▪Revit data is not archived and managed in Vault,but Vault can check in Inventor files properly andopen the files properly and resolve any linkedRevit filesUnused document detection Vault 2021 can help you clean up unused designs and avoid releasing them USED DESIGN UNUSED DESIGNNew Property “Has Parent Relationship” to easily recognize orphaned files. Can be used in Filter/Saved Search, state transition, and much more…Condition for state transitionCopy designCustomer RequestMany companies have very strict controls over properties and standards enforcementDeliverable▪Copy Design Rule Sets are stored on the server instead of the local disk▪Configure, export, import rulesets andenforce ruleset for all users▪Set a rule to copy a UDP value from the original file to a different UDP in the new file e.g. for original part number, source drawing file etc.1 2ValueRemove friction for more productivityDeliverable▪Add a New Filter to show out of date files to quickly retrieve updated files▪Change state condition is batched for actions including Files, Folders, and Items and presented in one dialog instead of separately and every time –huge time savings▪Option to show more than 1000 jobs in Job QueueMore flexibility and information within ECO notification for easy follow upDeliverable▪Customize the email template:•Include ECO properties in the subject and body of the email•Include links to files & Itemsand more▪Template is stored on the serverNavisworks preview and Shared ViewsValueShare Navisworks information to a wider audience forconsumption and reviewDeliverable▪Generate DWF files for Navisworksand expose them in the preview▪Shared Views capabilities availablefor Navisworks filesSmart Duplicate ReductionA new part is not just about design time, it is about time and costs of documenting,validating, producing and managing the same physical part again and again.Manage new partChallenges *According to The Aberdeen Group, a leading information technology and business intelligence research analystThe annual carrying costs of introducing anew part number range between $4,500 and$23,000 per item*PrototypingTestingProductionSupplying StockingDeliverable▪Understand the duplicate ratio within environment▪Clean up the existing design from duplicate parts duringreview/ release process and before check in process for external partsDuplicate reduction Value for subscriberValue▪Reduce time to market and increase profitability byreducing cost after design phase and avoid introducing quality issues▪No disruption for mechanical engineers by allowing themto continue to have the freedomto design the way they wantData analytics and duplicate reduction New functionalityReduce Find Reuse Detect duplicates andpromote more re-use Tell me about my data. I need more insights.How big is the problem in my environment?Do I need to take any action? If so which actions?DATA ANALYTICS & INSIGHTSTomEngineeringManagerPerform geometric search in Inventor and easily replace duplicate parts workflow I want to continue to have the freedom to design how I want, but before releasing the design I want to know whether duplicate parts are available?DUPLICATE REDUCTION Christina Mechanical EngineerMore Efficiency for AdministratorsMore efficiency for administratorsVault 2021 allows more granularity withinthe security model and minimizes deploymentand maintenance downtime Restrict file download access Audit logHide disabled users and groups Resizable security dialog Easily identify user with Admin role when logged inFlexible instance namePurge historical dataQuick file store validationVault 2020 security modelNeed more granularityFolder A Folder B CC XX Folder CFolder AFolder B CC XX Folder CFolder A Folder B CC XX Folder CRead access also allows file downloadShopfloor worker and ME from Team 2 can access and download all files including sensitive dataDesign/Folder A/Folder B/Folder CME Team 2ME Team 1Shopfloor WorkerVane PumpFolder ACC XXFolder BFolder CFolder A CC XXFolder B Folder CFolder A CC XXFolder B Folder CFolder A CC XX Folder B Folder C Folder A CC XXFolder B Folder C CC XXFolder B Folder CCC XXFolder CSecurity model in 2021More granularity!Read access: meta data like Used/Where Used, Thumbnail Download access: appropriate groups and users download the right design dataDesign/Folder A/Folder B/Folder CME Team 2ME Team 1Shopfloor WorkerVane PumpFolder ACC XXFolder BFolder CValue▪Increase cross department and external collaboration while continue to protect your data▪Eliminate extra work to re-organize your data to fit security system requirements▪Separate audit logs & configure the system with ease▪Address the most requested ideas in the forumWhat▪Grant read access to the appropriate groups and users role based while preventing data download▪Flexibility to restrict download access to sensible design data while continue to allow read access for meta data for search, reports etc.object & Lifecycle based▪Track download & Audit Log & several usability enhancements(resizable dialog, hide disabled users and much more)What does this mean for your existing data? You have a new download permissionMigrate existing roles, objects, and lifecycle security read permission toread plus download permissionsFlexibleRead/Download permissions can be applied to roles, objects, and lifecycle state Properties Read(incl. Thumbnail)Search, Reports, Send a linkOpen, View in Window,Insert into CADGET, File Download in Thin Client, Pack & Go, Copy DesignCreate PDF, DWF, Edit/ Update Properties, Job ProcessorShare Views, Update View, Manual Upload to Cloud Drive, Job ProcessorNote: DWF & PDF files continue to have a different ACL than CAD filesTrack download and audit log ▪Enhanced logging for download to track“real” download operations only▪GET, Open, View in Window, Insert intoCAD, Update View▪Pack & Go, Send File, Share Views▪UI setting to turn on/off logging for download and delete▪Separate Audit Logs file for download and delete 123Customer requestVery difficult today if you are managing 100's of users to navigate through the Object security dialogUsability enhancements in Object security dialogDeliverableResizable Details dialog for better usability on Security TabVault 2020Vault 2021Customer requestEasy administration of disabled usersDeliverableOption to filter out disabled users and groups in Users, Groups management dialogs as well as in “add Members dialogs” within object security tab, state security tab, transition definition, etc.usermanagement dialogsCustomer request“Easy Recognize” login user with administrator permissionsDeliverableConfigure status bar color in security tab for users assigned toadmin rolesMinimize downtime for backup / maintenance Customer challengeBackup, restore upgrade workflows aretaking a very long time by big databasesand file-storesWhat▪Allow purge for legacy versions which areunder lifecycle control▪File store validation is optimized▪You can also use quick file store optionfor quick validationValueMinimize downtime during Backup, Restore, and upgrade by reducing file stores and database sizeNew purge option to includeexisting file versions per state inthe control tabQuick File store validation optionwithin attach and restoreAllows Vault installation/configuration to connect to an Instance not named AUTODESKVAULT▪Naming conventions that must be kept forcompany standards▪When several Vault Servers reside in the same ITinfrastructure▪Separate DEV/ QA environment that is running amirror image of production Vault▪Several Vault Server versions within the same SQL ServerMore Flexible Deploymentand collaboration workflowsValue▪Increase cross-department and external collaboration while protecting data and eliminating extra work to reorganize data to fit security system requirements▪Separate audit logs and ability to configure the system with ease▪Reduce file store size impact downtime during Backup and Restore▪Comply and IT naming converting and maintenance costs for test environmentDeliverable▪Grant read access to the appropriate groups and user roles while preventing data download ▪Flexibility to restrict download access of sensitive data while allowing read access of meta data for search, reports, etc. by object and lifecycle▪Track download and audit log and several usability enhancements(resizable dialog, hide disabled users, and much more)▪Quick file store validation and purge historical data functionality▪Flexible instance nameVault 2021.1 UpdateInventor Revit Interoperability▪Check in the Revit files within the Inventor assemblies.▪Add the Revit file type using the Open from Vault dialog.Exclude Path –Inventor Vault Add-inAs a CAD Admin, I want to exclude path by using Vault Options withinInventor/Vault Add-in.Those files within the excluded paths will not be included during check-in. Example:▪Revit files managed in BIM 360▪Point CloudVault 2021.1 Update -Productivity for CAD Users ▪Enhancements to Show Details▪Show Details dialog box is also floating and dockable.▪New tabs are added (Uses, Change Order, and Bill of Materials) to display information about the model.▪Assign Items directly from Uses Tab▪Commands to Go To Item and Go To ECO Access Contextual Data BEFORE AFTERVault 2021.1 Update -Productivity for CAD Users Saved Search Enhancements▪Ability to group Saved Searches▪Ability to create custom view for Saved SearchesCombined Geometric & Properties FilteringProperties Filtering supports theMechanical Engineer to find quicklythe right part for replace workflow▪Advanced Search▪Exclude different Materials▪Identify the exact match▪Exclude mirror parts▪The process can now be donebefore the replace workflow for allfiles within one groupVault 2021: More Value for Subscribers Productivity-boosting functionality you can expectProductivity for CAD UsersSupports Inventorand Revit interoperability and adds significant workflow and usability improvementsSmart Duplicate ReductionCompares 3D shapesand delivers insights onduplicate contentReduceFind ReuseMore Efficiency for AdministratorsAllows more granularity within thesecurity model and minimizesdeployment and maintenancedowntimeVideo LinksPlease visit the following links for all the videos featured in the Presentation. Autodesk Vault 2021 What's Newhttps:///watch?v=UZdaknmjThEhttps:///campaigns/vault-roadmap/overviewhttps:///products/vault/features?plc=VLTM&term=1-YEAR&support=ADVANCED&quantity=1Make Your Voice HeardVault Feedback Communityhttps://autode.sk/VaultFeedbackVault Ideas Pagehttps://autode.sk/vaultideaAutodesk and the Autodesk logo are registered trademarks or trademarks of Autodesk, Inc., and/or its subsidiaries and/or affiliates in the USA and/or other countries. All other brand names, product names, or trademarks belong to their respective holders. Autodesk reserves the right to alter product and services offerings, and specifications and pricing at any time without notice, and is not responsible for typographical or graphical errors that may appear in this document.© 2020 Autodesk. All rights reserved.。
Autodesk Vault Server 2012 安装指南说明书
Installing Autodesk Vault Server 2012 on Small Business Server 2008Please follow the following steps to ensure a successful installation of the Autodesk Vault Server 2012 on Microsoft Small Business Server 2008. Please note that this document covers the most common Microsoft Small Business Server 2008 environment and your specific environment may vary. This document does not cover all possible configurations.Though it is supported, Autodesk does not recommend installing onto Microsoft Small Business Server 2008 due to the complexity of the operating system and that it is a domain controller. It is recommended to use a machine not running Microsoft Small Business Server 2008, if able.**Please note the following information regarding running SQL 2008 on a domain controller From /en-us/library/ms143506.aspx#DC_Support:For security reasons, Microsoft recommends that you do not install SQL Server 2008/ 2008 R2 on adomain controller. SQL Server Setup will not block installation on a computer that is a domain controller, but the following limitations apply:∙On Windows Server 2003, SQL Server services can run under a domain account or a local system account.∙You cannot run SQL Server services on a domain controller under a local service account or a network service account.∙After SQL Server is installed on a computer, you cannot change the computer from a domain member to a domain controller. You must uninstall SQL Server before you change the hostcomputer to a domain controller.∙After SQL Server is installed on a computer, you cannot change the computer from a domain controller to a domain member. You must uninstall SQL Server before you change the hostcomputer to a domain member.∙SQL Server failover cluster instances are not supported where cluster nodes are domain controllers.∙SQL Server Setup cannot create security groups or provision SQL Server service accounts ona read-only domain controller. In this scenario, Setup will fail.Pre Installation - Operating System1.Disable the User Account Control (UAC) through Control Panel -> User Accounts; a reboot isrequired.2.If applicable, download and install Windows 2008 Service Pack 2. Details on Server 2008 SP2can be found here.**Service pack 2 is required for a successful implementation.Pre Installation – Microsoft SQL ServerSQL 2008 / 2008 R21.Click Add a new user account inside the SBS Console.2.Enter user information shown below for the new user and click Next.3.Input a password that fulfills your password requirements and click Add user account.4.Click Finish to complete the wizard.5.Prior to installing SQL, please ensure that .NET 3.5 SP1 has been installed as it is a prerequisitefor SQL. The installer can be downloaded or ran from3rdParty\NET\35SP1\wcu\dotNetFramework on the installation media.6.Begin the SQL Server installation from your SQL installation media. If plan on using SQL Expressthat is bundled with vault, you will run Setup.exe located under 3rdParty\SQL2008Expressfolder on your Vault 2012 installation media. You can also download SQL Express 2008 R2 from .7.Start the installation process for Microsoft SQL 2008 Server by selecting New SQL Server stand-alone installation or add features to an existing installation from the Installation menu.8.The installation process installs any necessary prerequisites and begins running the pre-installation checks. Note any errors and take the necessary corrective actions before continuing.9.In the Feature Selection window, select Database Engine Services.10.In the Instance Configuration window, select Named instance and enter the name asAutodeskVault.Note: If you install SQL without using this instance name, the Autodesk Vault Server installation will create its own instance of SQL Server called AutodeskVault using Microsoft SQL Express 2008 and will fail due to the Domain Controller restrictions listed earlier in this document.11.In the Server Configuration window, select the Service Accounts tab.a.Specify user account created in Step 2 for the SQL Server Database Engine. Set theStartup Type to Automatic.12.In the Database Engine Configuration window, select the Account Provisioning tab.a.Select Mixed Mode authentication and set the SA password. The default password usedduring a default installation for the SA password is AutodeskVault@26200.b.Add the local administrator account (or desired account) as a SQL Server administrator.**Only Windows users entered in this dialog will have full rights when logging into theSQL server. All other Windows logins will be treated as a guest account.13.Verify the installation options chosen and Install. Once the installer has finished, it can beclosed.Pre Installation – IIS1.Browse to the IIS configuration files in SBS 2008:C:\Windows\System32\inetsrv\config\applicationHost.config2.Create a copy of applicationHost.config and place it in a temporary location. This will preservethe original file.3.Open the file applicationHost.config file in Notepad. Browse to the <globalModules>sectionand modify the line<add name="PasswordExpiryModule" image="C:\Windows\system32\RpcProxy\RpcProxy.dll" />to read<add name="PasswordExpiryModule" image="C:\Windows\system32\RpcProxy\RpcProxy.dll"preCondition="bitness64" />4.Additionally, if Exchange 2007 Service Pack 3 is installed, modify the lines<add name=”exppw” image=”C:\Program Files\Microsoft\ExchangeServer\ClientAccess\Owa\auth\exppw.dll” />to read<add name=”exppw” image=”C:\Program Files\Microsoft\ExchangeServer\ClientAccess\Owa\auth\exppw.dll” preCondition=”bitness64″/>and under <modules> section update line<add name=”exppw” />to read<add name=”exppw” preCondition=”bitness64″/>5.Save the file.6.Open the command prompt and stop and start IIS by running IISRESET at the command prompt.Do not close the command prompt.7.Type the following command at the command prompt and hit enter. Please note that this is oneline.%windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpCompression /-[name='xpress']8.Type exit to close the command prompt.Autodesk Vault Server 2012 Installation1. Autodesk recommends installing the Vault Server to a non-default website. This is achieved byselecting the Configure button during the installation. This is not required, but isrecommended.plete the installation of Vault Server 2012.3.In some cases, users experienced error 29001…Error –5001.19 during the installation of theAutodesk Vault 2012 (Server) Language Pack. If you experience this issue, please perform the following steps to resolve:a.Browse to the IIS configuration files in SBS 2008:C:\Windows\System32\inetsrv\config\applicationHost.configb.Open the file applicationHost.config file in Notepad and modify the line<section name="requestFiltering" overrideModeDefault="Deny" />to read< section name="requestFiltering" overrideModeDefault="Allow" />c.Save the file and close Notepad.d.Start the installation again.Post- Installation IIS 71.Open the IIS Manger by going to Control Panel -> Administrative Tools -> Internet InformationServices Manager2.Right click the Default Application Pool and select Set Application Pool Defaults3.Modify the Enable 32-Bit Applications and set the value to False.4.Right click on Application Pools and select Add Application Pool. Enter a name for a newapplication pool, 32DefaultAppPool.5.Right click the new application pool 32DefaultAppPool and select Advanced Settings.6.Set Enable 32-Bit applications to True.7.Next, right click the DefaultAppPool and select View Applications.8.Right click on /AutodeskDM/… application, and select Change Application Pool…9.Assign the new 32DefaultAppPool.10.Verify connectivity.Links referenced/en-us/library/ms143506.aspx#DC_Support/kb/968849/downloads/details.aspx?FamilyID=3181842A-4090-4431-ACDD-9A1C832E65A6&displaylang=nl&displaylang=en/kb/970259/EN-US/default.aspx?scid=kb;en-us;971272/en-us/library/cc546071(WS.10).aspxRevision History。
Autodesk Vault Data Standard 2018 用户指南说明书
What‘s New in Vault Data Standard 2018Technical Details | Migration | TipsMarkus KoechlSolutions Engineer PDM|PLM –Autodesk Central EuropeAgenda▪What‘s New –Features & Functions▪Property Validation CAD –Additional Use Cases ▪Issues Fixed▪Migrate Legacy Configurations▪Tips & TricksWhat‘s New –GeneralVDS 2018 What‘s New | General▪Improved Templates and Styles Dynamic Grid ▪Date Picker display*▪Enforce list values▪Uppercase / lowercase▪Avoid label selection▪Additional icons for file listings▪Maintain pick list selection in all dialogs▪Prepared for cascading selections / refresh* Need to Know: Localizations require Converter-Culture: https:///community/article/27246What‘s New –VDS CADVDS CAD | Validation Setup Flexibility✓Support Vault validation▪Support CFG override validation▪Support legacy behaviors -> see chapter Additional Use CasesVDS CAD | Folder Selection Usability ▪Interactive selection automatically expands ifsubfolders exist▪If new path suggestion is applied auto-expand is suppressedWhat‘s New –VDS InventorVDS Inventor | Leverage Options and Context ▪Preset▪File Numbering▪Generate File Numbers forIDW|DWG|IPN (2017.0.1)▪Folder selection adds smart support for▪“Suggested” path is preselected▪Assembly context▪Drawing first view’s model▪Presentation first scene’s assemblyVDS Inventor | Material Selection ▪Material selection new default▪Enforce list valuesCAD Property Validation Additional Use Cases VDS 2018 | VDS 2017.0.2VDS 2016 2017 2018 | Standard Use Case▪System Property –Static Label + Field▪Category Property –Dynamic Grid Label + Field➢Validation = Vault Property ConstraintsValidation = CFG +Category constraints▪CFG -RequiresValue ▪Override wins▪CFG -RequiresValue ▪Override winsVDS 2018/VDS 2017.0.2 | Use Case 3 –File Property ▪CFG –adds custom property▪Property is no category member▪Property is mappedVDS 2018/VDS 2017.0.2 | Use Case 4 –File ONLY Property ▪CFG –adds custom property(Property does notexist in Vault▪Dialog adds input field⇒File only custom property⇒CFG only drives constraintVDS 2018/VDS 2017.0.2 | Support Legacy Validation Behavior Validation = CFG only Dialog works without -Category-DynamicCategoryPropGridValidation = CFG + Category constraintsDialog works without-DynamicCategoryPropGrid Validation = CFG + Category constraintsVDS 2018/VDS 2017.0.2 | Validation BehaviorPropertyMapping ?Yes/NoNo(because pure CFG)Yes(because mapped)_Category ?Yes / NoNo matchIgnored forvalidationMatchIncluded invalidationProperty No (because pure CFG)Yes (because mapped)_Category ?Yes / No Included in validation Mapping ?Yes/NoNo Ignored for validationMatchPropertyMapping ?Yes/NoNo(because pure CFG)Included invalidationYes(because mapped)_Category ?Yes / NoNoIgnored forvalidationReminderVDS 2016 2017 2018 | Standard Use Case▪System Property –Static Label + Field▪Category Property –Dynamic Grid Label + Field➢Validation = Vault Property ConstraintsValidation = CFG +Category constraintsReminder | Dynamic Grid Property ListingRequired Setup to add property to Dynamic Grid✓Property included in category✓Property mappedChange Display Name / Label▪AutoCAD▪Inventor User Defined iProperties✓Display name / UIString.xmlIssues FixedVDS 2018/VDS 2017.0.2 | Issues Fixed▪Override formulas by values▪Sheet Metal –Material➢For Admins only ☺▪PowerShell -$dsDiag.Inspect()✓Use in loops** Continue not to use in event handlersMigrate 2017 –> 2018 Example –VDS Quickstart Configuration▪Create Visual Studio project for 2018▪Add 2018 references for▪General▪VDS Common.dll▪Vault WG/Pro Webservices.dll ▪CAD▪VDS dataStandard.UI.dll ▪Vault▪VDS CreateObject.dll▪Find / Replace 2017 by 2018▪All files of solution▪ComboBox–Selection▪Prevent reload of list for Category, Numbering Scheme and other custom ones▪Add “…, Mode=OneTime” to all dialogs’ combo boxes.https:///support/vault-products/troubleshooting/caas/simplecontent/content/vault-2017-data-standard-inventor-selected-numbering-scheme-functional-dialogs.html➢Action❑ComboBox Selection –Search and Replace▪ComboBox Selection –Checklist Dialogs updated?(Note –matching files number may very; example uses VDS Quickstart 2017 configuration)❑ItemsSource="{Binding PsList[GetCategories], Mode=OneTime}❑ItemsSource="{Binding PsList[GetNumSchms], Mode=OneTime}▪New Multilanguage Text Strings➢Action❑Add<UIString ID="LBL77">None</UIString>❑Add<UIString ID="TLT1">Local path</UIString>➢Repeat action for other languages▪Folder Selection –Suggested Path for ▪Components in assembly context▪Model of drawings first view▪Model of presentation first scene▪Folder Selection –AutoOpen▪Offers selection if subfolder(s) exist(s)▪Turned off if path is suggested➢Action -Leverage new property $Prop[_SuggestedVaultPath].Value❑Copy code block as shown below the existing call “AddCombo…” in existing CAD\Default.ps1➢Action❑Default.ps1: Add line $global:expandBreadCrumb=$false❑Replace breadCrumb.ps1 –if unchanged❑If already customized –Adopt change 1 in GetChildFolders($folder) $ret+=New-Object PSObject-Property@{ Name ="."; ID=-1}Toif($ret.Count -gt0){$ret+=New-Object PSObject-Property@{ Name ="."; ID=-1}}❑If already customized –add line in AddCombo($data)$cmb.IsDropDownOpen=$global:expandBreadCrumb▪DynamicDataGridCellStyle▪Character casing▪Enforce list of values▪Enforce list of Inventor Materials▪Date Picker format▪Note –Add ConverterCulture for non en-USenvironments, e.g.<DatePicker SelectedDate="{WPF:ValidatedBinding Value,ConverterCulture=de-DE}"SelectedDateFormat="Short" />▪DynamicDataGridLabelStyle▪Disable selection of labels➢Action❑Copy & Paste / Replace existing node for both styles in Inventor.xaml, SaveCopyAs.xaml▪DynamicDataGridCellStyle▪Character casing▪Enforce list of values▪Date Picker format▪Note –Add ConverterCulture for non en-USenvironments, e.g.<DatePicker SelectedDate="{WPF:ValidatedBinding Value,ConverterCulture=de-DE}"SelectedDateFormat="Short" />▪DynamicDataGridLabelStyle▪Disable selection of labels➢Action❑Copy & Paste / Replace existing node for both styles in AutoCAD.xamlMigrate 2017->2018 | Add Enhancements –Vault Explorer ▪DynamicDataGridCellStyle in Dialogs▪Character casing▪Enforce list of values▪Date Picker format▪DynamicDataGridLabelStyle▪Disable selection of labels➢Action❑Copy & Paste / Replace existing node for both styles in CustomObject, File, FileOffice, and Folder.xaml▪DynamicDataGridCellStyle in Datasheets ▪Character casing▪Enforce list of values▪Date Picker format▪DynamicDataGridLabelStyle▪Disable selection of labels➢Action❑Copy & Paste / Replace existing node for both styles in highlighted Datasheet files▪Item –Datasheet▪Display Icons of linked office files➢Action❑Copy additional / highlighted icons for office filesMigrate 2015R2 | 2016 –> 2018▪Create Visual Studio project for 2018▪Add 2018 references for▪General▪VDS Common.dll▪Vault WG/Pro Webservices.dll▪CAD▪VDS dataStandard.UI.dll▪Vault▪VDS CreateObject.dll▪Alternatively use the fully configured Advanced Editor template from here:https:///koechlm/VDS-2018-Advanced-Configuration-Editor.git❑Copy legacy 201x Configuration toC:\ProgramData\Autodesk\Vault 2018\Extensions\DataStandard ❑Open VS Editor Project to edit associatively 2018 configuration files➢Notice some files linked to the advanced editor project are not available in yourlegacy configuration❑Add Missing Files, copy from Default installed configuration (backup)➢CAD configuration❑.\CAD\addins\breadcrumb.ps1❑.\CAD\Configuration\SaveCopyAs.xamlContinue to add missing files…➢Vault Explorer configuration❑.\Vault\MenuDefinitions.xml❑Follow Step 5 to add legacy custom commands to thenew definition file➢Optionally copy document type definition files, if you plan to implement separated definition of XAML and XML sources (new in 2017)❑.\Vault\Configuration\File.xml❑.\Vault\Configuration\FileOffice.xml❑Find / Replace “Vault 2015 R2” or “Vault 2016”by “Vault 2018” according your source version➢All files of solution, Match whole word。
AutoCAD Vault 2022 使用指南说明书
AUTODESK UNIVERSITYIM500029-What's New in Vault 2022 -For the Author / ContributorSenthil KumarProduct Manager | @NG_Senthilkumar© 2021 Autodesk, Inc.Session DescriptionThe Vault 2022 continues to deliver a more modern, connected an insightful user experience. Vault 2022 is packed with features for the Author, Administrator and Participant company roles. For authors, those of you who use Inventor and other CAD design tools, we’re making sure you can focus on the work you love. Vault 2022 unlocks more design data by delivering a better-integrated data experience and BOM variants management. This keeps you better connected to your design data while working inside CAD, so you can spend more time getting your work done.Learning Objectives•Learn how to manage Inventor's Model State in Vault•Learn how to Save even more time with new filters in Duplicate Search•Learn how to Access and view data using the completely revamped Web Browser Experience •Learn about some general enhancements made in this new release for effective workflowVault 2022: Collaboration is Easier than EverContinues to deliver a more modern, connected, and insightfulexperienceStay connected to your engineering data Take your design data with you onto the shop floor, on-site, or out to meet your customer using the mobile app or web browserParticipants Optimize your deployment and manage your team easier With enhanced user and group management and modern replication technologyAdministrators Focus on the work you loveWith an integrated data experience and more efficiency to manage BOM variantsAuthorsAuthors Focus on the work you loveExperienceAccess Contextual & Relevant Engineering DataWhat’s New▪Vault ‘Show Details’ dockable panel inside Inventor ▪Assign Item within your CAD environment▪Access Change Order informationCustomer ValueFocus on your design tasks while accessing data management capabilities for optimumefficiencyAccess Contextual & Relevant Engineering DataWhat’s New Run Vault Copy Design directly inside Autodesk Inventor.▪Run copy design from the right-click menu in ‘Uses’ or ‘Where used’ in the Vault ‘Show details’ panel.▪Run copy design from the right-click menu in the Vault browser ▪Copy design runs –configure your copy as usual.After the Copy Design is complete, you can open your new design in Inventor, directly from the copy design dialog with a right mouse button click.Customer ValueFocus on your design tasks while accessing data management capabilities for optimum efficiencyInventor Model States ManagementWhat’s New▪Check In, Open/ Place operations support model state ▪Assign Item for each model state▪Manage BOM variants Customer ValueMore flexible and efficient solution to manage engineering BOM variant based on Inventormodel stateInventor Model States ManagementWhat’s New -Open Drawing from Vault –Model state support▪Right click on a model state and open the associated drawing ▪If a single drawing is associated to the model state file, the drawing file opens directly from Vault.▪If there are multiple drawings associated to the model state, you can select and open one or more of the associated drawings from the “Select File from Vault” dialog.▪If there is no associated drawing to the model state, you can open related drawings from other model states.Customer ValueMore flexible and efficient solution to manage engineering BOM variant based on Inventor model stateInventor Model States ManagementWhat’s New -Drawing support added for Vault items created from model states.▪When creating an item from an Inventor model that has model states, Vault will create a unique item for each model states that has a unique part number.▪In Vault 2022.1 support has been added to make sure that associated drawing (IDW & DWG) files referencing the appropriate model states are also linked to the items.“Has Model State” Property ▪A new "Has Model State" systemproperty is added to files to identify whether the file has an associated model state▪You can use it to search and customize the viewsDuplicate ReductionCustomer ValueIncrease profitability through duplicate reduction while allowing mechanical engineers to continue to have the freedom to design the way they wantWhat’s New▪Exclude mirror parts▪Identify the exact match▪Exclude different materials▪Advanced metadata search combined with geometricsearchCustomer ValueIncrease profitability through duplicate reduction while allowing mechanical engineers to continue to have the freedom to design the way they wantWhat’s New▪Exclude mirror parts▪Identify the exact match▪Exclude different materials▪Advanced metadata search combined with geometricsearchCustomer ValueAccess critical data like latest released date and approver without additional efforts for optimum efficiencyWhat’s New▪Track “Latest Released Date” and “Approver” properties▪Expose the information in revision table and title blockAdvanced Tab in Select Dialog What’s New▪The advanced options for file selection are now available consistently across all ‘File > Open’dialogs▪consistent access to Advanced search, shortcuts, and saved searches from the Vault client in the File > Open dialog for Vault Client (Copy Design, Attachments, Purge, Rename, Replace, Item, Plot Manager etc.)What’s New▪Vault 2022.1 integrates Autodesk Viewer into the Vault Client to view DWF/DWFx and PDF files.▪The addition of the Autodesk viewer includes printand markup functionality.Support for 3rd Party Add-insWhat’s New▪“Vault Details” Panel in SolidWorks Add-in▪SolidWorks 2021 Support▪Creo 7 Support for Creo add-in▪Connect Edition 14 and 15 Support forMicroStation Add-inParticipantsStay connected to your engineering data anywhere and in real timeParticipant Challenges& Digital Transformation▪Reduce the amount of paper needed▪No need to go to a computer terminal to access data▪No need to type in a part numberto search for drawings ▪Don’t get caught without theright documentation▪Feel confident that you areviewing correct, up to dateinformation▪Document engineering changerequests▪Reduce the need to print offpaper documents▪Search for drawings if you haveQR code▪Don’t get caught without theright documentationOn the shop Floor At the customer Site In the fieldBrowser experience for easyAccessCustomer ValueZero deployment to access, view and collaborate on vaulted dataWhat’s New▪Modern user experience & ease of use▪Support desktop as well as tablets▪Multiple tab browser support▪New View tab to view 2D/3D designs using the Autodesk Viewer▪Access Change Order Information▪Support folder/ project links▪Multi-select to View & Download▪Share desktop or web browser linksVault Thin (browser) Client support for Items and BOMs ▪Vault Thin Client 2022.1 includes support for Item Billof materials, and Item ‘where used’.Vault Thin client support for Markup▪Vault Thin Client 2022.1 includes support for markup your model and save it as image filein is mobileVault Mobile AppIOS 12 & higher Android 8 & higher Connects to Vault Professional 2020, 2021, and 2022▪View 2D/3D designs ▪Check non-CAD files in and out ▪Review, approve, and sign documents ▪Perform QR, barcode, simple, and extended searches ▪Create and participate in change orders, and moreVault Professional & Office subscription requiredCustomer ValueFlexibility to access and work with vaulted data on a mobile deviceVault 2022: Collaboration is Easier than EverContinues to deliver a more modern, connected, and insightfulexperienceStay connected to your engineering data Take your design data with you onto the shop floor, on-site, or out to meet your customer using the mobile app or web browserParticipants Optimize your deployment and manage your team easier With enhanced user and group management and modern replication technologyAdministrators Focus on the work you loveWith integrated data experience and more efficiency to manage BOM variantsAuthorsLinks to Videos▪Autodesk Vault 2022 What's New –Overviewhttps:///watch?v=rfdwB_e26Qk▪Autodesk Vault 2022 What's New Mobile Apphttps:///watch?v=dngLXP0P3pc▪Autodesk Vault 2022 What's New Model Stateshttps:///watch?v=cfeNt_sdUy4▪Autodesk Vault 2022 What's New Accessibility -Thin Client https:///watch?v=gWB_c7n6Qz0▪Autodesk Vault 2022.1 What’s New –Overviewhttps:///watch?v=rYDDReBaPNw© 2021 Autodesk, Inc.AUTODESK UNIVERSITYMake Your Voice Heard Vault Feedback Community https://autode.sk/VaultFeedback Vault Ideas Pagehttps://autode.sk/vaultideaThank you!AUTODESK UNIVERSITY。
Autodesk Vault 数据标准教程 - 第一章 - 新标准文件介绍说明书
Vault Data Standard – TutorialChapter 01 – New Standard FileIntroductionVault, as a default, does not create files and passively waits to manage files added by CAD or Office applications. Vault Data Standard adds the workflow to start new documents within Vault before the application first time opens it. See also Vault Data Standard – Tutorial, Chapter 00 - Introduction and ReadMe First.Learning Objectives-Learn how to configure Vault to enable the New Standard File… workflow-Learn how to leverage options like Auto-Numbering or enforced user input-Learn how to auto-select numbering schemes per category-Learn how to implement input constraints for properties-Get insights on Vault Data Standard configuration access points, allowing you to adjust or extend this command to your company’s needs.Training FilesYou need to have installed all training files by following the instructions in Chapter 00 – Introduction and ReadMe First.This chapter requires access to these files in Vault:VDS configuration files added or changed in this chapter’s exercises can be found in .\Training Files\VDS Configuration Files\Chapter 01 – finished\.WorkflowNavigate to the target folder, where a new file-record should create. Select the command New St andard File…from Toolbar or Context Menu.Clicking OK creates a file based on the selected document type and template.The new document is a blank copy of the selected template but got new property values; continue using double-click or right-click and open to edit the new file in the respective application.Exercise 1 - Configure VDS Document Types and TemplatesThe New Standard File … command requires file-templates managed in Vault. Companies may have many template files or even specific ones for different departments and persona. VDS builds folder structures to group templates; this structure is called Document Type. Selecting a Document Type fills the pull-down list Template automatically by listing the files residing in the folder, respectively.The default hierarchy of Document Type and its templates is configured like this:VDS expects the folders .\Templates\AutoCAD, .\Inventor, and .\Office being available in Vault. You imported all template-folders along with the training files in Chapter 00 – Introduction. The pull-down list Document Type does not list the native folder names and uses display names instead.Adding a new document type, e.g., Engineering Calculationrequires two steps.Step 1 – Create a new folderCreate a new folder of name Calculations in $/Templates/; this step is completed already, as we imported the folder alongside all training files.Step 2 – Register the new folder as Document Type in the Vault Data Standard Configuration.To do this, copy both files .\Vault\Configuration\File.xaml and File.xml to the customization path,.\Vault.Custom\Customization\.1.Edit the File.xml using the XML Editor of your choice as shown:2.Copy the node and adjust the values of DocName and Path:3.As we copied the Dialog definition file File.xaml and the Document Type definition file (File.xml) to theVault.Custom folder structure, we need to re-route the dialog to use the new type definition. Open the file File.xaml, search for “File.xml” and update the path as shown:Repeat the New Standard File … command and select the new Document Type and template file.Exercise 2 – Enable NumberingOur Vault VDS Tutorial has a pre-configured numbering scheme, Sequential. Activate it in the Vault behavior configuration; as we add more numbering schemes later, also set this scheme to Default:Now, as a user selects this numbering scheme in the New File dialog, the field File Name automatically hides (1) and the OK button enables (2):Exercise 3 – Enable Numbering per CategoryData Standard allows to auto-select a numbering scheme linked to the category selection; to bind numbering schemes and categories, the names of both need to match. We create new numbering schemes Engineering and Office, as shown below:Create a new file. VDS activates Engineering category as a default, and the matching name of the new numbering scheme activates automatically:Switching the category to Office (3) will also change the numbering scheme (4):Note – Switching categories also updates the property list. The dialog dynamically lists all properties linked to a category. Other Exercises of this tutorial, guide you on how to change the content of this grid, changing the order, or apply multi-language labels.Exercise 4 –Enforce “Title” Property ValueVault Property Behavior settings may enforce values and other constraints in general or per category. This exercise applies the restriction override Requires Value to the Title property for Office category files only. Enable this setting, as shown below:Note the change in behavior; even the validation of a valid filename is positive, the OK Button remains greyed until the additional constraint – a non-empty Title field – returns an accurate validation result.Data Standard prevents the creation of incompliant metadata, while Vault explorer as a default only marks a missing value as Compliance Violation.Configuration Insights – New Standard FileCreating a new file uses several configuration access points of VDS. The table below lists each workflow step, involved configuration files and functions, and refers to other customization tasks.。
Autodesk Vault 2011 属性系统简介与概述说明书
AUTODESK® VAULT 2011PROPERTIES INTRODUCTION AND OVERVIEWConcepts and common administrative tasks are described in this paper. This paper is not a comprehensive description - complete details are available through Vault 2011 Help. Most of the features described are in all Vault 2011 products. However, some features are only available in the higher levels of the Vault product line.IntroductionThe property system for Vault 2011 is a single set of properties that are shared across files, items, change orders and reference designators. There are two types of properties: System and User Defined Properties (UDP.) System properties cannot be deleted but do support some configuration options like renaming and a few support mapping. Duplicate property names are not permitted for either type.UDP’s are custom created properties that support assignment to object groups, policy constraints and mapping of values with file and BOM properties. With each new vault there are numerous UDP’s supplied as part of the default configuration.Some of the highlights of the new property system:o Consistent user interface for all property managemento Property constraint overrides by categoryo Streamlined Edit Properties wizardo New vertical properties grid supports multiple files as well as Items & Change Orders o‘Lists’ support text and number data types as well as addition and removal of valueso Standardized mapping for all property sourceso Bi-directional mappingProperty DefinitionA property definition contains a name, data type, policy settings and mappings. The definition also specifies which object groups are associated with and may utilize the property. As an example, we will use the property definition Author. If Author is associated with the File and Item groups it may appear on any file or item but cannot appear with change orders and reference designators. (Reference Designators are a feature of AutoCAD Electrical). Every object (file and item) that is associated with the property definition Author will have a unique value. This may seem obvious when comparing two files as they each may have a unique value. This principle may not be as obvious when comparing objects across groups. If a file is promoted to an item, the file and item are allowed to have unique values for Author.*Change Order Link Properties remain a separate propertysystem.AdministrationCreation and AssociationTo create a property the name and data typemust be specified. The new property is notavailable for use until it has been associated toan object group. The groups are: Change Order,File, Item and Reference Designator. In thesample image below, the File object group isselected. This new property cannot be attachedto an Item, Change Order or ReferenceDesignator unless those object groups are alsoselected.All files in the categories Base or Engineering will have this property automatically attached. If this property needs to be attached to a specific file in another category it may be manually attached. Manual attachment can be done in two ways: using the Edit Properties Wizard or the Add or Remove Property located on the Actions menu.The object groups Change Order and Reference Designator do not support categories. Therefore, any property associated with one of these groups will be automatically attached to all objects in that group.SettingsThe policy values under the Property Valuescolumn (left side of the dialog) are applied toall instances of this property except where thecategory override applies. The CategoryValues allow overrides by category. Consultthe Help for further details about overrides andpolicies. In this paper, we will outline InitialValue, List Values and Enforce List Values.Initial ValueThe Initial Value is applied once when theproperty is initially associated with an object.The initial value is only applied in the absenceof a user supplied or a mapped value.The initial association occurs in three circumstances: 1) object is created (ex: adding a file or creating an item) 2) assignment to a category that automatically attaches the property 3) manual property attachment.There are two types of Initial Value: static and mapped. The static value is a fixed value and may be any value that is valid for the selected data type. An initial mapped value copies the value from a file or BOM property.Initial Values should NOT be used onproperties where all regular mappings read thevalue from a file or BOM. A blank value in themapped file or BOM field takes precedenceover the initial value. This may appear as ifthe initial value is not applied when in fact themapped value of ‘blank’ takes precedence.List ValuesProperties of type Text and Number mayprovide a list of values for user selection andsearching. The administrator may add orremove values from the list at any time.Removal of a value from the list does notremove the value from any property where thatvalue has been applied. When specifying thevalue for this property, the user may chosefrom the list of values. Enter values that arenot on the list is allowed. If this property ismapped to read a value from a file or BOM, the imported value is not required to be on the list. Enforce List ValuesWhen enabled, this option will provide a warning symbol adjacent to this property if the value is not on the list. When a value is in violation of this policy, the default configuration for lifecycle transitions will not allow a file or item to be released.MappingTo create a property mapping, the administrator must first choose which object group is to be mapped. In the image below, this is specified under the first column titled Entity . The available choices are based on the value of the Associations field. Several Content Providers are included but in most cases it is best to leave theselection on All Files (*.*). Vault willautomatically select the most appropriateContent Provider based on the file type.Next, select a file that contains the propertyor BOM field to be mapped. The image onthe left shows the file properties available formapping in the file manifold_block.ipt .The Type column shows the data type of thesource property. Mapping may be doneacross data types. However, there arespecial considerations that are detailed in thenext section. The mapping direction bydefault will chose bi-directional unless the fileor BOM property does not support the inputof values. When this occurs the mappingoption will be limited to Read only. Readonly mappings should be used sparinglybecause any UDP that contains only ‘Readonly’ mappings may not be modified in Vault.Mapping Across Data TypesThere are four property types: Text,Number, Boolean & Date . The following matrix defines valid property mappings. Whenever a mapping is created between two different property types there is the possibility of incompatibility. The onus is on the user to input valid values. If an invalid value is entered in most cases, the equivalence will flag the property as non-equivalent. The exceptions are listed below.1. Mapping Boolean with Text : The supported valid text values are: Yes/No , True/False and1/0. These values are localized. A string like ‘Autodesk’ entered in a Text property cannot be transferred to a Boolean property. This property mapping would be flagged as notequivalent.2. Mapping Text with Number or Text with Date : Works well when all clients and the serverare in the same language-locale. With mixed locales values may convert in a manner that is not intuitive and may produce an undesirable result. Therefore, mapping Text withNumber or Text with Date is only recommended when the server and all clients are working in the same locale.Create OptionThe Create option applies to write mappings; if the file property does not exist when a value is pushed to the file, the administrator may choose whether the file property is created or not. The Create option has another function that is not obvious: when enabled the equivalence calculation will consider the absence of the property definition in the file as a blank value and Supported mapping across data types Source Property (File or BOM) U DP Text Number Boolean Date Text Yes Yes (2) Yes (1) Yes (2) Number Yes (2) Yes Yes NoBoolean Yes (1) Yes Yes No Date Yes (2) No No Yescompare it against the value of the UDP in Vault. When the Create option is disabled, equivalence will be set to ‘Good’ when the mapped property definition does not exist in the file.Example: I have two departments in myorganization that both create .dwg files but theyuse different file properties to represent thesame information. The R&D department usesthe file property DwgNum. The Toolingdepartment uses the file property DrwNo. I wantto manage all drawings from both groups in asingle Vault and with one UDP ‘DrawingNumber’. The correct configuration is to createbidirectional mappings and set the Create optionto Off for both mappings. The result is that amodification of the UDP Drawing Number willwrite its value back to whichever property existsand it will not create an extra property.Mapping AutoCAD Block AttributesAutodesk® AutoCAD® block attribute mapping requires configuration on the ADMS. Select Index Block Attributes… from the Tools menu in Autodesk Data Management Server Console 2011. Enter the AutoCAD block names from which to extract attributes. After this is done, it is possible to map a UDP to an attribute using the mapping processdescribed above. Configured mappings allow thesystem to read and/or write values between the UDPand the attribute.Usage of attribute mapping is intended for singleinstances of a block or when all block instances havethe same attribute values. It is not possible for multipleblock instances to be mapped to separate UDP’s. Manycompanies have one instance of a title block in a given.dwg files. Occasionally, there are companies that use multiple instances of a title block in a single file. In these cases, the attributes often share the same values. An example is a drawing file that contains three borders of different size. Each border uses the same title block with attributes. The attributes for Customer Name, Engineer, Project Number, etc. will share the same value for all instances. Such attributes that share the same value may be mapped to a UDP. Attributes like Border Size will have a unique value for each block instance. Therefore, Border Size should not be mapped to a UDP in Vault.AutoCAD MechanicalAutodesk® AutoCAD® Mechanical software (ACM) supports three distinct sets of properties, all ofwhich may be mapped to Vault UDPs. The three ACM property sets are: file, assembly and component. See the ACM documentation for details about the intended use and differences between these properties.Vault file properties may map to ACM file properties and Vault item properties may map to ACM assembly and component properties.It should also be noted that ACM assembly and file properties having the same name, should not be mapped to the same Vault UDP.AutoCAD ElectricalAutodesk® AutoCAD® Electrical software (ACE) supports both file and BOM properties. ACE BOM properties may be mapped to Item properties. ACE utilizes properties located in .dwg’s,.wdp’s and associated databases. ACE properties are exposed to Vault in four ways:First: Ordinary DWG™ file properties and block attributes may be mapped to Vault File objects. The majority of these mappings support bi-directional mapping. Creation of these mappings is described in the Mapping section of this document.Second: WDP properties support mapping to Item properties. They also support bi-directional mapping. Creating a mapping with WDP properties requires the AutoCAD Electrical Content Source Provider. The provider isspecified in the second columnof the image at the right. Thisprovider is automatically setwhen a file of type .wdp isselected under the File Propertycolumn. If an associated .wdlfile has been created both theline number and the alternateproperty name will automaticallyappear in the list for selection.You may select the line numberor the alternate display name tocreate the mapping. All wdlproperties will appear in the listof selectable properties; it does not matter if a value is present.Third: Component BOM properties may be mapped to Item properties. This includes properties like:Catalog Number, Component Name, Component Type, Electrical Type, Equivalence Value & Manufacturer and more...To create a mapping to a component BOM property, create a new UDP and associate it to Items. Then on the Mapping tab create a new mapping, making sure the first column Entity is set to Item. Under the File Property column, browse and select any file that contains the property to which you will create the mapping. Some properties require that a value exist or the property is not available for selection in the list.Reminder: When creating new properties it is best to associate them to a category which will automatically associate them to the files and/or items where the property should appear. If this is not done, the property will have to be manually associated to the file or item.Fourth: Reference Designator properties, when mapped will appear in Vault as optional data on an Item BOM. There are eighteen Reference Designator properties available:INST, LOC, TAG, DESC1...3, RATING1 (12)These properties may be mapped to an Item BOM using the DWG content source provider.To create a mapping to a Reference Designator, create a new UDP and associate it to Reference Designator. Then on the Mapping tab create a new mapping, ensure the first column Entity is set to Reference Designator. Under the File Property column select the dwg containing the Reference Designator to which the mapping needs to be created. All Reference Designators are available for selection in the list without requiring a value.Properties(Historical)A handful of properties have duplicates having the same display name with ‘(Historical)’ appended to the end: State, Revision Scheme, Property Compliance, Lifecycle Definition, Category Name & Category Glyph. These ‘historical’ properties exist solely to retain a record of the values when a configuration change alters the value of the non-historical properties. In other words, the ‘historical’property will always contain the value as it existed when that version was created. This situation arises because these properties may have a new value due to a configuration change, even though a new version is not created.A policy change is a good example of why these historical’ properties exist. An organization may have released documents that use the property Vendor. Currently the policy on the property Vendor does not require a value. The administrator modifies the policy ‘Requires Value’ to require a value. After the automatic compliance recalculation, any existing documents (including released documents) with the Vendor property and without a value will have a new PropertyCompliance value of non-compliant. PropertyCompliance(Historical) will retain the value of compliant. MigrationThe property features of Vault 2011 are a significant enhancement. A feature overhaul of this scale poses challenges for migration. Most prominent is the calculation of property compliance. In some migration cases, the compliance calculation will require additional information beyond that which was stored in Vault 2010 or earlier versions. Performing a Re-Index will resolve the majority of these cases. It is highly recommended that a Re-Index is performed after migration. A Re-Index using the option for Latest and Released Versions Only is sufficient. In rare cases, a re-index may not restore compliance values to pre-migration values. If this occurs, manual adjustment to the property configuration may be required.File Index PropertiesFIP’s are no longer supported. The values contained by the FIP’s will remain available in UDP’s. There are multiple FIP configurations that require unique migration rules, listed here:FIP with no mapping or grouping: this ordinary FIP exists in Vault 2010 or earlier, without any mapping to a UDP and is not a member in any group. Migration will create a UDP, which will be mapped to the file property from which the FIP was created.FIP mapped to a UDP: upon migration, the UDP is carried forward and the FIP is removed from Vault. The value remains available in Vault through the UDP.Grouped FIP’s: property groups are migrated to a UDP having the same name and are mapped to the sources of all the grouped FIP’s.Bi-directional MappingsNew to Vault 2011 is the ability to create Bi-directional property mapping. In previous releases, a mapping was either Read or Write. Because of this change, a UDP that has only Read mappings may not be modified. An example is a UDP that is mapped to Read its value from the file property Creation Date. It makes no sense to write a value back to Creation Date.After migrating to Vault 2011, property mappings that were previously Read will be changed to Bi-directional. If the mapped source does not support input of a value, like the Creation Date example above, the mapping will not be changed and will remain Read. UDP’s that have multiple mappingsthrough the same Content Provider may, under specific circumstances, become non-compliant. If this occurs, it may be necessary to alter the configuration to restore compliance.An example:Vault 2010 or any previous version has a property configuration where two or more fileproperties are mapped as Read into the same UDP. This can occur when companiesmerge or when file property name standards change. For the Read mappings of theconfiguration below, equivalence is calculated on the highest priority mapping, which isEng; the mappings to the other properties are ignored.Upon migration to Vault 2011, Read mappings are converted to Bi-directional (shown below.). For the Bi-directional mappings of the configuration below, equivalence iscalculated between the UDP and each file property that exists in the file. In most cases, only one of the file properties exists in any given file, which will result in the UDP being flagged as compliant.If two properties exist in a file both will be considered for equivalence. If either file property has a value that does not match the UDP it is flagged as non-compliant.Enabling the Create option on a mapping will force equivalence calculation on that mapping even when the property definition does not exist in the file. When the property definition does not exist in the file, each mapping with the Create option set to Off is ignored for equivalence calculation.Autodesk, AutoCAD, and DWG are either registered trademarks ortrademarks of Autodesk, Inc., in the USA and/or other countries. All otherbrand names, product names, or trademarks belong to their respectiveholders. Autodesk reserves the right to alter product offerings andspecifications at any time without notice, and is not responsible fortypographical or graphical errors that may appear in this document.© 2010 Autodesk, Inc. All rights reserved.。
Vault工具使用指南说明书
IM462271Seven Steps to Building the Ideal LifecycleMike ThomasTechnical Services Manager - Prairie MachineDescriptionThe ideal lifecycle is possible. Everyone can manage change the way they want—and, in fact, they do. Because, the way you manage files now, regardless of whether you like it or not, is what you choose to do. To move past the basics of file management into the area of drawing revisions, approvals, security, and advanced property management, you need to deal with lifecycles. In this class, we’ll look at Vault lifecycles and help you decide which is the best course of action. This class will introduce you to the powerful tools that are available in Vault Workgroup and Vault Professional for revision management, approval workflows, and engineering change orders (ECOs). Learn how categories are used to control the flow of your data and how versions and revisions are intertwined. We’ll also cover how to apply different revision schemes and how to initiate and track change via a change order.Speaker(s)I have been using AutoCAD since r13, cut my solid modeling teeth on Mechanical Desktop, and have been using Inventor since before it was known as Inventor. Data Management has always been a big part of my professional life, for the most part with Autodesk Vault. I’ve been utilizingVault for data management for as long as its been an Autodesk product.LifecyclesOur drawings and models are the language of engineering and manufacturing. It is how we communicate with others. It is how we go from concept-to-design-to-manufacture. How we manage this language is as important as the documents themselves.It is important to maintain a history of a document (including drawings) to track what has changed, when it changed, and hopefully why it changed. This history aids in making better decisions, provides crucial customer information, and provides the means to go back to a previous version. From Vault’s help: “A lifecycle definition is an engine that can be configured to automatically assign security, behaviors, and properties to Vault objects based on where the object is in the life of the design process.”The 7-steps to building the ideal lifecycle:1. Build Your Properties2. Add a Category3. Define the Rules4. Define the Revision Schemes5. Build the Transitions6. Make it Secure7. Track the ChangeIf you are using Autodesk Vault Basic you will not have access to the lifecycle engine. Vault Basic only provides version control, no tools to manage the change. Vault Workgroup and Vault Professional provide the tools for managing changeThe lifecycle engine is available for files and folders, and additionally within Vault Professional custom objects and items.Property AdministrationThe Oxford Dictionary describes Properties as meta data, a set of data describing and providing information about other data. In Vault, properties are meta data describing your data in Vault.Properties are available for files, folders, items (Vault Pro), and custom objects (Vault Pro). You associate with entity classes the property is available. Mapping determines where the property gets its information from.When files are checked into the vault, only the properties that are set enabled are automatically extracted and indexed by default.Create a new user-defined properties (UDP):• In the Property Definitions dialog select New • Specify the Name• Select the Property Type• Assign the UDP to one or more Categories• Use the Settings to optional further configure the property • Optional configure MappingCategoriesWhat are Categories?Building CategoriesDefine the RulesRulesUse Rules to define conditions where objects automatically assign to a category based on the object’s properties. For example, with Files, you could adjust the category manually or establish rules to assign the category automatically based on properties of the files.Figure 3: Assignment RulesCreate new rules to enforce how files, items, and custom objects are assigned to categories. Start by setting the Name and selecting the Category to assign it to the new rule.In the condition variables area, the Property, Condition, and Value lists are displayed. The property list shows the indexed user-defined and system properties for the vault that are in use. The conditions available in the condition list are determined by the selected property. The variable entered in the value box is compared to the property using the selected condition.Revision SchemesWhat is a Revision?Within Vault, you revise your objects by BUMPING the revision. Use Change Revision to grab the next available value in the current revision scheme. Within the dialog, select the revision level to bump to (i.e. are you going from 1 to 2 or 1 to 1.1) and Vaultautomatically getsthe next available value.Figure 4: Change RevisionRevision SchemesRevisions Schemes define the format and sequence of the revision. They define the format of the primary, secondary, and tertiary revisions. The scheme forces the users into predefined values, so they can not stray away from the standard.For example, the Standard Numeric Format starts at 1 and increments by 1, not skipping any numbers.Build (and modify) Revision Schemes within the Vault Settings(Behaviors tab):1. Name the new scheme and provide a description2. Select the Categories in which the scheme is available3. Assign the three Scheme Formats (primary, secondary, and tertiary) and the Delimiter4. Create Scheme Formats (as required)The Scheme Definition is simply the list of values available to the Revision.1The American Society of Mechanical Engineering (ASME) standard that defines the practices for revising drawings and associated documentation, includes the methods of identification and revision documentation.StatesThe State identifies the object’s status within the lifecycle. The number and type of states is based on the applied lifecycle and its associated Transition Rules.Figure 5: Change StateFolders are like files except youCategory, you can adjust the Stateforce you to perform a state change on the files contained within the folder before changingthe state.The State determines:•The Property Criteria requirements (Compliance) that must be in place before the state change can occur•The Actions that happen during the change (i.e. revision bump)•The Security enforcing who can make the change and who can see the file in the stateTransitionsFigure 6: Lifecycle Definition - TranstionsThe transition manages:• Criteria – the property details determining when a state transition can occur. For example,a file unable to transition to the next state without a value in the Initial Approver property. • Actions that occur automatically when the transition is made (like a revision bump) • Access control permissions – who can execute the transitionSecurityFigure 7: State SecurityThere are three ways to define the security of an object:•Object-based security – security is derived from the object settings. This is the default option.•State-based security – available when a state-based ACL exists and is combined with object-based security.•Overridden security– available when a state-based ACL is overriding object-based security, or when the administrator sets a manual override on the object.Tracking ChangeWhat are Change Orders?When a design requires a change or modification you want to put controls in place to help manage the change. A record of the changes provides a history trail of what was changed, why it was changed and when the change occurred.Vault Professional provides Change Orders to capture the changes and manage the change as the modifications are completed, reviewed, and released to be manufactured. The change order is the historical paper trail of the why, how, when, who, and what of the design modificationsC HANGE O RDER W ORKFLOWCreating New Change Orders (Quick Procedure)1. Locate the item or file requiring the change2. Create the Change Order (right-click add)3. Describe the change required4. Markup the drawing (as required)5. Assign the Routing6. Submit itChange Order AdministrationThe Change Orders tab contains options for controlling change order behavior, configuring the markup folder, and managing change order link properties.C HANGE O RDER A DMINISTRATIONIn addition to the Change Orders tab, define numbering schemes (Behaviors tab) to auto-label the change orders.。
Autodesk Vault 安装、配置和数据加载讲座说明书
Autodesk® Vault: Installation, Configuration, and Data LoadingSpeaker: Brian D. Verboort – M2 Technologies, Inc.PL1943 Class Description: In this class, we will cover the steps that are required to successfully install, configure, and populate Autodesk® Vault software to manage your data. We will introduce concepts, workflows, tools, and best practices. We will also discuss common mistakes that businesses make when planning and executing a Vault implementation.Learning ObjectivesAt the end of this class, you will be able to:∙Learning objective 1Plan a Vault installation∙Learning objective 2Install Vault∙Learning objective 3Configure Vault∙Learning objective 4Populate and load VaultAbout the SpeakerAdd edited Speaker BIO as per AU website [Arial 10]Add eMail address (optional)1). Plan a Vault installationAcquire Engineering-Related Data Flow (Departmental)∙Purchasing∙Mfg Production∙Sales/MktgFigure 1Existing Design/Engineering Data & Workflow ∙Data Storage Folder Structure∙Data/Document Types (XLSX, DOCX, PDF, GIF, TIFF) ∙Data Footprint (in Mb/Tb)∙Data Folder Permissions and groups∙Document Creation Process/ProcedureFigure 3∙Document Key Property DataFigure 4∙Document Release Process/Procedure∙Document Revision & Editing Process/ProcedureFigure 5∙Document Revision Schemes (A, B, C… X1, X2, X3)∙Document Numbering Schemes (Document Numbers, Part Numbers & Sequences/Logic)Schedule Implementation & Education∙Identify vault users: see "Vault User List/Roles” Matrix (Figure 2)∙Schedule Vault User Training Dates by role (Administrator, Author, editor, reviewer, consumer)Review Vault Server Readiness∙Filestore, database and backup locations∙Acquire & Review server specificationso OSo SPso Hotfixes∙Acquire System information "systeminfo.exe" and/or msinfo32 > File > Save (or use a PC Audit/reporting tool like Belarc: )∙Compare server specifications to Vault Server Requirements:/adsk/servlet/ps/dl/item?siteID=123112&id=18781512&linkID=9261340∙Size a new Vault Server using provided Guide:/Vault/enu/Help/Help/0206-Autodesk206/0207-Deployme207/IBM_Vault_Sizing_Guide∙Review list of Programs installed & Services (conflict/performance issues)∙Review and archive Server OS Event Logs for errors (Application, Security & System) ∙Review and document Server NIC Specs, MAC ID's, Settings & configurations (all NIC's) ∙Review & Document Inter-Server & Client-Server Performance-TRACERT from Vault Client system(s) to Vault Server(s) (ADMS/IIS & SQL)∙Review Vault Server & Client Firewall configurations∙Document above∙Confirm MS SQL Server Installation media availability∙Review SQL SP Level (if existing SQL)∙Review/define Vault (ADMS) Application Installation location (Server Name & System Volume)∙Review/define Vault MS SQL Database Location (Server name & System Volume) ∙Review/define Vault Filestore Location (Server Name & System Volume)∙Create/Provide admin account access (Domain Admin if required by Multi-server Configuration) for:o Application Installation(s)o Windows OS Configuration (IIS, Anti-Virus, etc...)o Service account for scheduled backups & SQL Maintenanceo Anti-Virus Configuration∙Review/Confirm/Notify "Multiple Server Reboots" requirement∙Review and define "Shared resources" folders and permissions∙Review and define Vault Backup Location and folder permissionsReview Client Workstation Readiness∙Review Access to Administrator account∙Review & Document Vault Client:o NIC and related notification settingso OS Versiono OS Service Pack levelo Microsoft Update status (pending updates)o Web Browser & Versiono Firewall settings (configure/disable)o Anti-Virus settings (configure/disable)∙Compare Vault Client specifications to Vault Client Requirements:/adsk/servlet/ps/dl/item?siteID=123112&id=18781512&linkID=9261340Review CAD Resources/CAD Management∙Determine/Define Centralized (shared) CAD Resources∙Identify/Define "Gold" copy of CAD Templates (Inventor, Revit, AutoCAD/M/E, Etc.) ∙Identify/Define Centralized Inventor CCL & Styles Share (location)∙Review and define shared folder Groups/Permissions∙Copy/Move Gold Templates, styles & CCL's to centralized share∙Define Preset IV Application Options (.XML)∙Create & Configure Vault-Specific Inventor Project (.IPJ)2). Install Vault∙License & Software Installation Preparation:/Vault/enu/Help/Help/0206-Autodesk206/0210-About_Yo210/0238-Installi238/0239-Autodesk239o Download Installation Package from your Autodesk Subscription Site:/adsk/servlet/ps/dl/item?siteID=123112&id=17293000&linkID=16831209o Place Installation Package on the server HDD where the deployment will be created/Hostedo Extract the installation media to the local HDDo Acquire software license for type of Software license (i.e. Network or stand-alone) /register▪Vault Basic License: None▪Vault Workgroup (VW), Vault Collaboration (VC) & Vault Professional(VP) are Network Only (ASP)∙License Manager Installation and Configuration:o Adjust Windows Firewallo Install FlexLM License Utilityo Acquire NIC MAC Addresso Acquire Vault Network license file (See above)o Configure FlexLM using Serviceso Test License Server Status/adsk/servlet/ps/dl/item?siteID=123112&id=13503006&linkID=9240617 o Merge multiple License files (if required)/adsk/servlet/ps/dl/item?siteID=123112&id=8057761&linkID=9240617 o Purpose and format of the contents in the LICPATH.LIC file/adsk/servlet/ps/dl/item?siteID=123112&id=2887766&linkID=9240617∙Vault Client Deployment Creation:o Identify Vault Clients/Users to deployo Create Vault Client Deployment/Vault/enu/Help/Help/0206-Autodesk206/0300-Autodesk264/0265-Network_265/0274-Creating274/0275-Create_a275o Include desired CAD & Office Application Add-inso Append available Vault service packs and/or hotfixes/adsk/servlet/ps/dl/index?siteID=123112&id=2334435&linkID=9261341o Test Vault Client Deployment InstallationFor Alternate Methods of Deploying Software, reference:/Vault/enu/Help/Help/0206-Autodesk206/0300-Autodesk264/0278-Alternat2783). Configure Vault∙Vault Backup Creation/Testing/Trainingo Create backup script(s)o Define backup locationo Test backup script(s)o Review/train IT on backup requirements, script & Locations /Vault/enu/Help/Help/0097-Administ97/0098-Autodesk98/0099-Manage_V99/0100-Backup_a100∙Configure Job Server for visualization Files (VW, VC & VP only)o Enable Job Server (Dedicated/Underutilized CAD Workstation)/Vault/enu/Help/Help/0097-Administ97/0188-Job_Serv188o Enable Job Processor on all CAD clients as temporary "farm" for Initial large data load/Vault/enu/Help/Help/0001-Using_Va1/0031-Manage_t31Figure 6∙Install or Extract & Attach Content Center libraries (Inventor)o Vault-Hosted vs Desktop Content/Vault/enu/Help/Help/0206-Autodesk206/0210-About_Yo210/0256-Install_256/0257-Install_257o Extract & Attach (Content Center Administrator role required)/Vault/enu/Help/Help/0097-Administ97/0098-Autodesk98/0109-Manage_C109∙Create MS SQL Server Maintenance plano For Full SQL Server using SQL Server Management Studio:/Vault/enu/Help/Help/0097-Administ97/0098-Autodesk98/0020-Perform_0o For SQL Server Express (go to "Create a Maintenance Script for Microsoft SQL Express"):/Vault/enu/Help/Help/0097-Administ97/0098-Autodesk98/0020-Perform_0∙Configure vault Environmento Create Indexed Block Attributes/Vault/enu/Help/Help/0001-Using_Va1/0054-Understa54/0056-Add-in_-56/0063-Extracti63o Create Users & Groups/Vault/enu/Help/Help/0097-Administ97/0098-Autodesk98/0118-Manage_U118o Create Folder Structure▪Designs▪Libraries▪Content Center Files (Inventor)▪CAD Resources/Vault/enu/Help/Help/0001-Using_Va1/0003-Essentia3/0010-Create_a10o Create Categories (VW, VC & VP)/Vault/enu/Help/Help/0097-Administ97/0127-Client_A127/0149-Category149o Create Rules (VW, VC & VP)/Vault/enu/Help/Help/0097-Administ97/0127-Client_A127/0149-Category149/0150-Category150o Create Lifecycle Definition (VW, VC & VP)/Vault/enu/Help/Help/0097-Administ97/0127-Client_A127/0151-Lifecycl151o Create Revision Schemes (VW, VC & VP)/Vault/enu/Help/Help/0097-Administ97/0127-Client_A127/0147-Revision147o Create Numbering Schemes (VW, VC & VP)/Vault/enu/Help/Help/0097-Administ97/0127-Client_A127/0143-Numberin143o Map Properties/Vault/enu/Help/Help/0097-Administ97/0127-Client_A127/0160-Properti160∙Deploy Vault Clientso Deploy Vault Explorer Clients to defined User listo Distribute wiki videos to users/Vault/enu/Help/Videoso Distribute Vault Web Client URL to defined Consumer list (VC & VP)http://<servername or IP Address>/AutodeskDM/WebClient/Vault/enu/Help/Help/0001-Using_Va1/0048-Autodesk48∙Load/Vault CAD Resources:o Map to shared folder (see "Map a Vault Folder to a Different Working Folder") /Vault/enu/Help/Help/0001-Using_Va1/0021-Manage_F21 o Copy, Migrate & check-in library fileso Copy, Migrate & check-in templates fileso Copy, Migrate & check-in styleso Get latest version to Share/Vault/enu/Help/Help/0001-Using_Va1/0003-Essentia3/0012-Get_Chec12∙Workflow & Data Load Testingo Set Default Inventor Project file (Inventor)/Vault/enu/Help/Help/0097-Administ97/0127-Client_A127/0129-Administ129/0131-Autodesk131o Create a new "Testing" vault/Vault/enu/Help/Help/0097-Administ97/0098-Autodesk98/0099-Manage_V99/0102-Create_a102o Export "Vault" Configuration CFG file/Vault/enu/Help/Help/0097-Administ97/0098-Autodesk98/0117-Manage_W117/1089ImportandExportConfo Import configuration CFG file into "Testing" Vaulto Load sample data using Autoloader/Vault/enu/Help/Help/0097-Administ97/0193-Autoload193#GUID-EA9B2552-30B9-4789-9A5E-6580B8648981o Review for Indexed Block Attributeso Review for Categories (VW, VC & VP)o Review for Rules (VW, VC & VP)o Review for Lifecycle states (VW, VC & VP)o Review for Revision Schemes (VW, VC & VP)o Review for Numbering Schemes (VW, VC & VP)o Review for Job Server Published Visualization Files (VW, VC & VP)∙Education Deliveryo Deliver Role-Based Vault Explorer training: VE (Administrator, Author, editor, reviewer, consumer)o Deliver Vault Web Client training: (VC & VP)4). Populate and Load Vault∙Load Data using Autoloader:/Vault/enu/Help/Help/0097-Administ97/0193-Autoload193∙Notes:o Autoloader requires Vault Administrator Role.o Autoloader uses an existing project file if one is found in the folder being loadedo Autoloader does not work with "Vault" Project file types.∙Tips:o Set Vault Categories for files using Rules prior to data load (see configuration)o Set default lifecycle state for a category to “Released” for Autoloader... then change it to Work in Progress for production.o Use Autoloader as a diagnostic tool to check data integrityo Use Autoloader on multiple systems as a "Farm" for large data uploads. See "Multiple Instances of Autoloader" topic here:/Vault/enu/Help/Help/0097-Administ97/0193-Autoload193o Break data load tasks into pieces.▪Consider following a "Project" or "Product-Line" strategy whenAutoloading data▪Consider using a "quarantine" folder or category for data that needsfurther review.▪Consider granting temporary "Administrator" role to Engineer/Design staff to load the active products/projects they are familiar with. Additional ResourcesVault Blogs:∙/∙/Vault-Specific White Papers:The following documents can be very helpful and can be found at the link below: ∙-Best Practices for Implementing Autodesk Vault∙-Best Practices for Loading Autodesk Inventor Data into Autodesk Vault∙-Migrating Autodesk Inventor Data into Autodesk Vault∙-DWF Settings in Autodesk Vault/adsk/servlet/index?siteID=123112&id=9720013&linkID=9261340 CAD Manager Resources:∙Inventor CAD Manager and IT Manager Resource/Inventor/enu/2013/Help/0000-Installa0/0177-CAD_Mana177∙Inventor CAD Manager Fundamentals (best practices)/Inventor/enu/2013/Help/3877-CAD_Mana3877 -Keep data current... Migrate your data following each upgrade-Configure the company standards/styles using the Styles Editor on a shared server -Define user Application Options and export to your shared server-Create templates and place on a shared server (and add to Vault)-Set up Vault project to create "Content Center Files" in a shared server folder.∙Vault Advanced Configuration guide:/Vault/enu/Help/Help/0206-Autodesk206/0264Advanced_Configuration ∙To Upgrade an existing Autodesk Vault:/Vault/enu/Help/Help/0206-Autodesk206/0261-Upgradin261。
Autodesk Vault 软件升级指南说明书
Vault GPS: Make All the Right Turns During Your Vault UpgradeIrvin Hayes Jr. – Autodesk, Inc.PL5843-P Upgrading your replicated Vault software environment to a new release of Vault software shouldn’t be an intimidating endeavor. Building an understanding of what actually happens when clicking the install button is crucial to having confidence in your upgrade plan. This class will cover existing and newly supported methods for upgrading your replicated Vault software installation, and you will leave armed with the knowledge of what is actually happening in the background with SQL so that you can proceed with confidence.Learning ObjectivesAt the end of this class, you will be able to:• Understand the importance and role that SQL plays in a Vault software upgrade• Understand the out-of-the-box procedure for Vault software upgrades of replicated environments• Understand the alternate snapshot procedure for Vault software upgrades of replicated environments• Learn how to set yourself up for a successful migrationAbout the SpeakerIrvin Hayes Jr. is a product manager for the data management group at Autodesk in Novi, Michigan. Irvin has worked at Autodesk for seven years starting in product support and as a user experience designer. Irvin is a Microsoft® Certified Professional, and has been working in the information technology field for more than 21 years.Table of ContentsLearning Objectives (1)About the Speaker (1)Introduction (3)What happens with a normal vault upgrade? (3)How it works (3)Understanding the obstacles (5)Planning to overcome the obstacles (6)Using Alternate Snapshots (8)How it works (8)Understanding the obstacles (12)Planning to overcome the obstacles (12)Setting yourself up for success (12)Closing (13)IntroductionUpgrading your replicated Vault software environment to a new release of Vault software shouldn’t be an intimidating endeavor. Building an understanding of what actually happens when clicking the install button is crucial to having confidence in your upgrade plan. This class will cover existing and newly supported methods for upgrading your replicated Vault software installation, and you will leave armed with the knowledge of what is actually happening in the background with SQL so that you can proceed with confidence.What happens with a normal vault upgrade?How it worksSome of the information in this section is taken from the Autodesk Vault Upgrade guide. Please refer to the guide for additional information as this class will not cover everything in the guide. As called out in the guide, the upgrade process for an Autodesk Vault environment is comprised of 5 steps:1. Validating a Backup2. Upgrading SQL3. Upgrading Vault Server4. Upgrading Clients5. Creating a BackupAutodesk recommends that every Vault upgrade starts with a validated backup. This validation will ensure that if the upgrade process fails, there is a backup that can be restored. It is also recommended that you have a test environment that is close to your production environment as possible. The reason for this is to allow you to better estimate how long the actual migration may take. You should add a buffer to the migration time so that you can report back your estimation of downtime to the reset of the business. Also, testing your backup and migration will help you identify potential pitfalls prior to executing the migration in the production environment.Prior to the upgrade, you may want the various business units to sign-off on the migration. Itis recommended to create a document containing the key features that the business uses. Testing workflows, customizations and integrations should all be done the test environment to make sure that everyone understands the changes and can be trained prior to upgrading the production server.Using the test environment provides a safe option to experience the migration process and discover unexpected hurdles. Although this process takes time it can, in the long run, save time and stress by avoiding impact to the production environment. You can use this environmentto create documentation that is necessary for a successful migration. This can come in handy in case something happens to any of the key players involved with the migration. This will be revisited later.Now let’s move on to the Upgrading Vault Server step. Before we can look at a replicated environment, we first must understand the single site environment. This single site environment is made up of the database (SQL), Autodesk Data Management Console (ADMS) and the Autodesk Vault File Store (AVFS).As called out in the Autodesk Vault Upgrade guide, you need to pay attention to how many releases you are skipping over in your migration. For example, if you are going from 2011 to 2015, you will need to go to some intermediate release. In the example, you would need togo from 2011 to 2013 followed by 2013 to 2015. Autodesk doesn’t allow you to migrate more than 2 releases apart. I would recommend getting to the appropriate service pack or hotfix level prior to opening up the ADMS Console during the migration process. Once you open the ADMS Console, the migration will begin. What is going on at this phase is that the databaseis being prepped for the current release. This involves updating stored procedures, tables and restructuring data where necessary.Now let’s look at a replicated environment. It does consist of the same pieces that a single environment entailed. However, it allows for multiple SQL locations which are known as Connected Workgroups. Believe it or not, upgrading a replicated environment isn’t that difficult. You must first upgrade the main Workgroup, also known as the Publisher Workgroup, by upgrading an ADMS machine within the workgroup. This starts the process of migrating the Publisher SQL databases. Once the SQL databases is properly updated, snapshot are created.A snapshot is a read-only view of a database at the time the snapshot was taken. This snapshot is then consumed by the SQL subscriber machines. Once the snapshot is consumed by the subscriber, the environment is now ready for use once all the ADMS / AVFS machines within that workgroup have been updated accordingly with the appropriate software release. It is best to upgrade all the ADMS machines in the subscriber workgroup first prior to moving onto the AVFS machines.Understanding the obstaclesWe recently worked closely with a customer to help them through a rather large migration process. Our goal was to help identify problems that may arise during the migration and also to ensure that the migration completed in a timely manner. In order to have success with this venture, we needed to collect various information from them. In particular, we needed the following:• Their databases• A detailed mapping of their network• Hardware specificationsOnce we had this information, we set up a lab environment close to what they have so that we can better understand the pitfalls. Along with us running a series of tests in our lab they were running similar tests in their lab. This was beneficial since it allowed us to compare notes and focus on various differences within the environment.This is a smaller example of their Vault environment.During our first couple migrations we noticed that there was considerable differences in the timings between the environments. This made us focus on the hardware. Since the migration process is very read/write intensive, we started to focus on the hard drives. We needed to look at what partitions the database were on and the type of RAID configuration. Another area of focus was on memory since SQL utilizations as much as it can (you can limit the amount within SQL itself). We monitored both of these activities use Performance Monitor to help us get a better understanding of what is going on. We also utilized a utility called Wireshark to get an understanding of how much data was going over the network. Upon investigating all avenues, it was determined that we were sending too much data over the network in terms of the snapshot. Remember the snapshot is the data that the publisher creates post migration and is updated from time to time based on the SQL schedule. There was obstacles with the hard drive and memory but they did not impact the total migration time as much as the network traffic did.Planning to overcome the obstaclesNow that we understand the obstacles of the migration we were able to come up with solutions to get around them.The main obstacle was the network. We were able to overcome this obstacle by using the “Alternate Snapshot” solution which will be discussed in the next section.The hard drive can be handled by purchasing additional partitions or reconfigure the existing partitions. If you are going to reconfigure the RAID partition, it is highly recommended copying all data off the entire drive to another location prior to beginning the operation. As mentioned in the previous section, a migration has intense read/write operations. If you are setup up a RAID configuration, you need to make sure that it can handle a lot of read/write operations. You will want to pull out SQL’s temp database and log files to a separate partition. The main database should be on a partition that can handle a lot of read/writes. You will want to have the log files on a separate partition as well. Once you are satisfied with your configuration, restore your data accordingly. NOTE: The file store is not impacted by a migration and if you are running it on the SQL machine as well you will want it on its’ own partition.Depending on your current system, you will want to have a sufficient amount of memory in the system. If more memory is determined to be needed, prior to the migration may be the best time to upgrade it. This way it can be fully utilized during the migration process itself. The memory / processor upgrades is something that the business unit will need to determine if it is worthwhile now or if the budget is even there for the upgrade.We found that having the issues documented prior to the migration made the actual migration run smoothly. If you are working with Autodesk or a reseller during your testing phase and have issues, they can help you solve this problems in the test environment prior to migrating the production environment. A documented process also allows the migration process to be executed by anyone on the team.NOTE: Please contact your reseller or Autodesk to make sure that whatever is being deleted can be deleted. Autodesk or the reseller may have to create a special script in order to make the migration run smoothly.Using Alternate SnapshotsHow it worksSince we determined that the network is a problem for the size of the database we need to migrate, we need to look at the Alternate Snapshot method. The point of this solution is to allow you to move the snapshot from the publisher to the subscribers in a manner that you find conducive to your environment. For example, you do not want to have a 500GB snapshot going over a network that has bandwidth of 1mbs with a 200ms latency. Here are the steps for using the alternate snapshot:1. Wait for the migration and snapshot to be created on the publisher. This can view thestatus by opening SQL Management Studio, launch the Replication Monitor and select the database that you want to see the status on. You should see a dialog as shown below.2. Immediately after the snapshot is created, turn off the SQL job on the remote SQLservers using the SQL Management Studio3. Move the snapshots to the subscriber location4. Modify the agent to point to the Alternate Snapshot location. At the end of the commandline remove “ -Continuous” and add “ -AltSnapshotFolder D:\VC_Replication_Share\” where “D:\VC_Replication_Share\” is the local path of the “unc” folder.5. Reinitialize the SubscriberSelect YES to this dialog.6. Restart the Job7. Wait until the snapshot consumption completes. The status of this can be viewed in the dialog above and when it shows that it is complete.8. Stop the SQL job9. Set the synchronization setting back to Continuous10. Start the SQL job11. Wait until replication to get into steady state. The replication status on a database will show “Waiting 60 second(s)”.12. At this point, your subscriber is ready for useUnderstanding the obstaclesThe reason why we are doing the Alternate Snapshot is that the network has some sort of issues with it whether it is bandwidth, latency or both. This obstacle will still be there. Other obstacles could be around the delivery method used to get the data to the subscribers. The data could arrive and be corrupt. Maybe you sent someone on a plane to the location and somehow the drive was wiped. We will need a plan to overcome these.Planning to overcome the obstaclesWays to get around this would be use multiple methods to assure that data will arrive in a timely manner. If you decide to go with a zip method, you would want to test that the zip is indeed working properly prior to sending it via a device.Setting yourself up for successBefore we do the migration we definitely want to remember that we need to have a goodsolid backup plan which includes a backup and several test iterations in a non-production environment. You will want to make sure that your backups are proper and indeed cover everything in your environment. You never know what could go wrong during the migration.To quote Jonathan Landeros of Inventor Tales, “Should the worst happen, have a backup plan that includes having a backup to restore, instead of slipping out the back door before anyone notices!”. I cannot iterate this enough that you want to run multiple migrations prior to the day of the actual migration. Write out a preliminary migration plan. Take notes during your test migrations. Combine your initial plan along with your notes to create robust document in which anyone can use in case the need arises.Remember, you are the expert of your environment. If you are doing the migration yourself or are getting outside resources to help out, it is best to make sure everyone is aware of the details of the environment. You will be the best to predict slowness at particular workgroups. This knowledge can be used during the testing phase of the migration. Again, your environment should be as close to the production environment as you can make it. You can set up network emulators and such to give you a better idea on what will go on during the migration day. Just remember that during this process there will be down time. Your system will be unavailableto the business units while it is executing. But, you can limit the down time and impact to the business by planning accordingly.Have a plan for migration day. Make sure you have the who, what, where, when & how’s allin order prior to that day. Make sure that the team involved in the migration is lined up. It is worth mentioning that you may want to have backup people ready to go in case something happens on the day of migration. They need to know where they are going to meet (online / at the office). They need to know when to start. This could be during business hours or off hours depending on what your plan yielded. Make sure that everyone understands what their role is during the migration. Who is updating what servers and when are they being updated. With a good predictable plan your team will know where they are at during the entire migration process. This will lead towards a smooth migration.ClosingNow that we know what to expect during a migration we can go forward and have a successful migration.。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
Autodesk vault 软件为提高BIM深化设计室设计文件管理效率，故引入autodesk vault管理软件。
该软件能够通过集中地存储所有工程设计数据和相关文档，节省整理文件所需的时间，避免成本高昂的错误，更加高效地发布和修改设计。
Autodesk Vault 包含丰富的功能，其主要功能可以用以下简图表示：二、软件使用1、vault 版本Autodesk Vault 有四种版本，每个版本均已扩展以符合您的特定业务需求。
1.1 Autodesk Vault Basic ：Vault Basic 在一个中心位置安全地存储和管理数据，可帮助团队快速创建、共享和重用数字原型设计信息。
用户可以对Vault 中的文件执行基本的版本控制操作，并可以快速打包文件以便共享。
1.2 Autodesk Vault Workgroup :Vault Workgroup 通过在一个中心位置安全地组织、管理和跟踪数据，从而帮助团队创建和共享设计及工程信息。
这种易管理性可以启用工作组对数据访问和安全性的控制，并能简化各种准则下基于团队的设计。
用户通过Vault Workgroup 可以快速管理其设计以及实时跟踪所做的更改，因此他们无需付出额外的劳动就提高了生产率。
此外，Vault Workgroup 可直接在设计应用程序中实现生命周期和版本控制过程，这样不仅可以缩短周期时间，还能提高工程数据的质量。
1.3 Autodesk Vault Collaboration :Vault Collaboration 不仅具备了Autodesk Vault Workgroup 的所有功能，还新增了高级工具集，为管理员提供了管理大型工作组时所需的可扩展性。
用户可以使用包含的Web Client 与下游数据客户共享工程设计数据，并通过发布到Microsoft® SharePoint® 可扩展多个站点功能（使公司能够在分布式工作组之间同步设计数据）向扩大后的企业显示设计相关的信息，使数字模型的可抵达范围扩展到整个项目团队。
1.4 Autodesk Vault Professional :Vault Professional 可以安全地存储和管理工程信息、设计数据和文档- 缩短了从设计到构建以及生产的流程。
它包括多个站点工具，以将位置分散的工作组关联在一起，从而帮助整个设计团队协同作业并共享项目信息。
V ault Professional 可充分利用高级功能，它会为设计部门提供跟踪变更单、管理明细表（BOM 表）以及通过集成到专业企业系统来升级早期版本的Collaboration 所需的工具。
此外，它还支持多CAD 环境，这说明使用非Autodesk 设计产品的Vault 客户端在其整个生命周期内都可以汇总和管理设计数据。
2、软件安装和应用2.1软件安装2.1.1 Vault是对硬盘要求比较高的软件，不属于CPU密集软件，所以多CPU的运算速率等性能要求不高，2.1.2 Server端最好装在Winodws 2008 R2 服务器上，兼容性好。
2.2软件使用2.2.1服务器端2.2.1.1项目数据库创建创建流程：右击“V ault”-----”创建”-----输入项目名称-----选择项目库数据存储位置。
2.2.1.2用户创建1、用户创建流程：工具----管理-----用户----新建用户，用户信息表如右图所示。
2、针对以项目为组的设计，“角色”不用添加。
在“组”中选择本用户所参与的项目名称。
3、勾选“启用用户”，然后单击“确定”。
2.2.1.3用户组创建1、用户组创建流程：工具----管理-----组----新建组，组信息表如右图所示。
2、“角色”选择，针对普通建模人员，选择“文档编辑者（第2级）”即可。
3、“vault”项选择以上所创建的项目数据库。
4、组成员通过“添加”按钮将该项目参与建模的人员添加即可，然后点击“确定”。
2.2.2客户端2.2.2.1客户端登陆1、“身份验证”选择vault账户。
2、“用户名”、“密码”即为服务器端创建的“用户名”和“密码”。
3、“服务器”选择软件服务器端所装在的服务器的名称。
4、“vault”选项选择本次建模所用的数据库名称。
2.2.2.1工作文件夹（本地）工作文件夹是从服务器上下载文件到本地存储的位置，建议设置在C盘以外的磁盘。
设置流程：文件----设置工作文件夹-----选择文件夹----确定2.2.2.2 分类文件的文件夹创建创建流程：右击“Vault Explorer”，单击“新建文件夹”，输入文件夹名称。
最终一个项目的数据库文件夹如右图所示。
2.2.2.3设计文件的检入和检出检入流程：右击“策划文件”，单击“检入”，从弹出的对话框中先择文件，单击“确定”。
检出流程：法一、右击“策划文件”，单击“获取/检出”，从弹出的对话框中勾选需要检出的文件，单击“确定”。
法二、单击“策划文件”，在右边的区域直接点选需要检出的文件。
（如果需要某个文件的早期版本，可以从下面对话框中选择对应版本，如下图所示。
（该表中包含文件版本、创建人、检入日期、注释，便于对不同版本的信息进行跟踪）2.3 目前遇到的问题由于目前使用的是Autodesk Vault Basic 版本，不支持dwg文件和revit文件，如下图所示：鉴于以上两类文件是建模过程中核心文件，故需要将软件升级为Autodesk Vault Professional，以便于项目文件的管理。
附录：一Autodesk Vault Basic 2013 状态图标图标描述和所需操作如果未显示图标，则表示文件已存在于Vault 中，但是在计算机上没有该文件的本地副本。
用户可以快速识别哪些文件对Vault 来说是新文件。
使用“获取最新版本”来检索文件的副本。
文件位于Vault 中并可以检出。
工作文件夹中的版本与Vault 中的版本相同。
也称为“最新版本”。
文件位于Vault 中，并可以被检出，但是本地版本比Vault 中最新版本还要新。
通常，这意味着本地文件已被更改，而未检出。
如果要保存这些更改，请使用“不获取本地副本”选项检出文件。
文件位于Vault 中并且可以被检出，但本地副本已过时。
从Vault 中获取最新版本。
文件已检出，但计算机上并没有该文件的本地副本。
这可能在以下情况下出现：尚未设置工作文件夹、以前曾在未获取本地副本的情况下检出文件或者将文件检出到非工作文件夹的位置。
使用“获取最新版本”来检索文件的副本。
文件已检出，并且本地版本与Vault 中的版本相同，也称为“最新版本”。
文件已检出，并且本地副本比Vault 中的最新版本还要新。
这通常意味着在文件检出后对文件进行了更改，但是没有将其重新检入。
文件已检出，并且本地副本早于Vault 中的最新版本。
通常，这意味着启动的Vault的版本早于最新版本，并在将其检出后升级至最新版本。
文件由其他用户检出，而本计算机上没有该文件的本地副本。
使用“获取最新版本”来检索文件的副本。
文件由其他用户检出，并且本地副本与Vault 中的副本相同。
也称为“最新版本”。
如果其他用户未将更改重新检入Vault，通常会出现这种情况。
文件由其他用户检出，但是本地副本比Vault 中的最新版本还要新。
如果其他用户已将更改检入Vault，但仍使文件保持为检出状态，通常就会发生这种情况。
文件由其他用户检出，但是本地副本早于Vault 中的最新版本。
文件具有附件。
请展开树以查看附着的文件。
文件不在Vault 中。
Vault 中的库文件夹。
库文件夹是专门指定的，表示该文件夹中的文件在其他部件环境中使用时不打算进行编辑。
库文件夹中的文件具有两个明显特征。
∙它们不能被其他文件夹共享。
∙它们通常在共享的公用网络位置上存储和引用。
附件二有关Autodesk Vault 中可用角色的详细信息管理员始终对所有文件夹具有所有权限，并对服务器具有管理权限，包括ERP 权限和作业服务器权限。
资源中心管理员具有资源中心中的所有权限，且具有服务器上的库管理权限（在服务器控制台内）。
这些权限包括创建库、删除库、导入库、导出库和库的碎片整理。
此角色不适用于Civil 3D 用户。
资源中心编辑者具有资源中心中的所有权限，但没有服务器上的任何管理权限（在服务器控制台内）。
此角色不适用于Civil 3D 用户。
文档用户（Autodesk VaultWorkgroup、Collaboration 和Professional）仅具有对文件和文件夹的只读权限，包括作业服务器队列。
文档编辑者第1 级（Autodesk Vault Workgroup、Collaboration 和Professional）Vault 中基本文件添加和编辑权限，还可以添加或删除文件和文件夹的用户定义特性，但是不能删除文件和文件夹。
没有服务器上的管理权限。
文档编辑者第2 级（Autodesk Vault Workgroup、Collaboration 和Professional）Vault 中的所有权限，还可以添加或删除文件和文件夹的用户定义特性，但不具有服务器的管理权限。
文档管理者级别1（AutodeskVault Workgroup、Collaboration 和Professional）具有更改类别、生命周期和修订指定以及编辑用户定义特性的权限。
文档管理者级别2（Autodesk Vault Workgroup、Collaboration 和Professional）具有Autodesk Vault 内的所有文件、文件夹和自定义对象行为的管理权限，包括添加、删除和编辑用户定义特性的权限。
该角色不能创建行为定义。
自定义对象用户(AutodeskVault Professional)仅限自定义对象的只读权限。
自定义对象编辑者（第1 级）(Autodesk Vault Professional) Vault 中基本自定义对象的添加和编辑权限，以及添加/删除自定义对象的用户定义特性的权限。
无法删除自定义对象。
不具有服务器上的管理权限。
自定义对象编辑者（第2 级）（Autodesk Vault Professional) Vault 中的所有权限，还可以添加/删除自定义对象的用户定义特性。
不具有服务器上的管理权限。
自定义对象管理者（第1 级）(Autodesk Vault具有更改类别、生命周期和修订指定以及编辑用户定义特性的权限。
Professional)自定义对象管理者（第2 级）(Autodesk Vault Professional) 具有Autodesk Vault 内的所有文件行为管理权限，包括添加、删除和编辑用户定义特性的权限。