CM-PE-002 Preparation of Engineering Flow Diagrams and Related Documents

8/13/2019 CM-PE-002 Preparation of Engineering Flow Diagrams and Related Documents

http://slidepdf.com/reader/full/cm-pe-002-preparation-of-engineering-flow-diagrams-and-related-documents 1/24

Home About News Products Tools Library Forum Contact

search...

16-Mar-2013

Main Menu

Home

About

News

Products

Tools

Library

Forum

Contact

Library Content Menu

QA Standards

General Procedures

Department Procedures

Work Instructions

General Guides

Design Guides

Engineer ing Guides

General Standards

Des ign StandardsEngineer ing Standards

Specifications

Requisitions

Forms

Cost Codes

Papers

PCC Software

Softw are for creation of pipe classes

and mechanical calculation of piping

components. Read more ...

VES Software

Softw are for the design and mechanical

calculation of pressure vessels and heat

exchangers. Read more ...

Home General Standards CM-PE-002

CM-PE-002 Preparation of Engineering Flow Diagrams and Related Documents

Table of Contents

1. Purpose

2. General

3. Responsibilities

4. Procedure

5. Flowcharts

6. References

7. Attachments

1. Purpose

Define the necessary steps to be follow ed in the preparation of engineering flow diagrams (EFD's).

Define the necessary steps to be follow ed in the preparation of documents related to the EFD’s, i.e.: demolition

diagrams, line tables, list of revision sheets, tie-in index, miscellaneous material lists (MM).

2. General

The EFD’s and related documents establish the plant configuration and are the key documents for the development

of piping and instrumentation construction draw ings.

The EFD’s are the most w idely used documents during the engineering, procurement, construct ion, and startup

phases of a project. Timely, complete, and high quality development of these documents enhances execution of the

overall project.

3. Responsibilities

http://www.red-bag.com/jcms/general-standards.html

http://www.red-bag.com/jcms/design-guides.html

http://www.red-bag.com/jcms/general-guides.html

http://www.red-bag.com/jcms/department-procedures.html

http://www.red-bag.com/jcms/general-procedures.html

http://www.red-bag.com/jcms/quality-assurance-system-procedure-standard.html

http://www.red-bag.com/jcms/free-online-engineering-tools.html

http://www.red-bag.com/jcms/about-red-bag.html

http://www.red-bag.com/jcms/

http://www.red-bag.com/



http://www.red-bag.com/jcms/general-standards/595-bn-s-uk001-8-project-function-descriptions.htmlhttp://www.red-bag.com/jcms/general-procedures/422-cm-pe-002-preparation-of-engineering-flow-diagrams-and-related-documents.html#general





http://www.red-bag.com/jcms/news.html

http://www.red-bag.com/jcms/general-standards/595-bn-s-uk001-8-project-function-descriptions.htmlhttp://www.red-bag.com/jcms/general-procedures/422-cm-pe-002-preparation-of-engineering-flow-diagrams-and-related-documents.html#attachments

http://www.red-bag.com/jcms/general-standards/595-bn-s-uk001-8-project-function-descriptions.htmlhttp://www.red-bag.com/jcms/general-procedures/422-cm-pe-002-preparation-of-engineering-flow-diagrams-and-related-documents.html#references

http://www.red-bag.com/jcms/general-standards/595-bn-s-uk001-8-project-function-descriptions.htmlhttp://www.red-bag.com/jcms/general-procedures/422-cm-pe-002-preparation-of-engineering-flow-diagrams-and-related-documents.html#flowcharts

http://www.red-bag.com/jcms/general-standards/595-bn-s-uk001-8-project-function-descriptions.htmlhttp://www.red-bag.com/jcms/general-procedures/422-cm-pe-002-preparation-of-engineering-flow-diagrams-and-related-documents.html#procedure

http://www.red-bag.com/jcms/general-standards/595-bn-s-uk001-8-project-function-descriptions.htmlhttp://www.red-bag.com/jcms/general-procedures/422-cm-pe-002-preparation-of-engineering-flow-diagrams-and-related-documents.html#reponsibilities

http://www.red-bag.com/jcms/general-standards/595-bn-s-uk001-8-project-function-descriptions.htmlhttp://www.red-bag.com/jcms/general-procedures/422-cm-pe-002-preparation-of-engineering-flow-diagrams-and-related-documents.html#general

http://www.red-bag.com/jcms/general-standards/595-bn-s-uk001-8-project-function-descriptions.htmlhttp://www.red-bag.com/jcms/general-procedures/422-cm-pe-002-preparation-of-engineering-flow-diagrams-and-related-documents.html#purpose

http://www.red-bag.com/jcms/component/mailto/?tmpl=component&link=4469d6b25b3aca1c86ad8667c8bc1f0372d7a8c3

http://www.red-bag.com/jcms/general-standards/422-cm-pe-002-preparation-of-engineering-flow-diagrams-and-related-documents.html?tmpl=component&print=1&page=



http://www.red-bag.com/jcms/index.php/software-products/pressure-vessel-exchanger-software

http://www.red-bag.com/jcms/index.php/software-products/pipe-class-component-software

http://www.red-bag.com/jcms/papers.html

http://www.red-bag.com/jcms/cost-codes.html

http://www.red-bag.com/jcms/forms.html

http://www.red-bag.com/jcms/requisitions.html

http://www.red-bag.com/jcms/specifications.html

http://www.red-bag.com/jcms/engineering-standards.html

http://www.red-bag.com/jcms/design-standards.html


http://www.red-bag.com/jcms/engineering-guides.html

http://www.red-bag.com/jcms/design-guides.html

http://www.red-bag.com/jcms/general-guides.html

http://www.red-bag.com/jcms/work-instructions.html

http://www.red-bag.com/jcms/department-procedures.html

http://www.red-bag.com/jcms/general-procedures.html

http://www.red-bag.com/jcms/quality-assurance-system-procedure-standard.html

http://www.red-bag.com/jcms/contact.html

http://www.red-bag.com/jcms/red-bag-forum.html

http://www.red-bag.com/jcms/red-bag-engineering-library.html


http://www.red-bag.com/jcms/software-products.html





http://www.red-bag.com/jcms/index.php/contact

http://www.red-bag.com/jcms/red-bag-forum.html

http://www.red-bag.com/jcms/red-bag-engineering-library.html


http://www.red-bag.com/jcms/software-products.html






Depending on project scope and size certain positions described in the following sections may be combined or

eliminated. The functions, how ever, remain as valid execution requirements w hich must be ass igned w ithin the

established project organization. The independence of QC and QA activ ities must be maintained when making such

reassignments.

3.1 Process Engineering Responsibilities

3.1.1 Process Supervisor

a. The Process Supervisor has the overall responsibility for the Systems Engineering scope of w ork.

b. The Process Supervisor has the responsibility for all process engineering inputs to the EFD’s and related

documents.

c. The Process Supervisor is responsible for Process Engineering's quality control of the EFD’s and related

documents and assures the documents are technically correct, meet the intent of the process design, and reflect

all facilities f or startup, shutdow n, and performance verification. The Process Supervisor shall approve all the

issues of the EFD’s, Demolition Diagrams and Line Tables (see ref. 6.4).

d. The Process Superv isor, in conjunction w ith the Plant Commissioning Engineer, ensures the EFD’s contain

adequate provisions for startup and decommissioning. He review s all EFD’s and adds/rev ises piping, as required,

to allow safe operation, safe and eff icient startup, shutdown, and decommissioning. Additional or revised

instrumentation, w here deemed required, shall be discussed w ith the Control Systems Engineer prior to

incorporation into the EFD’s. This review w ill be completed on the "For Client Comments" or "For Approval" issue of

the EFD’s.

3.1.2 Unit Process Engineer

The Unit Process Engineers on a project are assigned sections (units) of a plant for w hich there is an associated

block of EFD’s. The Unit Process Engineer’s EFD and related document responsibilities are as f ollow s:

a. Defines process details, such as required elevations, two-phase flow definition, gravity flow , startup and

shutdow n requirements, performance verif ication requirements, tracing, location of control valves (grade or at

equipment nozzles), sample connections, etc.

b. Defines the sys tem control philosophy. Part of this activity is the basic definition of r equired process

instrumentation to monitor/verify that the sy stem is operating correctly and the verif ication of the detailed definition

by the Control Systems Engineer on the EFD’s.

c. Defines the required safety devices (relief valves and rupture discs). Defines how emergency shutdow n (ESD)

sys tems function, i.e., preparation of ESD matrices , in close cooperation w ith the Control Systems Engineer and the

Process Control Engineer.

d. In conjunction w ith the preparation of the line table, establishes line sizes, operating pressures and

temperatures, design pressures and temperatures, maximum temperature for thermal stress, and process

insulation and trac ing requirements. Gives input f or class selection such as toxicity, corros ion and material.

e. Defines decommissioning/pumpout requirements.

f. Defines the number, type, and location of sample points.

g. Defines the process specifications (as required) for MM items.

h. Establishes pickling/chemical cleaning details for the plant.

3.2 System s Engineering Responsibilities



Translate

Select Language

Gadgets powered byGoogle

http://www.google.com/webmasters/gadgets.html

http://fusion.google.com/ig/add?synd=open&source=ggyp&moduleurl=http://www.google.com/ig/modules/translatemypage.xml

http://translate.google.com/translate_t



e. In conjunction w ith the preparation of the line table, numbers lines, completes f luid from/to, selects line classes,

and specifies test pressures and mediums.

f. In conjunction w ith the preparation of the line table, specifies insulation and tracing requirements f or mechanical

reasons i.e. w interizing and personnel protection and specifies insulation thickness for heat conservation.

g. Selects valve types, using the Specification for Piping Material as the basis.

h. Selects block valve sizes f or pump and control valve manifolds.

i. Works w ith Control Systems Engineering to ensure that the EFD’s are cons istent w ith the Control Systems design

documents.

j. Prepares and issues flow sheet revision sheets or prepares list of rev isions sheets.

k. Prepares list of MM- items.

l. Prepares the tie-in index.

3.3 Control Systems Responsibilities

3.3.1 Control Systems Engineer

The Control System Engineer def ines the instrumentation, based on basic requirements as show n on the Process

Flow Diagram (PFD) and assures that all required instrumentation is included and correctly indicated on the EFD’s,

and uses the process instrument data, to size the control valves, relief valves, and other in-line instruments.

3.4 Mechanical Engineer ing Responsibilities

3.4.1 Equipment Spec ialist Engineers

The Systems Engineer consults the Equipment Engineers for P, G, and H account equipment to ensure the

equipment details show n on the EFD’s are correct and agree w ith equipment specifications and vendor draw ings.

3.4.2Insulation/Painting Engineer

The Insulation/Painting Engineer specifies insulation and paint requirements in specifications for insulation and

painting. The Systems Engineer is to apply these requirements w hen completing the relevant columns in the line

table.

3.4.3 Acoustical Engineer

The Acoustical Engineer consults w ith Process Engineering and Specialist Engineers concerning items generating

excessive noise. Having determined the appropriate course of action, the Ac oustical Engineer advises the Systems

Engineer of any required revisions to the EFD’s.

3.5 Piping Design Responsibilities

3.5.1 Design Squad Leader

The Piping Design Squad Leader oversees and supervises all piping design generated EFD’s comments and inputs.

The Piping Designer is responsible for notifying the s quad leader w hen EFD revisions are required as a result of

detailed piping layout or revised routing. The Squad Leader advises the Systems Engineer of changes.

3.6 Project Engineering Department Responsibilities

3.6.1 Project Engineering Manager



The task force Project Engineering Manager's function in this area is primarily administrative. The Project

Engineering Manager coordinates the preparation, development, and issuance of EFD’s and related documents w ith

all involved engineering departments and the client. He also is responsible for implementation of the quality

assurance program for the diagrams and related documents.

3.7 Departmental Split of Work

A typical matrix is listed in Attachment 1. This matrix show s the major tasks associated w ith the preparation of

EFD’s and related documents, w ith a listing of the f unctional disciplines having the prime responsibility f or each

task.

4 Procedure

4.1 Presentation

4.1.1 Format

For forms, index sheet and page numbering requirements refer to procedures (ref . 6.4). For the formats to be used

refer to procedures (ref. 6.7).

4.1.2 Numbering

Document numbering for the project shall be defined in the project procedure and execution manual.

Refer to procedures (ref 6.2, 6.4 and 6.5).

4.2 Production

4.2.1 Procedure f or Engineering Flow Diagrams (EFD's)

4.2.1.1 Introductiona.The EFD’s are most w idely used of all engineering documents during the engineering, design,

and construction phases of a project, w ith heavy use continuing during the field checkout and startup phases. The

EFD’s display the inter-relationship of the equipment, piping, and controls to provide eff icient and safe operation.

They are the prime documents used for development of the piping and instrumentation construction draw ings. They

serve also as valuable reference documents and operator training tools f or the client. The EFD’s are given by :

Client

Process Engineers and Plant Commissioning Engineers

Mechanical Engineers (rotating equipment, general equipment, fired heaters)

Electrical, Control Systems, Piping, Insulation, and Acoustical Engineers

Piping Design Group

Given the many sources of input during an extended period, it is apparent the EFD’s are documents w hich develop

continually during the entire engineering and design effort. The EFD’s are not final until the plant is constructed, and

"as-built" modifications (if required) are incorporated. It is imperative that the EFD issues ref lect the best current

information available.

b. Some clients w ish to refer to the EFD’s depicting fac ilities and equipment used to provide utility serv ices, i.e.,

cooling water, steam, boiler feed w ater, demineralized w ater, air, etc., as Utility Flow Diagrams. For the purpose of

this procedure, they are to be considered as EFD’s.

c. Utility distribution diagrams (UDD's) are the engineering f low diagrams that show the layout of the utility services

headers and subheaders and the branches to consumers. They are arranged in a geographic format. Utility

services for w hich UDD’s normally are prepared include steam and condensate (all pressure levels), hot oil, plant

and instrument air, nitrogen, w ater (supply and return cooling w ater, potable, raw , plant, demineralized, etc.), brine,



fuel gas and oil, flare sy stems, and various flush mediums f or pump seals and instruments.

4.2.1.2 Titles and Criteria for Engineering Flow Diagram Major Issues

a. For Internal Comments

For this issue the Systems Engineer has pieced together as much process f low diagram, equipment and EFD

format information as is available at the time, in order to issue a diagram for various groups to mark-up and review .

b. For (Client) Comments/Approval

By this issue, the envisioned plant has been def ined by various input groups. The client (if required) and the input

groups are requested to comment on a fairly complete set of EFD’s prior to commencement of final detailed

engineering and design. At this point, many details such as sizes of in-line instruments, relief valves and pumps arenot know n and subjects such as miscellaneous pump piping and piping MM items are not yet defined. This issue,

how ever, contains the basic plant configuration and line sizes, pipe classes, instrument numbers, insulation and

tracing requirements, valve tag numbers, and startup and decommissioning provisions.

This issue authorizes piping design to begin piping studies.

c. Approved/Certified for Detailed Design

This issue resolves and incorporates the client (if required) and the input group's comments. It contains the control

valve sizes, relief valve s izes, other in-line instrument sizes, pump nozzle sizes, pump valve sizes, control valve

manifold valve sizes, and sample and chemical cleaning connections.

For in-house designed equipment (A, M, TT, etc.), the latest available revision of draw ings and specifications isincorporated.

For vendor designed equipment, the information f rom the latest rev ision of specification and vendor draw ings is

incorporated.

For vendor designed equipment, where the major equipment documents aff ecting the piping design are available

but complete auxiliary system documents are not available, the information from the "Certified" specification on the

major equipment details is incorporated. EFD’s f or the auxiliary systems w ould be certif ied after incorporation of

information f rom the vendor prints.

The "Certified for Detailed Design" issue authorizes the design groups to begin f inal design drawings.

Any details that cannot be finalized at this stage due to a lack of information from vendors, other disciplines, etc,should be clearly marked as "HOLD". Holds shall be restricted to the absolute minimum for this issue.

d. As Designed (Optional)

For this issue, the EFD is updated to ref lect the plant as it was f inally designed and engineered in the home off ice.

e. As-Built (Optional)

For this issue, any f ield changes are incorporated on the EFD for record purposes. This issue w ould be made only

if it is a job requirement.

f. A typical matrix is listed in Attachment 2. This matrix f orm show s the EFD technical content for major issues

reflecting the information that should be incorporated onto the major f low diagram issues.

Note that there will be additional issues of the engineering flow diagrams to keep functional groups up-to-date

with the latest information. These issues shall be titled "Updated/Revised as Marked".

All issues should be identified, this includes internal issues to a limited group of people for a particular purpose.

Thi h ll b t d i th i t l i ( f 6 3)



This purpose shall be noted in the internal issue (ref . 6.3).

4.2.1.3 Procedure

The procedure for preparation of EFD’s is detailed below. A flow chart f or EFD preparation is attached in 5.1. This

depicts the procedure f or a Company standard project.

Signing and approval

Signing and approval of EFD’s w ill be in accordance w ith ref. 6.4.

EFD kick-off

Engineering Manager calls an EFD kick-off meeting to be attended by the Process Supervisor, the Lead SystemsEngineer (LSE), the Systems Engineers (SE), the Unit Process Engineers (UPE), the Control Systems Engineer

(CSE), the Project Control Manager, and the Engineering/Design Coordinator. The purpose of this meeting is to

discuss specific client and job EFD requirements, standard details and instrumentation requirements/formats,

schedules, required level of detail on the EFD's (consistent w ith contractual requirements), requirement f or

equipment EFD’s (e.g., for compressors, etc.), requirements and extent of UDD's. If the job-specific EFD guide (ref

6.7) has yet to be issued at this time, it should be issued as soon as possible and the same applies to the project

EFD legend and symbols sheet.

Issue for internal comments

Using the PFD's, the job specific EFD guide (ref 6.7) and any appropriate EFD's from past jobs (taking due note of

different process conditions, Client requirements, instrumentation systems and format diff erences) the Systems

Engineer (SE) hand draw s the outline of the EFD's show ing equipment outlines and major lines and valves only andtransmits them to the CAD.

The SE continues to develop the EFD's including completion of all lines, incorporating equipment details (from the

equipment data sheets), completion of the instrumentation, incorporation of all secondary lines, and relief valve

requirements.

The SE consults w ith the UPE and the CSE on a case-by-case basis to ensure that all technical job requirements

are properly represented on the EFD's. He also consults all pertinent job specifications including basic design data ,

C-1, C-2, K-1 pertinent equipment general specifications, ISA-S5.3 (f or jobs w ith distributed control sys tems), and

client specification and design requirements, process data sheets, available equipment data sheets, project

bulletins, and the project legend and symbols sheet.

The SE develops the line table (w ith line number, f luid descr iption, and to and from columns completed), requestingincorporation of the line sizes, operating and design conditions, and the (generic) piping materials by the UPE.

Af ter receiving the line sizes and materials from the UPE, the SE incorporates the line sizes on the EFD's and line

tables and completes the line classes . The job-specific C-1 specification (or client imposed equivalent) should have

been issued at this time. The SE transmits the EFD's and corresponding line table to the LSE for rev iew and issue.

The LSE review s the diagrams and line table (QC), signs them and transmits them to the Project Engineering Aide

for Issue "For Internal Comments." The corresponding line table is also issued at this time.

In conjunction w ith this issue, the LSE wr ites a memo to the Proces s Supervisor, the UPE, the Start-up Engineer (if

required), the CSE, the appropriate Equipment Engineers as required, the Engineering/Design Coordinator, and the

Engineering Manager requesting comments on this issue of the EFD's and setting a date for an internal review

meeting. A copy of the memo is sent to the SEC.

Internal review meeting

An internal EFD review meeting is held, attended by the LSE, the SE, CSE, the Start-up Engineer (if required), the

appropriate Equipment Engineers, and the UPE (mandatory), the Engineering/Design Coordinator (optional, but

t l d d) d th P S i d E i i M ( ti l) Th f thi



strongly recommended), and the Process Supervisor and Engineering Manager (optional). The purpose of this

