0301-SI-004-02 - Engineering Management CORPORATE
0301-SI-004-02 - Engineering Management CORPORATE
Serial Rev
GENERAL PROCEDURE
ENGINEERING MANAGEMENT
0301-SI-004
SIGNED DATE
DOCUMENT STATUS
(name & initials) DD/MM/YY
DOCUMENT REVISIONS
This document is the property of SICIM spa who will safeguard its rights according to the civil and penal provisions of the law.
GENERAL PROCEDURE
Index
1 SCOPE ............................................................................................................................................................4
2 PURPOSE .......................................................................................................................................................4
3 TERMS AND DEFINITIONS ............................................................................................................................5
3.1 Abbreviations ...........................................................................................................................................5
3.2 Definitions ................................................................................................................................................5
4 ENGINEERING DEPARTMENT ORGANIZATION .........................................................................................7
5 DELIVERABLES TO EM .................................................................................................................................7
6 REFERENCE DOCUMENTS AND DOCUMENTED INFORMATION ............................................................7
6.1 Standards.................................................................................................................................................8
6.2 SICIM documents ....................................................................................................................................8
7 INTERNAL INTERFACES ...............................................................................................................................9
8 PROCESS DEFINITION ..................................................................................................................................9
8.1 General ....................................................................................................................................................9
8.2 Risk Based Thinking ................................................................................................................................9
8.3 Inputs .....................................................................................................................................................10
8.4 Property belonging to customers or external providers .........................................................................10
8.5 Outputs ..................................................................................................................................................11
9 PROCESS ACTIVITIES.................................................................................................................................11
9.1 Generals ................................................................................................................................................11
9.2 Design & Development Controls ...........................................................................................................11
9.3 Engineering planning .............................................................................................................................12
9.4 Progress monitoring ...............................................................................................................................13
9.5 Key Indicators ........................................................................................................................................13
9.6 CHANGES MANAGEMENT ..................................................................................................................14
10 RESOURCES AND HUMAN RESOURCE INTERFACE ..........................................................................14
11 ASSIGNING ACTIVITIES TO EXTERNAL ENGINEERING OFFICE .......................................................15
11.1 Scope of work definition.........................................................................................................................15
11.2 Technical Bid evaluation ........................................................................................................................15
11.3 Order issuing .........................................................................................................................................16
11.4 Monitoring ..............................................................................................................................................16
12 DESIGN CONTROL AND REGULATORY REQUIREMENT ....................................................................16
12.1 Design Review .......................................................................................................................................16
12.2 Design Verification .................................................................................................................................17
GENERAL PROCEDURE
GENERAL PROCEDURE
1 SCOPE
The scope of this procedure is to describe how engineering activities will be managed by SICIM to ensure that
COMPANY requirements are fulfilled.
This procedure is applicable to projects that require development of:
• Basic engineering
• Detail engineering
• Field design (meaning of field design is detailed at paragraph 3.2 of the present procedure)
and apply to engineering department of:
• Head Quarter
• Branch Offices
• Project Offices
• Site Offices
Minor changes to the present procedure are allowed only if required by project performed in Joint Venture or
Consortium with other partner(s).
These changes shall be agreed with Corporate Engineering Manager and formalized through a release of a
Engineering Management procedure issued for the project.
This document do NOT apply to the following process, as are ruled by procedures belonging other departments:
• Hydro test and Technical Supports (Methods)
• Welding and NDT
2 PURPOSE
Engineering includes the activities required to translate the scope of work into specifications, drawings and other
documents utilized for the procurement, manufacturing, assembly, installation, inspection and commissioning of
the product.
Planning and co-ordination of the Engineering activities, regulated by the present document, are those that will
be implemented following the acquisition of a given project and the relevant contract awarding notification.
SICIM starting point are requirements of ISO 9001 (reported in italic blue in this documents), such requirements
are general in their nature and this documents provide SICIM interpretation of the applicable code.
When determining the requirements for the products and services to be offered to customers, the organization
ensure that:
1) the requirements for the products and services are defined, including:
a) any applicable statutory and regulatory requirements
b) those considered necessary by the SICIM
2) The organization can meet the requirements of the products and services it offers.
For the purpose the roles of area manager and country manager are considered equivalent.
GENERAL PROCEDURE
3.1 Abbreviations
Construction Manager .......................................................................................................................... (CM)
Customer ................................................................................................................................. (COMPANY)
Engineering Manager ........................................................................................................................... (EM)
Engineering Project Quality Plan...................................................................................................... (EPQP)
Front End Engineering Design ......................................................................................................... (FEED)
Head Quarter ........................................................................................................................................ (HQ)
Organization ..................................................................................................................................... (SICIM)
Project Control Manager .................................................................................................................... (PCM)
Project Engineers .................................................................................................................................. (PE)
Project Engineering Manager ............................................................................................................. (PEM)
Project Manager ................................................................................................................................... (PM)
3.2 Definitions
Area Manager a manager of a business and or organization who has responsibility for a
specific geographical area.
Basic engineering: Basic engineering usually include a reduced set of basic studies and data
required to assess feasibility, cost estimation and to allow the development of
detail engineering, like:
Country Manager: Person who is responsible for organization and management of local
permanent office.
GENERAL PROCEDURE
Design and development:set of processes that progressively detail requirements for an object to met
contractual performance.
Detail engineering: Detail engineering include development and finalization of all documents
required for material purchasing, plant construction and commissioning related
to all disciplines, process, piping, pipeline, instrument, electrical , civil.
Field Design: Field design is related to translation of general construction drawings and
standards into a specific drawing related to permanent construction, collating
information received by detail engineering (supplied by Sicim or COMPANY ),
topographer, surveyors, third parties. Typical deliverable for field design are
drawings for construction and as built.
Process: Set of interrelated or interacting activities which transforms inputs into outputs
Product: A product is a tangible or intangible output that is the result of a process that
does not include activities that are performed at the interface between the
supplier (provider) and the customer.
Review: Activity to figure out how well the thing being reviewed is capable of achieving
established objectives.
Site Office: Office are generally located near construction site and are temporary in nature,
only there for the duration of the construction works related to a specific Project.
Validation: Process that uses objective evidence to confirm that the requirements which
define an intended use or application have been met
Verification: Process that uses objective evidence to confirm that specified requirements
have been met.
GENERAL PROCEDURE
5 DELIVERABLES TO EM
It is required that the following deliverables as per schedule and as applicable, according to project scope, are
delivered to Corporate Engineering Manager (EM) by mail:
GENERAL PROCEDURE
b) Storage and preservation, including preservation of legibility. SICIM store documents preferably in
electronic format on document management system or server. It is IT department responsibility to plan
and execute server backup as per IT procedure(s).
Actually it is uncommon however, If paper copies of the master documents are used for the project DCC
is responsible for filing copies in a proper place to preserve paper from deterioration and avoid loss of
legibility.
c) Control of changes (document control)
The organization shall ensure that relevant documented information are amended, and that relevant
persons are made aware of the changed requirements, when the requirements for products and services
are changed.
If there are no requirements by Client, SICIM will define it's proper Control of changes system in the
project specific document management procedure.
Changes done from previous revision have to be clearly identifiable on the relevant document,as
minimum, electronic filename must report the revision.
d) Retention and disposition. DCC is responsible to store files in an ordered archive on server in electronic
format or using a document management program, and according to the specific project Document
management system.
If there is no clear requirement in the project documents management procedure, ANY printed copies are
considerer “uncontrolled” copies.
This procedure is the guideline for defining the minimum requirements and responsibility for document
management, filing and preservation of the design process. Site/Project procedure may further detail this
management, according to the specific contract requirements.
Documented information of external origin determined by the organization to be necessary for the planning and
operation of the quality management system shall be identified, included into project deliverable list and properly
stored with project documents.
The organization shall ensure that relevant documented information are amended, and that relevant persons are
made aware of the changed requirements, when the requirements for products and services are changed.
Mail is generated by DCC after upload a revised document or comment sheet on server to PEM and Lead
Engineers with detail of received documents.
The revised documents will be subjected to the same iter (review, verification and validation) of any original
document.
6.1 Standards
ISO 9001:2015 Quality management system – Requirements
GENERAL PROCEDURE
7 INTERNAL INTERFACES
The execution of the assigned tasks requires the Engineering department to manage proactively internal interface
with other departments, such as:
• Subcontract Management
• Procurement & logistic
• Quality
• HSE
• Operations & Project Control
• Contract management & Legal
• Special processes & welding
• Methods & Hydro test
• Human Resources
8 PROCESS DEFINITION
8.1 General
The Engineering process is defined by its basic components that will be developed in the following phases:
a) Risk Based Thinking
b) Input
c) Output
d) Process activities
e) Resources and human resources interface
f) Internal controls and regulatory requirements
g) Verification of effectiveness
GENERAL PROCEDURE
8.3 Inputs
Input analysis is performed by PEM, and appointed staff, as first start activity upon the contract awarding, and
forms the basis for subsequent engineering and development activity.
Inputs related to product requirements are defined / identified by PEM and lead Engineers and the corresponding
records maintained, through the support of the DCC and according to the project document management system.
Inputs include:
a) Contract requirements
b) Front End Engineering Design (FEED) with scope of work, delivered by Client as part of the contract
c) functional and performance requirements;
d) applicable statutory and regulatory requirements;
e) information derived from previous similar engineering projects, where applicable;
f) statutory and regulatory requirements;
g) standards or codes of practice that the organization has committed to implement;
h) potential consequences of failure due to the nature of the products and services;
i) other requirements essential to engineering and development process;
Product requirements specified by the COMPANY must be complete, unambiguous and not in conflict with each
other. Otherwise, PEM will issue design changes or technical clarifications queries, as per project procedure, to
COMPANY in order to obtain all data, details, answer, or call for a clarification meeting.
PEM is responsible to maintain, update, file and distribute the technical queries and register and when required,
assess the contractual impact on cost and schedule, and transferring information to Project Manager and Project
Control Manager.
Inputs are reviewed to verify adequacy and highlight discrepancies. Result of such review will primarily be
formalized through one or a combination of the followings documents:
- review of Front End Engineering Design (FEED), when provided by COMPANY;
- other method required by Contract requirements (Ex: countersignature of a specific form proposed by the
COMPANY such as an "Engineering Endorsement record sheet" or similar, etc.);
- verification of the completeness of the documentation received after contract award compared with the list of
documentation attached to contract (Contract, specifications, etc.);
- possible documentation derived from previous engineering experiences (notes, photocopies, records, etc),
divided for location and/or COMPANY, as held opportune by PEM;
- possible technical opinions of competent inside resources, external advisors and / or engineering
subcontractor;
GENERAL PROCEDURE
The Contract Manager will inform the Project Manager that will inform the customer through the project
communication process, using, as appropriate, mail communication, Technical Query, derogation, Non
Conformity, etc.
8.5 Outputs
Engineering and development outputs are formalized in a form that enables verification against the design and
development input, and they are subject to approval before being released.
Outputs from engineering and development must:
a) meet engineering input requirements and comply with contract requirements
b) are adequate for the subsequent processes for the provision of product and service
c) include or reference monitoring and measuring requirements, as appropriate, and acceptance criteria;
d) specify the characteristics of the products and services that are essential for their intended purpose and their
safe and proper provision.
e) ensure activity review.
The main types of documents produced as outputs of SICIM engineering and development process are:
- document of synthesis of the input data (if any) through a document that gathers together the basic and
engineering data of the project (this document will also collect comments to the FEED document as input)
- Project engineering management procedure(s).
- Project deliverable, including material requisitions, material take offs, specifications, calculation reports,
drawings, data sheets, etc.
- other documentation foreseen for satisfy project requirements, according to the project specifications
The organization retain documented information on design and development outputs using document managing
procedure as described in dedicated paragraph.
9 PROCESS ACTIVITIES
9.1 Generals
The organization shall establish, implement and maintain a design and development process that is appropriate
to ensure the subsequent provision of products and services.
During planning of engineering and development, the organization shall specify:
• the engineering and development stages
• Control, review, verification and validation procedures for each engineering and development stage
• Responsibilities and authorities for engineering and development
• Contract requirements
GENERAL PROCEDURE
d) validation activities are conducted to ensure that the resulting products and services meet the requirements
for the specified application or intended use; (ref. 12.3 Design Validation)
e) any necessary actions are taken on problems determined during the reviews, or verification and validation
activities;
f) documented information of these activities is retained.
Project Engineering Manager in consideration of the assigned Scope of Work and the magnitude of the project
and available resource shall better define type of extension of such control. The present document form the official
corporate guideline to be followed up.
SICIM shall coordinate the interface between the different groups involved in engineering and development in
order to ensure effective communication and clear assignment of responsibility.
PEM will plan, in collaboration with the Project Manager and Project Control Manager, the following activities:
- internal Engineering Kick Off Meeting. Attendants of the meeting will be the PEM, the lead engineers for
each discipline, PEM of external engineering offices and eventually eternal specialists, project
procurement manager if and when required;
- subdivision of the engineering activities (stages / tasks);
- definition, schedule and modality of execution of the activities of review, verification and validation of the
engineering activities according to the contract;
- planning of the activities (process stages), that may consist in the redaction / production of:
a) a planning of execution of the engineering tasks (preliminary work planning)
b) deliverable list with issuing schedule complete of a "weight" in hours, or equivalent, is assigned to
each document.
c) a list, register or log of all the documents /specifications that have to be developed / issued for
cover the entire scope of work
d) definition of progress measurement system for the project, according to COMPANY “weightage”
defined into contract, or proposed by PEM, in cooperation with PM and project PCM.
e) other type of different Documents, as held opportune, in relationship to the extension of the project
and the contract requirements / applications
GENERAL PROCEDURE
- collaboration with Project Control Manager for integration of engineering planning into overall project
planning and identification of relation between activities
When apply, these documents may also be produced/released by the engineering subcontractor entrusted of the
activities and submitted to PEM for review / approval.
Planned outputs are managed and updated, as appropriate, according to engineering and development progress.
To such purpose, during the execution of the engineering activities PEM will follow the development and check of
the documents developed, to verify its correspondence to the contractual requirements and the conformity to the
statutory laws.
Specific alignment Meeting will be organized, if required, by Corporate Engineering Manager in Head Quarter
offices, involving interfaces of engineering, quality, project control and Operation department, to summarize the
status of engineering activities of all the active projects and of the project that have been completed during this
period.
c) Site Project Engineer shall follow the commissioning of project equipment/items with TAG number (for
bulk material it is not required), from arrival on site up to hand over to COMPANY. For this purpose a
hand over dossier for each Material Requisitions related to tag items shall be implemented and updated,
as a live document, following the guideline of Attachment 8. KPI is ON-OFF with reference to the project.
GENERAL PROCEDURE
It will stay open (OFF) until ALL the items have been successfully handed over and will be activated by
pre-commissioning and commissioning of relevant tag items.
PEM shall reviews the resources available for the project, correlating them with the work extension and
ascertaining, in cooperation with EPC Coordination Manager and Project Manager, the need to acquire additional
resources and/or suppliers of specialized services.
The relevant considerations will be formalized and shared with PM and Area/Country manager, to consolidate the
relevant decisions.
GENERAL PROCEDURE
For the positions with management responsibilities (first level / direct interface with client's representatives) , if
required by the CONTRACT, curriculum vitae will be submitted to the COMPANY for approval and COMPANY
requirements will be considered during the selection
The allocation of resources will be formalized through a project organization chart that will highlight the roles and
dependencies inside the project, and any dependencies and interfaces between the HQ and site organizations.
Moreover must be cleared any reports and / or interfaces with subcontractors and / or external companies.
GENERAL PROCEDURE
11.4 Monitoring
Following assignment of the order PEM, with the purpose to allow a regular and effective development of the
engineering works will organize for an engineering Kick off meeting with at least the following agenda
- clarification on scope of works, applicable documents, FEED endorsement, COMPANY requirements
- confirmed project organization, CV of assigned personnel and focal point
- finalization of deliverable list and schedule
- progress measurement, reporting and invoicing procedure
- engineering verification milestone
- CONTRACTOR focal point (PEM in first instance and as preferred choice)
- document and information path/exchange route
Monitoring of the performances of the subcontractor must conform the system implemented for the project as
described in the chapters 9.4 Progress monitoring and 9.5 Key Indicators.
PEM will receive, review and approve the external engineering office progress report, issued at least on a monthly
basis.
GENERAL PROCEDURE
- monitoring of engineering progress with respect to planned and on the basis of the development of the
project itself (e.g., monitoring and updating of the document issuing plan and feedback received from the
yard as geological surveys, topographical studies, examining consistency and soil compaction, etc..)
- evaluation of the problems deriving not only from the type of job to be performed, but also any preparatory
studies required for its realization (e.g., need for highly-specialized solutions, issues related to acquisition
of easements and permits)
- identification and correction of problems relating not only to the realization of the individual job itself, but
also the influence the latter could have on other parts of the project as a whole
- any problems, insufficiencies, incompatibility or interference between the various engineering disciplines
and/or areas, as well as in the work to be performed (e.g., mechanical equipment locations, foundations,
piping layout, drains, cable ways, underground utilities, etc..)
- possibility of design optimization and different design methodologies / software
- environmental impact
- COMPANY requirements regarding job functionality, safety, reliability, potential maintenance problems
and access in order to maximize the operational value of the work
- the verification of coherence of the specifications of the materials employees with the requisite of
temperature, pressure, corrosion allowance, etc.. defined by the project (es: type of the steel, material
thickness, etc.)
- collection and transfer to the involved parties (project engineer, Site Manager, as well as to the personnel
employed to the activities of design, construction and installation) of the notes and recommendations
produced by the engineering subcontractor (when foreseen) or by manufacturers that could have
influence on the design, erections, commissioning, quality and/or on the safety of the project
Records of the results of the reviews and any necessary actions will opportunely preserved and managed by PEM
in form of check lists, minutes of meetings, etc.
GENERAL PROCEDURE
Registration of inspection/check results and any relevant actions required shall be recorder and filed. If not defined
by contract or established by a project specific procedures, the formalization system chosen for the verification
activities carried out will be defined and managed by PEM.
As example the formalization of the verification activities can be made through interdisciplinary check forms (ex.
the attached Squad check distribution sheet) check lists, minutes, documentation attesting to comparative
calculations, etc.
Following the finalization of comments PEM provide to approve said report and distribute it to involved discipline
to incorporate the changes into revised documents.
GENERAL PROCEDURE
GENERAL PROCEDURE
The participants to these meetings will be defined, time by time, to discretion of the PEM, in agreement with the
engineering subcontractor responsible/interface.
Minute of meeting summarized the agreements and discussion held during the coordination meeting will be issued
by PEM and eventually distributed (Project Manager and/or internal function involved) as opportune.
13 DESIGN CHANGES
13.1 Generals
The organization shall identify, review and control changes made during or subsequent to, the design and
development of product and service, to the extent necessary to ensure that there is no adverse impact on
conformity to requirements.
The organization shall retain documented information to:
a) Design and development changes
b) The result of reviews
c) The authorization of the changes
d) The actions taken to prevent adverse impacts
The organization ensure that relevant documented information is amended, and that relevant persons are made
aware of the changed requirements, when the requirements for products and services are changed.
Engineering and development changes are identified and the corresponding registrations maintained.
The need for these modifications could arise during either the Review phase or Checking of documents.
The actions taken to prevent adverse impacts are identified through the methods shown in the corporate risk
assessment procedure.
Changes are reviewed, checked and, where applicable, validated and approved before being implemented.
The procedures used for reviewing, checking and validating of the modifications are primarily the same as those
used in the design of works subject to modification or may be different, in the respect of the agreement with the
engineering subcontractor.
Review of engineering and development modifications shall include evaluation of the effect of the changes on
constituent parts and product already delivered.
Registration of the results of the modifications and any actions required shall be maintained as specified in the
project specific engineering management procedures or project design change procedure.
13.2 Engineering changes BEFORE "the issue for construction" stage of the document
The changes of the engineering inputs and the comments on documents done before “issued for construction”
status can be handled and/or originated from PEM/PE following the comments received by the parts involved in
the project (COMPANY, engineering subcontractor, internal functions/departments, external collaborators or
specialist, materials suppliers / manufacturer, authorities, etc.).
The changes and comments are subject to review and verification, as described in the relevant paragraphs of this
procedure.
GENERAL PROCEDURE
13.3 Engineering changes AFTER "issue for construction" stage of the document
13.4 AS-BUILT
GENERAL PROCEDURE
15 CUSTOMER FOCUS
Project Engineer Manager is a direct interface with Company representatives.
He will monitor and safeguard properties belonging to customer or external providers, as reported in the chapter
8.4
Project Engineer Manager and Project Engineers will transfer any significant feedback relevant the engineering
management received from Client, care of property belonging , if any, to Project Manager and EPC Coordination
Manager/Engineering Manager, as a result of complaints management and/or Risk & opportunities management
processes.
Moreover, customer feedback can be kept from:
- Project correspondence system;
- Relevant project Minutes of Meeting.
that will be made available on project server to the Corporate Engineering Manager in case of need of review.
16 ATTACHMENTS
Forms attached to this procedure are provided in the revision in force at the date of the procedure itself.
Users are therefore responsible for periodically checking the correct version of the forms they are interested in
by downloading the updates available on the company network.
Moreover they are generic templates and may be adjusted to comply with project requirements and need
preserving the nature and intention of the form.
GENERAL PROCEDURE
GENERAL PROCEDURE
GENERAL PROCEDURE
Discipline Pla.
Remarks
Act. Pla. Act. Pla. Act.
Prog. Prog Prog. Prog Var. Prog. Prog Var.
% % % % % %
Process
Pressure Eqip.
Mechanical
Pipeline
Piping
Inst & Control
Electrical
Civil
Eng. HSE
ENG. OVERALL
PROJECT MILESTONES
Completion Completion Completion
ID Description of Milestone Date Date Date Type LD
Planned Foreseen Actual
A ENGINEERING
Unit XXX : XXXXXX
1 Contract signature
2 Contract effective date
3 Commencement date
4 Kick off meeting
5 Mobilization
6 Mechanical completion
7 Project completion
8
Milestone Type :
S Contractor to specify
GENERAL PROCEDURE
KPI SUMMARY
KPI a) _________% KPI b) __________% KPI c) OPEN CLOSED
SIGNIFICANT EVENTS
Activities completed during this period
Activities planned for next period
Document with delay
Events, Changes, …
LESSONS LEARNED
-
GENERAL PROCEDURE
GENERAL PROCEDURE
GENERAL PROCEDURE
ACTION
ITEM SUBJECT
by when
Urgent document
Company FEED documents review / endorsement
13 Long Lead Item data sheets
PID, station plan, design basis, specifications, data sheets and material requisitions
for long lead item (main valves, pig traps, insulation joint)
Documents
Document Format
14 Document numbered according to SICIM procedure and COMPANY requirements.
Verify COMPANY numbering philosophy for existing document that are involved /
modified in new installation and as-built. It is required to change the numbering or
the same will be keep unchanged?
Document will be transmitted from EEO DC to CONTRACTOR DC, which will
prepare issue to COMPANY.
15
EEO we will handle and upload directly the documents on CONTRACTOR web
based document control program.
EEO we will handle and upload directly the documents on CONTRACTOR web
16 based document control program.
FTP server with access philosophy and temporary directory for large file exchange
16 Handover of FEED Documents, list of documents
Engineering Check:
• PEM is responsible for planning and organization
• Review is carried out following a check list verifying that input data,
interfaces, output data, comparison with past project, COMPANY
specification changes during engineering proceeding have been PEM -
17
considered, implemented and actual documentation is consistent.
• Base frequency is monthly and minute of meeting will record the check
and result.
• Main planning shall incorporate the date for review.
• Additional meeting can be done on special subject as required by PEM
GENERAL PROCEDURE
ACTION
ITEM SUBJECT
by when
Engineering Verification:
• PEM is responsible for planning and organization
• Engineering check is systematic check of engineering and all the key
personnel involved, PEM, lead engineers, construction manager, surveyor
coordinator, permit coordinator and land acquisition coordinator shall
attend the meeting.
18 • Check are planned at 60% and 100% of overall engineering progress. PEM -
• Main planning shall incorporate the date for check
GENERAL PROCEDURE
GENERAL PROCEDURE
ACTION
ITEM SUBJECT
By when
Progress Monitoring (Para 9.4)
Is measuring procedure issued and followed ?
• Availability of written progress calculation procedure (Internal / Official)
• Weighing system
• Progress calculation method, and schedule performance index (SPI)
08 calculation
PEM -
If required, is in place a procedure to record the man hours to calculate the ACTUAL
costs and cost performance index (CPI) ?
Review of engineering progress report, actual status, concerns.
Is SICIM form used to issue engineering progress report ?
Key Indicator (Para 9.5)
Are key indicator defined or CORPORATE are used:
- Allowed maximum delay of engineering calculated on schedule
09 performance index is 15%. PEM -
- Respect of budget
- Tag Items Hand Over Dossier
If the above limit is exceeded, explanation meeting and recovery plan shall be
organized by PEM in cooperation with PM and planner.
Engineering resources (Para 10)
PM /
10 Engineering is developed using internal resources or subcontracted? -
PEM
Are external experts/specialists required, if yes are CV available ?
External Engineering / Main Subcontractors (Para 11)
Is available list of sub-contractors, service requirements with scope of works,
technical bid evaluation for engineering bid ?
GENERAL PROCEDURE
ACTION
ITEM SUBJECT
By when
Design Verification (Para 12.2)
Is available procedure for design verification available ?
13 PEM -
Is design verification meeting scheduled on project planning ?
Are minute of meeting/report with design verification, available and filed ?
Design Validation (Para 12.3)
14 Is available a schedule and method for design validation available ? PEM -
Are certificate for design verification, available and filed ?
Coordination Meetings (Para 12.6)
15 PEM -
Are coordination minute of meeting available, numbered and filed on server ?
Design change, Technical queries and change orders (Para 13)
Is available procedure for Technical queries and design changes management ?
Is available technical queries register ?
16 Are technical queries, with COMPANY reply filed on server ? PEM -
Is available design change register ?
Are design changes, with changes verification, that will arise during the project keep
in order and filed on server with a proper numbering ?
As-Built (Para 13.4)
17 Organization of As-Built PEM -
Availability of red marked copy
GENERAL PROCEDURE
General data
Material requisition N°: -
Tag Number: -
Item Description: -
Supplier Detail: -
Guarantee Bond Expire Date: -
Hand Over
Certificate Date: -
Certificate Number: (Attach Signed Report)
GENERAL PROCEDURE