Let us help you with Prototype Data
The small amounts of data in a start-up situation may not warrant investment in the latest and greatest software. However getting things right from early on can save a huge amount later. With our new service, we can help start-ups ensure that all possible information is found from whatever data is available early on.
MFG Vision is partnering with E.K.S.S. Microelectronics to offer this exciting service. MFG Vision’s latest software yieldHUB will be used by E.K.S.S. consultants to provide yieldHUB-startUP.
yieldHUB-startUP is a service targeted at semiconductor start-up companies who need to get the value from their data but do not have the expertise or software to do this themselves. The following are just some of the services that are offered:
- Analyzing characterization results over corner lots vs. WAT results
- Enhancing product robustness by analyzing first lots’ yields vs. sites vs. process
- Analyzing drift on reliability testing
- Checking for and identification of any reticle issues before large volume production
- Discovering and recommending the elimination of redundant tests
- Monitoring of early production
Both E.K.S.S. and MFG Vision staff include semiconductor product and test engineers with over 100 years combined experience. We can bring that experience to bear on your data to give your new product the best possible start.
You may (or may not) have heard that there was an earthquake three weeks ago in the Philippines, specifically in Bohol, which is the location of one of our worldwide offices. I, as CEO, received the text shortly after 1AM my time (I am based in Ireland) from my chief lieutenant in Bohol and only saw the text at 6.30AM or thereabouts when I woke up.
The earthquake hit about 60KM from our office in Tagbilaran City and, at 7.2 in the Richter Scale, qualified as a “massive” earthquake. As human beings the immediate concern of my wife and I, directors of the company, was of course for our staff over there and their immediate families. Over the following 24 to 48 hours the picture became clear that our Bohol staff were all OK, although unfortunately one of our engineer’s family home was destroyed.
Having support engineers in other countries meant our customer support wasn’t affected that week with everyone stepping up to the plate. It was a traumatic week for our staff in Bohol, especially with some of their family and friends affected.
How does a company survive when a large number of its developers and support engineers and technicians are affected by an act of God like this? One of my lawyer friends asked me if we had disaster insurance. The real insurance is the fact that our servers are not near any of our offices. We are a cloud technology company who also use the cloud for our software development and support. The servers we use are under the ground in a desert in the United States, well away from fault lines.
Our Bohol engineers were heavily involved in disaster relief. My chief lieutenant there, Jerome Auza, led relief of local villages cutoff by a major bridge that was taken down. He was in a customer site in Israel within seven days setting up a brand new product and is now back in Bohol. On arriving back he and his team fixed an important customer issue which came up with a customer in the USA. On a national holiday!
The lessons learnt? The resilience, resourcefulness and commitment of Filipinos. The advantages of the cloud when a natural disaster hits. The onward march of nature. We have people on the ground in multiple countries now, though a ground which sometimes can shift in an unexpected manner.
John O’Donnellread more
Is your product engineering mature?
Creaking with old age?
Young fresh and chaotic?
Or purring in prime performance?
The truth is that unless there is continuous improvement and regular investment in systems and training then all product engineering & yield management systems will start young, and end up old. The golden age is the time in between. But how to get into this performing time quickly and stay there? In my view a good assessment is needed of the current status and then a step by step approach to improvement.
I am in the fortunate position to see companies with product engineering teams in each of these phases and even more fortunate to engage with companies to help them move from one phase to the next.
Product engineering is a vital function in semiconductor companies. From fabless companies who need to ensure that the subcontractors are manufacturing according to specification, to IDMs who must use their joined approach to gain as much efficiency as possible. And in all cases yield is directly valuable, throwing product in the bin is directly throwing money way.
1. Understand your current system status
What is your present system like? What are the drawbacks? I saw an example recently where engineers in one country spend hours downloading data to their desktop in order to do analysis. They are feeling the pain of a system creaking with old age.
2. Compare solutions
No solution is perfect for everybody. Take a good look at what is new in the industry. There are some innovative ideas around. How about adding a collaboration engine to your analysis tool?
3. Bring in the right systems and experts to agree the next steps
Understand not only if the system you are looking at has the right functionality, but more importantly you need to know that you will receive the right support to achieve the return on your investment. This can all come from working with the right people.
4. Get visibility, give visibility
It’s amazing how many people cannot see their data. Even if they can they have to wait hours to get it, are restricted how much data can be viewed at one time, are restricted to only a certain desktop to access the data. I believe a key step is to get data anywhere, anytime. Give this visibility to your engineers. Both through access to the system and training.
5. Add functionality
Now that you can see your data and your team are trained on the basics it is time to start to implement those functions that you dreamed of but had no time to work on. Maybe gage R&R analysis, Lots on Hold control, Part Average Testing….
By this time there will be significant improvements in place (if you made the right choices in steps 1-3). It should already be clear that there is good return on investment and further enhancements to the system can be discussed.
Please comment or contact me (Kevin Robinson) if you have more to add.