Page 56 - Megaprojects Playbook
P. 56

Drax Biomass



            LESSONS LEARNED









                 OWNER ASSIGNMENT

                 Do not accept assignment of vendor contracts from owner if the terms and conditions do not allow or include
                 needs of Haskell to finalize the scope. There was limited information in the vendors' contracts giving detail to
                 the drawings' deliverables and the coordination required after these deliverables were received. This left Haskell
                 filling the gaps on the details or paying for more design hours from the vendors. Details to think about include:
                       – Give vendors as many relevant specs and criteria as possible when asking for a proposal.
                       – Define the deliverables in detail - involve process engineering.
                       – Expect that vendors won't have all loads and utilities known at proposal time. Contingency is important.
                       – Progress checks on vendor drawings between deadlines.
                       – Warranty start dates should only be based on performance testing.
                       Any exceptions should be agreed to with the Owner.
                       – Equipment delivery milestones should NOT be a single date. Instead, provide multiple milestones based
                       on significant/major components of the equipment. Sequence and completeness of deliveries is crucial.



                 SITE LAYDOWN

                 There was not enough space and equipments and materials had to be relocated frequently.
                 Early in the site development, a site utilization plan should be established to identify
                 areas for vendors' large material laydown needs. Would suggest making laydown area
                 needed by each vendor as a question to be answered as part of the vendor RFP.



                 DEDICATED SCHEDULER

                 The projects were initially set-up for a three-month lag. However there were delays on the first project
                 that should have pushed the second project as well. The project did not have a dedicated schedule tracking
                 these issues and we did not have the projects tied together so we did not identify the issue until the projects
                 became overlapped. This caused resource issues for the duration of the project between each site. With a
                 program this large there needed to be a focused scheduler for tracking all aspects of the project.




















        50                                                                               MEGA PROJECTS PLAYBOOK | 2021
                                CONTAINS CONFIDENTIAL AND PROPRIETARY INFORMATION.  FOR INTERNAL HASKELL USE ONLY.
   51   52   53   54   55   56   57   58   59   60   61