Library Panel - Default Footprints

When you place a part from the Libraries Panel if the part has multiple footprints listed in the database, then the default footprint in the design will be determined by the footprint assigned to Footprint Ref.

For example if the backend database has three footprint choices:

Footprint Ref        is   CAPC1005X55L (least)

Footprint Ref 2     is   CAPC1005X55N (nominal)

Footprint Ref 3     is   0402_RND (custom)

In the Library Panel these footprints are listed in alphabetical order with check mark applied to the default footprint.

Here is the database view using Parts Frontend

Note as shown in the Libraries Panel CAPC1005X55L is the default, because it is assigned to Footprint Ref.

Tips:

1) Prior to placing a part you can select the desired footprint the Libraries Panel..

2) After placement you add more footprints to a component if desired.

3) After placement use Tools > Footprint Manager to organize and select preferred footprints in the schematic, then update the PCB with the changes.

 4) If you only have access to the *.PCBdoc then use Find Similiar > PCB Inspector to select and change the footprints.

Moving and Sharing Parts

When the Parts download is unzipped the Frontend and Backend files are extracted to the same folder for ease of installation and quick evaluation.

By design the Parts database is portable and can be moved to another drive location.

To share the database with other users the Backend would be placed on a network drive and copies of the Frontend would be placed on each user's local machine.

If desired independent contractors (single users) can keep both the Frontend and Backend on their computer or laptop on a local drive.

Note the folder structure is important !

After moving the Backend Files you will need to link the Frontend and Backend.

Use the Frontend application 'Configuration' button to connect to the Parts database.

The Footprints and Symbols are stored in folders relative to the Database and DBLIB.

Set the Working Folder to point to the Footprints and Symbols Parent folder.

Set the Datasheets Folder to point to the Datasheets folder.

Edit and Install DBLIB Library

After moving the backend database in Altium you may need to edit the *.DBLib file.

For portability check the 'Store Path Relative to Database Library'. 

That's it !

PLM - Part 3: One too Many Dilemma

Links to Part 1 and Part 2.

PLM - Part 1: One too Many Dilemma
PLM - Part 2: One too Many Dilemma

In Part 3 of this series we will look at a real world example of a 'many to many' relationship that exist within a PLM system.

MCNs are Material Control Numbers, also known as company part numbers. 

PLM systems use MCNs. The MCNs control which Mfr Part Numbers are approved for use on a specific BOM.

Mfr P/N with many MCNs

First case has the same Mfr P/N used with more than one MCN.

As shown below a Samtec connector P/N BCS-115-F-D-TE is appearing in two MCNs in the PLM system. 

click on image to view
 

Why two MCNs for the same Mfr Part Number ?  

Let's take a closer look in PLM at the two MCNs.







The reason is simple. 

The P/N BCS-115-F-D-TE has been qualified and approved for use on two different BOMs.  

P/N BCS-115-F-D-TE is the only approved Mfr Part Number for the BOM that calls for MCN 206-0028-00. This MCN was created to restrict the use of Mfr P/Ns used on a specific BOM. 

MCN with many Mfr P/Ns 

This case is easy to understand because we can all agree that having alternate Mfr Part Numbers is a good thing.  

The alternate Mfr Part Numbers give manufacturing the ability to choose and buy approved parts for a build based on price and availability.

Conclusion

Many to many relationships are normally found in PLM systems.  Without these 'many to many' relationships it would not be possible to support the production line.

Most companies throw the engineering BOM over the wall to the company configuration control department, which has proven to work very well.

Then component engineers working with design engineers create MCNs with approved Mfr Part Numbers. In small companies the design engineers are the component engineers.

After the MCNs have been created in PLM, the engineering BOM is annotated with the MCNs, then the BOM is imported to PLM. 

The BOM with MCNs can be used to back annotate the CAD Library and Project Schematics.

If your company is using a PLM then you need a well designed CAD Library to deal with the 'many to many' relationships that are normally found in PLM systems.

There is a movement in the industry to create integrated solutions for CAD libraries and PLM systems. However I have not found any truly practical or affordable solutions, so I created my own solution which I call Parts.

The Parts database uses an incremented unique ID to create a solution for using CAD Libraries with PLM Systems.

That's It !