You have selected free tutorial of the AutoDesk for the Autodesk Certified User (ACU) :
Autodesk Inventor Certified User Exam - Imperial/Matric
Topics : File Management: Project File : Type of project: List the types of project files that can be created.
Project File Types
file management system in Inventor, which uses the extension of a project file (*.ipj). A project file are the configuration file set up and used to control the Inventor to creates and resolves file links, when you edit a files, how many old versions of the files to keep, and how Content Center files are stored and used.
For previous of Inventor, Autodesk offered two basic project types:
- single-user projects and
- multiuser projects.
The Autodesk Vault project has replaced the earlier multiuser project types.
Unless you have installed Vault, you have only one project type to choose from by default: the single-user project. The term single-user could be considered a misnomer because this project type is widely used by one-person shops and multiseat design departments alike.
Single-user does not mean that only one user can access the files in the project, as it might suggest; instead, it refers to the fact that there are no means of preventing files from being accessed for editing while another user is already editing the file. This can create a last-person-to-save-wins situation if care is not taken.
Single-User Projects among Multiple Users What happens when two users access the same file in a single-user project? Typically this is first noticed when one of the two tries to save the file. Inventor notifies the person trying to save that they are not working with the most current version and gives the other user’s name (depending on the network setup) so the first user knows what is going on. Inventor instructs the user that they must save the file using a different name to prevent losing the changes made.
Typically, at this point a conversation takes place to determine how to proceed. If it is decided that the first person is the one who needs to save changes, then the file this person was working on is saved using another name, the original file is deleted (or renamed as a reserve), and the other file is renamed to replace the original. In this way, the changes that were made to the original file are preserved.
Although this may seem like a terrible hassle, there are many design departments that use singleuser projects in a team setting effectively and only rarely run into this situation. More than likely you already have an idea of how often you and your colleagues handle the same files at the same time. But if you try to use single-user projects and find this situation happens fairly often, you should consider a true multiuser project.
Many design departments use single-user projects effectively in collaborative environments because of workflows that lend themselves to this type of project; others make it work by simply maintaining good communication among the design team.
For collaborative environments that require some safeguard against situations in which users could potentially save over one another’s work, using a multiuser project (Vault project) is recommended. Autodesk Vault is a data management application that, as the name implies, locks down files for their protection.
Once a file is in Vault, it must be checked out by a user to be edited. Vault typically resides on a file server where the entire design team can access it. When the file is checked out of the Vault server, it is placed on the user’s local machine for editing. The next user who comes along and attempts to access that file can access only a read-only version. Once the first user has finished editing, the fi le is checked back into Vault and automatically versioned. It is also important to note that Inventor installs with a default project setup. The default project is typically not used for production work because it is not fully configurable and will almost always lead to file resolution issues because it has no defi ned search path.
Creating a Good Data-Management Plan
A good data management plan is the key to using Inventor projects successfully. Using Vault will not resolve a poor project fi le or data management strategy. One part of a successful Inventor deployment is the hardware and network on which the software will run. It is important that the engineering group has buy-in by the IT group. You will need to discuss several issues with this group, including hardware for servers and workstations, the network setup (100BaseT or Gigabit), mapped network drives, and user permissions. A good server can be the diff erence between success and failure in your rollout. Although you do need to think about your fi le structure, don’t obsess over it. Most likely you will end up changing the structure at least a few times before you settle on a fi nal structure. Keep an open mind, and realize that if you have five people in a room discussing file structures, you’ll end up with fi ve diff erent ideas. Again, involve IT in your discussions. Finally, you
should designate one person in engineering to be the engineering administrator. This person needs to have administrative privileges on the engineering server or network share. IT may resist, but you have to keep pushing. This is important because you will need the ability to easily create, delete, and move files and folders without having to submit a help-desk ticket. Nothing will slow down a design process faster than having to wait for IT to make a simple change. Explain this need to your IT administrator, and most likely they will understand.