Team Meeting 1 To Dos Review Agenda for the 17 th Agenda for Next Week (round 1) Change Management Scope, Projects and Tracks and Timelines Review of Roles Team Culture Coordination with Other Projects

Project Set-up Next Steps and Dates Project Setup – Budget Allocations (Eric) – Cloud with Steve / Finalize Cloud (Eric) – Vendor Selection / Contracting (Eric/Mark/Tony/Dennis/Ophir) – Solution Finalization – Complete Selection Analysis Deliverable (Eric) – Project Space & Russell (Adam/Ayten) – maybe one for onsite vendor – Backfills (Mark/Chris) – Refined roles and responsibilities (Eric/Chris) – Project Staffing (Team) – Project Technologies / Tools – Detailed AWS planning and Training in LA week of August 12 th + End of Sept – Kick-off Agenda – Sequence of Channel Conversions Delivery – Program, Metadata and Integration Planning (Week of Aug 4 th )  Content Hierarch and Program Data Conversion Planning  Harris Planning – Integration Layer Go Forward (Kelly) week of August 12 th Steering committees (end of Aug) Formal overall Kick-off September 17 th in London (After IBC) Scoping Spain and staffing

Agenda for 17th Meeting with the Vendors Clearly define Vendor roles and responsibilities Update of the project to the business Assigning main contacts What does the project look like What does the core user group team look like (Key people) – Andy and Chris Spain… Cover budget, Scope, Schedule Refined budget review with Kate Team Meeting Introduction of Technology to larger team / Demo Introduce the team and their roles Review deep dives and times required List the projects Sukhi and the Finance P&L Tech Ops Collaboration ASPERA Project / Review with Tech Ops Opportunities with IBC Debrief Interactive Session with Group MedaiCentre Kick-off Video How Ongoing Communication / Stakeholder management will occur Describe Phasing Dave and Encompass

Agenda for Next week Red Hat AMMO CAZ Inventory Heirarchy Giant Source UAT Strategy GlobalTrax BPM End to End Workflow Mapping AWS Training Team Meeting Drinking Coordination with Provys Data Migration Tools

Change Management Roles & Responsibilities (RACI) – Project – Post Project Roles Communications Plan – Territories – Users – Executives – Supporting groups (Legal / Finance) – Encompass – Arqiva – Levira Group s User Engagement Strategy / Approach – User Group Committee – Users time Stakeholder management – Steering committee – User group* Team Culture CM Support / Coaching Key Super Users Identified – Richard Hard maybe – Mark McInnis – “Core Team” MediaCentre Branding and Logo Team Set-up Sharepoint Site Training

Steering Committees Executive Steering Committee Bob Billeci (Chair) Andy Kaplan Stephen Andujar Drew Shearer Mark Rogers Steering Committee Bob Billeci (Chair) Kate Marsh Lyle Stewart Sukhi Arora Spencer Stephens RCIO Mark Gleeson Eric Iverson Chris Roudette Charter: Validates and sponsors initial scope. Focuses on any Large Scope, Schedule or budget impacts. Provides direction to strategic budget decisions. Provider inter- company support. Ensure program priority alignment within organizations. Supports resource availability. Provides executive oversight. MEETINGS Meets Every 8 weeks Meets prior to GL and Immediately after GL Charter: Finalizes initial scope. Focuses on any medium and large Scope, Schedule or budget impacts. Manages the pacing of the project. Provides direction to functional/project budget decisions. Supports change management activities and other organizational decisions. Ensures program priority alignment within working teams. Supports resource availability. Provides program oversight. MEETINGS Meets every 4 weeks to start and every 6 weeks starting in Jan 14’ Meets prior to GL and Immediately after GL SCOPE MANAGEMENT

The MediaCentre Projects Master Program (Eric) – AWS MAM Buildout (Eric+) – Local Installation Buildout (Chris L.) – Network Buildout (Paul) – Aspera Project (Chris L.) – Metadata and Integration Buildout (Kelly) – Scheduling Systems Enhancements (Chris L.)

High level Scope Review Scalable Media Asset Management (MAM) – Vidispine and Cantemo based MAM solution – Cerify and Aspera – Leverage MCS tools Infrastructure to Support MAM and Workflows – Run in AWS Cloud (+ security) – Minor Local Storage for QC Jobs – Networking to connect points (HW and Service) – Expand Aspera to Budapest and Madrid – Expand infrastructure in Budapest for VOD/Vamos Build out of Technical QC Area Key Systems Integration – JBOSS Integration technology – Systems Integration: GPMS, EAGL, Vision UK, Vision CE, and Broadcast Master MADRID Insourced Content Prep – Insourced Ingest & QC Staff – Redesigned Workflows IT Support 8

