The Cove Business Standards Discussion Forums
ISO 9001 2015 Documentation for Engineering and Design
UL - Underwriters Laboratories - Health Sciences
ISO 9001 2015 Documentation for Engineering and Design
ISO 9001 2015 Documentation for Engineering and Design
ISO 9001 2015 Documentation for Engineering and Design
ISO 9001 2015 Documentation for Engineering and Design
ISO 9001 2015 Documentation for Engineering and Design
ISO 9001 2015 Documentation for Engineering and Design
ISO 9001 2015 Documentation for Engineering and Design
ISO 9001 2015 Documentation for Engineering and Design
ISO 9001 2015 Documentation for Engineering and Design
Go Back   The Elsmar Cove Business Systems and Standards Discussion Forums > >
Forum Username

Elsmar Cove Forum Visitor Notice(s)

Wooden Line

ISO 9001 2015 Documentation for Engineering and Design


Monitor the Elsmar Forum
Sponsor Links




Courtesy Quick Links


Links Elsmar Cove visitors will find useful in the quest for knowledge and support:

Jennifer Kirley's
Conway Business Services


Howard's
International Quality Services


Marcelo Antunes'
SQR Consulting, and
Medical Devices Expert Forum


Bob Doering
Bob Doering's Blogs and,
Correct SPC - Precision Machining


Ajit Basrur
Claritas Consulting, LLC



International Standards Bodies - World Wide Standards Bodies

AIAG - Automotive Industry Action Group

ASQ - American Society for Quality

International Organization for Standardization - ISO Standards and Information

NIST's Engineering Statistics Handbook

IRCA - International Register of Certified Auditors

SAE - Society of Automotive Engineers

Quality Digest

IEST - Institute of Environmental Sciences and Technology


Some Related Topic Tags
design and development, documents and documentation (general), iso 9001:2015
Reply
 
Thread Tools Search this Thread Rate Thread Content Display Modes
  Post Number #1  
Old 12th January 2018, 12:15 PM
cferrer

 
 
Total Posts: 3
Please Help! ISO 9001 2015 Documentation for Engineering and Design

Hello Everyone,

Could you help clear out my confusion about where do the different design documents such as sizing arrangements, mathematical calculations, dimensioning, configurations overview concept documents, etc. , fall within the pyramid hierarchy of documents of a QMS (i.e. Policy, Procedures, Instructions, forms, records...).

And how about the knowledge-base? where does this fall under. We have a repository of technical descriptions and guidelines. Are this considered procedures, forms, instructions?

Thanks in advance

Chris

Sponsored Links
  Post Number #2  
Old 12th January 2018, 12:44 PM
John Broomfield's Avatar
John Broomfield

 
 
Total Posts: 2,581
Lightbulb Re: ISO 9001 2015 Documentation for Engineering and Design

Quote:
In Reply to Parent Post by cferrer View Post

Hello Everyone,

Could you help clear out my confusion about where do the different design documents such as sizing arrangements, mathematical calculations, dimensioning, configurations overview concept documents, etc. , fall within the pyramid hierarchy of documents of a QMS (i.e. Policy, Procedures, Instructions, forms, records...).

And how about the knowledge-base? where does this fall under. We have a repository of technical descriptions and guidelines. Are this considered procedures, forms, instructions?

Thanks in advance

Chris
Chris,

I understand your desire for a rigorous hierarchy of documents commonly found in hard copy parts of documented management systems. The structure made the management system easier for users to navigate and find exactly what they needed.

That structure with its document coding scheme made hard copy systems easier to administer too.

But with electronic procedures and their hyperlinks to instructions, forms and tools we are seeing more and more that every doc is controlled as part of its parent procedure.

Be careful to separately control design inputs and outputs as records that may be tied to each project. Indeed, each drawing is controlled as a project document until it is superseded or updated to become the “as built” or project record

So, let’s take a look at the docs you identified:

- sizing arrangements - serves as a project instruction before becoming a record unless standardized across your practice when it would be controlled as an instruction

- mathematical calculations - record

- dimensioning - normally standardized practice-wide, so an instruction

- configurations overview (concept documents) is an output of the conceptual design stage before it becomes a record as detailed construction drawings take over.

