Click here to load reader
Upload
laura-clemons
View
9
Download
0
Embed Size (px)
Citation preview
Slide 1
Date: RemovedAttendees: RemovedIntel Map Meeting
Client Goals Overview
The Digital Revolution ProposalDefine viable, scalable systems and partners for supply chain ownership, defining where Intel's core services begin and endGenerate ongoing strategic alignment with content preparation companies Allow Intel's clients to create accurate and repeatable business models based on less volatile supply chain costs.
Goals Phase 1: Pilot an E2E PipelineDR Build Content Transform & Delivery Pipeline Process Definition & Ingest Design Systems Infrastructure & Automation Staging & CDN Integration w/ Akamai Staffing for Operations Validation DR Design Standarized Metadata Procedures & ServicesIntel Implement Web Services Systems & InfrastructureIntegration & On-boarding of Content Provider, Image EntertainmentEIDR Registration & Asset Processing
Phase 1: Architectural Overview
Phase 1: Three Key Planning AreasContent Transformation & DeliveryPhase 1 DR Design/Build & Operations PipelinePhase 2 DR Scalability, Adaptive Streaming Modifications & Hand-off to IntelMetadata Transformation ServicesPhase 1 DR Build Technology & Processes, Integrating with Intel DBPhase 2 DR Additional Content Source Customer OnboardingIntel Web Services OfferingPhase 1 & 2 Intel Determine Planning & Resources for:Productized License Server, License Application and License Keys DBTitles DB /Data StoreLogical Asset Manager
6
Planning Area 1Content Transformation & Delivery
Content Transformation & Delivery Key Planning Areas Part 1Execute Content Owner Delivery ContractsScope, Test & Finalize Systems & Architecture RequirementsProcure All Phase 1 Required Systems, HW/SW & LicensesObtain & Prepare Physical Operations Site(s) & SecurityObtain & Prepare Intel Cloud with Web Services Systems (Transcode, etc.)Register Content Assets with EIDR ServicesReceive & Configure Phase 1 Ops Required Systems, Networks, Security, HW/SW & LicensesStaff & Resource Operations for PilotDefine & Configure Phase 1 Ops WorkflowsDevelopment, Integration & Testing with DR Metadata Transformation Services
Content Transformation & Delivery Key Planning Areas Part 2Development Integration & Testing with Intel Liscense Keys/Server, Logical Asset Management, Titles DBDevelopment, Integration & Testing of Archive System & DB for HD Encoded Packages Integration & Testing of CDN with Processes & PlayerPerform E2E Integration Testing & Finalize WorkflowsFinalize & Document Technical Content Formatting RequirementsDeliver Content Formatting Requirements to Content Customer BaseObtain Content Owner Approval on Production Ready Content Optimize Incoming/Outgoing Workflow ConsiderationsLaunch E2E Pilot Operations
Content Transformation & Delivery Production Model Diagram
Content Transformation & Delivery Content Transform Diagram
Content Transformation & Delivery Content Transform ModelUtilize Intels cloud infrastructure to configure and service the data center/cloud-based Digital Rapids transcode farm, to cost-effectively transcode content.
Content Transformation & Delivery Proposed Operational Resource AreasSchedulingData Management /Archive & RetrievalFile TransfersStorage Navigation & MaintenanceIngestReceiving Mezzanine Files & Associating Metadata Asset ManagementTranscode/File DuplicationCreating Output Digital Media QCVerificationPackagingContent Files Assembly Artwork Creation/ManipulationMetadata AssociationMedia Pipeline DevelopmentDevelop Automation Methods
Content Transformation & Delivery Proposed Operational Support AreasDigital Media EngineeringResearch and development of the latest applicable content transform technologiesOn-boarding & WorkflowNew workflow process creation using existing and latest technologies and techniquesProduction EngineeringSupports operational systems and software; installation/testing of new equipment, networks, software, hardware.Software DevelopmentAuthors scripts and tools to support operations
Content Transformation & Delivery Example Organizational StructureResponsible for all file to file workflowsPackaging - Responsible for all metadata, artworkData Management Responsible for all data to/from archive and file system data mgmt
Responsible for scheduling and prioritizing daily work load to ensure that all content license windows are metResponsible for all QC workflowsDigital Media OperationsTranscodingDigital Media SchedulingPackaging And MetadataDigital Media QCTranscoding OperatorsPackaging & Metadata OperatorsData Management OperatorsQC SupervisorsQC OperatorsMedia Pipeline DevelopmentPipeline and Automation DevelopmentResponsible for automation of moving media through complex workflows
Planning Area 2Metadata Transformation Services
Metadata Transformation Services Metadata Diagram 1
The Metadata/Content ID Challenge
Three Types of MetadataAvails MetadataOn-going information stream indicating newly available content from the content ownerTechnical/Asset MetadataDetailed description of the content file characteristicsTypically created by the tool that is creating the digital fileDescriptive MetadataTypically seen on a consumer facing portal or serviceCreated by content creator or their service provider
Multi-Source, Multi-DestinationEach studio has a slight variation on how they express their metadataEach distributor has a slight variation on how they express their metadataThe above combination causes a compounded problem across the entire media supply and distribution chain.
Multi-Source, Multi-Destination
Metadata Creation Lifecycle
Content Identification Lifecycle
Part 1: Correlation The Challenge Three types of metadata are created at different times and by different partiesNo standardized way to correlate all types of data for a single title or version of that title
Part 1: Correlation The Solution Enforce the use of an industry standard content identifier registry for all content being licensed and distributedMust be used for all 3 types of metadata (Avails, Asset, Descriptive)Allows for automated correlation regardless of when the data is submitted
Part 2: Ingest/Conformance The ChallengeSources of metadata are not standardized on form or vocabularyMultiple internal sources exist within each content ownerNo standardized transport methodologyNo standardized messaging protocol or choreography for trading partners to implement
Part 2: Ingest/Conformance The Solution Implement a metadata processing service busIncludes all standardized steps required to leverage the solution from part 1 and automate most metadata ingest/conformance processesAllow for manual workflow steps for all non-automatable steps
Processing Pipeline Implementation
Phase 1 Planning Timeline