Meeting Notes on DAM Solutions

Option 1: Continue with Dynamic Media:
- Emily mentioned that this option involves using an on-cloud solution for dynamic media as well as dynamic media ultimate.
Option 2: Propose Assets on Cloud with Content Hub and Dynamic Media:
- This would entail a centralized DAM solution.
Option 3: Explore Alternatives to Dynamic Media:
- The crib operations team is looking at Binder and Brand Folder.
- This would involve pausing exploration of dynamic media.

Hetal mentioned that Dynamic Media only solved approximately three or four problem statements from the original problem statement table.
It does not meet the requirements of the creative team for a centralized DAM solution.

It was indicated that Content Hub could potentially solve the problems for the creative operations team, aligning with their problem statements.

The team emphasized that any considered option should first satisfy the business's must-have requirements before exploring technical questions and implementation details.
Ideally, a solution would meet 100% of the stated requirements.
Spending $250,000$ to meet only 25% of the requirements isn't justifiable if another team is onboarding a platform that can meet more requirements.

The creative operations team is exploring DAM solutions like Brand Folder and Binder, both of which are cloud-based.

Dynamic Media provides dynamic media components for AE Insights at its highest tier, potentially meeting the needs of both creative operations and video requirements.
The team needs dynamic media with open API to migrate away from Brightcove into AEM.
Alternative DAM solutions might not offer a video player feature, which is crucial for replacing Brightcove.
Some DAM offerings, like Vimeo, may have video players.
The current video setup has opportunities for issues and failures.

Some participants had technical issues, such as audio disconnections, during the meeting.

The team referred to an Excel sheet that contains the problem statements sent to Adobe.
Only a few requirements related to rendition were addressed by Dynamic Media.

Emily will inquire about the pricing of Brand Folder and Binder during an upcoming meeting.

The team is not planning to move forward with just the dynamic media offering.
The focus is on solutions that meet business requirements, such as Assets on Cloud.
A technical call with Adobe was planned to discuss Assets on Cloud implementation questions.
The RFP (Request for Proposal) process for Assets on Cloud has already been completed.
Adobe provided a ten-week migration plan for Assets on Cloud, including content hub and dynamic media.

Migrating to a new platform, be it Assets on Cloud or another DAM solution, will require a complete code rewrite for workflows, schedulers, and asset-related code.
Assets on Cloud provides some familiarity with workflows, server-led processes, schedulers, and APIs, while a new platform would have an entirely new code base.

The team aims to finalize a recommendation by July, with a decision needed as soon as possible.

Hetal might not need to have a technical call with Adobe for Assets on Cloud since many questions have already been answered.

If exploring Assets on Cloud becomes a priority, tasks will need to be prioritized accordingly.

There is a need for defined roles for different offerings like Asset on Cloud, Dynamic Media, and Content Hub.

Video is still a consideration in the conversation, and there's a valuable use case for having video and a video player within a single DAM environment.
All video authoring is currently enabled in assets.
If moving to a different DAM system, a different list of requirements will be needed, including an authoring environment for assets and dynamic pages.

The team needs to ensure that any solution integrates with ti.com, similar to the existing setup.

The team reviewed a demo from Adobe that covered rendition, brand portal, searchability, and other features related to Assets on Cloud.

The team needs to consider whether the cost and effort of migrating are worth resolving the existing issues.

The team needs to ensure that the requirements for chat.com are met with the creative operations team's choices of Binder and Brand Folder.
A document outlining all the integrations that the current DAM has will be shared.

There are concerns about losing existing connections and integrations if moving away from Adobe's platform.
It may be better for the creative operations team to adopt Content Hub.
Moving to a completely different system would be a full-blown re-architecture.

Kelly will update the proposal deck for Assets on Cloud with Dynamic Media and Content Hub.
Budgets are due by June 30.
The team will discuss next steps and obtaining an updated cost from Adobe next week.
Emily meets with the procurement team on Wednesday.
Kenny will put the problem statement table in Confluence, along with the list of connections.