meeting is to collect all input into the EFD's, comments and new information, and to discuss the EFD's in detail.

Comments are agreed upon and marked on a copy of the EFD's. Prints of these copies are transmitted as

attachment to the MOM to all attendees immediately after the meeting.

Issue for Client comments

The SE prepares a composite EFD master, incorporating all decisions and comments of the rev iew meeting. The

EFD masters are transmitted to control systems for instruments numbering (if not already included) and returned to

the SE, who transmits this master to the LSE. The LSE review s the EFD masters (QC) and tr ansmits them to CAD to

be drafted.

CAD updates and back-checks the EFD's and transmits them to the appropriate SE. The SE back-checks the EFD's,

recycles them to the CAD for corrections and af ter they are acceptable, he signs them and transmits them to the

LSE.

A copy is sent to the SEC for review (QA). Comments are discussed w ith the SE, LSE, SEC, reported to the Project

Manager and incorporated by the CAD. (Note: The review by the SEC may be done in parallel w ith obtaining client

comments).

The LSE review s the EFD's, s igns them (QC) and transmits them to the Engineering Manager f or s ignature. The EM

signs them (QA) and transmits them to the Project Engineering Aide for issue, "For Clients Comments." The

corresponding line table should also be issued at this time, complete w ith line sizes and line classes.