Phase 1 scope Content ID & Metadata – In an attempt to avoid “dirty data” later in the project, records should include the GPMS ID to allow clean-up of records as improvements are incorporated. Schedule Ingest from Vision/Provys – The solution needs to be able to import a schedule from the different business systems to trigger the start of workflows and begin record creation. Status Tracking – The solution needs a way for users to see the status of content flows, queuing, and prioritization of workflows and tasks. Ingest (file based) – The solution will allow users to choose an asset file and attach it to a record based on titles needed for the schedule. Storage/Library – The solution will require an upgrade to the existing Edit Storage repository to hold the additional ingested programs. QC Process – The solution will provide for the file-based QC of inbound files and reporting on status of all passed or failed assets. Conform/Compliance – The solution will provide the interfaces to allow assets to be handed off to editing systems to allow for editing for conforming and/or compliance issues. Transcode – The solution will include basic transcoding capability for making alternate renditions of the core assets to meet various needs. Notifications – The solution will provide a notification system to alert users to events requiring intervention Distribution to Playout – The solution will provide an automated method to get finalized broadcast versions to the playout center for airing. Integration with Aspera – The solution will integrate with existing Aspera environment within Sony Pictures Entertainment. Infrastructure & Infrastructure Constraints – The first phase of the MediaCentre Project will have a few constraints, based on current research, not all of the needed infrastructure for the final MediaCentre system will be ready in the short term.

High Level Timeline 10 1-Jan-14 Long Term File archive solution operational Phase One Requirements 1-Apr-14 Automated delivery to playout GPMS/MDM integration to Provys and Vision Integration Layer Live Long term QC Edit/Content Prep operational Madrid Archive to EAGL and BCM Integration Workflow Enhancements 1 1-Jun-14 Harris Enhancements to Vision for Content Heirarchy Vision live two way integration (Retire Provys) Workflow Enhancements 2 Full VOD Delivery operational EAGL/DMR integration (Images for VOD) 1-Sep-14 Budapest Integration into GPMS Mardid Working Inventory Available in MAM Workflow Enhancements 3 1-Nov-14 GPMS/MDM BI directional feed from MAM Long Term File archive solution operational Tape Ingest and Base Band Video Essentials Workflow Enhancements 4 Full ingest/transcoding system operational 15-Feb-15 Budapest to Use Selected MediaCentre Services

High Level Program Organization DRAFT TV DCIO - TBD Bob Billeci – Program Sponsor Program Delivery Executive AWS / Vidispine Vendor PM, BMS, Aspera Local Build Scheduler BMS Functional Lead (Ian) Infrastructure PM (Paul) MediaCentre Technical Architect ADAM Moore MediaCentre Functional Arch (Andy) Integration / Metadata Functional Architect (Kelly) Software Technical Arch - Arif Operational Executive Sponsor – Mark Gleeson Change - Chris Roudette (Tech Ops) Finance (Sukhi/Jodi) SPE Tech (SME) Systems Architecture SME – Ryan Kido Tatsu Infrastructure Architecture – SME – Glen Marzan RCIO (IT) QA Lead

Team Culture Innovative Open Passion Committed Considerate Honest Yah Ground Breaking Awesome Fun Pragmatic Cutting Edge Accountable

Chris / Mark and Project Culture Learning as a part of the project Positive engagement and energy Feeling of ownership Sense of fun and “joy” Capitalize on expertise (technical and user) High level of user engagement from the beginning… (not necessarily time) High Trust Respectful Listening Alignment (and focus to) to Mission and Vision of Networks – What is it? Why is this important? Why are we doing it? Context of the project is well communicated and understood Teamwork – working as a team Empowerment

Team Set-up and Culture Smaller Pots of Money Information Sharing (Documents Saved) Deliverables Focused “Team Culture” – See Eric’s expectations but work out as team Plan as a team Get the tools in place – Service now – QC – Project management – PPM – Documents Collaboration Delegation & Empowerment

Next Steps Questions? Other next steps? Complete Next steps Talk to Jessica about Traffic staffing – Follow-up with Johnny on traffic HC assumptions

Next Steps