In a design environment with libraries that can be used by multiple designers, the integrity of libraries becomes increasingly critical. Company's structure should be set up in a way as not allow accidental or unapproved library modification or deletion.
Engineering manager should appoint a librarian who would be responcible for creating new symbols, modify existing symbols, creating new libraries, and deleting obsolete symbols.
This person would have a Read/Write access to all libraries and projects. The rest of the designers would have Read Only access to common libraries and also may have their own libraries as needed.
AVSnap provides simple facilities for copying symbols from one library to another. A designer would submit new symbol to the librarian for incorporation into existing libraries.
In addition to a controlled creation of libraries, it is important to control the creation of project files. A librarian or custodian should be appointed who has Read/Write access to the project directories. Users, who create projects, should have only Read Only access to the released projects. Once a project is released for assembly or installation, access to the project file should be READ ONLY. Revision number should track any changes to a project.
The easiest way to achieve this is to create the following directory structure on the company's server:
The "WIP Projects" folder is used for work in progress and every designer has R/W access.
The "RW projects" folder serves as the temporary storage space before project is moved to the "Released Projects" folder. Users are responsible for moving project files from the "WIP projects" folder to the "RW project" folder.
The librarian is responsible for moving project files from "RW projects" folder to "Released Projects" folder. With this structure in place, the safety of your project files is assured and project revision control becomes very simple.
|
Today's Tip 
