Thursday, 17 Jan Day 4 9:00-9:15a.25 hrs Overview of the day 9:15-10:45a 1.5 hrsMichael/Andy/Adam Recap and Prioritization of Functional / Workflow Implications / Downstream Data / Potential show-stoppers Core Team 10:45-11:00a Break 11:00-12:30p 1.5 hrsAdam/Jess/Andy/Mark G Storage volumetric validation - Planning Assumptions Overview-storage/archive, etc Core Team 12:30-1:30p Lunch Brought in 1:30-2:30p 1 hrMark A/Paul A Infrastructure Overview - Business Continuity discussion Core Team 2:30-4:30p 2 hrsEric/Ryan/Kelly/Ian Content Organization and Content Identifiers "deeper-dive" (internal & external IDs) Core Team 4:30 -4:45p Break 4:30-6:30p 2 hrs Mark A/Spencer/Glen/Ryan Application, Systems & Infrastructure Overview- concept, App functional architecture - landscape - how systems will "talk" - Harris status/roadmap Core Team 6:30p END OF SESSION

FUNCTIONAL IMPLICATIONS John Doe Executive Vice President Digital Division

Implications and Response What do we do with each of our four categories? (10) – Before – During – Outside – Analysis What were the key functional themes? ( ) What is your vote? (10) Sorting the key scoping follow-up items (prioritization) – (25 min) – Two Groups (Write themes on board – categorize)  Group 1: Programme Acquisition & Set-up, Programme Ingest, Technical QC & Version, Sales and Commercials  Group 2: Digital/OTT, Localization - Dubs and Subs, Promotions & On Air Who is on point for each area to own resolution of these items (one owner) (10) – Who do you need to involve on your taskforce? – HOMEWORK FOR FRIDAY:  Who should be on point for specific items  What is the timeline you need to close your items?  What are your initial thoughts on potential impacts to scope, cost, timeline, and vendor selection? What issues were not identified that also may need to be addressed (10)

Approach Before – Take a closer look at the items, group – figure out if there is a cost implication – Finish homework (some will affect the Vendor)  Determine which ones affect the  Sort homework into requirements vs scope  Validate what has already been covered in the RFP  Split Linear and Non Linear scope / costs – reach out the Eric Berger – determine the cost and figure out how we fund it  Make sure that our Analysis results in a design that supports both Linear and Non Linear – Two kinds of questions  Fairly tangible -  Moving target – How big are the bread boxes – Potentially used to give feedback to RFP/Vendor selection process During After Outside – What is the Digital scope of additional functionality