Sie sind auf Seite 1von 34

MC and Commissioning Preparation

Typical Commissioning Objectives


Safety
The plant or facility will be commissioned in such a manner that it ensures the safety of all personnel and
avoids damage to any part of the plant or equipment
Design Confirmation
The commissioning of the plant or facility will prove it functions according to the design intent and within
the specific system and equipment design parameters
Documentation
The construction and commissioning groups will ensure they document all phases of the completion process
Auditable Trail
Documentation will be kept in such a way as to provide auditable evidence of the completion process during
construction completion / pre commissioning and through to system completion
Budget and Schedule
The commissioning process will be managed to ensure the project completion is within the defined schedule
and budget
Operational Acceptance
Early operational acceptance criteria will be defined and included in the commissioning process to ensure a
smooth transition at both handover and acceptance between contractor and client.

General Preparation
General Completion Preparation
Develop Commissioning execution plan and
strategy
Define plant start up sequence and set priorities
Define list of systems, sub systems and sub sub
systems
Develop and issue colored P&IDs and SLDs
showing limits of workable sub system
Compile equipment lists by sub system and
discipline
Develop comprehensive detailed commissioning
schedule (believe in the schedule)
Align and import relevant engineering data into
PWCOM tracking system
Review and align discipline check procedures for
both MC and PC

MC and PC Preparation
Finalize and develop MC and PC check
procedures
Develop MC and PC dossiers to be used as a
handover document to hold all the relevant
completion information.
Develop system based commissioning test
procedures
Develop a punch list management system and
utilize PWCOM to track all activities
Develop a handover and acceptance protocol
procedure

Project Breakdown
Systems and Sub systems
A good completion strategy is dependant on early
development of the correct structure and foundation thus
allowing the establishment of system based activities
A system is a major sub-division of an installation that
performs a major operation function of a plant or facility. The
installation and commissioning of this system is multidisciplined
A sub system is a sub-division of the system that performs a
given operational function with no or little interference from the
other parts of the plant. It also contains the equipment and is
usually checked and pre-commissioned as a single discipline

Project

System

Sub-system

Equipment

The Sub-System Approach


Project Duration Without Sub System Approach

Project
Project Duration With Sub System Approach

TIME BENIFIT

System 1

System 2

System 3

MC

PC

Comm

Start Up

Typical Sub-System Limit Definition


Sub-System Limits

Discipline Breakdown Within Sub-System Limits


Discipline Breakdown

Developing Workable Systems and Sub-systems


Typical Project Numbers

Develop Systems

0 Wells/Sub-sea

50 Instrument Air

1 Hull

51 Fresh Potable Water

2 Oil Process

52 Diesel

3 Gas Process

Develop Sub-System Boundaries

4 Process Utilities

5201 Storage

5 Utilities

5202 Purification

6 Fire and safety

5203 Supply

7 Electrical

5204 Transfer

8 Integrated Control
Develop Workable Limits and Create MultiDisciplined Work Packs

5204-001
General
General

5204-002

5204-003

Generator
Generator

FirePump
Pump
Fire

Create Work Pack Status


Assign Discipline Check Procedure
Electrical
Electrical
MCWP
MCWP
PCWP
PCWP

Instrument
Instrument
MCWP
MCWP
PCWP
PCWP

MC
CP-A

Mechanical
Mechanical
MCWP
MCWP
PCWP
PCWP

Piping
Piping
MCWP
MCWP
PCWP
PCWP

PC
CP-B

MC to Commissioning and Acceptance Flow


Mechanical Completion Sub-sub System
CP-A
M & P CP-AE & I
M&P
E&I

5204-001
5204-001

Pre Commissioning Sub-sub System

Pre-Comm Work Pack


Pre-Comm Work Pack

MC Work Pack
MC Work Pack
M
M
DAC
DAC

P
P
DAC
DAC

E
E
DAC
DAC

CP-B
CP-B I
E M
E M I

52-04-001
52-04-001

M
M
CDAC
CDAC

I
I
DAC
DAC

52-04-002
52-04-002

SAC
SAC

CTP
CTP
System 52
System 52
Diesel
Diesel

Commissioning System

I
I
CDAC
CDAC

RFC
RFC
5204-001
5204-001

MCC
MCC
5204-001
5204-001

MC from 5204-002

E
E
CDAC
CDAC

Discipline CP-B
EDiscipline
M CP-B
I
E
M
I
Pre-Comm Work Pack
Pre-Comm Work Pack
M
M
CDAC
CDAC

E
E
CDAC
CDAC

RFC
RFC
5204-002
5204-002

I
I
CDAC
CDAC

PWCOM Total Completions System

PWCOM Flow

Engineering
Engineering

Verification

Work pack

Construction
Construction

Development

Mechanical
Mechanical
Completion
Completion
Check
CheckSheet
Sheet
CP-A
CP-A

Work pack

Development

