31.01.2013 Views

Pay TV phase three document - Stakeholders - Ofcom

Pay TV phase three document - Stakeholders - Ofcom

Pay TV phase three document - Stakeholders - Ofcom

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Pay</strong> <strong>TV</strong> <strong>phase</strong> <strong>three</strong> <strong>document</strong> – non-confidential version<br />

9.149 In the context of a cost-plus cross-check, Virgin Media argued that accounting<br />

separation between Sky’s different businesses would be required to allow verification<br />

of the information submitted by Sky 545 . We are confident that the data we have<br />

analysed is sufficiently robust for our purposes and we describe our approach to cost<br />

allocation below. Furthermore, we have considered the impact of key parameters<br />

through sensitivity analysis (see paragraphs 9.178 to 9.183). We do not believe that<br />

imposing accounting separation obligations would be a significant benefit to our<br />

process.<br />

9.150 As for our retail-minus approach, in analysing Sky’s costs, it is necessary to allocate<br />

costs between different aspects of Sky’s businesses. The key categories which<br />

determine wholesale channel costs are:<br />

� Wholesale, retail and platform businesses: we have allocated common costs<br />

based on the number of customers served by each function.<br />

� UK and Ireland subscribers: we have allocated common costs based on the<br />

number of customers served by Sky in each of the two countries.<br />

� Residential and commercial subscribers: we have allocated common costs for<br />

premium sports between residential and commercial subscribers on the basis of<br />

revenue.<br />

� Basic and premium packages: we have allocated common costs on the basis of<br />

‘subscriber product units’ as a measure of value – as described in paragraph<br />

9.101.<br />

� Premium sports and premium movies: we have allocated common costs between<br />

these two categories on the basis of the total number of subscribers taking each<br />

product.<br />

9.151 Having established the costs which are relevant to the Core Premium channels as a<br />

whole, we then need to determine how these costs should be allocated to individual<br />

Core Premium channels. The majority of these costs are the programming costs of<br />

sports and movie rights. Our approach differs for sports and movie channels<br />

reflecting the different way in which these rights costs are incurred. In general, we<br />

consider the correct approach is to allocate rights costs to channels according to their<br />

value to customers. However, for movie rights costs, because of the structure of<br />

Sky’s agreements with the movie studios, we take a different approach. In more<br />

detail:<br />

� For sports channels, the principle we have adopted is that fees allocated to<br />

channels should reflect consumers’ perceived value of the content on each<br />

channel. We have examined Sky’s current sports contracts with rights-holders<br />

and related sources and have allocated these rights costs between Sky’s sports<br />

channels on the basis of a detailed analysis of channel listings and programme<br />

audiences, using viewer share data from the Broadcasters’ Audience Research<br />

Board (BARB) for 2008. For example, FAPL content is predominantly allocated to<br />

Sky Sports 1, much less to Sky Sports 2 and none to Sky Sports 3 and Sky<br />

Sports Xtra, reflecting Sky’s programming choices and viewers’ behaviour.<br />

Across a full portfolio of different sports, we would not see viewing share as a<br />

good proxy for value, since the duration and frequency of different events and<br />

545 Section 6, paragraph 6.32 of Virgin Media’s response to our Second <strong>Pay</strong> <strong>TV</strong> Consultation<br />

297

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!