VOLUMES

RFP Summaries Inbound to MC 14,500 hrs supplier programme content per annum is required into the MAM- managed disk storage. Equates to 40 hrs/day assumed an overall 30/70 SD/HD content split, 900 GB of data per day. To be added to this figure is that for the circa 100 hours of supplier commercials content per annum, equating to around another 7 GB of data per day. This gives a total input data volume to the store of 907 GB per day.

RFP Summaries Assuming a window for acceptance of distributor programme content of 30 days and that distributor content would not be staged to data tape storage during this period, this implies a storage volume for incoming content only of circa 30 TB.

RFP Summaries The same disk storage will be used for: – storage of work in progress content supporting programme QC and versioning operations – source content for promotions – work-in-progress content for non-linear – browse proxy content for the whole operation.

RFP Summaries Data volumes input in connection with the initial automated QC pass of received distributor masters will be as per above (900 GB/day). Assuming the transcoded / transwrapped distributor masters will also be subject to automated QC, this will require that approximately the same volume of data will need to be input again(900 GB/day), giving a total of 1.8 TB per day.

Input to the transcode farm responsible for content normalisation to and for the production above at 907 GB per day.

How CineShare is currently used Output volumes from this transcode farm will be similar to input volumes with the addition of % to account for the generated browse content, say 1,000 GB per day.

Assumed that browse proxy content for use within SPTN will be persistent. Use could be made of the data tape storage to stage browse content that was older then, perhaps, 3 years. A browse proxy will exist for each item of TX ready content. A storage volume of 28 TB per annum is calculated for SPTN in-house browse.

To these figures for SPTN's internal browse proxy volumetrics, should be added figures for the separate browse proxies needed to support production of language localisation content (language tracks and subtitles). Production of these additional proxies could generate a further 25 GB per day (based on 12,000 programmes per annum requiring localisation). If to be persistent, this would require a storage volume of 10 TB per annum for reference browse. It is suggested that browse proxies would be staged to data tape after 60 days

Pessimistically, weassume every channel also requires a B version, resulting in further 900 GB per day of new programme content being output from QC/Version edit. This gives a total output of programme content from the QC / Version edit process of 1,800 GB per day. Assuming this content would remain held on the MAM-managed disk storage for 30 days, this implies a storage volume for newly created programme versions only of circa 55 TB

With 9,201 input hours of programme content for the London-channels, and assuming a shot selection ration of 10% using MAM/browse, this equates to a transfer volume of 64 GB per day from the MediaCentre to the London production workgroup. Volumes of finished promotions being returned equate to 4 GB per day.

QUESTIONS ROUGHLY HOW MANY STREAMS MAKE UP THE 14,500 HRS PER DAY OF PROGRAMME CONTENT? (RYAN) WILL ON-AIR PROMOTIONS USE MC STORAGE AS WORKING STORAGE? (Currently not planned) We need to validate the assumption that THERE ARE 3 OR 4 DISK READS FOR EVERY FILE THAT COMES IN – E.G. 1tb INBOUND FROM EXTERNAL, FURTHER READS FROM DISK WITHIN MC FOR AUTOMATED QC ETC HOW MUCH OF CONTENT CREATION PROCESS FOR PROMOS WILL REQUIRE RESTORE FROM TAPE OR ARCHIVE INTERACTION RATHER, THAN WORKING STORAGE Validate the number of versions that we need to plan for… Validate the impact on our assumptions after we make an enhancement to Vision v4.x (program in a program) to reduce the amount of physical storage Validate territory requirements (estimates) are covered