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 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… – 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 – Assess list against Kate / Lyle expectations – Determine our vetting approach and committee – Share results with broader team Two kinds of questions – Fairly tangible – Address tactical items ….. [ ] – Moving target – How big are the bread boxes – convene group for philosophical points Potentially used to give feedback to RFP/Vendor selection process Prioritize

During – Refine statements – Capture list of requirements. Include in either RFP or Project scope – Share new list with vendors to validate scope understanding – Vet requirements with committee Analysis – Conduct an initial analysis to determine their buckets and move them into their correct spot Outside – Assign tasks and determine if there are any key dependencies – What is the Digital scope is needed additional functionality

Infrastructure Next Steps Space – Hold space – Look to begin negotiation on long term agreement Follow-up with TSL Local territory infrastructure requirements – Storage / Hardware – Network – Ingestion Workgroup – Sticky notes – Paul’s questions (detailed requirements, user locations) – Any requirements from other work groups See if we any hardware purchase opportunities in this FY (signiant and aspera)

Assignments of Key Theme Follow-up Items VOD/Non-Linear (Spencer Stephens - Christopher Taylor) Content Identifiers & Relationships & Inventory Management & Metadata (Kelly Harkness) Program Acquisition and Rights Management (Iverson/Caz) Integration - Vision/BMS, Business Systems changes, Finance (Allsop) System Architecture (Ryan Kido) Infrastructure Requirements (Glen Marzan) Technical Specifications & Client Profiles (Adam Moore) MAM Requirements: Overall and Distributed Ingest, 3rd Party Integration (Adam Moore) Workflows & Prioritization of Tasks (Andy Bolding) Security (Jaspal) Reporting (Chris) Operations - Support & Maintenance (Gleeson) Implementation Approach & Scope Management (Bob)

Transition / Operational Planning (and some project planning) To Dos – Shrink this down for Kate and Lyle Project Transition Planning – Potentially consider how the interim solution will coordinate with the MC project – Content migration needs to be planned – Coordinate with any business projects / external risks – What is the phasing and schedule for the channels and territories “Budapest and Madrid” (rollout strategy – lower risk) – Make sure we plan for POC opportunities that reduce the project risk – Identify all of the “knowns” and best practices – Identify any efficiencies planned by the media center and communicate to processes before the trigger points – Investigate and additional security requirements (such as facilities) – Are there any other SPE projects that can affect this project? – Setting expectations of time availability of LA resources Operations Design as a work stream in the project design – Generally – Determine the communication design for notifications – Transition planning need to account that we cannot affect current operations – Include the BMS systems transition and support is also planned and coordinated – Plan for preventive maintenance window (NO FRIDAY CHANGES) – Approach for how we do operation and technology changes – What systems and processes will we use to track configuration, incidents, problems and enhancements, asset tracking – Support Planning  Consider more technical resources for the front line support to improve first call resolution  Plan for development support / enhancement roadmap  Review SLA response time

Transitional and Operation Planning Continued Plan for Backfills – During for functional design requirements (identify the people – communicate to Kate and Lyle) – Determine staffing for operational Testing support (need back-fill for traffic?) – Traffic schedulers – Programming – Promo productions – Anyone doing ingest – Metadata creators for the websites Plan for business continuity – “what if we need to change a playout provider” – What is the plan for a degraded mode (Red book for Crisis) Project Readiness – Include integration testing – Plan for the Hypercare period – Calculate the peak times – Plan for the other systems (EAGL, GPMS, BMS)

Systems Architecture Tasks & Analysis – Investigate ECM integration (SPiDR) – Scripts and subtitles Client deliver profiles and master data Seciurty – IDM integration – Investigate local site minder instance / High availability – Facility security Boxes to ADD – Integration with Farmerswife and phasing / timing – Annotation – Audio Conform – MDM Tool? – Vidispine Specification – Statement of IMF – Other metadata standards Reporting – What is the reporting architecture – What operational reporting do we need? / Where? EPK / Promos – can we start using EAGL? Incident reporting / Service Now / Asset Tagging / 3 rd Party support system Ingest – Physical material ingest - Tape / HD – Smart jog – Regional requirements Application Security and User Profiles Non-Linear – eg. SKyGO metadata requirements Document Finance workflow Design Principles – Preserve File Names – Carefully use smart and dumb naming

POC Opportunities CPII – Cerify – Transcoders – Automation Tools – EAGL – “Maybe” Cineshare – “Maybe” GPMS Integration – GPMS POC – WebMethods and Harris Technology – Demo Systems – Signiant – Aspera – Non Linear Scheduling – Rights Management – Tech Logger / CFP Infrastructure – Network and Storage Lag Times Design – Overall user experience (how many systems do I need to work in) – UI Design (screens and workflow match) Operations – Workflows (Define)  Design of the workflows for efficiencies – Work management (Farmerswife) & Organization – Training and Change Management (and Time) – Incident reporting – Working Environment “Corporate Environment” – How long we store playout – Where we store assets – Reporting – Onboarding procedure Standards / Metadata / Data – Metadata Structures – Identifications – Client Profiles – Master Program Data – Distributor Specs

Next Steps Working Groups – Follow-up for the working groups (Eric) – Identify the team RFP – Michael on Point – Start working on ratings Greenlighting – Come up with the time line in two week Stakeholders / Communications – Bob updated – Follow-up with Kate and Lyle  Bob on Wednesday  Catch-up in 1 more week – Follow-up with workshop team - core team – end of next week – Schedule core team meetings – Team communication method / scorecard – Allsop template – Steering committee – Start planning on broader communication – Identify people that were not here and follow-up (engagement) – Resource availability (Holidays) Any other Missing Items

Workshop Wrap Went Well Do Different