"The idea of (test) code re-use
really intrigued us here at Lucent and we were extremely
satisfied with the results (of the cost study),"
said Michael Donlon, senior test engineer at Lucent.
The cost savings from re-using boundary
scan tests and programming operations originally developed
during development for prototype boards and later implemented
again in volume manufacturing was a major area of interest
for the study. In addition, Lucent wanted to quantify
the cost savings that might be generated by deploying
an integrated ScanWorks/3070 solution as a major part
of its test strategy. On both counts, the ScanWorks/3070
system passed with flying colors.
Lucent used four key metrics to determine
the cost savings from re-using boundary-scan test and
programming operations. The metrics were:
- Reduction in ICT test development
time.
- Lower ICT fixture complexity
and costs
- Improvements in test stability
- Lower in-system programming
costs
Other factors also contributed significant
cost savings. Foremost among these was the lowering
of fixture costs by reducing the number of nails needed
in fixtures since boundary scan's nail-less tests would
replace some of the tests previously performed by an
ICT fixture. And, by simplifying ICT fixtures, Lucent
lowered its fixture maintenance costs too.
The Lucent team that was conducting
the cost study noted that several other benefits were
derived from an integrated ScanWorks/3070 system. They
found that the boundary-scan tests had excellent stability
when used on a 3070 system in volume manufacturing.
This stability led to fewer false failures and fewer
good boards in the repair loop. As a result, debug and
test maintenance in manufacturing were reduced.
The seamlessness of the ScanWorks integration
with the 3070 also impressed the Lucent team. "I
was surprised at the seamless integration of ASSET ScanWorks
into the 3070 software," Donlon said. "The
process was quick and precise."
The tightly-coupled integration of
ScanWorks and the 3070 ensured Lucent an easy transition
of tests from development to volume production. This
takes on increasing importance for companies like Lucent
that are distributing manufacturing operations worldwide
to minimize costs.
The cost of programming PLDs and FPGAs
on-board through in-system programming operations also
were lower in the Lucent study because programming operations
generated during development could be re-used on the
3070, reducing significantly the time it would have
taken to re-develop the programming routines for manufacturing.
When all the cost savings were added
up, it came to $994,000 each year.
For
the complete Lucent success story, click here.
|
