TECHNET Archives

December 2001

TechNet@IPC.ORG

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Earl Moon <[log in to unmask]>
Reply To:
TechNet E-Mail Forum.
Date:
Mon, 31 Dec 2001 23:10:36 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (120 lines)
I've received some interesting off line comments concerning my last question
concerning DFM/CE. I need to be more specific, I think, as always.

There are about 20 SHALL statements in section 7.3 (Design and development)
alone. There were about 137 shall statements in all of the previous ISO
version. The following is section 7.3 and my question is how well is
everyone dealing with converting these shall requirements into "we are"
statements and ARE YOU REALLY DOING THEM and, if so, what are your results -
GOOD OR BAD? In other words, hows your DFM/CE program working?

7.3 Design And Development

7.3.1 Design And Development Planning

The organization shall plan and control the design and development of product.

During the design and development planning, the organization shall determine

a) the design and development stages,

b) the review, verification and validation that are appropriate to each
design and development stage, and

c) the responsibilities and authorities for design and development

The organization shall manage the interfaces between different groups
involved in design and development ot ensure effective communication and
clear assignment of responsibility.
Planning output shall be updated, as appropriate, as the design and
development progresses.

7.3.2 Design and Development Inputs
Inputs relating to product requirements shall be determined and records
maintained (see 4.2.4). These inputs shall include

a) functional and performance requirements,

b) applicable statutory and regulatory requirements,

c) where applicable, information derived from previous similary designs, and

d) other requirements essential for design and development.

These inputs shall be reviewed for adequacy. Requirements shall be complete,
unambiguous and not in conflict with each other.

7.3.3 Design and Development Outputs
The outputs of design and development shall be provided in a form that
enables verification development input and shall be approved prior to release.

Design and development outputs shall

a) meet the input requirements for design and development,

b) provide appropriate information for purchasing, production and service
provision,

c) contain or reference product acceptance criteria, and

d) specify the characteristics of the product that are essential for its
safe and proper use.

7.3.4 Design and development review
At suitable stages, systematic reviews of design and development shall be
performed in accordance with planned arrangements (see 7.3.1)

a) to evaluate the ability of the results of design and development to meet
requirements, and

b) to identify any problems and propose necessary actions.

Participants in such reviews shall include representatives of functions
concerned with the design and development stage (s) being reviewed. Records
of the results of the reviews and any necessary actions shall be maintained
(see 4.2.4).

7.3.5 Design and development verification
Verification shall be performed in accordance with planned arrangements (see
7.3.1) to ensure that the design and development outputs have met the design
and development input requirements. Records of the results of the
verification and any necessary actions shall be maintained (see 4.2.4).

7.3.6 Design and development validation
Design and development validation shall be performed in accordance with
planned arrangements (see 7.3.1) to ensure that the resulting product is
capable of meeting the requirements for the specified application or
intended use, where known. Whenever practicable, validation and any
necessary actions shall be maintained (4.2.4).

7.3.7 Control of design and development changes
Design and development changes shall be identified and records maintained.
The changes shall be reviewed, verified and validated, as appropriate, and
approved before implementation. The review of design and development changes
shall include evaluation of the effect of the changes on constituent parts
and product already delivered.

Records of the results of the review of changes and any necessary actions
shall be maintained (see 4.2.4).

What I'm getting at here is if you are registered to the 2000 version of ISO
9000, you must be doing everything ISO requires. If so, you are applying and
practicing good DFM/CE principles, right?

Just want some input about how everyone is approaching this important, to us
all, subject and how well it is working so far.

Thanks a lot,

Earl Moon

---------------------------------------------------------------------------------
Technet Mail List provided as a free service by IPC using LISTSERV 1.8d
To unsubscribe, send a message to [log in to unmask] with following text in
the BODY (NOT the subject field): SIGNOFF Technet
To temporarily halt delivery of Technet send the following message: SET Technet NOMAIL
Search previous postings at: www.ipc.org > On-Line Resources & Databases > E-mail Archives
Please visit IPC web site (http://www.ipc.org/html/forum.htm) for additional
information, or contact Keach Sasamori at [log in to unmask] or 847-509-9700 ext.5315
---------------------------------------------------------------------------------

ATOM RSS1 RSS2