DAM Shortlist Engine

How it works

The DAM Shortlist Engine scores the five DAMSelection segments with fixed weights, ranks them, and lists vendors from the two highest segments until five places are filled.

1. Every segment starts at zero: enterprise content platforms, brand and marketing DAM, product content, packaging and commerce, European specialists, and open source.
2. Each of the 12 answers adds or subtracts points for one or more segments, following the weight table in this section.
3. The engine sorts the segments by total weight. A tie keeps the fixed order enterprise, brand, product, European, open source.
4. The engine walks the highest segment first, then the second, and lists vendors in directory order until the list holds five.
5. A "Yes" to open source also places the open source product content platform from the directory on the list, in fifth position when the list is full.

Weight table

Answers missing from the table add nothing: a moderate budget, few external users, low video, no developers and fewer than 10 brands. The engine also writes a "Why" line that names the answers behind the ranking.

Fact: the directory lists 7 enterprise, 11 brand, 6 product, 5 European and 1 open source vendor. The top segment therefore fills all five places unless open source ranks first. The second segment works as the reserve list for widening the field.

Worked example

The DAM Shortlist Engine loads with example answers that describe a mid-sized product company with an existing PIM.

Worked example: an organisation of 50 to 2,000 employees, 80 active users, 150,000 assets and product imagery as the primary use case. The company runs 3 brands, has few external users, uses Akeneo as its PIM and holds little video. EU data residency is required, the budget is moderate, no developers are available and open source is not preferred.

The engine names product content, packaging and commerce (6 points) and European specialists (3 points) as the best-fit segments. The product segment holds six vendors, so its first five in directory order fill the shortlist. The "Why" line gives three reasons: product imagery points to product content DAM, the existing PIM raises integration depth, and EU residency raises European specialists.

Change one answer to see the sensitivity. Set the use case to brand and marketing assets and brand reaches 5 points, with product and European tied at 3. The tie resolves to product by the fixed order, and the shortlist switches to five brand and marketing vendors.

How to use the result

The DAM Shortlist Engine output opens Checkpoint 4, Shortlist, and becomes the vendor list for the scripted demos at Checkpoint 5.

1. Open each vendor profile from the list in the vendor directory and check the Passport: hosting regions, data residency and pricing archetype.
2. Read your PIM column in the PIM and DAM Fit Map for every shortlisted vendor.
3. Compare the segment definitions in types of DAM systems with your own priorities, and pull a vendor from the second segment when one fails a filter.
4. Apply the hosting, integration and budget filters from longlist to shortlist before sending an RFI.
5. Send every remaining vendor the same script from the Demo Script Generator.

DAMSelection assessment: the engine filters the market and the scripted demo decides the selection. Each vendor runs your scenarios on your assets.

Limitations

The DAM Shortlist Engine is a segment filter with published weights, and four limits follow from that design.

• The list order carries no ranking. Vendors appear in directory order inside a segment, and within-segment ranking publishes when scenario scores complete.
• The weights are a DAMSelection assessment from PIMvendors selection practice. They follow the segment definitions and are published in the page script.
• Thresholds work as steps. One brand and nine brands weigh the same, and 1,000,001 assets add weight where 999,999 add none.
• The engine checks no vendor fact. An EU residency answer raises the European segment and leaves hosting for you to confirm per vendor.

The engine ignores price levels and features, which the other DAM selection tools cover. The scoring methodology explains how scenario scores will rank vendors.