Saturday, March 16, 2013

Tools

Updated Oct 5, 2024

Import Libs
Import Single Part Symbol Libraries.
Related Link: Import Libs

Export Excel 
Export database tables to Excel file types *.xls or *.xlsx.
Related Link: Export Excel

Import Excel
Import Excel data to Parts Tables.
Related Link: Import Excel



MySQL Scripts
Use to generate Parts Scripts for a MySQL Parts Database.
Use with MySQL Workbench to design the Parts schema.

Export MySQL 
Export | pipe delimited | UTF-8 files for Load MySQL

Load MySQL
Fast Load Data of CSV files for MySQL databases.
Backup Parts
Use to Backup the Parts Database.
Related Link: Backup Parts

Clone MySQL
Clone MySQL can be used to Create local Access database tables.

Cloned tables can be exported using Tools > Export for MySQL.
The Exported MySQL data can be Loaded into MySQL.

Clean Parts
Opens the Clean Parts Dialog 

That's It !

PLM - Part 1: One too Many Dilemma

'One too Many Dilemma' is a pun on words for the Relationships' which exist in PLM systems.  

This article attempts to explain the primary integration problem for PLM systems and CAD tools. 

PLM systems support 'many to many' relationships. CAD tools typically have 'one to one' or 'one to many' relationships. 

In the digital computer age numerous PLM, MRP and ERP systems have been created to support the design and manufacturing process. Circuit board EDA and CAD design tools have also advanced considerably during the past decade.

Efforts are being made to integrate PLM systems with PCB design tools with most of the efforts being made in vain. This is due to the 'many to many' relationships which is corner stone feature of PLM systems.

To appreciate the PLM to CAD integration issues, it is necessary to understand the role of the PLM system. PLM systems are designed to support a product through it's life cycle.

In most companies the PLM life cycle for a product begins after the design has been released from engineering to manufacturing.

There is a lot of brainstorming work that occurs in the design phase, such as qualifying parts and optimizing the design for production that is not really useful to put into PLM.

PLM is about maintaining products that are in production and sustaining manufacturing. 

You can find PLM systems that are designed to track your project from conception to the grave. It is just not very efficient to force a design team to use configuration control while a product is in the design phase. 

However if you project is highly critical, say like getting to the moon and back, you may need a complete track record of your project including the design phase work.

PLM systems use Engineering Change Orders (ECOs) to facilitate configuration control during the product's life cycle.

Designs typically begin with a Bill of Materials (BOMs) which list manufacturer part numbers.

PLM systems use Material Control Numbers (MCNs), also known as company part numbers. 

Before a BOM can be released to PLM the MCNs (company part numbers) must be exist in the PLM system.

Manufacturer part numbers are associated with MCNs in PLM systems. 

The approved manufacturer part numbers in PLM are often referred to as the AVL (Approved Vendors List).

Next step is to back-annotate engineering BOM with the MCNs. With MCNs assigned to each line item the BOM is ready to be imported into the PLM system.

In Part 2 we will delve into relationships between the manufacturer part numbers and the MCNs.

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