Documentation Organization (Matrix) "HELP"

H

Herman

#1
#1
I am currently a Manufacturing Engineer for a new start up medical device contract manufacturer. We currently do not have a quality engineer and the general manager and myself are sharing these duties. It is my task to organize a document control system that is in place, but not yet organized. We currently have a string of documents such as procedures, forms, records/logs, work instructions. What I am looking for is a simple matrix that I can utilize to help me set up the organization of these documents into a single numbering system. The way they are currently numbered is that each catagory has its own prefix (i.e. WI for work instruction and so on and so forth). Can anyone help me with this problem?

Thanks

------------------
 
Elsmar Forum Sponsor
D

David Mullins

#2
#2
I'm keen to see the feedback on this one myself. My new employer has the office I'm at ISO 9001 certified/registered, but not the other dozen offices spread around Australia and SE Asia (and their certified office is extremely short on objective evidence, and long on dodgy meaningless procedures).

What they do have is a mother of a document numbering system.

Document identification is to be in accordance with the following format:
DDDDDD_KKK_NNNNN_CC
where:
· “DDDDDD” is the 6 digit job or project number and office code combined.
· “KKK” identifies the Document Type Code (refer to list below)
· “NNNNN” is the 5 digit document number which is independent of project but unique to the particular business unit (consecutive ordinal numbers from 0001). {Note if you currently have been using a similar ordering and are at , say, 0859, you could continue with the same number sequence (eg. 00860) and so provide good continuity.}
· “CC” is the 2 digit version/issue of the document: “numeric” for issued documents but an “alpha” for pre-issue draft versions.
Note: All letters to be in upper case.

DOCUMENT ELECTRONIC STORAGE (FILENAMES)
To facilitate ease of transfer and storage of electronic documents, file identification is to be in accordance with the following format (compatible with PC use):
DDDDDD_KKK_NNNN_CC_Freeform.Ext
where:
· “DDDDDD, KKK, NNNNN, CC” are as the document number above
· “FreeForm” is the document title and optional
· “Ext” is the filename extent automatically generated by the software package.
Note: All letters to be in Upper case.


Examples

For a Perth administrative letter requesting payment of an invoice, the document number would be:

600001_ADM_00945_00.doc

For a Perth proposal or quote associated with Job No 600235, the document number would be:

600235_PTQ_00946_00.doc

For a Perth document of a Test Procedure for Job No 600276, the document number would be:

600276_TPR_00947_00.doc

The first update of this procedure would have the number

600276_TPR_00947_01.doc

For an Adelaide document to provide an Interface Control Document for Job No 504496, the draft document number at sequence 11657, would be:

504496_ICD_11657_aa.doc

which would be issued after review at

504496_ICD_11657_00.doc

The next update and re-issue would then have the document number

504496_ICD_11657_01.doc


AND ON IT GOES FROM THERE.

Needless to say I am intending to change this system, as the other offices, upon which this system is being applied, don't like it too much - wonder why?


------------------
 
D

David Mullins

#3
#3
Sorry, I've taken the question a step further than Herman. I'm looking at one system for ALL documents, this includes Project Management, design, drawings, memo's, minutes, templates, etc. So I'm not just looking at procedures, instructions, manuals and forms.

The ultimate truth is that the numbering SYSTEM really only matters to quality people, and confused engineers. Nobody else cares, as long as there is a means of differentiating between document A and document B.

The main problem I have is that my new employer is applying a job control numbering system to documentation, which provides individual identifying numbers/codes, but they make no sense like the QM, SOP, WI analogy.

------------------
 
A

Al Dyer

#4
#4
100% agree with David. It doesn't matter if a document is labeled abs, xyz, 123 etc...

The more "intricate" the numbering system the more chance there is for error.

I do believe that the system should be robust enough to have traceability of a level III document back to the Level II procedure.

Example:

Policy: QS-000
Procedure: QS-031, Contract Review Procedure
Form: qs-031-A, Feasibility Study Form
Instruction: wi-031-01, Feasibility Instruction

Just a thought.

ASD...

[This message has been edited by Al Dyer (edited 01 December 2000).]

[This message has been edited by Al Dyer (edited 01 December 2000).]
 
