0% found this document useful (0 votes)
77 views

Quality Management System: Purpose

This document outlines the naming procedure for non-project documentation at Inhabit Group. It specifies that document names should follow the format "IN-XXX-YY000(00)-DocumentDescription" where: - IN indicates it is a company document - XXX is the document type code (e.g. PRD for Procedure) - YY is the function/discipline code (e.g. QA for Quality Assurance) - 000 is the document number in sequence - (00) is the revision number - DocumentDescription is a short description to identify the document Examples of correctly formatted document names are provided.

Uploaded by

mcblued
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
77 views

Quality Management System: Purpose

This document outlines the naming procedure for non-project documentation at Inhabit Group. It specifies that document names should follow the format "IN-XXX-YY000(00)-DocumentDescription" where: - IN indicates it is a company document - XXX is the document type code (e.g. PRD for Procedure) - YY is the function/discipline code (e.g. QA for Quality Assurance) - 000 is the document number in sequence - (00) is the revision number - DocumentDescription is a short description to identify the document Examples of correctly formatted document names are provided.

Uploaded by

mcblued
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

QUALITY MANAGEMENT SYSTEM

Title: Document Naming Procedure – Non Project

Author: Tom Candalepas / Sarah Coogan

Reference No.: IN-PRD-QA0002(07)-DocNamingNonProject

Version Date Author Reviewed Authorised Description Next review


Sarah Coogan /
00 26/11/13 Colin Yeung Draft – for review 29/11/13
Tom Candalepas
Sarah Coogan /
01 6/12/13 Colin Yeung Tony Alvaro For final review 10/12/13
Tom Candalepas
02 11/12/13 Tom Candalepas Colin Yeung Tony Alvaro For implementation 1/7/14
Included document type
03 14/1/14 Tom Candalepas Colin Yeung Tony Alvaro 1/7/14
for registers
04 23/05/14 Tom Candalepas Colin Yeung Tony Alvaro Changed [ ] to ( ) 23/11/14
05 19/1/15 Tom Candalepas Colin Yeung Colin Yeung Review prior to ISO Audit 19/1/16
06 10/2/15 Colin Yeung Colin Yeung Colin Yeung OP Operations 30/1/17
07 15/04/16 Colin Yeung Colin Yeung Colin Yeung EX Expert Witness 30/1/17

Purpose
The purpose of the document, is to provide consistency for Inhabit on a company wide basis and to assist in
easily identifying non-project specific documents. The document numbering convention outlined in this
document is composed of elements that have a specific useful function and is intended to be a simple as
possible.

Related Material
The naming conventions used in this document are based on company procedures and requirements from
experience of previously used systems.

Examples
Technical notes are discipline specific and are internal technical guidelines available to all staff.
Examples include:

IN-PRD-QA002(08)-DocNamingProject Document Naming Procedure Project (Revision 08)


IN-TCN-AC001(00)-TrafficNoiseIntrusionCalc Acoustic Technical Note (Revision 00)
IN-TCN-FR001(02)-DoorTest Fire Technical Note (Revision 02)
IN-PRC-QA001(11)-QualityPolicy Quality Policy (Revision 11)
IN-STF-IT001(03)-ComputerGuide Staff Computer Guide (Revision 03)
IN-REG-QA001(02)-DocRegister Document Register (Revision 02)

Inhabit Group
W.www.inhabitgroup.com [email protected]
Australia | China | Hong Kong | United Arab Emirates | United Kingdom | Indonesia
Document Naming Procedure – Non Project
Reference No.: IN-PRD-QA0002(07)-DocNamingNonProject
Page | 2
Date: 15/04/2016
Rev: 07

Procedure & Schema


Document numbering is defined into: 1/ Project 2/ Non-Project.
This document outlines the naming procedure for “Non Project” documentation.

IN-XXX-YY000(00)-DocumentDescription

A B C D E F

Group A (document purpose):

IN demonstrating that this document is a company document

Group B (document type):

CKL Checklist or Process POL Policy


CLC Calculation PRD Procedure
CON Consulting Notes PRS Presentation
DWG Drawing (CAD or PDF) REG Registers
FRM Form SKT Sketch
LGL Legal STF Staff Guide
MKG Marketing TCN Technical Note
MNG Management Guide TRG Training Guide
MTG Meetings

Group C (function/discipline code):

MU Multiple discipline for more than 2 disciplines or areas


AC Acoustics IT Information Technology
BM BMU LT Lighting
ES ESD/Building Physics LG Logistics
EX Expert Witness OP Operations
FC Façade PP Project Process
FI Finance PT Procurement
FR Fire QA Quality Assurance
HR Human Resources ST Structural

Group D (document number in that group):

This number is in the sequence and refers to the document type. The intranet is to be referenced for relevant
registers in order for this number is not duplicated.

Group E (revision):

[00] the revision number shall be up to 2 characters in brackets. The first issue of a document has a [00] revision
number and all subsequent revisions are numbered sequentially [01], [02] etc. Dates should not be included in
the file name as the revision number provides the sequence of document issues. Registers are exempt and
should not include revision numbers as they are a living document.

Group F (document description):

This is to help find a document easily. This group is not to include spaces, hyphens, underscores or full stops,
with the beginning of a word being a capital letter and overall file length as short as possible and practical.

You might also like