In conjunction w ith this issue of the EFD's, the Engineering Manager establishes the time and place for a review

meeting. Requested to attend this meeting are the Process Supervisor, Unit Process Engineer, Control Systems

Engineer, LSE, individual Systems Engineer, and the client (if required).

EFD Clients review meeting

An EFD client review meeting is held. Client comments are discussed and then marked on copies of the current

EFD's. In addition, Company highlights and discusses any revisions that have developed since the last issue of the

EFD's. Prints of all comments are transmitted to the client and all meeting attendees immediately after the meeting.

Minutes of meeting are prepared by the SE and signed by the PS, EM, and the client. It is recommended to w rite the

MOM during the meeting.

The SE incorporates the c lient comments in close cooperation w ith all input groups onto the EFD master (utilizing the

CAD if required) and transmits them to the LSE for his rev iew . The SE also updates the line table and transmits to

the LSE as w ell. The LSE conf irms that all comments are correctly added to the EFD's and transmits them to the

Engineering Manager. As part of the preparation of "Certified" issue, the Engineering Manager may need to call a

review meeting to resolve any outstanding questions.

The certified issue of the EFD's is signed by all personnel, of w hom a signature is required as established in ref.

6.4. The signatures denote that signees are in agreement w ith and approve their areas of responsibility as defined

