Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.
Where FEED sits between concept select and FID
Engineers often join a FEED without knowing what the previous stage decided or what the next gate expects, so they rework settled questions and miss the ones the investment committee will ask.
First tasks
- Ask the project manager for the owner's stage gate procedure
- Draw the gates on one page with the decision made at each
- List the concept select decisions and where each is recorded
- Write the FID gate requirements as a checklist for the team
FEED scope of work and contract read-through
Most FEED disputes trace back to a scope of work nobody read line by line: a missing tie-in, an unpriced survey, a licensor package assumed to be someone else's. Reading the FEED contract, scope of work and deliverables schedule against each other in the first two weeks, and raising every gap as a clarification, sets the boundary before the hours are spent.
First tasks
- Collect the FEED contract, scope of work and deliverables schedule
- Mark every scope item that has no matching deliverable
- Write the gap list with a proposed interpretation for each
- Send the gap list to the client as formal clarifications
Basis of design document
Every discipline designs against one document, the basis of design, which sets capacity, turndown, feed and product specifications, design life, availability target, utility conditions and the governing codes. Writing it early, issuing it for client approval and putting it under revision control stops each discipline from inventing its own assumptions.
First tasks
- Gather the concept select report, owner standards and licensor data
- Draft the basis sections for capacity, feeds, products and design life
- Mark every untraced value as an assumption with a named owner
- Issue the basis for client comment and log the responses