1. Click to edit master header title style
26/06/2014
Is DAM Dead…?
(If so, what’s next?)

2. Welcome
Agenda
• Thoughts on the future of DAM (or MAM)
• What is it?
• What’s next?
• What Vubiquity are doing at the forefront?
• Breakfast
• Open forum – what do you think?

3. First Some Bad News

4. We will be talking
Technology.
But don’t switch off!

5. Some Good News

6. This isn’t another Netflix
case study

7. What Did DAM Mean 10 Years Ago?
“maintaining
control and
access to your
digital assets”

8. What is DAM Today…?
1. Ingest
2. Secure (ACL)
3. Store
4. Render / Transform
5. Enrich
6. Relate
7. Process
8. Find / Search
9. Preview
10. Publish… and on….
“All things to
all people”
“Everything
and nothing”

9. What Does DAM “Look” Like?
“We need a
new MAM!”

10. Some Common Characteristics
• Monolithic
• On-Premise
• Silo’d or partially closed
• Hefty integration project
• Risky implementation – prone to failure (68%!)
• Workflow is a different consideration
• One size fits all – UI compromise across roles

11. What’s Breaking DAM?
Consumer
Technology
Media
Markets

12. So if “DAM” is Dying…
What’s Next…?

13. …And Can New Technology Help?

14. New Technology to the Rescue
1. Infrastructure as a Service
2. New UI Tech. HTML5, REST and JSON
3. Consumerization of IT
4. Mobile
5. Microservices

15. 1. IaaS and PaaS
• Economies of scale
• Millions of servers
• Near immediate access
• Variable cost
• Moving up the stack to
application management

16. 2. New UI - HTML5, REST and JSON
• Beautiful, event-driven user interfaces
• Responsive design
• Mobile-ready or mobile-first
• Rapid development – powerful, simple libraries
• Customer driven, role-based UI
+ +

17. 3. Consumerization of IT
• BYOD – from personal to enterprise
• Shadow IT
• Procuring own services
• Massive innovation on the consumer side
• Embracing cloud platforms

18. 4. Mobile
• Devices are very performant
• A move towards apps and discrete
functionality
• Many practical applications in media – R&A,
logging, simple editing

19. 5. Software as Microservices
Software is being built
differently in the cloud
than on-premise.
The new approach is based
On “microservices”.
Goodbye single server!

20. 5. Software as Microservices
• Opposite of monolithic (not all things to all people)
• Independently deployable services
• Faster development and roll-out
• Plays to strengths of cloud
• Service per business capability
• Decoupling with messaging

21. 5. Software as Microservices
Assets
NLE
Workflow
Scheduling

22. A New Approach to Media
Management…

23. An End-to-End “MLP” Architecture
• Service Approach
• Looser coupling
• Economies of scale
• Increased visibility
• Faster change

24. Finally…

25. Conclusions
1. New technology offers a new start for DAM
2. New ways of working mean we need one!
3. DAM isn’t dead – it’s evolving to something new
4. Workflow is more important than DAM
5. Not every vendor will make the leap to cloud
6. Technology started it, economics will drive it
7. It’s about “media logistics” now - not DAM

26. Who is pushing this forward…?

27. 26/06/2014

28. This Sounds Great!
(What’s the Bad News?)

29. Barriers for M&E?
• Moving heavy assets in and out of the cloud
• Cost of processing and storing in the cloud
• Perceived loss of control (security)
• Service levels / Service outage
• Lack of suitable software – “islands”
• A brand new architecture – expensive to make the leap
• Skills shortage

30. The Good News…

31. Enablers for M&E?
• Standards – AMWA, DPP, etc…
• Easier to justify OPEX and cost savings
• IaaS is maturing in media and entertainment
• Procurement is catching up
• Consumer IT is breaking through
• There are high-profile M&E success stories…

32. A little bit about Netflix