in section 3.0. The certifying authority is the Project Manager, w ho signs the "Certified" line on the title block (QA).

The client's signature may or may not be required for this issue.

Finally, the Engineering Manager transmits the signed EFD's originals to the Project Engineering Aide for issue as

"Certified."

Post-cert ification EFD issues w ill be made as needed, and w ill be based on comments generated by the UPE, Piping

Design Coordinator, CSE, Start-up, Equipment Engineers, LSE, Electrical Engineer, and the SE. It is the responsibility

of the SE to ensure that their comments are correctly interpreted and show n on EFD's. A ll of these subsequent EFDissues must be signed by the individual Systems Engineer, LSE (QC) and may require the signature of the

Engineering Manager ( ref. 6.4). Corresponding EFD revision sheets and line table revisions must accompany each

issue.

Notes:



Notes:

(1) A fter each EFD issue, the ‘void’ project master mark-ups are f iled, and a new master is s tarted using the new

issue.

All CAD check prints containing additional EFD input shall be filed together w ith the void masters.

(2) A ll issues should be identified, this includes internal issues to limited group of people for a particular purpose.

The purpose of this issue shall be noted on the internal issue. See ref. 6.3.

4.2.2 Preparation of Demolition Diagrams

4.2.2.1 Introduction

Demolition diagrams highlight all equipment, piping and instruments that have to be demolished.

