1. DATA MANAGEMENT CONTENT ORGANIZATION AND MEDIA IDENTIFICATION John Doe Executive Vice President Digital Division

2. Objectives Setting the Stage (Handout) – Numbering (Smart / dumb) – Master Data / Data – Basic Definitions for Title, Program, Version, Alpha, Metadata, Identification between systems design principles – Inter system – Across the Enterprise – Across multiple Enterprises Ccontent organization approaches (What’s working, what are the opportunities) – GOAL: Get on the same page – Review current approaches (Page 1 – screenshots and words, page 2 hierarchy picture  Spain  Budapest  UK  Digital Backbone / SPE Distribution  LATAM  EIDR – What definitions need to be worked out? What of that needs to be sorted out before the project starts – What do we want our practices to be:  What are the strengths and weaknesses of each approach?  What questions were raised on Wednesday data movement that we need to address?  What are the design constraints related to these (ie broadcast system requires a smart number ?  What design principles would we want to leverage from what we are doing?  What IDs (Data) should be referenced across the enterprise or between enterprises? For enterprise or inter enterprise, how should re register or issue ide?  Will this approach work for our digital distribution models (VOD/OTT)? If not, what needs to be considered  What needs more discussion and needs to be sorted out before GL – What are the gaps from where we want to be to where we are today? Master Data Opportunities Metadata and VOD/OTT – What additional metadata requirements do we need to plan for with VOD and OTT? (Leverage Spencer and Jocson and previous day comments) What Systems and Dataflows are in plan and what additional analysis do we need to complete to lock down scope? Decide what content

3. Outputs Homework or Decisions on – Content organization approach – Indentifiers used (Internal / External) – Masterdata in Scope – Source Systems Design Principles

4. Questions What needs to be identified? Versions How do we want to organize our content? What does a reference architecture look like? What issues or opportunities What are our master data opportunities? Design Principles What should be centrally registered versus locally registered? What is the implication on Data Migration OTT / VOD needs versus Broadcast Needs

5. Identify Areas of Content Organization Titles (Programs) Versions Alphas Inventory – Core Media – Source – from distributor – Supporting Materials (Eagle) – Promotions – Physical Sources – Deliverables – Transmission Copy Other?

6. Defining Version What is the current definition of version? How does it relate to what we define as an alpha? Review examples

7. Content Organization: Definitions Title/ProgramTitle is the master data describing the intellectual property, which is maintained as the highest level of organization for its content. AlphaAlpha is a unique picture/audio/content cut of a Title (See 'Title') created for business, territory, S&P, etc. It can loosely be thought of as a "version". In regards to fulfillment, it is the secondary level of organizational data used with a Title (See 'Title') in order to drive what end Product needs to be manufactured. (Title > Alpha > Component) Version Master Data MetadataMetadata is the data that describes other data. Metadata Specifications The Metadata Specification defines the information required to generate a Metadata File for a specific customer or client Technical Metadata Technical Metadata represents the data values that are captured for specific ingested or deliverable assets (i.e. frame rate, bitrate, aspect ratio, codec, audio configuration, file format) ComponentA Component is the building block for the creation of a 'Product', e.g. video, audio, subtitle, chapters, etc. A Component is the discrete audio, video, text and/or combined Assets (See 'Asset') that are associated with a Component Type, stored as raw materials for Automated Content Processing. Components are Title (See 'Title') and Alpha (See 'Alpha') specific. A Component can be used in one or many deliverables (applies to both digital and physical media).

8. Content Organization: Definitions AssetAsset is meant to convey the broad scope of physical or digital elements maintained and tracked as a unit within any asset management system. Asset metadata uniquely describes the characteristics of the asset and must be permanently connected to the essence whether in a physical or digital asset management system. Whether an asset contains multiple parts, e.g. 5.1 Audio, or whether each part is maintained as an asset is subject to the specific protocol of the managing system. With regard to the more formal term, Component (See Components); an asset, once verified and matched to Component Type specification, becomes a component. All Components are assets, not all assets are components.

9. Content Org Approaches: :LATAM Program record created representing a season. No series level record seems to exist Season Identified by ‘ID’ field Contains full list of episodes which exist season Materials for Transmission Associated directly to the TX id/Barcode on the alpha Content reference id from episode is referenced for each segment Program record created representing an episode. Episode record Identified by ‘Content Reference’ ID Contains full list of alphas for episode. Each alpha contains distinct ‘Transmission ID’ which is the same as the barcode

10. Content Org Approach: LATAM Program: Beveriy Hills 90210 – Season 3 ID: 1111046 Episode: Mystery Loves Company Content Ref ID: 24633 Version A: LAT Barcode: X194636 Materials – Segment 1 Barcode X194636 Content Ref ID: 24633 Materials – Segment 2 Barcode X194636 Content Ref ID: 24633 Materials – Segment 3 Barcode X194636 Content Ref ID: 24633 Version B: BRA Episode: Home and Away Version A: LATVersion B: BRA

11. Title : Alpha : Component Structure Title is the highest organizing level of SPE ’ s intellectual property Alpha can be thought of as a version or a unique cut of a title Component is an asset approved to fulfill a specific title alpha FEATURES

12. Title/Alpha/Component Structure Client Specification Transformers Unrated 169FFHDOM 43FFNTSCOM 5.1 LAS 5.1 Eng CC Eng

13. Content Organization: High Level Program Version Inventory (Assets) Version Inventory (Assets)

14. Content Organization: Example - 1 Breaking Bad Version: HD HD SourceSubs Version: SD SD SourceSubs

15. Content Organization: Example - 2 Breaking Bad Version: Dom SourceSubs Version: Compliance Edit SourceSubs

16. Content Organization: Example - 3 Breaking Bad Version: Localized - Spanish SourceSpanish Subs Version: Localized - French SourceFrench Subs

17. Content Organization: Example - 4 Breaking Bad Version: Base HD SourceSD SourceSubs Version: Int HD Source French Subs Spanish Subs German Subs

18. What Level of Content Organization exists in Business Systems Harris Systems (Broadcast Master, Harris, Landmark) GPMS Eagle Cineshare Media Center (CWM)

19. Internal and External Identifiers AreaIdentifiers ProgramTransmission ID, SPTN House Number, GPMS ID VersionVersion ID Alpha Inventory (Assets)Barcode

20. Content Registration Internal Product Identification – What internal identifiers are used within the existing business systems – Which identifiers are hardwired into existing business processes and automation External Product Identification – Registration to external organization (i.e. EIDR, ISAN)

21. Master Data Opportunities Where can we nourish existing content

22. Metadata surrounding hierarchy AreaType ProgramGeneral Title Attributes, Program Identifiers, Localized Metadata (i.e. Synopsis, Titles, Genres, Copyrights, Ratings), Client Specific Identifiers, Rights, Transmission information? VersionGeneral Version Attributes, Alpha Identifiers, Localized, Rights, Transmission information? Inventory (Assets)Asset Identifiers, Technical Metadata (i.e. Aspect ratio, format, framerate), QC, Ingest related (encode facility, ingest date, source id), DeliverablesTechnical Metadata, Title and Version metadata, Client Specific, Rights Detail, Package Details, content status?

23. Metadata related to Linear, Non Linear, OTT

24. Non-linear metadata Program Asset s Version/Alpha Rights

25. Metadata for VOT/OTT

26. Data Movement –Originated vs. Interfaced

27. Open Questions What will be the source system for setting up in the initial program? What level of content organization do we need within each business system in order to complete end-to-end process from program set up, delivery to play-out? Do we need standardized rules for defining versions for consistent inventory? How do we deal with promotions and supporting materials in the content hierarchy? What are the areas of data that will need to be interchanges across systems and at what point in the cycle are they needed? Metadata for content exports out of CWM – do we need to source this information from GPMS? Or are we storing and editing internally at the MC Where does schedule fit in the content oganization?

28. Data Migration What data can be migrated immediately? Implications of data migration Long term data migration goals

29. Homework Check connections to the RFP Kelly to connect to RFP via YouSendIt Kelly to see Vision

30. Wrap-up and Review

31. Question 1 -Question 2 - Question 3 - Question 4 -