Warning: Declaration of Jetpack_IXR_Client::query() should be compatible with IXR_Client::query(...$args) in /home/projec94/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php on line 91

Warning: Cannot modify header information - headers already sent by (output started at /home/projec94/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:91) in /home/projec94/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1719

Warning: Cannot modify header information - headers already sent by (output started at /home/projec94/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:91) in /home/projec94/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1719

Warning: Cannot modify header information - headers already sent by (output started at /home/projec94/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:91) in /home/projec94/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1719

Warning: Cannot modify header information - headers already sent by (output started at /home/projec94/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:91) in /home/projec94/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1719

Warning: Cannot modify header information - headers already sent by (output started at /home/projec94/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:91) in /home/projec94/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1719

Warning: Cannot modify header information - headers already sent by (output started at /home/projec94/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:91) in /home/projec94/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1719

Warning: Cannot modify header information - headers already sent by (output started at /home/projec94/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:91) in /home/projec94/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1719

Warning: Cannot modify header information - headers already sent by (output started at /home/projec94/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:91) in /home/projec94/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1719
{"id":218,"date":"2011-03-04T13:22:01","date_gmt":"2011-03-04T19:22:01","guid":{"rendered":"http:\/\/projectprofessionals.org\/?p=218"},"modified":"2011-03-04T13:22:01","modified_gmt":"2011-03-04T19:22:01","slug":"project-management-single-asset-owners","status":"publish","type":"post","link":"https:\/\/projectprofessionals.org\/2011\/03\/04\/project-management-single-asset-owners\/","title":{"rendered":"Project Management – Single Asset Owners"},"content":{"rendered":"

This post discusses unique project planning and management challenges associated with projects that are owned by single asset owners.\u00a0 Examples include power plants, large commercial facilities and process plants. \u00a0These assets tend to be project financed using the single asset as collateral.\u00a0 The financing typically relies on revenue generated from operation of the asset.\u00a0 Hence, delays in achieving revenue generating status can be extremely problematic.\u00a0\u00a0 Our conclusions and recommendations are based on decades of experience with many such projects.<\/p>\n

Introduction<\/h3>\n

Revenue generating facilities (e.g. power plants, chemical process facilities) are sometimes owned by a standalone entity.\u00a0 The design, engineering, procurement, construction, commissioning, startup and turnover of these plants and facilities can be particularly challenging for both owners and contractors.\u00a0 The planning, scheduling and execution of these requires attention to some unique and compelling factors.<\/p>\n

Often these owners are financed using project financing that is based on financial analyses focused on return on investment, cash flows and other time-related concepts.\u00a0 In these situations, the owner\u2019s balance sheet is limited and cash availability is the key.\u00a0 Further, these project management teams are formed from contract personnel with little or no infrastructure.\u00a0 Implementation tools for simple concepts such as project control processes, technical specifications or standards, and interface procedures may not exist.<\/p>\n

The project management teams (owner) may consist of contract personnel.\u00a0 While individually competent and skilled, the \u201cad hoc\u201d nature of such an organization is more characterized by individual skill sets and less by owner-oriented project management processes and infrastructure.\u00a0 Further, this sort of owner has no track record or reputation in the marketplace.\u00a0 This creates additional risk for the contractor.<\/p>\n

Another compelling factor is the nature of financing and\/or ownership.\u00a0 Projects that have public ownership tend to be particularly difficult for enlightened management if (and when) significant (planned or unplanned) disruptive events emerge.<\/p>\n

Finally, these owners seem unusually averse to implementing changes that are to the contractor\u2019s benefit (equitably).\u00a0 Both money and time are issues with these project financed owners.<\/p>\n

Consequently, unique project planning, management and control challenges exist.<\/p>\n

A key characteristic relates to \u201cstaying power\u201d in the face of significant disruptions to the planned execution.\u00a0 Significant disruptions alter the financial projections and cash flows that underlie the financing and project basis.\u00a0 Events that result in longer project duration (say 6-12 months delay to completion) challenge the asset or balance sheet of these owners.<\/p>\n

Case Studies<\/h3>\n

Examples of long term delays include serious design issues and major construction defects.<\/p>\n

In one such case, a construction defect gave rise to a long term (3-6 months) delay.\u00a0 As the contractor responsibly proceeded with remediation actions the extended schedule created pressure on the owner\u2019s balance sheet (cash position).\u00a0 The delay was aggravated and extended by a force majeure event which further impacted the owner\u2019s staying power.\u00a0 Ultimately, the facility was liquidated through a bankruptcy proceeding.\u00a0 It is not apparent that any of the primary parties avoided serious and negative financial impacts.<\/p>\n

In another such case, process issues (likely attributable to both the owner and the contractor) led to a prolonged commissioning and startup period\/duration.\u00a0 Of course, during this extended duration, the owner\u2019s cash position eroded over time.\u00a0 As above, the outcome was liquidation through bankruptcy.<\/p>\n

In both cases mentioned above, another influence presented itself.\u00a0 Both facilities relied upon a common commodity as feedstock and the output of the facility was to be a commodity.\u00a0 In both cases, the feedstock and the finished product experienced negative marketplace changes during the (disrupted) engineering and construction period.\u00a0 Further, operating costs were problematic due to energy costs.\u00a0 These negative marketplace factors degraded the deteriorating project financial projects and, therefore, financing options.\u00a0 While hedges and other risk management techniques mitigated the impacts, the size and complexity of the delays were too much for the tolerance level of these owners.<\/p>\n

Conclusions \/ Lessons Learned<\/h3>\n

The message and the conclusions in this regard is that unique and sometimes unorthodox planning and scheduling ways of working are necessary.\u00a0 These conclusions include:<\/p>\n