They form part of the construction package and are used for the mechanical subcontract to determine the exact

scope of demolition w ork as the basis f or the bid package. The draw ings are also used fore the same purpose by

the Company disciplines throughout the design phase.

4.2.2.2 Procedure

The Systems Engineer is responsible for identif ying on the draw ings the equipment, lines and instrumentation

w hich are no longer required and coordinates the input from other disciplines. The various engineering departments

are responsible for def ining the most practical extent of the demolition scope. A close liaison between the Systems

Engineer and the Piping Engineer is required at the start of the project to interpret the basic data to the correct

extent of demolition.

Demolition diagrams shall always be issued together w ith the project EFD's.

In the title block the flow sheet desc ription e.g. "Engineering Flow Diagram" shall be replaced by "Demolition

Diagram".

The draw ing lead number to be used is 138. The subletter to be added shall be the same as for the project EFD.

E.g. draw ing XXXX-138A is the demolition diagram, corresponding to the project EFD draw ing XXXX-107A.

Existing revision descriptions shall be deleted.

In the notes column a hatched cloud shall be added w ith the note "Denotes Equipment to be Modified/Removed for

Project XXXX.XX.XX".

Equipment, Piping, Instruments to be demolished shall be clouded and hatched, inclusive the equipment tabulation.

For systems to be relocated/reused an information note shall be added next to the cloud.

Tie-outs shall be numbered and listed

4.2.3 Preparation of the Line Table


The line table is a listing of pipelines appearing on the EFD's. It contains information of the fluid, operating pressure

