1 / 15

Embedding effective Project Control - Lessons Learned

Embedding effective Project Control - Lessons Learned. Project Control Lessons Learned Simon Springate – CH2M HILL Head of Project Controls, Europe October 2014. Introduction.

Download Presentation

Embedding effective Project Control - Lessons Learned

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Embedding effective Project Control - Lessons Learned Project Control Lessons LearnedSimon Springate – CH2M HILL Head of Project Controls, Europe October 2014

  2. Introduction CH2MHILL is renowned for supporting some of the UKs most iconic projects such as the Olympics 2012, CrossRail, HS2 and Thames Tideway plus many more globally. When the starting gun fires how do you set up project control that is both fit for purpose and its deliverables welcomed by the client.

  3. It’s a conversation I work on the principle that all management is a conversation In life all knowledge is shared through conversation

  4. What knowledge will make the client ‘comfortable’ • We are in the business of making clients client informed and confident in our material • We want to facilitate an open conversation • We want to support our Client in reporting to their ‘client’

  5. So what is Project Control • It is a term that grew out of the integration of project support disciplines • It treats Planning, Cost control, Risk, Change management & Reporting as an Integrated system • It understands how these disciplines relate to others such as Document Control, Quality Management and tools such as BIM

  6. Classic mistakes of project control • Aiming for an automated system early on • Data Cubes • Those designing reports are more aware of the project minutia than those reading. • Keep it simple • Projects change their nature • Design is not the same process as construction which in turn is not the same as commissioning • Projects are about people • Material produced has to support the performance discussion or provide assurance

  7. Start with the output • What does the client need now • What will they need – do they believe you? • Classic – Money & Milestones • Midway – Loaded schedules and contract integration (NEC3) • Fully functional – Earned Value

  8. The Basics • Time • Money • Change Control • Risk Management • Value & Opportunity Management

  9. Start with the output • An educated client is an easy sell • Be aware that their priorities are not always the classic time/cost & Quality • Reports are quick to model (excel is your friend)

  10. Basic dashboard

  11. Original dashboard

  12. Sophisticated Dashboard

  13. There is no universal dashboard • Has to be designed to support the client priority • Safety • Cashflow • Deliverables • Risk exposure • Rate of change • Commentary –the critical bit

  14. Key LearningIf no one is questioning the content of your report no one is reading it!

  15. Thankyou for your time I am always happy to talk Simon Springatesimon.Springate@ch2m.com

More Related