Install TortoiseSVN

Parts Frontend application supports Altium DBLIB and SVNDBLIB Libraries.

To integrate SVNDBLIB and the Parts Frontend you need to install the full version of TortoiseSVN, which includes the command line client tools.

Note the Parts Frontend is not a required.  The Parts Frontend is optional.

Installing TortoiseSVN

Link to Download for TortoiseSVN

click on images to view

Installation Tips:

Select Custom Setup and Select 'Do not close applications. A reboot will be required.'




Install TortoiseSVN with the command line client tools.

Then Reboot your PC.
It only takes an hour or less to migrate from DBLib to SVNDBLIB.

The instructions below assume that you have checked your Symbols and Footprints into a SVN repository and you are ready to switch to using a SVNDBLIB library.

The Library Folder is the Working Path to the user's local folder where copies of the symbols and footprints will be checked out from the SVN repository. 

The Working Path must be set in Altium Preferences. The Working Path should point to a local folder on the user's C: drive.


Example: (click on images to view)

If you are migrating from DBLib to SVNDBLIB, here is a clever trick to quickly setup the SVNDBLIB file. 

Copy your *.DBLib file and save the file as a *.SVNDBLIB file.

Open the SVNDBLIB file in Altium. The file should look very familiar, the only difference is the SVN Repository tab for the Database Library Options form.

Select the Options Button.

Use the Folder icon button to browse and select your SVN repository location. 

Then use the  [. . .] buttons to select your Symbols and Footprints folders.

Save and Close the *.SVNDBLIB file.

To Install the SVNDBLIB library, select:  

Systems > Libraries > Libraries . . . > Installed Tab > Install > Select the *.SVNDBLIB file.

Note: The first time you try to Edit a Symbol or Footprint you will be prompted to checkout the parts from the repository, if you have not already checked out the folders.

The first check out may take a long time, depending on the number of parts you have in your SVN repository.

A nice feature of SVNDBLIB Libraries is the Right Click > Edit Symbol or Footprint option that was not available in the DBLib.



Now you should be able to edit your parts and commit the changes to the repository.

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 !