and temperature, design pressure and temperature, insulation code and thickness, paint code, and type of heat

trac ing. Additionally, information on test pressure and test medium may be required, as w ell as other information

related to authority requirements, such as boiling point, hazard category, etc. The line table is an important adjunct

to the EFD's and also is the basis for piping stress analysis, piping system testing, and the piping portion of the

painting and insulation subcontract.

4.2.3.2 Procedure

The procedure for the preparation of the line table is detailed below A flow chart f or line table preparation is



The procedure for the preparation of the line table is detailed below . A flow chart f or line table preparation is

attached in 5.2. This depicts the procedure f or a Company standard project.

A job specific guide (ref. 6.9) defining format and w ork systems w ill be prepared by the SE Coordinator.

A Systems Engineer fills out the overall line table cover sheet including definition of line number blocks, process

fluid abbreviations, and standard notes.

The Systems Engineer numbers lines and f ills out all line table columns using the PFD's as a bas is, marked-up w ith

Material/Pipe classes, Design Pressures and Temperatures by the UPE (the P-T diagram), and insulation/tracing

information.

The Process Supervisor review s the process line table mark-up and indicates the critical lines to be checked

before the final piping design is completed. The marked-up line table is transmitted to the LSE for incorporation intothe line table original by the SE. The LSE checks and issues the line table "For Internal Comments" w ith the

corresponding issue of the EFD's.

The list of critical lines is issued to the Engineering Manager. The Engineering Manager ensures that the piping

design is checked before being finalized by the Unit Process Engineer. The Process Supervisor signs of f on the list

of critical lines for those lines checked and approved by the Unit Process Engineer. The Engineering Manager,

notified by the Process Supervisor, arranges for the f inal piping design of the approved critical lines.

The LSE requests comments f rom the UPE, the Engineering Design Coordinator, and the Piping Design Engineer.

The Systems Engineer incorporates inputs from the process and piping design line table masters onto the line table

originals. He also fills out the balance of the insulation codes (PP, AS, etc.), and the maximum temperature for

thermal stress . This last column is done in consultat ion w ith the UPE and Pipe Stress Engineer.

The Systems Engineer consults the Painting/ Insulation/Acoustical Engineer and applies their requirements w hen

completing the relevant columns. He also consults w ith the CSE to determine if any control valves require insulation

for noise.

The Systems Engineer transfers comments from the project master and incorporate into the line table originals. The

SE assembles the line table sheets w ith its cover sheet. The LSE review s the line table originals, signs it (QC), and

transmits it to the Engineering Manager. The Engineering Manager signs it (QA) and has it issued w ith the

corresponding EFD issue as "For Clients Comments" or "For Approval" as applicable.

a. The Engineering Manager interfaces w ith the client to obtain line table comments. These are transmitted to the

LSE w ho in turn has them noted on a master copy by the SE, who checks and incorporates c lient's comments

consulting w ith any specialists involved, if required.

b. Company comments are again requested. These are transmitted to the LSE by means of the master mark-ups

from process and piping design.

The Systems Engineer incorporates both internal and client comments into the line table original.

The Systems Engineer also fills out columns: Testing Medium and Testing Pressure (using XXXX-SP-C-10 as basis),

and Service Classification using (XXXX-SP-C-1 and C-2 and ANSI B31.3). He consults the Piping Engineer and the

UPE as required.

The SE assembles the line table sheets w ith its cover sheet. The LSE review s the line table originals, signs it (QC),

and transmits it to the Engineering Manager. The Engineering Manager signs it (QA). The certified issue of the line

table is signed by all personnel of w hom a signature is required as established in ref. 6.4. The line table is issued,w ith the corresponding EFD issue as "Certified".

The line table or the cover sheet and the revised parts of the line table w ill be reissued every time their

corresponding EFD's are reissued, using accumulated comments as the basis. Subsequent issues must as a

minimum be signed by the LSE and Engineering Manager



minimum be signed by the LSE and Engineering Manager.

Notes:

(1) After each line table issue, the project master line table is filed and a new master is started us ing the new

issue.

(2) Lines w hich are deleted should have that notation w ritten in the appropriate space of the line table. Line

numbers should never be reused.

4.2.4 Preparation of Lists of Revisions Sheets for Engineering Flow Diagrams


The use of f low sheet revision sheets is recommended to be used for approving changes to EFD's and to serve as

a back-up for change orders, cost control and material control (ref. 6.8). The PM decides on the applicability of the

referenced w ork instruction. In case the flow sheet revisions sheets are not used then the preparation of a rev ision

list is mandatory for record purposes

The EFD list of revisions is a w ritten detailed record of EFD revisions f rom issue-to-issue. These sheets should be

issued coincident w ith the EFD issues. List of revisions sheets are associated w ith particular EFD's and carry a

related number: i.e., EFD XXXX-107-A has a list of revision sheet XXXX-107-AS. List of revisions sheets describe

the EFD revis ions and also indicate w hether the origin of the revis ion is the client or Company. This document then

can be used as back up for change orders, cost control, and material control. Each revision to an EFD utilizes a

new revisions sheet and records only revisions since the last issue of the EFD. Old revision sheets are retained in

the project files.

List of revisions sheets normally are not issued until the EFD's have progressed to the "Certified" stage. The timing