Your knowledge base is a reference library and its documents (records really) are not subject to revision control. Again, today’s search engine savvy users prefer keywords in place of hierarchy.

John
Thanks to John Broomfield for your informative Post and/or Attachment!
  Post Number #3  
Old 12th January 2018, 12:56 PM
Pancho's Avatar
Pancho

 
 
Total Posts: 830
Re: ISO 9001 2015 Documentation for Engineering and Design

Hi Chris,

I understand your confusion. Many documents such as you describe do not fit into the classic descriptions. Drawings, for example, provide evidence of your design (could be records) but they also provide instruction to installation crews (could be work instructions).

Fortunately, the standard does not restrict your documents to the "pyramid" that you mention. Section 7.5.1.2 requires the QMS to include "documented information determined by the organization as being necessary for the effectiveness of the quality management system". ISO 9000 defines documented information as that created in order for the organization to operate, as well as to provide evidence of results achieved (records). So you are free to have "technical descriptions", "technical guidelines", "Mathematical calculations", "Drawings", "work orders", etc.

In our QMS wiki we have a forum for "Technical Notes" where we keep documents like internal descriptions and guidelines that our engineers regularly consult even though they are not part of any particular work instruction. We also have different forums for each project, where we keep the calculations, design reports and drawings for that project. The information is then used where required without worrying too much about what the document category is.

Hope this helps!
Pancho
Thanks to Pancho for your informative Post and/or Attachment!
  Post Number #4  
Old 13th January 2018, 05:07 AM
cferrer

 
 
Total Posts: 3
Re: ISO 9001 2015 Documentation for Engineering and Design

Hello Guys,

These are very insightful explanations. Thanks you very much!

Coincidently, I haven’t been able to stop thinking about this so in the mean time I was brainstorming and wrote a few things down so I thought I would share it.

Mechanical Design:
  • Drawings and 3D Model --> drafts for design review, not controlled
  • Drawings and 3D model finalized --> production planning and assembly instructions
  • Drawings red-lined from assembly --> ??
  • Corrected drawings and 3D model --> Final system documentation, i.e. as-built records

Electrical Design: Similar as mech. Design

Systems Engineering:
  • Hardware Design concepts --> production planning documents
  • Communications and interfaces design notes --> production planning documents
  • Engineering calculations and dimensioning decisions --> internal to systems engineering, not passed down. Is this a record?
  • First-draft PLC Programs, state machines, operating concepts --> I guess same as above
  • Parametrizing/Configuration data --> I guess it is like an appendix to a work instruction
  • Final system performance and hardward configuration compendium --> I guess what one would normally call the system specification (perhaps a record)

R&D (knowledge-base, not controlled):
  • Project reviews and technical Lessons learned
  • Sizing and calculation guidelines
  • Design Guidelines
  • Technical Descriptions
  • Product or replacement Investigations
  • Market or technology research
  • Product benchmarks

I guess the collection of all records from each of these departments is what the medical device industry would normally refer to as "Design History File" (DHF), correct?

However, I am starting to realize that I just have to „think outside the box“ more and think in tags in today’s dynamic and multidimentional environment.

I guess my real questions are:

Are our engineering documents percieved and treated correctly?

Which engineering documents do I really want/need to control as a small company ?

What is the best strategy for a small company to achieve design (quality) assurance without making the mistake of controlling too much and thus exposing too much in case of an audit?

Any thoughts?

Last edited by cferrer; 13th January 2018 at 05:12 AM. Reason: forgot a comment
  Post Number #5  
Old 13th January 2018, 08:32 AM
srinivasbom

 
 
Total Posts: 1
Re: ISO 9001 2015 Documentation for Engineering and Design

hai my friend.
am srinivas, i was assigned to iso 9001:2015. my company is engineering contracting company takeover the maintenance projects in the field of mechanical, electrical and instrumentation departments of Power Plants and Oil & Gas companies. we are just started the preperation of quality manual. which clause do i need to include and which are not to include, can you please guide?
  Post Number #6  
Old 13th January 2018, 09:32 AM
AndyN's Avatar
AndyN

 
 
Total Posts: 8,873
Let Me Help You Re: ISO 9001 2015 Documentation for Engineering and Design

