Hello,this is Chuck Bullo with EMam.
And today,thank you,I want to thank you actually for allowing us to present the EMA Spectrum Re case study.
So this will go through some of the
changes that Spectrumreach made with EMA and moving
basically all of their content and editing processing up into the EMA cloud
system in AWS and then being able to manage
other uh media and projects and so on all cloud.
So,
again,
we'll go through a few slides here and then show you a couple of demonstrations as well on how that was done.
So,again,Spectrum Reach,
they are a cable company and on their,uh,the client is actually Kernel,which is internally to the Spectrum Reach company.
They actually then
do all the ads and
promos and so on within the
company and so on.So they have actually editors
that are across the country.
And also photographers that are shooting
uh media and so on.And
so the idea was to provide a system where they can do collaboration,
centralize all the types of media and so on that they have,
but mostly for them,it's uh all 32nd spots and so on,and then of course remote editors.
Or throughout the country and then of course the uh photographers as well.
So,
they wanted to standardize on Amazon,AWS and storage and processing media all from the cloud.
That was really their goal and then using the EM system to uh kind of manage all the content
uh for the check-in,checkout of media,organizational
structure of media and then of course permission levels and so on.
So we've actually
moved them into an enterprise level system.
With the EMM system and then of course meeting all of the challenges that Charter has and with their IT and
permission levels as well
uh that they have set uh that we need to meet on a daily basis.
The challenges that they had,again,wanting to centralize the media,media workflows and so on
with wide access to all of the editors.And producers around the country in the US and then be able to uh move
large amounts of data
across multiple locations.I mean,that was
an issue for them,mostly because they were actually saving everything on hard drives,shipping hard drives,and so on.So again,the centralization of the media
was really key for them.
All the remote edits are done
throughout the country.Um,so again,there's about 200 editors and so on that they have.And then of course,then distribution of the media to
The head-ins and cable outlets and so on that they're delivering the content to in the promos,
ad spots,and so on that they're doing
as well.And then,of course,keeping it very efficient,um,and secure
of the media.So again,
keeping
track of where the media goes,who gets access to that media,that was really
key for them and of course,
uh collaboration across the US and,and with the folks uh in different regions
around the country.
So,the idea here again was all of the assets were ingested
and centralized into an S3 bucket.
Um,that was really key for them to be able to then
process the media,upload the content,store it in the uh AWS S3 bucket storage,
also use Glacier for archive
management as well,
putting away assets that they're not using and so on.
Again,all the assets went to S3 files were then transferred
from the camera.First off,this is kind of how the process works.So they
have the cameras,they uh transfer all the media to laptop or desktop in a remote location,and then from there,there are processes that they can use within the MAM system
to be able to upload that content.
Now,we also utilize the features of AWS and some of the transcoding processing that they can do for us,
create in mezzanine copies for offline edits.
Using also H264 proxy for viewing
and preview uh within the EMA system
and then of course with the elemental media convert,that's where they're doing all of the process for transcoding.
So,the upload process for them is quite simple,where
they're just dragging and dropping the content into a window here.
We also have an application called Feeder
where they can actually download that and use that locally.
When they're adding files or folders,it's quite simple.
Being able to go in,
uh,look for the different content that they have,
you know,with a simple video and so on.
They can also upload
different folder structure as well and then we actually bring that in as
media that's um
uh in categories,what we call categories.
So,the idea here is that they'll have profiles that make it quite simple for uploading to very specific locations and so on.
They can assign it to specific projects,the media that's being uploaded.
And then of course,also different uh categories
as well.In their case,they use Adobe Premiere for editing.
Um,then they can also tag the media and make it available,
um,you know,with uh search capabilities with the media,so globally tagging the content
as it's going up as well.
And then on the category side,we'll talk about this a little bit,uh,which is the categories set permission levels,uh,to be able to then manage who gets to see what,
um,and what they get to do with the media once it's being uploaded.
Um,the content's always uploaded,
um,and,uh,there's also a dashboard
that's also given always to see what the process is,
um,how things are going,and so on on that upload.
And then,of course,we also do,uh,various things where they can edit what they've tagged as media and metadata for,for this media that's going up as well
and just simply hitting the upload button.
And so at that,at that point,the media is now being being transferred up into the estuary bucket.
Um,so that's quite how,how quite simple it is to be able to process the media and then upload that content,uh,directly to the cloud.
Um,so the other,other idea is being able to publish the content or view uh the content in various different types of platforms and so on.
We can automate this whole process,
uh,send out review and approved,uh,media,
uh,to,uh,master control,
to VOD sites,to social media,
um,just simply.
Share the content as well through a web interface.
Um,it's quite simple actually to just drag and drop media to be able to share or then go ahead and deliver or package,
uh,the content as well,
um,which is quite nice if I'm packaging media with multiple audio files,and then,of course,also,uh,caption files,graphics,bugs,lower thirds,and so on.
I can then deliver that off to,uh,different,um,
Uh,trenchcoders to be able to then process that media and then be able to share that media.
Um,this is actually customizable with us where we can actually,uh,
uh,place inside of an email,uh,email,
and then be able to uh have it as a link,and then just click on the link and it then opens up into a local browser.
Um,
also with finished assets,then we can get very
specific on the packaging,as I mentioned.
Um,and then being able to kind of share that,uh,with other platforms,um,or deliver to automation and broadcast and play out,
uh,there as well.
So,
um,on the archiving side,this is quite nice where um EMA does offer that option for estuary and glacier and tearing
of the content.So,
um,with this media,
uh,once it moves off a production,it can then be placed and put into
a,um,
Uh,into a,uh,uh,uh,
you know,uh archive,uh,tier that's much,uh,more cost effective to store the media until it's used again and then restored.
So the idea here is that you can set up different permission levels within or different tiers,
um,
to get access to the archive,
being able to then move that media.From a cost,uh,you know,
uh,uh,you know,the S3 bucket,which is a little bit more costly,
then over on to a less cost,uh,glacier,uh,location,um,and then be able to store it.But then also the proxy and the metadata are still available within the MAM system to be able to share that,uh,there as well.
Um,so,file retrieval is,um,
kind of quickly,it just depends on what layer that you are gonna be at with the uh glacier.
Um,you know,you can go to the deep archive or even some of the lower tiers,which is a little bit easier to,uh,
uh,bring back,
um,quite quickly.
Um,the other thing.Is that all the media then is secure based on um everything uh
related to uh AWS
um security levels as well that they meet
and then also,of course,our login
uh featuring,um,you know,different uh single sign-on and various things.We'll talk about that here in a second.
Uh,we also,of course,uh,store the different project files and and various things,and then of course the metadata,
metadata is really key for
um very specific information that they want to keep.Uh,we do manage that process
um with different groups of metadata,
uh,giving people either just access to view the metadata or actually change the metadata,
um,and so we can control that through permission levels as well.
So,
Um,with that,then again,on the,you know,restoring the content,it's quite easy.So you have the media,you have all the project files,you have
everything related to projects and so on,
um,and very specific,uh,UIDs to the con uh content and so on,
um,and the naming convention that's built into the MAM system to keep everything quite unique,
uh,within the system.
Um,tools available quickly to then pull back that content,
um,from the cloud,
um,onto say a,a production storage in the cloud and then be able to edit that again,
um,so we can bring back all the project files and then of course all the media that's associated with that as well.
And then dynamic relinking with proxy and restored original content as well.
Um,so we manage all of that process for the clients,
um,or the system does,um,and so on.So,
Um,quite easy to kind of manage that process there as well.
Um,we also add on to the security levels where we can actually then create
um
the different user groups,um,first off,and that's all based on,say,Active Directory or,
uh,OCTA for single sign on and so on.
Uh,but the users are actually assigned to user groups that then have permissions
and accessibility.So we actually then define.
Within the interface as an admin,um,so these are,uh,of course,
admin users setting this up,
where they're,they're setting up a user and,and a number of users into a group
and then with that group,then they apply the different settings to which categories that they can see which media
is available to them,
and then being able to then
uh access that media and process that media,
um,and then.Also different permission levels of what they can do with the media as well.
So those different levels are all set,uh,using the admin tools,um,
and we also use the category levels,uh,to actually then do life cycle management of,of media.
So if things,uh,of rights management is,is,uh,
uh,maybe a contract has ended on certain media that we have,we no longer have access to that media.
automatically then be placed in another category that nobody has access to or they only have access to say proxy with uh
uh bugs,uh,or,you know,
any kind of,uh,you know,
a bug across the video and so on,
um,that they can't use it within the,uh,a project there as well.
So,uh,very nice control,um,within the system that uh you're able to do that,uh,
uh,within the EMA system here.
Um,we've also then taken into consideration and built in for charter
and also the security levels that they can set through the uh AWS platform.
So,
lots of protection and security levels are set,
uh,within the EMAM system.Um,
so the corporate,uh,security levels from their IT department,
um,and then also for us,they also give us,
um,the ability to get into the account as well then to,
uh,kind of manage their system and help them manage the system.But,
um,the team then,um,
Uh,works together,
um,on state of the art,uh,
you know,AWS protections that they have built in,
uh,to the platform.
And so we'll utilize that with the firewalls and load balancing,
um,
you know,and,and the different configurations and security hubs that we have available through AWS and apply that to their platform.
Um,so then,of course,all of the content is secure.
The S3 buckets are secure.
Um,so really,um,nobody can really access that content unless they're going through the MAM system and through these credentials.
Um,Charter also uses a single sign-on,
um,where they're doing,
um,you know,
uh,through their,
uh,system and through AWS then they can control and manage who gets to get access to the content.
And then of course on the permission levels uh based on the user groups,then they can kind of control what uh access,uh,what media they have access to as well and what they can do
uh within there as well.
So,we do have um built into the system,a unique identifier,so each of the assets do have a a UU ID assigned to it.
Um,
project metadata is created,um,for CR,uh,the CRMs are passed to EMA.
Um,so we do have,uh,through Charter,um,they'll actually create projects outside of the MAM system,
and then,of course,with that MAM,uh,with that project does come metadata,
and then,of course,we can then assign also
not only the UUID but then also the metadata that's part of that project,
uh,to each of the assets as well.
Um,so,
You know,
media workflows that we have non-destructive here.So,um,
what we do is we then
take the media,the original content,we create a proxy from that content,
um,and with that content,then being able to
Um,create that proxy,and then users will view that proxy,
um,and then utilize all their different,uh,workflows and different editing
based on proxy first,and then can link with the original content,
but we never destroy or,or touch that original content until they're
uh actually transcoding from that content to something else,a different codec,and so on.
Um,each of these,uh,projects again can be checked in,checked out,um,
with,uh,uh,with through the panels like with Adobe Premiere because they use all of the Adobe Suite.
Um,you also have built in for charter,
uh,multiple,multiple workflows that they have.So
different types of events,like if metadata changes on a project,
um,maybe process the media a little bit differently or
move the content because it's reached the stage where they've done production and they've distributed.
Distributed the ads,um,the adspot,um,and then delivered that.They can change the metadata then on all that uh uh project and so on,and then that could also trigger then another
type of workflow
to then move that content over to archive and then uh store it,
uh then for uh you know,
to restore.
Later,
um,when needed.
So,a number of conditions that can happen,and again,this is all menu-driven,
which is really nice.So there's no programming here involved and so on.If you do want to,we do have options to
add some scripts and various things,but
um most of this is menu-driven,
where we can actually then go in.
Uh,created,uh,there's an event,
so some type of event like metadata change,
just,
uh,uh,you know,um,any,any date is reached,um,scheduled dates and so on,then there's a condition.So
if it's a condition with the metadata that's available to us and it is,
uh,rights management is A go,
um,because we have a contract to be able to deliver the media,
um,and then you select an action,so like,you know,
uh,deliver the content,
uh,then move the content from one category to another,
um,and then be able to then distribute and deliver that content.
Um,so these are fully automated workflows that we have built in.
Um,they also can be triggered by buttons as well.So if a condition is met or a button is pushed,
these,uh,these,uh,workflows do,uh,process there as well.
So,
on the outbound side,which is quite nice,is you can customize the delivery profiles for packaging,
um,and various sidecar information that's being delivered as well,
um,in different metadata formats that's,uh,that are required,
uh,on the outbound side.So whatever platform we're delivering.
To they may require
like an XML or BFF BXF
uh file,um,or text file or something of that nature.
Uh,we can provide that with the media,
um,and then deliver that to the trendcoder uh for processing and of course,the metadata may be used by a platform we're delivering to
there as well.
Um,
you'll always have
a Hello,this is Chuck Bullo with EMam.
a