for starting list of revisions sheets s hould be established for each project to meet project objectives. For example, if

a detailed estimate precedes the "Certified" f low diagrams issue, then revisions sheets should be issued w ith all

subsequent EFD issues.

4.2.4.2. Procedure

The Systems Engineer prepares the list of revisions sheet using the EFD master markup as the basis.

4.2.5 Preparation of Tie-in Index


The purpose of the tie-in index is to locate all tie-in information on a central document and to facilitate information

transfer betw een Company and the client. The tie-in index presents process and mechanical data on the tie-ins,

and is used to establish agreement betw een Company and the client on each party's scope and requirements. The

tie-in index should be "Certified" prior to the EFD’s, so that the tie-in information can be added to the "Certified"

EFD’s. When a large number of tie-ins exist throughout the plant, a site plan to locate the tie-ins is prepared and this

becomes an attachment to the tie-in index. The LSE shall be responsible for assigning tie-in numbers, completing

the information on the tie-in index f rom various sources of input, and having the tie-ins site plan prepared. Contact

w ith the client on this subject w ill be made by the Engineering Manager.

4.2.5.2 Procedure

The procedure for preparation of the tie-in index is detailed below. A f lowchart for tie-in index preparation is

attached in 5.3. This depicts the procedure f or a Company standard project.

Using data f rom new/ex isting PFD’s, new /existing line table, and/or new /existing client information, the LSE

prepares the preliminary index filling in: Tie-in Number, Service, To/From, Line Number and Size, Operating and

Design Pressure Temperature.

a Index is transmitted to Process Supervisor w ho adds the peak and normal flow rates and performs general



a. Index is transmitted to Process Supervisor w ho adds the peak and normal flow rates, and performs general

review .

b. Engineering/Design Coordinator uses preliminary index information and client information to locate the layout lines

entering/leaving the boundary lines.

Index is transmitted to Engineering Manager w ho signs it (QA) and has it issued "For Clients Comments" of "For

Approval." Letter is written asking for client review and also that actual minimum and maximum pressure and

temperature at battery limit, type of connection, and other client originated information to be added.

Client comments are review ed and incorporated by the LSE. LSE signs the doc ument (QC) and transmits it to the

Engineering Manager for issue. Engineering Manager review s index, signs it (QA), and has it issued "Certif ied".

Information from the index is added to the EFD’s by the Systems Engineers. The LSE adds the EFD and plot plan

draw ings numbers to the index.

The LSE signs the document (QC), and transmits it to the Engineering Manager for issue. Engineering Manager

review s the index, signs it (QA), and has it issued "Updated."

4.2.6 Preparation of Miscellaneous Materials (MM) List


The miscellaneous material list, documents materials that are not covered in other standard specifications and lists

(such as the C-1 specification for piping items). The Engineering Manager has the overall responsibility for the

development and maintenance of the miscellaneous materials list and for the specification. The responsibilities of the Systems Engineers and the Piping Engineer are limited to identification and technical specification of

miscellaneous materials. Process Engineers assist, as required, in this task.

4.2.6.2 Procedure

Parallel w ith the development of the EFD’s, each Systems Engineer identif ies the miscellaneous items requiring MM

numbers and specif ication by adding the notation "MM" to the flow diagrams, and giving it a unique sequence

number.

The LSE is responsible for maintaining an MM-item list, ensuring uniqueness of each number.

The Systems Engineer adds the MM item number to the EFD.

Af ter the "For Client Comments" or "For Approval" issue of EFD’s, it may be assumed that a large percentage of MMitems have been identified and numbered. The MM list is issued "Preliminary” to the Engineering Manager.

The MM list is revised by the LSE after the "Certif ied" issue of the EFD's to ref lect rev ised and new or deleted items.

The MM list is issued "Certified".

The MM item list is revised and reissued during detailed design as required. The LSE maintains a master MM list

markup between issues.

5. Flowcharts

5.1 Flowchart for EFD Preparation





5.2 Flowc hart for Line Table Preparation



p







5.3 Flow chart f or Tie-in Index





6. References

Document Number Title Level

6.1 BN-DG-UD01Guide for Checking of Flow Diagrams and Line Designation Tables 5

6.2 BN-W-UE301Work Instruction for the Numbering of Project Documents 4

6.3 BN-W-U012Work Instruction for Document Issue Code and Change

Identification

4

6.4 CM-PE-504Procedure for the Product ion of Engineering Documents 2

6.5 BN-W-UD301Work Instruction for Preparing Manual Technical Drawings 4

6.6 -- -

6.7 BN-DG-UD008Design Guide f or the Preparation of Flow Diagrams 5

6.8 BN-W-UE307Work Instruction for Change Control of Engineering Flow Diagrams 4

6.9 BN-EG-UE208Engineering Guide for the Preparation of Flow Diagrams (in

preparation)

5

7. Attachme nts

1. Departmental Split of Work

2. EFD Technical Content for Major Issues

3. Line Table Technical Content for Major Issues

1. Departm ental Split of Work

Process/Systems

Engineering

Other

a. Engineer ing Flow Diagram (EFD) Task s

Overall responsibility (see Paragraph 3) X

Layout and Format X

