- What is SharePoint 2010? Vision and Reality
view comments - Is There A Business Case For Using SharePoint as an Enterprise CMS?
view comments - iPad 3 vs. New Samsung Tablet: War Starts in February
view comments - Information Architecture - SharePoint's Story
view comments - Wrapping Your Head Around the SharePoint Beast
view comments - SharePoint Implementation the Right Way
view comments - Knowledge Management in 2012? Probably Dead
view comments - 5 Critical Steps to SharePoint Information Architecture Planning
view comments
6 Things to Consider When Selecting A Digital Asset Management Solution
Becoming aware of an issue is one thing. Choosing a solution is another. Once you're aware of how crucial Digital Asset Management, or DAM, is to your organization, you have the fun of trying to sort out which software offerings on the market really are DAM solutions and which suit your particular needs.
DAMs in General
In the white paper Guidelines for Evaluating Digital Asset Management (DAM) Solutions from Interwoven (news, site), the author lists what should be a familiar set of steps for evaluating a DAM solution for anyone who's evaluated a CMS:
- Set goals and expectations
- Identify critical features
- Select a vendor
When it comes to features, in the white paper Best Practices in Selecting a Digital Asset Management (DAM) Solution, Mary Henry, CIO of ASAP!Jack, points out that just like the CMS world, most DAM solutions offer a fairly comparable list of common features, such as:
- Low-resolution thumbnails
- A visual asset browser
- Meta-data/keyword asset search
The following questions will help you sort through the rest.
1. What are your goals and expectations for this project?
Without a clear view of what you want to accomplish with your DAM, you're a bit too much like the Titanic steaming toward its fateful encounter with an iceberg. And just like its captain, you won't know you're in trouble until you hit.
In many cases a DAM is organization-wide, so be sure that those defining what is needed span as many departments as possible with a strong project manager in the kitchen to prevent the effort from collapsing under the weight of too many cooks. You'll need both a short-term and long-term view.
There are experienced firms that can help with this process if an outside guiding hand is needed. Often using one can make things move much faster with less false starts and dead ends.
One thing the Interwoven white paper warns of is scope creep. The project manager(s) will have to ensure that there are boundaries for the initial launch so that you can have it up and running sometime this century, and so that you can work out the kinks with a subset of your staff before unleashing it on the whole company.
2. Will the vendor help you meld the solution into your organization?
Henry suggests focusing on vendors that will "identify and address the critical concerns of each business unit, department, and function to create a comprehensive solution."
The key, she says, is that whatever DAM solution you choose must become a sustainable part of your organization's workflow and processes. "The reality is that digital asset management is not a one-time event," she says, "but rather an ongoing process — a process that your people must embrace, adopt and pursue."
A turnkey solution won't provide what you need. The DAM software and processes must be melded into your organization, and your organization must be melded to integrate the solution into everything they do. Otherwise you're wasting money both on not properly handling your digital assets, but also on software that's not giving you any ROI.
3. Does the solution meet your basic technological needs?
In the same whitepaper, Henry points out technology areas where you do need to double-check the solution against your organization. Ask yourself if a solution supports:
- The operating systems used within your organization — Any OS not supported will result in someone producing or retrieving assets without going through your DAM system, which negates the whole point of having it.
- Files of the number, size and formats you generate - If you have an animation render farm, file size is a non-trivial issue.
- The web browsers being used within your organization — If not, and the DAM solution has a web client, you've got the same problem you have with unsupported OS's.
- The number of users and administrators at various levels that you need to involve.
- Other infrastructure components the DAM may need to integrate with (your web CMS and so on).
4. Does the solution have the critical features you require?
According to Henry, the four major feature approaches taken by DAMs:
Continue reading this article:
Featured Events View all
| Add event
|
RSS
- Feb 22, 2012 – Intelligent Content Palm Springs 2012
- Feb 26, 2012 – SPTechCon - Sharepoint Conference San Francisco 2012
- Mar 6, 2012 – Get Social with Microsoft & Telligent in Dallas
- Mar 8, 2012 – Get Social with Microsoft & Telligent in New York
- Mar 14, 2012 – Get Social with Microsoft & Telligent in Irvine
Who's Hiring? View all
| Post a job
|
RSS
- Communications and Web Content Manager in New York- at Common Ground
- Business Development Specialist in Boise at Balihoo
- Director of Corporate Marketing in Charleston at Blackbaud
- Business Analyst in Ontario at OpenText
- Solutions Engineer in Long Beach at Laserfiche
- Scrum Master/Agile Project Manager in San Diego at MindTouch
- Copywriter in Tokyo at Twitter
- Senior UX/UI Designer in Massachussetts at Mzinga

Receive
the Free CMSWire Newsletter
Email It