July 2006 By: John Lagace, Director - Process Engineering at Commonwealth |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
“Get Your Scope Straight for Project Success” What is “project scope”? Scope is everything a project encompasses. It is the what, who, where, when, how, and even why of a project. It is the complete story, explaining what will be done, who will do what, when it will be done and where everything will go. It explains what is known, what is unknown and what must be further defined. As busy plant personnel, you do not have time to write novels, so you need ways to minimize the time it takes for developing your scope. “Replace steam turbine with an electric motor” is a problem statement, not a scope, though some people may insist otherwise. WHY IS A GOOD SCOPE IMPORTANT? Many companies now demand a +/- 10% estimate before making the business decision to commit capital to a project. A +/-10% estimate requires significant engineering effort to produce the documentation required (see Table 1). The cost to prepare a true +/-10% estimate is a major commitment, requiring from 20% to 40% of total TIC engineering depending on the type of project (Note 1). If a project is cancelled after expending this much money, someone in the head office will notice. Asking for +/-10% does not mean you received it. You probably have +/-30% or +/-20% estimates gussied up to look like more than they are. A +/- 25% estimate can often be used for funding authorization if the scope is well thought out and management understands what that level of estimate means (Note 2). Usually, however, the mean value of any estimate becomes “The e$timate”. This is unfortunate because the upper and lower ranges bracket the expected real interval into which the final cost will fall. In general, estimating is more accurate than the scoping. Estimates are blown more frequently due to things left out of the original scope than by poor estimating. If your preliminary scope is accurate, the median value of a +/- 25% estimate and a +/- 10% estimate will be the same. Only the range will be different. The +/- 25% estimate can be adjusted via "contingency" so that the upper limits align. Developing a good scope document is a major step in taking control of your small cap project costs, and can allow your company to become comfortable using a +/-25% estimate. A good scope document can allow badly conceived projects to be eliminated before much money is expended. WHO CAN YOU TURN TO?
Understanding that many co-workers have scope input and a stake in your project is a major first step to developing a good scope. In order to get the best information possible for “what”, “where” etc., the first order of business is determining your key players. This is your “Project Scoping Team”. It should include the key stake holders and experts as follows: Unit Representative - This is a knowledgeable person(s) in the operation of the unit(s) where the project will be located. If it will be a grass roots plant, this person is intimately knowledgeable of the process operation. Marketing or Business Rep. – This person is more likely to be involved in large capital projects although they can be instrumental in setting goals on production, new products and quality for smaller projects. Construction Rep. – It's not too early for this person to be involved . They will know if you require a large crane and for how long, a cost factor you will definitely want to know about early on. They think about things like underground piping, conduit, or contaminated soil as cost adders. The Construction Rep is a great advisor. Instrumentation Designer - This is an expert in plant implementation, not theory. Has an analyzer project ever come in at less than 5 times the original estimate? Between fast loops, exhaust stream treatment, stream conditioning, and a separate heated and air conditioned building to house it, these “instruments” can break a budget. If you have vendor packaged equipment, the matrix of responsibility can get incomprehensible in defining local, DCS and vendor panel responsibilities. Electrical needs can get complicated quickly too. He who gets stuck adding a 13KVA substation because they need one additional 1200 V motor and two 480 V motors pays the bill. Your I/E person will forewarn you so that appropriate cost factors are used to realistically estimate your instrument and electrical scope and cost. Environmental or HS&E Rep. – Remember “permits”? This person needs to understand what you intend to do so that the right permits will be available to allow it to be done. Permit applications take time and money. In today's world, permits are in the scope. Be aware of applicable OSHA, EPA and local requirements. Piping Designer - They will be able to realistically look at the current pipe racks and indicate whether they can handle a new project or if new steel will be needed. Not understanding this is a major cost risk. Projects always have more piping than first imagined. Don't forget insulation and tracing either. This is the person to help with this. What is a reasonable piping route to assume? Ask your piping designer. Civil Designer – Many people think of concrete as cheap, so they leave Civil out of their early scoping activity. This is dead wrong, because Civil is much more than concrete. Is the soil stable enough for putting up towers? What underground obstructions need to be planned around? Are underground drawings up to date, or is probing required? Will contaminated soil require disposal?
Utilities and Infrastructure Rep. – How many projects overrun because the Cooling Tower has no additional capacity and no one thought about it in time? The utilities expert will be able to make a knowledgeable assessment of utility requirements and existing capability so that your scope covers this critical area. Don't forget steam, air, water, nitrogen, cooling water, hot oil and power too. These people need not sit around a table together. Developing scope takes time. It is a dialogue, with info leading to questions leading to more info and more questions. Each question, fielded by the right person, will help a clear picture of the project to develop. KEEP TRACK OF ALL THE DETAIL Your primary document at this point should be a marked up Plot Plan called a “Coordination Diagram”. It shows the latest scope in terms of colors to reflect equipment locations, whether new, modified, moved, demolished; major piping routing, electrical feeds, MCC locations, DCS locations, utility supply locations and rates. This one tool summarizes everything in a picture all can see and comment on. Use all the margin notes you need to make sense of it. Show locations where underground obstructions are not well known. Show and list whatever is important to you. Show structure levels using small sketches on the back side of it. Show possible lay down yards and crane access routes. You may need multiple copies due to competing options. Change information as often as needed. Later, this information will be transferred to other documents. That point will be addressed later in the article. You are not trying to design your project at this time. You are deciding what is known and what is unknown; what is required by the project and what is outside of the project (not in the scope). As the project manager or sponsor; you are constantly writing down and documenting the scope to date; trying to ascertain what it is that you don't know that can bite you. Knowing what you do not know seems impossible, but it isn't, and it's very important. As the manager or sponsor, you need to steer the team toward the non-obvious. Ask them to visualize the project and to predict the biggest unknowns. They will have some idea. Take their opinions seriously. Ask what can be done to eliminate them as unknowns, and list that under possible solutions. What can be done if no underground drawings are available and extensive trenching, pilings or new underground lines are required? Add trenching and probing to the scope so that the money will be in the budget. When we have considered all of the knowns and unknowns, we will have our scope and a decent basis for determining the required contingency as well. Contingency, encompassing the known unknowns, is scope too. The better the definition at the beginning, the less chance of missing something significant later. This way of defining scope is useful no matter the project size. A small project can be realistically scoped out in a day if the right people are involved. Larger projects take a good amount of time. GETTING SPECIFIC Scope development can be reduced to a thought provoking check list (see Table 2). Be careful and really think before checking off each item. You will have a list of questions and possible answers when you are done. The next step is reducing your Coordination Diagram to other more user friendly documents as follows:
When all of these are considered, and the results are summarized, you have a scope to begin project evaluation. This work took you between a day and a month or so, and not full time.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||