Ooyala is now part of Dalet, the global leader in media workflows!
The Cloud changes everything else in broadcast and since most MAMs are not cloud-native, will cloud kill MAM as we know it? Kevin Savina, director of product strategy, Dalet answered all your questions.
Organizations using Media Asset Management (MAM) to increase their financial bottom line usually do so by reducing costs, increasing revenues or a combination of both. The big question is: how do we measure that? As you know, big questions often come with multiple answers... In this case, the main issue is that measuring the Return on Investment (ROI) of the implementation of a new MAM solution is not an easy task, because there is no baseline to measure it against.
At Dalet, we believe the value can be measured. First let’s define what we mean by MAM. Dalet define it as the platform that helps with the management of an organization’s media assets, cataloging assets for search, browse and retrieval. When properly used, the MAM should be the primary access point for ingress, access and egress for media in the organization. The productivity boost from a properly designed catalog is the ability to find things when you need them and retrieve them for use as quickly as possible.
The second key aspect of a modern MAM platform is the ability to orchestrate workflows to create value from these assets. MAMs that offer ‘If This, Then That’ (IFTTT) type of policies enable organizations to automate and keep tabs on all kinds of processes, including ingest operations, review & approvals, transcoding, automated QC and media distribution. Even at the basic IFTTT level, the ability to have a system route media within the organization has the value of eliminating wasted time (tasks no longer sit for a human resource to trigger or operate them), as well as providing limited reporting on proper completion. A well-designed MAM system with IFTTT policies will be able to report on the processes that were started and completed by this policy control.
We can see the value brought by these platforms from two angles:
Dalet customers who have implemented MAM systems have been able to substantially increase their productivity by a factorx4 to x6, and expand their content distribution by a factorx8 to x11.
From our point of view, the fact that a MAM project delivers on its promises is based on a combination of factors:
- On the end-user side:
- On the vendor side:
The issue isn’t so much whether MAM has delivered on its promises, but whether or not specific vendor promises of what a MAM is actually capable of, beyond the catalog, were fulfilled. There are numerous examples of vendors that have over-promised MAM capabilities for the ability to integrate with external metadata sources, interoperate with third-party systems, handle specific media formats and data models, or manage specific workflows.
The Cloud implies multiple things at once:
Media customers are choosing to utilize some or all of these items as they implement a ‘cloud’ workflow. In some cases, they want media transformation and distribution to run as close to the edge as possible, thus lowering their costs of distribution. In other cases, we’re seeing entire pre-production workflows operate in the cloud in order to provide elastic costs to match job order billing.
Cloud changes things in the sense that it adds a whole new level of flexibility to MAM deployments. Things that used to be fixed and constrained can now be used as needed. For example, cloud allows for:
Just as there is no one definition of ‘cloud’ there is no one ‘cloud’ implementation or business model that is right for every customer. Vendors should be prepared to talk about each of the items the ‘cloud’ makes possible and discuss how their solution can fit within the customer needs.
Point 1 impact is that MAM solutions need to support this new type of infrastructure. This is a new generation of infrastructure. The broadcast industry started with proprietary, ad-hoc hardware, then moved to off-the-shelf IT systems (servers, storage). Cloud is a similar change.
Point 2 is the real game changer as it has real operational and business impacts. The core of MAM products is not impacted by such change. Assets will continue to be referenced in a system and tools will still be required to process the content. What is impacted is the eco-system around the MAM, which can now become much more dynamic. A MAM should be able to leverage cloud services so that users can benefit from the cloud through the MAM. And there again orchestration will be a key component, giving the ability to provision, control and monitor the various services available.
The ability to successfully virtualize a MAM in the cloud obviously depends on how you measure success. We see success as customer-driven, not vendor-driven. If a customer wants to migrate their existing workflows and software licenses to an external datacenter for the purposes of offloading hardware management and gaining simpler, high availability / disaster recovery scenarios, virtualizing the existing MAM would be 100% appropriate. Some of our customers have been fully virtualizing their MAM solution for years and consider the project a success.
Of course, simply virtualizing your existing MAM infrastructure and hosting it in a cloud environment (public or private) doesn’t gain the other cloud benefits of elastic business rules and elastic costs. To truly enable these items, MAM and workflow orchestration systems built around them should be architected to enable individual processes to be created and deployed as business needs require them, which requires that vendors have knowledge of the cloud platform the customer has chosen in order to properly create either a virtual machine instance or virtual container host, clone the proper process, start the machine/container, start the process and connect it to the central system (and of course, the opposite, when the business need expires).
Like anything in a software organization, you start by listening to your customer’s needs, and then you build the pieces necessary to fulfill those needs. Controlling costs in software builds is a matter of two things:
MAM catalogs are an essential part of media operations, and they are not disappearing. Media organizations will always need to be able to search, browse and retrieve their media assets, retaining metadata from the interaction with external systems, and enabling workflow orchestration on top of those media-aware data models.
Tapping into the deep, multi-layered data model of MAM platforms such as Dalet Galaxy, internal or external reporting and analytics tools allow users to analyze vast amounts of data and offer Business Intelligence (BI) specifically tailored for media operations in order to measure performance throughout the chain and build sound data-driven strategies. This is one of the keys to growth for media organizations who greatly benefit from the agility and accessibility of the Cloud.
Smart vendors see the cloud as an enabler of new business models, providing customers what they want, when they want it. MAM needs to move from a solution to a smooth part of a business workflow. For a MAM to be future-proof, it must enable more and more workflows around it, provide a high level of agility, and last but not least, be easy to integrate.
Cloud is not a destroyer of worlds, it is a creator of them.
Thanks to The Broadcast Bridge for the interview of Kevin Savina.
Read the full interview here: