Eric joined the InfinityQS International team as an Application Engineer in November of 2006 and is based out of Gilbert, Arizona. He currently works with customers to provide on-site consultations, assist with the implementation of InfinityQS software and improve customers’ current implementations. In addition, Eric hosts online demonstrations of current and upcoming software elements and leads on-site classes of the Fundamentals Training course.
As a former customer of InfinityQS at Motorola/Freescale Semiconductor, Eric performed materials research and development where he used InfinityQS software to improve the capabilities and reliability of the data collection and process analysis. Now Eric shares his experience with customers to ensure they receive a complete understanding of the InfinityQS products and helping them look toward their future needs to benefit the overall project.
Eric earned a Bachelor of Science and Master of Science in Mechanical Engineering from the University of Wisconsin-Madison where his graduate school work focused on finite element analysis for the semiconductor industry.
Like many things in the manufacturing world, the definition of “mobile data collection” changes based on company, environment, collection type, required functionality, and who knows how many other variables. After many discussions with many customers on this topic, some general definitions of mobile data collection include:
Integration is a word that many people in manufacturing use, a subset of those interact with and a much smaller subset truly understands. From a very high level, it makes absolute sense that various systems should be aware of each other and communicate as much as possible. I’d like to make an addendum and change the last word in that sentence from "possible" to "practical".
When building InfinityQS projects and setting up data entry configurations, sometimes customers are in a quandary on whether they should use some of the pre-defined ProFicient "super descriptors" like Lot, Job, Shift and Serial Number.
"What are the advantages?"
"Should I save them for something special?"
Perhaps this blog's title is a misnomer. When I refer to "ugly" data I don't mean the actual data, I am referring to the file format that contains the data, but "Importing Data With a Less-Than-Cosmetic File Structure" just doesn't have much of a ring to it.