Professional Documents
Culture Documents
Document No.:
LPSHMB
Page 2 of 9
Revision No.: 0
-2Page 2
9/22/2016
- 2 - of 27
- 2 -Ulysses R. Gotera
Page 2
9/22/2016Confidential
Page 2
9/22/2016Page 2 of
112
Date:9 APR 2012
REV.
CONTENT OF REVISION
Issue for review and comment
DATE OF REVISION
9 Apr 2012
PTSC-LP
Document No.:
LPSHMB
Page 3 of 9
Revision No.: 0
-3Page 3
9/22/2016
- 3 - of 27
- 3 -Ulysses R. Gotera
Page 3
9/22/2016Confidential
Page 3
9/22/2016Page 3 of
113
Date:9 APR 2012
TABLE OF CONTENTS
SECTION
DESCRIPTION
1.
PURPOSE
2.
SCOPE
3.
REFERENCE
4.
DEFINITION
5.
PROCEDURE
APPENDIX 1:
APPENDIX 2:
SAMPLE OF DEFINITIONS
PTSC-LP
Document No.:
Page 4 of 9
Revision No.: 0
LPSHMB
-4Page 4
9/22/2016
- 4 - of 27
- 4 -Ulysses R. Gotera
Page 4
9/22/2016Confidential
Page 4
9/22/2016Page 4 of
114
Date:9 APR 2012
PTSC-LP
Document No.:
Page 5 of 9
Revision No.: 0
1.0
LPSHMB
-5Page 5
9/22/2016
- 5 - of 27
- 5 -Ulysses R. Gotera
Page 5
9/22/2016Confidential
Page 5
9/22/2016Page 5 of
115
Date:9 APR 2012
PURPOSE
To establish the process and format for the systematic documenting of procedures issued by
PTSC-LP
2.1
SCOPE
This applies to the preparation and maintenance of all procedures for issue by PTSC-LP.
3.0
REFERENCES
None
4.0
DEFINITIONS
None
5.0
PROCEDURE
5.1
Each Procedure shall consist of a cover sheet, revision status sheet, a table of contents sheet and be
divided into five (5) sections as follows:
1.0 Purpose
2.0 Scope
3.0 References
4.0 Definitions
5.0 Procedure
Sub-sections to each of the five sections may be added as necessary.
Attachments to the procedure will form appendices and be sequentially numbered Appendix 1,
2, 3 etc.
The procedure header style and content shall be as represented by this procedure.
General text font shall be Times New Roman (12 point) and square bullets. The date should be
written with the month in letter form.
Each procedure will describe in detail the tasks (and, when applicable, include interface
expectations/requirements) to be undertaken in the context of who does what, when ,where and
PTSC-LP
Document No.:
LPSHMB
Page 6 of 9
Revision No.: 0
-6Page 6
9/22/2016
- 6 - of 27
- 6 -Ulysses R. Gotera
Page 6
9/22/2016Confidential
Page 6
9/22/2016Page 6 of
116
Date:9 APR 2012
how , together with the forms, reports, checklists, registers etc. to be used, to successfully
accomplish the process outputs of the subject procedure.
Examples of standard forms (e.g. checklists, inspection records, reporting formats, registers etc.)
associated with the subject process will, where required, be contained within the Appendices to the
procedure.
Process flow charts and tables may be used to further clarify the process or procedural
requirements and may be appended to the procedure.
The purpose of a procedure is to give clear instruction for the implementation of a process or
activity. A brief guide to that aim is contained in Appendix 1.
5.2
Procedure Numbering
Each procedure will be subject to review and signatory approval by the originating
department/function Manager and Project Manager.
Prior to issue of procedures, they will be subject to formal review by the Quality function who
shall ensure that the content complies with procedural requirements.
The author shall submit new or revised procedures to the relevant QA/QC Manager for review and
approval prior to issue for implementation.
Each department or function head is responsible for the generation, hard copy distribution, control
and current validity of the procedures governing their activities. Electronic copies will be provided
to the Document Control Manager who shall make the procedures available electronically via the
QA/QC internal server site. A set of authorised hard copies of their own procedures is held by
each department/function. The electronic versions available throughout PTSC-LP shall be in pdf
format and shall contain a macro which ensures any prints taken are endorsed as Reference
Only.
The electronic listing of procedures under each function shall serve as an index of the latest
procedures and their revisions.
PTSC-LP
Document No.:
LPSHMB
Page 7 of 9
Revision No.: 0
-7Page 7
9/22/2016
- 7 - of 27
- 7 -Ulysses R. Gotera
Page 7
9/22/2016Confidential
Page 7
9/22/2016Page 7 of
117
Date:9 APR 2012
It is the responsibility of all employees to notify their department/ function head, of procedural
requirements that are:
Unclear;
No longer valid;
Inadequate in describing the process;
Impractical;
Inefficient;
Ineffective;
Conflicting with other specified Company requirements.
The department/function head shall in turn, implement the necessary corrective action and amend
the procedure accordingly.
APPENDIX 1
GUIDE TO POLICY AND PROCEDURE WRITING:
What is the difference between policy and procedure?
POLICY = RULES
PROCEDURE = ACTION
Policies:
Describe the rules that establish what will or will not be done.
Can range from a broad view to specific rules.
Are usually expressed in standard sentence and paragraph format.
Include:-
PTSC-LP
Document No.:
Page 8 of 9
Revision No.: 0
LPSHMB
-8Page 8
9/22/2016
- 8 - of 27
- 8 -Ulysses R. Gotera
Page 8
9/22/2016Confidential
Page 8
9/22/2016Page 8 of
118
Date:9 APR 2012
Chose a font and format and DO NOT CHANGE, be consistent, always check format and use
spellcheck, (make sure language is set to English UK)
Avoid the use of jargon, unnecessary technical expressions and fancy vocabulary.
Be Consistent.
Use an approved policy and procedure template - documents written and presented in a
consistent manner aids readability.
Use definitions to ensure consistency of terms throughout policies and procedures.
Be specific mean what you say and say what you mean
Rather than submit the appropriate form say Submit the Inspection Form.
If action is mandatory shall, must or will is used.
If the action is recommended or valid reasons to deviate from the requirement may exist in
particular circumstances, then should or may is used.
Avoid the use of information that is quickly out dated and needs regular amendment
PTSC-LP
Document No.:
Page 9 of 9
Revision No.: 0
LPSHMB
-9Page 9
9/22/2016
- 9 - of 27
- 9 -Ulysses R. Gotera
Page 9
9/22/2016Confidential
Page 9
9/22/2016Page 9 of
119
Date:9 APR 2012
PTSC-LP
Document No.:
LPSHMB
Page 10 of 9
Revision No.: 0
APPENDIX 2
- 10 Page 10
9/22/2016
- 10 - of 27
- 10 -Ulysses R.
Gotera
Page 10
9/22/2016Confidential
Page 10
9/22/2016Page 10 of
1110
Date:9 APR 2012
PTSC-LP
Document No.:
LPSHMB
Page 11 of 9
Revision No.: 0
- 11 Page 11
9/22/2016
- 11 - of 27
- 11 -Ulysses R.
Gotera
Page 11
9/22/2016Confidential
Page 11
9/22/2016Page 11 of
1111
Date:9 APR 2012
PTSC-LP
Document No.:
LPSHMB
Page 12 of 9
Revision No.: 0
- 12 Page 12
9/22/2016
- 12 - of 27
- 12 -Ulysses R.
Gotera
Page 12
9/22/2016Confidential
Page 12
9/22/2016Page 12 of
1112
Date:9 APR 2012