Piping Class Selection X Piping Engineering,

Mechanical (Assist)



Mechanical Details (P, vendor designed T, G & H

equipment)

X Mechanical Engineering

(Assist)

Valve Tagging X

Pickling/Chemical Cleaning Philosophy X Mechanical Engineering

and Piping Engineering

(Assist)

Pickling/Chemical Cleaning Details X

Maintenance Requirements X

Flow sheet Revisions Sheets X

Startup/Test Run Requirements X

Decommissioning (Pumpout) Details X

Sample Points X

Control Philosophy X

Application of Control Philosophy X Control Systems (shared)

Process Details (minimum elevations, tracing, etc.) X

Line Sizing X

Safety Systems X Control Systems (shared)

Tracing Requirements for Process Reasons X

Tracing Requirements for Mechanical Reasons

(w interization, etc.)

X

Instrumentation Number and Details Control Systems

b.Dem olition Diagram Task s

Overall responsibility X

Identification of equipment piping and instrumentation to be

demolished

X assistance from piping and

control systems

c. Line Table Tasks

Overall responsibility X

Assigning line Number, fluid from/to, material class,

Testing pressure and medium, tracing type, EFD draw ing

number

X

Establishing line size, operating pressure and temperature,

design pressure and temperature, maximum temperature

for thermal stress, process tracing needs

X

Insulation requirements for mechanical reasons

(personnel protection, etc.)

X assistance from insulation

engineering

Assigning insulation thickness and paint code X assistance from

insulation/painting/

acoustical engineering

d.Tie-in Index Tasks

Complete responsibilityX

e. Miscellaneous Material (MM) List Tasks

Overall responsibility X project engineering

Assigning MM numbers X project engineering

Preparing requests for purchase

Process specification requirements X

Mechanical specification requirements X project engineering

assistance other di i li i d



disciplines as required

2. Engineer ing Flow Diagram Technical Content for Major Issues

Engineering Flow Diagram Tasks For Int.

Comments

For Client

Comments/

Approval

Approved/

Certified

for Design

As

Designed

As

Built

1. Layout equipment; establish quantity of equipment in

each diagram, relative equipment size and relative

equipment elevations . Show the number and name of all equipment. Show package equipment as an

enclosed box w ith no details.

X

2. Establish the layout of each diagram X

3. Show valving, including location, as show n as much

as possible. Location is show n in tw o ways:

dramatically and by notes.

X

(start)

X (complete)

4. Show line numbers. X

(start)

X (complete)

5a.Show line sizes, material classes, class breaks, and

tracing.

X

(start)

X (complete)

5b.Show piping valve tag numbers (if required). X

6. For RE&C designed equipment, show nozzle sizes andrelative locations us ing RE&C draw ings and

specifications.

X

7. Show s tartup and decommiss ioning details.

8. Show UDD tie-in diagram numbers. X

9. Show instrument numbers X

10.Show how ESD systems function (i.e., a w ritten outline

of causes and effects).

X

11.For vendor design and equipment, w here complete

information is available on the “c ertified” specif ication,

show nozzle sizes and relative locations and other

details.

X

12.For vendor designed package equipment show thepackage outline and piping, Instrument and control

interfaces, including piping interface sizes.

X

13.For vendor designed equipment show the vendor

details, including piping, valving, instruments, controls,

and special details (e.g., v ents, drains, leak-offs , gland

condensers, governor valves, trip/throttle valves for a

turbine; instruments, burner valving, and controls for

heater, etc.). This detailed information typically w ould

be show on an auxiliary engineering flow diagram or

on a vendor draw n diagram.

X

14.Add client comments (if required) X

15.Show notes for non-standard controls. Also showESD Systems.

X

16.Show process vents and drains, sample connections

and chemical cleaning connections.

X

17.Show in-line instrument sizes. X

18.Show control valve manifold valve s izes and pumpsuction and discharge valve sizes

X



suction and discharge valve sizes.

19.Show pressure safety valve sizes. X

20.Show revisions to the piping resulting from the detailed

piping design.

X

21.Show rev is ions resulting f rom f ield changes . X

NOTE: If definitive estimate is required betw een the “For Client Comments” f or “For Approval” issue and the

“Certified” issue, then a “For Definitive Estimate” issue may be required incorporating some of the technical content

not required until the “Certified” issue, i.e., valve size as in Item 16., insulation and paint requirements, etc.

3. Line Table Technical Content for Major Issues

Line Table Iss ues

Preliminary Issue

to UPE

For

Comments

For Client Comments/ For

Approval

Cover Sheet X X X

Line Number X X X

Fluid X X X

From, To Flow Diagram No. X X X

Line Size X

Operating Pressure and

Temperature

X X

Design Pressure and

Temperature

X X

Insulation Code (HC, CC, PP) X X

Tracing X X

Material Class X X

Maximum Temperature for

Thermal Stress

X

Insulation Thickness X

Paint Code X

Testing Medium X

Test Pressure X

Service Classification X



'reliability is yet to become the most important characterstic of modern companies'

home | privacy | legal

© 2001 - 2013 Red-Bag

http://www.red-bag.com/jcms/index.php/about-red-bag/legal

http://www.red-bag.com/jcms/index.php/about-red-bag/privacy
