CIS Database Part - Ordering

A beautiful feature of CIP is it is built to show SQL Table Views, a subset of the Capacitor table fields.

In CIP (logged in as admin).  Admin pulldown>  Configuration> Component Views Tab>

You can create multiple Views of the ICs or Misc table having a subset of properties visible to CIS part browser.

CIP allows you to create a CSV list to subdivide a table.   Bulk Operations>  Component View Mover> ...  import the list.

IMHO, I manage more than 6K part records.   

Custom ICs we sell are subdivided from the rest of the ICs.  But, I have made extra effort to create specific tables to help engineers go "part shopping".  Ultimately, engineers shop using DigiKey first (can't get the part, why bother?) and eventually, slowly reverted to just using one ICs table.  Worse, if the part doesn't land in "Unassigned", my guys can't find it.

Deal with mostly RF designs.  The Misc table is split between etch parts/patterns (Wilkinson combiner, directional couplers, transitions) and physical components (ceramic filters, shield cans, standoffs, batteries, microphones, light pipes, speakers.)

Haven't had specific tables pay off except a flatter hierarchy is faster to navigate for new coworkers.

Don't know what to tell you about the sequence.  It is crazy easy to write your SQL query to report fields sorted alphabetically. 

Don't think that will change.

So you have resorted back to a singular ICs table with a folder navigation structure such as:

RS-485 transceiver in ICs with part type “Transcievers/RS-485”?

Thus the navigation structure in CIS looks like

ICs

   +Transcievers

       Rs-485

? or something similar?

my only is is the parameter table than brings little benefit as the parameter table is for the top level folder “ICs” so there may be many parametric fields left unfilled or meaningless.  But reading into your response, I think you are suggesting people shop on Digi-Key anyways for specific parameters if a short dig in the database doesn’t do the trick.

thanks for the response!

I forgot about PartType property allowing you to group parts together by type.  It was surreal to land a contract for a company having thousands of MPNs in a single ICs table.

The best part is you can change/optimize PartType in CIP without (shouldn't) any effect on your sch DSN files

(you could cache this in the sch DSN with the DBC file.  But, please don't.)

Wow would be difficult to find parts with only a single ICs table, I guess queries would come in handy.

but back to the root the parametric table is just sort of out the window having one ICs table?  Just rely on designers to pull up Digi-Key anyway to find relevant parametric?

CIP extracts extra data that you won't want to circle back to add in the future.  It doesn't hurt anything. 

I like the CIP/Silicon Expert plugin.  We're not at that point yet.