Hi Bada,
I agree with what the others have said. There are also other considerations for how much of a data
collection system you need. You really have to look at your business need to determine what type of system
will fit your situation.
What data you will be collecting? What areas & how much data needs to be collected. What analysis do you
hope to perform on the data? The decision on what type of system you will need depends mainly on what you
intend to use the data for... The driving factor for how much of a system you need should be what you hope
to get out of the information you are collecting ... Unfortunately, I guess another would be how much
money is your company willing to afford to spend. If you can't buy the system you need, develop your own.
If you just want to know what your top defect are so you can focus on them, a simple data collection sheet
and a spreadsheet may work. Also, how much data you will be collecting? How big is your facility? Do
you have a lot of products/ processes to keep track of or just a few?
On the other end of the spectrum, this data can be used to compile in-process, customer & supplier
reports... in all sorts of formats... top-level production summaries to component-level paretos... charts &
graphs... You could capture in-process data, incoming inspection, and customer returns.
There is just so much that can be done with quality data... I could bore you for hours on this subject.
When I started with my present company, my facility was using a simple data collection sheet & hand
counting the numbers from each sheet, then manually entered these into an Excel spreadsheet. It was a
time-consuming, tedious process. You can imagine that as production increased, this became totally
unsuitable. Shortly, after I started I developed a Microsoft Access database. I have continued to develop
this database as time has when on. We still presently use a data collection sheet to collect the info for
the database, but I hope to be getting away from that long term to have the operators enter the information
directly into the system themselves.
Now if any engineer or supervisor comes to me and ask what was the last week's pareto at SMT or Wave Solder
and who were the operators responsible for creating the defects, what were the yields or DPM, etc., in
under a minute I can print a formatted report telling them whatever level of information they need. If a
customer requests information on their product quality, I also have reports for them. Also, because all my
reports are automated, there is little time spend to obtain information and errors in calculations are
reduced. The only problems I have now with it is database management -- operator entry errors &
incorrectly recorded data on the data sheets.
The point I am making is that it really depends what is the end use for the data you will be collecting.
Develop a solution that fits your needs, present & future.
Hope this helps... or at least gives you some things to consider...
Rob Watson
Quality Assurance
Sanmina Corp. - Plant 10
Durham, NC
################################################################
TechNet E-Mail Forum provided as a free service by IPC using LISTSERV 1.8c
################################################################
To subscribe/unsubscribe, send a message to [log in to unmask] with following text in the body:
To subscribe: SUBSCRIBE TechNet <your full name>
To unsubscribe: SIGNOFF TechNet
################################################################
Please visit IPC's web site (http://www.ipc.org) "On-Line Services" section for additional information.
For technical support contact Hugo Scaramuzza at [log in to unmask] or 847-509-9700 ext.312
################################################################
|