You must log in or register to reply here.
Thread starter Similar threads Forum Replies Date
L AS9100 D- Handling Nonconformance Documentation for an organization that outsources most of the work. AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 11
I IATF Lab Scope Testing Qualification and Competency Documentation IATF 16949 - Automotive Quality Systems Standard 3
C Documentation hold during submissions? ISO 13485:2016 - Medical Device Quality Management Systems 0
K SOUP (Software of Unknown Provenance) Anomaly Documentation IEC 62304 - Medical Device Software Life Cycle Processes 2
C Gobys for operations documentation plan Oil and Gas Industry Standards and Regulations 4
C Refreshing an old and boring topic - Job descriptions and Roles vs Process Documentation ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 38
C Documentation for items used for Design Verification 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 4
P Does anyone have a API Q1 Documentation Package? Quality Management System (QMS) Manuals 1
J Documentation structure - Do I need Work Instructions? Document Control Systems, Procedures, Forms and Templates 23
J Where to Place Process Maps in our Documentation? Process Maps, Process Mapping and Turtle Diagrams 4
C Manufacturing overages & nonconforming material documentation ISO 13485:2016 - Medical Device Quality Management Systems 3
Robert Stanley Required Documentation Templates ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 4
I Maintaining Technical Documentation under MDD and MDR EU Medical Device Regulations 1
M Basic UDI and technical documentation EU Medical Device Regulations 1
I Control of Documentation Distribution - Document Control ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 2
M What is the average time needed for process documentation? ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 8
was named killer CLOUD BASED QUALITY DOCUMENTATION vs. SERVER BASED Document Control Systems, Procedures, Forms and Templates 5
S How to start with ISO process in project based team - Documentation Document Control Systems, Procedures, Forms and Templates 4
K ITAR Visitor Documentation of Citizenship AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 4
R Design Verification Documentation ISO 13485:2016 - Medical Device Quality Management Systems 19
A Process Documentation for ISO 9001:2015 Internal Auditing 2
F Process Review - What is the ISO requirement for reviewing SOPs and quality documentation? ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 9
J Good Documentation Practices Self Test? ISO 13485:2016 - Medical Device Quality Management Systems 6
F ISO 17025:2017 mandatory documentation requirements ISO 17025 related Discussions 1
D Virtual Documentation via Master Flow Chart? Process Maps, Process Mapping and Turtle Diagrams 4
S Defining a Quality System from scratch - Preferred system and documentation names Document Control Systems, Procedures, Forms and Templates 4
C Maintenance of Product Technical Documentation EU Medical Device Regulations 3
F PPAP Documentation Control APQP and PPAP 8
V Every good documentation practice observation is an data integrity issue US Food and Drug Administration (FDA) 7
CPhelan Labeling template on QMS - Kitting and labeling documentation Manufacturing and Related Processes 9
DuncanGibbons Documentation aerospace OEMs require with purchase of parts from manufacturers/suppliers Manufacturing and Related Processes 0
V What is the criteria to cite an good documentation practices observation as an data integrity related issue US Food and Drug Administration (FDA) 6
L ISO 9001:2015 standard documentation ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 4
N Time source for paper-based documentation (research nurses) US Food and Drug Administration (FDA) 1
W Documentation - Use of Addendum vs Amendment Document Control Systems, Procedures, Forms and Templates 1
I What level of change in documentation requires re-training? ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 5
C Access to Technical Documentation - MDR Chapter VI Article 61 EU Medical Device Regulations 4
D QMS Documentation Process - I want to put all the Process SOPs to a QMS system Document Control Systems, Procedures, Forms and Templates 3
T QMS - Documentation Cloud Storage EU Medical Device Regulations 0
C Updates on Documentation for outsourced OEM from ISO 13485:2003 to ISO 13485:2016 ISO 13485:2016 - Medical Device Quality Management Systems 4
N EU MDR Basic UDI-DI and Technical Documentation for Systems EU Medical Device Regulations 22
B Quality Management System documentation identification Document Control Systems, Procedures, Forms and Templates 11
J Training documentation - ISO 13485 audit and the auditor had questions General Auditing Discussions 7
D Documentation requirements for the new Medical Device Regulations (2019) CE Marking (Conformité Européene) / CB Scheme 5
Ashok sunder ISO 45001:2018 Documentation template Occupational Health & Safety Management Standards 4
M Informational BSI – MDR Documentation Submissions Best Practices Guidelines Medical Device and FDA Regulations and Standards News 0
R DMR or Manufacturing Documentation - How detailed does the documentation have to be? ISO 13485:2016 - Medical Device Quality Management Systems 1
S Is Software code documentation required for FDA premarket submissions? IEC 62304 - Medical Device Software Life Cycle Processes 2
I MDD Class I software technical documentation sample EU Medical Device Regulations 2
M Annex II - Technical Documentation. V&V, Performance and Safety EU Medical Device Regulations 3

Similar threads

Top Bottom