Indyme Retail Solutions Benefits from Corelis Advanced Diagnostics
News Release from:
24 August 2010
Corelis, Inc., a leading supplier of high-performance boundary-scan test and measurement tools, announced today the successful implementation and application of the ScanExpress ADO advanced diagnostics system at the test facilities of Indyme, the leading developer of retail event-triggering communication technologies. The advanced diagnostics module adds precise structural fault identification to Indyme's existing Corelis boundary-scan test system.
As a long time client with Corelis, Indyme has utilized the ScanExpress Runner GANG concurrent boundary-scan test system for high volume production testing and programming. After experiencing unexpected and difficult-to-identify failures in a recent production run on their Connect Start™ platform, Indyme opted to add the Corelis ScanExpress ADO module to assist in identifying the root cause of the encountered failures.
Indyme’s Connect Start™ platform is a versatile event response system used by retailers to conveniently manage and process alarm triggers. The platform is built on highly reliable electronic hardware capable of accepting up to 1,000 alarm input triggers, all in a compact form factor for convenient utility room installation.
We had been primarily using Corelis tools for high volume go/no-go decisions as well as chip programming, stated Bob Wendt, Indyme’s Manufacturing Engineering Manager. However, this set of circumstances required a tool that could help identify the root cause of our problem. Luckily, Corelis already had a software module with this capability. ScanExpress ADO led debug efforts to the root of the production failure, enabling Indyme to quickly take corrective action and greatly improving manufacturing yield with minimal resource commitment.
Wendt concluded, With just this one fault identification, the Corelis boundary-scan tools provided a return on our investment far beyond expectations. If you have BGA parts in your product, boundary-scan is a requirement. It isn’t really an option if you’re serious about testing.