1. Presentation Preparation Overview The format will be as follows for all of the sessions will be as follows – First third of the slot will be a presentation describing the area being discussed. Current state, future state, challenges and opportunities.  (Each Presentation should be about a third of the timeslot allocated but no more than half. So if you have 1.5 hours allocated, plan on 30 min of presentation and 1 hour of discussion) – Next third to half will be discussion on questions raised prior and during the session. Any known questions should be listed in the presentation deck. The room will be split in two (representative) to maximize discussion  Known questions to be printed on Cards prior to the meeting (see template in back of this presentation)  Participants will add any new cards during the exercise  Questions will be sorted into the following categories: – Resolve before project starts – Resolve during project – Resolve after project  All of the questions that need to be resolved before the project starts will be discussed. – If resolved in discussion, resolution or requirement will be written on the back side of card and an R will be written on the front side of the card – If not resolved, the homework necessary to resolve the question will be written on the back and an H will be written on the front of card – Report back - the two groups will then report back to each other – Wrap up – Next steps and highlights will be identified for each session Logistics – Use this template for all presentations – Presentation should be completed by Friday, Jan 11 th EOD for review – Please reuse content from the RFP or existing material. We are not asking you to start from scratch – We ask that you involve other points of view in your preparation or in prior questioning – Mark will send you and questions he receives prior to the session

2. LIBRARY & ACQUIRED PROGRAM SETUP WITHIN THE BMS/MAM John Doe Executive Vice President Digital Division

3. Understanding the basic programme set-up terms Review as a team the following terms: – Deal memos – Program grid (source of program, contract and rights level data being entered into Vision) – Programme – Programme set-up (season title, episode, version, materials) – Library content vs. Acquired content – BMS – MAM

4. Introduction – Library & Acquired Program setup within the BMS/MAM Programme Setup within the proposed workflow.

5. What we may know about the programme set up workflow… Deal memo created Program Grid generated from deal memo Program information entered into Vision manual

6. Understanding Deal Memos Is the catalyst for a programme set up the creation of a deal memo? What information exists within the deal memo? Are deal memos currently stored in any source deal/sales system? If so, does this system have a title/program repository? Does the structure of a deal memo ever change based on the territory or the deal itself? How are deal memos communicated in order to get the programme grid process going? Sample deal memos?

7. Understanding the Programme Planning Grid See sample grid on next slide What is the programme planning grid? At what point is the program planning grid generated? – Is this generated off of the deal memo? If so, does the status of the deal memo trigger the creation? – What is the full set of information needed for the generation of the program planning grid? And does it all come from the same source? (i.e. deal memo?) – Does the format of the program planning grid always stay the same or can it vary based on the territory or deal type? Is the program planning grid used to input information into Vision? – If yes, is this automated? Or manual data entry? – If yes, what set of information gets inputted from the grid into Vision? Some? All?

8. Program Planning Grid

9. Program Grid Detail Distributor Deal Status PG Translated Title (i.e. Russian Title) Title # of episodes 1 hour ½ hour Number of runs License period start License period finish # of months Catch up

10. Understanding current Program Set Up At what point in the current process does the actual programme get set up in Vision? – What information is used to do the initial programme set up in Vision? – Are there any internal or external content identifiers available at the time of programme set up? – Does it get set up all at once (i.e. Series, Season, Episodes, Versions, Materials)? Or when each piece of information becomes available in the process?  i.e. Series/Season set up from initial programme planning grid. Episode set up nearer to the time of execution or when data available Is the version and materials set up in Vision all considered part of the programme set up process? At what point does the user begin sourcing information from 3 rd party sources (i.e. IMDB, Wikipedia). – Are there any internal business systems currently that some of this information is sourced from? Does the programme set up process differ based on if deal memo titles are from existing library or aquired? What data needs to flow to the MAM from Vision? – What programme, rights, materials information needs to be fed over to the MAM? – At what point in the process should each piece of information be received in the MAM?

11. Ingesting assets for programs At what point in the workflow is the source content (assets) ingested into the MAM? How is the content currently delivered by distributor? What (if any) information is delivered with the source assets? – If data is delivered with the source, does it get stored anywhere? – What type of data is given? – What various formats does the distributor deliver data in? – Is there a standardized format to receive content? How does the distributor tie the source content (assets) to the program version in Vision?

12. Overview – Library & Acquired Program setup within the BMS/MAM Key areas regarding setup and the BMS(Vision) – Contracts & Rights – Programme Data Currently Held in BMS – Interfaces

13. Contracts & Rights – Library & Acquired Program setup within the BMS/MAM Contracts & Rights – Data entered by different people dependant on channel target region. Africa – London Based Acquisitions Manager Eastern Europe – Budapest based Acquisitions Team Germany – Director of Programming & Acquisitions UK, Italy, Baltics, Western Europe & Middle East – London Based Schedule Managers – Acquisition Managers & Programme Managers provide the details of the deal in a grid to those above and traffic between 1 year & 3weeks from 1st TX. This timeline differs as some regions confirm deals closer to TX than others. – Contracts are entered once deals have been confirmed (often before the terms and rights have been finalised). Data held in Vision Contract – Contract Reference – Contract Type (Acquired etc) – Contract Status (New, Signed, Expired) Rights – License Start Date – License End Date – Allowed Number of Plays – TX per Play – Transmission Period

14. Programme Data – Library & Acquired Program setup within the BMS/MAM Programmes, Episodes Versions & Materials data is entered into Vision by the Traffic team. High level Programme data is provided by the person who closes the deal and Episode level is taken from the internet IMDB, Wikipedia etc. Mandatory Programme Data fields are: -Programme Title -Programme Status -Slot Duration -Programme Type -Episode Title -Episode Number -Default Version -Version Title -Material Part -Material Barcode/TX ID -Material Timecode & Durations Other information that is currently entered includes: -Titles (for EPG Listings) -Genre -Billings & Synopsis -Cast & Credits -Aspect Ratio values -Source details -Certification -Classification

15. Programme Data Continued – Library & Acquired Program setup within the BMS/MAM Majority of data entered at Programme Level filters down to Episode and Version Level. All Material data is entered at the Version Level. Vision can also hold Subtitle, Dubbing and Music information against programmes and episodes however this is not currently utilised. There is currently no Series Level included within Vision however there is an enhancement planned to add this.

16. Interfaces – Library & Acquired Program setup within the BMS/MAM Interfaces -Playlists: Built for playout/automation purposes contain minimal metadata. -Break & Spot: Integration point with ad sales systems for the importing of 3 rd party commercial data. -Listings: Used for EPG & Web Reports, more flexible point of export but doesn’t contain access to all metadata. Known performance issues when pulling larger ranges of data. -VIL: Not currently used in EMEA but used successfully in LATAM. Access to 90% of data however can impact on production performance.

17. Questions

18. Report Back

19. Wrap-up and Review

20. Question 1 -Question 2 - Question 3 - Question 4 -