Beruflich Dokumente
Kultur Dokumente
Local/Project Variation
Activity Steps
END End
1.0
1.1
1.2
Project Manager
Construction/Fab. Manager
Discipline Lead
X X
Engineer Manager
Decision
Additional Note
Project QA Manager
ST
Involved in Activity
Start
Project IM Manager
Controls Manager
Legend
PURPOSE,
PURPOSE, SCOPE,
SCOPE,
DEFINITIONS,
DEFINITIONS,
REVISION
REVISION HISTORY
HISTORY
ST
1.3
1.4
1.5
Project
Project Mobilization
Mobilization //
Demobilization
Demobilization of
of Personnel
Personnel &
&
Facilities
Facilities
PM-GL-OFF-PM-202
PM-GL-OFF-PM-202
1.6
-
1.7
1.7
1.8
1.8
1.9
2.0
2.0
2.1
2.2
Contract
Contract Administration
Administration
PM-GL-OFF-CN-201
PM-GL-OFF-CN-201
Develop
Develop Engineering
Engineering Reporting
Reporting
&
& Meeting
Meeting Plan
Plan
PM-GL-OFF-EN-201
PM-GL-OFF-EN-201
X
Prepare
Prepare Project
Project Implementation
Implementation
Plan
Plan
PM-GL-OFF-PM-205
PM-GL-OFF-PM-205
Paper copies of this Process Map are UNCONTROLLED. Please refer to the KBR MS website for the current version.
Page 1 of 9
Local/Project Variation
Activity Steps
END End
2.3
2.4
2.5
2.6
2.7
2.8
2.9
PURPOSE,
PURPOSE, SCOPE,
SCOPE,
DEFINITIONS,
DEFINITIONS,
REVISION
REVISION HISTORY
HISTORY
3D
3D CAD
CAD Model
Model Execution
Execution
PM-GL-OFF-EN-217
PM-GL-OFF-EN-217
Project
Project Organization,
Organization,
Responsibilities,
Responsibilities, and
and
Management
Management Matrices
Matrices
PM-GL-OFF-PM-201
PM-GL-OFF-PM-201
Hardware
Hardware &
& Software
Software
Management
Management Plan
Plan
PM-GL-OFF-EN-220
PM-GL-OFF-EN-220
Project Manager
Process Measure
Construction/Fab. Manager
Project QA Manager
Discipline Lead
X X
Additional Note
Engineer Manager
Decision
ST
Involved in Activity
Start
Project IM Manager
Controls Manager
Legend
Engineering
Engineering Document
Document
Control
Control
PM-EA-OFF-DM-201
PM-EA-OFF-DM-201
Supplier
Supplier Document
Document Control
Control
PM-EA-OFF-DM-202
PM-EA-OFF-DM-202
Control
Control // Tracking
Tracking of
of
Engineering
Engineering Documents
Documents
PM-GL-OFF-EN-213
PM-GL-OFF-EN-213
Standard
Standard for
for Production
Production and
and
Format
Format of
of Engineering
Engineering Drawings
Drawings
ATT-GL-OFF-EN-215a
ATT-GL-OFF-EN-215a
Paper copies of this Process Map are UNCONTROLLED. Please refer to the KBR MS website for the current version.
Page 2 of 9
Local/Project Variation
Activity Steps
END End
3.0
3.1
3.2
Project Manager
Process Measure
Construction/Fab. Manager
Project QA Manager
Discipline Lead
X X
Additional Note
Engineer Manager
Decision
ST
Involved in Activity
Start
Project IM Manager
Controls Manager
Legend
PURPOSE,
PURPOSE, SCOPE,
SCOPE,
DEFINITIONS,
DEFINITIONS,
REVISION
REVISION HISTORY
HISTORY
Standard
Standard for
for Production
Production and
and
Format
Format of
of Engineering
Engineering Drawings
Drawings
ATT-GL-OFF-EN-215a
ATT-GL-OFF-EN-215a
Prepare
Prepare Project
Project Execution
Execution
Plan
Plan
PM-GL-OFF-PM-223
PM-GL-OFF-PM-223
Establish
Establish team
team Building
Building
Program
Program
PM-GL-OFF-PM-204
PM-GL-OFF-PM-204
3D
3D Model
Model Progress
Progress
Measurement
Measurement
PM-GL-OFF-EN-218
PM-GL-OFF-EN-218
3.3
3.3 Provide input to project control plan
- Work Breakdown Structure (WBS)
- Schedule Work Packages & Restraints
- Supplier Data Requirements
- Engineering Progress Milestones
- Establish Design Change Notice &
Control
- Deliverable Category List
3.4
3.4 Develop engineering assurance plan
- Provide Schedule Input
- Agree with Home Department Extent of
Audit
3.5
-
Project
Project Change
Change Control
Control
PM-GL-OFF-PM-213
PM-GL-OFF-PM-213
Engineering
Engineering Support
Support for
for
Procurement
Procurement
PM-GL-OFF-EN-205
PM-GL-OFF-EN-205
Engineering
Engineering Assurance
Assurance Reviews
Reviews
PM-GL-OFF-EN-222
PM-GL-OFF-EN-222
Establish
Establish &
& Control
Control Design
Design
Basis
Basis &
& Criteria
Criteria
PM-GL-OFF-EN-225
PM-GL-OFF-EN-225
3.6
Page 3 of 9
Local/Project Variation
Activity Steps
END End
Project Manager
Process Measure
Construction/Fab. Manager
Project QA Manager
Discipline Lead
X X
Additional Note
Engineer Manager
Decision
ST
Involved in Activity
Start
Project IM Manager
Controls Manager
Legend
PURPOSE,
PURPOSE, SCOPE,
SCOPE,
DEFINITIONS,
DEFINITIONS,
REVISION
REVISION HISTORY
HISTORY
- Inquiry Documents
- Technical Reviews
3.7
3.7
-
3.8
-
3.9
-
Develop
Develop External
External Design
Design
Interface
Interface Plan
Plan
PM-GL-OFF-EN-260
PM-GL-OFF-EN-260
Interface
Interface with
with Third
Third Party
Party
PM-GL-OFF-PM-209
PM-GL-OFF-PM-209
Hazardous
Hazardous Area
Area Design
Design
Procedures
Procedures
PM-GL-OFF-EN-236
PM-GL-OFF-EN-236
Process
Process Data
Data for
for Mechanical
Mechanical
Equipment
Equipment and
and Inline
Inline
Instruments
Instruments
PM-GL-OFF-EN-204
PM-GL-OFF-EN-204
Process
Process Data
Data for
for Line
Line List,
List,
Equipment
Equipment List
List and
and Instrument
Instrument
List
List
PM-GL-OFF-EN-229
PM-GL-OFF-EN-229
3.10
3.10 Finalized project specific 3D model
management plan.
Paper copies of this Process Map are UNCONTROLLED. Please refer to the KBR MS website for the current version.
Page 4 of 9
Process Measure
Local/Project Variation
Activity Steps
END End
Project Manager
Construction/Fab. Manager
Discipline Lead
X X
Engineer Manager
Decision
Additional Note
Project QA Manager
ST
Involved in Activity
Start
Project IM Manager
Controls Manager
Legend
4.0
5.0
-
PURPOSE,
PURPOSE, SCOPE,
SCOPE,
DEFINITIONS,
DEFINITIONS,
REVISION
REVISION HISTORY
HISTORY
Control
Control Administration
Administration
PM-GL-OFF-CN-201
PM-GL-OFF-CN-201
FOLLOW-UP ACTIVITIES
Site / Field Assistance
Commissioning Assistance
As-Built
Start-Up Support
END
Author/Revised by:
Date:
Terrance N. Ivers
13-May-03
Printed names here confirm that the document has been signed off approved, the original held by the Quality Management Group
Paper copies of this Process Map are UNCONTROLLED. Please refer to the KBR MS website for the current version.
Page 5 of 9
Purpose
The purpose of this Process Map (PM) is to define the requirements for developing a Project Engineering
Execution Plan. The Project Engineering Execution Plan is part of the complete Project Execution Plan
and provides input that supports both the Project Implementation Plan (PIP) and the Project Execution
Plan (PEP).
Scope
The Engineering Execution Plan is part of the overall Project Execution Plan. The Engineering Execution
Plan will be developed on all projects whose scope includes engineering. The plan addresses
engineering activities that support project initiation, execution and closeout. The plan is dynamic and
must be kept current as the project progresses to reflect all significant changes. This process map is the
standard for the KBR Offshore business unit and applies to regions.
Definitions
The terms as defined below, refer specifically to their use in this procedure.
Project Execution Plan - The PEP defines the project goals, framework and direction and is based on
the Project Execution teams strategies for executing the work. The plan is a further detailed development
of the Execution Plan as presented with the bid documents. The plan is a brief, action-oriented
communication tool used to document a common basis of understanding and commitment by all project
functional groups. A PEP is required for every project. The level of detail in the PEP is dictated by the
scope of work and complexity of the project along with the amount of risk and the requested execution
detail required by the client during the bid stage. The PEP is dynamic and is kept current as the project
progresses from the mobilization phase to project handover.
Revision History
All revisions to Process Maps following first issue (Rev 0) shall be indicated by a vertical blue line to the
left of the affected text.
13-May-03
Rev 1 - Removed EPC limitation and made applicable to all engineering projects. Added attachment to
define drawing standards. Removed connector lines to "Involved in Activity" to conform with new Process
Map standards.
17-Mar-03
25-Feb-03
Dec-03
Additional Notes
Note 1.7
Major re-work, and the associated time lost within the engineering design group can be caused by not
having a sufficiently firm understanding of the KBR bid documents, the contract requirements and the
project profitability plan prior to starting the detailed design activity. It is therefore essential that enough
time be allowed to ensure that the fundamental aspects of the process flow scheme, plant layout, process
control and loss prevention as well as the structural design are well founded prior to proceeding with the
resource intensive detailing phases.
Note 1.8
Business Acquisition (BA) - This Engineering Process Map has a basic assumption that serves as its
beginning point is time. The initiation point is the Business Unit announcement of a successful project
acquisition effort. Therefore, there are certain assumptions about the BA effort necessary to translate the
"As Bid" documents into a financially successful project execution plan. The key areas for understanding
between the Acquisition team and the Project Execution Team include the following:
340976616.xls
Paper copies of this Process Map are UNCONTROLLED. Please refer to the KBR MS website for the current version.
Page 6 of 9
Note 2.0
Project Implementation Plan - The PIP is a concise written plan, inclusive of a logic based schedule that
defines all activities required to transition a project from the authorization to proceed and initial
mobilization phase through to the routine execution of contractual scope. The PIP addresses all activities
for the first 60 to 120 days that must be implemented prior to considering a project as fully operational.
The PIP utilizes information from the BA phase issued in a collection of document that include:
Note 2.3
Model "Engineering Execution Plan" document is maintained and will be provided by the KBR Offshore
Regional Engineering Process Owner. The Engineering Execution Plan model provides the Regional
best practice for overall project execution of the detailed engineering effort. The model will be modified to
fit the Contract requirements and approved by the Process Owner and the Project Manager prior to issue.
An initial release may be made with the Project Managers approval.
Note 3.3
Engineering input to the project control schedule. The information to be provided to the project control
group includes a work package of clearly related items along with an estimate of the deliverables, the
duration, the type of resource needed, the man hours required and any predecessor / successor
description. This aspect of project control starts with an understanding of the deliverable list, the
associated production assumed for these during the bid phase (engineering estimate metrics).
Note 3.4
Engineering Assurance Audits. This aspect of engineering planning does not relieve the project
engineering personnel of their responsibility to produce both contract compliant and technically correct
designs. The scope of an EA audit is an independent, second level review over and above those reviews
and checks performed within a project. Its purpose is to ensure the quality of engineering by verifying
that adequate technical checks and projects design controls are maintained within the project and that
appropriate technical procedures are followed. EA audits are scheduled by the project discipline lead at
preset intervals and conducted by the discipline department. Generally there are a minimum of three
audits, typically 15-25 percent, 40-50 percent and 70-80 percent complete points. Design Reviews or
Technical Audits are considered one off as they pertain to a particular aspect of a design project and are
undertaken at the request of the Project Engineering Manager or Project Manager. The purpose is to
ensure the design meets all technical issues, is safe, workable and well integrated.
340976616.xls
Paper copies of this Process Map are UNCONTROLLED. Please refer to the KBR MS website for the current version.
Page 7 of 9
Clients 3rd Party Interface Requirements. Within the Scope of this process map this issue is the
interfaces with 3rd parties imposed by the contract. It does not include any execution strategy that
involves KBR subcontracting a part of the work nor does it include any purchase activities KBR
undertakes. Examples of a 3rd party would be: 1.) DnV, Lloyds or ABS nominated by the client to act as
a certification agent. 2.) The client purchase of any long lead equipment and it is not assigned to KBR to
administer.
Note 3.10
"3D Model Management" documents are maintained and will be provided by the KBR Offshore Regional
Engineering Process(s) Owner. The 3D Model Management covers the management of the data base
design and progress reporting aspects. The model will be modified to fit the Contract requirements and
approved by the Process Owner and the Project Manager prior to issue. An initial release may be made
with the Project Managers approval.
Note 3.12
PE Seal and Stamp of Engineering Documents. All completed engineering documents that are issued on
KBR Offshore projects in the Americas will be issued with a PE Seal. The only exception to this
requirement is under circumstances that are judged by KBR Offshore Sr. Management, in consultation
with KBR, Inc. to not require a seal. Engineering documents are to be sealed according to KBR Offshore
Standard Work Method EP-01105.00 that is obtained from the KBR Offshore Americas BU Engineering
Process Owner. Preliminary documents issued for review, comments or information are not to be sealed.
These documents shall bear the responsible engineers name (with "PE" attached) and the registration
number. Such documents shall be clearly identified to not be suitable for construction, bidding and/or
permit issue.
340976616.xls
Paper copies of this Process Map are UNCONTROLLED. Please refer to the KBR MS website for the current version.
Page 8 of 9
Attachments Section
Engineering Execution Planning
PM-GL-OFF-EN-215
Paper copies of this Process Map are UNCONTROLLED. Please refer to the KBR MS website for the current version.
Page 9 of 9