Document Level for Drawings and Specifications

[ahollandutk]

Hello,

I am setting up my company's document control system. I understand the content of the 4 levels, but I'm not sure what to do with drawings and specifications. Should I be using a seperate method/number system. I am starting from scratch, so I really have no limitations. Just trying to understand the best way to go about it.

Thanks!

 

[qusys]

Hello,

I am setting up my company's document control system. I understand the content of the 4 levels, but I'm not sure what to do with drawings and specifications. Should I be using a seperate method/number system. I am starting from scratch, so I really have no limitations. Just trying to understand the best way to go about it.

Thanks!

I made a research for you in this forum in post attachment bar putting document control as key word.
Check if it is helpfull
http://elsmar.com/Forums/fileslist....=filename&pageamt=1&criteria=document+control

As suggestion , you can use whatever method to identify drawings and specifications.
it is up to you how to meet the clause of the standard.You can go for the most effective foryour organization. The important is to satisfy your need to bette serve your customers and have effective processes in place.
Hope this helps

 

[kgott]

Hello,

I am setting up my company's document control system. I understand the content of the 4 levels, but I'm not sure what to do with drawings and specifications.

Thanks!

I think the first of part of the answer lies in equating drawings with customer requirements.

You can use more than 4 levels if you wish. Many people have the company policy as the first level document which is something I cant agree with beause it's simply one sole document with goes into the manual as an appendix.

 

[Jim Wynne]

Hello,

I am setting up my company's document control system. I understand the content of the 4 levels, but I'm not sure what to do with drawings and specifications. Should I be using a seperate method/number system. I am starting from scratch, so I really have no limitations. Just trying to understand the best way to go about it.

Thanks!

There is no requirement for creating different levels of documents. It's fine if it works for you, but it's not required. Drawings are usually identified by either part number or drawing number, which is assigned at the time the drawing or design is initiated. Specifications can be numbered as you see fit. When you start having trouble determining what level documents should fit into, you begin to see a limitation in having a strictly-regulated "pyramid." Where most cases will have a clear place in the system, there will be others that aren't so clear, and the important thing is to just concern your self with effective control, and not so much about what level of the pyramid things should be in.

 

[Wes Bucey]

Typically, when an organization designates its documents by "levels," the difference between levels is one of detail:
Least detail (overall policy, for example) is Level 1
Most detail (work instructions, technical or engineering drawings) are Level 4

I'm more concerned about you confusing "control" as some sort of high security activity. In the sense you are using the term here it simply means managing the creation, approval, distribution, storage, and retrieval of documents. There is an additional facet, a separate emphasis in Aerospace, of Configuration Management. Configuration Management is primarily concerned with assuring updates of documents get timely distribution and obsolete documents are removed from use.