Helpful info

What information we would like to keep with components (component parameters)?

When it comes to component parameters, there are different approaches as to how much information to include. Some people like to include all of the parameters that are available on sites like Digi-Key or Mouser, while others prefer to only include the minimum amount of parameters needed to select a part for an application. For bill of materials (BOM) generation, the minimum parameters typically include the manufacturer, manufacturer part number, and description.

Why are component Lifecycles Important?

Tracking component items through their lifecycles is important for a number of reasons. One of the main reasons is so that you can build a set of production-proven component elements, such as symbols, footprints, and unified component items like CompLibs in Altium Designer, over time.

How do you handle symbol and footprint versions and updates?

It is best practice to have your symbols and footprints in a version control environment. However, managing file-based libraries with many parts in this way can be cumbersome, as updating even a single component in the library will result in the entire library being up-revved and it will not be possible to track which component was edited. To address this issue, it is recommended to split libraries into one library for each component. This structure is the preferred method for symbol and footprint management for database libraries, where there should be no parametric data as it should all exist in the database backend (such as an Access database or Excel spreadsheet). In some cases, it may be beneficial to include the value, voltage, and package as parameters only for passive components, so that the position of this text can be set when the symbol is placed.

Should templates be used to create new components, symbols, and footprints faster?

Using templates to create new components, symbols, and footprints can greatly increase efficiency. If your software has the capability to set up component templates, they should be used. If there is no component template file in your software, it is recommended to create templates for symbols and footprints, so that the font type, size, and mechanical layer usage do not have to be redefined every time a new component is created.

Should symbol naming be kept generic for organizing large number of components?

When organizing a large number of components, it can be helpful to keep symbol names generic. For example, a single symbol can be used for all standard 2-pin type passive components. For ICs, it may be best to use a complete or truncated symbol name that includes just the silicon portion of the part number, as some complete IC part numbers can be too long to display easily in a schematic. Footprint names should follow the IPC footprint naming standard, to avoid having multiple footprints with the same dimensions for a single package type (such as multiple SOT23-3 footprints).

Can you compare File Based and Database Libraries?

There are a few key differences between file-based and database libraries. File-based libraries are simpler to create, use, and manage, but database libraries offer a number of benefits. Database libraries are able to handle every aspect of component data management and can be managed using version control software like GIT or SVN. They are also better suited for managing lifecycle states and revision data, as they can be accessed and updated through a database backend such as an Access database or Excel spreadsheet.

Should lifecycle states be used as component parameters?

It can be helpful to include the lifecycle state (such as draft, prototype, production, or obsolete) as a component parameter, especially if your software allows for it. Database libraries that use an Access database or Excel spreadsheet as the database backend are particularly well-suited for managing lifecycle states and revision data.

Should users of component databases be configured with different levels of permissions?

It is important to have different levels of permissions for users of component databases, as this allows for better control over access to sensitive information. Version control systems can be used to manage user access and permissions, and it is critical to have at least one person with administrator privileges to manage the system.

 What is the best library type for small, medium, and large companies? 

 For small companies, using a database library may be sufficient for managing component data. However, mid to large sized companies may benefit more from using a database server to manage every aspect of their data. All company sizes can benefit from using a product like Altium 365 Pro/Enterprise to manage their component data. 

In conclusion, there are a number of factors to consider when managing component parameters and libraries, and the particular use case will determine which library type is best. However there are many advantages when using Database libraries other than the fact that they take more time to set up.