Академический Документы
Профессиональный Документы
Культура Документы
CONTENTS
Clause Title Page No.
ANNEXURES
Annexure-I – Quality Policy.
Annexure-II – Flow diagram of project process.
Annexure-III: Project Activity Quality Plan.
Annexure- IV Organogram For The Project
Engineers India Ltd. (EIL) has established a Quality Management System (QMS) for all
of its functions and areas of operations. The QMS of EIL is certified to ISO: 9001
International standard since 1994. In order to meet the specific, quality related
requirements of a project/job, a project specific quality plan is derived from the
standard QMS, based on the contract requirements and scope of the work in line with
ISO 10005 guide (Quality management – Guidelines for quality plans).
The purpose of this Quality Plan is to identify the quality management system being
applied to the contract between EIL and M/s Nuclear Power Corporation of India
Limited (NPCIL) for the project.
This Project Quality Plan (PQP) is applicable to all project activities of carrying out
Environmental Impact Assessment (EIA) Study project of M/s NPCIL.
Where EIL is PMC and EPCC contractors execute the project on turnkey basis.
This document shall serve the purpose of planning certain activities to achieve the
highest quality of services provided by EIL and shall not be treated as the basis for any
contractual and legal disputes.
The scope laid out in this PQP is applicable from the start of preparation of Terms of
Reference (TOR) to obtaining Environmental Clearance and closure of Contract.
Project Manager shall ensure that all job & lead engineers working on this job shall
implement the quality plan during project realization. Project Quality Manager
appointed by Head Environment shall monitor the implementation of the Quality Plan.
CQA Department shall audit during various phases of the project on implementation of
the Quality Plan in the project.
4.1 PROJECT
Project means the EIA study for Mirthi Virdhi Nuclear Power Park project of M/s NPCIL
situated at Bhav Nagar.
Group of people, having assigned roles and responsibility for completing the project.
The Project Manager leads project team.
Person responsible for leading a functional group, carrying out a particular activity.
4.4 CONTRACTOR
4.5 CUSTOMER
4.6 SUPPLIER
The flow diagram of project processes of this project is given in Annexure-II at the end
of this document.
• ISO:9001 Standard
• ISO:10005 Standard
• Project Contract Documents
• 1-0000-0001 Quality Manual (EIL)
• 1-1741-1000 Quality Manual (Environment Division)
Procedure No. 5-1741-0050 (Procedure for Carrying out Technical Bid Analysis)
Procedure No. 5-1741-0070 (Procedure for Selection of Specialist Agencies in the field
of Environmental Management)
Guideline No. A100-8-1741-0020 (Guidelines for carrying out Field Monitoring and
Supervision)
All project team members of EIL shall focus on the Customer’s requirement during the
project.
Each engineer shall pay attention to the customer’s comments and respond quickly.
They shall identify and determine customer’s requirements, and take necessary action,
or pass Customer’s requirements to Marketing/Project Department, if so required.
During the project execution, Environment Division is responsible for collecting the
customer’s requirements in general. They shall pass the Customer’s requirement to
concerned departments for action as per Contract, or otherwise discuss with customer
if a contract change is required.
The quality policy (see Annexure-I) as committed by Chairman & Managing Director of
EIL and understood within organization shall be followed in the project.
To achieve the project objective, EIL has identified the processes to be controlled
during project realization (see Annexure-II).
The interfaces among various processes/working groups are identified in the interface
plans, and the procedures for carrying out the project activities.
Based on the project realization process, contract and project quality plan, all
engineers shall establish their department procedures/checklists to ensure the
fulfillment of their objectives as required.
The project activity quality plan define responsibility and authority of personnel for the
purpose of performing, review/checking and approval controls of deliverables/services
is given in Annexure-III. In addition, the functions of key personnel is given below:
Project Manager (PM) is directly responsible for the overall successful management of
the Project Quality Plan in order to meet the above objectives. Major responsibility and
authority of PM are:
• to prepare Project Quality Plan, after award of job within 15 days and ensure
that specific requirements of the contract are identified and incorporated into
the Project Quality Plan;
• to monitor the implementation of Project Quality Plan;
• authority to issue CAR over noncompliance to system and also on any
deliverable not meeting specified requirements;
• authority to close CAR reported by him after the corrective action;
• to compile lessons learnt report on a regular basis (half yearly).
Although the project contract has been studied and the Customer’s requirement is fully
understood, EIL shall continue to review customer related process carefully throughout
project tenure in the following aspects:
14.0 COMMUNICATION
Project Manager shall do all communication with customer and the suppliers/
contractors. For efficient and smooth communication with the customer and the
contractors of the project, specific procedure for Project Coordination and
Communication, shall be prepared based on standard procedure no. 5-7700-0020
(Procedure for project coordination and communication) and any project specific/
requirements of customer so as to avoid last minute specific procedures/formats
approvals activities. Procedures to be developed foolproof for smooth execution
without any hurdles of procedural constraints. The coordination procedure shall also
describe the process to be followed when a customer compliment or complaint is
received. The procedure shall take care of customer comments, if any, also.
All information received by PM from external sources shall be systematically filed for
quick traceability and control.
14.2.1 An internal kick off meeting shall be conducted before the project kick off meeting with
the customer. In this internal meeting PM shall present the description of project
facilities, brief scope of work, and proposed execution methodology to the
nominated/likely team members.
14.2.2 Project Manager shall ensure that all inputs, requirements and information is promptly
communicated to the concerned project team members.
14.2.3 Project Quality Manager shall participate in project review meetings and shall be
responsible for providing information on the performance of quality management
system (inputs to top management/MR on CARs, customer complaints, supplier/
contractors feedback, corrective actions, etc.) in the project review meeting.
15.1 Project team of qualified personnel of various disciplines, based on their qualification
and experience, shall be formed for the project. The project organogram showing key
persons deployed and communication channels shall be prepared by PM.
Project Manager shall prepare the resource plan for the project based on the scope of
work and contractual requirements. The resources including human resources,
infrastructure (workspace, furniture, document storage space, computers, software,
storage space on server, Xerox machine, printers, transportation, communication
facilities viz. fax, telephone, e-mail, internet, courier service, etc.) shall be planned and
deployed as per approved plan, in timely manner so as the project work
progress/quality is not affected in any way. Any infrastructure/facilities to be provided to
the customer, as per contract, shall also be covered in the resource plan.
15.3 TRAINING/AWARENESS
PM and PQM shall arrange structured awareness program for the project team
members on the QMS requirements contained in this PQP and other requirements of
the customer, if any. The awareness program shall be planned within 15 days from the
internal kick off meeting.
17.1 All standard QMS documents viz. standard procedures, guides, checklist etc. are
controlled by Environment HOD through divisional quality representative. The latest
version of such documents is made available to all engineers in the form hard copies in
addition to soft copies in intranet.
17.2 Documents, which are project specific and represent requirements of the project
(project specific procedures and deliverables), shall be identified and subjected to
control as detailed below:
Standard format and templates shall be used for generating documents and drawings
for the project. These formats and templates shall be made available by lead engineer
at EIL Intranet for common use.
Revision numbering philosophy for the project documents shall be as per Procedure
No. 8-76-0004.
17.3.1 The initial and subsequent revisions of documents shall be reviewed and approved
before issue for specified use in line with the standard quality plans and procedure for
design control (5-0000-0030). Approval status shall be indicated on the document
through signatures of the approving authority. Signatures shall be preferably in color
other than black ink. Name/Initials of the performer, checker/reviewer and approver(s)
shall be shown in the issue table. In addition to the review/checking of technical
aspects, the reviewer/checker shall ensure that the various control points mentioned in
the checklists of concerned department are taken care.
The initial and subsequent revisions of documents shall be sent to customer for
comments/approval in line with the approved quality plans/contract requirements.
Document class shall be indicated in the transmittal based on the definition given in
transmittal format.
17.5.1 All engineers shall prepare index of deliverables. The index shall show the document
title, document number, document revision number and date of issue. Project Quality
Manager shall prepare the index of QMS documents for the project.
17.5.2 Lead Engineer, while releasing their drawings or issuing the revised version, shall
immediately update the status in EDMS. A copy of the relevant page of drawing index,
on which drawing description appears, shall be attached so that both the documents
are issued together to users internally as well as externally.
17.6.1 Project Quality Manager shall control the Project specific QMS documents. The QMS
documents shall be available on electronic media and accessible to the project team.
Hard copy of the QMS documents shall be accessible to all Lead Engineers.
17.6.2 Transmittal Format No. 5-0000-0040-F3 shall be used for transmitting documents for
IDC. In case of task force situations the IDC comments can be obtained using any one
of the following methodologies:
• getting the comments from the affected disciplines marked on the drawings/
documents itself/soft files;
• keeping a separate record of comments from the respective disciplines on
separate sheets or through exchange of e-mails;
• conducting a meeting of affected discipline engineers.
17.6.3 Transmittal Format No. 5-7700-0020-F3 shall be used for transmitting the documents
to customer, whenever the documents are transmitted to them in the form of hard
copies.
17.6.4 Lead Engineers shall be responsible for preparing the transmittals and issuing
documents as per respective interface plan/guide for engineering coordination.
17.6.5 Documentation officer (DO) shall be responsible for preparing the transmittal and
distributing the documents to customer. Record of transmittals, sent shall be
maintained in Format No. 3-0000-0003, by DO. Persons carrying out VPTL activities
can be DO for the concerned project.
17.6.6 All superseded documents or section thereof shall be prominently marked superseded
documents or section thereof shall be prominently marked "SUPERSEDED" in bold
letters and segregated and stored separately immediately after a revision has been
issued/received. Superceded document need not be stored except where ambiguity
w.r.t. third party is encountered.
All Engineers shall follow the project activity quality plans of their respective function, to
the extent applicable in job, as given in Annexure-III. This plans identifies the
activities/deliverable type, relevant procedure, if any, code of conformance, resources
for performance and checking/monitoring, approval requirements and authority.
• checklists;
• applicable formats;
• divisional/departmental procedures;
• procedures referred in this document.
Impact assessments shall carefully study the Project Contract, especially about the
technical part, identify the Customer’s requirement and ensure that assessment shall
satisfy the contract requirement and achieve the Customer’s expectation bounded by
the Contract including all amendments.
a) the activities are considered for both construction and operation stages,
b) Project activity quality plan.
20.2 INPUTS
Interface plan identifies the required inputs for carrying out environmental impact
assessment and is given in Environment Division Quality Manual (1-1741-1000). Input
documents shall be reviewed by engineer for adequacy and completeness. Any
incomplete, ambiguous or conflicting requirement shall be resolved before proceeding
with design/engineering activity.
• meet the all input requirements for construction and operation phases;
• include design/engineering deliverables required for purchasing, detailed
drawings for construction, an operation and maintenance manual etc;
• contain or reference project acceptance criteria in the form of job specifications;
• specify the characteristics of the project that are essential for its safe and
proper use.
The type of output may be documents, specifications, drawings and data sheets.
20.4.1 As part of the Quality Plan, An assessment Review shall be developed to address HSE
hazards and exposure, Reliability, Operability, Maintainability and Standardization.
The Review shall assure:
• compliance of the assessment with the process design basis and engineering
design basis;
• optimization for minimum lifecycle costs;
• verification of technical integrity;
• completion of documentation in readiness for the next project phase.
Verification shall be performed in accordance with standard quality plan and checklists
to ensure that the design outputs have met the design input requirement.
The validation shall be performed through environmental monitored data to ensure that
the resulting project is capable of meeting the requirements for the specified
application or intended use as per contract. Wherever practicable, validation shall be
completed prior to the delivery of the assessment.
The objective of controlling the use of software is to ensure that calculations and
analysis are performed using authorized software and that the results can be traced to
the software and version that was used for the task.
•
validation, confirmed by the provision of a Validation Certificate. For software
built on proprietary software, e.g. spreadsheets, validation shall include manual
spot checks of calculations, checking validity at the numerical limits of the
inputs/output and production of a User’s Guide;
• authorization of users by supervisors to confirm that they understand the
software, have access to the User’s Guide and that any limitations of the
software do not impair its use for its proposed task;
• format registration of all versions of software in use
.
21.0 PROJECT DOCUMENTS/DRAWINGS/EQUIPMENT NUMBERING/CODING
21.1 All deliverables shall be appropriately identified by unique numbering to ensure that
these are traceable and well identified for future reference.
Guidelines for Electronic Flow of Documents No. 8-76-0031 shall be followed for
electronic file numbering of drawings and other documents.
22.1 Numbering of correspondence (day to day normal activities), fax, moms, letters, notes,
transmittals to customer shall be as per Project Co-ordination procedure No. A100- 5-
7700-1004 (Job specific).
Numbering of inter office memorandum (IOM), transmittals for internal use, minutes of
meeting (corporate review) shall be as follows:
A B C D
A - Job number
C - File No. (number of digits can vary depending on file numbering system)
23.1 Lead engineer shall prepare a file list, using the file numbering system developed by
their respective departments, based on the actual requirements and update the same
as required and distribute the updated list to all concerned.
23.2 Hard Copy of the documents shall be filed in respective files. Lead engineers shall
ensure that backlog on filing does not exceed one week.
23.3 Electronic copy of all deliverables, at different stages of generation, shall be stored by
the performer in his PC/server.
23.4 Electronic copies of documents of in-process stage and final stage shall be stored in
separate folders. These folders shall be stored in a main folder. Different category of
documents viz. specifications, drawings, study reports, etc. shall be stored in separate
sub-folders.
24.1 TENDERING
24.1.1 C&P shall prepare the tender procedure for Data collection contracts for the project.
The procedure shall be reviewed and approved by customer.
24.1.3 Respective engineering disciplines shall be responsible for including the standard ITPs
in the MRs & PRs.
PQM shall evaluate the bids received, w.r.t. the Specification No. 6-0000-0001 &
documents submitted against supplier data requirement related to QMS.
Documentation Officer (DO) shall be responsible for receipt and routing of the
supplier’s documents received for review/approval by engineers.
• monitor submission of Job Quality Plan, HSE Plan, Job (Work) Procedure,
ITPs, by contractors, its review & approval;
• monitoring contractor’s activities to verify that activities are performed by
contractors as per approved quality plan, procedures & ITPs;
• monitor that specs for positive material identification is being followed;
• review and approve the procedure for control of monitoring & measuring
devices and monitor its implementation;
• furnishing list of testing laboratories.
Project internal quality audits shall be planned and conducted to check the compliance
of QMS in various functional areas involved in the project. During these internal quality
Head of Environment Division shall ensure detailed analysis of the reasons and
remedial actions. The data shall be systematically analyzed and corrective action taken
by the head of division/department to whom target functional group belongs to, in order
to ensure that the problem do not recur in future projects. Procedure for Feedback,
Corrective Action and Preventive Action - Document No. 5-0000-0130 shall be followed
for this purpose.
31.1 The project specific records, which need to be maintained, are listed in project record
matrix.
Lead engineer shall maintain one set (Hard copy) of their deliverables with their group.
DO under the supervision of PM shall maintain only the records of incoming and
outgoing documents (register). Back up of deliverables shall be maintained on server
or CDs, during production and after final approval.
The documents and records, which are required to be handed over to customer, as per
contract requirements, shall be prepared in the storage medium as desired by the
customer.
Providing ¨Technical Inputs for the Study¨ to NPCIL for starting the job.
Preparing TOR
Procedures:
Guidelines:
Formats:
Checklists:
Sl. Activity / Process Description Procedure Code of Performer Checker / Approver Sampling Plan
No. Number Conformance Reviewer Reviewer Approver
1. Carrying out environmental impact 5-17-41-0040 AERB Job Lead Group 100% Random
assessment studies Guidelines Engineer Engineer Leader Checks
and related
standards
2. Preparation of Terms of Reference for A100-17-41- AERB Job Lead Group 100% Random
EIA study 0010 Guidelines Engineer Engineer Leader Checks
and related
standards and
MOEF
Guidelines
3. Preparation of tender inputs for selection A100-17-41- Job Lead Group 100% Random
-
of baseline data collection agency 0020 Engineer Engineer Leader Checks
4. a) Prediction and Assessment of Impacts 5-1741-0040 Job Lead Group 100% Random
-
Engineer Engineer Leader Checks
b) Preparation of EMP 5-1741-0040 Job Lead Group 100% Random
-
Engineer Engineer Leader Checks
c) Preparation of EIA Reports 5-1741-0040 Job Lead Group 100% Random
-
Engineer Engineer Leader Checks
5. Preparation of technical bid analysis 5-17-41-0050 Job Lead Group 100% Random
-
Engineer Engineer Leader Checks
6. Selection of specialist agencies in the 5-17-41-0070 Evaluation HOD 100% Random
- -
field of environmental management Committee Checks
7. Performance monitoring of environmental 5-17-41-0080 Job Lead Group 100% Random
-
data collection agencies Engineer Engineer Leader Checks
8. Procedure for execution of various A100-17-41- Job Lead Group 100% 100%
-
activities 0030 Engineer Engineer Leader
ANN
NEXURE-- IV ORGA
ANOGRA
AM FOR THE
T PROJECT
Mr J K Joshi
EIA C
Coordinator AB
BBREVIATION
NS
PM ‐ Projecct Manager
Mr R
R S Prasad PQM ‐ Project Quality Manager
M
PM
M & PQM FAE ‐ Functtional Area Expert
APC ‐ Air Po
ollution Conttrol
WPC ‐ Wateer Pollution Control
C
Mr Vikram Singh SHWM ‐ Solid waste w &
Lead
d Engineer Hazardous Waste Manaagement
SE ‐ Socio‐EEconomic Aspect
EB ‐ Ecologgy & Bio‐diversity
Mr SSrikumar Mr Maanish Kumar Mr Vinodh Kumarr
Malakar Jaiswal MS
Job EEngineer Job Engineer b Engineer
Job
Mrr P K Goel Mr S V R
M
Mr R
R S Prasad Pro
of. D N Jena D
Dr P A Aze
FAEE ‐ WPQ & Sub
bramanium
FA
AE ‐ APC FAE ‐ SE FAE‐ EB
S
SHWM FA
AE ‐ Noise
emplate No
o. 5-0000-0001-T2 Re
ev. 1 Copyyrights EIL – All rights reserved