Article View: bit.listserv.quality
Article #24Re: Inspection and test status
From: Larry McElhiney
Date: Sun, 27 Sep 1998 00:00
Date: Sun, 27 Sep 1998 00:00
70 lines
3925 bytes
3925 bytes
RNav@aol.com wrote:
>
> In a message dated 9/25/98 19:50:18, you wrote:
>
> <<I am the Quality Manager of ABB Centrum Ltd. in Poland. Scope of my firm
> activity include: design engineering, supply, erection supervision,
> commissioning, after sales service of automation system for use in power
> generation industries.
> I have the problem with Inspection and test status. Our product include
> automation systems used in power generation industry and it is not obvious
> how to establish and implement the inspection and test status. To the
> computer system we can not stick the status card. Naturally we test our
> products in many ways and we have a lot of measurements, but in fact, I
> feel, this is not enough. We maintain the products register which include
> all the goods we sold, but I think this is not a good solution.
> I count on your help and good advice.
>
> Monika Bryczkowska
> Quality Manager
> monika.bryczkowska@plcen.mail.abb.com
> >>
>
> I'm not sure exactly what your question is, but I think it is you want to know
> how to identify the inspection and test status of your product.
>
> Not being familiar with your product or process, this will be generic. I
> assume you have components and completed assemblies. Per ISO-9000, where ever
> you have an inspection and or test in your process, the product in test or
> completing test must be identified as to the status of the inspection or test.
> For instance, pass, rejected, scrap, rework, repair. The status determination
> and who determines it should be per your procedures.
>
> I hope this helps.
>
> Robert Drensek, CQE, CQA, CRE
> Quality Engineer
> RNAV@AOL.COM
Hi,
Some thoughts...
Is there any form of serial number of the item which can ensure tracking
back to your testing data? This could be used to help prove the
status.
Is there a place where you could place a small rubber stamp impression
or a small label? Either could be used to show status.
Can the items which are bad be physically placed into a "hold" area
until corrected--this would identify status.
Is there a printout of the rejected test status on bad units? You could
meet the requirements by allowing all good units to continue on down a
production line and physically identifying only the bad units--while
they are a captive to that test area. When transferred to another area
there must be something which indicated status, even if only a temporary
piece of paper which would be removed during the next stage of the
operation.
The standards are looking for control, but allow you to define your own
way of doing it for the most part. Many auditors will give you their
own favorite method during an audit, but few will disallow a system that
provides control, no matter how it is accomplished.
Good luck,
Larry McElhiney
QXpert
mack@netcom.com
Technical Details
Message-ID:
<360D7E7D.C8F@netcom.com>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<199809262320.QAA09807@mail2.netcom.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 1159be,6704879cace188e8 X-Google-Attributes: gid1159be,public From: Larry McElhiney <mack@NETCOM.COM> Subject: Re: Inspection and test status Date: 1998/09/27 Message-ID: <360D7E7D.C8F@netcom.com> X-Deja-AN: 395685111 Sender: TQM in Manufacturing and Service Industries Discussion List <QUALITY%PUCC.BITNET@vtbit.cc.vt.edu> Content-Transfer-Encoding: 7bit Approved: NETNEWS@AUVM.AMERICAN.EDU * References: <199809262320.QAA09807@mail2.netcom.com> Comments: ******************************************************** Approved-By: "Bill Casti (System Admin)" <help@QUALITY.ORG> Content-Type: text/plain; charset=us-ascii X-Received: from 10.0.2.15 (mack@netcom20.netcom.com [192.100.81.133]) by netcom3.netcom.com (8.8.5-r-beta/8.8.5/(NETCOM v1.02)) with SMTP id QAA03910; Sat, 26 Sep 1998 16:54:08 -0700 (PD MIME-Version: 1.0 Reply-To: mack@NETCOM.COM Newsgroups: bit.listserv.quality