xoserve core + user pays discussion Marcus Stewart
Proposed Core + User Pays funding model for change/new services All future UNC mods will need to be defined as core or user pays when they are raised xoserve income/ costs Existing Services Core + User Pays UNC Core (known at PC outset) UNC Core (unknown at PC outset) UNC User Pays User Requested (either individual or group) User Pays (Sharing factor, refunding mechanism to all users) Total xoserve income +ve Price Control adjustment -ve Price Control adjustment Funding Mechanism Price Control Users defined at Mod stage Requesting user(s) Contract Mechanism Model A Model B