From: owner-stds-1450-4@majordomo.ieee.org on behalf of
jim_oreilly@agilent.com
Sent: Thursday, April 18, 2002 8:56 AM
To: stds-1450-4@majordomo.ieee.org
Subject: RE: stds-1450.4: stds-1450.4 Multi-site STIL


Hi, all

Well, this multi-site flow issue certainly has gotten the blood flowing
to the back of my brain (where all the best ideas are kept :-) ).  In
thinking about it, I find myself in agreement with Gordon and Ernie -
especially since my experience with multi-site comes from testers that
have an independent sequencer for each site.  In such situations, the
same flow is used whether running on a single site or multiple sites.

So, my preference would be to concentrate for now (i.e., the next few
months) on single-site flow issues.  At the same time, we can lay any
needed groundwork for dealing with multi-site issues.  I'd propose
that we follow up on Ernie's suggestion  about collecting info about
currently-available multi-site schemes.  From that data, we can identify
areas where they're similar and areas where they diverge - and the
common areas would likely be amenable to standardization.

Also, as Don noted, multi-site is but one type of parallelism - he also
mentioned core testing (i.e., P1500-type work).  And we'll probably have
to deal with that as well (though it *could* be less complex than
multi-site issues, since in such a situation, we'd be dealing with only
one device, not many).


Regards,

Jim 

-----Original Message-----
From: Ernst_Wahl [mailto:wahl@aloft.agere.com]
Sent: Thursday, April 18, 2002 5:12 AM
To: stds-1450-4@majordomo.ieee.org
Subject: RE: stds-1450.4: stds-1450.4 Multi-site STIL



Tom, Gordon, and all,

I thought i'd restrain myself on the multi-site issue before applying my
steady drone: create the standard in phases. Tom has cracked the door
and i find myself staring into the deep morass. I'm backing Gordon on
this one, certainly for phase one.

To the extent that we feel compelled to carry on, i would focus
multi-site discussions on avoiding potential pitfalls in designing a
single-site-flow, i.e., the single-site-flow should not pose unnecessary
difficulties integrating multi-site schemes.  That may require a
compilation of known schemes that we can hold our single-site-flow up
to.  On the other hand, history is that ATE vendor multi-site flows were
constructed over existing single-site flows so, how circumspect do we
need to be ?  I'm not wise enough to say so i'll rely on the wisdom of
our group.

-----------------------------------------------------------------------
Ernie Wahl          Agere Systems               Tel:   610.712.6720    
Computer-Aided Test 55F-124D, 6755 Snowdrift Rd Fax:   610.712.4235    
                    Allentown, PA, 18103        Email: ejwahl@agere.com
-----------------------------------------------------------------------