Media Inventory Management...Inventory Management Data Automation Playlists Data File Management...

Preview:

Citation preview

Media Inventory Management

byAnthony DuBoyce, P.Eng

IMMAD ECVS Systems Integration

Introduction

n Media Asset Managementn A ‘fault tolerant’ broadcast architecturen The levels of Media Asset Managementn Levels of Metadatan The role and Critical Interfaces Media

Inventory Managementn Conclusion

The Redundant Server Principle

HUB

HUB

HUB

RECOVERY MODEFLOW

ON AIR

ON AIR

PROTECT

PROTECT

NETWORK1

NETWORK2

HUB

Fault Tolerant Program Integration

Main

Back-up

Back-up

SERVER 1

SERVER 2

AUTOMATION

PROGRAMFILL

PROGRAMFILL

PROGRAMFILL

PROGRAMFILL

Network1

Network2

AUTOMATION

Main

SystemNode

SERVER 1

SERVER 1

SERVER 2

Program Stream

Integration

Program Stream

Integration

HUB

Main

Back-up

Back-up

SERVER 1

SERVER 2

AUTOMATION

PROGRAMFILL

PROGRAMFILL

PROGRAMFILL

PROGRAMFILL

Network3

Network4

AUTOMATION

Main

SystemNode

SERVER 3

SERVER 1

SERVER 4

Program Stream

Integration

Program Stream

Integration

HUB

Fault Tolerant Broadcast Infrastructure

System

Node

DATA ROBOT

SystemNode

DATA ROBOT

SystemNode

AUTOMATION

SERVER C

SystemNode

AUTOMATION

SERVER B

SystemNode

AUTOMATION

SERVER A

FILE TRANSFER NETWORK

SystemNode

Disk arrayDisk array

Disk arrayDisk array

RAIDCache

Main

Back-up

Back-up

SERVER 1

SERVER 2

AUTOMATION

PROGRAM

FILL

PROGRAMFILL

PROGRAMFILL

PROGRAMFILL

Network1

Network2

AUTOMATION

Main

SystemNode

SERVER 1

SERVER 1

SERVER 2

Program Stream

Integration

Program Stream

Integration

HUB

Fault Tolerant Broadcast Infrastructure

n System ‘Node’ approach protects against system-wide failure

n High levels of redundancy and local storage in critical air chain

n Extended cache storage reduces wear on data drives and robotic hardware

n Robotic storage provides system back-up in the event of catastrophic cache failure

Fault Tolerant Broadcast Infrastructure

n Requires a system-wide Inventory Manager to implement– instances of a program segment may exist in a

variety of disparate locations - ingest servers, central cache, robotic archive (data tape and DVD-RAM), redundant airplay servers

– different treatment of long-form and short-form program requires a high-level director, programmed according to work-flow methodology and system configuration

High Level System Model

Data

CentralCache

ArchiveStorage Video

Audio

VideoAudio

File Management

LocalStorag

eVideoAudio

LocalStorag

eVideoAudio

LocalStorag

eVideoAudioLocal

Cache VideoAudio

Playout System

Data

AutomationPlaylistsIngest

Encoding

Data

VideoAudio

Data

VideoAudio

Data

VideoAudio

Data

VideoAudio

INGEST STORAGE EMISSION

Data

Traffic

Data

Sales/Operations

Data

Data

Data

Captioning

CG/SStore

Bugs

Elements V Chip ratingsDownstream CuesEnhanced DataProgram GuideDTV Transport Muxetc.

ProductionVideoAudio

File Management

n Routes incoming program files to cache, archive or both

n Controls generation of archive safety copies n ‘Broadcasts’ program files to air servers

from cache or archiven Optimizes robotic and data drive usagen ‘Purges’ cached files upon command

Sales/Operations Needs

Data

CentralCache

ArchiveStorage Video

Audio

VideoAudio

File Management

LocalStorag

eVideoAudio

LocalStorag

eVideoAudio

LocalStorag

eVideoAudioLocal

Cache VideoAudio

Playout System

Data

AutomationPlaylistsIngest

Encoding

Data

VideoAudio

Data

VideoAudio

Data

VideoAudio

Data

VideoAudio

INGEST STORAGE EMISSION

Data

Traffic

Data

Sales/Operations

Data

Data

Data

Captioning

CG/SStore

Bugs

ElementsProgram content informationRun lengthsRatingsContributing Elements

ProductionVideoAudio

Data Data Data

Content Management

Annotation Retrieval Keyframes/Browse

Content Management

n Controls collection and storage of annotation data

n Provides sophisticated database query tools - content retrieval from keywords, keyframes, browse

n Primarily a sales and operations tool for management of product throughput

Broadcast System Management

Data

CentralCache

ArchiveStorage Video

Audio

VideoAudio

File Management

LocalStorag

eVideoAudio

LocalStorag

eVideoAudio

LocalStorag

eVideoAudioLocal

Cache VideoAudio

Playout System

Data

AutomationPlaylistsIngest

Encoding

Data

VideoAudio

Data

VideoAudio

Data

VideoAudio

Data

VideoAudio