Quote:
In Reply to Parent Post by cferrer View Post

Hello Everyone,

Could you help clear out my confusion about where do the different design documents such as sizing arrangements, mathematical calculations, dimensioning, configurations overview concept documents, etc. , fall within the pyramid hierarchy of documents of a QMS (i.e. Policy, Procedures, Instructions, forms, records...).

And how about the knowledge-base? where does this fall under. We have a repository of technical descriptions and guidelines. Are this considered procedures, forms, instructions?

Thanks in advance

Chris
Chris: You are labouring under an old model. ISO 9001 never required such a structure, despite the fact that it became commonly used. Furthermore, this structure ended up CREATING the problem you are wrestling with - trying to pigeon hole documents document classifications totally artificially.

Similarly, unless there's a compelling reason for you to do this, your quality manual should only be like a "quick-start" guide, like you'd get with a new item of electrical equipment (not like the full blown user manual you also get)

I'd avoid creating a monster you'll have to feed from now and for ever...
  Post Number #7  
Old 13th January 2018, 09:34 AM
AndyN's Avatar
AndyN

 
 
Total Posts: 8,873
Let Me Help You Re: ISO 9001 2015 Documentation for Engineering and Design

Quote:
In Reply to Parent Post by srinivasbom View Post

hai my friend.
am srinivas, i was assigned to iso 9001:2015. my company is engineering contracting company takeover the maintenance projects in the field of mechanical, electrical and instrumentation departments of Power Plants and Oil & Gas companies. we are just started the preperation of quality manual. which clause do i need to include and which are not to include, can you please guide?
Please see my other post...
  Post Number #8  
Old 13th January 2018, 11:40 AM
John Broomfield's Avatar
John Broomfield

 
 
Total Posts: 2,581
Lightbulb Re: ISO 9001 2015 Documentation for Engineering and Design

Chris,

How about consulting the creators and users of engineering information to determine their objectives of the process: controlling documented engineering information?

You may find it goes something like this:

“Valid engineering information readily available to authorized users and invalid information withdrawn from project use”.

Once you have this process objective you can then see if the existing process is effective. If it isn’t then issue a CAR to define that nature of the nonconformity and to engage creators and users in removing the root causes of this processes’ failures from the system.

You may also be able to engage some of the creators and users in mistake-proofing their process so they’ll be more inclined to make it work effectively.

Proposing solutions looking for a problem may result in pushback.

Better to define and agree upon the problem that needs to be solved.

Best wishes,

John
Reply

Lower Navigation Bar
Go Back   The Elsmar Cove Business Systems and Standards Discussion Forums > >

Bookmarks



Visitors Currently Viewing this Thread: 1 (0 Registered Visitors (Members) and 1 Unregistered Guest Visitors)
 
Thread Tools Search this Thread
Search this Thread:

Advanced Forum Search
Display Modes Rate Thread Content
Rate Thread Content:

Forum Posting Settings
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Emoticons are On
[IMG] code is On
HTML code is Off


Similar Discussion Threads
Discussion Thread Title Thread Starter Forum Replies Last Post or Poll Vote
ISO 9001:2015 8.3 Design and Development (in Civil Engineering) gavin.D ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 4 30th August 2017 02:11 PM
ISO 9001:2015 - Design of Process vs. Design of Service QualitySteve Service Industry Specific Topics 4 23rd June 2017 12:21 AM
Changing Terminology in ISO 9001:2015 - Documentation Content QAMTY ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 5 25th January 2017 08:20 AM
Engineering Department Documentation Requirements - ISO 9001 Clause 7.3 juliov ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 6 23rd May 2007 05:02 AM
Design Control 4.4 - Design Engineering manager has no structured documentation Marc Design and Development of Products and Processes 11 15th October 1999 10:09 AM



The time now is 01:31 PM. All times are GMT -4.
Your time zone can be changed in your UserCP --> Options.



Misc. Internal Links


NOTE: This forum uses "Cookies"
The Elsmar Cove web site and all content is owned by Rabbithash Corp. as of 1 MAY 2018.
Unlike Facebook and other properties such as Linkedin, We don't buy, sell, or "share" visitor information. Never have, Never will...
GDPR Compliant since 1996, keeping Marc's vision alive!