The document discusses the evolution of media asset management (MAM) systems, from early generations that centralized assets and supported basic tasks to newer generations that utilize microservices, APIs, HTML5 technology, and cloud computing to provide more open, flexible and scalable platforms for managing and distributing digital media across organizations. It also predicts that future MAM systems may act more like utilities in the cloud and further integrate disparate media functions into unified platforms.

1. The Next Generation
MAM Systems
Ximena Araneda

2. Ximena Araneda
EVP Video Workflows at Vizrt
Based in Stockholm Sweden
More than 12 years experience with Media
Asset Management
Worked as Developer, Solution Architect,
Operations Manager, Sales in Americas and
Sweden

3. Before we start with the journey….
What is a MAM?

5. Why so many difference answers?
Everyone has different needs from a MAM.
It will always depend on who you ask.

6. The Original Needs - Digitalization
• More people should access content in a secure way
• Preserve the valuable archive content

7. So how do we get from here…
Essence Metadata

8. To here.. ?
Essence Metadata

9. The META Project at Swedish Television
Started at 1999…

10. Early Generation MAM – We needed more
• Having all assets in the same system now required us to
grow functionality.
• Proxy editing with MPEG-1
• Connect other systems such as Ingest, Editing, Playout
and more.
• HD Support

11. In the beginning there was nothing….

12. And then there was a MAM Big Bang

14. More tools & features

15. Viz Video Engine
Omneon Spectrum/MediaDeck
Seachange
Imagine Nexio
Grassvalley K2
Baton QC
Cerify
IBM Aspera
Manager + Agents
Unlimi-Tech
FileCatalyst
Promedia Carbon
Vantage
FlipFactory
Media Composer
Newscutter
Premiere Pro Anywhere
Final Cut Pro 7 and X
Data Direct Network (DDN)
GPFS
StorNext
EMC Isilon
Netapp
Hitachi
Harmonic Mediagrid
Tivoli Storage Manager (TSM)
DIVA
Stornext HSM
FTP
Flashnet
Spectralogic
ENPS
iNews
IBMS
Schedudle All
ADC-100
Etere
Pebble Beach
SeaChange
K2
Imagine Nexio
Media/Omneon
Viz Video Engine
DB2
Oracle
Nagios
Active Directory
Dialogue Search
After Effects
Avid
EVS
More integrations

16. All of it in the same box.

17. And inside the box?
Monolithic Traditional SOA

18. How did you buy this box …

19. How did you buy this box …
• MAM sized and planned
for at least 3-5 years
(guessed growth)
• It is/was better to buy
more just in case
• Scalability becomes
extremely important

20. Communication - they key to successful projects

21. Summary.. And what did we learn
• Start smaller with simpler features and grow from there
• Productize more
• QA more
• Divide the workflows and business logic with media handling
• Simplify and don’t over engineer integrations
• Avoid to unique customizations – that are owned by the vendor

22. Summary.. Early generation MAM
• Central system to handle assets
• Mainly designed for News, Sports and Program Production
• Proxy tools (MPEG-1, H264) for preview, log and edit
• Most tools are desktop client – not using web technology as much
• Simpler task managements
• Usually handle one (SD) and one (HD) house format

23. Ok, Let’s talk about the Future!!!

24. So, what is changing?
The consumption of video is changing,
it’s growing, it’s more mobile
and it’s on-demand!
The technology is exploding
with new tools, Big Data,
Cloud technology, HTML5 and Codecs

25. So new changes require updated MAM
The 2nd generation MAM
• Move to platform view
• Open API – Restful API to enable rapid development
• Use of stable HTML5 web technology
• Google like search & remote access
• Fully integrated with online departments
• Cloud technologies (start)
• Use standards like: DPP, FIMS, IMF

26. Move out workflow engine
ESB
NLE
User Tasks &
Work Lists Workflow Engine
SDI & IP Ingest
QC
File Import
Tape
Library
Central
LR+HR
MAM
(Connect via API)
Traffic
Transcoders
File Imports
Online
Media
Business
Online

27. Tasks
Snaptasks
OR
Task types

28. Decouple and aim for micro services
Monolithic Traditional SOA Microservices

29. Search Transfer Audits
Web studio Database Metadata
Conform Ingest Transcoder
ARDOME (previous version of Viz One)
SOAP APIs
Example of 1st Generation MAM

30. Search Transfer
Web studio Database
2nd generation - Modular services with APIs
Transcoder
Rest API
Search
Web Studio
Conform
Transfer Audits
Database Metadata
File
Manager

31. Easier search

32. Optional Advanced search

33. Search Facets

34. Video Player

35. HTML5 - Responsive design

36. HTML5

37. Cloud technologies
Some MAMs can fully run on
cloud, but are they using the full
power of a cloud?
But with that said, we do use it for
archive and collaboration.

38. Summary: The 2nd generation MAM
• It’s a platform
• It has Open API – Restful API to enable rapid development
• Don’t reinvent what web technology can provide us - HTML5 web technology
• Simple Google like search & remote access
• “Online first” productions
• Cloud technologies (start)
• Use standards like: DPP, FIMS, IMF

39. Ok, what is happening now?

40. What might happen in the future?
• Media services will be utilities you buy to your media factory -> use cloud
computing in its full
• Machine vs Human – what will do what?
• Everything is accessed from anywhere – from a simple tool hiding ALL
complexity behind. Systems must be truly federated.
• Functional collapse – will there be a MAM DAM PAM or just a “media factory”?
• Even more fancy reports, monitoring and analytics!

41. Media services – pay for what you use