INGEST STORAGE EMISSION

Data

Traffic

Data

Sales/Operations

Data

Data

Data

Captioning

CG/SStore

Bugs

Elements

Data Data Data

Content Management

Annotation Retrieval Keyframes/Browse

Missing Lists

Purge Routines, File Routing

Cache Pre-loadIngest

Control

ProductionVideoAudio

Data

Inventory Management

Inventory Management

n Generates and tracks progress of Ingest lists n Dictates destination of ingest files - to

cache, archive or air server n Responds to playlist requests for material -

controls ‘push’ of material to air serversn Receives advance notice of required

material to ‘pre-load’ cache

"Media Asset Management"

Media Asset Management

Data

CentralCache

ArchiveStorage Video

Audio

VideoAudio

File Management

LocalStorag

eVideoAudio

LocalStorag

eVideoAudio

LocalStorag

eVideoAudioLocal

Cache VideoAudio

Playout System

Data

AutomationPlaylistsIngest

Encoding

Data

VideoAudio

Data

VideoAudio

Data

VideoAudio

Data

VideoAudio

INGEST STORAGE EMISSION

Data

Traffic

Data

Sales/Operations

Data

Data

Data

Captioning

CG/SStore

Bugs

Elements

Data Data Data

Content Management

Annotation Retrieval Keyframes/Browse

Data

Inventory Management

ProductionVideoAudio

Media Asset Management

n Is used to describe:n File Management

– Control and routing of files within networked storage

n Inventory Management– Control and routing of program elements within

broadcast system

n Content Management– Annotation and content retrieval of program

assets

Why Discrete Layers of Media Asset Management ?

n Assists definition of software elements during system specification

n Is compatible with the fault tolerant ‘system node’ architecture

n Enables vendor specialization, resulting in ‘best - in - class’ system performance

n Is compatible with current Metadata definitions

Metadata

n Essential Metadata– Unique Material ID (UMID), travels with the

program file: resides in all MAM databases

n Technical Metadata– Description of program format and related

elements: resides in Inventory and Content databases

n Content Metadata– Description of program content: resides in

Content databases only

"Media Asset Management"

Metadata Layers

Data

CentralCache

ArchiveStorage Video

Audio

VideoAudio

File Management

LocalStorag

eVideoAudio

LocalStorag

eVideoAudio

LocalStorag

eVideoAudioLocal

Cache VideoAudio

Playout System

Data

AutomationPlaylistsIngest

Encoding

Data

VideoAudio

Data

VideoAudio

Data

VideoAudio

Data

VideoAudio

Data

Traffic

Data

Sales/Operations

Data

Data

Data

Captioning

CG/SStore

Bugs

Elements

Data Data Data

Content Management

Annotation Retrieval Keyframes/Browse

Data

Inventory Management

EssentialMetadata

EssentialMetadata

TechnicalMetadata

ContentMetadata

Technical,EssentialMetadata

ProductionVideoAudio

Inventory Management Interfaces

Data

Inventory Management

Data

AutomationPlaylists

Data

File Management

Data

IngestAutomation

Data

Sales/Operations

To service a variety of automation vendors,a generic software interface (SDK) must beavailable from the Inventory Manager. Generation of a Missing Materials List is aprerequisite of the automation system.Specification of interface is the role of the System Integrator

Comprehensive API required for integratedoperation. Common element is the UMIDInventory Manager dictates storage locationof file, (ie cache, archive or both) and generatespurge list

The interface to Sales/Operations enablesthe look ahead function to pre-load thecentral cache. A flat-file from the salesOperations database in a pre-defined formatis sufficient. A common UMID is a prerequisite of this interface

Comprehensive API required for integrated operation. Common element is the UMID. Inventory Manager queries Ingest database for UMID, and instructsFile Manager to ‘pull’ program into storage. Inventory Manager generatesIngest list to Ingest automation

Data

AutomationPlaylists

Data

File Management

Data

IngestAutomation

Data

Sales/Operations

Where can I buy an Inventory Manager?

n This function can be performed (with varying degrees of success) by:– Single vendor system solutions

Data

Inventory Management

Where can I buy an Inventory Manager?

n This function can be performed (with varying degrees of success) by:– Content Management vendors

Data

AutomationPlaylists

Data

File Management

Data

IngestAutomation

Data

Sales/Operations

Data

Inventory Management

Where can I buy an Inventory Manager?

n This function can be performed (with varying degrees of success) by:– Automation vendors

Data

AutomationPlaylists

Data

File Management

Data

IngestAutomation

Data

Sales/Operations

Data

Inventory Management

Conclusions

n Specifying a discrete ‘Inventory Manager’ system layer or module offers the following advantages:– allows continued use of legacy automation

systems– aids system functional specification– allows other system modules to perform within

their respective areas of expertise – potentially improves system modularity and

fault tolerance– allows selection of ‘best- in- class’ software

and hardware components

Conclusions

n Defining the ‘Inventory Manager’ as a discrete system layer or module has the following caveats:– requires ‘turnkey’ software systems integration– requires exact definition of system function and

scope prior to purchase and installation

Recommended