An evolutionary game analysis of user-pay public–private partnership projects

Abstract

Purpose With the growing demand for infrastructure and public services in recent years, PPP-UP have attracted a great deal of attention. However, while the user focuses on the payment for use and the private sector is concerned with its return on investment, the public sector pays more attention to the efficient utilization of public funds. In order to analyze the willingness of each stakeholder to join PPP-UP, an evolutionary game model involving the three parties is constructed. Design/methodology/approach An evolutionary game model is established that considers the users and the public and private sectors in user-pay public-private-partnership projects (PPP-UP). Eight scenarios of equilibriums and the game's evolutionary stable strategies are analyzed, and the corresponding stability conditions are then obtained. A situation where all three players are willing to cooperate in theory is also examined. The key influencing parameters that affect cooperation behaviors are further discussed. Findings First, the results illustrate that by properly adjusting the influencing factors, the cooperation status among the three parties can be changed along with certain evolutionary trends. Second, it is hard to modify unsatisfactory evolutionary stability by small changes in both the price compensation of and the construction and operation compensation. Third, it is necessary to involve the users in the decision-making process in PPP-UP and take their demands regarding benefits and payments into account. Originality/value In this paper, we focus on PPP-UP to research interactions among the public and private sectors and the users. Based on the analysis of the evolutionary game, to facilitate the successful implementation and development of a project, several conditions are needed to ensure tripartite cooperation. Several recommendations are then proposed for decision-makers in PPP-UP.

Cite this work

No public copy is stored for this record, so only the metadata is cited.

Stored only when both papers are in the corpus — 21 citations exist upstream.

Papers that cite the same references — the relational fallback while embeddings are still backfilling.