TEMPLATE FOR PROJECT INITIATION

PROJECT SCOPE States the scope of the Project, its deliverables and customer request and technological issues PROJECT TEAM PROJECT MANAGER TECHNICAL TEAM

< name of Project manager> Technical manager Mechanical

PROCUREMENT FINANCIAL MAIN MILESTONES PROJECT STARTS FEASIBILITY STUDY CONCLUDED CONCEPTUAL ENGINEERING CONCLUDED PROCUREMENT CONCLUDED PRICE CALCULATED TENDER READY FOR DELIVERY TENDER BUDGET PRICE 1st estimation Goal price (estimation)

< name of tech. manager> < names of mech team members> Electrical < names of electrical team members> Civil < names of civil team members> < name of procurement responsible> < name of financial responsible> (responsible for price calculation) DATE <___/___/___> <___/___/___> <___/___/___> <___/___/___> <___/___/___> <___/___/___> DURATION YY days YY days YY days YY days YY days YY days

< price estimated by historical records of similar projects> <competitive market value of this particulary Project>

TEMPLATE FOR PLANNING PROCESS

COMMUNICATION Define here: 1- Internal protocol communications 2- Communication protocols with suppliers (information to be requested/provided) 3- Confidential communications/ information 4- Who does the communications 5- Who receives the communications 6- Templates to be used for RFQs ROLES AND RESPONSABILITIES PROJECT MANAGER <Describe Project manager responsabilities> TECHNICAL TEAM Technical manager <Describe technical manager responsabilities> Mechanical <Describe mechanical team responsabilities> Electrical <Describe electrical team responsabilities> Civil <Describe civil team responsabilities> PROCUREMENT <Describe procurement department responsabilities> FINANCIAL <Describe responsabilities> PROJECT COST PLAN Responsible <identifies who is responsible to manage costs> Project Budget <> Measuring Project costs < Detail here how the costs will be measured> PROCUREMENT PLAN Main items to be procured Item Suppliers

Types of contracts to be used

Item

Contract type

Vendor Management

Describe the roles and actions the project team and procurement department will take to ensure that the selected vendor provide all products/services agreed upon

SCHEDULING Shall be provided in MS Project a Project gant chart with the activities for the tender elaboration.

CONTROLLING PROJECT STATUS

WORK PLANED LAST WEEK Provide a highlight of work performed and milestones and/or deliverables met during the past week. WORK PLANNED FOR NEXT WEEK Provide an overview of the work being performed during the next week and any milestones or deliverables you expect to meet. OPEN ISSUES This section should contain a list of open issues along with their status. OPEN RISKS This section should contain a list of all open risks (risks which have occurred, or are on the verge of occurring). DELIVERABLES & MILESTONES Planned Forecasted Actual Status 1st price estimation Conceptual engineering Technical solution defined Power Plant Layout Civil MTO Mechanical MTO Electrical MTO C&I MTO Packing list defined Man Power for construction defined Site logistics defined Technical proposal concluded Cash-flow calculated Off-shore price calculated On-shore price calculated Commercial proposal concluded

CLOSING THE PROJECT TEMPLATE

TRANSITION TO PRODUCTION DEPARTMENT Transition Approach Define the overall approach to the transition to production team that will execute the project. Subcontractors Define all the existing contracts and if/how they will be transitioned. It should contain this information in a table format (subcontract agreements, maintenance contracts, etc.). Knowledge transfer Define how knowledge will be transferred from the incumbent staff to production team (documentation/instruction manuals including as-built documents, etc.). This is an important consideration as the transfer of knowledge is what provides continuity for the contract. LESSONS LEARNED FROM THIS PROJECT The lessons learned must be communicated in a consistent manner. In addition to the categorization and description of the lesson, it is important to state what the impact was and provide a recommendation for project managers to consider on future projects. All project lessons learned and other historical information need to be transferred to the knowledge/database in order to provide one centralized repository for ease of use. This should also include information on issues and risks as well as techniques that worked well which can be applied to future projects. Issue name Problem/Success Impact Recommendation

PROJECT SCHEDULE Describes projects planned schedule and how the project measured against this plan. Project Phase Scheduled Completion Actual Completion Comments