Enhanced package modeling for V3 IBIS

My proposal is to add a PCB (like) specification to IBIS.
I am think it would be an attached file like .pkg is already.
Since there really is no PCB standard, it seems to me we could
provide a simplified format that is an IBIS connection layer
specification. None of the major groups have yet to get a PCB
standard accepted. It seems the major problem is that the PCB
companies don't want it. Only the users want it. EDIF and IPC
both have "standards that are not used. The EDIF PCB group is
also working on an MCM specification to add on to EDIF PCB. There
may be some overlap with this effort and IBIS.
So it isn't clear that there is any advantage to using an existing
standard except that it is debugged. The requirements are that
it be an ASCII format that can be released to the public domain.

I will follow up by getting a copy of what the EDIF PCB group is
working on for MCM's.

The advantages for the IBIS community of a PCB like specification
are:
 - MCM supported as a chip
 - Hypbirds supported as a chip
 - Chip modules (like CPU's with cache) supported as a chip.
 - SIMM modules supported as a chip.
 - Packaging like PGA's with ground planes could be nicely supported.
 - Easily available design data for IC vendors. No need to convert
   mechanical data into behavioral data.
    

The disadvantages are:
 - Some vendors may not want to disclose packaging designs
 - Availability of translators.

Another idea is to enlist Router Solutions to create
an output generator in whatever format we decide on. Then anyone
that needs to output this format could simply call Router Solutions
and order a translator from their format to the IBIS format.
Router Solutions already supports about every PCB and mechanical package
on the planet Earth. We would probably need to pay them to develop the
writer portion to create IBIS. I haven't talked to them yet but I will.

Have a great day...Kellee Crisafulli, HyperLynx Inc.
Received on Fri Apr 7 13:13:16 1995