Pre
Pre
Commissioning
Commissioning

Data

Handover
Handover

Development

Data
Procedure

Operation
Operation
Maintenance
Maintenance

Check
CheckSheet
Sheet
CP-B
CP-B
Verification

Commissioning
Commissioning
Acceptance
Acceptance

Verification

PWCOM Preparation
Develop system and sub system definition

Mark up the relevant P&ID and SLDs to suit the system definition into
workable sub systems
Align system and sub system definition into PWCOM
Review check procedures CP-A and CP-B and adjust to suit project
requirements
Align engineering data externally to suit PWCOM input requirements including
sub system and discipline alignment
Import engineering tags into PWCOM
Assign tags with the required CP-A and CP-B
The MC and PC work packs are automatically developed within PWCOM
Print out all draft MC and PC work packs and carry out first pass verification
review of their content
Ensure all the relevant data is captured and that the relevant checks have been
correctly assigned
Readjust MC and PC work packs to suit verification review and re print
Carry out second pass review and adjust to suit
Issue MC and PC work packs as final
Print out and date MC and PC work packs including all relevant CP-A, CP-Bs

PWCOM Execution

Issue and assign all MC work packs to field including CP-As


On completion of CP-A sign off within PWCOM
When all discipline CP-As are complete and signed off for specific
MC work pack, issue discipline acceptance certificate DAC
When all DACs are issued for that specific sub system, issue
mechanical completion Certificate MCC
Issue and assign all PC work packs to field including CP-Bs
On completion of CP-B sign off within PWCOM
When all discipline CP-Bs are complete and signed off for the
specific PC work pack, issue commissioning discipline acceptance
certificate CDAC
When all CDACs are issued for that specific sub system, issue
ready for commissioning certificate RFC
The system is now ready for multi discipline commissioning via the
commissioning test procedure CTP

PWCOM Main Menu

PWCOM is a Microsoft access 2000 based database with a visual basic


software platform.
The system is designed to be very user friendly and flexible enough to
suit any site condition and project quality requirements without the need
for corporate intervention.

System Development

The project system and sub systems are developed as the foundation of PWCOM
and are further split into workable levels into sub sub systems

Internal MC and PC check procedures

PWCOM has a complete set of both construction and pre commissioning check
procedures across all disciplines and can be easily adjusted and formatted
internally to suit any project requirement

Project Tag Register

The tag register is developed buy importing the relevant project engineering data and
assigning specific sub systems to each tag which then forms the basis of the work pack
development . Engineering data of any format can be utilized and imported

Assigning check procedures to Tagged Items

Each tag will be assigned a specific check procedure to suit the project
requirements and forms the basis of the verification process and auditable trail of
checks carried out during both construction and commissioning

Automatic Development of MC Workpacks

The Mechanical Completion work packs are automatically developed as each tag
is assigned a sub system and specific check procedure CP-A

Automatic Development of PC Workpacks

The PC work packs are automatically developed as each tag is assigned a sub
system and specific check procedure CP-B

Sign Off Completed check procedures

Signing off completed check procedures is an easy task and creates the final
verification platform. It also allows progress reporting to be established at any
level required

Mass Update Ability

By using the mass update function, the assignment of checks procedures and
revised data is by the click of a button

Automatic Development of Certification

The development of the relevant certification requirements is an automatic


function. The certificates can be adjusted to suit the project QA/QC requirements

Discipline Acceptance Certificates

The standard issue of discipline acceptance certificates when the relevant work
packs are complete is recommended but in some instances you may need to use
the added ability of being able issue partial completion which will include all
outstanding activities listed on the certificate

Internal Development of check procedures

The development of the check


procedures is carried out
internally therefore eliminating
the need for external word
documents to be developed
and allowing greater flexibility
should you need it on site

Internal Progress Reports Available

There are many reporting levels within PWCOM with it having the added ability of
changing the reports to suit any project managers requirements. The reports are
generated by either discipline, system, subsystem or tag number. Each check
procedure has an assigned hourly norm allocated therefore allowing the
calculation of man hours to be very accurate

Typical Progress Report

Bar Chart Type Progress Report

This report uses the reference of the total check procedures assigned as 100%
therefore allowing the calculation of completed check procedures as a % to be
very accurate. Progress is achieved when the sheet is returned and signed off in
PWCOM

Automatic Development of S Curve Reports

Internal Punchlist Capability

The punchlist is managed internally within PWCOM and encompasses both


construction and commissioning activities consolidating as one punchlist

Punchlist Development

Each punchlist generic description is given a reference code therefore eliminating


the need to for the site engineers to spend hours typing in the descriptions of the
punch

Typical Punchlist Summary Report

The reports are developed with as much detail as the project requires with each
punchlist referenced back to a system and tag to enable accurate progress
reporting levels to be established

Typical CP-A and CP-B check procedures

MC and PC Workpack Forms

Das könnte Ihnen auch gefallen