You are on page 1of 3

June 2010

Upcoming Training Course
Engineering Coordination Tips During being held in Rockaway, NJ
Front-End Engineering Design • Course 1613A, Turnaround
Best Practices
By Jerry Lacatena
October 26-28, 2010
This might be a statement of the obvious to many, but it’s surprising how often some fundamental For more information, see our
coordination tips for successful front-end engineering design and execution are forgotten under website at www.carmagen.com
pressure. There can be exceptions and additions to any project; so, these tips are not all
inclusive. This article hopes to provide a checklist for such work and why we need to remember.
Work Highlights
Scope of Work Equipment Lifting
Every front-end design project should at least start with a defined scope of work document Provided onsite
assistance in the
detailing the extent and specifics of the work, expected deliverables, and format/content of the initial review of
final product. This document is part of the contract, which ultimately controls the required work. overall
It’s not uncommon for work scope to evolve during the course of a project, and often those equipment lift
involved just do what they are asked without consideration of contractual obligations or recording plans and
decisions which differ from those obligations. It is important not to lose sight of the formal project procedures for a major capital
objectives, and to mutually change them as appropriate in a timely manner if they are no longer project currently underway in the
Far East. Follow-up detailed
pertinent. review activity is anticipated as
specific equipment lift plans are
Confidentiality developed by the contractor.
The contract may also indicate certain requirements for non-disclosure of proprietary information,
which must be understood by the team and considered in the conduct of work. However in certain Process, Operations, & Safety
instances it should be confirmed that third parties, who need to provide information or respond to Providing
project requests, acknowledge confidentiality also. technical
expert
Performance Requirements litigation
support to a refiner on a case
involving a process technology
It’s essential for the process designers to be aware of all performance requirements specified in
licensor. Client’s revamped unit
any process guarantees, and if defined liabilities apply. The technical values and wording was alleged to not meet process
contained in the guarantee document are important, and surprisingly may not always convey the performance requirements after
full expectations. If this occurs, it could result in litigation. For example, if a guarantee document implementation of their
includes a capacity, a product quality, and a catalyst life guarantee, the wording must clearly proprietary technology and
define that all guarantees are coincident during operations, and cannot be met independently and catalyst.
still satisfy the intent. All involved in execution want the facilities to perform, but generally
guarantees without defined liabilities are considered of lesser priority than ones that do.

Carmagen Engineering, Inc. – Industry Leading Engineering Consulting and Training
4 West Main Street, Rockaway, NJ 07866 • 973-627-4455 • www.carmagen.com

and recovered later when necessary. Electronic data and/or hardcopy procedures information. how to handle condensate (usually weekly or bi-weekly) to discuss schedule. owner. and change notifications the project. and An early task on larger projects also includes assessment overall performance usually is detailed in a Basis of Design of resources. technology. personnel (with contact information). preference for maximizing air cooling. This is particularly important if the owner desires that his standards be used Proper management of change is required for efficient instead of the licensor’s or contractor’s. and schedule based on the latest document. and on more complicated multi-unit projects. or It is prudent to conduct brief periodic status meetings specific instructions (e. since there will execution and technical quality. who will receive These would augment the basic engineering design data correspondence distributions. changes. so data can be properly to the project. feed stocks basis. be defined. Outside support by third-party mesh. products with specifications. These might also include safety margins on process equipment. along with critical path analysis. Needs and action items are typically captured on a list with date and Design Standards status tracked to confirm when items are resolved. client process design criteria and owner preferences on the unit and/or others. You can’t underestimate current/valid and mutually understood by the parties the value of having the right people in the right place on a involved (i. also need attention. Ensuring that the design basis is productivity and product quality. and to interfaces. Coordination Procedure Information Memoranda It helps greatly to establish a coordination procedure early Memoranda are often used to disseminate more specific to efficiently communicate between project team.e. and local codes which will apply project document control needs. . and transmittals of (BEDD) that every project should establish at the start of specifications or information.. It is recommended that the use of design standards be Management of Change identified quickly to avoid issues later. and identify the key staff and client level. Project changes need to likely be differences to reconcile. instructions and information usually are assembled and distributed to the team and maintained for the duration of Status Meetings the project. to consultants can be used to augment project teams with prepare a systems diagram schematically depicting these specific technical expertise. Change impacts need to be assessed. These general design guidelines. filed. contractor) is of paramount project roster. and an e-file index set-up that covers environmental regulations. outstanding information or decision needs. licensor. approved by a responsible party. or they may apply to specific sections of a project. utility data.Basis of Design Resource and Schedule Assessment On any process unit. and then assimilated into a master project schedule with compositions. and implemented by the team. recovery. or problems. which tends to improve interfaces and conditions. the capacity.. importance to a successful project. and requested piping details that may deviate from general current technical issues. discount the value of face-to-face contact. the type of unit. and reflected into the master schedule and manpower requirements. BEDD includes climatic data. You can’t design standards due to location). capabilities. operating flexibility requirements. Monthly performance will and battery limit conditions of process streams to/from unit be tracked during the project to identify problems. or priorities. equipment standardization preferences. It’s advisable to check at the very beginning forecast any course corrections necessary to achieve that the upstream and downstream unit’s design bases timely completion.g. That document usually includes a simplified execution plan and technical requirements on a per unit schematic of the process flow. utility automatically.

coordination. reviewed calculations and pertinent documents need to be organized and properly filed at completion. correspondence documentation. clients. HAZOP reviews may be conducted before (preferably) or after issue as long as the status is defined. Would you like more information about Carmagen? Please visit our website at www. For more information. and a plan agreed upon. key plot. please contact Jerry at jlacatena@carmagen. having extensive plant design experience on numerous revamp and grassroots projects throughout the world. etc. vendors.com. discuss issues. Excellent presentation. actual) • Status meetings (periodic. technology evaluation. document control • Progress Tracking (schedule execution performance. All the approved comments must get incorporated prior to sign-off. language. other) • Schedule (overall & by unit or task) • Coordination Procedure • Team Capabilities/Manpower (need for third-party technical consultation) • Project e-file. etc. Front-End Engineering Design Checklist The following checklist summarizes the main areas to be considered in Front-End Engineering Design. and liability) • Basis of Design • BEDD (location. environmental regulations/local codes. with values. units of measure. licensor. to plant performance testing.) • Process Design Memoranda (design preferences/criteria. plan vs. and scope should be assured via technical reviews prior to final release. general instructions & information.Technical Reviews Quality and consistency of the unit deliverables with the design basis. transmittals. Proficient and organized multi-tasker. contractor. . communication. and interpersonal skills utilized to develop strong working relationships with team members. sub-contractors. climatic conditions. guarantees. If the project does not continue directly into the detail engineering phase.. etc. • Project Scope of Work/Contract • Confidentiality • Process Guarantees (stated coincident or independent. priorities.) • Management of Change • Needs List (tracked) • Quality/Technical reviews/HAZOP • Final Process Package/Close-out Jerry Lacatena has over 30 years of process engineering experience in a broad range of design applications and technologies.carmagen. safety margins.) • Standards (owner. EPC development. with projects ranging from feasibility studies. and technical licensors. etc. FEED.com.